<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.178047.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Research Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Low-Latency Digital Health Framework for Rural Areas Leveraging Fog Computing and 5G</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 1 approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Acharya</surname>
                        <given-names>Manas Ranjan</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Resources</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Tripathy</surname>
                        <given-names>Sarita</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-7813-6328</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Pattnaik</surname>
                        <given-names>Prasant Kumar</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>School of Computer Science Engineering, Kalinga Institute of Industrial Technology, Bhubaneswar, Odisha, 751024, India</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:sarita.tripathyfcs@kiit.ac.in">sarita.tripathyfcs@kiit.ac.in</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>4</day>
                <month>5</month>
                <year>2026</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2026</year>
            </pub-date>
            <volume>15</volume>
            <elocation-id>661</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>26</day>
                    <month>3</month>
                    <year>2026</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2026 Acharya MR et al.</copyright-statement>
                <copyright-year>2026</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/15-661/pdf"/>
            <abstract>
                <sec>
                    <title>Background</title>
                    <p>The rural locations of telemedicine and urgent care are slowed down by communication latency as a result of the poor network infrastructure and overreliance on centralized cloud computing that adds to time lag in responding. Even with the development of networking technology, reliable low-latency systems to support rural areas are yet to be developed.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>The current paper suggests a Fog-5G Latency Optimization (F5GLO) application framework, which integrates 5G connectivity and fog computing to permit local data processing. To reduce the transmission delay and latency, healthcare data is stored at local fog nodes to allow predictive mobility of the fog node activation and low latency routing algorithms to utilize resources effectively and guarantee efficiency in transfer.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>The model is capable of cutting end to end latency by up to 87 percent in comparison to the conventional cloud-based models thereby enhancing critical healthcare applications such as remote patient monitoring and emergency medical services. It is also strong in various network traffic conditions.</p>
                </sec>
                <sec>
                    <title>Conclusions</title>
                    <p>Fog computing plus 5G networks introduce agility to the healthcare service delivery in the remote environment where quick processing of clinical data locally and transmission can improve the reliability of the given services by transmitting information to decision makers faster. This is a realistic incremental solution to the issue of healthcare provision to the populations that are not within reach of the giant facilities.</p>
                </sec>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Latency Reduction</kwd>
                <kwd>Rural Healthcare</kwd>
                <kwd>Fog Computing</kwd>
                <kwd>5G Networks</kwd>
                <kwd>Predictive Analytics</kwd>
                <kwd>Dynamic Routing</kwd>
                <kwd>Simulation</kwd>
                <kwd>Healthcare IoT</kwd>
                <kwd>Data Processing</kwd>
                <kwd>Ultra-Low Latency</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source>NA</funding-source>
                </award-group>
                <funding-statement>The author(s) declared that no grants were involved in supporting this work.</funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec5" sec-type="intro">
            <title>1. Introduction</title>
            <p>Health services have always been a major concern in the rural areas to provide appropriate treatment to the patients. The delays in the data transfer and processing may lead to adverse outcomes and, in particular, medical crises and crises that require immediate care. The process of processing real-time data and quick response systems are gaining relevance with the advancement of digital healthcare. This paper addresses the issue of latency in rural healthcare by examining a specific solution of 5G technology combined with fog computing. Healthcare systems latency does not solely influence patient monitoring and diagnosis, but also poses a critical effect on emergency response time that may save lives. Typical failure in rural areas results from the very long distance that data has to travel resulting in high latency when all processing takes place remotely due to cloud computing models. Here, fog computing provides a viable paradigm by separating computation nearer to the source of data hence reducing latency significantly (
                <xref ref-type="bibr" rid="ref21">Bonomi 
                    <italic toggle="yes">et al.</italic>, 2012</xref>). In addition to this, the advent of 5G technology introduces ultra-reliable low-latency communication (URLLC), which is very advantageous for real-time data transfer applications such as telemedicine, remote patient monitoring, and emergency medical services; these have shown how 5G can change healthcare by allowing services that were previously blocked because of network limitations (
                <xref ref-type="bibr" rid="ref17">Agiwal 
                    <italic toggle="yes">et al.</italic>, 2016</xref>, 
                <xref ref-type="bibr" rid="ref26">Gupta 
                    <italic toggle="yes">et al.</italic>, 2021</xref>). Insignificant study has been done on the mix of fog computing with 5G in rural healthcare settings. Most research have focused either on the possibilities of 5G in general healthcare benefits without special attention on latency in rural areas or on the advantages of fog computing for IoT in urban contexts (
                <xref ref-type="bibr" rid="ref24">Dastjerdi &amp; Buyya, 2016</xref>, 
                <xref ref-type="bibr" rid="ref31">Li 
                    <italic toggle="yes">et al.</italic>, 2019</xref>). This work aims to address this knowledge gap by proposing a method whereby mutual exploitation of both technologies helps to reduce rural healthcare latency.</p>
            <p>Geographic distance of rural areas sometimes results in limited resources for healthcare facilities, including network infrastructure. Local data processing by fog nodes placed close or at healthcare facilities can help to reduce the requirement for all data to be transported to far-off cloud centers (
                <xref ref-type="bibr" rid="ref40">Shi 
                    <italic toggle="yes">et al.</italic>, 2016</xref>). 5G networks provide a spine for this system with its lower latency and higher capacity. By allowing data to be transferred fast between local fog nodes and far-off cloud servers as needed, 5G can enable a hybrid paradigm whereby only necessary or complex data processing activities are escalated to the cloud (
                <xref ref-type="bibr" rid="ref38">Qin 
                    <italic toggle="yes">et al.</italic>, 2020</xref>, 
                <xref ref-type="bibr" rid="ref25">Goswami 
                    <italic toggle="yes">et al.</italic>, 2023</xref>). This model lowers latency and increases utilization of resources in places with limited network facilities.</p>
            <p>This study includes dynamic data routing and resource allocation prediction. These systems preload computing resources using real-time network measurements and projected demand patterns. Predictive models facilitate the anticipation of high-traffic or unforeseen events, enabling the system to manage increased data volumes without latency (
                <xref ref-type="bibr" rid="ref46">Zhang 
                    <italic toggle="yes">et al.</italic>, 2018</xref>, 
                <xref ref-type="bibr" rid="ref45">Zeng &amp; Li, 2023</xref>). Various researches showing the poor condition of rural healthcare emphasize the importance of this kind of research. This work combines the computational capability of fog nodes with the network capabilities of 5G using a system model. We provide and model dynamically managing data and resources approaches to ensure least delay delivery of healthcare services. Simulations measure the effect of our proposed methods on latency by means of a controlled environment, thereby evaluating various strategies. This approach complements the latency-aware task scheduling method and the load balancing simulation methods (
                <xref ref-type="bibr" rid="ref42">Wang &amp; Wang, 2019</xref>, 
                <xref ref-type="bibr" rid="ref28">Hong 
                    <italic toggle="yes">et al.</italic>, 2020</xref>). In this context, predictive analytics is hence rather crucial. Based on past information, our system can determine where and when to allocate resources, therefore guiding choices. This aligns with the findings of the use of machine learning in network management to optimize performance dynamically (
                <xref ref-type="bibr" rid="ref43">Wang &amp; Wu, 2020</xref>, 
                <xref ref-type="bibr" rid="ref34">Mahmud 
                    <italic toggle="yes">et al.</italic>, 2020</xref>). The integration of these technologies presents several challenges. Considerations must include data transfer security, energy efficiency, and the initial costs associated with developing 5G infrastructure in remote locations.</p>
            <p>There has been minor decrease in latency as a result of the use of 5G for remote healthcare in rural areas (
                <xref ref-type="bibr" rid="ref36">Patel 
                    <italic toggle="yes">et al.</italic>, 2022</xref>). Emphasize on exploiting 5G capabilities for efficient data processing in fog nodes have additional contributions with case studies on 5G-fog integration in remote places. Case studies that investigate the possibility of integrating 5G and fog computing in rural areas are included among the additional contributions (
                <xref ref-type="bibr" rid="ref23">Cheng &amp; Zhang, 2022</xref>, 
                <xref ref-type="bibr" rid="ref44">Xu &amp; Zhang, 2023</xref>, 
                <xref ref-type="bibr" rid="ref37">Pattnaik 
                    <italic toggle="yes">et al.</italic>, 2021</xref>). The influence of 5G on IoT healthcare applications and smart healthcare architectures underline the challenges of adopting fog computing in rural healthcare environments (
                <xref ref-type="bibr" rid="ref35">Park &amp; Choi, 2021</xref>, 
                <xref ref-type="bibr" rid="ref29">Hossain 
                    <italic toggle="yes">et al.</italic>, 2022</xref>).</p>
        </sec>
        <sec id="sec6">
            <title>2. The comprehensive theoretical basis and the proposed method</title>
            <p>Fog computing has developed into a required technology for lowest latency in the healthcare sector by means of localized data processing. Emphasizing its possibilities in IoT applications, notably in healthcare, by lowering reliance on remote cloud services for data processing, established the concept of fog computing (
                <xref ref-type="bibr" rid="ref21">Bonomi 
                    <italic toggle="yes">et al.</italic>, 2012</xref>). By enabling localized data management, fog computing might improve IoT potential in healthcare (
                <xref ref-type="bibr" rid="ref24">Dastjerdi &amp; Buyya, 2016</xref>). Using fog computing, which is an architecture for real-time analytics in healthcare IoT, the decision-making times is significantly reduced (
                <xref ref-type="bibr" rid="ref31">Li 
                    <italic toggle="yes">et al.</italic>, 2019</xref>). A taxonomy and survey of fog computing in healthcare, highlighting its use in several medical IoT environments have been discussed (
                <xref ref-type="bibr" rid="ref34">Mahmud 
                    <italic toggle="yes">et al.</italic>, 2020</xref>). Some important uses include heart tracking and helping old people (
                <xref ref-type="bibr" rid="ref22">Cao 
                    <italic toggle="yes">et al.</italic>, 2019</xref>, 
                <xref ref-type="bibr" rid="ref27">Hassan 
                    <italic toggle="yes">et al.</italic>, 2021</xref>). A complete study was done to show how fog computing is needed in emergency health care systems (
                <xref ref-type="bibr" rid="ref20">Bhatia 
                    <italic toggle="yes">et al.</italic>, 2020</xref>).</p>
            <sec id="sec7">
                <title>2.1. 5G and healthcare</title>
                <p>5G technology, with its low latency and high capacity, has transformed healthcare delivery, especially in distant areas. 5G wireless networks in healthcare to demonstrate their potential benefits has been extensively studied (
                    <xref ref-type="bibr" rid="ref17">Agiwal 
                        <italic toggle="yes">et al.</italic>, 2016</xref>). How 5G might assist rural healthcare with connectivity problems, opening the door to telemedicine and remote operations (
                    <xref ref-type="bibr" rid="ref26">Gupta 
                        <italic toggle="yes">et al.</italic>, 2021</xref>). 5G network slicing enables low-latency telemedicine, crucial for distant healthcare (
                    <xref ref-type="bibr" rid="ref38">Qin 
                        <italic toggle="yes">et al.</italic>, 2020</xref>).</p>
                <p>The impact of 5G technology on surgical and IoT healthcare applications have been investigated (
                    <xref ref-type="bibr" rid="ref35">Park &amp; Choi, 2021</xref>, 
                    <xref ref-type="bibr" rid="ref18">Ahmad 
                        <italic toggle="yes">et al.</italic>, 2022</xref>). A real-time 5G infrastructure designed for smart healthcare services was introduced (
                    <xref ref-type="bibr" rid="ref29">Hossain 
                        <italic toggle="yes">et al.</italic>, 2022</xref>). 5G technology enhances telehealth services in rural areas (
                    <xref ref-type="bibr" rid="ref36">Patel 
                        <italic toggle="yes">et al.</italic>, 2022</xref>).</p>
            </sec>
            <sec id="sec8">
                <title>2.2. Latency optimization techniques</title>
                <p>New approaches of considering latency improvement have emerged. Fog computing resource allocation with predictive analytics (
                    <xref ref-type="bibr" rid="ref46">Zhang 
                        <italic toggle="yes">et al.</italic>, 2018</xref>). Load balancing and task scheduling aiming at latency reduction in healthcare applications using certain methodologies have been studied (
                    <xref ref-type="bibr" rid="ref42">Wang &amp; Wang, 2019</xref>, 
                    <xref ref-type="bibr" rid="ref28">Hong 
                        <italic toggle="yes">et al.</italic>, 2020</xref>). A dynamic resource allocation technique was suggested that considers data urgency and hence helps to lower latency in Internet of Things enabled healthcare systems (
                    <xref ref-type="bibr" rid="ref39">Sharma &amp; Singh, 2022</xref>). A fog computing multi-objective optimization framework including cost, energy consumption, and delay was presented (
                    <xref ref-type="bibr" rid="ref32">Liu 
                        <italic toggle="yes">et al.</italic>, 2021</xref>).</p>
            </sec>
            <sec id="sec9">
                <title>2.3. Combining 5G with fog computing</title>
                <p>Despite being understudied, 5G and fog computing are increasingly gaining traction. 5G enhances healthcare fog computing by diminishing latency (
                    <xref ref-type="bibr" rid="ref30">Jiang 
                        <italic toggle="yes">et al.</italic>, 2021</xref>). Empirical studies executed to illustrate advancements in rural telehealth and remote monitoring (
                    <xref ref-type="bibr" rid="ref36">Patel 
                        <italic toggle="yes">et al.</italic>, 2022</xref>, 
                    <xref ref-type="bibr" rid="ref19">&#x00c1;lvarez 
                        <italic toggle="yes">et al.</italic>, 2023</xref>). Case study for demonstrating the functionality of integration in rural healthcare has been studied (
                    <xref ref-type="bibr" rid="ref44">Xu &amp; Zhang, 2023</xref>). The potential of 5G to enhance data processing in fog nodes for healthcare IoT applications was investigated (
                    <xref ref-type="bibr" rid="ref23">Cheng &amp; Zhang, 2022</xref>).</p>
            </sec>
            <sec id="sec10">
                <title>2.4. Energy efficiency and security</title>
                <p>A balance of security, energy economy, and latency is clearly necessary. There is provisions to lower energy consumption and latency in fog-5G systems, enabling their efficient running in rural locations with restricted power supplies (
                    <xref ref-type="bibr" rid="ref33">Liu 
                        <italic toggle="yes">et al.</italic>, 2023</xref>, 
                    <xref ref-type="bibr" rid="ref41">Tang &amp; Wang, 2022</xref>).</p>
            </sec>
            <sec id="sec11">
                <title>2.5 Gaps and future directions</title>
                <p>The papers demonstrate number of gaps in the current literature:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>There has been a lack of practical implementation and testing in rural locations.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>No overall models that deal with scalability, energy-efficiency, data security, and latency-reduction across all the dimensions are present.</p>
                        </list-item>
                    </list>
                </p>
                <p>More adaptive and foresight algorithms specific to the specific requirements of the healthcare domain are needed. Further research in this area should be conducted on actual applications of such integrated systems in the rural healthcare environment. It is found that there is an upsurge towards highly sophisticated forecasting models that can deal with emergencies and also deal with medical data. The role of bringing such high level technologies in the undeveloped regions in terms of the effects they have on society. Lastly, with the solution of the latency issues, integration of 5G and fog computing will immensely change the rural healthcare. The reviewed literature provides a good foundation on which additional improvements can be achieved to ensure that healthcare services provided in rural communities are not only as fast and efficient, but even more so. The formulation of the problem in mathematical terms is aimed at approaching the latency reduction in fog-5G-based rural healthcare.</p>
            </sec>
            <sec id="sec12">
                <title>2.6. Objective function</title>
                <p>This research project will primarily aim to minimize the latency in the overall case of the rural health system by streamlining the workload of data processing between the fog nodes and the cloud service, using 5G as a connectivity medium. The formulated objective function is: 
                    <italic toggle="yes">L
                        <sub>total</sub>=w
                        <sub>1</sub>.L
                        <sub>fog</sub>+w
                        <sub>2</sub>.L
                        <sub>cloud</sub>
                    </italic>
                </p>
                <p>Where:</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mtext mathvariant="italic">total</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> represents the total system latency.</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mi mathvariant="italic">fog</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> is the average latency for data processed by fog nodes.</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mtext mathvariant="italic">cloud</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> is the average latency for data processed by the cloud.</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula> are the weights representing the proportion of data processed by fog nodes and cloud, respectively, with the constraint: 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>+</mml:mo>
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                        </mml:math>
</inline-formula>
                </p>
            </sec>
            <sec id="sec13">
                <title>2.7 Mathematical formulations and calculations</title>
                <p>Let 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mi>n</mml:mi>
                        </mml:math>
</inline-formula> be the number of fog nodes (assumed to be 15), 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>d</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the distance from the IoT device to the nearest fog node, 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>t</mml:mi>
                                <mml:mrow>
                                    <mml:mtext mathvariant="italic">process</mml:mtext>
                                    <mml:mo>_</mml:mo>
                                    <mml:mi mathvariant="italic">fog</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the processing time at a fog node, assumed to be low due to localized processing, 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>t</mml:mi>
                                <mml:mrow>
                                    <mml:mn>5</mml:mn>
                                    <mml:mi>g</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the latency introduced by 5G communication (estimated to be between 1-10 ms).</p>
                <p>The fog node latency can be expressed as:
                    <disp-formula id="e1">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mi mathvariant="italic">fog</mml:mi>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mn>1</mml:mn>
                                <mml:mi>N</mml:mi>
                            </mml:mfrac>
                            <mml:munderover>
                                <mml:mo>&#x2211;</mml:mo>
                                <mml:mrow>
                                    <mml:mi>i</mml:mi>
                                    <mml:mo>=</mml:mo>
                                    <mml:mn>1</mml:mn>
                                </mml:mrow>
                                <mml:mi>N</mml:mi>
                            </mml:munderover>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:msub>
                                    <mml:mi>t</mml:mi>
                                    <mml:mrow>
                                        <mml:mtext mathvariant="italic">process</mml:mtext>
                                        <mml:mo>_</mml:mo>
                                        <mml:mi mathvariant="italic">fog</mml:mi>
                                    </mml:mrow>
                                </mml:msub>
                                <mml:mo>+</mml:mo>
                                <mml:msub>
                                    <mml:mi>t</mml:mi>
                                    <mml:mrow>
                                        <mml:mn>5</mml:mn>
                                        <mml:mi>g</mml:mi>
                                    </mml:mrow>
                                </mml:msub>
                                <mml:mo>+</mml:mo>
                                <mml:mfrac>
                                    <mml:msub>
                                        <mml:mi>d</mml:mi>
                                        <mml:mi>i</mml:mi>
                                    </mml:msub>
                                    <mml:msub>
                                        <mml:mi>C</mml:mi>
                                        <mml:mrow>
                                            <mml:mn>5</mml:mn>
                                            <mml:mi>g</mml:mi>
                                        </mml:mrow>
                                    </mml:msub>
                                </mml:mfrac>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                        </mml:math>
</disp-formula>
                </p>
                <p>Where:</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>C</mml:mi>
                                <mml:mrow>
                                    <mml:mn>5</mml:mn>
                                    <mml:mi>g</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
</inline-formula>is the speed of 5G signal.</p>
                <p>

                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mi>N</mml:mi>
                        </mml:math>
</inline-formula> is the total number of IoT devices (assumed to be 1000).</p>
                <p>Let 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mi>D</mml:mi>
                        </mml:math>
</inline-formula> be the distance from the rural area to the cloud server (significantly larger than 
                    <bold>d</bold>
                    <sub>

                        <bold>i</bold>
                    </sub>), 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>t</mml:mi>
                                <mml:mrow>
                                    <mml:mtext mathvariant="italic">process</mml:mtext>
                                    <mml:mo>_</mml:mo>
                                    <mml:mi mathvariant="italic">fog</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                            <mml:mspace width="0.25em"/>
                        </mml:math>
</inline-formula>be the processing time in the cloud, which is higher due to centralized computing and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>t</mml:mi>
                                <mml:mtext mathvariant="italic">network</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the latency due to traditional network connectivity to the cloud (assumed to be around 100 ms).</p>
                <p>The cloud latency can be expressed as
                    <bold>:</bold>

                    <disp-formula id="e2">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi mathvariant="bold-italic">L</mml:mi>
                                <mml:mtext mathvariant="bold-italic">cloud</mml:mtext>
                            </mml:msub>
                            <mml:mo mathvariant="bold-italic">=</mml:mo>
                            <mml:msub>
                                <mml:mi mathvariant="bold-italic">t</mml:mi>
                                <mml:mrow>
                                    <mml:mtext mathvariant="bold-italic">process</mml:mtext>
                                    <mml:mo>_</mml:mo>
                                    <mml:mtext mathvariant="bold-italic">cloud</mml:mtext>
                                </mml:mrow>
                            </mml:msub>
                            <mml:mo mathvariant="bold-italic">+</mml:mo>
                            <mml:msub>
                                <mml:mi mathvariant="bold-italic">t</mml:mi>
                                <mml:mtext mathvariant="bold-italic">network</mml:mtext>
                            </mml:msub>
                            <mml:mo mathvariant="bold-italic">+</mml:mo>
                            <mml:mn mathvariant="bold">2</mml:mn>
                            <mml:mfrac>
                                <mml:mi mathvariant="bold-italic">D</mml:mi>
                                <mml:msub>
                                    <mml:mi mathvariant="bold-italic">C</mml:mi>
                                    <mml:mtext mathvariant="bold-italic">internet</mml:mtext>
                                </mml:msub>
                            </mml:mfrac>
                        </mml:math>
</disp-formula>
                </p>
                <p>Where:&#x00a0;
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="bold-italic">C</mml:mi>
                                <mml:mtext mathvariant="bold-italic">internet</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> represents the average internet speed.</p>
            </sec>
            <sec id="sec14">
                <title>2.8 Constraints</title>
                <p>

                    <bold>2.8.1 Data Urgency Constraint</bold>
                </p>
                <p>Each data packet is assigned an urgency level 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>u</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mspace width="0.25em"/>
                        </mml:math>
</inline-formula>(ranging from 1 to 10). Critical data (where 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>u</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>&gt;</mml:mo>
                            <mml:mn>5</mml:mn>
                        </mml:math>
</inline-formula>) must have latency below 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mtext mathvariant="italic">threshold</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula>(20 ms).</p>
                <p>The constraint is: 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mo>&#x2200;</mml:mo>
                            <mml:mi>i</mml:mi>
                            <mml:mo>,</mml:mo>
                        </mml:math>
</inline-formula> where 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>u</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>&gt;</mml:mo>
                            <mml:mn>5</mml:mn>
                        </mml:math>
</inline-formula>
                    <sub>,</sub>
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mo>&#x2264;</mml:mo>
                        </mml:math>
</inline-formula> 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>L</mml:mi>
                                <mml:mtext mathvariant="italic">threshold</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula>
                </p>
                <p>

                    <bold>2.8.2 Resource Utilization Constraints</bold>
                </p>
                <p>Let 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>R</mml:mi>
                                <mml:mi mathvariant="italic">fog</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the total processing resource available at fog nodes, 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>R</mml:mi>
                                <mml:mtext mathvariant="italic">cloud</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the total processing resource available in the cloud and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>R</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the resource requirement for processing data packet i.</p>
                <p>The constraints are:
                    <disp-formula id="e3">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>.</mml:mo>
                            <mml:munderover>
                                <mml:mo>&#x2211;</mml:mo>
                                <mml:mrow>
                                    <mml:mi>i</mml:mi>
                                    <mml:mo>=</mml:mo>
                                    <mml:mn>0</mml:mn>
                                </mml:mrow>
                                <mml:mi>N</mml:mi>
                            </mml:munderover>
                            <mml:msub>
                                <mml:mi>r</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:msub>
                                <mml:mi>R</mml:mi>
                                <mml:mi mathvariant="italic">fog</mml:mi>
                            </mml:msub>
                        </mml:math>
</disp-formula>
                </p>
                <p>

                    <bold>2.8.3 Bandwidth Constraints</bold>
                </p>
                <p>Let 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>B</mml:mi>
                                <mml:mrow>
                                    <mml:mn>5</mml:mn>
                                    <mml:mi>G</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the total bandwidth available for 5G channels (assumed to be 12 channels).</p>
                <p>Let 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>B</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> be the bandwidth requirement for transmitting data packet i.</p>
                <p>The constraints are:
                    <disp-formula id="e4">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>.</mml:mo>
                            <mml:munderover>
                                <mml:mo>&#x2211;</mml:mo>
                                <mml:mrow>
                                    <mml:mi>i</mml:mi>
                                    <mml:mo>=</mml:mo>
                                    <mml:mn>0</mml:mn>
                                </mml:mrow>
                                <mml:mi>N</mml:mi>
                            </mml:munderover>
                            <mml:msub>
                                <mml:mi>b</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:msub>
                                <mml:mi>B</mml:mi>
                                <mml:mrow>
                                    <mml:mn>5</mml:mn>
                                    <mml:mi>G</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
</disp-formula>
                </p>
                <p>For cloud communication, traditional internet bandwidth (
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>B</mml:mi>
                                <mml:mtext mathvariant="italic">internet</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula>

                    <bold>)</bold> should also be considered, but with 5G connectivity, it is not a significant constraint.
                    <disp-formula id="e5">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>+</mml:mo>
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>,</mml:mo>
                            <mml:mn>0</mml:mn>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:msub>
                                <mml:mi>W</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>,</mml:mo>
                            <mml:mn>0</mml:mn>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:mi>W</mml:mi>
                            <mml:mn>2</mml:mn>
                            <mml:mo>&#x2264;</mml:mo>
                            <mml:mn>1</mml:mn>
                        </mml:math>
</disp-formula>
                </p>
                <p>By considering the important character of healthcare data, the available computational resources, and the real-time conditions of the network, this problem formulation aims to optimize latency so enabling the system to respond to the changing needs of healthcare in rural areas.</p>
            </sec>
            <sec id="sec15">
                <title>2.9 Proposed algorithms</title>
                <p>The details of the proposed algorithms are summarized in 
                    <xref ref-type="table" rid="T1">
Table 1</xref>.</p>
                <table-wrap id="T1" orientation="portrait" position="float">
                    <label>
Table 1. </label>
                    <caption>
                        <title>Proposed algorithms for F5GLO.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Algorithm name</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Description</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Key features</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Predictive Resource Allocation (PRA)</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Dynamically allocates computational resources based on predicted healthcare demands.</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Uses machine learning to predict patient data volume, urgency, and network load. Adjusts resources per prediction.</td>
                            </tr>
                            <tr>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Latency-Aware Dynamic Routing (LADR)</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Routes data through the network path with the lowest latency.</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Considers current network conditions, device urgency, and available resources. Optimizes for real-time processing.</td>
                            </tr>
                            <tr>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Adaptive Network Slicing (ANS)</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Configures 5G network slices for optimal performance based on data type and urgency.</td>
                                <td align="justify" colspan="1" rowspan="1" valign="middle">Gives top priority to essential healthcare information, guaranteeing quick response times even when the network is busy.</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>

                    <bold>2.9.1 PRA Algorithm Outline:</bold> The proposed Predictive Resource Allocation (PRA) method is presented in 
                    <xref ref-type="boxed-text" rid="B1">Algorithm 1</xref>, which dynamically allocates network resources based on predicted demand and current consumption patterns.
                    <list list-type="bullet">
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Input:</bold> The present status of the network, previous data consumption, priority of patient information, Historical (H): 10000 runs, Existing Need: D
                                <sub>c</sub>, Time Frame (W): last 1000 runs</p>
                        </list-item>
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Output:</bold> Allocated Resources: R
                                <sub>a</sub>
                            </p>
                        </list-item>
                    </list>
                </p>
                <boxed-text id="B1" orientation="portrait" position="float">
                    <label>Algorithm 1. </label>
                    <caption>
                        <title>Predictive Resource Allocation (PRA).</title>
                    </caption>
                    <p>

                        <bold>Input: H, DC, W</bold>
                    </p>
                    <p>

                        <bold>Output: Ra</bold>
                    </p>
                    <p>

                        <bold>Step 1: Predict future demand using H over W</bold>
                    </p>
                    <p>

                        <bold>Step 2: Calculate</bold>
                    </p>
                    <p>

                        <bold>DR=Dp/Dc</bold>
                    </p>
                    <p>

                        <bold>where</bold>
                    </p>
                    <p>

                        <bold>Dp</bold>
                    </p>
                    <p>

                        <bold>is PredictedFutureDemand</bold>
                    </p>
                    <p>

                        <bold>Step 3: If</bold>
                    </p>
                    <p>

                        <bold>DR &gt; 1.2</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>Ra= Dc &#x00d7; 1.2</bold>
                    </p>
                    <p>

                        <bold>end of If</bold>
                    </p>
                    <p>

                        <bold>Step 4: Else If</bold>
                    </p>
                    <p>

                        <bold>DR&lt;0.8</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>Ra = Dc &#x00d7; 0.8</bold>
                    </p>
                    <p>

                        <bold>end of Else If</bold>
                    </p>
                    <p>

                        <bold>Step 5: Else</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>Ra = Dc</bold>
                    </p>
                    <p>

                        <bold>end of Else</bold>
                    </p>
                    <p>

                        <bold>Step 6: Ensure minimum resources (</bold>
                    </p>
                    <p>

                        <bold>Ra =max</bold> 
                        <inline-formula>

                            <mml:math display="inline">
                                <mml:msub>
                                    <mml:mi mathvariant="bold-italic">f</mml:mi>
                                    <mml:mn mathvariant="bold">0</mml:mn>
                                </mml:msub>
                            </mml:math>
</inline-formula> 

                        <bold>(Ra,0.5&#x00d7;Dc)</bold>
                    </p>
                    <p>

                        <bold>)</bold>
                    </p>
                    <p>

                        <bold>Step 7: Cap maximum resources (</bold>
                    </p>
                    <p>

                        <bold>Ra=min</bold> 
                        <inline-formula>

                            <mml:math display="inline">
                                <mml:msub>
                                    <mml:mi mathvariant="bold-italic">f</mml:mi>
                                    <mml:mn mathvariant="bold">0</mml:mn>
                                </mml:msub>
                            </mml:math>
</inline-formula> 

                        <bold>(Ra,2&#x00d7;Dc)</bold>
                    </p>
                    <p>

                        <bold>)</bold>
                    </p>
                    <p>

                        <bold>Step 8: Stop</bold>
                    </p>
                </boxed-text>
                <p>

                    <bold>2.9.2 LADR Algorithm Outline:</bold> The detailed procedure of the Latency-Aware Dynamic Routing (LADR) mechanism used to select the optimal routing path based on latency constraints is demonstrated in 
                    <xref ref-type="boxed-text" rid="B2">Algorithm 2</xref>.
                    <list list-type="bullet">
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Input (&#x039b;: LatencyMap, 15 fog nodes, 12 5G channels):</bold> Data urgency, current network latency, fog node status.</p>
                        </list-item>
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Output (Ps: Selected Path):</bold> Best path for data packet (fog node or cloud)</p>
                        </list-item>
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Process:</bold> Assess latency for each possible route, choose the path with minimal delay.</p>
                        </list-item>
                    </list>
                </p>
                <boxed-text id="B2" orientation="portrait" position="float">
                    <label>Algorithm 2. </label>
                    <caption>
                        <title>Latency-Aware Dynamic Routing (LADR).</title>
                    </caption>
                    <p>

                        <bold>Step 1: Initialize</bold>
                    </p>
                    <p>

                        <bold>L</bold>
                        <sub>

                            <bold>min</bold>
                        </sub>
                    </p>
                    <p>

                        <bold>to 20 ms (latency threshold) and</bold>
                    </p>
                    <p>

                        <bold>P</bold>
                        <sub>

                            <bold>s</bold>
                        </sub>
                    </p>
                    <p>

                        <bold>to null</bold>
                    </p>
                    <p>

                        <bold>Step 2: For each P in</bold>
                    </p>
                    <p>

                        <bold>&#x039b;</bold>
                    </p>
                    <p>

                        <bold>do</bold>
                    </p>
                    <p>

                        <bold>Step 3: If</bold>
                    </p>
                    <p>

                        <bold>&#x039b;[P]&lt;L</bold>
                        <sub>

                            <bold>min</bold>
                        </sub>
                    </p>
                    <p>

                        <bold>and</bold>
                    </p>
                    <p>

                        <bold>&#x03f5;&#x2264;(10&#x2212;&#x039b;[P]/10)</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>L</bold>
                        <sub>

                            <bold>min</bold>
                        </sub> 
                        <bold>= &#x039b;[P]</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>P</bold>
                        <sub>

                            <bold>s</bold>
                        </sub> 
                        <bold>= P</bold>
                    </p>
                    <p>

                        <bold>end of If</bold>
                    </p>
                    <p>

                        <bold>end of For</bold>
                    </p>
                    <p>

                        <bold>Step 4: Stop</bold>
                    </p>
                </boxed-text>
                <p>

                    <bold>2.9.3 ANS Algorithm Outline:</bold> The procedure for the proposed Adaptive Network Slicing (ANS) mechanism, which dynamically assigns network slices based on system load and priority requirements, is shown in 
                    <xref ref-type="boxed-text" rid="B3">Algorithm 3</xref>.
                    <list list-type="bullet">
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Input:</bold> &#x03f5;: (DataUrgency, 1 to 10), &#x03d5;: (CurrentNetworkLoad, 0 to 1, Data packet characteristics, network load.</p>
                        </list-item>
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Output</bold> (S: NetworkSlice): Slice configuration for the packet.</p>
                        </list-item>
                        <list-item>
                            <label>-</label>
                            <p>

                                <bold>Process:</bold> Dynamically adjust slice parameters to match data urgency and network conditions.</p>
                        </list-item>
                    </list>
                </p>
                <boxed-text id="B3" orientation="portrait" position="float">
                    <label>Algorithm 3. </label>
                    <caption>
                        <title>Adaptive Network Slicing (ANS).</title>
                    </caption>
                    <p>

                        <bold>Step 1: If</bold>
                    </p>
                    <p>

                        <bold>&#x03f5; &gt; 8</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>S = &#x2019;HighPriority&#x2019;</bold>
                    </p>
                    <p>

                        <bold>end of If</bold>
                    </p>
                    <p>

                        <bold>Step 2: Else If</bold>
                    </p>
                    <p>

                        <bold>&#x03a6; &gt; 0.7</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>S = &#x2019;MediumPriority&#x2019;</bold>
                    </p>
                    <p>

                        <bold>end of Else If</bold>
                    </p>
                    <p>

                        <bold>Step 3: Else</bold>
                    </p>
                    <p>

                        <bold>-</bold>
                    </p>
                    <p>

                        <bold>S = &#x2019;LowPriority&#x2019;</bold>
                    </p>
                    <p>

                        <bold>end of Else</bold>
                    </p>
                    <p>

                        <bold>Step 4: Stop</bold>
                    </p>
                </boxed-text>
                <p>The flowchart shows the data handling technique of the suggested system model. Healthcare IoT devices begin the process with data collecting; classification and forwarding to a fog node for urgency evaluation follows. Depending on urgency, we either send data to the cloud over a 5G network for additional processing or handle data locally. Choosing where to handle the data considers dynamically both local and cloud processing options. Once processing is finished, the data is restored into the system for dynamic changes and system flexibility to maximize it once more. Seeking to lower delay in rural health systems, this flowchart effectively shows data flow and decision-making process. The detailed data handling mechanism and processing architecture of the proposed system are illustrated in 
                    <xref ref-type="fig" rid="f1">
Figure 1</xref>.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>
Figure 1. </label>
                    <caption>
                        <title>Flowchart of the data handling technique of the suggested system model, illustrating the data flow and decision-making process for latency reduction in rural healthcare systems.</title>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure1.gif"/>
                </fig>
            </sec>
        </sec>
        <sec id="sec16" sec-type="methods">
            <title>3. Method</title>
            <p>In order to minimize latency, the F5GLO model utilizes a multi-tier architecture that dynamically processes information based on urgent, available resources and network conditions. The architecture includes three layers: Cloud Layer that uses 5G to cover the area; Fog Layer that provides local processing to reduce the latency and End Devices tier that includes healthcare devices and other end-user gadgets. It also needs transmission delays in the transmission of data by grouping the nodes of the fog in close proximity to the end devices thus ensuring that the end devices in the rural locations transmit the most important health information with the minimum lag. In this method, computing capabilities are transferred nearer to the sources of data, which is the feature of 5G that is based on the concept of fog computing and the ability to provide high speed and low latency. 
                <xref ref-type="fig" rid="f2">
Figure 2</xref> presents the architectural framework of the F5GLO model, highlighting the cloud, fog, and end-device layers.</p>
            <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                <label>
Figure 2. </label>
                <caption>
                    <title>Architectural framework of the F5GLO model, highlighting the cloud, fog, and end-device layers.</title>
                </caption>
                <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure2.gif"/>
            </fig>
            <p>

                <bold>Simulation Parameters:</bold>
            </p>
            <p>Number of IoT Devices: 1000, Number of Fog Nodes: 15, Number of 5G Channels: 12,</p>
            <p>Data Packets: 10,000</p>
            <p>Max Latency for Cloud: 100 ms, Latency Threshold: 20 ms (for critical data),</p>
            <p>Simulation Iterations: 10000</p>
            <p>

                <bold>Data Urgency:</bold> Randomly assigned between 1 to 10, with higher numbers indicating</p>
            <p>greater urgency.</p>
            <sec id="sec17">
                <title>3.1 Performance analysis</title>
                <p>
The F5GLO is used in this section to compare the results of the simulation of Local Server Model and Traditional Cloud Model. F5GLO proves its ability to significantly decrease the response time, with the maximum decrease of latency up to 87%. F5GLO is also characterized by a better energy efficiency and high throughput in addition to relying on more powerful technology, such as fog computing and 5G technology, to improve the performance of the rural health system.</p>
            </sec>
            <sec id="sec18">
                <title>3.2 Latency analysis:</title>
                <p>

                    <bold>3.2.1 Average Latency:</bold> The F5GLO technology demonstrates the 87 percent enhancement of the conventional cloud computing and dropping of the latency by 13 milliseconds. The mean latency of Local Server Model is 40 milliseconds and this is not as low in terms of latency reduction as F5GLO can provide when used in combination with 5G to process data locally. Conversely, the Traditional Cloud Model that is based on remote data processing has the highest average of 100 milliseconds of latency out of the three models. The comparison shows that F5GLO has significantly enhanced the responsiveness and latency of the rural health system. As shown in 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref>, the F5GLO model achieves significantly lower latency compared to the Local Server and Traditional Cloud models.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>
Figure 3. </label>
                    <caption>
                        <title>Average and maximum latency comparison across the F5GLO, Local Server, and Traditional Cloud models.</title>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure3.gif"/>
                </fig>
                <p>

                    <bold>3.2.2 Peak Load Handling:</bold> Local Server Model is better than the cloud-based technique, but latencies of 80 ms to the peaks suggests local processing limitations without integration to 5G. This demonstration indicates the difficulty in maintaining minimal delays in the situation when the demand on the service is growing. Traditional Cloud Model has the highest delay of 150 milliseconds due to use of centralized processing. By using the peak load management tool provided by F5GLO, rural healthcare centres will become more efficient and can be better equipped to deal with emergencies. 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref> presents the comparison of peak load latency across the F5GLO, Local Server, and Traditional Cloud models.</p>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>
Figure 4. </label>
                    <caption>
                        <title>Peak load handling: Maximum latency comparison across the F5GLO, Local Server, and Traditional Cloud models.</title>
                    </caption>
                    <graphic id="gr4" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure4.gif"/>
                </fig>
                <p>

                    <bold>3.2.3 Latency Distribution:</bold> The results of the assessment have shown that the F5GLO model now whirs along with significantly faster speed of about 19.5 ms lag on average, compared to 120 ms, which was about 87% reduced. It retains its low-latency appeal even with the heavy load, and works in a variety of situations. The latency distribution is skewed to the left with approximately 90% of data packets received in less than 20 ms. The Local Server Model is faster than the Traditional Cloud Model but lagged behind F5GLO; nevertheless, the former is significantly faster than cloud-only solutions. In this configuration 90 percent of the packets arrive within 40 ms, and only a handful of them go after 80 ms. The delays in the Traditional Cloud Model skyrocket because of transmission and processing requests: approximately 90 percent of packets end up having an average delay of approximately 100 ms (maximum delay is approximately 150 ms). The latency distribution across the evaluated models is summarized in 
                    <xref ref-type="table" rid="T2">
Table 2</xref> and illustrated in 
                    <xref ref-type="fig" rid="f5">
Figure 5</xref>.</p>
                <table-wrap id="T2" orientation="portrait" position="float">
                    <label>
Table 2. </label>
                    <caption>
                        <title>Latency metrics.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Scenario</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Average latency (ms)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Max latency (ms)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Latency distribution</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">F5GLO Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">13</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">30</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">90% &lt; 20ms, 10% up to 30ms</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Local Server Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">40</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">80</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">90% &lt; 40ms, 10% up to 80ms</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Traditional Cloud Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">100</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">150</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">90% = 100ms, 10% up to 150ms</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>
Figure 5. </label>
                    <caption>
                        <title>Latency distribution: Comparison of models (F5GLO, Local Server, and Traditional Cloud).</title>
                    </caption>
                    <graphic id="gr5" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure5.gif"/>
                </fig>
                <p>

                    <bold>3.2.4 Average Throughput:</bold> F5GLO framework is more effective by having the average of approximately 0.077 packets/ms or 77 packets/s. This is the enhanced performance of the fog processing and high-speed 5G connections that reduce delays and accelerate the processing of data. F5GLO performs even better when we consider the latency and throughput jointly. F5GLO has lower latency and higher throughput, increasing the efficiency of data processing. The Local Server Model reduces the distance between source and processor, averaging approximately 0.050 packets/milliseconds and it is faster than pure cloud setups, yet, still, not faster than F5GLO. The Traditional Cloud Model reduces to a rate of approximately 0.010 packets per millisecond due to centralized processing and transmission latencies and creates higher latency as well. Distributed architecture of F5GLO, which has localized decision-making, maintains throughput approximately eight times compared to the conventional cloud solutions. This near combination of low latency and high throughput indicates F5GLO will provide a good solution to data-intensive healthcare applications where quick delivery is important and latency is a significant limitation. The throughput characteristics of the proposed and existing models are depicted in 
                    <xref ref-type="fig" rid="f6">
Figure 6</xref>.</p>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>
Figure 6. </label>
                    <caption>
                        <title>Throughput analysis of the proposed and existing models.</title>
                    </caption>
                    <graphic id="gr6" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure6.gif"/>
                </fig>
                <p>

                    <bold>3.2.5 Resource Utilization:</bold> The F5GLO model has a peak throughput of 0.100 packets/ms, which is more than the Local Server Model and Traditional Cloud Model at 0.075 packets/ms and 0.015 packets/ms respectively. Such throughput capacity maximum highlights the scalability of F5GLO and its ability to handle great data volumes in order to provide a timely response in the healthcare process. Implementation of mist nodes to process in F5GLO lessens the workload on the cloud and therefore enhances the ability to perform more activities or functions in this system. ANS technique enhances the use of bandwidth, thus, the throughput is increased and resources are used more efficiently in every model. 
                    <xref ref-type="fig" rid="f7">
Figure 7</xref> and 
                    <xref ref-type="table" rid="T3">
Table 3</xref> present the comparison of resource utilization across the F5GLO, Local Server, and Traditional Cloud models.</p>
                <fig fig-type="figure" id="f7" orientation="portrait" position="float">
                    <label>
Figure 7. </label>
                    <caption>
                        <title>Resource utilization comparison across the F5GLO, Local Server, and Traditional Cloud models.</title>
                    </caption>
                    <graphic id="gr7" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure7.gif"/>
                </fig>
                <table-wrap id="T3" orientation="portrait" position="float">
                    <label>
Table 3. </label>
                    <caption>
                        <title>Throughput metrics.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Scenario</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Average throughput (packets/ms)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Max throughput (packets/ms)</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">F5GLO</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.077</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.100</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Local Server Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.050</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.075</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Traditional Cloud Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.010</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.015</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
            <sec id="sec19">
                <title>3.3 Energy efficiency</title>
                <p>

                    <bold>3.3.1 Average Energy Use:</bold> F5GLO system consumes approximately 3.5 energy units per packet, hence it is more energy efficient in comparison to the Local Server Model and the Traditional Cloud Model. Local Server Model has a speed of approximately 4.0 units per packet. It is facilitating local processing yet consumes more power because there is poor data management in the 5G network. The Traditional Cloud Model consumes approximately 5.0 units per packet, the most energy consuming since processing occurs in remote data centers and data transfers require more power. F5GLO involves processing over fog nodes, and this implies that fewer data are transmitted to the cloud. This reduces the volume of information transmission, hence, improving energy efficiency and reducing latency. The simulation outcomes clearly show such benefits in efficiency and prove that F5GLO is more efficient in terms of managing energy consumption than the rest.</p>
                <p>

                    <bold>3.3.2 Energy vs. Latency Trade-off:</bold> The F5GLO model is also able to keep low power consumption in intense workload or when dealing with data streams of large volume. Using 7.0 energy units per packet, the F5GLO model will be used at peak throughput. Even though the incorporation of local processing, indeed makes the energy consumption higher, particularly, as the existing 5G networks are not optimized regarding energy efficiency, its consumption remains significantly lower than the one of the Local Server Model, which consumes approximately 10.0 units per packet under the same conditions. F5GLO is considered to be compatible with adaptive control. It also tries to balance the speed and energy usage with a better distribution of resources. The energy saving will be dependent on the location of the fog nodes and the distribution of the workload, and this can vary in various configurations. However, local data processing with the help of the fog nodes will always reduce additional data transmissions. This provides F5GLO with an improved trade-off between latency and energy consumption. Such a trade-off is essential in rural healthcare since timely and accurate information has to be deployed with careful power management, although the two tend to be conflicting ultimately. The energy&#x2013;latency trade-off among the evaluated models is summarized in 
                    <xref ref-type="table" rid="T4">
Table 4</xref>.</p>
                <table-wrap id="T4" orientation="portrait" position="float">
                    <label>
Table 4. </label>
                    <caption>
                        <title>Energy vs latency trade-off.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Model</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Max energy consumption (Units/packet)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Energy Vs. latency trade-off
</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">F5GLO</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">7.0</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.100</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Local Server Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">10.0</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.075</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Traditional Cloud Model</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">15.0</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.015</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
        </sec>
        <sec id="sec20" sec-type="results|discussion">
            <title>4. Results and discussion</title>
            <p>The highlighted simulation shows that healthcare service delivery in rural locations can be improved by minimizing latency via the incorporation of fog computing into the 5G technology. This report gives an observation and implications of the three models.</p>
            <sec id="sec21">
                <title>4.1 Latency reduction</title>
                <p>The outcomes of the simulation have shown that the reduction of latencies through the use of 5G of the network and the implementation of fog computing can enhance the healthcare services delivery to rural locations. In this paper, the discussion, observation, and implication in the three models are discussed. Since F5GLO paradigm cuts down the latency by 87 percent on the Local Server paradigm and the Traditional Cloud Model.</p>
            </sec>
            <sec id="sec22">
                <title>4.2 Scalability</title>
                <p>The F5GLO design has a process called Predictive Resource Allocation (PRA) that enables resource allocation on the basis of predictions. It implies that even a scaling up does not require the introduction of any latency, which is essential when more devices or patients are introduced into the system. Local Server Model can be scaled because it can process data locally but lacks dynamic resource management in comparison with F5GLO. Whereas the Traditional Cloud Model is capable of scaling up its data processing capabilities, it tends to increase its latency as it scales and demonstrates that this model cannot be used in dynamic and latency-sensitive settings such as healthcare. The scalability characteristics of the proposed and existing models are depicted in 
                    <xref ref-type="fig" rid="f8">
Figure 8</xref>.</p>
                <fig fig-type="figure" id="f8" orientation="portrait" position="float">
                    <label>
Figure 8. </label>
                    <caption>
                        <title>PRA-allocated resources over time, demonstrating the scalability characteristics of the proposed and existing models.</title>
                    </caption>
                    <graphic id="gr8" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure8.gif"/>
                </fig>
            </sec>
            <sec id="sec23">
                <title>4.3 Throughput improvement</title>
                <p>The increased throughput also suggests that the system will be able to handle additional data or additional patients at the same time at the expense of the timeliness of service, therefore, ideal in scenarios such as mass casualty situations in rural environments where resources are typically scarce.</p>
            </sec>
            <sec id="sec24">
                <title>4.4 Energy considerations</title>
                <p>Although we aimed not only to reduce latency, but also to make our method energy efficient, it is another benefit level, especially in those regions where power costs may be sporadic or expensive. Latency and energy optimization Twin optimization is the full design of the F5GLO system.</p>
            </sec>
            <sec id="sec25">
                <title>4.5 Network slicing impact</title>
                <p>ANS algorithm is capable of reducing emergency data delay and maintaining network performance to other services by creating network slices according to the urgency of data. This makes sure that it transmits important healthcare information with utmost urgency. The influence of network slicing on latency and service prioritization is depicted in 
                    <xref ref-type="fig" rid="f9">
Figure 9</xref>.</p>
                <fig fig-type="figure" id="f9" orientation="portrait" position="float">
                    <label>
Figure 9. </label>
                    <caption>
                        <title>ANS-network slice selection, showing the influence of network slicing on latency and service prioritization.</title>
                    </caption>
                    <graphic id="gr9" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/196385/bbd6361d-45c9-43ef-b6de-5ec9620afa32_figure9.gif"/>
                </fig>
            </sec>
        </sec>
        <sec id="sec26">
            <title>5. Conclusion and future work</title>
            <p>The Fog-5G F5GLO model improves the problem of latency, as it incorporates fog computing in 5G infrastructure to lower the end-to-end latency of the rural healthcare systems. It makes use of the synergy between 5G low-latency and localized processing of data in fog nodes. To the best of simulation results, this technique can potentially lessen the latency by as much as 87 percent thereby enhancing the response time of remote telehealth services. The technology is aimed at closing the digital healthcare gap and can be useful in particular cases with patients in critical conditions. Peak demand, throughput enhancement, and energy reduction can be handled by localized processing at the 5G network with the help of intelligent routing of data across the network and in the fog nodes. The dynamic network slicing adaptation algorithms, resource usage prediction and low-latency path selection can be used to respond to the changing needs in healthcare by prioritizing the urgent data and ensuring that the system does not fail.</p>
            <p>Future efforts should prioritize field testing and validation of the F5GLO model in rural environments to prove the benefits observed through simulation. These real studies would try to fully use the F5GLO idea, moving rural healthcare systems toward faster and better medical responses.</p>
        </sec>
        <sec id="sec27">
            <title>Ethics and consent</title>
            <p>Ethical approval was not required for this research work.</p>
        </sec>
    </body>
    <back>
        <sec id="sec30" sec-type="data-availability">
            <title>Data availability statement</title>
            <p>

                <list list-type="order">
                    <list-item>
                        <label>1.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Table 1.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31287748.v1">https://doi.org/10.6084/m9.figshare.31287748.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref13">Acharya et al. 2026m</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Table 1.docx (Table 1. Proposed Algorithms for F5GLO)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>2.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Table 2.docx. figshare. Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288309.v1">https://doi.org/10.6084/m9.figshare.31288309.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref14">Acharya et al. 2026n</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Table 2.docx (Table 2. Latency Metrics)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>3.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Table 3.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288318.v1">https://doi.org/10.6084/m9.figshare.31288318.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref15">Acharya et al. 2026o</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Table 3.docx (Table 3. Throughput metrics)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>4.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Table 4.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288324.v1">https://doi.org/10.6084/m9.figshare.31288324.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref16">Acharya et al. 2026p</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Table 4.docx (Table 4. Energy Vs Latency Trade-off
)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>5.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 1.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31287844.v2">https://doi.org/10.6084/m9.figshare.31287844.v2</ext-link> (
                            <xref ref-type="bibr" rid="ref4">Acharya et al. 2026d</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 1.docx (Figure 1. Flow Chart of System Model)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>6.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 2.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31287874.v1">https://doi.org/10.6084/m9.figshare.31287874.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref5">Acharya et al. 2026e</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 2.docx (Figure 2. Basic diagram of F5GLO Model)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>7.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 3.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31287880.v1">https://doi.org/10.6084/m9.figshare.31287880.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref6">Acharya et al. 2026f</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 3.docx (Figure 3. Average and Maximum Latency Comparison)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>8.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 4.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288048.v1">https://doi.org/10.6084/m9.figshare.31288048.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref7">Acharya et al. 2026g</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 4.docx (Figure 4. Peak Load handling: Maximum Latency Comparison)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>9.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 5.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288054.v1">https://doi.org/10.6084/m9.figshare.31288054.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref8">Acharya et al. 2026h</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 5.docx (Figure 5. Latency Distribution: Comparison of Models)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>10.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 6.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288066.v1">https://doi.org/10.6084/m9.figshare.31288066.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref9">Acharya et al. 2026i</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 6.docx (Figure 6. Throughput Analysis)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>11.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 7.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288099.v1">https://doi.org/10.6084/m9.figshare.31288099.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref10">Acharya et al. 2026j</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 7.docx (Figure 7. Resource Utilization Comparison)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>12.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 8.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288135.v1">https://doi.org/10.6084/m9.figshare.31288135.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref11">Acharya et al. 2026k</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 8.docx (Figure 8. PRA-Allocated Resources over Time)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>13.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Figure 9.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288183.v1">https://doi.org/10.6084/m9.figshare.31288183.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref12">Acharya et al. 2026l</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>
Figure 9.docx (Figure 9. ANS-Network slice selection)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>14.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Algorithm 1.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288345.v1">https://doi.org/10.6084/m9.figshare.31288345.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref1">Acharya et al. 2026a</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>Algorithm 1.docx (Algorithm 1: Predictive Resource Allocation (PRA))</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>15.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Algorithm 2.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288360.v1">https://doi.org/10.6084/m9.figshare.31288360.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref2">Acharya et al. 2026b</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>Algorithm 2.docx (Algorithm 2: Latency-Aware Dynamic Routing (LADR)</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                    <list-item>
                        <label>16.</label>
                        <p>Figshare: ACHARYA, MANAS RANJAN; TRIPATHY, SARITA; KUMAR PATNAIK, PRASANT (2026). Algorithm 3.docx. figshare.</p>
                        <p>Dataset. 
                            <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.31288372.v1">https://doi.org/10.6084/m9.figshare.31288372.v1</ext-link> (
                            <xref ref-type="bibr" rid="ref3">Acharya et al. 2026c</xref>)</p>
                        <p>The project contains the following underlying data:
                            <list list-type="bullet">
                                <list-item>
                                    <label>&#x2022;</label>
                                    <p>Algorithm 3.docx (Algorithm 3: Adaptive Network Slicing (ANS))</p>
                                    <p>Data are available under the terms of the&#x00a0;
                                        <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license&#x00a0;(CC-BY 4.0)</ext-link>.</p>
                                </list-item>
                            </list>
                        </p>
                    </list-item>
                </list>
            </p>
        </sec>
        <ack>
            <title>Acknowledgments</title>
            <p>We are thankful to the administrative support provided by our university.
</p>
        </ack>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Algorithm 1.docx</data-title>. Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288345.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Algorithm 2.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026b</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288360.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:<year>2026c</year>.
                    <data-title>Algorithm 3.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288372.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 1.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026d</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31287844.v2</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 2.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026e</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31287874.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 3.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026f</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31287880.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 4.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026g</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288048.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 5.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026h</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288054.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 6.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026i</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288066.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 7.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026j</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288099.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 8.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026k</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288135.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref12">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Figure 9.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026l</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288183.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Table 1.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026m</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31287748.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Table 2.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026n</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288309.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Table 3.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026o</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288318.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Acharya</surname>
                            <given-names>MR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tripathy</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Patnaik</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <data-title>Table 4.docx.</data-title>Dataset.
                    <source>

                        <italic toggle="yes">Figshare.</italic>
</source>
                    <year>2026p</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.31288324.v1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Agiwal</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Roy</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Saxena</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>Next generation 5G wireless networks: A comprehensive survey.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Commun Surv Tutor.</italic>
</source>
                    <year>2016</year>;<volume>18</volume>(<issue>3</issue>):<fpage>1617</fpage>&#x2013;<lpage>1655</lpage>.</mixed-citation>
            </ref>
            <ref id="ref18">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ahmad</surname>
                            <given-names>I</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liyanage</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ylianttila</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>5G for healthcare: Remote surgery and beyond.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Netw.</italic>
</source>
                    <year>2022</year>;<volume>36</volume>(<issue>2</issue>):<fpage>165</fpage>&#x2013;<lpage>172</lpage>.</mixed-citation>
            </ref>
            <ref id="ref19">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>&#x00c1;lvarez</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Garc&#x00ed;a</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>L&#x00f3;pez</surname>
                            <given-names>G</given-names>
                        </name>
</person-group>:
                    <article-title>Edge computing and 5G integration for enhancing remote patient monitoring services.</article-title>
                    <source>

                        <italic toggle="yes">J. Med. Syst.</italic>
</source>
                    <year>2023</year>;<volume>47</volume>(<issue>1</issue>):<fpage>1</fpage>&#x2013;<lpage>15</lpage>.</mixed-citation>
            </ref>
            <ref id="ref20">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bhatia</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Sood</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar</surname>
                            <given-names>V</given-names>
                        </name>
</person-group>:
                    <article-title>Applications of fog computing in healthcare: A review.</article-title>
                    <source>

                        <italic toggle="yes">Futur. Gener. Comput. Syst.</italic>
</source>
                    <year>2020</year>;<volume>108</volume>:<fpage>480</fpage>&#x2013;<lpage>492</lpage>.</mixed-citation>
            </ref>
            <ref id="ref21">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bonomi</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Milito</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhu</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <chapter-title>Fog computing and its role in the Internet of things</chapter-title>.
                    <source>

                        <italic toggle="yes">Proceedings of the First Edition of the MCC Workshop on Mobile Cloud Computing.</italic>
</source>
                    <year>2012</year>; pp.<fpage>13</fpage>&#x2013;<lpage>16</lpage>.</mixed-citation>
            </ref>
            <ref id="ref22">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Cao</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Leung</surname>
                            <given-names>VCM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Chow</surname>
                            <given-names>C</given-names>
                        </name>
</person-group>:
                    <article-title>Enhancing fog computing for healthcare IoT systems through local processing.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2019</year>;<volume>7</volume>:<fpage>114574</fpage>&#x2013;<lpage>114586</lpage>.</mixed-citation>
            </ref>
            <ref id="ref23">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Cheng</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>L</given-names>
                        </name>
</person-group>:
                    <article-title>Leveraging 5G capabilities for efficient data processing in fog nodes.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Mob. Comput.</italic>
</source>
                    <year>2022</year>;<volume>21</volume>(<issue>7</issue>):<fpage>2218</fpage>&#x2013;<lpage>2231</lpage>.</mixed-citation>
            </ref>
            <ref id="ref24">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Dastjerdi</surname>
                            <given-names>AV</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Buyya</surname>
                            <given-names>R</given-names>
                        </name>
</person-group>:
                    <article-title>Fog computing: Helping the Internet of Things realize its potential.</article-title>
                    <source>

                        <italic toggle="yes">Computer.</italic>
</source>
                    <year>2016</year>;<volume>49</volume>(<issue>8</issue>):<fpage>112</fpage>&#x2013;<lpage>116</lpage>.</mixed-citation>
            </ref>
            <ref id="ref25">
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Goswami</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Panda</surname>
                            <given-names>N</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mohanty</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <chapter-title>Machine learning techniques and routing protocols in 5G and 6G mobile network communication system - An overview.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the 2023 7th International Conference on Trends in Electronics and Informatics (ICOEI).</italic>
</source>
                    <publisher-name>IEEE</publisher-name>;<year>2023</year>; pp.<fpage>1094</fpage>&#x2013;<lpage>1101</lpage>.</mixed-citation>
            </ref>
            <ref id="ref26">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Gupta</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Jha</surname>
                            <given-names>RK</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>A survey on 5G-enabled healthcare: Applications, challenges, and future directions.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2021</year>;<volume>9</volume>:<fpage>51988</fpage>&#x2013;<lpage>52016</lpage>.</mixed-citation>
            </ref>
            <ref id="ref27">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hassan</surname>
                            <given-names>MM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Gumaei</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Alsanad</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>Fog computing for elderly care: A latency-aware approach.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2021</year>;<volume>9</volume>:<fpage>23982</fpage>&#x2013;<lpage>23995</lpage>.</mixed-citation>
            </ref>
            <ref id="ref28">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hong</surname>
                            <given-names>CH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Varghese</surname>
                            <given-names>B</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Buyya</surname>
                            <given-names>R</given-names>
                        </name>
</person-group>:
                    <article-title>Adaptive load balancing for healthcare applications in fog computing.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Transactions on Cloud Computing.</italic>
</source>
                    <year>2020</year>;<volume>10</volume>(<issue>1</issue>):<fpage>104</fpage>&#x2013;<lpage>117</lpage>.</mixed-citation>
            </ref>
            <ref id="ref29">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hossain</surname>
                            <given-names>MS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Muhammad</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Alamri</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>Smart healthcare: An approach to 5G-enabled architecture.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2022</year>;<volume>10</volume>:<fpage>33191</fpage>&#x2013;<lpage>33208</lpage>.</mixed-citation>
            </ref>
            <ref id="ref30">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Jiang</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>X</given-names>
                        </name>
</person-group>:
                    <article-title>Enhancing smart healthcare with fog computing and 5G.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Internet Things J.</italic>
</source>
                    <year>2021</year>;<volume>8</volume>(<issue>15</issue>):<fpage>11939</fpage>&#x2013;<lpage>11952</lpage>.</mixed-citation>
            </ref>
            <ref id="ref31">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Da Xu</surname>
                            <given-names>L</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhao</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>The Internet of things: A survey.</article-title>
                    <source>

                        <italic toggle="yes">Inf. Syst. Front.</italic>
</source>
                    <year>2019</year>;<volume>21</volume>(<issue>1</issue>):<fpage>1</fpage>&#x2013;<lpage>24</lpage>. [Note: Fixed "Da Xu, L." to consistent initials].</mixed-citation>
            </ref>
            <ref id="ref32">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Liu</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>B</given-names>
                        </name>
</person-group>:
                    <article-title>Multi-objective optimization in fog computing for healthcare.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans Netw Sci Eng.</italic>
</source>
                    <year>2021</year>;<volume>8</volume>(<issue>3</issue>):<fpage>2370</fpage>&#x2013;<lpage>2382</lpage>.</mixed-citation>
            </ref>
            <ref id="ref33">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Liu</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>L</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <article-title>Energy-efficient fog computing in 5G networks for healthcare IoT.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Internet Things J.</italic>
</source>
                    <year>2023</year>;<volume>10</volume>(<issue>10</issue>):<fpage>8801</fpage>&#x2013;<lpage>8812</lpage>.</mixed-citation>
            </ref>
            <ref id="ref34">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mahmud</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kotagiri</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Buyya</surname>
                            <given-names>R</given-names>
                        </name>
</person-group>:
                    <chapter-title>Fog computing: A taxonomy, survey and future directions.</chapter-title>
                    <source>

                        <italic toggle="yes">Internet of Things, Machine Learning &amp; Artificial Intelligence in Healthcare.</italic>
</source>
                    <year>2020</year>; pp.<fpage>105</fpage>&#x2013;<lpage>133</lpage>.</mixed-citation>
            </ref>
            <ref id="ref35">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Park</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Choi</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Impact of 5G on IoT healthcare applications.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Internet Things J.</italic>
</source>
                    <year>2021</year>;<volume>8</volume>(<issue>1</issue>):<fpage>125</fpage>&#x2013;<lpage>135</lpage>.</mixed-citation>
            </ref>
            <ref id="ref36">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Patel</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Niyato</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <article-title>5G-enabled telehealth in rural areas: Challenges and opportunities.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Commun. Mag.</italic>
</source>
                    <year>2022</year>;<volume>60</volume>(<issue>5</issue>):<fpage>114</fpage>&#x2013;<lpage>120</lpage>.</mixed-citation>
            </ref>
            <ref id="ref37">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Pattnaik</surname>
                            <given-names>PK</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Panda</surname>
                            <given-names>BK</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Sain</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Design of novel mobility and obstacle-aware algorithm for optimal MANET routing.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2021</year>;<volume>9</volume>:<fpage>110648</fpage>&#x2013;<lpage>110657</lpage>.</mixed-citation>
            </ref>
            <ref id="ref38">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Qin</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Peng</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Xu</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>A survey of network slicing for 5G.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2020</year>;<volume>8</volume>:<fpage>19703</fpage>&#x2013;<lpage>19726</lpage>.</mixed-citation>
            </ref>
            <ref id="ref39">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Sharma</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Singh</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Dynamic resource allocation for IoT-enabled fog computing in healthcare.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Serv. Comput.</italic>
</source>
                    <year>2022</year>;<volume>15</volume>(<issue>1</issue>):<fpage>466</fpage>&#x2013;<lpage>479</lpage>.</mixed-citation>
            </ref>
            <ref id="ref40">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Shi</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cao</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Q</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Edge computing: Vision and challenges.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Internet Things J.</italic>
</source>
                    <year>2016</year>;<volume>3</volume>(<issue>5</issue>):<fpage>637</fpage>&#x2013;<lpage>646</lpage>.</mixed-citation>
            </ref>
            <ref id="ref41">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Tang</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <article-title>Energy-aware scheduling in fog computing for reducing latency and energy consumption.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Transactions on Sustainable Computing.</italic>
</source>
                    <year>2022</year>;<volume>7</volume>(<issue>2</issue>):<fpage>333</fpage>&#x2013;<lpage>346</lpage>.</mixed-citation>
            </ref>
            <ref id="ref42">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>X</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <article-title>Latency-aware task scheduling in fog computing for healthcare applications.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2019</year>;<volume>7</volume>:<fpage>158107</fpage>&#x2013;<lpage>158121</lpage>.</mixed-citation>
            </ref>
            <ref id="ref43">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wu</surname>
                            <given-names>J</given-names>
                        </name>
</person-group>:
                    <article-title>Machine learning for network management in 5G: A survey.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2020</year>;<volume>8</volume>:<fpage>110843</fpage>&#x2013;<lpage>110866</lpage>.</mixed-citation>
            </ref>
            <ref id="ref44">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Xu</surname>
                            <given-names>X</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>H</given-names>
                        </name>
</person-group>:
                    <article-title>Case study on integrating 5G and fog computing in rural healthcare.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
</source>
                    <year>2023</year>;<volume>11</volume>:<fpage>12023</fpage>&#x2013;<lpage>12037</lpage>.</mixed-citation>
            </ref>
            <ref id="ref45">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zeng</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>K</given-names>
                        </name>
</person-group>:
                    <article-title>AI-driven predictive resource allocation for healthcare.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Netw. Serv. Manag.</italic>
</source>
                    <year>2023</year>;<volume>20</volume>(<issue>1</issue>):<fpage>1</fpage>&#x2013;<lpage>14</lpage>.</mixed-citation>
            </ref>
            <ref id="ref46">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Vasilakos</surname>
                            <given-names>AV</given-names>
                        </name>
</person-group>:
                    <article-title>Efficient resource allocation for fog computing in IoT.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Industr. Inform.</italic>
</source>
                    <year>2018</year>;<volume>14</volume>(<issue>10</issue>):<fpage>4427</fpage>&#x2013;<lpage>4437</lpage>.</mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report483176">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.196385.r483176</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Samal</surname>
                        <given-names>Chandra Kanta</given-names>
                    </name>
                    <xref ref-type="aff" rid="r483176a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r483176a1">
                    <label>1</label>University of Delhi, New Delhi, Delhi, India</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>4</day>
                <month>6</month>
                <year>2026</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2026 Samal CK</copyright-statement>
                <copyright-year>2026</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport483176" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.178047.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>Author&#x2019;s research work on digital health system for rural areas using Fog Computing and 5G Technology;&#x00a0;propose three algorithms: 1. Predictive Resource Allocation (PRA) method is presented in which dynamically allocates network resources based on predicted demand and current consumption patterns. 2. Latency-Aware Dynamic Routing (LADR) mechanism used to select the optimal routing path based on latency constraints. 3. Adaptive Network Slicing (ANS) mechanism, which dynamically assigns network slices based on system load and priority requirements. Author&#x2019;s mention of the F5GLO model using Fog Computing and 5G technologies. The F5GLO simulation results in comparison with the Local Server Model and Traditional Cloud Model in the context of Average and Maximum Latency, Peak load handling, Maximum latency,</p>
            <p> Throughput, Efficiency, and Resource utilization. The F5GLO model proves its ability to significantly decrease the response time, with the maximum decrease of latency up to 87%. F5GLO is also characterized by better energy efficiency and high throughput in addition to relying on more powerful technology, such as fog computing and 5G technology, to improve the performance of the rural health system. Author&#x2019;s is not mentioning the simulation configuration details for energy efficiency and not details discussing the real-world application. As per proposed algorithms and the suggested F5GLO model, simulation results to prove low latency due to</p>
            <p> improving the IoT-based service.</p>
            <p>Is the work clearly and accurately presented and does it cite the current literature?</p>
            <p>Yes</p>
            <p>If applicable, is the statistical analysis and its interpretation appropriate?</p>
            <p>Yes</p>
            <p>Are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Is the study design appropriate and is the work technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions drawn adequately supported by the results?</p>
            <p>Yes</p>
            <p>Are sufficient details of methods and analysis provided to allow replication by others?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Wireless Networks, Brain Networks, Social Networks etc</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
</article>
