<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by GooRAM on Medium]]></title>
        <description><![CDATA[Stories by GooRAM on Medium]]></description>
        <link>https://medium.com/@gooram?source=rss-c733ed9d0761------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mdg8_hugxoqoQ4DIoYUT_Q.png</url>
            <title>Stories by GooRAM on Medium</title>
            <link>https://medium.com/@gooram?source=rss-c733ed9d0761------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:59:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gooram/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5G : What’s the NRF ?]]></title>
            <link>https://gooram.medium.com/5g-whats-the-nrf-7db7a83cb1bd?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/7db7a83cb1bd</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[5gc]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Thu, 08 Jun 2023 20:07:46 GMT</pubDate>
            <atom:updated>2023-06-08T20:25:18.763Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>5G : What’s the NRF ?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*ijOwsy5OK2js5Fb2Kn0bIQ.png" /></figure><p>The new 5G Core network (5GC) is completely based on what is called a Service-Based Architecture (SBA), which implements IT network principles and a cloud-native design approach. Thus, 5GC network functions (NFs) are refactored into individual micro-services coming together to automatically discover each other, and utilize the services offered by each other. With this refactoring, NFs become composed of a multitude of services, each of which might have many instances. With the increasing number of such micro-services, the complexity of service-to-service communications is further increased. And to overcome this challenge, 3GPP has drawn on IT experiences and adopted the “service discovery” concept, one of the NRF‘s tasks.</p><p>In this blog, we will describe the NRF (Network Repository Function), its benefits and all the services that offers.</p><h4><strong>SBA Challenge</strong></h4><p>To enhance the flexibility and scalability of the network, 3GPP has adopted the SBA approach. With this new architecture, the core network is decomposed into well-defined, standardized network functions that communicate with each other using standardized interfaces and protocols. 4G core network elements are decomposed into individual services called Network Functions (NFs) and new NFs were added to meet the needs of the new 5G use cases, like NRF, NSSF etc… (see figure 1)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jCxv8TntUIEqJ0JhK3LLeg.png" /><figcaption>Figure 1: EPC and 5GC comparison</figcaption></figure><p>The table below outlines the decomposition of some EPC network elements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*QRwhKTEnvnDWSFo-YCNCNw.png" /><figcaption>Table 1: Mapping between some 4G network elements and 5GC NFs</figcaption></figure><p>SBA design also consists in reorganizing network elements into NF consumers and NF producers that are coming together to automatically discover each other, and utilize the services offered by each other. Moreover, 5GC NFs will be implemented using the micro-service architecture, which means that each NF will be formed by a combination of micro-services running with dynamic changes. Each NF is divided into several self-contained, self-managed and reusable network function services (NFSs) which can operate independently without relying on each other.</p><p>This approach will certainly enhance the flexibility, scalability and efficiency of the new 5G core network. However, with the increasing number and dynamic/volatile nature of such micro-services, the complexity of the network architecture is further increased. Which lead to the need for an automatic mechanism that allows services to locate and communicate with other services without the need for a complex and static configuration. These challenges are the key reasons behind the 3GPP adopting of IT service discovery concept and the introduction of a new NF called NRF.</p><h4><strong>NRF services</strong></h4><p>In previous generations of mobile core networks (2G, 3G and 4G), if a new function is introduced or an existing network element is expanded, the operator needs to reconfigure all the existing networks elements with the information needed to address the newly added equipment. In 5G however, this static configuration does not fit the dynamic environment of the SBA architecture, which leads to the introduction of the NRF. The NRF removes the need for network configuration every time a new NF is added/removed from the network, or every time NF capacity is expanded.</p><p>The NRF is a central registry, holding information about every NF, which can then be shared with any NF, when required. It can be viewed as an evolution of the DNS in EPC networks with enhanced capabilities.</p><p>In practice, when you bring a new NF or expand an existing one, this new NF instance only need to interact with the NRF in order to register its profile and discover all the NFs composing the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*KOyIuA2bPOgZa6PgxBfJHg.png" /><figcaption>Figure 2: NRF based registration and discovery</figcaption></figure><p>To maintain its database and to have a continually up-to-date topology view, the NRF allows NFs to register/deregister itself, its supported services and to update their status. Additionally, the NRF allows NF instances to subscribe to status updates of other peers. Any registration, deregistration or profile change of an NF instance should be notified to other NFs which result in keeping NF local cache up-to-date and thus minimizing the number of NRF queries.</p><p>The following table shows the NRF services and service operations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*7h3LEip2ExDfiD4Na_VzuA.png" /><figcaption>Table 2: NRF services and operations</figcaption></figure><h4><strong>NF discovery</strong></h4><p>Service discovery is the process of automatically finding what instances of a service fulfil a given request. Upon receipt of the discovery message from the NF consumer, the NRF checks its own database and selects a list of available service producers from the registered NFs based on different parameters specified by the consumer NF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdvKQGO1qxNrgku349srVQ.png" /><figcaption>Figure 3: Discovery &amp; selection call flow</figcaption></figure><p>The call flow above is an example to illustrate the SMF selection process:</p><p>1. All the NFs (AMF and SMFs) need to register their profiles in the NRF. The NF profile contains: supported services, PLMN, IP address, DNN, S-NSSAI …</p><p>2. The consumer AMF initiates a discovery request to the NRF, searching for an available SMF fitting the requirements (NF service= PDU session; S-NSSAI =1; DNN =1, PLMN=1, Locality =2)</p><p>3. The NRF checks its own database and selects an SMF that fits the AMF requirements. In our case, the only SMF matching the discovery criteria is SMF2. <strong>Which means that the whole selection process is done by the NRF.</strong></p><p>N.B: When the NRF replies with a <strong>list</strong> of available NF producers, the NF consumer should handle the selection or delegates this process to the SCP (if one exists). For more details about this case, you can refer to my previous post about “<a href="https://gooram.medium.com/5g-signaling-c-or-d-265a15b55006">C or D model</a>”.</p><p>4. The AMF send then a PDU session request to the selected SMF to establish a session.</p><h4><strong>NF authorization</strong></h4><p>The 5GC introduces the notion that an NF can discover all other NFs by consulting the NRF. Therefore, and for security reasons, NF consumers have to be authorized before initiating a service request. Thus an NF producer defines access authorization policies (based on NF type, PLMN, S-NSSAI…) to determine the NF consumers that can access it. The policies can be sent to the NRF during the registration/profile update processes or can be configured directly on the NRF. This kind of authorization is called <strong>static authorization</strong> (like authorization mechanisms used in 3G/4G) and it can be implemented when token-based authorization is not used.</p><p><strong><em>Token-based authorization</em></strong></p><p>To secure intra-domain communications between NFs, 3GPP has introduced the Token-based authorization, a new concept based on OAuth2.0 framework (as specified in RFC 6749) where the NRF plays the role of “Authorization server” to restrict unauthorized NF consumers to access the services provided by the NF producers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*aT282OFZiVur7UUoOLPzXw.png" /><figcaption>Figure 4: Token-based authorization</figcaption></figure><p>When an NF sends a discovery request, it requests an access token from an NRF. The NRF then issues an access token with a validity period.</p><p>After receiving the service request from the consumer (OAuth client), the NF producer in “Resource server” role shall validate the access token, its expiry and its access scope before authorizing the access to the provided services.</p><blockquote>N.B:</blockquote><blockquote>· Token-based authorization is performed when a NF consumer invokes a NF producer for the first time, access token expires or there is a change in the requested service.</blockquote><blockquote>· Token-based authorization is optional in case mTLS is used. However, with the complexity that TLS brings, many operators are opting for token-based authorization (application layer security) as a security solution for intra NF communications.</blockquote><h4><strong>Selection &amp; Load Balancing</strong></h4><p>The NRF, as a centralized repository for all the 5G core network functions, maintains an updated record of NF status and their profiles. Among the attributes that compose a NF profile, are Capacity, Priority and Load. These parameters, if present, can help in performing NF selection and load balancing:</p><blockquote>· NF priority: lower values indicate a higher priority.</blockquote><blockquote>· NF Capacity: static information expressed as a weight relative to other NF instances of the same type.</blockquote><blockquote>· NF Load: dynamic load information (0 to 100); indicates the current load percentage of the NF.</blockquote><p>The call flow below illustrates the role of the NRF in providing selection &amp; load balancing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mmxw9kse6SPNQi3UtLQyng.png" /><figcaption>Figure 5: UDM selection example</figcaption></figure><p>· Upon receiving a service discovery request from the AMF, the NRF selects available UDM instances (UDM1, UDM2, UDM3 and UDM4) based on SUPI ranges and returns the service discovery result. The NRF response includes priority, capacity and load of each UDM instance.</p><p>· The AMF will use the information priority, capacity and load to select the appropriate UDM instances (UDM3 is not selected because of its load and UDM4 because of its priority).</p><p>· The AMF calculates the percentage based on the <strong>free capacities</strong> (40% and 60% in our case) and send the requests to UDM1/UDM2.</p><blockquote>N.B: when an <a href="https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5">SCP </a>is used, NFs will be relieved from managing all those selection and load balancing mechanisms.</blockquote><h4><strong>NRF deployment</strong></h4><p>The NRF is a function that can be deployed standalone or can be collocated with other network functions. The table below shows NRF implementation per vendor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*taK-gezReISg6rXJgjw68A.png" /><figcaption>Table 3: NRF implementation per vendor</figcaption></figure><p>As you can see from the table above, most of the vendors are implementing the NRF function as a standalone solution combined with the NSSF function. However, 3GPP in their TS 23.501 recommanded to collocate the NRF with the SCP when <a href="https://gooram.medium.com/5g-signaling-c-or-d-265a15b55006">model D</a> is adopted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*ZeCKQXOJegG9g-QQL0eLsA.png" /><figcaption>Figure 6: NRF &amp; SCP in model D</figcaption></figure><p>3GPP recommendation is mainly justified by the volume of the traffic exchanged between NRF and SCP. In model D as you know, communications between NF consumers and NF producers are indirect and all the NRF traffic (service discovery, authorization, selection and load balancing) goes through the SCP (see figure 6). Thus, when NRF and SCP work together, they can enable more optimized NF selection/load balancing and a better-secured NF-NF communication.</p><h4><strong>Summary</strong></h4><p>3GPP introduces the NRF to deal with SBA challenges and enhance the autonomy of networks. In small deployments, NFs can be configured manually and can communicate by creating static links among themselves. However, in medium- and large-sized 5G networks, this static configuration become unmanageable.</p><p>As a discovery solution, the NRF automate the network so that each new NF instance can be plug-and-play. NFs can be upgrad­ed; expanded or removed independently with minimal impact on each other, which reduces operational costs and time-to-market of new solutions.</p><p>Given its role in the 5G core, the NRF has a complete view of the topology, capacity and performance of the network. Therefore, it can help to centralize selections decisions and to better control the overall load balancing in the network. The NRF can also enhance the security of the network by implementing the NF authorization mechanism.</p><p>To conclude, the NRF allow operators to get the most of the new 5G architecture in terms of flexibility, efficiency and automation.</p><h4><strong>References:</strong></h4><p>-3GPP TS 29.510</p><p>-3GPP TS 23.502</p><p>-3GPP TS 33.501</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7db7a83cb1bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5G: Do we need a BSF?]]></title>
            <link>https://gooram.medium.com/5g-do-we-need-a-bsf-32847673b292?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/32847673b292</guid>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[5gc]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Thu, 06 Apr 2023 12:26:34 GMT</pubDate>
            <atom:updated>2023-05-12T21:02:31.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*iZB5ZExILQahjgZHiAyQ1Q.png" /></figure><p>5G Core (5GC) is the heart of a 5G mobile network; it handles a wide variety of essential functions in the mobile network, such as connectivity and mobility management, authentication and authorization, and policy management, among others. Like 4G networks, the new 5G core domain supports the PCC (Policy and Charging Control) architecture where the PCF (Policy Control Function) takes the role of a central network component interacting with other network functions (SMF, AMF, NEF/AF…) and feeds them with <strong>policy rules</strong> needed for requesting and managing service quality on a per session basis.</p><p>With the advent of 5G, PCC networks are expected to support massive number of devices with various data, transmission, and bandwidth requirements. These requirements are driven mainly by use cases ranging from mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). To cope with the growing number of connected devices and huge amount of policy traffic, Communication Service Providers (CSP) are opting for deploying multiple PCFs as a scalability solution and thus securing their policy networks. However, having numerous PCFs in a network comes at a cost, mainly increasing the complexity of selecting a PCF when many NFs are getting involved during a session.</p><p>In PCC architecture with multiple PCFs, policy rules shall be applied from the access network to the core with consistency and the PCF needs to be able to maintain the relations of different sessions over different interfaces. Therefore, all messages of the same subscriber from different interfaces and for a specific session must be routed to the same PCF. This routing mechanism is called “Session Binding” and it is handled by a new 5G network function called BSF (Binding Support Function).</p><h3><strong>4G session binding</strong></h3><p>BSF concept is borrowed directly from the experiences of 4G. In EPC networks with multiple PCRFs (Policy and Charging Rules Function) deployed, it is recommended that all Diameter sessions established over different interfaces (Gx, Rx, S9) for a specific session; use the same PCRF instance. This intelligent routing is called “PCRF Session Binding” and it is provided by the Diameter Routing Agent (DRA). Based on subscriber identity (e.g. IMSI or IP address), DRA ensures that all sessions related to the same subscriber will be routed to the same PCRF.</p><p>A good example here is Gx/Rx binding during a VoLTE call (figure 1). The DRA binds Gx and Rx interfaces to one PCRF based on IMSI/IP address. It first establishes Gx session by selecting a PCRF and then creates/stores the PCRF instance ID. When another Rx session is created, the DRA uses the included IP address to find the associated binding information in its session storage and route Rx messages to the selected PCRF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IPZHyIUqVSdQbmmqf73Gw.png" /><figcaption>Figure 1: Gx-Rx session binding</figcaption></figure><p>For subsequent Gx and Rx messages, Gx and Rx session ID are used to select the same PCRF even if the UE IP address is not present in the received message.</p><p>N.B: In 4G, session binding is also applicable to OCS and AAA solutions.</p><h3><strong>5G session binding</strong></h3><p>The session binding function used in 4G is comparable to the 5G BSF. In 5G, subscribers are dynamically assigned to a PCF when the initial session is created. All subscriber Policy sessions from anywhere in the network are routed to the assigned PCF until that subscriber’s last session ends, at which point the next session may be routed to a different PCF. This dynamic mapping of subscribers to PCFs is provided by the BSF that ensures that all messages of a session received over different interfaces (such as N5 and N7) go to the same PCF with which a subscriber registers.</p><h3><strong>Main 5G use case</strong></h3><p>As of today, the main scenario that necessitates a binding is voice call over new radio (VoNR). As you know, IMS networks will continue to manage voice calls for 5G subscribers, as there is no SBA solution for voice services at the moment. A 5G subscriber who wants to make a voice call, will initiate the voice session on the IMS network via Rx diameter interface but it should be connected to the same PCF which was previously selected while creating the N7 session in 5GC. The BSF then will correlate between 5GC and IMS sessions and bind them to select the same PCF instance. (See figure 2)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WdVsBsb34uBMoHIAQFk4gg.png" /><figcaption>Figure 2: N7-Rx binding</figcaption></figure><p>In 5G, N7 sessions are established first, well before associated Rx sessions are created. Therefore, the SMF selects a PCF when a subscriber makes a service request. In the following, PCF asks the BSF to create a new entry in its session binding storage, which mainly includes the mapping between the UE IP address and selected PCF. Subsequently, when a request for a new Rx session is received, DRA uses the included UE IP address to find the associated binding information in its session storage. Otherwise, it sends the Rx message to the BSF to get the PCF address serving the subscriber and thus routing the message to the indicated PCF.</p><p>Upon session termination, all associated information is removed from the BSF and DRA session storages, which opens the door to selecting another PCF when the subscriber starts another session.</p><p>According to 3GPP, the only use cases that need a binding are:</p><p><em>1. Application Function (AF): it interacts with the BSF via HTTP2 N5 or Diameter Rx interfaces. For VoNR use case, the P-CSCF is the IMS AF.</em></p><p><em>2. Network Exposure Function (NEF): A NF that exposes 5G core network capabilities to third parties (same as 4G SCEF). It uses </em><strong><em>HTTP N5</em></strong><em> interface to interact with the PCF.</em></p><p><em>3. Network Data Analytics Function (NWDAF): NWDAF brings analytics capabilities to 5GC and define how other NFs should interact with it.</em></p><h3><strong>BSF Services</strong></h3><p>BSF is one of the control plane network functions of the 5G core network. It provides Protocol Data Unit (PDU) session binding functionality and ensures that an Application Function (AF) request for a certain PDU session, reaches the PCF holding the PDU session information. BSF stores the binding information and allow NF service consumers to register, update, remove and discover a binding information by exposing <strong>Nbsf_management</strong> service. (see table 1 below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*wMoh9g7xbgXWi2XrVtcnZA.png" /><figcaption>Figure 3: NFs interacting with BSF</figcaption></figure><p>The following table shows the BSF services and service operations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAhC-BXSUO4wRJKPs_9aDQ.png" /><figcaption>Table 1: BSF services and operations</figcaption></figure><p>According to 3GPP, the only NF that is responsible for creating a session binding is PCF. It uses the “Register” operation to instruct the BSF to create a new entry in its session storage based on the “PcfBinding” information. The “PcfBinding” field contains the mapping between the user identity (SUPI and GPSI), the UE addresses (IP or Ethernet), network ID (DNN, S-NSSAI) and the selected PCF.</p><p>The “PcfBinding” info shall include:</p><p><em>· UE address (IPv4 and/or IPv6 and/or MAC)</em></p><p><em>· PCF address</em></p><p><em>· DNN (same as 4G APN)</em></p><p><em>· S-NSSAI (slice ID)</em></p><p>It may include:</p><p><em>· SUPI (or IMSI)</em></p><p><em>· GPSI (or MSISDN)</em></p><h3><strong>BSF binding types</strong></h3><p>BSF provides the session binding function for :</p><p><em>• Voice services: via two modes, proxy or redirect.</em></p><p><em>• Data services</em></p><h4><strong>BSF binding for voice services</strong></h4><p>For voice services, two modes are supported: Proxy agent and Redirect agent. The call flow below illustrates differences between the two modes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4AL8t4vkWiNy8o-re13O0w.png" /><figcaption>Figure 4: proxy and redirect modes</figcaption></figure><p>As already explained, 5G voice services are still managed by the IMS network. In this regard, the BSF needs to be able to interwork with the DRA over the Rx interface to enable session correlation between Diameter and HTTP2. In this case, the BSF can act as a proxy agent or a redirect agent (See above):</p><p><em>• Proxy agent mode: Upon receiving AAR message from the DRA, the BSF queries its own binding database to obtain the host name of the selected PCF. It then inserts the PCF host name in the AAR message, and sends it to the target PCF over the Diameter link.</em></p><p><em>• Redirect agent mode: After receiving an AAR message from the DRA, the BSF queries its own binding database to get the host name of the selected PCF and returns a response carrying the host name to the DRA. The DRA then constructs a new AAR message and sends it to the target PCF.</em></p><p>Here is a brief comparison between the two modes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qy6BaxG8WTacOi4SA3pUzg.png" /><figcaption>Table 2: proxy and redirect modes comparison</figcaption></figure><p>For voice service binding, BSF offers both scenarios (proxy or redirect) and it is up to the designer to choose the most suitable mode based on operator’s requirements.</p><h4><strong>BSF binding for data services</strong></h4><p>The session binding during data services is the same as that during voice services, except that in data services the whole process is HTTP based between two SBA interfaces N5 and N7. (See call flow below)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaJEIa6J14QzImEj465xEA.png" /><figcaption>Figure 5: N5-N7 binding</figcaption></figure><p><strong><em>Call flow description:</em></strong></p><p><em>· Steps 1/2: N7 session is established first, before the associated N5 session is created</em></p><p><em>· Steps 3/4: At the request of the PCF, the BSF creates a new entry in its session storage that includes the mapping between the user equipment (UE) IP address and the selected PCF.</em></p><p><em>· Step 5: When a request for a new session is received, NEF/AF discovers the BSF using the NRF.</em></p><p><em>· Steps 6/7: NEF/AF uses the Nbsf_Management_Discovery service to request the PCF address from the BSF. The BSF uses the included UE IP address to find the associated binding information in its session storage.</em></p><p><em>· Steps 8/9: After receiving the PCF address from the BSF, the NEF/AF initiate a new request and sends it via N5 interface to the target PCF.</em></p><h3><strong>BSF Deployment Options</strong></h3><p>As per 3GPP, the BSF is a function that can be deployed standalone or as a functionality provided by other network functions, such as PCF, UDR, NRF and SMF. However, 4G experiences have shown that the best option for session binding function is to be managed by a node in the middle (like DRA) as it belongs to the signaling controlling framework. Therefore, the best choice for BSF deployment is a <strong>standalone</strong> node acting as a middleware or co-located with signaling controllers like SCP (Service Communication Proxy). That is why 5GC vendors like Ericsson, Huawei, and Nokia include the BSF in their signaling controller package:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_p7Ndfl0KQvXONFfnYi2w.png" /><figcaption>Table 3: BSF colocation with SCP and DSC</figcaption></figure><h3><strong>Conclusion</strong></h3><p>The 5GC network is expected to support massive number of devices with various data, transmission, and bandwidth requirements. A solid signaling architecture must have the flexibility to control all parts of a 5G core network, while also allowing the core network to scale with zero impact on QoS. In a network with multiple PCFs, it is important to ensure continuous communication between various NFs in any scenario. Therefore, different NFs need to coordinate when selecting a PCF to ensure that various sessions belonging to a single subscriber originating on different interfaces are bound together and routed towards the same PCF. Which brings a new entity called BSF in the 5GC architecture.</p><p>To conclude, carriers need a BSF as soon as they have two or more PCFs serving a subscriber and a binding use case either VoNR or an AF/NEF need. When a carrier deploy multiple PCFs, but each subscriber is assigned to a unique PCF (range based PCFs); in this case there is no need for a BSF and the SCP is capable of handling this kind of selection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32847673b292" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5G signaling: C or D?]]></title>
            <link>https://gooram.medium.com/5g-signaling-c-or-d-265a15b55006?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/265a15b55006</guid>
            <category><![CDATA[5gc]]></category>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 14:52:27 GMT</pubDate>
            <atom:updated>2023-03-06T17:42:02.769Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zx2JNmIaM95_vS1GrgQkQg.png" /></figure><p>By adopting cloud-native technology, the 5GC will be reorganized into individual services called Network Functions (NFs) that are coming together to dynamically discover each other, utilize the services offered by each other and <strong>interact</strong> which each other in order to fulfill the required 5G service. For the communication between NFs, 3GPP has defined four modes encompassing direct and indirect scenarios between a Consumer NF and a Producer NF:</p><p>- A and B modes : for Direct communication without any proxy in the middle</p><p>- C and D modes : for Indirect communication with the use of SCP (Service Communication proxy)</p><p>In this paper, we will go through the four modes and discuss which configuration is recommended in a production environment.</p><h3><strong>Direct modes</strong></h3><p>In their first release of 5G specifications (<strong>Release 15</strong>), 3GPP has adopted the direct mode for the interaction between NFs Consumers and Producers. This model of communication does not necessitate any proxy between NFs (no SCP is used).</p><p>In the direct mode, there are two options: option A without NRF (Network Repository Function) and option B with NRF. The NRF is the NF that is responsible for the service discovery (a new concept that is related to the adoption of micro-service architecture in 5G); it is used by NFs for the discovery of other NFs and their services. Resulting in off-loading NFs from handling complex connection configuration and management.</p><p><strong>Model A:</strong> As you can see in the figure 1 below, neither NRF nor SCP are used. Consumers are statically configured with producers’ “NF profiles” and directly communicate with a producer of their choice. The selection process of service producers is performed by consumers. This kind of deployment can be used in a test environment for example, but not in production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/1*1uMx3roFgzOmFUJ0wkBdMA.png" /><figcaption><em>Figure 1: NF/NF Communication model A</em></figcaption></figure><p><strong>Model B: </strong>Before sending the request to the producer, the NF consumer interacts directly with the NRF for service discovery (producers’ discovery). Based on the discovery result, the consumer does the selection and sends the request to the selected producer. In this option, the NF consumer need to support discovery result caching and selection process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*Z7aCmu7T9c9RW1ZKfpO7Bg.png" /><figcaption><em>Figure 2: NF/NF Communication model B</em></figcaption></figure><p>Model B has typically been used by operators for early 5GC deployments based on Release 15 and also for Release 16 small networks.</p><h3><strong>Indirect modes</strong></h3><p>Indirect communication between NFs was introduced in <strong>3GPP Release 16</strong> to offload discovery and selection tasks from consumers so that they can become lighter and focus on the business logic. In contrast to direct modes, the new models of communication are indirect via SCP that mediates messages between service consumers and producers. The use of an SCP is similar to the use of a STP/DRA in 2G-3G/4G mobile core networks.</p><p><strong>Model C:</strong> Indirect communication <strong>without</strong> delegated discovery</p><p>Allows NFs to communicate directly with NRF for profile registration and discovery, while adding the SCP on communication path for some service selections and routing processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/365/1*PrEwvglU419yqJI1lTzhhA.png" /><figcaption><em>Figure 3: NF/NF Communication model C</em></figcaption></figure><p><strong>Model D: </strong>Indirect communication <strong>with</strong> delegated discovery</p><p>Unlike C model,<strong> </strong>consumers do not do any discovery or selection. Discovery is delegated to the SCP, which performs the discovery via NRF and select the suitable producer instance based on the parameters sent the consumer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*8CvhjuQutHM0UJpOPm9T0w.png" /><figcaption><em>Figure 4: NF/NF Communication model D</em></figcaption></figure><p><strong>Summary: </strong>Table 1 summarizes the communication models and how they relate to the usage of an SCP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1UGTObBOVNn-pQd8hQZUSA.png" /><figcaption><em>Table 1: NF/NF communication models summary</em></figcaption></figure><h3><strong>Models C and D comparison</strong></h3><p>In a previous <a href="https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5">post</a>, we discussed the advantages of indirect mode compared to the direct one and detailed the critical role that an SCP plays in optimizing discovery, selection and routing of the traffic. In what follows, we will be trying to further explain what’s the difference between the two <strong>indirect</strong> modes and what’s the best scenario an operator should consider when planning to introduce an SCP solution.</p><p>Both model C and model D add the SCP on communication path. The SCP aggregates signaling links, and provides centralized signaling controlling. In model C, NF consumers continue to own the responsibility of NF producer discovery and selection but delegate the routing logic to SCP. In model D, however the NF producer discovery and selection are delegated to the SCP. Therefore, the difference between model C and D is mainly the responsibility of discovery and selection of producers.</p><h4><strong><em>Call flow</em></strong></h4><p>In model C and as you can see from the call flow below (PCF selection by SMF), the whole process of NF discovery is performed by the NF consumer (SMF in our case). For the selection process however, the NF consumer has the choice to handle it by itself (figure 5: Selection process case1) or delegate a part of it to the SCP (figure 5: Selection process case2).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ip0YTPOuGPSHZFCmYoTQGA.png" /><figcaption><em>Figure 5: Example of model C call flow</em></figcaption></figure><p><em>Description:</em> In model C, a new header added in R16 called 3gpp-Sbi-target-apiRoot, which is used by SCP to route the HTTP request to the producers.</p><ul><li>SMF do the service discovery</li><li>SMF fill <strong>Authority</strong> field with SCP destination, and fill the <strong>3GPP-SBI-TARGET-APIROOT</strong> with real destination.</li></ul><p>Case 1: SMF do the instance selection (PCF1) and SCP do the indirect routing only.</p><p>Case 2 : SMF picks PCF Set 2, allowing SCP to perform the instance selection</p><ul><li>SCP will replace the <strong>Authority</strong> value with 3GPP-SBI-TARGET-APIROOT real destination and route the request to the selected PCF</li></ul><p>Model D shares all the characteristics of model C. Besides, the SCP in Model D takes over the whole process of NF discovery and selection. In addition, the discovery and selection processes are processed by using one request; unlike model C that necessitate two separate requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZwMmiamehJ16mNp4OfDTpg.png" /><figcaption><em>Figure 6: Example of model D call flow</em></figcaption></figure><p><em>Description</em>: In the model D flow, a new header is added in R16 called 3GPP-SBI-DISCOVERY. The use of the 3gpp-Sbi-Discovery enables indirect communication mode for discovery and selection.</p><ul><li>SMF includes Discovery Parameters and directly sends the service request to SCP with 3GPP-SBI-DISCOVERY:</li></ul><p>+ Authority = SCP</p><p>+ 3GPP-SBI-DISCOVERY = PCF Discovery Parameters</p><ul><li>SCP do the delegated discovery and selects the best PCF to address the request based on location, load, capacity, priority and health of the PCF.</li></ul><h4><strong><em>Load-balancing and re-selection</em></strong></h4><p>Delegating the discovery and selection process to the SCP is in accordance with service based architecture (SBA) and cloud native requirements for decoupling the end-user service from the underlying network. By doing so, NFs consumers will be relieved from handling those routine complex tasks and allow them to focus on the application.</p><p>In model D, the whole process of discovery and selection is delegated to the SCP, which takes responsibility for harmonization of load balancing and reselection mechanisms across the network.</p><p>In model C and <strong>depending on the NF consumer configuration</strong>; the SCP can handle routing based on location, load, capacity, priority and health of the NF. Therefore, Load-balancing and re-selection processes could be delegated to the SCP and this delegation will help to harmonize and uniform load balancing and reselection mechanisms.</p><h4><strong>Caching &amp; storing producer’s information</strong></h4><p>Since discovery and selection are the responsibility of the consumer, NFs in model C need to support:</p><ul><li>Discovery result caching.</li><li>Store the producer’s status and information.</li><li>Routing selection policies.</li></ul><p>Model D however, offloads those tasks from NFs consumers so that they can become lighter, focus on the business logic and handle more traffic.</p><h4><strong><em>SCP dimensioning</em></strong></h4><p>Unlike model C where discovery and selection are performed using two different requests, there is only one request that is used for discovery and selection from the consumer side in model D (see figure 6). Therefore, the adoption of model D will simplify the call flow and reduce the number of transactions that a NF consumer should handle, but on the other hand will increase the number of transaction that the SCP should manage.</p><p>When dimensioning an SCP solution, you should take into account the type of model you will deploy. <strong>A model D SCP needs more capacity and resources than a model C one</strong>. Communication service providers must consider this when planning to introduce an SCP solution.</p><h3><strong>Which mode to deploy?</strong></h3><p>As already explained in a previous <a href="https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5">post</a>, the indirect modes of communication offer a range of benefits such as simplifying network topology, centralizing discovery/selection and routing, harmonizing load balancing, etc. The table below give a comparison between C and D models in terms of benefits:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrrx5t1qAEXuOqCkIXG23g.png" /><figcaption><em>Table 2: Pros and Cons of C/D communication models</em></figcaption></figure><p>Considering all of the benefits that the SCP offers, an operator which plans to deploy a 5G signaling controller solution will likely choose between model D and model C or a mix of both. To choose the appropriate communication model, an operator should consider the capability of the 5GC (its NFs) and operational needs.</p><p>If all NFs composing the 5GC support the model D and all APIs are supported in both sides SCP and NFs, so it’s recommended to start with model D. This the case for operators who are planning to start their 5GC deployment with Release 16, or operators who are planning to upgrade their existing R15 5GC while introducing the SCP. By implementing model D, they get the maximum benefit from the SCP.</p><p>If there are some existing NFs that support only the model C or some APIs are not supported in D mode, in this case a C mode or a mix of C and D could be implemented.</p><p>So depending on the 5GC capabilities (NFs and SCP), network topology and use cases that will be fulfilled, operators may choose hybrid deployments where model C and model D are both implemented and coexist in the same network. This is because the SCP is able to support them simultaneously, moreover all the SCP vendors provide configuration for model C or model D at per NF service level. And it’s up to the NF consumer to decide which mode to use for a service request. Coexistence of communication modes also facilitates an easy migration from one mode to the other by changing corresponding configurations in the NF consumer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=265a15b55006" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5G Signaling and Service Mesh]]></title>
            <link>https://gooram.medium.com/5g-signaling-and-service-mesh-fda82f509409?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda82f509409</guid>
            <category><![CDATA[service-mesh]]></category>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[telecom]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Tue, 27 Dec 2022 14:33:50 GMT</pubDate>
            <atom:updated>2022-12-27T14:33:50.831Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*owqaGPAKnDwmgECRJ93XZQ.png" /></figure><p>In my previous article <a href="https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5">“5G signaling: Why do telecom operators need an SCP?”</a>, I outlined the importance of the SCP -5G signaling controller- in a 5GC network and why Communication Service Providers should invest in it right at the start of the 5GC deployment. In this post, I will try to further describe the architecture of the SCP (Service Communication Proxy).</p><p>The new 5GC architecture is a set of network functions (NFs) that need to interact in order to fulfill the required 5G service. To facilitate the communication between NFs (consumers and producers), 3GPP has introduced the SCP. For its architecture, 3GPP outlined three possible scenarios: SCP based on service mesh, SCP based on independent deployment units, and SCP based on name-based routing. In this article, we will be discussing those three proposals and which one is implemented by vendors.</p><h3><strong>SCP based on service mesh</strong></h3><p>As already explained in my previous <a href="https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5">post</a>, the new 5G Core network (5GC) is completely based on what is called a Service-Based Architecture (SBA), which implements IT network principles and a cloud-native design approach. This allows the implementation of the existing web scale technologies and open source software used in IT architectures. One of the technologies that 3GPP has recommended to adopt is “service mesh”.</p><h4><strong>Off-the shelf service mesh</strong></h4><p>In the cloud native ecosystem, applications are developed using micro-service architecture with a high degree of modularity, such that applications are composed from easily managed and deployed services across a multitude of infrastructures with flexible and minimal coupling. With this refactoring, applications become composed of hundreds of services, each of which might have many instances. This new concept enhance the flexibility and efficiency of IT solutions, however with the increasing number of such microservices, the complexity of service-to-service communications is further increased. To overcome this challenge, a service mesh was introduced.</p><p>A service mesh is a dedicated infrastructure layer for facilitating service-to-service communications. It manages service discovery, controls the delivery of service requests, performs load balancing, encrypts data and adds observability features to microservices.</p><p>As illustrated in figure 1, a service mesh consists of two elements: the data plane and the control plane:</p><p>· <strong><em>The data plane</em></strong> is a set of proxies (sidecars) deployed alongside application code. In the case of Kubernetes, a sidecar container can be deployed along with application service container as part of the Kubernetes Pod. These proxies handle the communication between microservices, all service calls moving to and from a service go through these proxies. The proxy also act as a point at which the service mesh features can be introduced. It then applies rules of authentication, authorization, encryption, rate limiting and load balancing, handles service discovery, implements logging, tracing etc.</p><p>· <strong><em>The control plane </em></strong>is the brain of the mesh that coordinates the behavior of proxies and provides them with the rules needed to manage inter-service communications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*HQ85jSHS5R6N0NebEKS5cA.png" /><figcaption>Figure 1: service mesh architecture</figcaption></figure><h4><strong>Service Discovery</strong></h4><p>One of the tasks that are handled by a service mesh is Service Discovery. A new concept that is related to the adoption of micro-service architecture. A microservice application consist of a number of service instances running with dynamic changes. Therefore, a client needs a mechanism, such as Service Discovery, to locate a server automatically without the need for a complex configuration process. This is done via a <strong>service registry</strong> that allow service instances to register/deregister itself in order to maintain a database of all available service instances.</p><p>The top service mesh solutions (i.e Istio, Consul, Linkerd) have an internal registry to supply the proxy sidecars with information needed for service discovery.</p><p>In 5G, the service discovery is provided by a 5GC NF called NRF (Network Repository Function). The NRF works as a centralized repository for all the NFs, it maintains a record of available NF instances and their supported services. The NRF allows NFs to register/deregister itself and its supported services, which is used by other NFs for the discovery of available instances and their services.</p><h4><strong>3GPP proposal</strong></h4><p>By adopting cloud-native technology, the 5GC will be reorganized into individual services called Network Functions (NFs) that are coming together to dynamically discover each other, and utilize the services offered by each other. As a result, the new 5G network will be confronted with the same challenges that IT solutions have faced. That’s why 3GPP has added in 3GPP TS 23.501/R16 the SCP, to deal with the same issues that the “Off-the shelf service mesh” has dealt with. [1]</p><p>Because of the similarities between SCP and “Service Mesh”, 3GPP has urged 5GC vendors to design their SCP solutions based on the service mesh architecture.</p><p>The design proposed by 3GPP (see figure 2) is based on a distributed model in which SCP service agents are co-located with 5GC network functions (NF) and are acting as sidecar proxies. All the logic required for inter-service communication is abstracted out of the NF microservice and put into the sidecar. Service agent is injected as a sidecar container alongside the NF instance (in the same Pod for Kubernetes) and without the knowledge of the NF. That means, the SCP is <strong>unknown</strong> to the NF and therefore the NF will act as there is no SCP in the path. Once a service agent has been deployed, it interacts with the service-mesh controller; which is responsible for pushing all traffic management policies to all service agents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*XUEgsGj3MVh1aBvH1UtpYg.png" /><figcaption>Figure 2: 3GPP SCP service mesh based architecture</figcaption></figure><p>In this deployment, the SCP manages registration and discovery for communication within the service mesh and it interacts with an external NRF for service exposure and communication across service mesh boundaries.</p><h3><strong>SCP based on independent deployment units</strong></h3><p>Like service mesh architecture, this deployment consists of SCP agents and an SCP controller. The SCP Agent is acting as a proxy that implement necessary peripheral tasks and providing NFs with indirect communication and delegated discovery. It implements the http intermediaries between service consumers and service producers. Routing and selection policies an SCP Agent applies for a given request are determined by routing and selection policies pushed by the SCP controller. Communication between SCP controller and SCP agents is via SCP internal interface. (see figure 3)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*m7tOaeE226Z9Kt77HrMTBA.png" /><figcaption>Figure 3: SCP based on independent deployment architecture</figcaption></figure><p>The word “independent deployment units” indicates that the SCP agent is not co-located in the same deployment unit (i.e. kubernetes pod) with the NF, which means that the SCP is a component known to the NF. Therefore, there is a need to explicitly address the SCP within the NF for leveraging the SCP’s functionality, which necessitates further configuration in both consumer and producer sides. Also, routing mechanisms will be different from those specified for SCP based on service mesh architecture (see clause 6.10 of 3GPP TS 29.500) and NFs should be configured to route all the traffic toward the SCP. [2]</p><h3><strong>SCP name-based routing deployment</strong></h3><p>This scenario implements a name-based routing mechanism that provides IP over ICN (Information-Centric Networking) capabilities [3]. It comprises three essential components (see figure 4):</p><p>· <strong><em>Service router</em></strong><em>:</em> acts as communication proxy and it provides discovery, registration, and routing through a path computation element. It is responsible for mapping IP based messages onto ICN publication and subscriptions. Once ICN information is translated to an IP message, the task of selecting the optimum path is handled by another component called PCE.</p><p>· <strong><em>Path Computation Element (PCE):</em></strong> is the core part of the SCP, which implements the Name-based Routing mechanism. It calculates a path between the consumer and the producer (e.g. the shortest path between the nodes).</p><p>· <strong><em>Registration and discovery service:</em></strong> to perform registration/discovery in the form of an internal service registrar and controller.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*GU0nTCCr4962-6UWFBILpg.png" /><figcaption>Figure 4: SCP name-based routing architecture</figcaption></figure><p>As you can see in figure 4, a service router resides as a single unit within a cluster and serves multiple 5G NFs within that cluster. Service router and 5G NFs are separate components but should be co-located within the same Service Deployment Cluster.</p><p>Service registration is forwarded to the internal registry as well as forwarded to the NRF, which is used to expose NF services outside the depicted SCP.</p><p>After selecting the producer, an NF consumer may communicate either directly without any SCP involvement; or via the Service Router when the NF producer resides outside of the consumer’s Service Deployment Cluster.</p><h3><strong>Which architecture is implemented by SCP vendors?</strong></h3><p>5GC vendors are leveraging the existing service mesh used in IT architectures, to address SBA challenges. To handle congestion control, traffic prioritisation, overload control and optimized routing within a microservices architecture etc.; many 5GC solution vendors are building their SCP based on the service mesh architecture. We will discuss here two of the leading vendors in the 5GC market, Nokia and Oracle.</p><p><strong><em>Nokia CSD</em></strong></p><p>Nokia SCP solution is called Nokia Cloud Signaling Director (CSD). It consists of two main components, a signaling plane and a mesh control plane (see figure 5). All 5G core signaling traverses a signaling plane composed of lightweight service proxies called NFP (Network Function Proxy). The centralized mesh control plane is tasked with the coordination and application of management, operations, and policies to all NFPs. Nokia uses <strong>Istio</strong> for the mesh control and <strong>Envoy</strong> as NFP. [4]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*Bo1QTdVhEqxne32XPTK02A.png" /><figcaption>Figure 5: Nokia SCP architecture [4]</figcaption></figure><p>In Kubernetes, each of the NFPs is autonomously injected as a <strong>sidecar container</strong> alongside the instance of an NF service (same pod). Once an NFP has been deployed, it interacts with the mesh control plane over its APIs to implement and apply the necessary policies ― observability and security, for example ― to the 5G core signaling traffic flows.</p><p>The architecture described above is in line with the service mesh architecture used in IT solutions where the proxy is co-located with the NF in the same deployment unit. The SCP is unknown to the NF, thus there will be no https between the two elements according to 3GPP. This kind of deployment is recommended when the SCP and NFs are all provided by a single 5GC vendor.</p><p><strong><em>Oracle SCP</em></strong></p><p>Oracle SCP is modeled after the cloud-native service mesh solution and is made up of a control plane and data plane (see figure 6). The control plane is used to transfer routing rules from the controller to the worker, while the data plane is used to transport 5G messages. Oracle SCP is composed of Service Proxy Controllers and Service Proxy Workers:</p><p>· <em>Service Proxy Controller</em> — Learns network topology by subscribing to notifications from the NRF. It then derives routing policies and transfers them to the SCP workers. Also hosts the configuration interface for SCP.</p><p>· <em>Service Proxy Workers</em> — Use the routing policies to route the 5G signaling traffic between consumer and producer NFs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*el_KgYdKG3SfM57RAmglcQ.png" /><figcaption>Figure 6: Oracle SCP architecture [5]</figcaption></figure><p>Oracle’s SCP leverages the existing <strong>IT service mesh (Istio/Envoy)</strong> and adds some capabilities to address many of the challenges caused by the SBA architecture. [6]</p><p>Unlike <strong>Istio/Envoy</strong> standard deployment, the proxies in the figure above are not deployed as sidecars alongside the instance of a 5G NF but as a part of SCP microservices. That means that the SCP is a standalone component known by 5GC elements, therefore all NFs should be configured to route the traffic toward the SCP. This kind of architecture is a bit similar the SCP based on independent deployment units, it’s a mix of service mesh architecture and traditional telco architectures which is a good fit when dealing with a multivendor 5GC solution.</p><h3><strong>Conclusion</strong></h3><p>The best SCP architecture should combine the flexibility of modern IT architectures with the reliability and security of traditional telecom solutions. By adopting cloud-native technology, a 5GC network element should be able to take advantage of IT web-scale models that have proven to be agile, cost-effective and customer-oriented. That’s why telco vendors are using open source technologies like service mesh to build their SCP solutions. They make some modifications to the existing IT service mesh (like Istio/Envoy) to fit the requirements of 3GPP and manage the signaling traffic for the 5G deployments.</p><p><strong><em>References:</em></strong></p><p>[1] 3GPP TS 23.501 V16 : Annex G</p><p>[2] 3GPP TS 29.500 V16 : 6.10 Support of Indirect Communication</p><p>[3] “IP over ICN goes live”, Xylomenos, George</p><p>[4] Nokia Software and SK Telecom technical whitepaper “Evaluation of a Service-mesh based Service Communication Proxy for Future 5G Core Network”</p><p>[5] ABI-research: Importance of signaling in 5G</p><p>[6] <a href="https://docs.oracle.com/en/industries/communications/cloud-native-core/2.3.0/scp_install/overview.html#GUID-E3A5EB05-23E0-4CB8-9DC6-3BB262BB2DB5">https://docs.oracle.com/en/industries/communications/cloud-native-core/2.3.0/scp_install/overview.html#GUID-E3A5EB05-23E0-4CB8-9DC6-3BB262BB2DB5</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda82f509409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5G signaling: Why do telecom operators need an SCP ?]]></title>
            <link>https://gooram.medium.com/5g-signaling-why-do-telecom-operators-need-an-scp-e1433d3a7f5?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1433d3a7f5</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[service-mesh]]></category>
            <category><![CDATA[5g]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Mon, 03 Oct 2022 14:31:57 GMT</pubDate>
            <atom:updated>2023-05-12T20:47:38.672Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>5G signaling: Why do telecom operators need an SCP ?</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*_bZihNzvK5Q-6L0kFeHcfA.png" /></figure><p>Signaling is the brain of a any mobile network. It establishes reliable, secure connectivity to the network for end users and provides access to its services. 5G signaling like its predecessors 2G/3G/4G, handles a wide variety of critical functions in the mobile network, such as connectivity and mobility management, authentication and authorization, subscriber data management and policy management, among others. The new 5G Core network (5GC) is completely based on what is called a Service-Based Architecture (SBA), which implements IT network principles and a cloud-native design approach. Thus, 5G network functions (NFs) are agnostic to the underlying cloud infrastructure, enhancing the flexibility and efficiency of the network. However, these improvements come at a cost, mainly increasing the complexity of communications between NFs and connection management.</p><p>To overcome the challenges of the SBA approach, the 3GPP standardized in 5G Release 16 an <strong>optional</strong> entity called Service Communication Proxy (SCP). The SCP can be seen as a middleware for handling signaling communications among NF services in the 5GC. However, this component was missed in the first 5G release (3GPP Release 15); where NFs interact directly; raising the question of whether to deploy the SCP right at the start of the 5GC deployment or wait until later when it becomes necessary.</p><p>Signaling controller is a critical component of any cellular network and a topic of debate since the first digital network was deployed. Previous experiences, especially in 4G, have shown that signaling infrastructure should not be ignored. DSC/DRA/DEA were not specified in the official 3GPP specification. Nevertheless, practical deployments of 4G illustrated that these were indeed vital components to cope with Diameter signaling and its challenges.</p><p>Discussions on the necessity of the SCP took place in 3GPP between Release 15 and 16. In theory and according to the 3GPP, the NRF (Network Repository Function); a new centralized repository for service discovery and management; is the only network element needed for NFs to communicate. A solution that works for trials and small network deployments, but as the network grows in size it becomes unmanageable.</p><p>In this article, we will outline the benefits of using an SCP for indirect communication between NFs, and explain why operators should opt for it when deploying the 5GC.</p><h4>Simplifying Network Topology</h4><p>An obvious benefit from the SCP is that it simplifies the architecture from a mesh network to a star network (see figure 1). By being deployed, the SCP eliminates the need for 5G NFs to set up direct connections between each other. Connections can be optimized (connections reduced by 55% in our example: figure 1) so that each NF only needs to be integrated with the SCP. Resulting in off-loading the consumer NFs from handling complex connection management, reducing deployment effort and therefore lower integration cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*8kj2ngqM3OuGKS68XAwEow.png" /><figcaption><strong>Figure 1: From mesh to a star network</strong></figcaption></figure><h4><strong>Centralizing discovery/selection and routing</strong></h4><p>5G core networks has adopted the Service Based Architecture, a paradigm shift in the network architecture and on how network elements or Network Functions (NFs) communicate with each other. Traditional point-to-point architecture that was being used in 4G is now substituted by a “service bus” that connects the individual network functions (see figure 2). This bus will allow NFs (consumers and producers) to exchange information through service-based interface (Rest APIs) and exchange signaling messages through the HTTP/2 protocol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*zNaX8tnYwGmS6LCA2XuQJA.png" /><figcaption><strong>Figure 2: 5G and 4G core comparison</strong></figcaption></figure><p>The new 5G control plane allow network functions (finer-grained micro-services decoupled from the underlying infrastructure) advertise and provide services which can be consumed by other elements. Each NF can register itself and its supported services to the NRF, which is used by other NFs for the discovery of NF instances and their services. Thus, NFs must discover each other to find those that offer the required services and select the most adequate ones in terms of load, network topology, etc.</p><p>Without SCP, every NF consumer interacts with NRF for service discovery and has to support discovery result caching, and selection; which add a lot of common redundant work on every single NF. However, in indirect communication, discovery/selection/routing tasks are delegated to SCP; which offloads those tasks from NFs consumers so that <strong>they can become lighter and focus on the business logic.</strong></p><h4><strong>Improving routing and Load Balancing</strong></h4><p>One of the functions that SCP can provide is load balancing. Given its position and status, the SCP acts as an intermediary between NFs. This avoids the need for NFs to communicate directly with each other. In this intermediary position, the SCP has a complete view of all the messages arriving for a given NF type; it knows the overall traffic volumes on the network level and how the traffic is distributed across different interfaces, enabling it to take work requests and balance loads across all NFs.</p><p>Load balancing and failover behaviors are not standardized in 3GPP, leading to different behaviors among NF consumer and NF producer implementations. When those tasks are delegated to the SCP, network configurations and behaviors can be harmonized. Additionally, Load balancing algorithms take a large number of parameters into account, such as NF priority/capacity/load, HTTP status codes, TCP connection statuses, rate limits, etc. and implementing all those mechanisms in every NF is a highly complex task. Nevertheless, when an SCP takes the responsibility, NFs will be relieved from remembering and interpreting all those complex routing rules allowing them to focus on the application.</p><p>In a Service Based Architecture, NFs are instantiated in a dynamic fashion that is; they can be added and removed quickly; which make it very difficult for the other network elements to manage these life cycle events. The SCP, however, understands which NFs are active, which NFs are not and can decide how traffic should be routed.</p><p>The “canary upgrade” is another example here, if a NF is upgraded, the SCP decides which requests should be routed to the NF instance running the stable version and which requests should be routed to the NF instance running the upgraded version. This approach cannot be done easily without an SCP.</p><p>In addition to the preceding examples, the SCP can enhance routing by providing features like alternate routing, circuit breaking, outlier detection and can take re-routing decisions based on load conditions and health status of NF providers, which boosts network resiliency.</p><h4><strong>Providing Overload control</strong></h4><p>Telecom operators have already experienced overload issues in their existing EPC networks (4G) and this won’t be different for 5G, as overload situations can happen any time, in any network. 5G core networks will be subject to the very same challenges previous networks have faced, especially given the producer/consumer interface model and the increased number of network elements due to microservices.</p><p>The 3GPP has standardized the overload/load control information (OCI/LCI) mechanism. It consists of sharing the load status via the network repository function (NRF). But with this solution, every NF shall know what to do, and every NF shall do what it needs to do correctly which places a lot of burden on every single NF to do a lot of common redundant work. Another disadvantage is that the load reporting to the NRF is done in configurable intervals so this approach comes with some delay. However, when those tasks are centralized to the SCP, the behavior is always consistent and harmonized, and if even a consumer lacks the OCI/LCI support, the SCP can take a reacting role and start throttling based on the instructions coming from the producers.</p><p>Given its position, the SCP knows the overall traffic volumes on the network level and how the traffic is distributed across different interfaces, therefore it can identify and prioritize important messages over others and proxy them towards the overloaded producer NFs. The SCP can also protects the network from flooding by malicious consumer NFs and at the same time protects producer NFs from being overloaded.</p><h4><strong>Message mediation</strong></h4><p>Message mediation is another concern for 5GC signaling, because of incompatible implementations of the HTTP2 protocol between NFs. This may be needed when the NFs come from different vendors, or to fix some interaction issues even for NFs from the same vendor; for example-those caused by upgrades. An SCP in the middle can address such an issue without requiring software updates from the involved network functions. By manipulating HTTP messages, modifying HTTP headers/ JSON payload or by mapping HTTP statuses and reason codes; the SCP provide a quick and easy solution for protocol adaptation between NFs and therefore resolve all mismatches related to protocol incompatibility and interoperability between NFs.</p><h4><strong>Improving network security</strong></h4><p>Another area where the SCP plays a valuable role is in NFs security. 3GPP has decided to use the HTTP/2 protocol for signaling, taking advantage of the maturity of the protocol and the good understanding the Internet community has for it. Nevertheless, the choice of HTTP/2 does introduce new challenges despite the fact that standards have strongly emphasized security in 5GC architecture such as mandatory use of TLS (Transport Layer Security). HTTP/2 will likely introduce new vulnerabilities that have been well researched and documented in the web domain, where malicious attacks (like DoS : denial-of-service) are on a larger scale than in the telco domain.</p><p>With a star topology, the SCP uniforms the use of the security guidelines for communications between NFs and for their communications with the external world. This means authentication, authorization, and encryption need to be enforced for all intra-NFs communications. Moreover, the SCP enforces these security measures without affecting application code. The SCP can implement global access control lists that prevent unauthorized communications between network functions; it can also implement cryptographic verification using techniques such as mutual transport layer security (mTLS); which brings maximum security by preventing unsolicited interception. In addition, the communications security can be further improved by packet screening to deal with DOS attacks.</p><h4><strong>Centralizing operations</strong></h4><p>Indirect communication mode can help with day-to-day operational challenges. By having the SCP in the signaling path several tasks can be centralized, resulting in a dramatic reduction of operation effort and therefore lower cost. The complete network view, allows the SCP to enable end-to-end signaling visibility of communications (Traceability, Observability and centralized monitoring), which makes network-wide troubleshooting much easier.</p><p>For example, when something is not working correctly, we need probes to gain visibility of the signaling messages to find out why. Without an SCP, many probes are required, but with an SCP, the network gains complete observability through a single probe.</p><p>The use of Transport Layer Security (TLS) on all service-based interfaces further complicates data gathering, that’s why the industry is moving towards application-level tracing solutions where the SCP is the best candidate to provide such tracing.</p><p>Signaling metrics/KPI (Success Rates, Volume, Duration, Size, Latency and HTTP error codes etc.) are automatically collected from any NF and the SCP provides a consistent view of the network health by generating uniform metrics at any given time.</p><p>When centralizing operations to the SCP, the behavior is always consistent. Configuring the centralized SCP is easier than distributing and configuring all nodes. This dramatically reduces the potential for errors by eliminating per-NF configuration scripts and makes system-wide updates and upgrades much easier.</p><p><strong>To conclude</strong></p><p>Deploying a 5GC network is no easy task. With 5G, the core network architecture has evolved to a new Service Based Architecture, bringing some unprecedented benefits in terms of flexibility, agility, and scalability; but does not solve all the <strong>signaling</strong> related issues that service providers have already experienced with legacy networks. Past experiences indicate that signaling infrastructure is one of the most important and critical parts of any mobile network; and even though a 5GC may be deployed without an SCP, it is very likely that every operator will need one once large size deployments are reached.</p><p>Regardless of what 5GC network strategy an operator is following, deploying a signaling infrastructure right from the beginning allows the service provider to reap the benefits of superior performance, high network reliability, and business agility while reducing costs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1433d3a7f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4G/5G interworking : HSS and UDM]]></title>
            <link>https://gooram.medium.com/4g-5g-interworking-hss-and-udm-b91dd2023bfd?source=rss-c733ed9d0761------2</link>
            <guid isPermaLink="false">https://medium.com/p/b91dd2023bfd</guid>
            <category><![CDATA[telecom]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[GooRAM]]></dc:creator>
            <pubDate>Tue, 19 Jul 2022 10:48:12 GMT</pubDate>
            <atom:updated>2023-01-02T14:57:29.317Z</atom:updated>
            <content:encoded><![CDATA[<h3>HSS and UDM Interworking</h3><h4>T<strong>he best data management strategy</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-v_pl8Hz5seGms0zijzogw.jpeg" /></figure><p>It is evident that 5G will dominate the mobile landscape in the future. However, that does not mean that 4G is going away anytime soon. Due to the coverage problem, the coexistence of 4G and 5G will continue for a long time to come even after 5G launches. This coexistence will require interworking between the two systems to provide all types of subscribers with the services required including data management services.</p><p>According to 3GPP standardization, the existing 4G subscriber data management system (HSS: Home Subscriber Server) will be replaced by a new cloud native solution Unified Data Management (UDM). This change will require interworking between HSS and UDM, and especially for operators who choose to keep their HSS separated from UDM. <strong>So, how can operators choose the best data management strategy to ensure interworking with 4G while introducing new 5G services?</strong></p><p>Before answering this question, let us briefly discuss why UDM and HSS need to interact?</p><h4>Why UDM interacts with HSS?</h4><p>Most operators today have to deal with different technologies in their networks, 2G, 3G, 4G or 5G networks. They need to manage subscribers’ data and subscriber access management in a flexible way across all these technologies, while also reducing the impact on nodes on live networks and protecting existing investments. Therefore, at the initial phase of 5G, carriers may have a preference to reuse the existing HLR/HSS infrastructure to provide 2G/3G/4G services. Carriers’ choice to retain the legacy HSS/HLR; in the early stages of 5G; is also driven by the demand for avoiding subscriber data migration and the complexity that brings, especially for subscribers who want to benefit from 5G services without changing their USIM card. This reusing of existing HSS will result, in storing separately the user data of 2G/3G/4G and 5G in different repositories (convergent HSS storing user data for 4G/3G/2G and IMS domains and 5G UDM/UDR storing user data for 5G domain).</p><p>As legacy 2G/3G/4G networks will run alongside 5G for the foreseeable future, interworking is essential for reliable access to subscriber data for user authentication/registration, mobility management, and service authorization. For example, when a 4G subscriber is updated to 5G subscriber, the 4G subscription profile keeps stored in HSS while the new 5G subscription data is provisioned in 5G UDM. The authentication data is only stored in HSS and is reused by UDM for 5G authentication. In this case, the UDM needs to interact with HSS to retrieve the authentication vectors.</p><p>So, to answer the question how can operators choose the best data management strategy to ensure interworking with 4G while introducing new 5G services? 3GPP outlined a number of options for UDM-HSS interworking in their technical reports (TR 23.973; TR 23.732). Essentially, there are three main approaches that can be taken for efficient interworking to ensure that a 5G UDM can coexist with legacy subscriber data management systems. The three options assume that:</p><p>- UDM and HSS are separately deployed and the user data of 5G and 4G/3G/2G are also stored separately in different repositories (convergent HSS storing user data for 4G/3G/2G and IMS domains and 5G UDM/UDR storing user data for 5G domain).</p><p>- HSS is deployed using the UDC architecture: Most telecom operators have a SDM (subscriber data management) solution that acts as a convergent HSS/HLR.</p><h4>Option #1: UDM-HSS Interworking via SBA interface</h4><p>The first option that we will discuss is direct SBA UDM-HSS Interworking. A 3GPP standardized solution (3GPP TS 23.632) that ensures interworking via a new SBA (service-based architecture) interface. As shown in Figure 1, a new service based interface (SBI) will be added between HSS and UDM, to handle all interworking cases. Therefore, the existing HSS must be evolved to support the new SBA interface (upgrade of the HSS).</p><figure><img alt="Figure 1: Architecture for UDM-HSS Interworking via SBA interface" src="https://cdn-images-1.medium.com/max/488/1*IfeeOwGdII43iWpuXmfr7A.png" /><figcaption>Figure 1: Architecture for UDM-HSS Interworking via SBA interface</figcaption></figure><p>By specifying a new SBI interface, this first option supports all the procedures that have been defined on EPS and 5GS. It enables seamless interworking between 3G, 4G and 5G environments but requires changes to the legacy HSS.</p><h4>Option #2: UDM-HSS Interworking reusing legacy protocol</h4><p>To avoid the impact on legacy systems, 3GPP proposes a second option that uses Diameter interfaces already available in the HSS (Figure 2). In this approach, UDM is the only access point to 5GC, EPC and IMS and acts as a fake MME/CSCF/AS. All the interactions for retrieving or updating user data are <strong>initiated</strong> by UDM through reusing existing HSS supported protocol and procedures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*s_lDs9YF7o38mwW1GWgN7w.png" /><figcaption>Figure 2: UDM/HSS interworking reusing Legacy Protocols</figcaption></figure><p>This solution enables interworking without requiring any changes to the existing HSS. UDM acting as a gateway and sole access point to subscriber’s data, offers a smooth evolution towards shutting down the HSS. Because of the separation of the storage, this approach may causes the inconsistency between 5G service profile and 2G/3G/4G service profile of the same user.</p><h4>Option #3: UDM-HSS coexistence without Interworking</h4><p>This scenario proposes an alternative for coexistence between UDM and HSS by avoiding interworking between the two nodes. It ensures that the 2G/3G/4G/5G profiles of a user exist in the same UDR database through migrating the existing 2G/3G/4G data of 5G-enabled subscribers, thus avoiding interactions between “existing HSS” and “UDM”. To do so, 3GPP recommends deploying a combined HSS/UDM (Figure 3), supporting all interfaces and procedures specified for 5GC, EPC and IMS. The Combined network entity stores 2G/3G/4G/IMS/5G subscription data for 5G enabled users, so that the interactions between HSS and UDM within the Combined entity are performed internally and therefore it is not required to define such interworking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*75azksu7y8HOcEUnWZK9pg.png" /><figcaption>Figure 3: UDM-HSS coexistence without Interworking</figcaption></figure><p>This solution avoids any impact on existing nodes, services, protocols and interfaces; but require migration of subscriber data for existing users that enable 5G. It also needs to add route information for 5G users (in the STP/DRA) to send requests to either the Combined HSS/UDM for 5G enabled users or the existing HSS for 2G/3G/4G only users.</p><h4>What’s the best option?</h4><p>When evaluating options for interworking between UDM and HSS, it’s important to consider a few key points that are very important to operators; like data migration, impact on network, TTM and investments,… etc. The table below gives a brief comparison between the three options:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*fFh1dBYt1P3NxBwEkYg0DA.png" /><figcaption>Table 1: comparison of the three options</figcaption></figure><p>The evolution of user data from 4G to 5G has multiple paths, and each solution has its own Pros and Cons. As you can see from the table above, <strong>option 1 has the lowest score</strong> because of the impact on the existing HSS, and also not the best Investment direction for an operator. <strong>To avoid touching the legacy HSS, option 2</strong> is a good fit for operators that want the benefits of a new 5G core without changing the existing HSS and investing in it. In this approach, the UDM acts as a gateway and sole access point, offering a smooth evolution towards shutting down the HSS. It offers the fast 5G launch with a focus on pure 5G SA subscribers. The only negative point in my opinion is the separation of data storage for the same user, and the complexity that may bring (provisioning and data consistency). <strong>Compared with other solutions, option 3 is an excellent one.</strong> The combined UDM-HSS avoid interworking, thus keeping the existing HSS untouched. This scenario ensures data consistency by using a unified user profile, thus facilitating provisioning. This approach require migrating legacy subscription data and needs more investments at the start compared to option 2, but in terms of architecture/design it offers the opportunity to implement the target solution from day one.</p><p>3GPP has specified multiple flexible interworking options to support the transition to UDM systems but does not cover all possible solutions. The operator may select more flexible and optimized transition solutions out of TS 23.973 based on its actual conditions. The best strategy for subscriber data management needs to reconcile different systems and standards that have been applied to achieve a smooth migration to 5G. And operators need to select proper evolution solutions in accordance with their own network conditions and policies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b91dd2023bfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>