WO2023192832A1 - Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers - Google Patents

Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers Download PDF

Info

Publication number
WO2023192832A1
WO2023192832A1 PCT/US2023/065005 US2023065005W WO2023192832A1 WO 2023192832 A1 WO2023192832 A1 WO 2023192832A1 US 2023065005 W US2023065005 W US 2023065005W WO 2023192832 A1 WO2023192832 A1 WO 2023192832A1
Authority
WO
WIPO (PCT)
Prior art keywords
sfp
sfc
traffic flows
ntcrm
service
Prior art date
Application number
PCT/US2023/065005
Other languages
English (en)
Inventor
Alexandre Saso STOJANOVSKI
Meghashree Dattatri Kedalagudde
Thomas Luetzenkirchen
Ching-Yu Liao
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202380023608.3A priority Critical patent/CN118765519A/zh
Publication of WO2023192832A1 publication Critical patent/WO2023192832A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to service function chaining in wireless cellular system with service exposure to third parties.
  • SFC Service Function Chaining
  • 5GS 5G System
  • TR 23.700-18 SFC is a concept defined by the Internet Engineering Task Force (IETF) in the following documents: Request for Comments (RFC) 7498 (Problem Statement), RFC 7665 (SFC Architecture) and RFC 8300 (Network Service Header (NSH)).
  • RFC Request for Comments
  • RFC 7665 SFC Architecture
  • RFC 8300 Network Service Header
  • Each service function is an opaque processing element in user plane.
  • the SF forwarder, and SF behaviour/control are out of 3GPP scope.
  • the initial classification for the service chain to be applied to traffic flow is performed by 5GC.
  • a traffic flow of a PDU Session is subject to a single service function path (SFP) at a given time.
  • SFP single service function path
  • Figure 1 is an illustration of service function chaining concepts.
  • Figure 2 illustrates an example of external metadata and policy.
  • Figure 3A illustrates a 5G system architecture for SFC support (uplink traffic), in accordance with various embodiments.
  • FIG. 3B illustrates a 5G system architecture for SFC support (downlink traffic), in accordance with various embodiments.
  • FIG. 4 illustrates a procedure for application function (AF)-influenced traffic routing for SFC in 5G core network (5GC) for protocol data unit (PDU) Sessions not identified by a user equipment (UE) address, in accordance with various embodiments.
  • AF application function
  • PDU protocol data unit
  • Figure 5 illustrates a procedure for AF-influenced traffic routing for SFC in 5GC when targeting an individual UE address, in accordance with various embodiments.
  • Figure 6 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 7 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIGS 9, 10, and 11 illustrate example processes in accordance with various embodiments.
  • embodiments herein may provide service exposure to third parties for service function chaining (SFC) in a wireless cellular network.
  • SFC service function chaining
  • embodiments provide techniques for SFC support in 5GS that allows a trusted 3rd party to dynamically request that specific set of one or more traffic flows (e.g. a flow identified via a packet filter, or all traffic of a specific UE, or all traffic of a group of UEs) be steered towards a service function path (SFP) as requested by the 3rd party.
  • SFP service function path
  • metadata may be added into the SFP, e.g., as requested by the 3rd party.
  • the embodiments herein may enable vendors specialized in specific functionality (e.g. firewall, deep packet inspection) to provide stand-alone boxes to network vendors.
  • FIG 1 which corresponds to Figure 4-1 of 3GPP TR 23.700-18, illustrates service function chaining (SFC) concepts. As summarized in TR 23.700-18:
  • Each service function is an opaque processing element in user plane.
  • the SF forwarder, and SF behaviour/control are out of 3GPP scope.
  • the initial classification for the service chain to be applied to traffic flow is performed by 5GC.
  • a traffic flow of a PDU Session is subject to a single service function path (SFP) at a given time.
  • SFP single service function path
  • the SFC functionality could be considered as a stand-alone function implemented in the Data Network (DN) reachable via the N6 interface e.g. as a function residing outside of the 5GS.
  • the User Plane Function (UPF) serving as the PDU Session Anchor (PSA) could be configured with pre-defined N6 tunnels, each N6 tunnel pointing to a pre-defined SFP deployed in the DN.
  • UPF User Plane Function
  • PSA PDU Session Anchor
  • this may not be very practical in case where the SFC functionality is deployed by a trusted 3rd party, because the configuration of SFPs by the 3rd party would be intimately linked with the configuration of predefined N6 tunnels at the UPF owned by the network operator.
  • FIG. 2 which corresponds to IETF RFC 8300 Figure 10, there are use cases where an external party should be allowed to provide Metadata that can be fed into the Service Function Path.
  • the Metadata could carry control information (e.g. allow/deny certain SF operation to a specific user) that allows the 3rd party to dynamically exercise certain controls of the SFP.
  • Various embodiments herein provide techniques for SFC support in 5GS that allow a trusted 3rd party to dynamically request that specific set of traffic flows (e.g. flow identified via a packet filter, or all traffic of a specific UE, or all traffic of a group of UEs) be steered towards an SFP as requested by the 3rd party, and also feed Metadata into the SFP as requested by the 3rd party.
  • Embodiments may extend existing 5GS exposure services allowing a 3rd party Application Function (AF) to request that selected traffic flows (“target traffic”) be steered towards a specific Service Function Path, including injection of Metadata into the Service Function Path.
  • AF Application Function
  • the embodiments herein may enable vendors specialized in specific functionality (e.g. firewall, deep packet inspection) to provide stand-alone boxes to network vendors. This minimizes the operator dependency on the big network vendors and contributes to building a healthy ecosystem .
  • vendors specialized in specific functionality e.g. firewall, deep packet inspection
  • Embodiments herein may assume that there is a service level agreement between the operator and a third party that includes a list of authorized predefined Service Function Paths (SFPs), each SFP being identified by a Service Function Path Identifier (SFP ID).
  • SFPs Service Function Paths
  • SFP ID Service Function Path Identifier
  • Each SFP implements a set of pre-agreed policies (e.g. an ordered set of operations to be applied on the user plane packets).
  • the third party can request that selected traffic flows be steered towards a specific SFP, either at PDU Session establishment or any time after PDU Session establishment.
  • the service level agreement can also contain a pre-agreed set of metadata that the third party is allowed to insert into the SFP.
  • Example use of Metadata is to allow the third party to include/ex elude specific service operation in/from the SFP (e g. age verification, denial of using specific application, etc.) for selected user.
  • UPF-SFC user plane function with SFC capability
  • UPF-PSA PDU Session Anchor
  • the UPF-SFC includes at least the Service Classification Function as defined in IETF RFC 7665.
  • the UPF-SFC may include support for SFC Encapsulation, SFC Forwarding Function, etc. as described in IETF RFC 7665).
  • the following network functions are impacted for handling of the SFP ID and/or Metadata: NEF, UDR, SMF and PCF.
  • Figures 3A and 3B show the 5G system architecture for SFC support, for uplink and downlink traffic, respectively.
  • Uplink traffic line 302 corresponds to traffic that is steered to the UPF-SFC; line 304 corresponds to traffic that goes directly to the Data Network as illustrated in Figure 3 A.
  • Downlink traffic corresponds to traffic that is steered to the UPF-SFC; line 308 corresponds to traffic that goes directly to the UE as illustrated in Figure 3B.
  • each SFP for downlink traffic enforces the steering of processed traffic flows back into the same UPF-SFC, and from there to the same UPF-PSA.
  • the AF can provide traffic steering information (TSI) that can contain e.g. targeted traffic descriptor, a list of DNAI(s), a Routing Profile ID and/or N6 routing information.
  • TSI traffic steering information
  • the traffic steering information can instruct the UPF to select a specific preconfigured tunnel on N6 for the traffic flows matching the traffic descriptor.
  • the main SFC-specific impact e.g. SFC service classification, SFP selection, SFC encapsulation etc.
  • the other impacted functions PCF, NEF, SMF, UDR
  • SFP ID and Metadata SFC-specific parameters
  • An example deployment option is where the SFC is hosted in a trusted Edge Data Network environment and is operated by a trusted 3rd party.
  • the AF in the trusted Edge Data Network environment can dynamically make decisions for steering of selected traffic flows onto a selected SFP and optionally convey Metadata to the Service Functions on that SFP.
  • Such a deployment corresponds to Figure 2 (External Metadata and Policy), whereby an external network can provide Metadata containing classification information for policy enforcement and context information for forwarding packets within an SFC.
  • the UPF-PSA uses existing mechanisms for packet data detection (incoming F-TEID and SDF filters) and forwarding (outgoing F-TEID) to steer the targeted traffic flows towards the UPF-SFC. There is no specification impact on the UPF-PSA.
  • the traffic forwarding between a specific UPF-PSA and a specific UPF-SFC takes place over a pair of N6s tunnels associated with the UPF-PSA and UPF-SFC, one tunnel per traffic direction as illustrated in Figure 3A and Figure 3B.
  • This pair of tunnels is set up dynamically by the SMF and is not UE-specific e.g. the same pair of tunnels can be used for traffic associated with multiple UEs.
  • the N6s tunnel for downlink traffic is used in both directions.
  • the N6s tunnel for uplink traffic is used in one direction only.
  • the UPF-PSA is the IP anchor point for the PDU sessions.
  • the UPF-PSA detects the traffic that is subject to SFC and steers it towards the UPF-SFC based on the FAR configured in the UPF-PSA.
  • the service function processing is applied in UPF- SFC, the DL traffic is sent from the UPF-SFC to the UPF-PSA based on the FAR configuration in the UPF-SFC which is then further forwarded towards the UE by the UPF-PSA.
  • the SFP for uplink traffic contains a Network Address Translation (NAT) device
  • the NAT device needs to steer the downlink packet towards the N6 interface of the UPF-PSA.
  • the steering is performed via standard IP routing because the new IP address will automatically steer the downlink packet towards the N6 interface of the UPF-PSA.
  • Uplink traffic that is not subject to SFC can break out directly to the DN via N6 (see Figure 3A). Downlink traffic always enters the 5GS at the UPF-PSA and only selected traffic is steered towards SFC (via “hairpin” forwarding), while the rest of the traffic is forwarded to N3/N9.
  • UPF-SFC The UPF with SFC capability (UPF-SFC) deploys an SFC functionality with several SFPs corresponding to pre-defined SFC polices as indicated in Figures 3A-3B.
  • the AF indicates the SFP ID and optionally Metadata for a selected target (e.g. a traffic flow, a UE, a group of UEs, etc.) per traffic direction e.g. a distinct SFP ID is used for uplink and downlink traffic.
  • a selected target e.g. a traffic flow, a UE, a group of UEs, etc.
  • a distinct SFP ID is used for uplink and downlink traffic.
  • the PCF authorizes the requested SFP ID and optionally Metadata e.g. by checking whether it is part of a pre-agreed SFP ID list or pre-agreed Metadata values in the service level agreement.
  • the SMF indicates the SFP ID(S) and optionally Metadata to the UPF-SFC via N4x interface, in addition to the targeted traffic flows description.
  • the targeted traffic flows description is provided in the associated Packet Detection Rule (PDR).
  • the UPF-SFC steers the targeted traffic flows towards the SFP indicated by the received SFC ID. Additionally it may perform SFC encapsulation as defined in RFC8300 [Y] and include the received Metadata in the SFC encapsulation header.
  • preconfigured N6 tunnels may have scalability issues because the SMF would need to select a specially configured UPF-PSA upon PDU Session establishment, even if there is no SFC-related request from a 3rd party during the lifetime of the PDU Session.
  • keeping SFC ID as a distinct parameter allows for changes in the SFP configuration without any impact on the 5GC user plane configuration. It also allows for selecting a generic UPF-PSA during PDU Session establishment with no SFC-related preconfiguration. Note also thatN4x is needed to convey the Metadata information to the UPF-SFC.
  • Figure 4 illustrates a procedure for processing AF requests to influence traffic routing for PDU Sessions not identified by a UE address, in accordance with various embodiments.
  • the procedure of Figure 4 may include enhancements compared with the procedure described in TS 23.502 clause 4.3.6.2.
  • the procedure of Figure 4 is used when targeting a group of UE(s), or any UE accessing a combination of DNN and S-NSSAI, or targeting individual UE by a GPSI.
  • the SFP ID and Metadata provided as part of this procedure are applied upon PDU Session establishment, but can also result in modification of already established PDU Sessions that are impacted by the AF request. Aspects of various operations of the procedure of Figure 4 are described further below.
  • the AF creates AF request that includes an SFP ID and, optionally, Metadata corresponding to that SFC ID, in addition to existing parameters (e.g. Traffic descriptor, Application Identifier, traffic steering information (TSI)), to the NEF for requesting traffic routing to a SFP identified by the SFP ID.
  • SFP ID an SFP ID and, optionally, Metadata corresponding to that SFC ID, in addition to existing parameters (e.g. Traffic descriptor, Application Identifier, traffic steering information (TSI)), to the NEF for requesting traffic routing to a SFP identified by the SFP ID.
  • TTI traffic steering information
  • the AF sends the AF request via Nnef_TrafficInference_Create/Update/Delete message to NEF.
  • the NEF requests to store/update/remove information of PFD(s), SFP ID and Metadata based on Application ID/Traffic descriptor.
  • the NEF returns Nnef_TrafficInference_Create/Update/Delete response message to AF.
  • the PCF(s) that have subscribed to modifications of AF requests receive(s) a Nudr_DM_Notify notification of data change from the UDR including the SFP ID and the Metadata.
  • the PCF checks if the indicated SFP ID corresponds to an authorized SFC policy for the AF. If the check is successful, the PCF notifies SMF via Npcf_SMPolicyControl_UpdateNotify message including PCC rules.
  • the PCC rules contain SFP ID and Metadata (if available), in addition to existing parameters, such as PFD(s) and TSI.
  • the SMF selects UPF-SFC taking into account specific optional UPF capabilities, e.g., as described in clause 6.3.3 of 3GPP TS 23.501. In this case the specific capabilities refer to the SFC-related capability and configuration in the UPF. 6b.
  • the SMF requests allocation of two tunnel endpoints at the UPF-PSA (one tunnel per traffic direction).
  • the SMF requests allocation of two tunnel endpoints at the UPF-SFC (one tunnel per traffic direction). 6d. Based on the PCC rules received from the PCF, the SMF configures the UPF-PSA via N4 message including PDR and FAR as described in Table 1.
  • the SMF Based on the PCC rules received from the PCF, the SMF configures the UPF-SFC with uplink and downlink PDR and FAR via N4 message as described in Table 2.
  • Figure 5 illustrates enhancements to the procedure for Processing AF requests to influence traffic routing when targeting a specific UE address, as described in TS 23.502 [2] clause 4.3.6.4.
  • the SFP ID and Metadata provided as part of this procedure are applied any time after PDU Session establishment.
  • the NEF receives a Nnef_TrafficInfluence_C reate / Update / Delete Request from the AF.
  • the AF may send the AF request to PCF directly, in which case operation 1 is skipped, or via the NEF.
  • the AF/NEF sends a Nbsf_Management_Discovery request to the binding support function (BSF).
  • BSF binding support function
  • NEF invokes the
  • Npcf_Policy Authorization service to the PCF to transfer the AF request. If an AF sends the AF request directly to the PCF, AF invokes Npcf Policy Authorization service and the PCF responds to the AF.
  • the Npcf_Policy Authorization service request includes the SFP ID and (optionally) the Metadata, in addition to existing parameters e.g. UE address and targeted traffic flows description.
  • the PCF authorizes the AF request and performs the operations 5, 6a and 6b described in Figure 4.
  • FIGS 6-8 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • Figure 6 illustrates a network 600 in accordance with various embodiments.
  • the network 600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection.
  • the UE 602 may be communicatively coupled with the RAN 604 by a Uu interface.
  • the UE 602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 600 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 602 may additionally communicate with an AP 606 via an over-the-air connection.
  • the AP 606 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 604.
  • the connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.11 protocol, wherein the AP 606 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 602, RAN 604, and AP 606 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.
  • the RAN 604 may include one or more access nodes, for example, AN 608.
  • AN 608 may terminate air-interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 608 may enable data/voice connectivity between CN 620 and the UE 602.
  • the AN 608 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 604 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 604 may each manage one or more cells, cell groups, component carriers, etc. to provide the HE 602 with an air interface for network access.
  • the UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 604.
  • the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 602 or AN 608 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 604 may be an LTE RAN 610 with eNBs, for example, eNB 612.
  • the LTE RAN 610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 604 may be an NG-RAN 614 with gNBs, for example, gNB 616, or ng-eNBs, for example, ng-eNB 618.
  • the gNB 616 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN614 and an AMF 644 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 602 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 604 is communicatively coupled to CN 620 that includes network elements to provide various functions to support data and telecommunications services to custom ers/sub scribers (for example, users of UE 602).
  • the components of the CN 620 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.
  • the CN 620 may be an LTE CN 622, which may also be referred to as an EPC.
  • the LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 622 may be briefly introduced as follows.
  • the MME 624 may implement mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 626 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 622.
  • the SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 628 may track a location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME selection for handovers; etc.
  • the S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 630 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 620.
  • the PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application/content server 638.
  • the PGW 632 may route data packets between the LTE CN 622 and the data network 636.
  • the PGW 632 may be coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 632 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 632 and the data network 6 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 632 may be coupled with a PCRF 634 via a Gx reference point.
  • the PCRF 634 is the policy and charging control element of the LTE CN 622.
  • the PCRF 634 may be communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 620 may be a 5GC 640.
  • the 5GC 640 may include an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 640 may be briefly introduced as follows.
  • the AUSF 642 may store data for authentication of UE 602 and handle authentication- related functionality.
  • the AUSF 642 may facilitate a common authentication framework for various access types.
  • the AUSF 642 may exhibit an Nausf service-based interface.
  • the AMF 644 may allow other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602.
  • the AMF 644 may be responsible for registration management (for example, for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646, and act as a transparent proxy for routing SM messages.
  • AMF 644 may also provide transport for SMS messages between UE 602 and an SMSF.
  • AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions.
  • AMF 644 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.
  • the SMF 646 may be responsible for SM (for example, session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.
  • the UPF 648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multi-homed PDU session.
  • the UPF 648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 648 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 650 may select a set of network slice instances serving the UE 602.
  • the NSSF 650 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 650 may also determine the AMF set to be used to serve the UE 602, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 654.
  • the selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650, which may lead to a change of AMF.
  • the NSSF 650 may interact with the AMF 644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 650 may exhibit an Nnssf service-based interface.
  • the NEF 652 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 660), edge computing or fog computing systems, etc.
  • the NEF 652 may authenticate, authorize, or throttle the AFs.
  • NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces.
  • the stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 652 may exhibit an Nnef service-based interface.
  • the NRF 654 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 654 also maintains information of available NF instances and their supported services.
  • the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 654 may exhibit the Nnrf service-based interface.
  • the PCF 656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658.
  • the PCF 656 exhibit an Npcf service-based interface.
  • the UDM 658 may handle subscript! on -related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644.
  • the UDM 658 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 658 may exhibit the Nudm servicebased interface.
  • the AF 660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 640 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may exhibit an Naf service-based interface.
  • the data network 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 638.
  • FIG. 7 schematically illustrates a wireless network 700 in accordance with various embodiments.
  • the wireless network 700 may include a UE 702 in wireless communication with an AN 704.
  • the UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 702 may be communicatively coupled with the AN 704 via connection 706.
  • the connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 702 may include a host platform 708 coupled with a modem platform 710.
  • the host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710.
  • the application processing circuitry 712 may run various applications for the UE 702 that source/sink application data.
  • the application processing circuitry 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706.
  • the layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726.
  • the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714.
  • the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726.
  • a UE transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726.
  • the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.
  • the AN 704 may include a host platform 728 coupled with a modem platform 730.
  • the host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730.
  • the modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746.
  • the components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702.
  • the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry.
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
  • the processors 810 may include, for example, a processor 812 and a processor 814.
  • the processors 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808.
  • the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory/storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 6-8, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • One such process 900 is depicted in Figure 9.
  • the process 900 may be performed by a user plane function (UPF) with service function chaining (SFC) capability (UPF-SFC).
  • the process 900 may include receiving, from an application function (AF), a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs for SFC of one or more traffic flows.
  • the process 900 may further include steering the one or more traffic flows to the first SFP based on the SFC ID.
  • FIG. 10 illustrates another process 1000 in accordance with various embodiments.
  • the process 1000 may be performed by a policy control function (PCF) or a portion thereof.
  • the process 1000 may include receiving a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs that is requested by an application function (AF) for service function chaining (SFC) of one or more traffic flows.
  • SFP service function path
  • the process 1000 may further include verifying that the SFP ID corresponds to an authorized SFC policy for the AF.
  • the process 1000 may further include sending the SFP ID to a session management function (SMF) based on the verification.
  • SFP session management function
  • Figure 11 illustrates another process 1100 in accordance with various embodiments.
  • the process 1100 may be performed by an application function (AF).
  • the process 1100 may include sending, to a network exposure function (NEF), a request that includes a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs that is requested by the AF for service function chaining (SFC) of one or more traffic flows.
  • the process may further include receiving, from the NEF, a response to the request.
  • NEF network exposure function
  • SFP service function path
  • SFC service function chaining
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example Al may include one or more non-transitory, computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors configure a user plane function (UPF) with service function chaining (SFC) capability (UPF- SFC) to: receive, from an application function (AF), a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs for SFC of one or more traffic flows; and steer the one or more traffic flows to the first SFP based on the SFC ID.
  • NCRM non-transitory, computer-readable media
  • Example A2 may include the one or more NTCRM of example Al, wherein the instructions, when executed, further configure the UPF-SFC to: receive, from the AF, metadata associated with the SFP ID; and perform SFP encapsulation to include the metadata in an SFP encapsulation header.
  • Example A3 may include the one or more NTCRM of example A2, wherein the metadata is to include or exclude a service operation in the SFP for the one or more traffic flows.
  • Example A4 may include the one or more NTCRM of example A2, wherein the SFP ID and the metadata are received from the AF via a UPF protocol data unit (PDU) session anchor (UPF-PSA).
  • PDU UPF protocol data unit
  • UPF-PSA UPF protocol data unit session anchor
  • Example A5 may include the one or more NTCRM of example A4, wherein the SFP ID and the metadata are received from the AF further via a network exposure function (NEF), a unified data repository (UDR), a policy control function (PCF), and a session management function (SMF).
  • NEF network exposure function
  • UDR unified data repository
  • PCF policy control function
  • SMF session management function
  • Example A6 may include he one or more NTCRM of example Al, wherein the SFP ID is associated with a service level agreement.
  • Example A7 may include the one or more NTCRM of example Al, wherein the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • UE user equipment
  • Example A8 may include the one or more NTCRM of example Al, wherein the SFC ID is designated for uplink traffic flows or downlink traffic flows.
  • Example A9 may include one or more non-transitory, computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors configure a policy control function (PCF) to: receive a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs that is requested by an application function (AF) for service function chaining (SFC) of one or more traffic flows; verify that the SFP ID corresponds to an authorized SFC policy for the AF; and send the SFP ID to a session management function (SMF) based on the verification.
  • SFP service function path
  • AF application function
  • SFC service function chaining
  • Example A10 may include the one or more NTCRM of example A9, wherein the instructions, when executed, further configure the PCF to: receive metadata that is requested by the AF to be included in the first SFP; determine that the metadata corresponds to an authorized metadata value of a service level agreement associated with the AF; and send the metadata to the SMF based on the determination.
  • Example Al 1 may include the one or more NTCRM of example A10, wherein the metadata is to include or exclude a service operation in the SFP for the one or more traffic flows.
  • Example A12 may include the one or more NTCRM of example A9, wherein the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • UE user equipment
  • Example A13 may include the one or more NTCRM of example A9, wherein the SFC ID is designated for uplink traffic flows or downlink traffic flows.
  • Example A14 may include one or more non-transitory, computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors configure an application function (AF) to: send, to a network exposure function (NEF), a request that includes a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs that is requested by the AF for service function chaining (SFC) of one or more traffic flows; and receive, from the NEF, a response to the request.
  • NCRM non-transitory, computer-readable media
  • Example Al 5 may include the one or more NTCRM of example A14, wherein the request further includes metadata that is requested by the AF to be included in the first SFP.
  • Example A16 may include the one or more NTCRM of example A15, wherein the metadata is to include or exclude a service operation in the SFP for the one or more traffic flows.
  • Example A17 may include the one or more NTCRM of example A14, wherein the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • the one or more traffic flows correspond to a specific traffic flow, all traffic flows of a user equipment (UE), or all traffic flows of a group of UEs.
  • UE user equipment
  • Example Al 8 may include the one or more NTCRM of example A14, wherein the SFC ID is designated for uplink traffic flows or downlink traffic flows.
  • Example A19 may include the one or more NTCRM of any of examples A14-A18, wherein the SFC ID corresponds to a SFC policy that is authorized for the AF according to a service level agreement.
  • Example Bl may include a method for support of Service Function Chaining (SFC) in 5G System (5GS) with service exposure to a 3rd party.
  • SFC Service Function Chaining
  • Example B2 may include the method of example Bl or some other example herein, whereby Service Function Chaining functionality is deployed on the N6 interface of the 5GS.
  • Example B3 may include the method of example B2 or some other example herein, whereby the 5GS operator and 3rd party have a service level agreement including Service Function Path Identifier (SFP ID) and optionally Metadata.
  • SFP ID Service Function Path Identifier
  • Metadata optionally Metadata
  • Example B4 may include the method of example B3 or some other example herein, whereby the SFP ID points to a pre-defined Service Function Path (SFP).
  • SFP Service Function Path
  • Example B5 may include the method of example B4 or some other example herein, whereby the SFP implements a set of pre-agreed policies e.g. an ordered set of operations to be applied on the user plane packets.
  • a set of pre-agreed policies e.g. an ordered set of operations to be applied on the user plane packets.
  • Example B6 may include the method of example B5 or some other example herein, whereby selected Metadata are dynamically inserted in the encapsulation header on the SFP and are used for control of specific Service Functions on the SFP.
  • Example B7 may include the method of examples B5 orB 6 or some other example herein, whereby the third party AF includes per traffic direction an SFP ID and optionally Metadata in the Nnef_TrafficInference_Create/Update/Delete message towards a Network Exposure Function (NEF).
  • NEF Network Exposure Function
  • Example B8 may include the method of example B7 or some other example herein, whereby the NEF stores the SFP ID(S) and Metadata in a User Data Repository (UDR).
  • UDR User Data Repository
  • Example B9 may include the method of example B8 or some other example herein, whereby a Policy Control Function (PCF) obtains the SFP ID(S) and Metadata from the UDR.
  • PCF Policy Control Function
  • Example BIO may include the method of examples B5 or B6 or some other example herein, whereby the third party AF includes per traffic direction an SFP ID and optionally Metadata in the Npcf_PolicyAuthorization_Create/Update/Delete message towards the PCF.
  • Example Bl 1 may include the method of examples B9 or BIO or some other example herein, whereby the PCF creates a Policy Control and Charging (PCC) rule including SFP ID(S) and Metadata and Traffic Steering Policy ID (TSP ID) and sends it to Session Management Function (SMF) serving the UE.
  • PCC Policy Control and Charging
  • TSP ID Metadata and Traffic Steering Policy ID
  • SMF Session Management Function
  • Example B12 may include the method of example Bl 1 or some other examle herein, whereby the SMF selects a first User Plane Function (UPF), referred to as UPF-SFC, that provides access to preconfigured SFPs.
  • UPF-SFC User Plane Function
  • Example B13 may include the method of example B12 or some other example herein, whereby the SMF establishes two GTP-U tunnels (N6s tunnels; one tunnel per traffic direction) between the UPF-SFC and a second UPF which serves as the PDU Session Anchor for the UE’s PDU Session, referred to as UPF-PSA.
  • N6s tunnels one tunnel per traffic direction
  • Example B14 may include the method of examples Bl 1, B12 or B13 or some other example herein, whereby the SMF configures the UPF-SFC with Packet Detection Rules (PDRs) and Forwarding Action Rules (FARs) as indicated in Table 2.
  • PDRs Packet Detection Rules
  • FARs Forwarding Action Rules
  • Example B15 may include the method of example B14 or some other example herein, whereby for uplink traffic arriving on the N6s interface (e.g. from the UPF-PSA) the SMF configures a PDR rule in the UPF-SFC including the uplink Service Data Flow (SDF) filter.
  • SDF Service Data Flow
  • Example B16 may include the method of examples B14 and B15 or some other example herein, whereby for uplink traffic arriving on the N6s interface (e.g. from the UPF-PSA) the SMF configures a FAR rule in the UPF-SFC including the uplink SFP ID and Metadata.
  • the SMF configures a FAR rule in the UPF-SFC including the uplink SFP ID and Metadata.
  • Example B17 may include the method of example B14 or some other example herein, whereby for downlink traffic arriving on the N6s interface (e.g. from the data network via the UPF-PSA) the SMF configures a PDR rule in the UPF-SFC including the downlink Service Data Flow (SDF) filter.
  • SDF Service Data Flow
  • Example B18 may include the method of examples B14 and B17 or some other example herein, whereby for downlink traffic arriving on N6s (e.g. from the data network via the UPF- PSA) the SMF configures a FAR rule in the UPF-SFC including the downlink SFP ID and Metadata.
  • N6s e.g. from the data network via the UPF- PSA
  • the SMF configures a FAR rule in the UPF-SFC including the downlink SFP ID and Metadata.
  • Example B19 may include the method of example B14 or some other example herein, whereby for downlink traffic arriving from the Service Function Chain the SMF configures a PDR rule in the UPF-SFC including the downlink SFP ID and downlink Service Data Flow (SDF) filter.
  • SDF Service Data Flow
  • Example B20 may include the method of examples B14 and B19 or some other example herein, whereby for downlink traffic arriving from the Service Function Chain the SMF configures a FAR rule in the UPF-SFC including a remote tunnel endpoint identifier (Remote F- TEID (N6s)) corresponding to the N6s tunnel for downlink traffic towards the UPF-PSA.
  • a remote tunnel endpoint identifier Remote F- TEID (N6s)
  • Example B21 may include the method of examples Bl 1, B12 or B13 or some other example herein, whereby the SMF configures the UPF-PSA with Packet Detection Rules (PDRs) and Forwarding Action Rules (FARs) as indicated in Table 1.
  • Example B22 may include the method of example B21 or some other example herein, whereby for uplink traffic arriving on the N3/N9 interface (e.g. from the radio access network) the SMF configures a PDR rule in the UPF-PSA including the uplink Service Data Flow (SDF) filter.
  • PDRs Packet Detection Rules
  • FARs Forwarding Action Rules
  • Example 23 may include the method of examples B21, B22, or some other example herein, whereby for uplink traffic arriving on the N3/N9 interface (e g. from the radio access network) the SMF configures a FAR rule in the UPF-PSA including a remote tunnel endpoint identifier (Remote F-TEID (N6s)) corresponding to the N6s tunnel for uplink traffic towards the UPF-SFC.
  • the SMF configures a FAR rule in the UPF-PSA including a remote tunnel endpoint identifier (Remote F-TEID (N6s)) corresponding to the N6s tunnel for uplink traffic towards the UPF-SFC.
  • N6s remote tunnel endpoint identifier
  • Example B24 may include the method of example B21 or some other example herein, whereby for downlink traffic arriving on N6 (e.g. from the data network) the SMF configures a PDR rule in the UPF-PSA including the downlink Service Data Flow (SDF) filter.
  • SDF Service Data Flow
  • Example B25 may include the method of examples B21, B24 or some other example herein, whereby for downlink traffic arriving on N6 (e.g. from the data network) the SMF configures a FAR rule in the UPF-PSA including a remote tunnel endpoint identifier (Remote F- TEID (N6s)) corresponding to the N6s tunnel for downlink traffic towards the UPF-SFC.
  • N6s remote tunnel endpoint identifier
  • Example B26 the method of example B21, whereby for downlink traffic arriving on N6s (e.g. from the Service Function Chain via the UPF-SFC) the SMF configures a PDR rule in the UPF-PSA including a local tunnel endpoint identifier (Local F-TEID (N6s)) corresponding to the N6s tunnel for downlink traffic towards the UPF-PSA.
  • N6s Local F-TEID
  • Example B27 may include the method of example B14 or some other example herein, whereby the UPF-SFC uses the received Metadata e.g. to insert in the Network Service Header (NSH) of data units exchanged on the selected SFP.
  • NSH Network Service Header
  • Example B28 may include the method of any of the previous examples herein, whereby the SFP for uplink traffic contains a Network Address Translation (NAT) device.
  • NAT Network Address Translation
  • Example B29 may include the method of example 28 or some other example herein, whereby after performing the network address translation of a downlink packet, the NAT device steers the downlink packet towards the N6 interface of the UPF-PSA.
  • Example B30 may include a method comprising: receiving a service function path (SFP) ID to indicate a first SFP of a plurality of SFPs for service function chaining (SFC); and steering one or more traffic flows toward the first SFP based on the SFC ID.
  • SFP service function path
  • SFC service function chaining
  • Example B31 may include the method of example B30 or some other example herein, wherein the method further comprises receiving metadata associated with the SFP ID; and performing SFP encapsulation to include the metadata in an SFP encapsulation header.
  • Example B32 may include the method of example B30-B31 or some other example herein, wherein the SFP ID is associated with a service level agreement.
  • Example B33 may include the method of example B30-B32 or some other example herein, wherein the SFP ID and/or the metadata are received from a session management function (SMF).
  • SFP ID and/or the metadata are received from a session management function (SMF).
  • SMS session management function
  • Example B34 may include the method of example B30-B33 or some other example herein, wherein the method is performed by a user plane function (UPF) with SFC capability (UPF-SFC)
  • UPF user plane function
  • UPF-SFC user plane function with SFC capability
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples example Al -Al 9, B1-B34, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples example A1-A19, B1-B34, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples example A1-A19, B1-B34, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples example Al -Al 9, B1-B34, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples example A1-A19, B1-B34, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples example A1-A19, B1-B34, or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples example A1-A19, B1-B34, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples example A1-AI9, B1-B34, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples example Al- A19, B1-B34, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples example A1-A19, B1-B34, or portions thereof
  • Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples example Al- A19, B1-B34, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • Gateway Function Premise Measurement CHF Charging 50 Equipment 85 CSI-RS CSI
  • Conditional Access Network Multiple Access Mandatory Cloud RAN CSMA/CA CSMA CMAS Commercial CRB Common with collision Mobile Alert Service 65 Resource Block 100 avoidance CMD Command CRC Cyclic CSS Common Search CMS Cloud Redundancy Check Space, Cell- specific Management System CRI Channel-State Search Space CO Conditional Information Resource CTF Charging Optional 70 Indicator, CSI-RS 105 Trigger Function CTS Clear-to-Send DSL Domain Specific 70 ECSP Edge CW Codeword Language. Digital Computing Service CWS Contention Subscriber Line Provider Window Size DSLAM DSL EDN Edge D2D Device-to- 40 Access Multiplexer Data Network Device DwPTS 75 EEC Edge
  • E-UTRAN Evolved FDM Frequency Management System UTRAN Division eNB evolved NodeB, EV2X Enhanced V2X Multiplex E-UTRAN Node B F1AP Fl Application FDMA F requency EN-DC E- 40 Protocol 75 Division Multiple UTRA-NR Dual Fl-C Fl Control plane Access
  • E-UTRA Evolved FDD Frequency Network UTRA 70 Division Duplex GGSN Gateway GPRS 35 GTP GPRS Tunneling 70 HSS Home Support Node Protocol Subscriber Server GLONASS GTP-UGPRS HSUPA High
  • NodeB Hybrid Block centralized unit 50 Automatic 85 ICCID Integrated gNB-DU gNB- Repeat Request Circuit Card distributed unit, Next HANDO Handover Identification
  • HSDPA High IE Information
  • LWIP LTE/WLAN 65 service Single MIMO Multiple Input
  • MPLS MultiProtocol NAI Network Access Connectivity Label Switching 60 Identifier 95 NM Network MS Mobile Station NAS Non-Access Manager MSB Most Significant Stratum, Non- Access NMS Network Bit Stratum layer Management System MSC Mobile NCT Network N-PoP Network Point Switching Centre 65 Connectivity Topology 100 of Presence MSI Minimum NC-JT NonNMIB, N-MIB System coherent Joint Narrowband MIB
  • NPUSCH wake-up signal Primary CC
  • PDU Protocol Data RACH reference signal Unit 50 PRB Physical PTT Push-to-Talk
  • PEI Permanent resource block 85 PUCCH Physical Equipment PRG Physical Uplink Control
  • P-GW PDN Gateway Services 90 Channel PHICH Physical Proximity-Based QAM Quadrature hybrid-ARQ indicator Service Amplitude channel PRS Positioning Modulation
  • PHY Physical layer 60 Reference Signal QCI QoS class of PLMN Public Land PRR Packet 95 identifier Mobile Network Reception Radio QCL Quasi co ⁇
  • SCC Secondary 50 Storage Function 85 SL Sidelink Component Carrier, SDT Small Data SLA Service Level Secondary CC Transmission Agreement
  • Radio Network 45 Resource Identifier 80 VM Virtual Machine
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • user equipment or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to an SS/PBCH block.
  • Primary Cell refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Secondary Cell refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers modes de réalisation de la présente invention concernent des techniques d'exposition de service à des tiers pour un chaînage de fonctions de service (SFC) dans un réseau cellulaire sans fil. Par exemple, des modes de réalisation concernent des techniques de prise en charge de SFC dans un système 5G (5GS) qui permet à un tiers de confiance de demander de manière dynamique qu'un ensemble spécifique d'un ou plusieurs flux de trafic (par exemple un flux identifié par l'intermédiaire d'un filtre de paquets, ou tout le trafic d'un UE spécifique, ou tout le trafic d'un groupe d'UE) soit dirigé vers un trajet de fonction de service (SFP) tel que demandé par le tiers. Dans certains modes de réalisation, des métadonnées peuvent être ajoutées dans le SFP, par exemple, tel que demandé par le tiers. D'autres modes de réalisation peuvent faire l'objet d'une description et de revendications.
PCT/US2023/065005 2022-03-28 2023-03-27 Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers WO2023192832A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202380023608.3A CN118765519A (zh) 2022-03-28 2023-03-27 具有对第三方的服务暴露的无线蜂窝系统中的服务功能链锁

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263324309P 2022-03-28 2022-03-28
US63/324,309 2022-03-28
US202263338174P 2022-05-04 2022-05-04
US63/338,174 2022-05-04

Publications (1)

Publication Number Publication Date
WO2023192832A1 true WO2023192832A1 (fr) 2023-10-05

Family

ID=88203409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/065005 WO2023192832A1 (fr) 2022-03-28 2023-03-27 Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers

Country Status (1)

Country Link
WO (1) WO2023192832A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160134531A1 (en) * 2014-11-11 2016-05-12 Broadcom Corporation Network Based Service Function Chaining
US20180309689A1 (en) * 2017-04-19 2018-10-25 Cisco Technology, Inc. Latency reduction in service function paths
US20190222521A1 (en) * 2016-09-30 2019-07-18 Nokia Solutions And Networks Oy Controlling service function chaining
WO2022006109A1 (fr) * 2020-06-29 2022-01-06 Intel Corporation Services de chaînage de fonctions de service dans un réseau de données de bord et des réseaux 5g

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160134531A1 (en) * 2014-11-11 2016-05-12 Broadcom Corporation Network Based Service Function Chaining
US20190222521A1 (en) * 2016-09-30 2019-07-18 Nokia Solutions And Networks Oy Controlling service function chaining
US20180309689A1 (en) * 2017-04-19 2018-10-25 Cisco Technology, Inc. Latency reduction in service function paths
WO2022006109A1 (fr) * 2020-06-29 2022-01-06 Intel Corporation Services de chaînage de fonctions de service dans un réseau de données de bord et des réseaux 5g

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMAR SHAILENDRA: "Service Function Chaining Support in Edge Data Networks", 3GPP TSG-SA6 MEETING 46-E, S6-212519, 10 November 2021 (2021-11-10), XP052182277 *

Similar Documents

Publication Publication Date Title
US20230163984A1 (en) User equipment (ue) route selection policy (usrp) ue in an evolved packet system (eps)
EP4271068A1 (fr) Support pour le transfer d'une configuration de mesure pour positionner en rrc inactive dans un noeud de réseau d'accès radio de prochaine génération désagrégé (ng-ran)
US20230269057A1 (en) Unified transmission configuration indicator (tci) framework for multi-transmission-reception point (trp) operation
US20240237082A1 (en) Using physical random access channel (prach) to identify multiple features and combinations of features
WO2022197678A1 (fr) Configuration de signaux de référence de sondage pour commutation d'antenne et commutation de porteuse
US20240155503A1 (en) Spatial relationship and power control configuration for uplink transmissions
WO2022174073A1 (fr) Facturation convergente pour la périphérie permettant l'utilisation des ressources et le transfert du contexte d'application
US20230155781A1 (en) User equipment behavior and requirements for positioning measurement without gap
US20240235775A1 (en) Configuration and collision handling for simultaneous uplink transmission using multiple antenna panels
US20240224268A1 (en) Rate-matching for transport block processing over multiple slots for physical uplink shared channel
US20240204931A1 (en) Multi-cell communication with multi-pdsch/pusch scheduling via a single dci
US20240188097A1 (en) Default beam operations for uplink transmissions
WO2023018779A1 (fr) Support d'accès direct à la mémoire distante (rdma) dans des réseaux cellulaires
WO2022170213A1 (fr) Architecture de communication et de système informatique centrée sur les données
WO2022155302A2 (fr) Exigence de retard pour transfert intercellulaire avec une cellule secondaire primaire (pscell)
WO2022169716A1 (fr) Systèmes et procédés d'indication de formation de faisceau
US20240251274A1 (en) Pre-configured measurement gap status indication to a user equipment (ue)
US20240235797A1 (en) Transmission configuration indicator (tci) chain enhancements for new radio systems
EP4271042A1 (fr) Changement de cellule ps conditionnel inter-sn à libération-17 (rel-17) de noeud secondaire (sn)
US20240214158A1 (en) Enhanced non-codebook-based uplink transmissions in wireless cellular network
US20240235772A1 (en) Collision handling for sounding reference signal (srs) transmission
US20230163916A1 (en) Techniques for ue positioning measurement in rrc_inactive or rrc_idle
WO2023192832A1 (fr) Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers
WO2023178091A1 (fr) Signal de référence de démodulation (dmrs) amélioré pour transmission en liaison montante
WO2023154691A1 (fr) Communication de microservice et déchargement informatique par l'intermédiaire d'un maillage de service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23781994

Country of ref document: EP

Kind code of ref document: A1