WO2022159400A1 - Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré - Google Patents

Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré Download PDF

Info

Publication number
WO2022159400A1
WO2022159400A1 PCT/US2022/012819 US2022012819W WO2022159400A1 WO 2022159400 A1 WO2022159400 A1 WO 2022159400A1 US 2022012819 W US2022012819 W US 2022012819W WO 2022159400 A1 WO2022159400 A1 WO 2022159400A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
cnc
packet delay
qos monitoring
monitoring
Prior art date
Application number
PCT/US2022/012819
Other languages
English (en)
Inventor
Honglei Miao
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
Publication of WO2022159400A1 publication Critical patent/WO2022159400A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0858—One way delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0864—Round trip delays

Definitions

  • This disclosure generally relates to wireless communications and, more particularly, to quality of service monitoring in integrated cellular time sensitive bridged network.
  • New radio (NR) radio access technology may provide ultra-reliable low latency communication (URLLC).
  • URLLC services comprise a wide range of use cases from augmented reality (AR) and/or virtual reality (VR) to industrial automation and may require different levels of quality of service and a different combination of reliability and latency.
  • AR augmented reality
  • VR virtual reality
  • FIG. 1 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4 depicts an illustrative schematic diagram for a control frame for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 illustrates an example method, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 illustrates an example network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 illustrates an example wireless network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 illustrates an example of a computing system, in accordance with one or more example embodiments of the present disclosure.
  • 3GPP TS 22.104 specification describes a challenging class of vertical applications, namely cyber-physical control applications, which require very high level of communication service availability.
  • Real-time industry Ethernet is one of the established wireline communication technologies for cyber-physical control applications, and TS 22.104 specification specifies the requirements that 5G systems must meet to support real-time Ethernet.
  • the most important sets of industry use cases with their varying demands on the communications network can include Motion control; Control-to-Control communication, Control-to- sensor/actuator communications, Mobile robots and automated guided vehicles (AGVs) Closed- loop process control, etc.
  • the 5G system can be integrated with the external industrial Ethernet as a time sensitive network (TSN) bridge.
  • TSN time sensitive network
  • This “logical” TSN bridge includes TSN Translator functionality for interoperation between TSN Ethernet system and 5G System for both user plane and control plane.
  • 5GS TSN translator functionality consists of Device-side TSN translator (DS-TT) and Network-side TSN translator (NW-TT).
  • the TSN application function (AF) provides the control plane translator functionality for the integration of the 5GS with a TSN network, e.g. the interactions with the centralized network configuration (CNC).
  • CNC centralized network configuration
  • 5GS specific procedures operated in 5G core network (CN) and radio access network (RAN), and wireless communication links, etc. remain hidden from the external industry TSN bridged network.
  • the 5GS provides TSN ingress and egress ports via DS-TT and NW-TT.
  • NW-TT and DS-TT optionally support link layer connectivity discovery and reporting as defined in IEEE standard 802.1 AB for discovery of Ethernet devices attached to NW-TT and DS-TT, respectively.
  • QoS monitoring requirements specified for URLLC services and vertical automation communication services should be supported by 5G system.
  • a 5G system may be comprised of a core network and radio access network.
  • a UE may be considered as part of the radio access network.
  • a packet transmission from the controller located in a data network outside of the 5G system may send this packet first to an interface between a 5G system and the external data network. Basically, this interface is a 5G network gateway.
  • a 5G network may provide an interface to the application for QoS monitoring (e.g. to initiate QoS monitoring, request QoS parameters, events, logging information, etc.). And the 5G system may be able to provide real time QoS parameters and events information to an authorized application.
  • QoS monitoring e.g. to initiate QoS monitoring, request QoS parameters, events, logging information, etc.
  • the 5G system may be able to provide real time QoS parameters and events information to an authorized application.
  • Various embodiments herein provide methods to realize QoS monitoring process for integrated 5G-TSN bridged network.
  • the CNC managing industry TSN bridged Ethernet interacts with the future factory application (FFA) server in 5GS to (un)subscribe QoS monitoring events which are further forwarded by factory application enabler (FAE) server and service enabler architecture layer (SEAL) server in 5G AF to the network exposure function (NEF) providing QoS monitoring capability specified in TS 23.502.
  • FFAE factory application enabler
  • SEAL service enabler architecture layer
  • NEF network exposure function
  • monitoring capability on DS-TT port transmission rate which can vary due to change of channel condition and/or co-channel interference level, is also proposed to be provided by NEF to CNC to enable more efficient traffic shaping algorithm among those TSN and non-TSN traffic mapped to the same DS-TT.
  • NEF Network Engineering Function
  • the SEAL consists of a common set of services (e.g. group management, location management) and reference points.
  • the SEAL offers its services to the vertical application layer (VAL).
  • the SEAL server(s) may communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system.
  • the SEAL server interacts with the VAL user database for storing and retrieving user profile over VAL-UDB reference point.
  • the SEAL server provides the server side functionalities corresponding to the specific SEAL service.
  • the SEAL server supports interactions with the VAL server(s).
  • the SEAL server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222.
  • a latency reduction system may relate to QoS monitoring in various applications such as industrial automation communications using 5G. Some of these applications have stringent service requirements in terms of latency or reliability.
  • controller to device or controller to control use cases For example, a controller to a sensor or actuator, communication is considered controller to device communication because the device can be a sensor or an actuator that collects data from the field and send the data back to the controller. In that case, when the device (e.g. sensor or an actuator) receives the control command from the controller it executes the received command.
  • These received commands could be control commands which when executed may provide some operation on the device.
  • some actuators may be installed on a robot and each actuator may be responsible for certain motion operations of a certain part of the robot.
  • a robot may contain many movable parts.
  • a controller may be understood to be located in a central control room running on a computer or a server that may be connected to the Internet or the data network using the Internet and that the industrial device such as a robot may be placed in a factory floor for example.
  • the robot may also be connected to the network using Ethernet using an Ethernet circuit installed on the robot.
  • the Ethernet circuit may detect an Ethernet packet which may include command control that may be encapsulated in the Ethernet packet detected by the Ethernet circuit on the robot.
  • the robot may comprise a central controller that receives these control commands and then distribute them to related moving parts of the robot.
  • 5G a robot may receive a control command using a wireless connection instead of a wired connection. Therefore, a robot may be equipped with a 5G UE.
  • Network exposure function provides QoS monitoring capability specified in on DL/UL or round-trip packet delay between UPF and 5G RAN/UE. Due to the change of system load and channel/interference condition experienced by 5G UE, it is envisioned that QoS monitoring capability on DS-TT port DL/UL transmission rate, can be also provided by NEF to enable more efficient rate adaptation and traffic shaping algorithm among those TSN and non-TSN traffic mapped to the same DS-TT. It remains open issues on the detailed signaling solution to support the QoS monitoring on DS-TT port DL/UL transmission rate in 5GS and the associated reporting to the related AF.
  • embodiments of the present disclosure are directed to realizing QoS monitoring and reporting of DS-TT port DL/UL transmission rate for a TSN PDU session.
  • all the data types used for QoS monitoring and reporting in the signaling messages communicated between SMF, UPF, AMF, RAN-node, AF, NEF, and policy and control function (PCF) are enhanced to incorporate DS-TT port DL/UL transmission rate as one possible QoS parameter to be monitored and reported to PCF or AF.
  • PCF policy and control function
  • CNC is capable of adjusting the rate adaption and traffic shaping algorithms of TSN bridges along the communication path of the TSN traffics associated with the PDU session with the concerned DS-TT port to optimize the network resources usages to take into account the overall TSN communication requirements in the network.
  • overall network resources in integrated 5G-TSN bridged network can be optimally managed by CNC in a unified and transparent manner.
  • service capability exposure function or network exposure function (NEF) can provide QoS guarantee status tracking capability specified for a subscribed application session comprised of one or several packet flows sharing the same QoS requirements and compatible traffic time characteristics. Due to the change of system load and channel/interference condition experienced by 5G UE, it is beneficial that the application server (AS) can be informed about the QoS guarantee status and adapt the QoS requirements of the traffic steam according to the achievable 5GS QoS capability. This can enable the optimal use of 5GS resource and information transmission capability. However, it remains open question how QoS adaptation can be realized by the AF interfacing the SCEF/NEF.
  • this disclosure provides embodiments to realize QoS adaptation for packet flows in a subscribed application session according to QoS guarantee status change reported by SCEF/NEF.
  • the packet flows of an application session that possesses the same QoS requirements in terms of packet loss rate and maximum packet delay and compatible transmission time characteristics in terms of periodicity and packet arrival time can be grouped into the same application session context (ASC) which can be established in SCEF.
  • ASC application session context
  • the desired QoS requirements e.g., corresponding to a particular QoS reference predefined in service level agreement (SLA), and a set of alternative QoS requirements, namely altQoSReference, can be also included in subscribed ASC.
  • SLA service level agreement
  • SCEF shall translate these requirements and forward them to the policy and charging function (PCF) which further communicates the requirements to the session management function (SMF).
  • PCF policy and charging function
  • SMF session management function
  • Embodiments include methods to enable QoS monitoring process for integrated 5G-TSN bridged network supporting future factory application (FFA) services with ultra-reliability and low latency communication (URLLC) requirements to be configured and established between centralized network configuration (CNC) entity managing the TSN bridged network and FFA server within 5GS.
  • FFA server communicates with FFA enabler (FAE) for QoS monitoring function (un)subscription, which further utilizes the QoS monitoring capabilities directly provided by the Network Exposure Function (NEF) or via the service enabler architecture layer (SEAE).
  • FFAE FFA enabler
  • NEF Network Exposure Function
  • SEAE service enabler architecture layer Due to the fact that QoS monitoring is not only useful for FFAs but also can be applicable for other vertical applications, it is beneficial to enable SEAL to support QoS monitoring functionality in addition to the existing network resource management capability.
  • the QoS monitoring process can configure QoS monitoring parameters as well as the QoS reporting methods per QoS flow and/or per 5GS transmission port, e.g., device side-TSN translator (DS-TT) port of the PDU session.
  • the QoS monitoring parameters can be bridge packet DL/UL or round-trip delay corresponding to a QoS flow, and port transmission rate of DS-TT of the PDU session.
  • QoS reporting method for the associated QoS monitoring parameter can be one of the following options: 1) one-time reporting upon the establishment of the PDU session, 2) periodic reporting, and 3) aperiodic event-triggered reporting with configurable threshold, e.g., reporting is triggered when measured packet delay is larger than configured threshold, or port transmission rate is smaller than the configured value.
  • the described methods realize QoS monitoring process for integrated 5G-TSN bridged network.
  • the CNC managing industry TSN bridged Ethernet interacts with the future factory application (FFA) server in 5GS to (un)subscribe QoS monitoring events which are further forwarded by factory application enabler (FAE) server and service enabler architecture layer (SEAL) server in 5G AF to the network exposure function (NEF) providing QoS monitoring capability specified in TS 23.502.
  • FFAE factory application enabler
  • SEAL service enabler architecture layer
  • NEF network exposure function
  • monitoring capability on DS-TT port transmission rate which can vary due to change of channel condition and/or co-channel interference level, is also proposed to be provided by NEF to CNC to enable more efficient traffic shaping algorithm among those TSN and non-TSN traffic mapped to the same DS-TT.
  • NEF Network Engineering Function
  • a CNC may be outside of the 5G system.
  • a controller may send control command to the CNC to effectuate a part of a robot.
  • the controller may need the control command to be transferred or executed at a predetermined propagation delay in the 5G system associated with the robot.
  • the 5G system may be viewed as a virtual bridge part of the TSN network.
  • the CNC may be responsible for the communication path between the controller and the robot in this example.
  • the CNC may require that the 5G system report on packet propagation delay. When a packet arrives at the 5G system that may be forwarded to the robot, the packet will go through the 5G gateway, the base station, and the UE.
  • a packet propagation delay may be produced by the 5G system from the time the packet arrives at the 5G gateway until the packet is received by the controller located in the robot.
  • the controller sending the control commands may require that the packets be transmitted within a certain threshold of the packet delay. Some parts of the packet propagation delay may be due to the wired network and some parts may be due to the 5G system.
  • the CNC may decide whether the packet propagation delay is within a certain threshold before sending the control command to be executed by the robot. In that sense, the CNC may request the 5G application function to monitor the packet propagation delay variation. If the packet propagation delay experienced by the 5G system is above a certain threshold, the 5G system should notify the CNC.
  • the SEAL function does not currently support QoS monitoring.
  • the CNC may send the QoS monitoring to the FFA server which needs to forward the request to the SEAL function, where the SEAL function interfaces with the 5G internal network function.
  • CNC entity managing the TSN bridged network can reconfigure the transmission rate of TSN streams from TSN end-station, e.g., TSN Talker/Listener station, and the traffic shaping algorithm parameters of per-stream filtering protocol (PSFP) in the connected upstream 5G-TSN bridges along the TSN stream communication path to be adapted to the new transmission rate of DS-TT port.
  • PSFP per-stream filtering protocol
  • the proposed methods realize QoS monitoring and reporting of DS-TT port DL/UL transmission rate for a TSN PDU session. Specifically, all the data types used for QoS monitoring and reporting in the signalling messages communicated between SMF, UPF, AMF, RAN-node, AF, NEF, and policy and control function (PCF) are enhanced to incorporate DS- TT port DL/UL transmission rate as one possible QoS parameter to be monitored and reported to PCF or AF.
  • PCF policy and control function
  • CNC is capable of adjusting the rate adaption and traffic shaping algorithms of TSN bridges along the communication path of the TSN traffics associated with the PDU session with the concerned DS-TT port to optimize the network resources usages to take into account the overall TSN communication requirements in the network.
  • overall network resources in an integrated 5G-TSN bridged network can be optimally managed by CNC in a unified and transparent manner.
  • some embodiments may include a TSN application server (TSN-AS) requesting to create an application session context (ASC) with required QoS in 5G service capability exposure function (SCEF).
  • TSN-AS TSN application server
  • ASC application session context
  • SCEF 5G service capability exposure function
  • One or several packet flows (stream), identified by the respective flow filter can be included in the requested ASC.
  • TSC time sensitive communication
  • SLA service level agreement
  • the SLA shall include a number of provisioned QoS references and the respective charging rate.
  • Each QoS reference defined in SLA can be comprised of a set of QoS parameters such as requested bandwidth in unit of bits/s, and maximum packet loss rate and maximum packet delay along the path from transmitter/talker to receiver/listener.
  • the application server can include a desired QoS reference and a list of alternative QoS references.
  • the desired QoS reference can correspond to a particular traffic transmission rate of the TSN transmitter to achieve the respective throughput/productivity.
  • alternative QoS references can correspond to other transmission rates of TSN talker than the rate configured in desired QoS reference so that TSN talker transmission rate can be adapted according to the changing UE achievable throughput due to the variation of radio channel condition and system load.
  • TSN talker can change the periodicity of transmission burst of frames while remaining the frame size unchanged.
  • the TSN talker can remain the periodicity of transmission burst of frames while changing the frame size.
  • the effective TSN talker transmission bandwidth can be adapted according to the achievable 5G TSN bridge QoS capability for the concerned UE connected to TSN listener.
  • the proposed embodiments realize QoS adaptation for packet flows in a subscribed application session according to QoS guarantee status change reported by SCEF/NEF.
  • the packet flows of an application session that possesses the same QoS requirements in terms of packet loss rate and maximum packet delay and compatible transmission time characteristics in terms of periodicity and packet arrival time can be grouped into the same application session context (ASC) which can be established in SCEF.
  • ASC application session context
  • the desired QoS requirements e.g., corresponding to a particular QoS reference pre-defined in service level agreement (SLA), and a set of alternative QoS requirements, namely altQoSReference, can be also included in subscribed ASC.
  • SLA service level agreement
  • altQoSReference can be also included in subscribed ASC.
  • SCEF shall translate these requirements and forward them to the policy and charging function (PCF) which further communicates the requirements to the session management function (SMF).
  • PCF policy and charging function
  • SMF session management function
  • FIG. 1 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • QoS monitoring process for integrated 5G-TSN bridged network can be configured and established between centralized network configuration (CNC) entity managing the TSN bridged network and FFA server within 5GS.
  • CNC centralized network configuration
  • FFA server communicates with FFA enabler (FAE) for QoS monitoring function (un)subscription, which further utilizes the QoS monitoring capabilities directly provided by the Network Exposure Function (NEF) or via the service enabler architecture layer (SEAL).
  • FFA FFA enabler
  • SEAL service enabler architecture layer
  • the QoS monitoring process can configure QoS monitoring parameters as well as the QoS reporting methods per QoS flow and/or per 5GS transmission port, e.g., device side-TSN translator (DS-TT) port of the PDU session.
  • the QoS monitoring parameters can be bridge packet DL/UL or round-trip delay corresponding to a QoS flow, and port transmission rate of DS-TT of the PDU session.
  • QoS reporting method for the associated QoS monitoring parameter can be one of the following options: 1) one-time reporting upon the establishment of the PDU session, 2) periodic reporting, and 3) aperiodic event-triggered reporting with configurable threshold, e.g., reporting is triggered when measured packet delay is larger than the configured threshold, or port transmission rate is smaller than the configured value.
  • QoS monitoring process communicated between the CNC entity of the TSN bridged network and 5GS based bridge can be established with the following steps:
  • Step-1 CNC of TSN bridged network sends a QoS monitoring subscribe request to the FFA server.
  • Step-2 The FFA communicates with the FAE sever and SEAL network resource management/monitoring (NRM) server to subscribe to the QoS monitoring process.
  • the SEAL NRM server interacts with the NEF to establish a QoS monitoring subscription in which the SEAL NRM server determines QoS parameters to be measured and associated reporting methods.
  • QoS parameters may include Downlink/Uplink (DL/UL) or roundtrip packet delay and/or DS-TT port transmission rate of the PDU session multiplexing multiple TSN streams/flows of one or more end-stations.
  • QoS reporting methods may include, 1) One-time reporting after the PDU session is established, 2) Periodic reporting with configured periodicity, and/or 3) Event triggered reporting with the configured reporting threshold and minimum waiting time between subsequent reports.
  • Step-3 The FFA server sends a QoS monitoring subscribe response to the CNC to confirm the subscribe request.
  • Step-4 When a QoS monitoring event is triggered and the SEAL NRM server is notified by the NEF, the SEAL NRM server sends a QoS monitoring notification to the FFA server.
  • Step-5 The FFA server notifies the CNC about the QoS monitoring event.
  • Step-6 When the CNC decides to unsubscribe for the QoS monitoring, the CNC sends a QoS monitoring unsubscribe request to the FFA server.
  • Step-7 The FFA server communicates with the SEAL NRM server to unsubscribe the QoS monitoring events.
  • the SEAL NRM server further interacts with the NEF to terminate the QoS monitoring subscription.
  • Step-8 The FFA server sends a QoS monitoring unsubscribe response to the CNC to confirm the unsubscribe request.
  • steps 4 and 5 are repeated when QoS monitoring events occur.
  • FIG. 2 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • the QoS monitoring process for integrated 5G-TSN bridged network supporting industrial automation services with ultra-reliability and low latency communication (URLLC) requirements can be configured to monitor the device-side TSN- translator (DS-TT) port DL/UL transmission rate variation caused by the change of system load, and/or UE’s radio channel/interference condition in addition to DL/UL or round-trip packet delay between UPF and 5G-RAN.
  • DS-TT device-side TSN- translator
  • centralized network configuration (CNC) entity managing the TSN bridged network can reconfigure the transmission rate of TSN streams from TSN end-station, e.g., TSN Talker/Listener station, and the traffic shaping algorithm parameters of per-stream filtering protocol (PSFP) in the connected upstream 5G-TSN bridges along the TSN stream communication path to be adapted to the new transmission rate of DS-TT port.
  • PSFP per-stream filtering protocol
  • the rate adaption algorithm in the TSN network can be timely realized according to the momentary variation of the transmission rate of 5G-TSN bridge ports.
  • DS-TT port DL/UL transmission rate shall be included in the QoS monitoring request data types in the related messages involved with SMF used for session management with QoS monitoring procedures illustrated in FIG. 2.
  • a latency reduction system may provide enhancements for PCF initiated SM policy association modification.
  • Type RequestedQosMonitoringParameter can be enhanced to include DS-TT port DL/UL transmission rate as highlighted in Table 1.
  • the parameter qosMonDecs of type QoSMonitoringData in type SmPolicyDecision carried in the message Npcf_SMPolicyControl_UpdateNotify transmitted from PCF to SMF as shown in FIG. 2 can include DS-TT port DL/UL transmission rate as QoS parameters to be monitored.
  • the reporting frequency associated with DS-TT port DL/UL transmission rate shall be also configured in the parameter repFreqs of qosMonDecs of type QoSMonitoringData in Npcf_SMPolicyControl_UpdateNotify message.
  • the QoS reporting method for DS-TT port DL/UL transmission rate can extend the QoS reporting method defined in the Type ReportingFrequency as in Table 2.
  • a latency reduction system may provide enhancements for Namf_Communication_NlN2MessageTransfer message
  • SMF shall send the message Namf_Communication_NlN2MessageTranfer via AMF to RAN-node, e.g., gNB, to include the configuration parameters associated with QoS monitoring operation.
  • NGAP message e.g., PDU session resource setup/modify/release request messages, etc
  • NGAP session management related messages can configure QoS monitoring operation by related parameters.
  • IE information element
  • QoS monitoring request and “QoS monitoring reporting frequency” are included in IE “QoS flow level QoS parameters” of “PDU session resource setup/modify request” messages to configure the QoS monitoring parameters and QoS monitoring reporting frequency.
  • parameter “QoS monitoring request” in IE “QoS flow level QoS parameters” shall be defined as new IE type “QoSMonitoringParameters” to include DS-TT port DL/UL transmission rate as highlighted in Table 3.
  • IE “QoS flow level QoS parameters” can be enhanced to include new parameter “QoS monitoring reporting method” of IE type “QoSMonitoringReportingMethod” which can be defined as ReportingFrequency in Table 2, and other related parameters to enable event triggered QoS monitoring reporting method. It should be noted that some QoS monitoring parameters, e.g., DS-TT port transmission rate, can be also defined in the PDU session level instead of QoS flow level.
  • a latency reduction system may provide enhancements for “PFCP Session Establishment/Modification Request” message.
  • SMF shall send the “PFCP Session Establishment Request” or “PFCP Session Modification Request” to UPF to include the configuration parameters associated with QoS monitoring operation.
  • PFCP session management related messages can configure QoS monitoring operation by related parameters.
  • information element (IE) “Requested QoS Monitoring” and “Reporting Frequency” are included in IE “QoS Monitoring per QoS flow Control Information” of IE “Create SRR” or “Update SRR” carried in “PFCP Session Establishment Request” or “PFCP Session Modification Request”, respectively, to configure the QoS monitoring parameters and QoS monitoring reporting frequency.
  • IE “Requested QoS Monitoring” in IE “QoS Monitoring per QoS flow Control Information” shall be enhanced to include DS-TT port DL/UL transmission rate as shown in Table 5.
  • Bit 1 - DL (Downlink) when set to “1”, this indicates a request for measuring the downlink packet delay from the UPF (PDU session anchor (PSA)) to the UE.
  • PDU session anchor PDU session anchor
  • Bit 2 - UL (Uplink) when set to “1”, this indicates a request for measuring the uplink packet delay from the UE to the UPF (PSA).
  • Bit 3 - RP (Round Trip): when set to “1”, this indicates a request for measuring the round trip packet delay between the UPF (PSA) and UE.
  • Bit 4 - DLR (DL Rate): when set to “1”, this indicates a request for measuring the DS- TT port DL transmission rate of the PDU session.
  • Bit 5 - ULR (UL Rate): when set to “1”, this indicates a request for measuring the DS- TT port UL transmission rate of the PDU session.
  • Bit 6 to 8 Spare, for future use and set to “0”.
  • FIG. 3 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • QoS monitoring process for integrated 5G-TSN bridged network supporting industrial automation services with ultra-reliability and low latency communication (URLLC) requirements can be configured to monitor the device-side TSN- translator (DS-TT) port DL/UL transmission rate variation caused by the change of system load, and/or UE’s radio channel/interference condition in addition to DL/UL or round-trip packet delay between UPF and 5G-RAN.
  • DS-TT device-side TSN- translator
  • centralized network configuration (CNC) entity managing the TSN bridged network can reconfigure the transmission rate of TSN streams from TSN end-station, e.g., TSN Talker/Listener station, and the traffic shaping algorithm parameters of per-stream filtering protocol (PSFP) in the connected upstream 5G-TSN bridges along the TSN stream communication path to be adapted to the new transmission rate of DS-TT port.
  • PSFP per-stream filtering protocol
  • the rate adaption algorithm in the TSN network can be timely realized according to the momentary variation of the transmission rate of 5G-TSN bridge ports.
  • DS-TT port DL/UL transmission rate shall be included in the QoS monitoring event subscription and notification data type in the related messages used for AF session with required QoS establishment and QoS monitoring procedure illustrated in FIG. 3.
  • a latency reduction system may provide enhancements for Nnef_AFsessionWithQoS_Create message.
  • Type RequestedQosMonitoringParameter in can be enhanced to include DS-TT port DL/UL transmission rate as highlighted in Table 6.
  • the parameter qosMonlnfo of type QoSMonitoringlnformation in type AsSessionWithQoSSubscription in carried in the message Nnef_AFSessionsWithQoS_Create request transmitted from AF to NEF as shown in FIG. 3 can include DS-TT port DL/UL transmission rate as QoS parameters to be monitored.
  • the reporting frequency associated with DS-TT port DL/UL transmission rate shall be also configured in the parameter repFreqs of qosMonlnfo in Nnef_AFSessionWithQoS_Create message.
  • the QoS reporting method for DS-TT port DL/UL transmission rate can extend the QoS reporting method defined in the Type ReportingFrequency as in Table 7. Table 6. Definition of Type RequestedQosMonitoringParameter.
  • a latency reduction system may provide enhancements for Npcf_PolicyAuthorization_Create/Subscribe message.
  • NEF shall send the message Npcf_PolicyAuthorization_Create and Npcf_PolicyAuthorization_Subscribe to PCF.
  • Either of the two messages can include a parameter defining events subscription of Type EventsSubscReqData which is comprised of, among others, a list of RequestedQosMonitoringParameters and parameter QosMonitoringlnformation.
  • Type QosMonitoringlnformation in shall also be enhanced to include DS-TT port DL/UL transmission rate related QoS monitoring parameters as shown in Table 8.
  • a latency reduction system may provide enhancements for Npcf_PolicyAuthorization_Notify message.
  • PCF shall send the message Npcf_PolicyAuthorization_Notify to NEF as shown in FIG. 3.
  • Type EventsNotification is transmitted in Npcf_PolicyAuthorization_Notify, and it includes a list of QoS monitoring reports defined as QosMonitoringReport.
  • QosMonitoringReport shall be enhanced to include DS-TT port DL/UL transmission rate as shown in Table 9.
  • a latency reduction system may provide enhancements for
  • the received QoS monitoring report in Table 4 shall be further forwarded by NEF to AF by using message Nnef_AFsessionWithQoS_Notify carrying UserPlaneNotificationData, which includes a list of QoS monitoring report defined as QosMonitoringReport. Similar to Table 3, QosMonitoringReport shall be also enhanced to include DS-TT port DL/UL transmission rate as shown in Table 10.
  • FIG. 4 depicts an illustrative schematic diagram for latency reduction, in accordance with one or more example embodiments of the present disclosure.
  • TSN-AS TSN application server
  • ASC application session context
  • SCEF 5 G service capability exposure function
  • One or several packet flows (stream), identified by the respective flow filter can be included in the requested ASC.
  • TSC time sensitive communication
  • SLA service level agreement
  • ASP application service provider
  • the SLA shall include a number of provisioned QoS references and the respective charging rate.
  • Each QoS reference defined in SLA can be comprised of a set of QoS parameters such as requested bandwidth in unit of bits/s, and maximum packet loss rate and maximum packet delay along the path from transmitter/talker to receiver/listener.
  • application server can include a desired QoS reference and a list of alternative QoS references.
  • the desired QoS reference can correspond to a particular traffic transmission rate of the TSN transmitter to achieve the respective throughput/productivity.
  • alternative QoS references can correspond to other transmission rates of TSN talker than the rate configured in desired QoS reference so that TSN talker transmission rate can be adapted according to the changing UE achievable throughput due to the variation of radio channel condition and system load.
  • TSN talker can change the periodicity of transmission burst of frames while remaining the frame size unchanged.
  • TSN talker can remain the periodicity of transmission burst of frames while changing the frame size.
  • the effective TSN transmission bandwidth can be adapted according to the achievable 5G TSN bridge QoS capability for the concerned UE connected to the TSN listener. The procedure to realize ASC configuration with QoS adaptation is illustrated in FIG. 4.
  • the AS session with QoS adaptation operation can be realized by the following steps:
  • Step-1 AS sends a Nnef_AFsessionWithQoS_Create request message comprised of resource data type AsSessionWithQoSSubscription to SCEF/NEF to establish an ASC for the packet flows with QoS requirements.
  • QoS references in this message correspond to the pre-defined QoS parameters specified in the SLA between ASP and operator.
  • QoS reference can include the maximum burst size of packet flow frames and the maximum packet delay.
  • QoS references in altQoSReferences can be arranged in an order of decreased maximum burst size of packet flows, this can help SCEF/NEF to reduce the QoS notification event reporting load.
  • an event of “QoS_GUARANTEED” is notified by SCEF for a particular QoS reference in the altQoSReference list
  • all the QoS references in the list with the smaller bandwidth demands can be also guaranteed by the 5GS.
  • an event of “QOS_NOT_GUARANTEED” is notified by SCEF for a particular QoS reference in the altQoSReference list, all the QoS references in the list with the larger bandwidth demands cannot be guaranteed by the 5GS either.
  • Step-2 SCEF verifies the QoS requirements with respect to the SLA, and forwards the requirements to policy and charging function (PCF). Upon approval from PCF, SCEF completes the authorization process for ASC establishment request.
  • PCF policy and charging function
  • Step-3 SCEF sends the Nnef_AFsessionWithQoS_Create response message to AS.
  • the response message includes the copy of resource data type AsSessionWithQoSSubscription sent in the request message and subscriptionld value to be used for modifying an active ASC when needed, e.g., for QoS adaptation purposes.
  • Step-4 When QoS guarantee status of 5GS for the packet flows in the ASC changes, e.g., desired QoS reference, as well as some alternative QoS references, cannot be guaranteed by 5GS.
  • SCEF sends a Nnef_AFsessionWithQoS_Notify message to AS to notify the QoS guarantee status change for packet flows in the particular ASC identified by subscriptionld.
  • the Nnef_AFsessionWithQoS_Notify message includes a resource data type of UserPlaneNotificationData which is comprised of a number of data type UserPlaneEventReports, each of which is associated with a specific notification event such as “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED” etc.
  • Step-5 Upon the reception of updated achievable QoS notification for a particular subscribed ASC, AS can determine a new desired QoS reference and an updated list of altQoSReferences, and send a Nnef_AFsessionWithQoS_Update message comprised of resource data type AsSessionWithQoSSubscription, which includes the new desired QoS reference and updated list of altQoSReferences, associated with the concerned ASC identified by subscriptionld to the SCEF.
  • the new desired QoS reference should be achieved by the 5GS, and the updated list of altQoSReferences should have better coverage for QoS adaptation for the current 5GS.
  • Step-6 SCEF performs the authorization process as in step-2 for the request to update ASC with required QoS from AS.
  • Step-7 SCEF sends the Nnef_AFsessionWithQoS_Update response message to AS.
  • the response message includes the copy of resource data type AsSessionWithQoSSubscription sent in the update request message to confirm the successful ASC update and resource allocation for the packet flows with updated QoS requirements.
  • FIG. 5 illustrates a flow diagram of illustrative process 500 for an illustrative latency reduction system, in accordance with one or more example embodiments of the present disclosure.
  • a device may establish a communication with a centralized network configuration (CNC), wherein the communication is associated with a 5G time-sensitive networking (TSN) bridged network
  • CNC centralized network configuration
  • TSN time-sensitive networking
  • the device may decode a subscribe quality of service (QoS) monitoring request received from the CNC.
  • QoS subscribe quality of service
  • the device may establish a QoS monitoring procedure at a service enabler architectural layer (SEAL) of a 5G system.
  • SEAL service enabler architectural layer
  • the 5G system supports future factory application (FFA) services.
  • FFA communicates with a factory application enabler (FAE) server.
  • FFA factory application enabler
  • the device may cause to send a subscribe QoS monitoring response to the CNC confirming the subscribe request.
  • the device may detect a QoS monitoring event, wherein the QoS monitoring event returns a QoS notification associated with QoS parameters.
  • the QoS parameters comprise downlink packet delay, uplink packet delay, or round-trip packet delay.
  • the QoS monitoring event is based on a comparison of a packet delay to a threshold, wherein the packet delay being greater than the threshold indicates to the CNC to refrain from sending control messages to the 5G system.
  • the QoS monitoring event is based on a comparison of a packet delay to a threshold, wherein the packet delay being less than the threshold indicates to the CNC to send control messages to the 5G system.
  • the device may decode a QoS monitoring unsubscribe request received from the CNC to unsubscribe from QoS monitoring.
  • FIGs. 6-8 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 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. However, 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 3 GPP 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, electronic/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 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 UE 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 CSLRS, 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 customers/subscribers (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 3GPP 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 servicebased 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. As used herein, 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 subscription-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 ETE 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 mmW ave 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.
  • FIG. 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.
  • FIG. 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.
  • 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 1 may include an apparatus comprising a processor configured to: establish a communication with a centralized network configuration (CNC), wherein the communication may be associated with a 5G time-sensitive networking (TSN) bridged network; decode a subscribe QoS monitoring request received from the CNC; establish a QoS monitoring procedure at a service enabler architectural layer (SEAL) of a 5G system; cause to send a subscribe QoS monitoring response to the CNC confirming the subscribe request; detect a QoS monitoring event, wherein the QoS monitoring event returns a QoS notification associated with QoS parameters; and a memory to store the QoS notification.
  • CNC centralized network configuration
  • TSN time-sensitive networking
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the 5G system supports future factory application (FFA) services.
  • FFA future factory application
  • Example 3 may include the apparatus of example 2 and/or some other example herein, wherein the FFA communicates with a factory application enabler (FAE) server.
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the QoS parameters comprise downlink packet delay, uplink packet delay, or round-trip packet delay.
  • FFA factory application enabler
  • Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being greater than the threshold indicates to the CNC to refrain from sending control messages to the 5G system.
  • Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being less than the threshold indicates to the CNC to send control messages to the 5G system.
  • Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processor may be further configured to decode a QoS monitoring unsubscribe request received from the CNC to unsubscribe from QoS monitoring.
  • Example 8 may include the apparatus of example 1 and/or some other example herein, wherein the processor comprises a baseband processor.
  • Example 9 may include a computer-readable storage medium comprising instructions to cause processing circuitry, upon execution of the instructions by the processing circuitry, to: establish a communication with a centralized network configuration (CNC), wherein the communication may be associated with a 5G time-sensitive networking (TSN) bridged network; decode a subscribe quality of service (QoS) monitoring request received from the CNC; establish a QoS monitoring procedure at a service enabler architectural layer (SEAL) of a 5G system; cause to send a subscribe QoS monitoring response to the CNC confirming the subscribe request; and detect a QoS monitoring event, wherein the QoS monitoring event returns a QoS notification associated with QoS parameters.
  • CNC centralized network configuration
  • TSN time-sensitive networking
  • SEAL service enabler architectural layer
  • Example 10 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the 5G system supports future factory application (FFA) services.
  • FFA future factory application
  • Example 11 may include the computer-readable storage medium of example 10 and/or some other example herein, wherein the FFA communicates with a factory application enabler (FAE) server.
  • FFA factory application enabler
  • Example 12 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the QoS parameters comprise downlink packet delay, uplink packet delay, or round-trip packet delay.
  • Example 13 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being greater than the threshold indicates to the CNC to refrain from sending control messages to the 5G system.
  • Example 14 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being less than the threshold indicates to the CNC to send control messages to the 5G system.
  • Example 15 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the processor may be further configured to decode a QoS monitoring unsubscribe request received from the CNC to unsubscribe from QoS monitoring.
  • Example 16 may include the computer-readable storage medium of example 9 and/or some other example herein, wherein the processing circuitry comprises a baseband processor.
  • Example 17 may include a method comprising: establishing, by one or more processors, a communication with a centralized network configuration (CNC), wherein the communication may be associated with a 5G time-sensitive networking (TSN) bridged network; decoding a subscribe quality of service (QoS) monitoring request received from the CNC; establishing a QoS monitoring procedure at a service enabler architectural layer (SEAL) of a 5G system; causing to send a subscribe QoS monitoring response to the CNC confirming the subscribe request; and detecting a QoS monitoring event, wherein the QoS monitoring event returns a QoS notification associated with QoS parameters.
  • CNC centralized network configuration
  • SEAL service enabler architectural layer
  • Example 18 may include the computer-readable storage medium of example 17 and/or some other example herein, wherein the 5G system supports future factory application (FFA) services.
  • FFA future factory application
  • Example 19 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the FFA communicates with a factory application enabler (FAE) server.
  • FFA factory application enabler
  • Example 20 may include the computer-readable storage medium of example 17 and/or some other example herein, wherein the QoS parameters comprise downlink packet delay, uplink packet delay, or round-trip packet delay.
  • Example 21 may include the computer-readable storage medium of example 17 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being greater than the threshold indicates to the CNC to refrain from sending control messages to the 5G system.
  • Example 22 may include the computer-readable storage medium of example 17 and/or some other example herein, wherein the QoS monitoring event may be based on a comparison of a packet delay to a threshold, wherein the packet delay being less than the threshold indicates to the CNC to send control messages to the 5G system.
  • Example 23 may include the computer-readable storage medium of example 17 and/or some other example herein, wherein the processor may be further configured to decode a QoS monitoring unsubscribe request received from the CNC to unsubscribe from QoS monitoring.
  • Example 24 may include an apparatus comprising means for performing any of the methods of examples 16-23.
  • Example 25 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 16- 23.
  • Example 26 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein.
  • Example 27 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 1-23, or any other method or process described herein.
  • Example 28 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 1-23, or any other method or process described herein.
  • Example 29 may include a method, technique, or process as described in or related to any of examples 1-23, or portions or parts thereof.
  • Example 30 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 1-23, or portions thereof.
  • Example 31 may include a signal as described in or related to any of examples 1-23, or portions or parts thereof.
  • Example 32 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 33 may include a signal encoded with data as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 34 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 1-23, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 35 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 1-23, or portions thereof.
  • Example 36 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 1-23, or portions thereof.
  • Example 37 may include a signal in a wireless network as shown and described herein.
  • Example 38 may include a method of communicating in a wireless network as shown and described herein.
  • Example 39 may include a system for providing wireless communication as shown and described herein.
  • Example 40 may include a device for providing wireless communication as shown and described herein.
  • 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, VO 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)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Cette divulgation décrit des systèmes, des procédés et des dispositifs liés à la surveillance de qualité de service (QoS) dans un réseau ponté sensible au temps cellulaire intégré. Un dispositif peut établir une communication avec une configuration de réseau centralisée (CNC), la communication pouvant être associée à un réseau ponté de réseautage sensible au temps (TSN) 5G. Le dispositif peut décoder une demande de surveillance de QoS d'abonnement reçue en provenance de la CNC. Le dispositif peut établir une procédure de surveillance de QoS au niveau d'une couche architecturale de facilitateur de service (SEAL) d'un système 5G. Le dispositif peut provoquer l'envoi d'une réponse de surveillance de QoS d'abonnement à la CNC confirmant la demande d'abonnement. Le dispositif peut détecter un événement de surveillance de QoS, l'événement de surveillance de QoS renvoyant une notification de QoS associée à des paramètres de QoS.
PCT/US2022/012819 2021-01-19 2022-01-18 Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré WO2022159400A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US202163138917P 2021-01-19 2021-01-19
US63/138,917 2021-01-19
US202163139517P 2021-01-20 2021-01-20
US63/139,517 2021-01-20
US202163143486P 2021-01-29 2021-01-29
US63/143,486 2021-01-29
US202163153760P 2021-02-25 2021-02-25
US63/153,760 2021-02-25

Publications (1)

Publication Number Publication Date
WO2022159400A1 true WO2022159400A1 (fr) 2022-07-28

Family

ID=82549649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/012819 WO2022159400A1 (fr) 2021-01-19 2022-01-18 Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré

Country Status (1)

Country Link
WO (1) WO2022159400A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115208808A (zh) * 2022-09-14 2022-10-18 北京智芯微电子科技有限公司 服务质量测试方法、装置以及芯片设备、存储介质
EP4319095A1 (fr) * 2022-08-02 2024-02-07 Mitsubishi Electric R&D Centre Europe B.V. Apprentissage automatique de modèle tsn pour systèmes 5g
WO2024027422A1 (fr) * 2022-08-04 2024-02-08 华为技术有限公司 Procédé de communication et appareil de communication
WO2024037423A1 (fr) * 2022-08-15 2024-02-22 华为技术有限公司 Procédé et appareil de commande de largeur de bande
WO2024102035A1 (fr) * 2022-11-07 2024-05-16 Telefonaktiebolaget Lm Ericsson (Publ) Rapport d'informations de caractéristiques sans fil pour une communication sensible au temps

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253936A1 (fr) * 2019-06-17 2020-12-24 Nokia Technologies Oy Entités de réseau et procédés de surveillance de qualité de service massive à la volée

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253936A1 (fr) * 2019-06-17 2020-12-24 Nokia Technologies Oy Entités de réseau et procédés de surveillance de qualité de service massive à la volée

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application layer support for Factories of the Future in 5G network; (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.745, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.2.0, 27 November 2020 (2020-11-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 73, XP051961787 *
LENOVO, MOTOROLA MOBILITY: "Update of Solution #16 on TSN policy negotiation", 3GPP DRAFT; S6-210073, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20210118 - 20210126, 13 January 2021 (2021-01-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051968727 *
MOTOROLA MOBILITY, LENOVO: "Proposal for solution to key issue #4 on TSN support", 3GPP DRAFT; S6-201254, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20200720 - 20200731, 27 July 2020 (2020-07-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051910134 *
ZTE CORPORATION: "New solution for key issue 4", 3GPP DRAFT; S6-200083, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. Hyderabad, India; 20200113 - 20200117, 6 January 2020 (2020-01-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051841637 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4319095A1 (fr) * 2022-08-02 2024-02-07 Mitsubishi Electric R&D Centre Europe B.V. Apprentissage automatique de modèle tsn pour systèmes 5g
WO2024029121A1 (fr) * 2022-08-02 2024-02-08 Mitsubishi Electric Corporation Procédé de regroupement de flux de données établis par un pont sans fil, système de communication et programme informatique
WO2024027422A1 (fr) * 2022-08-04 2024-02-08 华为技术有限公司 Procédé de communication et appareil de communication
WO2024037423A1 (fr) * 2022-08-15 2024-02-22 华为技术有限公司 Procédé et appareil de commande de largeur de bande
CN115208808A (zh) * 2022-09-14 2022-10-18 北京智芯微电子科技有限公司 服务质量测试方法、装置以及芯片设备、存储介质
WO2024102035A1 (fr) * 2022-11-07 2024-05-16 Telefonaktiebolaget Lm Ericsson (Publ) Rapport d'informations de caractéristiques sans fil pour une communication sensible au temps

Similar Documents

Publication Publication Date Title
US11871436B2 (en) Apparatus for UE measurement delay and granularity for new radio positioning measurement
WO2022159400A1 (fr) Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré
US11968559B2 (en) Apparatus and method for 5G quality of service indicator management
CN114443556A (zh) 用于ai/ml训练主机的人机交互的装置和方法
US20230141237A1 (en) Techniques for management data analytics (mda) process and service
US11792814B2 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
US11871460B2 (en) Domain name system (DNS)-based discovery of regulatory requirements for non-3GPP inter-working function (N3IWF) selection
US20230246689A1 (en) Support of simplified multiple input multiple output features for reduced capability user equipment in new radio systems
WO2022011527A1 (fr) Configuration et transmission de srs en multi-dci multi-trp et agrégation de porteuses
US11979894B2 (en) Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum
WO2022154961A1 (fr) Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie
WO2022240969A1 (fr) Procédés et appareil de rapport de marge de puissance pour transmissions à multiples points de réception de transmission (multi-trp)
CN114641044A (zh) 用在源基站、目标基站和用户设备中的装置
US20240237035A1 (en) Apparatus for ue measurement delay and granularity for new radio positioning measurement
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
EP4239479A1 (fr) Orchestration de services informatiques et de ressources pour des systèmes de prochaine génération
US20240187172A1 (en) Single trp and multiple trp dynamic switching for single dci based pusch transmissions
US20240214147A1 (en) Group-based channel state information reference signal (csi-rs) transmission
EP4207666A1 (fr) Configuration d'occasions de surveillance de pdcch pour capacité de surveillance de pdcch à intervalles multiples
WO2022155505A1 (fr) Techniques de déclenchement d'un signal de référence de sondage (srs) apériodique et flexible
WO2022216859A1 (fr) Configuration d'avance temporelle pour mobilité inter-cellules
WO2023049076A1 (fr) Procédés et appareil de configuration efficace de bande passante de services de synchronisation temporelle dans des systèmes 5g
WO2022217083A1 (fr) Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g
WO2022155098A1 (fr) Mesures de performance pour fonction d'exposition de réseau sur la fourniture de paramètres de service, la négociation de politique et l'établissement de connexion
WO2022032205A1 (fr) Rapport de défaillance de transfert conditionnel dans la minimisation des tests de conduite (mdt)

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: 22743042

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22743042

Country of ref document: EP

Kind code of ref document: A1