Changes

gsm/Makefile.am: add missing kdf/crypto.h

Change-Id: I55fb391d61969357bb55f0834b389f9c701554aa

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

esipa_rest_utils: add support for PSMOs added in SGP.32 V.1.2

SGP.32 adds 3 additional PSMOs:
- setFallbackAttribute
- unsetFallbackAttribute
- setDefaultDpAddress

Change-Id: I03cdd70065a83dfc611d614cf32d817c13fad347
Related: SYS#8100

mnesia_db_euicc: rename timer_setparam to timer_rest

The function timer_setparam is processing REST API orders
in regular intervals. Naming the timer "timer_rest" makes
more sense.

Change-Id: Icfa203477e044ce2cc312d4b6e2693a97191c61d
Related: SYS#8100

esipa_asn1_handler_utils: use maps:find

We can replace maps:is_key and maps:get with a single maps:find call.

Change-Id: I6cc151deef161f3ca4726e6b81ae1f5cc80ad184
Related: SYS#8100

esipa_asn1_handler: store IPAd stateChangeCause

The IPAd may pass a notifyStateChange and a stateChangeCause code.
The notifyStateChange flag tells that a state change happened and
the stateChangeCause code tells what the cause was.

let's store the stateChangeCause code as a state in the euicc
table, so that the REST API user can poll for stateChangeCause
codes in suitable intervals.

Change-Id: I3fe64687786d9184ae82cbb12f9d1292fdc945c8
Related: SYS#8100

restop.py, tryme_*.sh: improve log output and handling

The tryme scripts and the restop.py script produce lots of
distracting and difficult to read log output. Let's renovate
the scripts a bit so that the useful information is displayed
in a readable way.

Change-Id: Id257e7a541fc92386cecee5af3dad2077b62709c
Related: SYS#8100

esipa_middleware: log incompatible requests

The esipa_middleware filters incompatible requests by their protocol
version (X-ADMIN-PROTOCOL), but there is no error logged in that
case. Let's make sure that incompatible requests are brought to the
operator's attention.

Related: SYS#8100
Change-Id: Icadc2434794cbd0f7205181a8d506e1d24ee9d0d

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

mnesia_db_rest: add comment on why we create an euicc entry early

Even though it is technically not necessary, we ensure that an
entry is present in the euicc table on each REST API call. Let's
add a comment to explain why we do it anyway.

Change-Id: Ifb9340655c5f36e074a1a92c0e234ef62c79b9d8
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

esipa_asn1_handler_utils: use eimTransactionId in EuiccPackageErrorUnsigned

EuiccPackageErrorUnsigned contains an eimTransactionId, let's make sure that
it is used (if it is present).

Change-Id: Ibfbc6debcd36d2aae1f4530a608db823caf3a394
Related: SYS#8100

esipa_rest_utils: align IpaEuiccDataResponse to SGP.32 V.1.2

The ASN.1 struct IpaEuiccDataResponse has renamed the error code
member from ipaEuiccDataError to ipaEuiccDataErrorCode. The new
ipaEuiccDataErrorCode is a sequence that has an ipaEuiccDataErrorCode
member, which is the equivalent of the previously existing
ipaEuiccDataError member.

See also: SGP.32, section 2.11.2.2

Change-Id: Ie734a09ed4b0d57de30dc6fb377dfada79ea2ae4
Related: SYS#8100

contrib/tryme_euiccDataRequest: fixup example tag string

The eUICC data request takes a string with TLV tags as input. The
example in this example still uses tags from SGP.32 V.1.0.1, let's
update the string so that it is compliant with SGP.32 V.1.2.

(see also SGP.32, section 2.11.1.2)

Change-Id: I5be04c954330638d3e7d78e8f5f280bebb707efa
Related: SYS:8100

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

rest_handler, cosmetic: clean up order of variable assignments

We assign a couple of varibales before we output them to InfoList,
let's make sure the order is consistent with the order in InfoList.

Related: SYS#8100
Change-Id: I2b998a619cf1db5532bcfe671d6d451d095c37f8

rest_handler: add API versions and schema validation

The JSON based REST API currently has no version checking and also
does not use any JSON schema based validation yet. This patch adds
both. An X-ADMIN-PROTOCOL field in the HTTP header informs about
the API version (same style as the JSON interfaces defined in
GSMA SGP.32 and SGP.22 would use). For incoming messages, the
X-ADMIN-PROTOCOL field is checked to prevent outdated clients from
using the REST API.

The incoming and outgoing JSON messages are now validated against
JSON schema files. Those are the same JSON schema file which were
only provided for documentation purposes only before. Now those
files have been fixed up and moved to the priv directory, where
they are now actively used.

Change-Id: I76e91e53a009cedf2cb1a0297db86e9e5fe7047a
Related: SYS#8100

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

rest_api_response_schema: add missing error codes

In SGP.32 V.1.2, new error codes were added to EnableProfileResult,
DisableProfileResult, DeleteProfileResult and AddEimResult

See also: SGP.32, section 2.11.2

Change-Id: I525ca9d3b7fb870405d374160272d8ec26c85880
Related: SYS#8100

onomondo_eim_app: unify HTTP/HTTPs server startup

The REST API also makes use of the cowboy HTTP server in the same
way as the ESipa API does when running without SSL/TLS. Let's unify
the code in such a way that both HTTP servers call the same startup
helper functions.

Related: SYS#8100
Change-Id: Ie63a97b7ca6873d02866a11226733b37017504cd

esipa_asn1_handler_utils: clean up handling of EuiccPackageResult

The function that handles the parsing and processing of the
EuiccPackageResult is written in a confusing way and also seems
to be slightly wrong (we do not want to re-bind any work item to a
eimTransactionId here). Let's clean it up in a way that is easier
to follow.

Change-Id: Ic2f64c254f3e07ce8dfdf43af977decf3514627b
Related: SYS#8100

testenv: init: check distro argument early

Check the --distro argument and print a proper error, instead of failing
later on with a stack trace if it is unsupported.

Change-Id: I9d51c2b236f10f4c10e991873df47b4f3297e6e1

testenv: support Debian Unstable

Related: SYS#7025#note-10
Change-Id: Ib8f04ee1e8b33f6e724ea2a74b1a96f26746e878

testenv: Dockerfile: rebar3 version via apt-cache

When building for Debian Unstable, we need a higher rebar3 version so it
is compatible with the Erlang OTP version in the distribution. Get the
version of rebar3 from the distribution via apt-cache and download it
instead of hardcoding a version number.

Related: OS#7025#note-10
Change-Id: Ie3c8812c41648dd5ca655114dec00ae7d48eaba8

testenv: init: check distro argument early

Check the --distro argument and print a proper error, instead of failing
later on with a stack trace if it is unsupported.

Change-Id: I9d51c2b236f10f4c10e991873df47b4f3297e6e1

Bump version: 0.1.2

Change-Id: I350f6ed32b1c9543c2985c7991ee3d5a6dce1c1c

rebar.lock: use a more recent version of gen_netlink

This works around a compiler bug in OTP 29.0.3 [1].

Change-Id: Iae0c4b3827c7ae5c8076fbf782adf8db02d975ea
Related: [1] https://github.com/erlang/otp/issues/11368
Related: OS#7025

Bump version: 1.9.2.3-2ef2 → 1.9.3

Change-Id: I276fec3ff862da688eefd9b2738fedbdedd4ef32

debian-{bullseye,bookworm}-titan[-master]: drop libfftranscode

We've meanwhile migrated to more recent TITAN release that can do
ASN.1 PER encoding/decoding, so libfftranscode is no longer needed.

Change-Id: If68f478d29f4728a9f3518b20128b195a8267955
Related: OS#6490

Install osmo-python-tests with pip

Use pip to install osmo-python-tests instead of calling setup.py, so it
works with modern python packaging as well.

Related: osmo-python-tests I186544163ab02834c33f1363f3a06cd380898f56
Change-Id: I9bb5d13897dbf1be9855c4eba29c6b3a2c35729c

debian-bullseye-jenkins*: remove

This container does not build anymore (fails on "License classifiers
have been superseded by license expressions" while installing
lcov-to-cobertura-xml with pip). This means it is unused, remove it.

Change-Id: Iec6ecbc7446aaf3a643aec0168264dba3e671894

debian-sid-jenkins: remove

This container is not being used, and it still attempts to install
python2 which has been removed from debian sid quite some time ago.
Let's remove it.

Change-Id: Ia7e2a92cba81a51bae409e0dadfd592204bce6d0

debian-buster-jenkins*: remove

We are clearly not using these containers anymore, as they fail to
build:

  0.297 Err:4 http://deb.debian.org/debian buster Release
  0.297   404  Not Found [IP: 199.232.190.132 80]
  0.305 Err:5 http://deb.debian.org/debian-security buster/updates Release
  0.305   404  Not Found [IP: 199.232.190.132 80]
  0.314 Err:6 http://deb.debian.org/debian buster-updates Release
  0.314   404  Not Found [IP: 199.232.190.132 80]
  0.320 Reading package lists...
  0.334 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
  0.334 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
  0.334 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.

Change-Id: Ia7fc6aac738738c1a3929ad92ae93d0f2d6a825d

Modernize python packaging

When building the debian package, we get the following deprecation
warning. Modernize the python packaging to fix it, before it stops
working altogether. Keep the old setup.py in contrib so we can still
build for older debian releases.

Fix for:
  SetuptoolsDeprecationWarning: setup.py install is deprecated.
  !!

          ********************************************************************************
          Please avoid running ``setup.py`` directly.
          Instead, use pypa/build, pypa/installer or other
          standards-based tools.

          See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
          ********************************************************************************

  !!

Depends: docker-playground I9bb5d13897dbf1be9855c4eba29c6b3a2c35729c
Change-Id: I186544163ab02834c33f1363f3a06cd380898f56

Implement vendor requests to set debug/break_on_panic

Use vendor request in to read and set the break_on_panic.
In the future this vendor request could be also used to set other
debug related options.

Change-Id: Ia2bffa05b96e3857610cb3ad2f9122fa75a90780

cosmetic: fix missing spaces in string_req_h

Change-Id: Ia92ac605d83718399f19db67057e740ceaa8c37f

V1.2: EuiccResultData.setFallbackAttribute / unsetFallbackAttribute

Add setFallbackAttribute and unsetFallbackAttribute to EuiccResultData.

The IoT eUICC emulation just acknowledges the operation with a log
message and does nothing. A non IoT eUICC does not support fallback.

Reference: SGP.32 Section 2.11.1.1.3

Related: SYS#8101
Change-Id: I59fba32cb12de22f71b3238adcbab5fc7f66e991

WIP: Add refreshFlag

Ich weiss nicht die Bohne, was das hier soll. TBD!!!

5.9.15

TBD: explain why this is always true
Change-Id: I7d8f9182b675ca0851e00ef8d36201151f30178f

V1.2: Add error codes to GetEimPackageResponse

Add several new error codes to eimPackageError in GetEimPackageResponse.
These errors are displayed during IPA process.

Reference: SGP.23 Section 6.3.2.6

Related: SYS#8101
Change-Id: Ic0cdce1f5269794f37c5da3a63985706a7959184

V1.2: Update imported ASN.1 definitions

Define what ASN.1 defintions are inported from RSPDefinitions by
SGP32Definitions.

Related: SYS#8101
Change-Id: Id86c682e5c9fee43b6af6ec011b91565b82fa776

V1.2: Add eimTransactionId to InitiateAuthenticationRequestEsipa

Add new eimTransactionId field to InitiateAuthenticationRequestEsipa.

The eimTransactionId walks through the IPA process like this:

* The eimTransactionId is retrieved from ProfileDownloadTriggerRequest
   at proc_eim_pkg_retr.c.
* Then it is handed to the Common Mutual Authentication Procedure at
   proc_indirect_prfle_dwnld.c.
* There it is handed to the InitiateAuthentication function at
   proc_cmn_mtl_auth.c.
* There it is stored in initiateAuthenticationRequestEsipa at
   esipa_init_auth.c.

Reference: SGP.32 Section 5.14.1

Related: SYS#8101
Change-Id: I1c8ef6fc0a3f7ab5735e401597fc8c6b2021fc09

V1.2: Add new error codes to EnableProfileResult, DisableProfileResult, DeleteProfileResult, AddEimResult

Reference: SGP.32 Section 2.11.2

New error code of AddEimResult is used at IoT eUICC emulation.

Related: SYS#8101
Change-Id: Idb023c994770fe4ee048da128026f566bd7fe146

V1.2: Add function ES10b.GetConnectivityParameters

Add new library function to get connectivity parameters from IoT eUICC.
Also add an option to the command line interface to call the library
function.

The function cannot be emulated with non-IoT eUICC.

Reference: SGP.32 Section 5.9.24

Related: SYS#8101
Change-Id: I075590e095dbbe05fa6cdb0a96d5b38c7a17ff78

V1.2: Rename euiccCiPKId of IpaEuiccDataRequest to euiccCiPKIdentifierToBeUsed

Reference: SGP.32 Section 2.11.1.2

Related: SYS#8101
Change-Id: Id397206316721962cd534e8131fe2a3b6979d828

V1.2: Change names and structure in IpaEuiccData

The “SEQUENCE OF SGP32-PendingNotification” is now direct member of the
IpaEuiccData.

The notficationList in IpaEuiccDataResponse is taken from the
RetrieveNotificationsListResponse. After the structure change, the ASN.1
compiler creates two equal definitions in the header files. An
assignment causes a C compiler error, so that the pointer to the list
must be casted to the definition of the response. (See
ipa_proc_euicc_data_req().)

Reference: SGP.32 Section 2.11.2.2

Related: SYS#8101
Change-Id: I0dc80706bff5b2020cbd31a57c9526aae9d50169

V1.2: Add AuthenticateResponseOk and EuiccSigned1

Both structures are taken from SGP.22 but do not change. The IPA process uses these new structures, because the may be expanded in the future.

Reference: SGP.23 Section 5.14.3

Related: SYS#8101
Change-Id: I501247132de30618a2b1ace44c7c3772ab42eb09

V1.2: Add new causes to initiateAuthenticationErrorEsipa

Reference: SGP.32 Section 6.3.2.1

Related: SYS#8101
Change-Id: I0a9acaba7b706f68bc89bae3dff7d2d0e380e797

V1.2: Add new fields to EUICCInfo2

Add fields euiccCiPKIdListForSigningV3, additionalEuiccInfo and
highestSvn to EUICCInfo2. Also add fields to SGP.22 version of
EUICCInfo2.

The IoT eUICC emulation converts the fields that are now supported in
both versions. These fields are only available if eUICC supports SGP.22
V3.0.

Reference: SGP.32 Section 5.9.2

Related: SYS#8101
Change-Id: I808139f1b2bfde5fba5320bf7582afa5d8fe6019

V1.2: Add function ES10b.ExecuteFallbackMechanism

Add new library function to enable the fallback profile on IoT eUICC.
Also add an option to the command line interface to call the library
function. The optional refresh flag may be set via command line option.

The function cannot be emulated with non-IoT eUICC.

Reference: SGP.32 Section 5.9.20

Related: SYS#8101
Change-Id: Ia751f0888c36f39ddfadf7f8bb923a8ee50178dc

V1.2: Add setDefaultDpAddress function

Add setDefaultDpAddress to EuiccResultData. Implement the SGP.32
function SetDefaultDpAddress and handle the setDefaultDpAddress PSMO.

The IoT eUICC emulation uses the non-IoT eUICC SGP.22 function
SetDefaultDpAddress.

Reference: SGP.32 Section 2.11.1.1.3

Related: SYS#8101
Change-Id: I514b03240289469142e6a41a7290a4afce199318

V1.2: Remove error code from ListEimResult

Remove the commandError code from listEimError in ListEimResult. The
IPA process must use undefinedError instead.

Reference: SGP.23 Section 2.11.2.1

Related: SYS#8101
Change-Id: I8acb868970a589e70c1688427994854f9393a01b

V1.2: Add eimTransactionId to EuiccPackageErrorUnsigned

Add new field eimTransactionId to EuiccPackageErrorUnsigned. The IoT
eUICC emulation set this field, if found in EuiccPackageSigned of
EuiccPackageRequest.

Reference: SGP.23 Section 2.11.2.1

Related: SYS#8101
Change-Id: Idfd596c56ef8cfe745f96cbaa6b8a5537927a919

V1.2: Add size constraint to EimConfigurationData.eimId

The size constraint has no impact on the existing code, because it only
reads string data from structure.

Reference: SGP.32 Section 2.11.1.1.1

Related: SYS#8101
Change-Id: Iafe940876763215a28b9f9067eda090f25ad836c

V1.2: Add new fields to ProfileInfo list

Add new tags for ecallIndication, fallbackAttribute and fallbackAllowed.

They new are not supported by non IoT eUICC. The IoT eUICC emulation
will remove the unsupported tags from the ProfileInfoListRequest and
later adds the requested fields to the ProfileInfoListResponse with the
value 'false'.

Reference SGP.32 Section 2.11.1.1.3

Related: SYS#8101
Change-Id: I6667dba8dd84817cfee69daa1c44b98239fa171c

V1.2: Add new fields to IoTSpecificInfo

Add ecallSupported and fallbackSupported to IoTSpecificInfo, There is
no impact on IPA process, because it is not used.

Reference: SGP.32 Section 5.9.2

Related: SYS#8101
Change-Id: Iba95ac8dd059ee48d46f2ace54ece7a3338ae79f

V1.2: Add SGP.32-custom StoreMetadata

Add new StoreMetadata, which overrides and expands StoreMetadata from
SGP.22. There is no impact on IPA process, because it is optional and
not used.

Reference: SGP.32 Section 5.5

Related: SYS#8101
Change-Id: Icfbc141dda82f091bcc9a1d7177e9fdb5b424750

WIP: Add eimId to GetEimConfigurationDataRequest

Add search criteria eimId to GetEimConfigurationDataRequest. The IoT
eUICC emulation does not require this, because it returns an empty
result anyway.

Reference: SGP.23 Section: 5.9.18

Related: SYS#8101
Change-Id: Ia8aacd9d5b8ec7a9d524a446114557efdb0614f5

V1.2: Change tag in TransferEimPackageResponse

Change tag value of notificationList in TransferEimPackageResponse.
Also change it from RetrieveNotificationsListResponse to
PendingNotificationList.

Reference: SGP.23 Section 6.3.1

Related: SYS#8101
Change-Id: I4c9cdd1b79ec22a1d5e36d1720cf5c703890c28b

V1.2: Change tag of eimIdType in EimIdInfo

Reference: SGP.23 Section 2.11.2.1

Related: SYS#8101
Change-Id: Id96353ef74ffe51aa7de4848832f32e8f58ab4df

V1.2: Rename internal structure names from "auto" to "immediate"

Rename all occurrences of "auto" or similar to "immediate" or similar
respectively.

Reference: SGP.32 Section 2.9.2

Related: SYS#8101
Change-Id: Iad212f9b3e4430d4eaa6d4afdac0e73009275dfb

V1.2: Add EimConfigurationData.indirectProfileDownload

The flag indicates, if eIM supports indirect download. As the current
version of IPA only supports indirect download, this flag is checked. If
it is not supported, profile download is rejected.

get_euicc_ci_pkid() is renamed to get_euicc_ci_pkid_ipd(), to indicate
that it also gets this flag.

This also requires an update of contrib/sample_eim_cfg.ber, which is a
BER encoded EimConfigurationData.

Reference: SGP.32 Section 2.11.1.1.1

Related: SYS#8101
Change-Id: Ic40111531e6f35d5ea7f3789de6cae0f1c0d5ba7

V1.2: Add function ES10b.DisableEmergencyProfile

Add new library function to disable emergency profile on IoT eUICC.
Also add an option to the command line interface to call the library
function. The optional refresh flag may be set via command line option.

The function cannot be emulated with non-IoT eUICC.

Reference: SGP.32 Section 5.9.23

Related: SYS#8101
Change-Id: I2af2077228fb8c5fa3f254acc15bd0afaa33fe43

V1.2: Change fields in ProvideEimPackage(Result)

Change parameters in ProvideEimPackage and ProvideEimPackageResult. The
structure is changed in IPA too. The new field eimTransactionId of
EimPackageResultResponseError is filled with the eimTransactionId of
IpaEuiccDataRequest, if exists.

Reference: SGP.32 Section 5.14.6

Related: SYS#8101
Change-Id: I24baab4f9351aec27c58403b94974cba4b274c34

V1.2: Rename searchCriteria of IpaEuiccDataRequest to searchCriteriaNotification

Reference: SGP.32 Section 2.11.1.2

Related: SYS#8101
Change-Id: I245c2c1c1c5cdd2be387d515d1bf51d0bf82ef41

V1.2: Change field name in InitiateAuthenticationOkEsipa

Change the fiel name euiccCiPKIdToBeUsed in
InitiateAuthenticationOkEsipa to euiccCiPKIdentifierToBeUsed.

Reference: SGP.32 Section 6.3.2.1

Related: SYS#8101
Change-Id: I68d59b44bd8b5dd23ae070d42dab9727c0da5272

V1.2: Rename EuiccPackageSigned.transactionId to EuiccPackageSigned.eimTransactionId

Reference: SGP.32 Section 2.11.1.1

Related: SYS#8101
Change-Id: I46270d626d64f4ca6513423d9cebfc929076027d

V1.2: Specify tag values in HandleNotificationEsipa

Add specific tag values to fields in HandleNotificationEsipa.

Reference: SGP.23 Section 6.3.2.4

Related: SYS#8101
Change-Id: I3abeb7295fd43e499105086a49bd62c4f835aeed

V1.2: Add function ES10b.ReturnFromFallback

Add new library function to return from fallback profile on IoT eUICC.
Also add an option to the command line interface to call the library
function. The optional refresh flag may be set via command line
option.

The function cannot be emulated with non-IoT eUICC.

Reference: SGP.32 Section 5.9.21

Related: SYS#8101
Change-Id: Ib49a8ef3a5ea5639d881ca51eaeeea24f083fe0e

V1.2: Add IPAe related ASN.1 templates

There is no use of these templates, as beeing IPAe is not supported.

Reference: SGP.32 Section 3.8.4

Related: SYS#8101
Change-Id: I7d659734bfac44da4f1f3d5bca80314b2f20c299

V1.2: Change fields in RetrieveNotificationsListResponse

Remove notificationAndEprList and restructure definitions in
RetrieveNotificationsListResponse.

This requires name changes in IPA process. The notificationAndEprList
case is removed.

Reference: SGP.32 Section 5.9.11

Related: SYS#8101
Change-Id: I757586e92c5eb1ca54ddf8ab6f71eb418de20f6e

V1.2: Rename field in GetBoundProfilePackageResponseEsipa

Rename field profileMetadataMismatch to metadataMismatch in
GetBoundProfilePackageResponseEsipa.

Reference: SGP.23 Section 6.3.2.3

Related: SYS#8101
Change-Id: I87965b68bde39d29317f9848aa3a88d9966c4e78

Generate ASN.1 code with recent master branch of asn1c

Commit-Hash of asn1c using from now on:
2f7f40dab3973f707d66f4a67cae0cc1bc8e62b5

Related: SYS#8101
Change-Id: I1ac4cf8980af501bb119208213242468ee4f3c06

V1.2: Update from "EnableUsingDD" to "ImmediateEnable" function

Work on 5.9.15 -> Renamed things and added ASN.1 fields, but no
processing of these fields yet.

Reference: SGP.32 Section 5.9.15

Related: SYS#8101
Change-Id: Id750b2f5ca6c08a013aa30f876aa37e6291a30d5

WIP: Change of IpaEuiccDataRequest

Section 2.11.1.2

* Changed tags
* Two search criteria: searchCriteriaNotification, searchCriteriaEuiccPackageResult

This patch is totally wrong. The filter cannot work, because it reads
from the wrong choice. If eIM asks for eUICC Package Results, we need to
return that result.

We have to generade the list in convert_notification_list() with the
correct choice. Do we have all the required information?

Change-Id: I411111c71787ce27615b6b66fc8b19488883d15b

V1.2: Add size constraints to eimId

The remaining eimId in EuiccPackageResultDataSigned,
EuiccPackageErrorDataSigned, EuiccPackageErrorUnsigned and EimIdInfo
are now limited to 128 characters.

The limit has no impact on the process. Assignments are made from other
eimID of other structures that are also limited to 128.

At some location the eimId is set from 'eim_id' of context structure,
which is received by EimConfigurationData which is also limited to 128.

Reference: SGP.32 Section 2.11.2

Related: SYS#8101
Change-Id: I5a0f52c0aa4851e802909f98d5a5677e596c4d7f

V1.2: Add function to set Device Capabilities

Add new library function to set the SGP.22 Device Capabilities. Also
add an option to the command line interface to call the library
function.

The IoT device (modem) may and the IPA must set Device Capabilities.
They cannot be set independently. The IoT device would overwrite what
IPA has set and vice versa. Therefore add a library function for the
IoT device that takes care about setting the required capabilities for
IPA.

Reference: SGP.22 Section 3.4.2

Related: SYS#8101
Change-Id: I866787b8cda9a87a9f2e0db4965fbb554d339a6c

V1.2: Add eimTransactionId to IpaEuiccDataRequest and IpaEuiccDataResponse

Add eimTransactionId to IpaEuiccDataRequest and to
IpaEuiccDataResponseError  or IpaEuiccData of IpaEuiccDataResponse.
The IPA takes the transaction ID from the request, if exists, and sets
it in the response. The eIM can use it to match the request with the
successful or unsuccessful outcome.

Reference: SGP.32 Section 2.11.1.2

Related: SYS#8101
Change-Id: I34db78c4eb8461c154459204ec13a2184085e96a

V1.2: Rename "Automatic" -> "Immediate" in ASN.1 definitions

Rename all occurrences of "Automatic" or "AutomaticEnable" or similar to
"Immediate" or "ImmediateEnable" or similar respectively.

Reference: SGP.32 Section 2.9.2

Related: SYS#8101
Change-Id: I2b18e5cf65269347ce40e5e9560ab934e75a92a6

V1.2: Add StateChangeCause to GetEimPackageRequest

State change notification is optional and currently not supported by
IPA.

Reference: SGP.32 Section 6.3.2.6

Related: SYS#8101
Change-Id: I1ae561f6709a9eb490fa7a53420c332ff20bd058

Minor fix of compiler warning in esipa.c

Related: SYS#8101
Change-Id: Ied72573a5fd4486f59e0fe71ae678374cafd6b19

V1.2: Add eimValue to CompactOtherSignedNotification

The IPA just forwards the message, so no change in process is required.

Reference: SGP.23 Section 5.14.7

Related: SYS#8101
Change-Id: I0183ef6555d23d762e6c8fa8584453b3a07d4940

V1.2: Add function ES10b.EnableEmergencyProfile

Add new library function to enable emergency profile on IoT eUICC.
Also add an option to the command line interface to call the library
function. The optional refresh flag may be set via command line option.

The function cannot be emulated with non-IoT eUICC.

Reference: SGP.32 Section 5.9.22

Related: SYS#8101
Change-Id: I0304b869a14a36b82cc2d1676b2a5f613e1da171

V1.2: Add TERMINAL CAPABILITY for IoT support

Also enable support for IoT function by setting the TERMINAL CAPABILITY.
If not set, eUICC may not support IoT specific functions. With IoT eUICC
emulation it is disabled.

Reference: SGP.32 Section 3.8.2

Related: SYS#8101
Change-Id: I1116bee93b31ee4a159125d840d7c5866be6fdb4

V1.2: Add SGP.32-custom AuthenticateClientRequest

Add new AuthenticateClientRequest, which overrides and expands
AuthenticateClientRequest from SGP.22. There is no impact on IPA
process, because it is not used.

Reference: SGP.32 Section 5.6.1

Related: SYS#8101
Change-Id: I0003994fb82f8bbccb4de19946bbba975c98ef04

V1.2: Add more error codes to AddInitialEimResponse

Reference: SGP.32 Section 3.5.2

Related: SYS#8101
Change-Id: Ib4bc1e06b6571d18ff46080f5e5ba1fe3bc0be70

V1.2: Rename field in PSMO

Rename two field in PSMO.

Reference: SGP.23 Section 2.11.1.1.3

Related: SYS#8101
Change-Id: I9336f18aaf104629845948877294437188979376

V1.2: Add new flags to eUICCMemoryReset

Introduce flags to reset pre-installed test profiles and provisioning
profiles.

The IoT eUICC emulation forwards these flags. The eUICC with V3.0 of
SGP.22 will delete these profiles.

Reference: SGP.32 Section 5.9.5, SGP.22 Section 5.7.19

Related: SYS#8101
Change-Id: I8c683e93c2a10ff64c3ef14767000c59f81be090

V1.2: Cange remaining ASN1 definition to SGP.32 V1.2

These changes are cosmetic or have no impact on functionality.

Related: SYS#8101
Change-Id: Ifa2546784a6d75170e4f5aae2a5e98edb2c0627a

V1.2: Rename TransactionId in EuiccPackageResultDataSigned

Reference: SGP.32 Section 2.11.2

Related: SYS#8101
Change-Id: I5515bfbff91c1fb4ecd90bb151b499b223f7d673

V1.2: Add profileDownloadErrorReason to ProfileDownloadTriggerResult

Reference: SGP.32 Section 2.11.2.3

Related: SYS#8101
Change-Id: Ia5da46a793db54f2e2671be2b50dd1dddc97e318

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

saip.PES.rebuild_mandatory_services(): set 5G get-identity, profile-a-x25519, profile-b-p256

Related: SYS#8096 SYS#8037
Change-Id: Ibc29c6437c5c92e2b14938b733156536863465c1

rebar.config: use more recent rebar3_diameter_compiler

This fixes building on Erlang/OTP 29.  Our pull request [1] has
been merged upstream, but no release has been tagged yet.

[1] https://github.com/carlosedp/rebar3_diameter_compiler/pull/28

Change-Id: I548a3fef6f8a23a548fb6376076b9d4a9345d692
Related: OS#7025

stp: M3UA: add a TC for `as groups` which prevents traffic between group member

The idea is to put multiple AS into a group. If traffic should be
rounted from one group membert to another, drop those traffic.

Change-Id: I2e734ef3d42e6da292edef00618f227037d79a1f

stp: TCAP: tests `tcap-unroutable-sessions route-fallback`

The route fallback allows to route TCAP packets which can't be matched nor
assigned to a ASP by TCAP id, to be routed to a different instance.

Change-Id: I70ef08df0d86ee64aeec9321f6db2b2a8b7bd091

Add UDTS

Change-Id: Ieaf9590b915e64b2cfa663c17f146d60845f4403

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

firmware: Drop CEMU_TX_DATA when sim is in-active

When the emulated sim is in reset or without power, drop
CEMU_TX_DATA.

Change-Id: I796e548225a742cddfde12bd6a60e4d2e5c04c8f

firmware: Add talloc_report_buf() encode the allocation by bits

First byte encodes the amount of blocks.
The following bytes encode a block as a single bit.

Change-Id: I3a8ddbe4100f342db2c59ad1fb9aa0014efc62b8

WIP: implement loop prevention over AS groups

TODOs:

* show as: groups
* show asp: groups
* show group GROUPNAME
* write vty config
* vty tests

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

WIP: implement loop prevention over AS groups

TODOs:

* show as: groups
* show asp: groups
* show group GROUPNAME
* write vty config
* vty tests

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

WIP: implement loop prevention over AS groups

TODOs:

* show as: groups
* show asp: groups
* show group GROUPNAME
* write vty config
* vty tests

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

TCAP: Refactoring unroutable messages into own function

In preparation of adding another method to handle those.

Change-Id: Ib4d114273423730418458767d17b11de9bd815d4

WIP: implement loop prevention over AS groups

TODOs:

* show as: groups
* show asp: groups
* show group GROUPNAME
* write vty config

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

TCAP: implement a fallback routing

If a TCAP message from an ongoing session can't be routed by
either the TCAP session cache or by the destination TID to a known
node, allow to route the MSU to a different destination.

Change-Id: I3e4e634b38a1845c2ce62a3805ff91a530520d88

esipa_asn1_handler_utils: use eimTransactionId in EuiccPackageErrorUnsigned

EuiccPackageErrorUnsigned contains an eimTransactionId, let's make sure that
it is used (if it is present).

Change-Id: Ibfbc6debcd36d2aae1f4530a608db823caf3a394
Related: SYS#8100

esipa_asn1_handler_utils: clean up handling of EuiccPackageResult

The function that handles the parsing and processing of the
EuiccPackageResult is written in a confusing way and also seems
to be slightly wrong (we do not want to re-bind any work item to a
eimTransactionId here). Let's clean it up in a way that is easier
to follow.

Change-Id: Ic2f64c254f3e07ce8dfdf43af977decf3514627b
Related: SYS#8100

doc/build.md: fix typo

Change-Id: Ie6a066f3289fbdde40f55bd9f38a3dd90102e7e6
Related: SYS#8100

restop.py, tryme_*.sh: improve log output and handling

The tryme scripts and the restop.py script produce lots of
distracting and difficult to read log output. Let's renovate
the scripts a bit so that the useful information is displayed
in a readable way.

Change-Id: I7fe40e7ed50354114e80cd96a5b40f3e579220e9
Related SYS#8100

Change-Id: Id257e7a541fc92386cecee5af3dad2077b62709c

mnesia_db_euicc: renovate handling of euicc table (mnesia, REST)

The REST API that allows users to set certain eUICC parameters
(we call them "states" from now on) only allows to set eUICC
states, but doesn't allow to read them back.

With this patch, we renovate the handling of the mnesia euicc
table from the ground up so that REST API users have read and
write access to the states stored in the mnesia euicc table.

Change-Id: I74c602555b194a28d6eb9dd67ec4c6a8865fcb77
Related: SYS#8100

esipa_asn1_handler: store IPAd stateChangeCause

The IPAd may pass a notifyStateChange and a stateChangeCause code.
The notifyStateChange flag tells that a state change happened and
the stateChangeCause code tells what the cause was.

let's store the stateChangeCause code as a state in the euicc
table, so that the REST API user can poll for stateChangeCause
codes in suitable intervals.

Change-Id: I3fe64687786d9184ae82cbb12f9d1292fdc945c8
Related: SYS#8100

SGP32Definitions_Templates: rename tr/ts_getEimPackageResponse_eimPkgErrUndef

The template name suffix _eimPkgErrUndef is a bit unflexible. Let's change
it to eimPkgErr and add a parameter erroCode with a default value. This
allows us to use the template with any eimPackageError.

Change-Id: I81b7c3b5ebc8c95d8ea8f1a6030b884ed2efcff3
Related: SYS#8100

eIM: echo eimTransactionId from euiccDataReq in provideEimPackageResult

The udted eIM now includes an eimTransactionId in its ipaEuiccDataRequest
message, which means that the IPAd (testsuite) has to echo that exact
same eimTransactionId in the IpaEuiccData of the IpaEuiccDataResponse

Related: SYS#8100
Change-Id: I286362e6499eb9440e006f08b7c142c6dfd98843

eIM, REST: use template to encode eimConfigurationData

We currently use a hardcoded binary blob for the testcases that test the
addEim and updateEim eCOs. Let's use the enc_EimConfigurationData encoder
function, which we already have, to encode the eimConfigurationData
instead.

Related: SYS#8100
Change-Id: Ic51731da355cd9a209837d4015c02943367ed90b

eIM, add new PSMOs introduced with SGP.32 V.1.2

SGP.32 V.1.2 adds new PSMOs, which are setFallbackAttribute,
unsetFallbackAttribute and setDefaultDpAddress. Let's add testcases
for those.

Related: SYS#8100
Change-Id: Ic2416dc06d917228b71c61da9acebed26d68b2d9

eIM_Tests: add testcase to test stateChangeCause/stateChangeCause

The IPAd may pass a stateChangeCause with the getEimPackageRequest.
The stateChangeCause is then recorded by the eIM and can be queried
via the REST API. This patch adds a testcase to verify that
functionality.

Related: SYS#8100
Change-Id: I6befc43f2dfd2178e352b9ab0a24a04d6e116fbb

eIM: use eimTransactionId during profile download

When the eIM initiates a profile download via the
profileDownloadTriggerRequest, it includes an eimTransactionId to identify
sent by the IPAd (testsuite) in the initiateAuthenticationRequestEsipa
response. The eimTransactionId (even though it is optional) is essential
for the eIM to recognize the response from the eIM correctly.

(SGP.32 V.1.0.1 lacked the eimTransactionId, which meant that the eIM had
to rely on other identifiers such as the TCP connection itself. The problem
is now fixed with SGP.32 V.1.2)

Related: SYS#8100
Change-Id: I045d93b9f40ddfb3dc6dfbd9602e736bbc6b4abc

eIM: add testcase to test an unsuccessful eUICC data request

When we test the ipaEuiccDataRequest/IpaEuiccDataResponse, we currently
only test the success case. However, we should also test the failure
case, bceause an IpaEuiccDataResponseError can also contain an
eimTransactionId, which has to be equal to the eimTransactionId we have
received with the ipaEuiccDataRequest

Related: SYS#8100
Change-Id: Ied212eb636cf46df5fc9f86ddee15c242c50d45a

systemd: run db-upgrade script in ExecStartPre

We have seen in CI jobs that calling the DB upgrade script from
debian/postinst does not work reliably.

When doing a fresh install of osmo-hlr, it usually works as expected:

  Setting up osmo-hlr (1.9.2) ...
  osmo-hlr-post-upgrade: nothing to do (no existing database)

But sometimes:

  Setting up osmo-hlr (1.9.2) ...
  osmo-hlr-post-upgrade: database upgrade is required
  osmo-hlr-post-upgrade: stopping osmo-hlr service
  osmo-hlr-post-upgrade: creating backup: /var/lib/osmocom/hlr.db.20260706135658.bak
  osmo-hlr-post-upgrade: performing database upgrade
  <0001> db.c:600 using database: /var/lib/osmocom/hlr.db
  <0001> db.c:103 (283) recovered 4 frames from WAL file /var/lib/osmocom/hlr.db-wal
  <0001> db.c:679 Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 0
  <0001> db.c:103 (1) duplicate column name: last_lu_seen in "ALTER TABLE subscriber ADD COLUMN last_lu_seen TIMESTAMP default NULL"
  <0001> db.c:248 Unable to prepare SQL statement 'ALTER TABLE subscriber ADD COLUMN last_lu_seen TIMESTAMP default NULL'
  <0001> db.c:318 Unable to update HLR database schema to version 1
  <0001> db.c:685 Failed to upgrade HLR DB schema to version 1: (rc=1) duplicate column name: last_lu_seen
  <0000> hlr_db_tool.c:509 Error opening database

It seems that osmo-hlr can get started before the osmo-hlr-post-upgrade
script runs, then starts to create the database with the current schema,
and gets stopped before it is done, leading to the failure above.

Rename the script to osmo-hlr-db-upgrade.sh, remove logic for stopping
and starting the service and let systemd call it in ExecStartPre. That
way we are sure that it runs *before* osmo-hlr starts up.

Related: SYS#8125
Change-Id: If13f4c8b49397e6630956e92a7825843c7d55ebd

systemd: run db-upgrade script in ExecStartPre

We have seen in CI jobs that calling the DB upgrade script from
debian/postinst does not work reliably.

When doing a fresh install of osmo-hlr, it usually works as expected:

  Setting up osmo-hlr (1.9.2) ...
  osmo-hlr-post-upgrade: nothing to do (no existing database)

But sometimes:

  Setting up osmo-hlr (1.9.2) ...
  osmo-hlr-post-upgrade: database upgrade is required
  osmo-hlr-post-upgrade: stopping osmo-hlr service
  osmo-hlr-post-upgrade: creating backup: /var/lib/osmocom/hlr.db.20260706135658.bak
  osmo-hlr-post-upgrade: performing database upgrade
  <0001> db.c:600 using database: /var/lib/osmocom/hlr.db
  <0001> db.c:103 (283) recovered 4 frames from WAL file /var/lib/osmocom/hlr.db-wal
  <0001> db.c:679 Database '/var/lib/osmocom/hlr.db' has HLR DB schema version 0
  <0001> db.c:103 (1) duplicate column name: last_lu_seen in "ALTER TABLE subscriber ADD COLUMN last_lu_seen TIMESTAMP default NULL"
  <0001> db.c:248 Unable to prepare SQL statement 'ALTER TABLE subscriber ADD COLUMN last_lu_seen TIMESTAMP default NULL'
  <0001> db.c:318 Unable to update HLR database schema to version 1
  <0001> db.c:685 Failed to upgrade HLR DB schema to version 1: (rc=1) duplicate column name: last_lu_seen
  <0000> hlr_db_tool.c:509 Error opening database

It seems that osmo-hlr can get started before the osmo-hlr-post-upgrade
script runs, then starts to create the database with the current schema,
and gets stopped before it is done, leading to the failure above.

Rename the script to osmo-hlr-db-upgrade.sh, remove logic for stopping
and starting the service and let systemd call it in ExecStartPre. That
way we are sure that it runs *before* osmo-hlr starts up.

Related: SYS#8125
Change-Id: If13f4c8b49397e6630956e92a7825843c7d55ebd

WIP: implement loop prevention over AS groups

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

WIP: implement loop prevention over AS groups

Change-Id: Ice548cedf12d4a9e69f5e7aaf1d2df9e14d7f016

TCAP: Refactoring unroutable messages into own function

In preparation of adding another method to handle those.

Change-Id: Ib4d114273423730418458767d17b11de9bd815d4

TCAP: implement a fallback routing

If a TCAP message from an ongoing session can't be routed by
either the TCAP session cache or by the destination TID to a known
node, allow to route the MSU to a different destination.

Change-Id: I3e4e634b38a1845c2ce62a3805ff91a530520d88

firmware: Add talloc_report_buf() encode the allocation by bits

First byte encodes the amount of blocks.
The following bytes encode a block as a single bit.

Change-Id: I3a8ddbe4100f342db2c59ad1fb9aa0014efc62b8

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

contrib: add usb_vendor_request.py script to collect debug infos

Change-Id: Ie18e171c684ce9d67e711e3d6fda6850d5fc9e7e

firmware: card_emu.h: add missing header stdbool.h.

Change-Id: I4ad6d5cf0b4477cbd5f761d70c4cd92fb3ca1fcd

README.md: describe the debug uart

Change-Id: I4cf929fded962e7ffb4c01628279385b2af04157

firmware: Add talloc_report_buf() encode the allocation by bits

First byte encodes the amount of blocks.
The following bytes encode a block as a single bit.

Change-Id: I3a8ddbe4100f342db2c59ad1fb9aa0014efc62b8

firmware: Drop CEMU_TX_DATA when sim is in-active

When the emulated sim is in reset or without power, drop
CEMU_TX_DATA.

Change-Id: I796e548225a742cddfde12bd6a60e4d2e5c04c8f

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

firmware: card_emu.h: declare usb_buf_upd_len_and_submit()

usb_buf_upd_len_and_submit() already a public function and should be
accessible.

Change-Id: I734d4b2d782223dd2f735f140d8c9bc6fc00a086

README.md: fix typo in firmware

Change-Id: I16721418fce55322c8730920ceaa4e65f91a8a7e

contrib: add usb_vendor_request.py script to collect debug infos

Change-Id: Ie18e171c684ce9d67e711e3d6fda6850d5fc9e7e

firmware: Add talloc_report_buf() encode the allocation by bits

First byte encodes the amount of blocks.
The following bytes encode a block as a single bit.

Change-Id: I3a8ddbe4100f342db2c59ad1fb9aa0014efc62b8

firmare: Drop CEMU_TX_DATA when sim is in-active

When the emulated sim is in reset or without power, drop
CEMU_TX_DATA.

Change-Id: I796e548225a742cddfde12bd6a60e4d2e5c04c8f

firmware: card_emu.h: declare usb_buf_upd_len_and_submit()

usb_buf_upd_len_and_submit() already a public function and should be
accessible.

Change-Id: I734d4b2d782223dd2f735f140d8c9bc6fc00a086

firmware: card_emu.h: add missing header stdbool.h.

Change-Id: I4ad6d5cf0b4477cbd5f761d70c4cd92fb3ca1fcd

README.md: describe the debug uart

Change-Id: I4cf929fded962e7ffb4c01628279385b2af04157

firmware: Implement debug command via USB control vendor class

Allows to collect talloc reports and other debug information
from a script while the remsim-client is still running.

Change-Id: I1f4d29335eb0d2feef376b8ecdfe57a0162914d6

eIM: use eimTransactionId during profile download

When the eIM initiates a profile download via the
profileDownloadTriggerRequest, it includes an eimTransactionId to identify
sent by the IPAd (testsuite) in the initiateAuthenticationRequestEsipa
response. The eimTransactionId (even though it is optional) is essential
for the eIM to recognize the response from the eIM correctly.

(SGP.32 V.1.0.1 lacked the eimTransactionId, which meant that the eIM had
to rely on other identifiers such as the TCP connection itself. The problem
is now fixed with SGP.32 V.1.2)

Related: SYS#8100
Change-Id: I045d93b9f40ddfb3dc6dfbd9602e736bbc6b4abc

eIM, REST: use template to encode eimConfigurationData

We currently use a hardcoded binary blob for the testcases that test the
addEim and updateEim eCOs. Let's use the enc_EimConfigurationData encoder
function, which we already have, to encode the eimConfigurationData
instead.

Related: SYS#8100
Change-Id: Ic51731da355cd9a209837d4015c02943367ed90b

eIM: add testcase to test an unsuccessful eUICC data request

When we test the ipaEuiccDataRequest/IpaEuiccDataResponse, we currently
only test the success case. However, we should also test the failure
case, bceause an IpaEuiccDataResponseError can also contain an
eimTransactionId, which has to be equal to the eimTransactionId we have
received with the ipaEuiccDataRequest

Related: SYS#8100
Change-Id: Ied212eb636cf46df5fc9f86ddee15c242c50d45a

eIM: echo eimTransactionId from euiccDataReq in provideEimPackageResult

The udted eIM now includes an eimTransactionId in its ipaEuiccDataRequest
message, which means that the IPAd (testsuite) has to echo that exact
same eimTransactionId in the IpaEuiccData of the IpaEuiccDataResponse

Related: SYS#8100
Change-Id: I286362e6499eb9440e006f08b7c142c6dfd98843

eIM, add new PSMOs introduced with SGP.32 V.1.2

SGP.32 V.1.2 adds new PSMOs, which are setFallbackAttribute,
unsetFallbackAttribute and setDefaultDpAddress. Let's add testcases
for those.

Related: SYS#8100
Change-Id: Ic2416dc06d917228b71c61da9acebed26d68b2d9

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

doc/build.md: fix typo

Related: SYS#8100
Change-Id: Ie6a066f3289fbdde40f55bd9f38a3dd90102e7e6

esipa_asn1_handler_utils: use maps:find

We can replace maps:is_key and maps:get with a single maps:find call.

Change-Id: I6cc151deef161f3ca4726e6b81ae1f5cc80ad184
Related: SYS#8100

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

mnesia_db_euicc: renovate handling of euicc table (mnesia, REST)

The REST API that allows users to set certain eUICC parameters
(we call them "states" from now on) only allows to set eUICC
states, but doesn't allow to read them back.

With this patch, we renovate the handling of the mnesia euicc
table from the ground up so that REST API users have read and
write access to the states stored in the mnesia euicc table.

Change-Id: I74c602555b194a28d6eb9dd67ec4c6a8865fcb77
Related: SYS#8100

esipa_rest_utils: add support for PSMOs added in SGP.32 V.1.2

SGP.32 adds 3 additional PSMOs:
- setFallbackAttribute
- unsetFallbackAttribute
- setDefaultDpAddress

Change-Id: I03cdd70065a83dfc611d614cf32d817c13fad347
Related: SYS#8100

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

mnesia_db_rest: add comment on why we create an euicc entry early

Even though it is technically not necessary, we ensure that an
entry is present in the euicc table on each REST API call. Let's
add a comment to explain why we do it anyway.

Change-Id: Ifb9340655c5f36e074a1a92c0e234ef62c79b9d8

contrib/tryme_euiccDataRequest: fixup example tag string

The eUICC data request takes a string with TLV tags as input. The
example in this example still uses tags from SGP.32 V.1.0.1, let's
update the string so that it is compliant with SGP.32 V.1.2.

(see also SGP.32, section 2.11.1.2)

Related: SYS:8100
Change-Id: I5be04c954330638d3e7d78e8f5f280bebb707efa

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

esipa_rest_utils: align IpaEuiccDataResponse to SGP.32 V.1.2

The ASN.1 struct IpaEuiccDataResponse has renamed the error code
member from ipaEuiccDataError to ipaEuiccDataErrorCode. The new
ipaEuiccDataErrorCode is a sequence that has an ipaEuiccDataErrorCode
member, which is the equivalent of the previously existing
ipaEuiccDataError member.

See also: SGP.32, section 2.11.2.2

Change-Id: Ie734a09ed4b0d57de30dc6fb377dfada79ea2ae4
Related: SYS#8100

rest_api_response_schema: add missing error codes

In SGP.32 V.1.2, new error codes were added to EnableProfileResult,
DisableProfileResult, DeleteProfileResult and AddEimResult

See also: SGP.32, section 2.11.2

Change-Id: I525ca9d3b7fb870405d374160272d8ec26c85880
Related: SYS#8100

mnesia_db_euicc: rename timer_setparam to timer_rest

The function timer_setparam is processing REST API orders
in regular intervals. Naming the timer "timer_rest" makes
more sense.

Change-Id: Icfa203477e044ce2cc312d4b6e2693a97191c61d

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

CCID: Check if reader times out while expecting procedure byte

A case 2 APDU (according to ISO 7816) is sent toward the reader. The
reader expects a procedure byte or a status word. If none of these are
sent by the SIM the reader must timeout and send an error message back
to the host.

Change-Id: Iacd6aacaf8220e69b9b7038e354d54c788d1eb05

CCID: Check if reader handles Abort correctly

The tests aborts an ongoing case 2 APDU (according to ISO 7816). The
SIM responds with a NULL procedure byte so that the reader does not
time out.

The abort messages are sent on both, the control pipe and the bulk
pipe with the same sequence number.

This test fails with osmo-ccid-firmware, because the abort
message/handling is not yet implemented.

Change-Id: Iebe97e73497b8468ebf08faf2c4db700fc76997f

contrib/onomondo-eim.sh: add option to set a mnesia dir

The onomondo-eim.sh startscript we provide in the contrib directory
does not set the "mnesia dir" parameter when starting the erlang VM.
Let's add a commandline parameter and a default location to the
script.

Related: SYS#8100
Change-Id: I6a13a631da7903db4766168380ce727127a4d47b

Add old eUICC library to run IPA with SGP.32 V1.0.1

The current eUICC library was updated, to new ASN.1 defintions of
SGP.32 V1.2. This was required to run IPA and eIM based on SGP.32 V1.2.
Since the patches for IPA based on SGP.32 V1.2 are not merged yet, add
the old eUICC library and use it for testing currrent IPA based on
SGP.32 V1.0.1.

Change-Id: I6d4a2bef08847cd58e75f88a02d0299ce694516e

pySim/global_platform: make functionality available outside of cmd2

The nested class AddlShellCommands holds methods that encapsulate
the actual functionality from the related do_ method (e.g.
do_store_data calls self.store_data). This is already a good level
of separation but it does not allow us to call those methods from
programs that are not based on cmd2. Let's turn those methods into
functions so that non cmd2 applications have easy access to the
functionality of pySim.global_platform.

Let's also add a pySimLogger, so that we do not have to call
self._cmd.poutput

Related: SYS#6959
Change-Id: Idf4e4b58bf49ba62b2c22de4c49a2dcacfa872cb

Remote Card Procedure Framework

Problem: When UICC/eUICC cards are deployed into the field it is often
difficult to perform modifications to those cards. One important factor
that makes after-deployment modifications often difficult is that the
key material needed to perform the task must not be handed to the card
holder due to security requirements.

The presented Remote Card Procedure Framework solves this problem. It
provides a so called Remote Card Procedure Client (RCPC), which is a
lightwight software client which can be run by the card holder on the
remote machine.

With the RCPC, the card holder can access a so called Remote Card
Procedure Server (RCPC), to which so called Remote Card Procedure
Modules (RCPM) can subscribe and publish their functionality. With
the RCPC, the card holder can browse the functionality offered by
those connected modules and eventually the card holder may execute
a certain procedure by passing a command to the RCPS.

When a procedure is carried out, the RCPS automatically retrieves the
required key material from a database or CSV file and passes those
keys on to the selected RCPM. The RCPM can then use the key material
to establish a secure channel to carry out the procedure. The procedure
is then protected by a secure channel and the key material is never
disclosed towards the card holder on the remote end.

The framework is desinged in such a way that existing pySim APIs and
functions can be used from the RCPM API user code. Also only minimal
boilerplate code is required. The implementation also ships with a
comprehensive example.

Change-Id: I8500a98492328ed5b3eb4bb177af2a4a8e481f80
Related: SYS#6959

Add install target to CMakeLists.txt

The file allows to compile and install onomondo-eim. This allows to
build it with osmo-dev and therefore build and run it with testenv of
osmo-ttcn3-hacks.

The program name changed from 'ipa' to 'onomodo-ipa'.

Related: SYS#8101
Change-Id: Id2c61e754c59fe1d4d59f61de2745bab6543fba2

CCID: Check if reader handles Abort correctly

The tests aborts an ongoing case 2 APDU (according to ISO 7816). The
SIM responds with a NULL procedure byte so that the reader does not
time out.

The abort messages are sent on both, the control pipe and the bulk
pipe with the same sequence number.

This test fails with osmo-ccid-firmware, because the abort
message/handling is not yet implemented.

Change-Id: Iebe97e73497b8468ebf08faf2c4db700fc76997f

CCID: Send procedure byte, when not expected

A case 1 APDU does not request any data from SIM to return. The SIM will
only return a status byte with no procedure byte in advance.

The test sends a the INS byte + some other byte (0x42) instead of the
two status bytes as a response to the reader. The reader waits for
payload to be received from the SIM and times out.

This means that the reader uses the SIM response to determine if it is
a case 1 or case 2 APDU and not the instruction GET_RESPONSE or any
other instruction code.

Change-Id: Icffd48d99f0eb48e0898efb027854eba8c22f4a4

CCID: Check if reader times out while expecting procedure byte

A case 2 APDU (according to ISO 7816) is sent toward the reader. The
reader expects a procedure byte or a status word. If none of these are
sent by the SIM the reader must timeout and send an error message back
to the host.

Change-Id: Iacd6aacaf8220e69b9b7038e354d54c788d1eb05

IPAd: Make tests work with testenv and current master of IPAd

The IPAd can now be tested using testenv.

Several minor changes are required to run them successfully. All tests
pass now.

Related: SYS#8101
Change-Id: Id4abf15feb179b17594bd11c6e7089469684900c

eIM: Make tests work with testenv

The eIM can now be tested using testenv.py.

Related: SYS#8100
Change-Id: I38364e4bd5625b301c32fd58b50e35667c64b1be

Add empty getEimPackageResponse send template

This template can be sent, if no eIM package is available for the IPAd.
The IPAd will then stop polling for new eIM packages terminate (or
delay).

Related: SYS#8101
Change-Id: Idf777e168c2f86ed80ce184cbb65fe86cdabe56a

IPAd: Add TERMINAL CAPABILITIES request (IoT Device Capabilites)

In order to activate IoT functions on eUICC, IPAd will send a TERMINAL
CAPABILITIES request. This has to be answered by the test-suite.

Related: SYS#8101
Change-Id: I0a6d8d6bb6eb0ee30e14afdb5e4ce37af0ae711e

Add close function to HTTP_Server_Emulation

If we want to simulate a broken HTTP request towards the client, we may
wait until the client times out. This results in closing the TCP
connection by the client. It then results in failure of the SSL
connection at Titan's Abstract_Socket component. The TTCN3-tests fails.

One solution is to actively close the connection via a close function.
The client will not wait for the timeout. The Abstact_Socket will then
not receive any failure. The test runs faster.

Related: SYS#8101
Change-Id: Id09976800c7498a7173b5d8911fe545504cfa266

IPAd: Update nvstate.bin to SGP.32 Version 1.2

Related: SYS#8101
Change-Id: I3d22980f5f8be546f0d80423b3bd80d197aa8872

pySim/ara_m: move code from do_aram_ to static methods

The method do_aram_store_ref_ar_do and do_aram_delete_all, which
are part of the nested AddlShellCommands class, may be moved into
the parent class as a static method, just like the already existing
get_config method.

This makes the functionality re-usable to callers that do not use
the CMD2 API.

Change-Id: Icd1b08ec707dd939bc9e8524d7f9431aa4daae7c
Related: SYS#6959

CCID: Send a wrong procedure byte towards the reader

A case 2 request (according to ISO 7816) is sent and a response with
data is expected, but the first byte replied by the SIM is not a
procedure byte, nor a valid status byte.

This text expects the reader to return an error that states an incorrect
received procedure byte.

Change-Id: Iaa0bd8845b3408fba309874fe41c855d8e7efccc

CCID: Send procedure byte, when not expected

A case 1 APDU does not request any data from SIM to return. The SIM will
only return a status byte with no procedure byte in advance.

The test sends a the INS byte + procedure byte (0x62) instead of the
two status bytes as a response to the reader. The reader waits for
payload to be received from the SIM and times out.

This means that the reader uses the SIM response to determine if it is
a case 1 or case 2 APDU and not the instruction GET_RESPONSE.

Change-Id: Icffd48d99f0eb48e0898efb027854eba8c22f4a4

CCID: Check if reader handles Abort correctly

The tests aborts an ongoing case 2 APDU (according to ISO 7816). The
SIM responds with a NULL procedure byte so that the reader does not
time out.

The abort messages are sent on both, the control pipe and the bulk
pipe with the same sequence number.

This test fails with osmo-ccid-firmware, because the abort
message/handling is not yet implemented.

Change-Id: Iebe97e73497b8468ebf08faf2c4db700fc76997f

CCID: Check if reader times out after first status word

A case 1 APDU is sent towards the reader. The reader expects two status
words. If only the first word is sent by the SIM, the reader must
timeout and send an error message back to the host.

Change-Id: Ic5b892e356c13808555d75746c48c6d8c96ec462

CCID: Check if reader times out while expecting procedure byte

A case 2 APDU (according to ISO 7816) is sent toward the reader. The
reader expects a procedure byte or a status word. If none of these are
sent by the SIM the reader must timeout and send an error message back
to the host.

Change-Id: Iacd6aacaf8220e69b9b7038e354d54c788d1eb05

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

mnesia_db_rest: add comment on why we create an euicc entry early

Even though it is technically not necessary, we ensure that an
entry is present in the euicc table on each REST API call. Let's
add a comment to explain why we do it anyway.

Change-Id: Ifb9340655c5f36e074a1a92c0e234ef62c79b9d8

mnesia_db_euicc: renovate handling of euicc table (mnesia, REST)

The REST API that allows users to set certain eUICC parameters
(we call them "states" from now on) only allows to set eUICC
states, but doesn't allow to read them back.

With this patch, we renovate the handling of the mnesia euicc
table from the ground up so that REST API users have read and
write access to the states stored in the mnesia euicc table.

Related: SYS#8100

The original purpose of the euicc table was to hold static params
for an eUICC (e.g. the public key or the flag that tells if it is
a consumer eUICC or not). Now that we plan to extend the scope
of the euicc table, it makes more sense to talk about states rather
than parameters.

Change-Id: I74c602555b194a28d6eb9dd67ec4c6a8865fcb77

doc/build.md: fix typo

Related: SYS#8100
Change-Id: Ie6a066f3289fbdde40f55bd9f38a3dd90102e7e6

contrib/tryme_euiccDataRequest: fixup example tag string

The eUICC data request takes a string with TLV tags as input. The
example in this example still uses tags from SGP.32 V.1.0.1, let's
update the string so that it is compliant with SGP.32 V.1.2.

(see also SGP.32, section 2.11.1.2)

Related: SYS:8100
Change-Id: I5be04c954330638d3e7d78e8f5f280bebb707efa

mnesia_db_euicc: rename timer_setparam to timer_rest

The function timer_setparam is processing REST API orders
in regular intervals. Naming the timer "timer_rest" makes
more sense.

Change-Id: Icfa203477e044ce2cc312d4b6e2693a97191c61d

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

esipa_asn1_handler_utils: use maps:find

We can replace maps:is_key and maps:get with a single maps:find call.

Change-Id: I6cc151deef161f3ca4726e6b81ae1f5cc80ad184
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

IPAd: Make tests work with testenv and current master of IPAd

The IPAd can now be tested using testenv.

Several minor changes are required to run them successfully. All tests
pass now.

Related: SYS#8101
Change-Id: Id4abf15feb179b17594bd11c6e7089469684900c

Add empty getEimPackageResponse send template

This template can be sent, if no eIM package is available for the IPAd.
The IPAd will then stop polling for new eIM packages terminate (or
delay).

Related: SYS#8101
Change-Id: Idf777e168c2f86ed80ce184cbb65fe86cdabe56a

IPAd: Add TERMINAL CAPABILITIES request (IoT Device Capabilites)

In order to activate IoT functions on eUICC, IPAd will send a TERMINAL
CAPABILITIES request. This has to be answered by the test-suite.

Related: SYS#8101
Change-Id: I0a6d8d6bb6eb0ee30e14afdb5e4ce37af0ae711e

eIM: Make tests work with testenv

The eIM can now be tested using testenv.py.

Related: SYS#8100
Change-Id: I38364e4bd5625b301c32fd58b50e35667c64b1be

IPAd: Update nvstate.bin to SGP.32 Version 1.2

Related: SYS#8101
Change-Id: I3d22980f5f8be546f0d80423b3bd80d197aa8872

Add close function to HTTP_Server_Emulation

If we want to simulate a broken HTTP request towards the client, we may
wait until the client times out. This results in closing the TCP
connection by the client. It then results in failure of the SSL
connection at Titan's Abstract_Socket component. The TTCN3-tests fails.

One solution is to actively close the connection via a close function.
The client will not wait for the timeout. The Abstact_Socket will then
not receive any failure. The test runs faster.

Related: SYS#8101
Change-Id: Id09976800c7498a7173b5d8911fe545504cfa266

CMakeLists: add install target for ipa

Change-Id: I1b3d248ca2df14835c65139df90ccd2e2f1b80aa

Add 'onomondo-ipa' project

Related: SYS#8100
Change-Id: I732e63625943b20989001102c7447d0e0a62af5a

Add 'onomono-eim' project

Related: SYS#8100
Change-Id: I47bfc02397b6f97ad891fe4816763ba634df7934

Add Makefile and start script for installation

The Makefile allows to compile and install onomondo-eim. This allows to
build it with osmo-dev and therefore build and run it with testenv of
osmo-ttcn3-hacks.

The start script allows to run onomondo-eim without starting erlang by
hand. It was taken from osmo-s1gw repository and log-level option was
added.

The program name changed from 'onomondo_eim_release' to 'onomodo-eim'.

Related: SYS#8100
Change-Id: I4f038c0901c23cbe18ef62eb546e264d0b924cc7

Support building onomondo-eim

The onomondo-eim project is an erlang project, but it does not have a
Makefile like the others. Run rebar3 directly in that case.

I've also considered always doing this instead of running the Makefile,
but that would break osmo-s1gw, which needs to run "rebar3 asn compile"
before "rebar3 compile" as its Makefile does it.

Change-Id: I551e0b88110ed20fdbc301035fc3dac6e0d83635

manuals: ignore osmo-s1gw 0.4.1

Change-Id: Id5bddb61c7ae711242060d31a806bc44fee46e5d

rebar.config: use a fork of rebar3_diameter_compiler

This fixes building on Erlang/OTP 29.  A pull request [1] has been
submitted upstream.  Once merged, we get switch back to upstream.

[1] https://github.com/carlosedp/rebar3_diameter_compiler/pull/28

Change-Id: I548a3fef6f8a23a548fb6376076b9d4a9345d692

IPAd: Update nvstate.bin to SGP.32 Version 1.2

Related: SYS#8101
Change-Id: I3d22980f5f8be546f0d80423b3bd80d197aa8872

IPAd: Add TERMINAL CAPABILITIES request (IoT Device Capabilites)

In order to activate IoT functions on eUICC, IPAd will send a TERMINAL
CAPABILITIES request. This has to be answered by the test-suite.

Related: SYS#8101
Change-Id: I0a6d8d6bb6eb0ee30e14afdb5e4ce37af0ae711e

IPAd: Update nvstate.bin to SGP.32 Version 1.2

Related: SYS#8101
Change-Id: I3d22980f5f8be546f0d80423b3bd80d197aa8872

IPAd: Add TERMINAL CAPABILITIES request (IoT Device Capabilites)

In order to activate IoT functions on eUICC, IPAd will send a TERMINAL
CAPABILITIES request. This has to be answered by the testsuite.

Related: SYS#8101
Change-Id: I0a6d8d6bb6eb0ee30e14afdb5e4ce37af0ae711e

eIM: Make tests work with testenv

The eIM can now be tested using testenv.py.

Related: SYS#8100
Change-Id: I38364e4bd5625b301c32fd58b50e35667c64b1be

IPAd: Make tests work with testenv and current master of IPAd

The IPAd can now be tested using testenv.

Several minor changes are required to run them successfully. All tests
pass now.

Related: SYS#8101
Change-Id: Id4abf15feb179b17594bd11c6e7089469684900c

Add close function to HTTP_Server_Emulation

If we want to simulate a broken HTTP request towards the client, we may
wait until the client times out. This results in closing the TCP
connection by the client. It then results in failure of the SSL
connection at Titan's Abstract_Socket component. The TTCN3-tests fails.

One solution is to actively close the connection via a close function.
The client will not wait for the timout. The Abstact_Socket will then
not receive any failure. The test runs faster.

Related: SYS#8101
Change-Id: Id09976800c7498a7173b5d8911fe545504cfa266

Add empty getEimPackageResponse send template

This template can be sent, if no eIM package is available for the IPAd.
The IPAd will then stop polling for new eIM packages terminate (or
delay).

Related: SYS#8101
Change-Id: Idf777e168c2f86ed80ce184cbb65fe86cdabe56a

redmine: hide avatars

We aren't using gravatar or other 3rd party avatar services, and we
don't want the default avatars either as they can give the same color to
different users, making them look like the same user on first glance.

Related: SYS#8097#note-15
Change-Id: I136549e00f806a76704b354498083002fddb5b67

rebar.config: use a fork of rebar3_diameter_compiler

This fixes building on Erlang/OTP 29.  A pull request [1] has been
submitted upstream.  Once merged, we get switch back to upstream.

[1] https://github.com/carlosedp/rebar3_diameter_compiler/pull/28

Change-Id: I548a3fef6f8a23a548fb6376076b9d4a9345d692

contrib/obs-mirror: log to systemd journal

Instead of having a lot of logfiles in /home/pkgmirror and starting the
obs-mirror scripts via cronjob, add systemd services and timers and let
them log to the systemd journal.

Change-Id: I3a567770ef6d98bb3fdc2d52214cacbfe59640ad

contrib/obs-mirror: log to systemd journal

Instead of having a lot of logfiles in /home/pkgmirror and starting the
obs-mirror scripts via cronjob, add systemd services and timers and let
them log to the systemd journal.

Change-Id: I3a567770ef6d98bb3fdc2d52214cacbfe59640ad

eIM: echo eimTransactionId from euiccDataReq in provideEimPackageResult

The udted eIM now includes an eimTransactionId in its ipaEuiccDataRequest
message, which means that the IPAd (testsuite) has to echo that exact
same eimTransactionId in the IpaEuiccData of the IpaEuiccDataResponse

Related: SYS#8100
Change-Id: I286362e6499eb9440e006f08b7c142c6dfd98843

eIM, REST: use template to encode eimConfigurationData

We currently use a hardcoded binary blob for the testcases that test the
addEim and updateEim eCOs. Let's use the enc_EimConfigurationData encoder
function, which we already have, to encode the eimConfigurationData
instead.

Related: SYS#8100
Change-Id: Ic51731da355cd9a209837d4015c02943367ed90b

eIM, add new PSMOs introduced with SGP.32 V.1.2

SGP.32 V.1.2 adds new PSMOs, which are setFallbackAttribute,
unsetFallbackAttribute and setDefaultDpAddress. Let's add testcases
for those.

Related: SYS#8100
Change-Id: Ic2416dc06d917228b71c61da9acebed26d68b2d9

eIM: use eimTransactionId during profile download

When the eIM initiates a profile download via the
profileDownloadTriggerRequest, it includes an eimTransactionId to identify
sent by the IPAd (testsuite) in the initiateAuthenticationRequestEsipa
response. The eimTransactionId (even though it is optional) is essential
for the eIM to recognize the response from the eIM correctly.

(SGP.32 V.1.0.1 lacked the eimTransactionId, which meant that the eIM had
to rely on other identifiers such as the TCP connection itself. The problem
is now fixed with SGP.32 V.1.2)

Related: SYS#8100
Change-Id: I045d93b9f40ddfb3dc6dfbd9602e736bbc6b4abc

eIM: add testcase to test an unsuccessful eUICC data request

When we test the ipaEuiccDataRequest/IpaEuiccDataResponse, we currently
only test the success case. However, we should also test the failure
case, bceause an IpaEuiccDataResponseError can also contain an
eimTransactionId, which has to be equal to the eimTransactionId we have
received with the ipaEuiccDataRequest

Related: SYS#8100
Change-Id: Ied212eb636cf46df5fc9f86ddee15c242c50d45a

eIM, IPAd: migrate from SGP.32 V.1.0.1 to SGP.32 V.1.2

SGP.32 V.1.2 is not backward compatible to SGP.32 V.1.0.1. This patch updates
the ASN.1 specification and the TTCN3 templates and types accordingly.

It also applies the bare minimum of changes required to compile the eIM and IPAd
testcases.

Related: SYS#8100
Related: SYS#8101
Change-Id: Id9e112669d9ed8caaec0893c55189eb566fe59be
Co-authored-by: Andreas Eversberg <aeversberg@sysmocom.de>

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

esipa_asn1_handler_utils: use maps:find

We can replace maps:is_key and maps:get with a single maps:find call.

Change-Id: I6cc151deef161f3ca4726e6b81ae1f5cc80ad184
Related: SYS#8100

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

mnesia_db_euicc: rename timer_setparam to timer_rest

The function timer_setparam is processing REAT api orders
in regular intervals. Naming the timer "timer_rest" makes
more sense.

Change-Id: Icfa203477e044ce2cc312d4b6e2693a97191c61d

eIM, IPAd: migrate from SGP.32 V.1.0.1 to SGP.32 V.1.2

SGP.32 V.1.2 is not backward compatible to SGP.32 V.1.0.1. This patch updates
the ASN.1 specification and the TTCN3 templates and types accordingly.

It also applies the bare minimum of changes required to compile the eIM and IPAd
testcases.

Related: SYS#8100
Related: SYS#8101
Change-Id: Id9e112669d9ed8caaec0893c55189eb566fe59be
Co-authored-by: Andreas Eversberg <aeversberg@sysmocom.de>

eIM: use eimTransactionId during profile download

When the eIM initiates a profile download via the
profileDownloadTriggerRequest, it includes an eimTransactionId to identify
sent by the IPAd (testsuite) in the initiateAuthenticationRequestEsipa
response. The eimTransactionId (even though it is optional) is essential
for the eIM to recognize the response from the eIM correctly.

(SGP.32 V.1.0.1 lacked the eimTransactionId, which meant that the eIM had
to rely on other identifiers such as the TCP connection itself. The problem
is now fixed with SGP.32 V.1.2)

Related: SYS#8100
Change-Id: I045d93b9f40ddfb3dc6dfbd9602e736bbc6b4abc

eIM: echo eimTransactionId from euiccDataReq in provideEimPackageResult

The udted eIM now includes an eimTransactionId in its ipaEuiccDataRequest
message, which means that the IPAd (testsuite) has to echo that exact
same eimTransactionId in the IpaEuiccData of the IpaEuiccDataResponse

Related: SYS#8100
Change-Id: I286362e6499eb9440e006f08b7c142c6dfd98843

eIM, add new PSMOs introduced with SGP.32 V.1.2

SGP.32 V.1.2 adds new PSMOs, which are setFallbackAttribute,
unsetFallbackAttribute and setDefaultDpAddress. Let's add testcases
for those.

Related: SYS#8100
Change-Id: Ic2416dc06d917228b71c61da9acebed26d68b2d9

eIM: add testcase to test an unsuccessful eUICC data request

When we test the ipaEuiccDataRequest/IpaEuiccDataResponse, we currently
only test the success case. However, we should also test the failure
case, bceause an IpaEuiccDataResponseError can also contain an
eimTransactionId, which has to be equal to the eimTransactionId we have
received with the ipaEuiccDataRequest

Related: SYS#8100
Change-Id: Ied212eb636cf46df5fc9f86ddee15c242c50d45a

eIM, REST: use template to encode eimConfigurationData

We currently use a hardcoded binary blob for the testcases that test the
addEim and updateEim eCOs. Let's use the enc_EimConfigurationData encoder
function, which we already have, to encode the eimConfigurationData
instead.

Related: SYS#8100
Change-Id: Ic51731da355cd9a209837d4015c02943367ed90b

eIM: add testcase to test an unsuccessful eUICC data request

When we test the ipaEuiccDataRequest/IpaEuiccDataResponse, we currently
only test the success case. However, we should also test the failure
case, bceause an IpaEuiccDataResponseError can also contain an
eimTransactionId, which has to be equal to the eimTransactionId we have
received with the ipaEuiccDataRequest

Related: SYS#8100
Change-Id: Ied212eb636cf46df5fc9f86ddee15c242c50d45a

eIM: use eimTransactionId during profile download

When the eIM initiates a profile download via the
profileDownloadTriggerRequest, it includes an eimTransactionId to identify
sent by the IPAd (testsuite) in the initiateAuthenticationRequestEsipa
response. The eimTransactionId (even though it is optional) is essential
for the eIM to recognize the response from the eIM correctly.

(SGP.32 V.1.0.1 lacked the eimTransactionId, which meant that the eIM had
to rely on other identifiers such as the TCP connection itself. The problem
is now fixed with SGP.32 V.1.2)

Related: SYS#8100
Change-Id: I045d93b9f40ddfb3dc6dfbd9602e736bbc6b4abc

eIM: echo eimTransactionId from euiccDataReq in provideEimPackageResult

The udted eIM now includes an eimTransactionId in its ipaEuiccDataRequest
message, which means that the IPAd (testsuite) has to echo that exact
same eimTransactionId in the IpaEuiccData of the IpaEuiccDataResponse

Related: SYS#8100
Change-Id: I286362e6499eb9440e006f08b7c142c6dfd98843

eIM, IPAd: migrate from SGP.32 V.1.0.1 to SGP.32 V.1.2

SGP.32 V.1.2 is not backward compatible to SGP.32 V.1.0.1. This patch updates
the ASN.1 specification and the TTCN3 templates and types accordingly.

It also applies the bare minimum of changes required to compile the eIM and IPAd
testcases.

Related: SYS#8100
Related: SYS#8101
Change-Id: Id9e112669d9ed8caaec0893c55189eb566fe59be
Co-authored-by: Andreas Eversberg <aeversberg@sysmocom.de>

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId for ipaEuiccDataResponse

The ipaEuiccDataResponse does currently not use the eimTransactionId,
which was added with SGP.32 V.1.2, let's make use of the eimTransactionId
and move the handler functionality to a dedicated helper function in
esipa_asn_handler_utils.

Change-Id: Ie414eef7fd5c8928dd611503f4dd8d67322c0e80
Related: SYS#8100

esipa: rename TransactionId to EimTransactionId where applicable

In SGP.32 V.1.2 all TransactionIds which are generated by the eIM are
called now called "eimTransactionId". Let's make sure that we name
the EimTransactionId variables and atoms (eimTransactionId) accordingly.

Change-Id: Ia97f96c27d5dc4405effd5266de4cdb797849699
Related: SYS#8100

esipa_asn1_handler_utils: rename EsipaReq to Debuginfo

The parameter EsipaReq only exists because we pass it as
Debuginfo to mnesia_db_work:finish. Let's rename it to
"Debuginfo" in esipa_asn1_handler_utils as well to make
clear what the purpose of this parameter is.

Change-Id: I8115d382172989b9ef7ae7f97ce39520e3e2dd16
Related: SYS#8100

esipa_asn1_handler: use eimTransactionId in EimPackageResultResponseError

EimPackageResultResponseError contains an eimTransactionId, let's use this
eimTransactionId and add a dedicated handler function for the
EimPackageResultResponseError to esipa_asn1_handler_utils

Change-Id: Iadd852a7531f180618cf12b314170ceea3f97615
Related: SYS#8100

esipa_asn1_handler: replace handle_asn1_notificationList

The helper function handle_asn1_notificationList can also be
described using the comprehension syntax.

Change-Id: Ia95f56998b4f7a8b0f9fce727d82dedc942e5aeb
Related: SYS#8100

esipa: supply eimTransactionId in profileDownloadTriggerRequest

When we supply an eimTransactionId in profileDownloadTriggerRequest,
the IPAd will echo the same eimTransactionId in the
initiateAuthenticationRequestEsipa message. This allows the eIM
to distinguish to which transaction (work) the received
initiateAuthenticationRequestEsipa belongs. This was not possible
before. The eIM had to rely soly on the PID of the sub process
which is handling the HTTP connection.

Change-Id: I822d6b2bb51498713739671804b173260e9a28a3
Related: SYS#8100

esipa_rest_utils: re-align to SGP.32 Section 2.11.2

Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult

Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308
Related: SYS#8100

mnesia_db: split functionality into dedicated modules

The mnesia_db module is responsible to handle three different tables
with different scope. Let's split the functionality into separate
modules to make the code easier to maintain.

Change-Id: Ifc649337ab7ce7eb9dc602a1439293130f002f41
Related: SYS#8100

esipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6

Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse
Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters

Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce
Related: SYS#8100

es9p_client: convert InitiateAuthenticationOkEsipa to match SGP.32 V.1.2

In SGP.32 V.1.0.1, InitiateAuthenticationOkEsipa is almost identical to
SGP.22 InitiateAuthenticationOkEs9. However, in SGP.32 V.1.2, the member
euiccCiPKIdToBeUsed is renamed to euiccCiPKIdentifierToBeUsed. This means
it is no longer possible to pass InitiateAuthenticationOkEsipa as
InitiateAuthenticationOkEs9 to ES9+ directly. Instead we have to re-build
the the InitiateAuthenticationOkEs9 from the contents of
InitiateAuthenticationOkEsipa.

Change-Id: I44c60a2f0d1129093ea67908d2eed167643a4a87
Related: SYS#8100

eim_cfg: set eimSupportedProtocol and indirectProfileDownload flags

The members eimSupportedProtocol and indirectProfileDownload were
added as optional members to EimConfigurationData with SGP.32 V.1.2.

Since our eIM implementation only supports eIM Package Retrieval via
HTTPs and the Indirect Profile Download procedure is the only Profile
Download procedure we currently support, the EimConfigurationData
should reflect those properties correctly.

(The EimConfigurationData is not announced actively by the eIM, but
this eIM implementation contains a generator to help with the encoding
of the EimConfigurationData that is programmed into the eUICC)

Change-Id: I4ce236fb1bfb8a3790191be95ab0958dce13a9d8
Related: SYS#8100

esipa_asn1_handler: fix transactionId handling

The transactionId member is now called eimTransactionId. It is also
an optional member.

Change-Id: I1340e0c7aed091e8e5a5089ebd6e524512408cf7
Related: SYS#8100

esipa_asn1_codec: add special handling for ProvideEimPackageResultResponse

In SGP.32 V.1.2 ProvideEimPackageResultResponse is defined as a CHOICE.
This means that this struct now also requires special handling.

Change-Id: I859a175cc28a18ea9334d9b2cf233294fdc95b76
Related: SYS#8100

rebar.config: bump meck version: 0.9.2 -> v1.2.0

This fixes a compilation error with recent Erlang/OTP 29:

[  335s] ===> Compiling meck
[  335s] ===> Compiling _checkouts/meck/src/meck_matcher.erl failed
[  335s] meck_matcher.erl:76:6: 'catch ...' is deprecated; please use 'try ... catch ... end' instead.
[  335s] Compile directive 'nowarn_deprecated_catch' can be used to suppress
[  335s] warnings in selected modules.

Change-Id: If3409de1e09ac1b6ce3355d19e47ef0e160a2d3b
(cherry picked from commit a013155e8af1b4cca604e10f81dcb683a5e7812c)

Bump version: 0.4.1

Change-Id: I17c9806400a48b4cdf7be19a824e10c56620d655

Bump version: 0.9.0.4-3248-dirty → 0.9.1

Change-Id: I0d06c6f15aa99be7609eac9afb6b9df8e6cf3dc5

Add missing const for struct hostent *hostent

The hostent parameter is supposed to be const. This is being enforced in
c-ares 1.34.7, which is why osmo-sgsn currently fails to build in debian
unstable. The c-ares developers are preparing a new release that reverts
this change to avoid breakage with other users of libc-ares, and only
document that this should basically be const. But let's use the API as
intended so the compiler knows that osmo-sgsn is not supposed to modify
the hostent parameter.

Fix for:

  sgsn_ares.c:141:63: error: passing argument 4 of 'ares_gethostbyname' from incompatible pointer type [-Wincompatible-pointer-types]
    141 |         ares_gethostbyname(sgsn->ares_channel, name, AF_INET, ares_cb, cb_data);
        |                                                               ^~~~~~~
        |                                                               |
        |                                                               void (*)(void *, int,  int,  struct hostent *)
  /usr/include/ares.h:881:22: note: expected 'ares_host_callback' {aka 'void (*)(void *, int,  int,  const struct hostent *)'} but argument is of type 'void (*)(void *, int,  int,  struct hostent *)'

Related: https://github.com/c-ares/c-ares/pull/1060
Related: https://github.com/c-ares/c-ares/pull/1244
Change-Id: Ibe3debc5d3b7af5883001960c40efb296692f93d

Revert "OBS: sync_obs_projects: remove AlmaLinux:8"

This reverts commit 618140a22e41cba21ac2cfac51a84c7514041657.

Related: SYS#8110
Change-Id: Idbaeed2af6441b15f11ca7cf1b7563a99586ed85

OBS: build_binpkg: adjust for new almalinux repo

We are enabling CentOS 8 compatible repositories again for very few
packages. The URL for the package feed is now AlmaLinux_8 instead of
CentOS_8, because AlmaLinux 8 is not EOL yet and seems to work best with
OBS of the CentOS 8 compatible distros.

Related: SYS#8110
Change-Id: I3e9f44f200cdbe28fa4cd21f54b81d73fa543075

contrib/obs-mirror: add AlmaLinux_8

Related: SYS#8110
Change-Id: I8ebf9d613e9ce8ee0982dd68646f248148ac6226

jobs/gerrit: build osmo-pcap + deps for almalinux8

Related: SYS#8110
Change-Id: I8ba119b77f7bb04b0899af8c09ac35782625425a

deps: use a fork of titan.ProtocolEmulations.SCCP

Change-Id: I8c0de4dab088930d5d7a9febcbebcb5e1f9411e8

stp: add ASP_SCCP_N_NOTICE_req support and f_asp_tx_notice()

Wire ASP_SCCP_N_NOTICE_req as a simple passthrough in TCAP_CODEC_PT,
so test components can send UDTS via the existing SCCP_TCAP port.
Add f_asp_tx_notice() to STP_Tests_TCAP as a convenience wrapper.

Change-Id: I74c05405f1c99d43b4bf863f959275ee51301f2e

stp: Add TCAP_N_NOTICE_req to send a UDTS with TCAP payload

Change-Id: Ie13cecc2f2fc8a20d9646f0fb010b91c2ecf7766

stp: Test that UDTS containing tcap is routed correctly

Related: SYS#8090
Depends: libosmo-sigtran.git I2051aa9e84e553feb17daabb93ba3ce82358e0e4
Change-Id: I264ab424fbc3652249535bbe4f30029defa64c09

tcap_as_loadshare: Forward UDTS to the correct tcap-loadshare ASP

Related: SYS#8090
Change-Id: I2051aa9e84e553feb17daabb93ba3ce82358e0e4

STP_Tests_TCAP: Test routing of fragments in TC_tcap_loadshare_ipa_tcap_range_success_pc

A TCAP Begin will cause the stp to create a cache entry and route
according to that. Send only a TCAP Continue so we check the tcap range
routing logic.

Change-Id: I1cb47174b8f0e69970e75109b9d15b2012e150c3

STP_Tests_TCAP: Fix ipa_to_ipa testcase

tcap routing doesn't work the way the test thinks. E.g. a Begin can't be
routed to a special destination because it does't contain a dtid which
is needed to route to the correct ASP.

Change-Id: Ie274232b706348b5ab6d0ac248883d86c53ebb4e

redmine: upgrade to 6.1.3

* Use the redmine:6.1.3 image from upstream (the sysmocom registry image
  was a workaround for 5.1.11).

* Install nkf with native extensions (needs gcc, libc6-dev, make) for
  the redmine_openid_provider plugin. This was not needed for the
  redmine 5 container, it was probably bundled there already.

* Upgrade "activerecord-session_store" to version 2.2.0, which is
  compatible with redmine 6.

Related: SYS#8097
Change-Id: I3e7f746b1a96ff98bbdea2e043a88b9a492672d2

5gc: disable TC_handover_inter_ngran_xn for latest

Temporarily disable the test for latest as it is known to result in a
crash with open5gs v2.8.0.

Related: OS#7023
Change-Id: Ibf3683683093c41a85bb443e14eab23d23fefa24

redmine: upgrade to 6.1.3

Related: SYS#8097
Change-Id: I3e7f746b1a96ff98bbdea2e043a88b9a492672d2

library: add f_gsm_fn_{sum,sub,diff}()

Change-Id: Ie91ccef5d3f170f4a341a6cf9d3323a896b299e6

bts: TC_pcu_interf_ind: check reporting interval instead of absolute FN

Recent osmo-bts commit 53f0ec29 broke TC_pcu_interf_ind:

  Verdict: fail reason: Odd TDMA frame number := 935

There's no requirement that periodic interference reports must land
on a TDMA frame number satisfying 'fn mod 104 == 0' - only that they
keep arriving every configured averaging period.  Instead, verify
that the interval between consecutive reports equals 104 TDMA frames
(1 SACCH period), using the new f_gsm_fn_sub() helper.

Change-Id: Ia96f2926400bae8c0a6fb8f81eb56b48ca5f2de9
Related: 53f0ec29 ("l1sap: fix duplicate RF RESOURCE INDICATION on clock bootstrap")

library: add f_gsm_fn_{sum,sub,diff}()

Change-Id: Ie91ccef5d3f170f4a341a6cf9d3323a896b299e6

bts: TC_pcu_interf_ind: check reporting interval instead of absolute FN

Recent osmo-bts commit 53f0ec29 broke TC_pcu_interf_ind:

  Verdict: fail reason: Odd TDMA frame number := 935

There's no requirement that periodic interference reports must land
on a TDMA frame number satisfying 'fn mod 104 == 0' - only that they
keep arriving every configured averaging period.  Instead, verify
that the interval between consecutive reports equals 104 TDMA frames
(1 SACCH period), using the new f_gsm_fn_sub() helper.

Change-Id: Ia96f2926400bae8c0a6fb8f81eb56b48ca5f2de9
Related: 53f0ec29 ("l1sap: fix duplicate RF RESOURCE INDICATION on clock bootstrap")

pySim.log: fix E0611: No name 'style' in module 'cmd2'

Change-Id: I191ea56f4c6e4e1916369f69fe2e1653e1d92df1
Fixes: 597f1e0 ("pySim.log, pySim-shell: fix compatibility with cmd2 >= 3.0.0")

common: reset lchan meas state in gsm_lchan_release()

lchan->meas (including interf_meas_num and num_ul_meas) is normally
only reset by lchan_meas_reset() called from rsl_tx_chan_act_ack() on
RSL CHANNEL ACTIVATION.  Idle logical channels are never RSL-activated,
so their measurement state is never reset via that path.

On an OML link re-establishment, osmo-bts does not exit: abis.c tears
down the signalling links, the bts_shutdown FSM powers down all TRXs,
and then waits for reconnect.  The gsm_bts/trx/ts/lchan structures
remain in memory, so stale interf_meas_num survives the reconnect.

This is why we're seeing these ERRORs while running ttcn3-bts-test:

(bts=0,trx=2,ts=4,ss=6) Not enough room to store interference report (0dBm)

Add a lchan_meas_reset() call to gsm_lchan_release(), which is called
from gsm_ts_release() when the nm_channel_fsm enters state
NM_CHAN_ST_OP_DISABLED_NOTINSTALLED.  This is exactly the right
moment: the radio is fully stopped, so no new samples arrive.

Change-Id: I18dc9d30417b0c5b2e579660d4a087d93445f956
AI-Assisted: yes (Claude)

common: stop buffering UL measurements when SACCH is deactivated

When the BSC sends RSL DEACT SACCH, the per-SACCH UL measurement drain
stops (it runs on SACCH timing), but the producer in lchan_new_ul_meas()
keeps appending the measurement contributions from every received
TCH/SDCCH burst.  After one SACCH period (104 frames) the 104-slot
uplink measurement buffer fills up, yielding a flood of:

  NOTICE measurement.c:336 no space for uplink measurement, num_ul_meas=104

Add a bool sacch_active flag to gsm_lchan, set to true in the common
l1sap_chan_act() and clear in l1sap_chan_deact_sacch().  Guard
lchan_new_ul_meas() with this flag so that measurements are silently
discarded while SACCH is inactive - there is nothing to drain the
buffer and no SACCH channel on which to report the results to the BSC.

Change-Id: I3943c788cab5d2411b06ac681d4d412852bac0a7
AI-Assisted: yes (Claude)

common: flush paging queue in nm_bts_fsm's NOTINSTALLED on_enter

paging_reset() exists to flush stale paging records from the queue,
but was never called anywhere.  Stale paging records can accumulate
when the OML link goes down: osmo-bts does not exit, so the paging
queue survives into the next BSC session.

Call it alongside bts_cbch_reset() and bts_asci_notification_reset()
in st_op_disabled_notinstalled_on_enter(), which fires after all TRXs
are confirmed closed and before a new OML connection is accepted.

Change-Id: I109ab282986b68b68ba5c11859c44b771c0416fd
AI-Assisted: yes (Claude)

rest_api_response_schema: add missing error codes

In SGP.32 V.1.2, new error codes were added to EnableProfileResult,
DisableProfileResult, DeleteProfileResult and AddEimResult

See also: SGP.32, section 2.11.2

Change-Id: I525ca9d3b7fb870405d374160272d8ec26c85880
Related: SYS#8100

esipa_rest_utils: align IpaEuiccDataResponse to SGP.32 V.1.2

The ASN.1 struct IpaEuiccDataResponse has renamed the error code
member from ipaEuiccDataError to ipaEuiccDataErrorCode. The new
ipaEuiccDataErrorCode is a sequence that has an ipaEuiccDataErrorCode
member, which is the equivalent of the previously existing
ipaEuiccDataError member.

See also: SGP.32, section 2.11.2.2

Change-Id: Ie734a09ed4b0d57de30dc6fb377dfada79ea2ae4
Related: SYS#8100

esipa_rest_utils: add support for PSMOs added in SGP.32 V.1.2

SGP.32 adds 3 additional PSMOs:
- setFallbackAttribute
- unsetFallbackAttribute
- setDefaultDpAddress

Change-Id: I03cdd70065a83dfc611d614cf32d817c13fad347
Related: SYS#8100

esipa_rest_utils: add support for PSMOs added in SGP.32 V.1.2

SGP.32 adds 3 additional PSMOs:
- setFallbackAttribute
- unsetFallbackAttribute
- setDefaultDpAddress

Change-Id: I03cdd70065a83dfc611d614cf32d817c13fad347
Related: SYS#8100

rest_api: move "required" member to the correct level

In some locations in the JSON schema files we find the "required"
member on the same level as the members of "properties" (likewise
"items"). This is incorrect, the "required" member should always
be on the same level as the "properties" or "items" member.

(At the moment the JSON schema files serve only documentation
purposes, they are not used to do any actual validation yet.)

Change-Id: I07d51d0e809a718144bd51a6540ab51187bb4daa
Related: SYS#8100

eim_cfg: set eimSupportedProtocol and indirectProfileDownload flags

The members eimSupportedProtocol and indirectProfileDownload were
added as optional members to EimConfigurationData with SGP.32 V.1.2.

Since our eIM implementation only supports eIM Package Retrieval via
HTTPs and the Indirect Profile Download procedure is the only Profile
Download procedure we currently support, the EimConfigurationData
should reflect those properties correctly.

(The EimConfigurationData is not announced actively by the eIM, but
this eIM implementation contains a generator to help with the encoding
of the EimConfigurationData that is programmed into the eUICC)

Change-Id: I4ce236fb1bfb8a3790191be95ab0958dce13a9d8
Related: SYS#8100

esipa_rest_utils: re-align to SGP.32 Section 2.11.2

Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult

Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308
Related: SYS#8100

esipa_rest_utils: re-align to SGP.32 Section 2.11.2

Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult

Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308
Related: SYS#8100

eim_cfg: set eimSupportedProtocol and indirectProfileDownload flags

The members eimSupportedProtocol and indirectProfileDownload were
added as optional members to EimConfigurationData with SGP.32 V.1.2.

Since our eIM implementation only supports eIM Package Retrieval via
HTTPs and the Indirect Profile Download procedure is the only Profile
Download procedure we currently support, the EimConfigurationData
should reflect those properties correctly.

(The EimConfigurationData is not announced actively by the eIM, but
this eIM implementation contains a generator to help with the encoding
of the EimConfigurationData that is programmed into the eUICC)

Change-Id: I4ce236fb1bfb8a3790191be95ab0958dce13a9d8
Related: SYS#8100

esipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6

Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse
Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters

Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce
Related: SYS#8100

esipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6

Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse
Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters

Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce
Related: SYS#8100

esipa_asn1_handler: fix transactionId handling

The transactionId member is now called eimTransactionId. It is also
an optional member.

Change-Id: I1340e0c7aed091e8e5a5089ebd6e524512408cf7
Related: SYS#8100

esipa_asn1_codec: add special handling for ProvideEimPackageResultResponse

In SGP.32 V.1.2 ProvideEimPackageResultResponse is defined as a CHOICE.
This means that this struct now also requires special handling.

Change-Id: I859a175cc28a18ea9334d9b2cf233294fdc95b76
Related: SYS#8100

es9p_client: section 6.3.2.1, rename euiccCiPKIdToBeused to match SGP.32 V.1.2

Section 6.3.2.1: rename InitiateAuthenticationOkEsipa.euiccCiPKIdToBeused to InitiateAuthenticationOkEsipa.euiccCiPKIdentifierToBeUsed

Change-Id: I44c60a2f0d1129093ea67908d2eed167643a4a87
Related: SYS#8100

eim_cfg: set eimSupportedProtocol and indirectProfileDownload flags

The members eimSupportedProtocol and indirectProfileDownload were
added as optional members to EimConfigurationData with SGP.32 V.1.2.

Since our eIM implementation only supports eIM Package Retrieval via
HTTPs and the Indirect Profile Download procedure is the only Profile
Download procedure we currently support, the EimConfigurationData
should reflect those properties correctly.

(The EimConfigurationData is not announced actively by the eIM, but
this eIM implementation contains a generator to help with the encoding
of the EimConfigurationData that is programmed into the eUICC)

Change-Id: I4ce236fb1bfb8a3790191be95ab0958dce13a9d8
Related: SYS#8100

es9p_client: section 6.3.2.1, rename euiccCiPKIdToBeused to match SGP.32 V.1.2

Section 6.3.2.1: rename InitiateAuthenticationOkEsipa.euiccCiPKIdToBeused to InitiateAuthenticationOkEsipa.euiccCiPKIdentifierToBeUsed

Change-Id: I44c60a2f0d1129093ea67908d2eed167643a4a87
Related: SYS#8100

esipa_rest_utils: re-align to SGP.32 Section 2.11.2

Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult

Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308
Related: SYS#8100

esipa_asn1_handler: fix transactionId handling

The transactionId member is now called eimTransactionId. It is also
an optional member.

Change-Id: I1340e0c7aed091e8e5a5089ebd6e524512408cf7
Related: SYS#8100

esipa_asn1_codec: add special handling for ProvideEimPackageResultResponse

In SGP.32 V.1.2 ProvideEimPackageResultResponse is defined as a CHOICE.
This means that this struct now also requires special handling.

Change-Id: I859a175cc28a18ea9334d9b2cf233294fdc95b76
Related: SYS#8100

esipa_asn1_handler: re-align to SGP.32 section Section 2.11.2 and Section 5.14.6

Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse
Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters

Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce
Related: SYS#8100

asn1/SGP32Definitions: apply workarounds

- Some ASN.1 structs from SGP.22 are re-defined under the same name by SGP.32.
  This leads to name clashes, which most ASN.1 compilers have problems with.
  Prefixing the re-defined struct in SGP.32 with "SGP32-" solves the problem.

- The erlang asn1ct ASN.1 compiler seems to misinterpret the ASN.1 spec when
  a context specific tag is used (redundently) on a child struct definition
  and in the parent definition at the same time. Removing te context specific
  tag on the child struct definition solves the problem.

Change-Id: Id90b005fc3c8c8f737b0c740d4c067f90842a1fe
Related: SYS#8100

asn1/SGP32Definitions: upgrade ASN.1 spec to V.1.2

This replaces the existing SGP.32 V.1.0.1 ASN.1 spec with the
unmodified, official SGP.32 V.1.2 spec.

Unfortunately V.1.2 is not backward compatible to V.1.0.1. This means
that the eIM application will still compile, but the result will be
non-functional. The incompatibility problems will be addressed in
the follow-up patches of this patchset.

Change-Id: Id4d217296f43846aa39f5dc7076465e2dab72a7c
Related: SYS#8100

rebar.config: bump meck version: 0.9.2 -> v1.2.0

This fixes a compilation error with recent Erlang/OTP 29:

[  335s] ===> Compiling meck
[  335s] ===> Compiling _checkouts/meck/src/meck_matcher.erl failed
[  335s] meck_matcher.erl:76:6: 'catch ...' is deprecated; please use 'try ... catch ... end' instead.
[  335s] Compile directive 'nowarn_deprecated_catch' can be used to suppress
[  335s] warnings in selected modules.

Change-Id: If3409de1e09ac1b6ce3355d19e47ef0e160a2d3b

common: stop buffering UL measurements when SACCH is deactivated

When the BSC sends RSL DEACT SACCH, the per-SACCH UL measurement drain
stops (it runs on SACCH timing), but the producer in lchan_new_ul_meas()
keeps appending the measurement contributions from every received
TCH/SDCCH burst.  After one SACCH period (104 frames) the 104-slot
uplink measurement buffer fills up, yielding a flood of:

  NOTICE measurement.c:336 no space for uplink measurement, num_ul_meas=104

Add a bool sacch_active flag to gsm_lchan, set to true in the common
l1sap_chan_act() and clear in l1sap_chan_deact_sacch().  Guard
lchan_new_ul_meas() with this flag so that measurements are silently
discarded while SACCH is inactive - there is nothing to drain the
buffer and no SACCH channel on which to report the results to the BSC.

Change-Id: I3943c788cab5d2411b06ac681d4d412852bac0a7
AI-Assisted: yes (Claude)

common: flush paging queue in nm_bts_fsm's NOTINSTALLED on_enter

paging_reset() exists to flush stale paging records from the queue,
but was never called anywhere.  Stale paging records can accumulate
when the OML link goes down: osmo-bts does not exit, so the paging
queue survives into the next BSC session.

Call it alongside bts_cbch_reset() and bts_asci_notification_reset()
in st_op_disabled_notinstalled_on_enter(), which fires after all TRXs
are confirmed closed and before a new OML connection is accepted.

Change-Id: I109ab282986b68b68ba5c11859c44b771c0416fd
AI-Assisted: yes (Claude)

l1sap: fix duplicate RF RESOURCE INDICATION on clock bootstrap

The TTCN-3 test suite (ttcn3-bts-test) expects to receive exactly one
RF RESOURCE INDICATION message from each TRX during the bootstrap stage,
while waiting for all TRX to come up and be configured by the BSC.

l1sap_interf_meas_report() fires whenever bts->gsm_time.fn % period is
0, where period = intave * 104 (typically 624 frames).  Since CLCK.ind
with FN=0 satisfies this condition, a report is sent at the very
beginning of each clock epoch.

This was not a problem before commit fcfc4e83, because the first
CLCK.ind from the transciever was effectively a no-op: with
last_fn_timer.fn zero-initialised, the first indication at FN=0 yielded
elapsed_fn=0 (not > MAX_FN_SKEW), and the catch-up loop (while fn !=
last_fn_timer.fn) would not execute either.  Downlink scheduling only
started on the second CLCK.ind (at FN=102, which is > MAX_FN_SKEW),
and 102 % 624 != 0, so no RF RESOURCE INDICATION was triggered.

fcfc4e83 changed the logic so that Downlink scheduling now begins
immediately on the first CLCK.ind, via an unconditional call to
trx_setup_clock() -> bts_sched_fn(fn).  When fake_trx starts its frame
counter from FN=0, this immediately triggers l1sap_interf_meas_report()
because 0 % 624 == 0.  A second report follows ~2.88s later when the
periodic timer reaches FN=624, making the bootstrap logic
in ttcn3-bts-test unhappy.

Fix by shifting the trigger to (fn + 1) % period == 0, i.e. the report
fires at the last frame of each period rather than the first.  FN=0 now
yields (0+1) % 624 = 1 != 0, suppressing the spurious bootstrap report.
The periodic behaviour and report cadence are otherwise unchanged.

Change-Id: I6550178427b08e67c9763f0f37efff5b88960b1f
Related: fcfc4e83 ("osmo-bts-trx: fix spurious shutdown on first CLCK.ind from osmo-trx")
AI-Assisted: yes (Claude)

common: reset lchan meas state in gsm_ts_release()

lchan->meas (including interf_meas_num and num_ul_meas) is normally
only reset by lchan_meas_reset() called from rsl_tx_chan_act_ack() on
RSL CHANNEL ACTIVATION.  Idle logical channels are never RSL-activated,
so their measurement state is never reset via that path.

On an OML link re-establishment, osmo-bts does not exit: abis.c tears
down the signalling links, the bts_shutdown FSM powers down all TRXs,
and then waits for reconnect.  The gsm_bts/trx/ts/lchan structures
remain in memory, so stale interf_meas_num survives the reconnect.

This is why we're seeing these ERRORs while running ttcn3-bts-test:

(bts=0,trx=2,ts=4,ss=6) Not enough room to store interference report (0dBm)

Add a lchan_meas_reset() call to gsm_ts_release(), which is called
from nm_channel_fsm's NOTINSTALLED on_enter after the TRX is confirmed
closed.  This is exactly the right moment: the radio is fully stopped,
so no new samples arrive.

Change-Id: I18dc9d30417b0c5b2e579660d4a087d93445f956
AI-Assisted: yes (Claude)

common: stop buffering UL measurements when SACCH is deactivated

When the BSC sends RSL DEACT SACCH, the per-SACCH UL measurement drain
stops (it runs on SACCH timing), but the producer in lchan_new_ul_meas()
keeps appending the measurement contributions from every received
TCH/SDCCH burst.  After one SACCH period (104 frames) the 104-slot
uplink measurement buffer fills up, yielding a flood of:

  NOTICE measurement.c:336 no space for uplink measurement, num_ul_meas=104

Add a bool sacch_active flag to gsm_lchan, set to true in the common
l1sap_chan_act() and clear in l1sap_chan_deact_sacch().  Guard
lchan_new_ul_meas() with this flag so that measurements are silently
discarded while SACCH is inactive - there is nothing to drain the
buffer and no SACCH channel on which to report the results to the BSC.

Change-Id: I3943c788cab5d2411b06ac681d4d412852bac0a7
AI-Assisted: yes (Claude)

oml: validate Intave Parameter range in SET BTS ATTR

3GPP TS 52.021 §9.4.24 defines valid range for the Intave Parameter
as 1..31, matching the fixed size of the per-lchan interference sample
buffer (interf_meas_dbm[31] in lchan.h).  Previously any uint8_t value
was accepted without validation, meaning a buggy BSC could send
intave=0 (silently disabling interference reporting) or intave>31
(causing a buffer overflow in gsm_lchan_interf_meas_push()).

Let's guard against that by NACKing the SET BTS ATTR message with
cause=NM_NACK_PARAM_RANGE if the value is outside the valid range.

Change-Id: Id4d3353d4397aaa2517091b020d38ee15e084e2c
AI-Assisted: yes (Claude)

lint: ignore LINUX_VERSION_CODE

When running the linter against dahdi-linux.git or potentially other
repositories with out-of-tree linux kernel modules, it should not
complain about the LINUX_VERSION_CODE being used there:

> drivers/dahdi/dahdi-base.c:6397: WARNING:LINUX_VERSION_CODE:
> LINUX_VERSION_CODE should be avoided, code should be for the version to
> which it is merged

Change-Id: I82d64d43c04561b1643785cb71cfee92e513e560

contrib/jenkins: run 'rebar3 fmt --check'

The pull request "v0.0.2" had a patch that formatted everything with
erlfmt. Let's run it in CI to keep the style consistent.

Related: https://github.com/onomondo/onomondo-eim/pull/10/commits/8bafdb3839d868d6bc18499617761d9acd73d2ad
Change-Id: I271c90dace6e7b6f052b38054815e6dfcbfa60f5