WO2022150004A1 - Procédé de traitement de mesures de qualité d'expérience (qoe) pour des applications sensibles au temps dans un réseau de communication sans fil - Google Patents

Procédé de traitement de mesures de qualité d'expérience (qoe) pour des applications sensibles au temps dans un réseau de communication sans fil Download PDF

Info

Publication number
WO2022150004A1
WO2022150004A1 PCT/SE2022/050002 SE2022050002W WO2022150004A1 WO 2022150004 A1 WO2022150004 A1 WO 2022150004A1 SE 2022050002 W SE2022050002 W SE 2022050002W WO 2022150004 A1 WO2022150004 A1 WO 2022150004A1
Authority
WO
WIPO (PCT)
Prior art keywords
qoe
tsc
wireless communications
network node
configuration
Prior art date
Application number
PCT/SE2022/050002
Other languages
English (en)
Inventor
Luca LUNARDI
Johan Rune
Gunnar HEIKKILÄ
Paul Schliwa-Bertling
Filip BARAC
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022150004A1 publication Critical patent/WO2022150004A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • Embodiments herein relate to a radio network node, a user equipment (UE) and methods performed therein regarding wireless communication. Furthermore, a computer program and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as handling one or more quality of experience (QoE) measurements for one or more time sensitive applications, in a wireless communications network.
  • QoE quality of experience
  • UEs also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB.
  • the service area or cell is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node.
  • the radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.
  • DL downlink
  • UL uplink
  • a Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment.
  • WCDMA wideband code division multiple access
  • HSPA High-Speed Packet Access
  • radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNC radio network controller
  • BSC base station controller
  • the RNCs are typically connected to one or more core networks.
  • the Evolved Packet System comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E- UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network.
  • SAE System Architecture Evolution
  • Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions.
  • a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
  • QoE measurements have been specified for LTE and UMTS and it is being specified for NR.
  • the purpose of the application layer measurements is to measure the end user experience when using certain applications.
  • QoE measurements for streaming services and for Mobility Telephony Service for IP multimedia subsystem (IMS), abbreviated as MTSI, services are supported.
  • Quality of Experience Measurement Collection enables configuration of application layer measurements in a UE and transmission of QoE measurement result files by means of radio resource control (RRC) signalling.
  • RRC radio resource control
  • Application layer measurement configuration received from operations, administration and maintenance (OAM) node or CN is encapsulated in a transparent container, which is forwarded to the UE in a downlink RRC message.
  • Application layer measurements received from UE's higher layer are encapsulated in a transparent container and sent to network in an uplink RRC message.
  • the result container is forwarded to a Trace Collector Entity (TCE).
  • TCE Trace Collector Entity
  • the measurements may be initiated towards RAN in management-based manner, i.e. , from an operations and maintenance (O&M) node in a generic way, e.g., for a group of UEs, or they may also be initiated in a signalling-based manner, i.e., initiated from CN to RAN, e.g., for a single UE.
  • O&M operations and maintenance
  • the configuration of the measurement includes the measurement details, which is encapsulated in a container that is transparent to RAN.
  • the measurement When initiated via the core network, the measurement is started towards a specific UE.
  • the "TRACE START" S1 AP message is used, which carries, among others, the details about the measurement configuration the application should collect, in the “Container for application layer measurement configuration” information element (IE), transparent to the RAN, and the details to reach the trace collection entity to which the measurements should be sent.
  • IE Container for application layer measurement configuration
  • RAN is not aware of when the streaming session is ongoing in the UE Access Stratum and is also not aware of when the measurements are ongoing. It is an implementation decision when RAN stops the measurements. Typically, it is done when the UE has moved outside the measured area.
  • One opportunity provided by legacy solution is also to be able to keep the QoE measurement for the whole session, even during handover situation.
  • the UE capability transfer is used to transfer UE radio access capability information from the UE to E-UTRAN.
  • Fig. 1 shows the UE capability transfer in E-UTRAN.
  • the UE-EUTRA-Capability IE is used to convey the E-UTRA UE Radio Access Capability Parameters and the Feature Group Indicators for mandatory features to the network.
  • the UE can include the “UE- EUTRA-Capability” IE.
  • the “UE-EUTRA-Capability “ IE may include the UE-EUTRA- Capability-v1530-1 E which can be used by the UE to indicate whether the UE supports or not supports QoE Measurement Collection for streaming services and/or MTSI services, as detailed in the “MeasParameters-v1530” encoding below.
  • the contribution change request (CR) 4297 (R2-2004624) for 3GPP TS 36.331 v16.0.0 at the 3GPP TSG RAN2 Meeting #110 proposed an extension of the “UE-EUTRA- Capability” IE that, within the “UE-EUTRA-Capability-v16xy-IE” may include a “measParameters-v16xy” comprising the qoe-Extensions-r16 IE.
  • the qoe-Extensions-r16 IE may be used to indicate whether the UE supports the release 16 extensions for QoE Measurement Collection, i.e., if the UE supports more than one QoE measurement type at a time and if the UE supports the signaling of withinArea, sessionRecordinglndication, qoe-Reference, temporaryStopQoE and restartQoE.
  • Fig. 2 shows an application layer measurement reporting in E-UTRAN.
  • a UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e., when measConfigAppLayer has been configured by E-UTRAN.
  • the RRCConnectionReconfiguration message is used to reconfigure the UE to setup or release the UE for Application Layer measurements. This is signaled in the measConfigAppLayer-15 IE within the “OtherConfig” IE.
  • the setup includes the transparent container measConfigAppLayerContainer which specifies the QoE measurement configuration for the Application of interest and the serviceType IE to indicates the Application (or service) for which the QoE measurements are being configured.
  • Supported services are streaming and MTSI.
  • the measConfigAppLayerToAddModList-r16 may be used to add or modify multiple QoE measurement configurations, up to maxQoE-Measurement-r16.
  • the measConfigAppl_ayerToReleaseUst-r16 IE may be used to remove multiple QoE measurement configuration, up to maxQoE-Measurement-r16.
  • the MeasReportAppLayer RRC message is used by the UE to send to the E-UTRAN node the QoE measurement results of an application, or service.
  • the service for which the report is being sent is indicated in the “serviceType” IE.
  • the “UE Application layer measurement configuration” IE is described in 3GPP TS 36.413 V16.3.0 and TS 36.423 v16.3.0.
  • the area scope parameter defines the area in terms of cells or Tracking Area/Routing Area/Location Area where the QoE Measurement Collection (QMC) shall take place. If the parameter is not present the QMC shall be done throughout the PLMN specified in PLMN target.
  • QMC QoE Measurement Collection
  • the area scope parameter in UMTS is either:
  • CGI cell global identity
  • RAI Routing Area identifier
  • LAI Location area identifier
  • the area scope parameter in LTE is either: list of cells, identified by E-UTRAN-CGI. Maximum 32 CGI can be defined. List of Tracking Area, identified by tracking area code (TAC). Maximum of 8 TAC can be defined.
  • the parameter is mandatory if area based QMC is requested.
  • the 5G System is extended to support Time Sensitive Communication (TSC) as defined in IEEE 802.1 Time Sensitive Networking (TSN) standards.
  • TSC Time Sensitive Communication
  • TSN Time Sensitive Networking
  • the 5G System is integrated with the external network as a TSN bridge.
  • This "logical" TSN bridge includes TSN Translator functionality for interoperation between TSN System and 5G System both for user plane and control plane.
  • 5G system (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
  • 5G System specific procedures in 5G Core (5GC) and RAN, wireless communication links, etc. remain hidden from the TSN network.
  • the 5GS provides TSN ingress and egress ports via DS-TT and NW-TT.
  • the system architecture view with 5GS appearing as TSN bridge is shown in below.
  • the Fig. 3 shows a system architecture view with 5GS appearing as TSN bridge.
  • An industrial automation (IA) network generally consists of two distinct time domain types: the global time domain and the working clock domains.
  • the global time domain is the time used for overall synchronization in the system, e.g., the factory. It is used to align operations and events chronologically.
  • Industrial automation uses the term universal time domain for the global time domain described in this document.
  • Global time is known as a synonym for universal time in industrial automation.
  • Global time is called wall clock in certain areas and standards.
  • the synchronization precision is typically £ 1ps. In some areas, a precision of £ 100 ps might be sufficient for the global time domain if a working clock with precision of £ 1 ps is available.
  • the assigned timescale is usually the International Atomic Time (TAI, Temps Atomique International), based on the Precision Time Protocol (PTP) epoch (starting from 1 January 197000:00:00 TAI). While there is usually only one global time, multiple global time domains are possible. Clock synchronization in the global time domain usually applies to all UEs within the industrial facility in industrial automation. That is, a global time domain covers usually the industrial facility.
  • the working clock domains are constrained in size. They often consist of a single machine or a set of neighbouring machines that physically collaborate. The restricted size allows very precise time synchronization (£1 ps) with efficient network components. Synchronization to a working clock is used to align, e.g., production lines, production cells, or machines/functional units. In these cases, the application synchronizes locally within the working clock domains, see Fig. 4, allowing precise synchronization with more efficient components.
  • a global time domain usually contains multiple working clock domains. The starting point (epoch) is the start of the working clock domain.
  • the assigned timescale of a working clock domain is arbitrary (timescale ARB). Therefore, different working clock domains may have different timescales and different synchronization accuracy and precision. Robots, motion control applications, numeric control, and any kind of clocked / isochronous application rely on the timescale of the working clock domain to make sure that actions are precisely interwoven as needed.
  • Clock synchronization in the working clock domain is constrained in size.
  • a specific working clock domain will contain only a subset of the UEs within the industrial facility. Often, the UEs of the working clock domain are connected to the same gNB. However, it is also possible that a working clock domain contains multiple neighboring gNBs. This depends on the actual use case and its vertical application.
  • a given device may be part of multiple time domains, leading to overlapping working clock domains.
  • Fig. 4 shows Global time domain and working clock domains.
  • Each TSN working domain sends its own generalized Precision Time Protocol (gPTP) messages.
  • the related Ethernet frames carry the gPTP multicast Ethernet destination medium access control (MAC) address and the gPTP message carries a specific precision time protocol (PTP) "domainNumber" that indicates the time domain they are referring to.
  • the NW-TT makes ingress timestamping (TSi) for the gPTP event messages of all domains and forwards the gPTP messages of all domains to the UEs.
  • TSi ingress timestamping
  • Interaction of working clock domains When members of different working clock domains interact, there are two possible options, see Fig. 5. Which option is used depends on the application and its requirements.
  • Fig. 5 shows working clock domain interactions "Merge” and "Separate”.
  • TSN-IA Time Sensitive Network Profile for Industrial Automation.
  • the IEC/IEEE 60802 joint project aims at specifying the TSN Profile for Industrial Automation (TSN-IA).
  • TSN-IA TSN Profile for Industrial Automation
  • Time-Sensitive Stream a stream of traffic, transmitted from a single source station, destined for one or more destination stations, where the traffic is sensitive to timely delivery, and requires bounded latency and bounded latency variation.
  • TSN domain a quantity of commonly managed industrial automation devices; a set of devices, their Ports, and the attached individual LANs that transmit Time-Sensitive Streams using TSN standards, which include Transmission Selection Algorithms, Preemption, Time Synchronization and Enhancements for Scheduled Traffic, and that share a common management mechanism. It is an administrative decision to group these devices.
  • Universal time domain gPTP domain used for the synchronization of universal time
  • Working clock domain gPTP domain used for the synchronization of a working clock
  • Isochronous domain stations of a common working clock domain with a common setup for the isochronous cyclic real-time traffic type
  • Cyclic real-time domain stations with a common setup for the cyclic real-time traffic type - even from different working clock domains or synchronized to a local timescale
  • Network cycle transfer time including safety margin, and application time including safety margin values are specific to a TSN domain and specify a repetitive behaviour of the network interfaces belonging to that TSN domain.
  • An object herein is to provide a mechanism to handle QoE measurements in an efficient manner in the wireless communications network.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication, for example, handling measurements, in a wireless communications network.
  • the UE receives from a radio network node, a configuration or a reconfiguration message, such as an RRC Reconfiguration message or alike, related to a QoE measurement configuration for a service type indicating an application using TSC over the wireless communications network.
  • a configuration or a reconfiguration message such as an RRC Reconfiguration message or alike, related to a QoE measurement configuration for a service type indicating an application using TSC over the wireless communications network.
  • the UE may receive a configuration message to set up, release, pause or resume the QoE measurement configuration or configurations for a service type or types indicating application or applications using TSC over the wireless communications network.
  • the object is achieved, according to embodiments herein, by providing a method performed by a radio network node for handling communication, for example, handling measurements, in a wireless communications network.
  • the radio network node transmits to a UE, a configuration message or a reconfiguration message, such as an RRC Reconfiguration message or alike, related to a QoE measurement configuration for a service type indicating an application using TSC over the wireless communications network.
  • the radio network node may transmit a configuration message to set up, release, pause or resume the QoE measurement configuration or configurations for service type or types indicating application or applications using TSC over the wireless communications network.
  • the object is achieved, according to embodiments herein, by providing a UE and a radio network node configured to perform the methods herein, respectively.
  • a UE for handling communication for example, handling measurements, in a wireless communications network.
  • the UE is configured to receive from a radio network node, a configuration or a reconfiguration message related to a QoE measurement configuration for a service type indicating an application using TSC over the wireless communications network.
  • a radio network node for handling communication in a wireless communications network is configured to transmit to a UE, a configuration message or a reconfiguration message related to a QoE measurement configuration for a service type indicating an application using TSC over the wireless communications network.
  • a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method above, as performed by the UE or the radio network node, respectively.
  • a computer-readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the method above, as performed by the UE or the radio network node, respectively.
  • Embodiments herein introduce support to collect QoE measurements for time sensitive applications which make use of TSC over the wireless communications network. For example, embodiments herein enable to conduct a QoE measurements campaign for applications requiring TSC, such as QoE measurements for industrial applications (IA), and may be used to monitor Service Level Agreement (SLA) fulfilment, thereby enabling an efficient use of TSC applications when communicating in the wireless communications network.
  • QoE measurements campaign for applications requiring TSC, such as QoE measurements for industrial applications (IA)
  • SLA Service Level Agreement
  • Fig. 1 shows signalling of a capability of a UE according to prior art
  • Fig. 2 shows signalling for a UE according to prior art
  • Fig. 3 shows an architecture for supporting a time sensitive communication according to prior art
  • Fig. 4 shows an overview of a wireless communications network for supporting different time domains according to prior art
  • Fig. 5 shows an overview of a wireless communications network for supporting different time domains according to prior art
  • FIG. 6 shows an overview depicting a wireless communications network according to embodiments herein;
  • Fig. 7 shows a combined signalling scheme and flowchart despciting embodiments herein;
  • Fig. 9 shows a flowchart depicting a method performed by a UE according to embodiments herein;
  • Fig. 10 shows a flowchart depicting a method performed by a radio network node according to embodiments herein;
  • Fig. 11 shows a block diagram depicting embodiments of a UE according to embodiments herein;
  • Fig. 12 shows a block diagram depicting embodiments of a radio network node according to embodiments herein;
  • Fig. 13 schematically illustrates a telecommunication network connected via an intermediate network to a host computer
  • Fig. 14 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection;
  • Figs. 15-18 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Embodiments herein relate to wireless communications networks in general.
  • Fig. 6 is a schematic overview depicting a wireless communications network 1.
  • the wireless communications network 1 comprises one or more RANs and one or more CNs.
  • the wireless communications network 1 may use one or a number of different technologies.
  • Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as, e.g., LTE or Wideband Code Division Multiple Access (WCDMA).
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • one or more UEs such as a UE 10 and a second UE 10’ are comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN).
  • AN Access Networks
  • RAN radio access network
  • CN core networks
  • a UE is exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal.
  • UE is a non-limiting term which means any terminal, robot, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.
  • NB-loT narrowband internet of things
  • MTC Machine Type Communication
  • D2D Device to Device
  • node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.
  • the wireless communications network 1 comprises a first radio network node 12 providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar.
  • the radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g.
  • a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the radio network node depending e.g. on the first radio access technology and terminology used.
  • gNB gNodeB
  • eNB evolved Node B
  • eNode B evolved Node B
  • NodeB a NodeB
  • a base transceiver station such as a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a
  • the radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device.
  • a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.
  • Embodiments herein enable to conduct QoE measurements for one or more applications requiring TSC.
  • QoE measurements for industrial applications can be used to monitor Service Level Agreement fulfilment.
  • UE terminal equipment
  • wireless terminal wireless terminal
  • QoE measurement configuration QoE measurement
  • QoE configuration QoE configuration
  • application layer measurement configuration application layer measurement configuration
  • Measurement Collection Entity MCE
  • Trace Collection Entity TCE
  • a RAN node which can be any of gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU- CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, IAB-node, IAB-donor DU, IAB-donor-CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O- eNB.
  • a RAN node which can be any of gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU- CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, IAB-node, IAB-donor DU, IAB-donor-CU, IAB-DU, IAB-MT, O-CU,
  • Special QoE metrics or parameters are defined for applications related to industrial use cases that use TSC over wireless communications network, e.g., via a 5GS.
  • Such QoE metrics may be part of the configuration for QoE measurements and may include one or more of the following:
  • Timestamp e.g., of an operation, expressed as time elapsed from the global time domain epoch or as the time elapsed from the working clock domain epoch
  • An indication or a list of indications to identify the distinguishing characteristics of the application e.g.: o isochronous application with guaranteed low latency o non-isochronous application with bounded latency
  • Residence time this metric follows the definition provided in IEEE Std 802. IAS- 2020: The duration of the time interval between the receipt of a time- synchronization event message by a PTP Instance and the sending of the next subsequent time-synchronization event message on another PTP Port of that PTP Instance. Residence time can be different for different PTP Ports. The term residence time applies only to the case where syncLocked is TRUE.
  • the performance statistics related to the achieved residence time stipulates that residence time shall not exceed 10 ms. Some examples of these performance statistics may include, but are not limited to: o The number of times within a certain period or the number of consecutive times that residence time requirement has been exceeded o Standard deviation, variance or mean of the difference between the required residence time and the achieved residence time
  • Pdelay messages including Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up, are used by transparent clocks to measure delays across the communications medium so that they can be compensated for by the system.
  • the IEEE Std 802.1AS-2020 stipulates that Pdelay turnaround time shall not exceed 10 ms.
  • Some examples of these performance statistics may include, but are not limited to: o The number of times within a certain period or the number of consecutive times that Pdelay turnaround time requirement has been exceeded o Standard deviation, variance or mean of the difference between the required Pdelay turnaround time and the achieved Pdelay turnaround time
  • the residence time can be the residence time at UE.
  • Frequency offset this metric follows the definition provided in IEEE Std 802. IAS- 2020: The offset between a measured frequency, fm, and a reference frequency, fr, as defined by (fm - fr), where fm is the frequency of the measured clock and fr is the frequency of the reference clock.
  • fr the frequency of the reference clock.
  • the measurement units of fm and fr are the same.
  • QoE metrics for at least one Internet of Things (loT) application associated with the UE e.g. an execution time of a task performed by a UE, an accuracy or precision of a measured parameter, a metric relating to a survival mode or downtime of a UE, a time between commands received by a UE, an identification of an event that caused the survival mode or downtime, a status of a UE after the survival mode or downtime.
  • LoT Internet of Things
  • Fig. 7 is a combined signalling scheme and flowchart depicting embodiments herein.
  • the radio network node 12 may obtain, e.g., receive from an OAM or 5GC node, a set of information to enable QoE measurements associated to one or more applications using TSC over the wireless communications network.
  • the set of information may comprise at least one of the following:
  • the radio network node 12 may further receive a communication request such as a protocol data unit (PDU) Session Resource Setup Request or requests or PDU Session Resource Modify Request or requests related information for which the PDU or PDUs to Setup or the PDU or PDUs to Modify are of type “Ethernet”. This may be an indication that the application is using TSC since UEs operating in TSC are often Ethernet devices, and associated PDU Sessions for such UEs have “PDU Session Type” IE set to “ethernet”. TSC Assistance Information, a part of TSC Traffic Characteristics, may be optionally included. Action 703. The radio network node 12 may then perform the setup of resources for the communication such as PDU Sessions according to the received PDU Session Resource Setup Request or Requests.
  • PDU protocol data unit
  • the radio network node 12 sends to one or multiple UEs a reconfiguration message such as an RRC Reconfiguration message, or alike, to set up, release, pause or resume the QoE measurement configuration or configurations for service type or types indicating one or more applications using TSC over the wireless communications network.
  • a reconfiguration message such as an RRC Reconfiguration message, or alike
  • the QoE measurement configuration can be the one that the radio network node 12 received from OAM or 5GC, or
  • the QoE measurement configuration can be prepared by the radio network node 12, e.g., according to lightweight QoE measurement, that is QoE measurements encoded in a format that is understandable by a Radio Access Network node using a RAN protocol, e.g., a representation of conventional QoE metric such as buffer level and initial playout delay.
  • the radio network node 12 may select the UE or UEs to send the QoE measurement configuration to, based on information implying that the UE 10 is running one or more applications using or requiring TSC, e.g.: o UE capability information, e.g., signaled from the UE together with other UE capability signaling.
  • o Packet inspection checking for certain application flows, e.g., based on transport protocol layer port numbers
  • o Packet inspection checking for TSC related protocols, such as PTP.
  • o Information received from the CN e.g., in the NGAP INITIAL UE CONTEXT SETUP REQUEST message,
  • the CN may in turn have based this on subscription information, quality of service (QoS) related signaling or packet inspection o QoS related signaling, e.g., QoS/quality of service class identifier (QCI)/5QI associated with a bearer or data flow.
  • QoS quality of service
  • QCI quality of service class identifier
  • TSCAI Presence of TSC Assistance Information
  • UE location information e.g., indirectly indicating that a UE is located in a certain factory area.
  • the UE 10 being connected to a Non-Public Network (NPN).
  • NPN Non-Public Network
  • the UE 10 receives from the radio network node 12 the reconfiguration message such as the RRC Reconfiguration message or alike to set up, release, pause or resume the QoE measurement configuration or configurations for one or more service types indicating one or more applications using TSC over the wireless communications network, see action 704.
  • the UE 10 may then send to the application layer, e.g., via attention (AT) commands, or specific application programming interface (API) the QoE measurement configuration related to the applications using TSC over the wireless communications network.
  • the UE 10 may perform the QoE measurements and may receive from the application layer, e.g., via AT commands, or specific API the QoE measurement reports related to the applications using TSC over the wireless communications network.
  • AT attention
  • API application programming interface
  • the UE 10 may send to the radio network node 12 one or more QoE measurement reports related to the application or applications using TSC over the wireless communications network.
  • the radio network node 12 may receive from the UE 10 a RRC Measurement Report message or messages, or alike, containing the QoE measurement report or reports for the service type or types related to application or applications using TSC over the wireless communications network.
  • the QoE measurement reports can be related to QoE configurations that the radio network node 12 received from OAM or 5GC or
  • the QoE measurement reports can be related to QoE configurations prepared according to lightweight QoE measurement.
  • the radio network node 12 may then check whether Service Level Agreement is fulfilled based on the received one or more QoE measurement reports. That is, check that the performance is according to an agreed level.
  • the Fig. 8 shows an example of two devices, UEs, operating in a factory, “Device 1” and “Device 2”.
  • each device can operate independently of each other and each device is part of a working clock domain, e.g. “Device 1” operates in working clock domain 1 at working clock 1, “Device 2” operates in working clock domain 2 at working clock 2.
  • the assigned tasks for the devices implies that Device 1 and Device 2 have to tightly collaborate and there is a need to merge the working clock domains. Time period with Device 1 and Device 2 operating at merged working clocks.
  • the devices are configured to perform QoE Measurement Collection, e.g., release, pause or resume the QoE measurement configuration, for a service type indicating an application using TSC over wireless communications network, wherein the QoE measurement configuration comprises one or more QoE metrics, see above.
  • QoE Measurement Collection e.g., release, pause or resume the QoE measurement configuration
  • the QoE measurement configuration comprises one or more QoE metrics, see above.
  • the two UEs can operate each one at individual clock when not interacting with each other, and use a merged clock when operating in tandem.
  • one UE may be a robot that moves to reach another device on an assembly line and when there, the UE has to work according to the clock that respect the assembly line.
  • QoE measurement may be used to measure how effectively the two devices work together.
  • the IE defines configuration information for the QoE Measurement Collection (QMC) function.
  • AT commands An example of implementation is provided below for the AT commands (3GPP TS 27.007), where the underlined and bold marked texts pertain to embodiments herein
  • This command allows control of the application level measurement configuration according to 3 GPP TS 25.331 [74] and 3 GPP TS 36.331 [86] and 3GPP TS 38.331[xx]
  • the set command controls the presentation of the unsolicited result code +C APPLE VMC: ⁇ app-meas_service_type>, ⁇ start- stop_reporting>[, ⁇ app-meas_config_file_length>, ⁇ app-meas_config-file>] providing data for the configuration. Refer subclause 9.2 for possible ⁇ err> values.
  • Read command returns the current value of ⁇ n>.
  • Test command returns values supported as a compound value.
  • ⁇ n> integer type. Disable and enable presentation of the unsolicited result code +CAPPLEVMC to the TE.
  • ⁇ app-meas_service_type> integer type. Contains the indication of what application that is target for the application level measurement configuration.
  • ⁇ app-meas_config-file> string of octets. Contains the application level measurement configuration file for the application indicated by the ⁇ app-meas_service_type>. The parameter shall not be subject to conventional character conversion as per +CSCS.
  • This command allows the MT to provide the application level measurement report according to
  • the method actions performed by the UE 10, such as an loT device or a robot, for handling communication in the wireless communications network 1 according to embodiments will now be described with reference to a flowchart depicted in Fig. 9. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Dashed boxes indicate optional features.
  • the UE 10 may be connected to a Non-Public Network (NPN).
  • NPN Non-Public Network
  • the UE 10 may transmit to the radio network node 12, a communication request indicating that a PDU Session to Setup or a PDU Session to Modify is of an ethernet type.
  • the communication request may comprise TSC Assistance Information.
  • the UE 10 may transmit a communication request such as a PDU Session Resource Setup Request or requests or PDU Session Resource Modify Request or requests indicating for which PDU or PDUs to Setup or PDU or PDUs to Modify are of type “Ethernet”.
  • TSC Assistance Information a part of TSC Traffic Characteristics, can be optionally included.
  • the UE 10 may receive from the radio network node 12, a communication request indicating that a PDU Session to Setup or a PDU Session to Modify is of an ethernet type.
  • a PDU Session can be setup or modified when the radio network node 12 requests to do so.
  • the UE 10 receives from the radio network node 12, the configuration or the reconfiguration message related to the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the configuration or reconfiguration message may be a configuration message to set-up, release, pause or resume the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the UE 10 may thus receive from the radio network node 12 the reconfiguration message such as an RRC Reconfiguration message, or alike, related to QoE measurement configuration for a service using TSC over wireless communications network. For example, a configuration message to set up, release, pause or resume the QoE measurement configuration or configurations for service type or types indicating application or applications using TSC over the wireless communications network.
  • the UE 10 may then send to the application layer or to the specific API, the QoE measurement configuration related to the application.
  • the UE 10 may send to the application layer, e.g., via AT commands, or specific API the QoE measurement configuration related to the applications using TSC over the wireless communications network.
  • the UE 10 may perform the QoE measurement based on the configuration or reconfiguration message.
  • the UE 10 may receive from the application layer or the specific API a QoE measurement report related to the application using TSC over the wireless communications network.
  • the UE 10 may perform the QoE measurements and/or may receive from the application layer, e.g., via AT commands, or the specific API the QoE measurement reports related to the applications using TSC over the wireless communications network.
  • the UE 10 may obtain the QoE measurement report.
  • the UE 10 may send to the radio network node 12 the QoE measurement report related to the application or applications using TSC over the wireless communications network.
  • the QoE measurement reports can be related to QoE configurations that the radio network node 12 received from OAM or 5GC or the QoE measurement reports can be related to QoE configurations prepared according to lightweight QoE measurement.
  • the radio network node 12 may obtain from an OAM node or a core network node, a set of information to enable QoE measurements associated to one or more applications using TSC over the wireless communications network.
  • the set of information may comprise at least one of the following:
  • the radio network node 12 may receive the communication request from the UE 10. It should be noted that the radio network node 12 may transmit to the UE 10, a communication request indicating that a PDU Session to Setup or a PDU Session to Modify is of an ethernet type. Action 1002. The radio network node 12 may then perform the setup of resources for the communication such as PDU Sessions according to the received communication request such as the PDU Session Resource Setup Request.
  • the radio network node 12 may select the UE to receive the configuration or reconfiguration message based on information implying that the UE is running an application using TSC. If the radio network node 12 chooses a UE 10 to send the QoE configuration to, i.e. , unless the QoE measurement configuration is signaling based, i.e., received from the CN, pointing out one or more specific UEs, the radio network node 12 may select the UE or UEs to send the QoE measurement configuration to, based on information implying that it/they is/are running applications using/requiring TSC, e.g.: o UE capability information, e.g., signaled from the UE together with other UE capability signaling.
  • o UE capability information e.g., signaled from the UE together with other UE capability signaling.
  • o Packet inspection checking for certain application flows, e.g., based on transport protocol layer port numbers
  • o Packet inspection checking for TSC related protocols, such as PTP.
  • o Information received from the CN e.g., in the NGAP INITIAL UE CONTEXT SETUP REQUEST message
  • the CN may in turn have based this on subscription information, quality of service (QoS) related signaling or packet inspection o QoS related signaling, e.g., QoS/quality of service class identifier (QCI)/5QI associated with a bearer or data flow.
  • QoS quality of service
  • QCI quality of service class identifier
  • Presence of TSC Traffic Characteristics IE associated with a QoS Flow in e.g., NGAP, F1AP orXnAP messages o ‘Presence of TSC Assistance Information (TSCAI) associated with a QoS Flow in, e.g., NGAP, F1AP orXnAP messages o Information about pre-configured 5Qls used for gPTP message transfer o UE location information, e.g., indirectly indicating that a UE is located in a certain factory area.
  • TSCAI Presence of TSC Assistance Information
  • the radio network node 12 transmits to the UE 10 the configuration or reconfiguration message related to the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the configuration or the reconfiguration message may be a configuration message to set-up, release, pause or resume the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the radio network node 12 may transmit the configuration message or the reconfiguration message such as an RRC Reconfiguration message, or alike, related to QoE measurement configuration for a service using TSC over the wireless communications network. For example, a configuration message to set up, release, pause or resume the QoE measurement configuration or configurations for service type or types indicating application or applications using TSC over wireless communications network.
  • the QoE measurement configuration can be the one that the radio network node 12 received from OAM or 5GC, or
  • the QoE measurement configuration can be prepared by the radio network node 12, e.g., according to lightweight QoE measurement.
  • the radio network node 12 may select the UE or UEs to send the QoE measurement configuration to, based on information implying that it/they is/are running applications using/requiring TSC, e.g.: o UE capability information, e.g., signaled from the UE together with other UE capability signaling.
  • o Packet inspection checking for certain application flows, e.g. based on transport protocol layer port numbers
  • o Packet inspection checking for TSC related protocols, such as PTP.
  • Information received from the CN e.g., in the NGAP INITIAL UE
  • the CN may in turn have based this on subscription information, quality of service (QoS) related signaling or packet inspection o QoS related signaling, e.g., QoS/quality of service class identifier (QCI)/5QI associated with a bearer or data flow.
  • QoS quality of service
  • QCI quality of service class identifier
  • Presence of TSC Traffic Characteristics IE associated with a QoS Flow in, e.g., NGAP, F1AP orXnAP messages o ‘Presence of TSC Assistance Information (TSCAI) associated with a QoS Flow in, e.g., NGAP, F1AP orXnAP messages o Information about pre-configured 5Qls used for gPTP message transfer o UE location information, e.g., indirectly indicating that a UE is located in a certain factory area.
  • TSCAI Presence of TSC Assistance Information
  • the UE 10 being connected to a Non-Public Network (NPN).
  • NPN Non-Public Network
  • the radio network node 10 may receive from the UE 10 a measurement report message comprising a QoE measurement report for the service type related to the application using TSC over the wireless communications network.
  • the radio network node 12 may receive from the UE 10 RRC Measurement Report message or messages, or alike, containing the QoE measurement report or reports for the service type or types related to application or applications using TSC over the wireless communications network.
  • the QoE measurement reports can be related to QoE configurations that the radio network node 12 received from OAM or 5GC; or
  • the QoE measurement reports can be related to QoE configurations prepared according to lightweight QoE measurement.
  • the radio network node 12 may then check whether Service Level Agreement is fulfilled based on the received measurement reports. That is, performance is according to an agreed level.
  • Fig. 11 is a block diagram depicting the UE 10 in two embodiments for handling communication in the wireless communications network 1 according to embodiments herein.
  • the UE 10 may comprise processing circuitry 1101, e.g., one or more processors, configured to perform the methods herein.
  • processing circuitry 110 e.g., one or more processors, configured to perform the methods herein.
  • the UE 10 may comprise a receiving unit 1102., e.g., a receiver or transceiver.
  • the UE 10, the processing circuitry 1101 and/or the receiving unit 1102 is configured receive from the radio network node 12, the configuration or reconfiguration message related to the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the UE 10, the processing circuitry 1101 and/or the receiving unit 1102 may be configured to receive configuration data from the radio network node 12. For example, a configuration message or a reconfiguration message such as an RRC Reconfiguration message, or alike, related to QoE measurement configuration for a service using TSC over wireless communications network.
  • the configuration or reconfiguration message may be the configuration message to set-up, release, pause or resume the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the UE 10 may comprise a transmitting unit 1103, e.g., a transmitter or a transceiver.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1103 may be configured to transmit to the radio network node 12, the communication request indicating that a PDU Session to Setup or a PDU Session to Modify is of an ethernet type.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1103 may be configured to transmit the communication request such as a PDU Session Resource Setup Request or Requests or PDU Session Resource Modify Request or Requests indicating for which PDU or PDUs to Setup or PDU or PDUs to Modify are of type “Ethernet”.
  • the communication request may comprise TSC Assistance Information.
  • TSC Assistance Information a part of TSC Traffic Characteristics, can be optionally included.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1103 may be configured to send to the application layer or to the specific API the QoE measurement configuration related to the application.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1103 may be configured to send to the application layer, e.g., via AT commands, or specific API the QoE measurement configuration related to the applications using TSC over the wireless communications network.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1103 may be configured to send to the radio network node 12, the QoE measurement report related to the application or applications using TSC over the wireless communications network.
  • a communication request indicating that a PDU Session to Setup or a PDU Session to Modify is of an ethernet type may be received from the radio network node 12.
  • the UE 10 may comprise a measuring unit 1104.
  • the UE 10, the processing circuitry 1101 and/or the measuring unit 1104 may be configured to perform a QoE measurement based on the configuration or reconfiguration message.
  • the UE 10, the processing circuitry 1101 and/or the measuring unit 1104 may be configured to receive from the application layer or the specific API the QoE measurement report related to the application using TSC over the wireless communications network.
  • the UE 10, the processing circuitry 1101 and/or the measuring unit 1104 may be configured to perform the QoE measurements and may receive from the application layer, e.g. via AT commands, or specific API the QoE measurement reports related to the applications using TSC over wireless communications network.
  • the UE 10 may comprise a memory 1105.
  • the memory 1105 comprises one or more units to be used to store data on, such as data packets, configurations, QoE information, measurements, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the UE may comprise a communication interface 1108 such as a transmitter, a receiver, a transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the UE 10 are respectively implemented by means of, e.g., a computer program product 1106 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer program product 1106 may be stored on a computer-readable storage medium 1107, e g. a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 1107, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer-readable storage medium may be a transitory or a non-transitory computer- readable storage medium.
  • embodiments herein may disclose a UE 10 for handling communication in a wireless communications network, wherein the UE 10 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE 10 is operative to perform any of the methods herein.
  • Fig. 12 is a block diagram depicting the radio network node 12 in two embodiments for handling communication in the wireless communications network 1 according to embodiments herein.
  • the radio network node 12 may comprise processing circuitry 1201, e.g. one or more processors, configured to perform the methods herein.
  • the radio network node 12 may comprise a transmitting unit 1202, e.g. a transmitter or a transceiver.
  • the radio network node 12, the processing circuitry 1201 and/or the transmitting unit 1202 is configured to transmit to the UE 10 the configuration or reconfiguration message related to the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the configuration or reconfiguration message may be a configuration message to set-up, release, pause or resume the QoE measurement configuration for the service type indicating the application using TSC over the wireless communications network.
  • the radio network node 12, the processing circuitry 1201 and/or the transmitting unit 1202 may be configured to select the UE to receive the configuration or reconfiguration message based on information implying that the UE is running an application using TSC.
  • the radio network node 12, the processing circuitry 1201 and/or the transmitting unit 1202 may be configured to transmit the configuration message or the reconfiguration message such as an RRC Reconfiguration message, or alike, related to QoE measurement configuration for a service using TSC over wireless communications network. For example, a configuration message to set up, release, pause or resume the QoE measurement configuration or configurations for service type or types indicating application or applications using TSC over wireless communications network.
  • the QoE measurement configuration can be the one that the radio network node 12 received from OAM or 5GC, or
  • the QoE measurement configuration can be prepared by the radio network node 12, e.g. according to lightweight QoE measurement.
  • the radio network node 12 may select the UE or UEs to send the QoE measurement configuration to, based on information implying that it/they is/are running applications using/requiring TSC, e.g.: o UE capability information, e.g. signaled from the UE together with other UE capability signaling. o Packet inspection, checking for certain application flows, e.g. based on transport protocol layer port numbers o Packet inspection, checking for TSC related protocols, such as PTP. o Information received from the CN, e.g. in the NGAP INITIAL UE CONTEXT SETUP REQUEST message)
  • the CN may in turn have based this on subscription information, quality of service (QoS) related signaling or packet inspection o QoS related signaling, e.g. QoS/quality of service class identifier (QCI)/5QI associated with a bearer or data flow.
  • QoS quality of service
  • QCI quality of service class identifier
  • TSCAI Presence of TSC Assistance Information
  • UE location information e.g., indirectly indicating that a UE is located in a certain factory area.
  • the radio network node 12 may comprise a receiving unit 1203.
  • the radio network node 12, the processing circuitry 1201 and/or the receiving unit 1203 may be configured to obtain from the OAM node or a core network node, the set of information to enable QoE measurements associated to the one or more applications using TSC over the wireless communications network.
  • the set of information comprises at least one of the following: information or a set of information containing the QoE measurement configuration for the one or more applications using TSC over the wireless communications network; an indication of an area scope where the QoE measurement configuration is valid; an indication of one or more measurement collection entities towards which the radio network node should send QoE measurements reports for the one or more applications; and information concerning a service type indicating the one or more applications using TSC over the wireless communications network.
  • the radio network node 12, the processing circuitry 1201 and/or the receiving unit 1203 may be configured to obtain, e.g., receive from OAM or 5GC node a set of information to enable QoE measurements associated to one or more applications using TSC over the wireless communications network.
  • the set of information comprises at least one of the following:
  • the radio network node 12, the processing circuitry 1201 and/or the receiving unit 1203 may be configured to receive the communication request from the UE 10.
  • the radio network node 12, the processing circuitry 1201 and/or the receiving unit 1203 may be configured to receive from the UE 10, the measurement report message comprising the QoE measurement report for the service type related to the application using TSC over the wireless communications network.
  • the QoE measurement reports can be related to QoE configurations that the radio network node 12 received from OAM or 5GC or
  • the QoE measurement reports can be related to QoE configurations prepared according to lightweight QoE measurement.
  • the radio network node 12 may comprise a setup unit 1204.
  • the radio network node 12, the processing circuitry 1201 and/or the setup unit 1204 may be configured to perform the setup of resources for the communication such as PDU Sessions according to the received communication request such as a PDU Session Resource Setup Request.
  • the radio network node 12 may comprise a memory 1205.
  • the memory 1205 comprises one or more units to be used to store data on, such as data packets, QoE configurations, measurement reports, allocated resources, thresholds, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the radio network node 12 may comprise a communication interface 1208 such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the radio network node 12 are respectively implemented by means of, e.g., a computer program product 1206 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12.
  • the computer program product 1206 may be stored on a computer-readable storage medium 1207, e.g., a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 1207, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12.
  • the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.
  • embodiments herein may disclose a radio network node 12 for handling communication in a wireless communications network, wherein the radio network node 12 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio network node 12 is operative to perform any of the methods herein.
  • radio network node can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node.
  • network nodes are NodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.
  • MCG Master cell group
  • SCG Secondary cell group
  • MSR multi-standard radio
  • wireless device or UE refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system.
  • UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.
  • Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • signals e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • ASIC application-specific integrated circuit
  • processors or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Other hardware, conventional and/or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.
  • DSP digital signal processor
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 being an example of the UE 10, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 13 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Fig.14) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Fig.14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331 , which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Fig. 14 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Fig. 13, respectively.
  • the inner workings of these entities may be as shown in Fig. 14 and independently, the surrounding network topology may be that of Fig. 13.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the performance since applications using TSC may be handled more efficiently and thereby provide benefits such as reduced user waiting time, and better responsiveness.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • Fig. 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • Fig. 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Fig. 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon certains modes de réalisation, l'invention concerne un procédé exécuté par un UE (10) pour traiter la communication dans un réseau de communication sans fil. L'UE (10) reçoit d'un nœud de réseau radio (12), un message de configuration ou de reconfiguration relatif à une configuration de mesure de QoE pour un type de service indiquant une application à l'aide de TSC sur le réseau de communication sans fil.
PCT/SE2022/050002 2021-01-05 2022-01-03 Procédé de traitement de mesures de qualité d'expérience (qoe) pour des applications sensibles au temps dans un réseau de communication sans fil WO2022150004A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163133802P 2021-01-05 2021-01-05
US63/133,802 2021-01-05

Publications (1)

Publication Number Publication Date
WO2022150004A1 true WO2022150004A1 (fr) 2022-07-14

Family

ID=82357521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050002 WO2022150004A1 (fr) 2021-01-05 2022-01-03 Procédé de traitement de mesures de qualité d'expérience (qoe) pour des applications sensibles au temps dans un réseau de communication sans fil

Country Status (1)

Country Link
WO (1) WO2022150004A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222491A1 (en) * 2016-11-10 2019-07-18 Ciena Corporation Adaptive systems and methods enhancing service Quality of Experience
WO2020104969A1 (fr) * 2018-11-20 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Réalisation d'un accord de niveau de service, sla, de tranche de réseau

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190222491A1 (en) * 2016-11-10 2019-07-18 Ciena Corporation Adaptive systems and methods enhancing service Quality of Experience
WO2020104969A1 (fr) * 2018-11-20 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Réalisation d'un accord de niveau de service, sla, de tranche de réseau

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "NR QoE Measurement Triggering, Configuration, Collection and Reporting", 3GPP DRAFT; R2-2007600, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911074 *
ERICSSON: "pCR for TR 38.8xx: NR QoE Measurement Triggering, Configuration, Collection and Reporting", 3GPP DRAFT; R3-205201, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20200817 - 20200827, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915875 *
ERICSSON: "pCR for TR 38.8xx: Use Cases for NR QoE Management", 3GPP DRAFT; R3-205202, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20200817 - 20200827, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915876 *
NOKIA, NOKIA SHANGHAI BELL: "Framework for QoE measurement collection", 3GPP DRAFT; R3-204851, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20200817 - 20200827, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911276 *

Similar Documents

Publication Publication Date Title
US11695491B2 (en) 5G system support for conveying TSN time synchronization
EP3854140B1 (fr) Contrôle de connexion de communication au moyen d'un transfert conditionnel
US10880792B2 (en) Nodes and method for determining target PLMN ID and target cell ID
US11832164B2 (en) Technique for time-sensitive networking over a radio access network
WO2019137472A1 (fr) Procédé et appareil de reprise après défaillance de faisceau
JP2020520579A (ja) 無線通信ネットワークにおけるユーザ装置、基地局及び方法
US20160338074A1 (en) Method and Apparatus of Latency Measurement for LTE-WLAN Aggregation
EP3400739A1 (fr) Noeuds d'accès radio, et procédés mis en oeuvre dans ceux-ci
US11864139B2 (en) Transmitting device, receiving device and methods performed therein for handling communication
JP2023551978A (ja) 無線通信ネットワークにおいてサービスをハンドリングするためのネットワークノードおよび方法
US20210144604A1 (en) Radio network node, wireless device and methods performed therein
KR102497696B1 (ko) 무선 네트워크 노드, 사용자 평면 기능(upf) 및 페이징 정책 차별화를 위한 내부에서 수행된 방법
US20220095156A1 (en) Detecting Congestion at an Intermediate IAB Node
US20210400621A1 (en) Wireless Device, Radio Network Node and Methods Performed Therein for Handling Positioning in a Wireless Communication Network
WO2022150004A1 (fr) Procédé de traitement de mesures de qualité d'expérience (qoe) pour des applications sensibles au temps dans un réseau de communication sans fil
CN109417831B (zh) 用于增强lwa的上行链路路由方法和用户设备
US20240129839A1 (en) Radio network node, network node and methods performed therein
US20240244499A1 (en) Methods and apparatus for providing mobility state information
WO2023068996A1 (fr) Nœud de réseau radio, équipement utilisateur et procédés mis en œuvre par ceux-ci
WO2023009043A1 (fr) Nœud de réseau et procédé dans ce dernier pour une utilisation optimisée de ports de pont de système 5g
EP4233353A1 (fr) Procédé et noeuds permettant de gérer des mesures de faisceau
WO2023025373A1 (fr) Mesure de temps d'établissement d'appel au niveau d'un équipement utilisateur
KR20240038808A (ko) 마스터 노드, 이차 노드, 및 무선 통신 네트워크에서 실행되는 방법
WO2024035303A1 (fr) Coordination entre nœuds pour rapport d'expérience de qualité visible de réseau d'accès radio en double connectivité
WO2024049343A1 (fr) Dispositif sans fil, nœud de réseau et procédés exécutés par ces derniers pour gérer une défaillance dans une procédure de mobilité mise en œuvre par le dispositif sans fil

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

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

Country of ref document: EP

Kind code of ref document: A1