Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If you want to use 5G with HTTP/2 agents, you require a 5G profile configuration. You can select the profile that you configure in the HTTP/2 Server agent configuration.

...

SettingDescription
3GPP Version Setting
Version Select

Select the version of 3GPP to apply to the 5G Profile. 

Note
titleNote!
  • 3GPP Release 15 is the current default version supported
by
  • by Image Modified.
  • Release 16 was added to support the handling of 3xx status codes.


Enable Custom Specification

Support the custom version of the specification of NRF NFManagement Service. See Custom Specification Enabled for more information.


Info
titleInfo!

When enabling custom specification, all fields except for OpenAPI Profile and Enable Validation will be disabled. You need to use the Analysis agent or APL Code to create the NRFspecificationUDR that will contain all the values for the disabled fields. See Custom Specification Enabled for more information.


OpenAPI ProfileSelect the OpenAPI profile for specification of NRF NFManagement Service
Enable ValidationValidate the request for NF (Network Function) registration, heartbeat and de-registration against the OpenAPI schema provided from the OpenAPI profile. 
Configure Server Settings
Path

Enter the exact path to where the HTTP request will register, de-register and update the NF profile in the NRF.

Example: /nnrf-nfm/v1/nf-instances/

Configure NF Settings
NF Instance nameEnter the name of the NF instance for the NF type that you want to use. 
NF typeA list of various NF types is available for selection. The default is set to CHF (charging function).
Heartbeat timerEnter how often you want the NF registration to be updated in seconds in the NRF.
NF Registration status

Select the registration status that you want to have updated. You can select REGISTERED or UNDISCOVERABLE. 

Select REGISTERED to register your NF instance to the NRF. Select UNDISCOVERABLE if you want to register to the NRF but without being discovered by other NFs.

FQDNEnter the Fully Qualified Domain Name (FQDN) for the NF instance.
Support NRF ChangeSelect this option to allow the NRF server to modify the heartbeat timer provided by the NRF client upon registration.
IPv4 Address ListYou can add the IPv4 address(es) for the NF instance.
IPv6 Address ListYou can add the IPv6 address(es) for the NF instance.

...

5G Profile - Advanced parameters tab

In this tab, you can add settings in a JSON configuration in accordance with 6.2.6.2.3 "Type: NFProfile" as defined in 3 the specification GPP TS 29.510, https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3345. See the example below:

Note
titleNote!

Values set in the Advanced Parameters tab will override those set in the General tab.

...

Info
titleExample - Json configuration of advanced parameter


Code Block
{
	"nfProfileChangesSupportInd": true,
	"nfProfileChangesInd": true,
	"allowedPlmns": [
                           {
		"mcc":"262-01",
		"mnc":"302-720"
                           }
	],
	"allowedNfTypes": [
		"PCF",
		"CHF"
	],
	"allowedNfDomains": [
		"www.domainname.com"
	]
}

Custom Specification Enabled


Anchor

...

custom.spec

...

custom.spec
Custom Specification Enabled

When custom specification is enabled in 5G Profile, HTTP/2 Server agent will not perform registration of NF (Network Function) automatically during the startup of the workflow. The HTTP/2 Server agent will instead, wait to receive the NRFspecificationUDR in order to perform NF registration, heartbeat and de-registration. You can refer to the example below:

...