wordsmithing

Author: Larry Peterson

arch.rst

@@ -348,37 +348,37 @@ the EPC:
 -  AUSF (Authentication Server Function): Essentially an authentication
    server. Includes part of the functionality in the EPC’s HSS.
 
-The second group also runs in the Control Plane (CP) but does not have a
-counterpart in the EPC:
+The second group also runs in the Control Plane (CP) but does not have
+a direct counterpart in the EPC:
 
 -  SDSF (Structured Data Storage Network Function): A “helper” service
-   used to store structured data. Might be implemented by an “SQL
+   used to store structured data. Could be implemented by an “SQL
    Database” in a microservices-based system.
 
 -  UDSF (Unstructured Data Storage Network Function): A “helper” service
-   used to store unstructured data. Might be implemented by a “Key/Value
+   used to store unstructured data. Could be implemented by a “Key/Value
    Store” in a microservices-based system.
 
 -  NEF (Network Exposure Function): A means to expose select
    capabilities to third-party services, including translation between
-   internal and external representations for data. Might be implemented
+   internal and external representations for data. Could be implemented
    by an “API Server” in a microservices-based system.
 
 -  NFR (NF Repository Function): A means to discover available services.
-   Might be implemented by a “Discovery Service” in a
+   Could be implemented by a “Discovery Service” in a
    microservices-based system.
 
 -  NSSF (Network Slicing Selector Function): A means to select a Network
    Slice to serve a given UE. Network slices are essentially a way to
    differentiate service given to different users. It is a key feature
-   of 5G that we discuss in depth later in this tutorial.
+   of 5G that we discuss in depth later in a later chapter.
 
 The third group includes the one component that runs in the User Plane
 (UP):
 
 -  UPF (User Plane Function): Forwards traffic between RAN and the
    Internet, corresponding to the S/PGW combination in EPC. In addition
-   to packet forwarding, responsible for policy enforcement, lawful
+   to packet forwarding, it responsible for policy enforcement, lawful
    intercept, traffic usage reporting, and QoS policing.
 
 Of these, the first and third groups are best viewed as a
@@ -388,7 +388,7 @@ to a cloud native solution as the desired end-state for the Mobile Core.
 Of particular note, introducing distinct storage services means that all
 the other services can be stateless, and hence, more readily scalable.
 Also note that :ref:`Figure 3.10 <fig-5g-core>` adopts an idea that’s
-common in microservice-based systems, namely, to show a “message bus”
+common in microservice-based systems, namely, to show a *message bus*
 interconnecting all the components rather than including a full set of
 pairwise connections. This also suggests a well-understood
 implementation strategy.
@@ -437,7 +437,7 @@ similar challenge in the chapters that follow. The closer the following
 discussion gets to implementation details, the more specific we have to
 be about whether we are using 4G components or 5G components. As a
 general rule, we use 4G components—particularly with respect to the
-Mobile Core, since that’s the available open source software—and trust
+Mobile Core, since that’s what's available in open source today—and trust
 the reader can make the appropriate substitution without loss of
 generality. Like the broader industry, the open source community is in
 the process of incrementally evolving its 4G code base into its

intro.rst

@@ -22,27 +22,28 @@ from their smartphones, but also swarms of autonomous devices working
 together on their behalf. All of this requires a fundamentally
 different architecture.
 
-The requirements for this architecture are ambitious. They can be
-summarized along three dimensions:
-
-- *Massive Internet-of-Things*, potentially including devices with
-  ultra-low energy (10+ years of battery life), ultra-low complexity
-  (10s of bits-per-second), and ultra-high density (1 million nodes
-  per squared-km).
-
-- *Mission-Critical Control*, potentially including ultra-high availability
-  (greater than :math:`10^{-5}` per ms), ultra-low latency
-  (as low as 1 ms), and extreme mobility (up to 100 km/h).
-
-- *Enhaned Mobile Broadband*, potentially including extreme capacity
-  (10 Tbps per squared-km) and extreme data rates
+The requirements for this architecture are ambitious, and can be
+summarized as having three primary objectives:
+
+- To support *Massive Internet-of-Things*, potentially including
+  devices with ultra-low energy (10+ years of battery life), ultra-low
+  complexity (10s of bits-per-second), and ultra-high density (1
+  million nodes per square kilometer).
+
+- To support *Mission-Critical Control*, potentially including
+  ultra-high availability (greater than :math:`10^{-5}` per ms),
+  ultra-low latency (as low as 1 ms), and extreme mobility (up to 100
+  km/h).
+  
+- To support *Enhaned Mobile Broadband*, potentially including extreme
+  capacity (10 Tbps per square kilometer) and extreme data rates
   (multi-Gbps peak, 100+ Mbps sustained).
-
-These goals will certainly not be met overnight, but that's in keeping
+  
+These targets will certainly not be met overnight, but that's in keeping
 with each generation of the mobile network being a decade-long
 endeavor.
 
-This book describes the 5G cellular network, which because it is on an
+The 5G mobile network, because it is on an
 evolutionary path and not a point solution, includes standardized
 specifications, a range of implementation choices, and a long list of
 aspirational goals. Because this leaves so much room for interpretation,
@@ -121,7 +122,7 @@ allocations opening above 24-GHz.
 While the specific frequency band is not directly relevant to
 understanding 5G from an architectural perspective, it does impact the
 physical-layer components, which in turn has indirect ramifications on
-the overall 5G system. We will identify and explain these ramifications
+the overall 5G system. We identify and explain these ramifications
 in later chapters.
 
 1.2 Access Networks