kubernetes show deployment and delete deployment

 

show deployment

$ kubectl get deployments;

NAME              DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
spring-hello      1         1         1            1           22h
spring-world      1         1         1            1           22h
vfe-hello-wrold   1         1         1            1           14m

show services

$kubectl get services;

NAME              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
kubernetes        ClusterIP   10.96.0.1        <none>        443/TCP          2d
spring-hello      NodePort    10.103.27.226   <none>        8081:30812/TCP   23h
spring-world      NodePort    10.102.21.165    <none>        8082:31557/TCP   23h
vfe-hello-wrold   NodePort    10.101.23.36     <none>        8083:31532/TCP   14m

delete deployment

$ kubectl delete deployments vfe-hello-wrold

deployment.extensions "vfe-hello-wrold" deleted

delete services

$ kubectl delete service vfe-hello-wrold

service "vfe-hello-wrold" deleted


by at No comments:

Install Go Lang latest version 1.15.5 in ubuntu

 Download and install

we can install the Go Lang in very easy and simple steps in Linux(Ubuntu)

1. Download Go

2. Install Go

3. Check version of Go

1. Download Go.

Use Curl or wget to download the current binary for Go from the official download page.


sudo wget https://golang.org/dl/go1.15.5.linux-amd64.tar.gz


 If Wget or curl not install, install wget and curl first.


2. Go install.


Extract the archive you downloaded into /usr/local, creating a Go tree in /usr/local/go by below command.

Important: This step will remove a previous installation at /usr/local/go, if any, prior to extracting. Please back up any data before proceeding.

For example, run the following.

sudo tar -C /usr/local -xzf go1.15.5.linux-amd64.tar.gz



Add the go binary path to .bashrc file /etc/profile. Add /usr/local/go/bin to the PATH environment variable.

You can do this by adding the following line to your $HOME/.profile or /etc/profile (for a system-wide installation): 
 
export PATH=$PATH:/usr/local/go/bin

After adding the PATH environment variable, you need to apply changes immediately by running the following command.

source ~/.bashrc

3. Check version of Go

 
Verify that you've installed Go by opening a command prompt and typing the following command: 
 
go version

 

You can also install go from the snap store too.


sudo snap install --classic --channel=1.15/stable go



Remove Go Lang from the system completely: 

To remove an existing Go installation from your system delete the go directory. This is usually /usr/local/go under Linux.


 sudo rm -rf /usr/local/go 

 sudo nano ~/.bashrc # remove the entry from $PATH 

 source ~/.bashrc
by at No comments:

5G-NR: NRF


Role of NRF in 5G architecture:

Network Repository Function (NRF)

The NRF maintains a record of all the 5G elements that are available in the network and their supported services. It allows other NF instances to subscribe and be notified of registrations from NF instances of a given type


The NRF supports discovery mechanisms that allows 5G elements to discover each other and get updated status of the desired elements.

The NRF supports the following functions:

  • Maintains the profiles of the available NF instances and their supported services in the 5G core network
  • Allows consumer NF instances to discover other providers NF instances in the 5G core network
  • Allows NF instances to track the status of other NF instances

 It supports the above functions through the following services:

  • Management Services (Nnrf_NFManagement)
  • Discovery Services (Nnrf_NFDiscovery)

Management Services (nrf_NFManagement.

This will handles the following service operations:
  • Receives and handles NFRegister service requests from the Nfs.
  • Receives and handles NFDeregister service requests from the NFs
  • Stores the registered profiles in its own data store using the database service.
  • Receives and handles NFDeregister service requests from the Nfs.
  • Receives and handles the Heart-beat messages from the NFs
  • Monitors the heart-beat expiry, mark the NF profiles as suspended and take appropriate action on the suspended NF profiles.
  • NF profile Retrieval.
  • Receives and handles NFStatusSubscribe service requests from the NFs.
  • Receives and handles NFStatusUnsubscribe service requests from the NFs.
  • Receives and handles NFNotify service requests from the NFs
  • Stores the subscription data in its own data store using the database service
Discovery Services (Nnrf_NFDiscoveryService)

This will handles the following service operations:
  • Receives and handles NFDiscover service requests from the Nfs.

 
NRF Functions/Procedure Support:

The NRF interacts with every other element in the 5G core network and it supports the above functions through the following services over HTTPS protocols:
  • Management Services
  • Discovery Services


Supports the following Functions/Procedure-
1) NRF Management Services-
The NRF Management service is identified by the service operation name Nnrf_NFManagement. NRF supports the following management services.
 
Register NF instance (NFRegister):- It allows an NF Instance to register its NF profile in the NRF; it includes the registration of the general parameters of the NF Instance, together with the list of services exposed by the NF Instance. This service operation is not allowed to be invoked from an NRF in a different PLMN. 
 
Update NF instance (NFUpdate): Enables an NF instance to partially update or replace the parameters of its NF profile in the NRF. It also allows to add or delete services provided by the NF instance.
 
De-register NF instance (NFDeregister): It allows an NF Instance to de-register its NF profile in the NRF, including the services offered by the NF Instance. This service operation is not allowed to be invoked from an NRF in a different PLMN.
 
Subscribe to Status (NFStatusSubscribe): Enables an NF instance to subscribe the status changes of other NF instances registered in the NRF.
 
Unsubscribe to Status (NFStatusUnsubscribe): Enables an NF instance to unsubscribe the status changes of other NF instances.
 
Receive Notifications of Status (NFStatusNotify): Enables the NRF to notify changes status of NF instances to any subscriber of NF status. Changes also include information regarding newly registered and de-registered NFs.


2) Discovery Service:

The NRF Discovery service is identified by the service operation name Nnrf_NFDiscoveryService.
Nnrf_NFDiscoveryService- It also allows an NF to subscribe to be notified of registration, de-registration and profile changes of NF Instance along with their NF Services.





by at No comments:

5G(NR)-F1 Setup Procedure

 

F1 Setup

The purpose of the F1 Setup procedure is to exchange application level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface. This procedure shall be the first F1AP procedure triggered after a TNL association has become operational. The procedure uses non-UE associated signalling, it is cell related procedure.

This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also re-initialises the F1AP UE-related contexts (if any) and erases all related signalling connections in the two nodes like a Reset procedure would do.

Successful Operation


The gNB-DU initiates the procedure by sending a F1 SETUP REQUEST message including the appropriate data to the gNB-CU. The gNB-CU responds with a F1 SETUP RESPONSE message including the appropriate data.

If the F1 SETUP REQUEST message contains the gNB-DU Name IE the gNB-CU may use this IE as a human readable name of the gNB-DU.

For NG-RAN, the gNB-DU shall include the gNB-DU System Information IE and the TAI Slice Support List IE.

The gNB-CU may include the Cells to be Activated List IE in the F1 SETUP RESPONSE message. The Cells to be Activated List IE includes a list of cells that the gNB-CU requests the gNB-DU to activate. The gNB-DU shall activate the cells included in the Cells to be Activated List IE and reconfigure the physical cell identity for cells for which the NR PCI IE is included.

For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the F1 SETUP RESPONSE message.

The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the F1 interface is operational and other F1 messages may be exchanged.

For NG-RAN, the gNB-DU may include the RAN Area Code IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to TS 38.300 [6].


F1 SETUP REQUEST IEs.

This message is sent by the gNB-DU to transfer information for a TNL association.

Direction: gNB-DU ® gNB-CU

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

 

9.3.1.1

 

YES

reject

Transaction ID

M

 

9.3.1.23

 

YES

reject

gNB-DU ID

M

 

9.3.1.9

 

YES

reject

gNB-DU Name

O

 

PrintableString(SIZE(1..150,…))

 

YES

ignore

gNB-DU Served Cells List

 

1

 

List of cells configured in the gNB-DU

YES

reject

>gNB-DU Served Cells Item

 

1.. <maxCellingNBDU>

 

 

EACH

reject

>>Served Cell Information

M

 

9.3.1.10

Information about the cells configured in the gNB-DU

-

-

>>gNB-DU System Information

O

 

9.3.1.18

RRC container with system information owned by gNB-DU

-

-

 

Range bound

Explanation

maxCellingNBDU

Maximum no. cells that can be served by a gNB-DU. Value is 512.

 

9.3.1.1    Message Type

The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Message Type

 

 

 

 

>Procedure Code

M

 

INTEGER (0..255)

 

>Type of Message

M

 

CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, …)

 

 Procedure Code: every message has its procedure code, so that, that can be identified their class and message type by other nodes. 

Type of Message: The Type can be Initiating Message, Successful Outcome, Unsuccessful Outcome. it is selected by sending node.

9.3.1.23  Transaction ID

The Transaction ID IE uniquely identifies a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure shall use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Transaction ID

M

 

INTEGER (0..255, …)

 

 

9.3.1.9    gNB-DU ID

The gNB-DU ID uniquely identifies the gNB-DU at least within a gNB-CU.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

gNB-DU ID

M

 

INTEGER (0 .. 236-1)

The gNB-DU ID is independently configured from cell identifiers, i.e. no connection between gNB-DU ID and cell identifiers.

9.3.1.10 Served Cell Information

This IE contains cell configuration information of a cell in the gNB-DU.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

NR CGI

M

 

9.3.1.12

 

-

-

NR PCI

M

 

INTEGER (0..1007)

Physical Cell ID

 

 

5GS TAC

M

 

9.3.1.29

5GS Tracking Area Code

YES

reject

Configured EPS TAC

O

 

9.3.1.29a

 

–

 

Served PLMNs

 

1..<maxnoofBPLMNs>

 

Broadcast PLMNs

–

–

>PLMN Identity

M

 

9.3.1.14

 

-

-

>TAI Slice Support List

O

 

Slice Support List

9.3.1.37

Supported S-NSSAIs per TA.

YES

ignore

CHOICE NR-Mode-Info

M

 

 

 

–

–

>FDD

 

 

 

 

 

 

>>FDD Info

 

1

 

 

-

-

>>>UL FreqInfo

M

 

NR Frequency Info

9.3.1.17

 

–

–

>>>DL FreqInfo

M

 

NR Frequency Info

9.3.1.17

 

–

–

>>>UL Transmission Bandwidth

M

 

NR Transmission Bandwidth

9.3.1.15

 

–

–

>>>DL Transmission Bandwidth

M

 

NR Transmission Bandwidth

9.3.1.15

 

–

–

>TDD

 

 

 

 

-

-

>>TDD Info

 

1

 

 

-

-

>>> NR FreqInfo

M

 

NR Frequency Info

9.3.1.17

 

–

–

>>> Transmission Bandwidth

M

 

NR Transmission Bandwidth

9.3.1.15

 

–

–

Measurement Timing Configuration

M

 

OCTET STRING

Contains the MeasurementTimingConfiguration inter-node message defined in TS 38.331 [8].

–

–

RANAC

O

 

9.3.1.57

RAN Area Code

YES

ignore

 

Range bound

Explanation

maxnoofBPLMNs

Maximum no. of Broadcast PLMN Ids. Value is 6.


  


9.3.1.18          gNB-DU System Information

This IE contains the system information generated by the gNB-DU. here we have two mandatory parameters, you could further reach to 38.331 for details.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

MIB message

M

 

OCTET STRING

MIB message, as defined in TS 38.331 [8].

 

SIB1 message

M

 

OCTET STRING

SIB1 message, as defined in TS 38.331 [8].

 

 


by at No comments:
Subscribe to: Posts (Atom)