NETWORK NODE AND METHOD FOR HANDLING SERVICES IN A WIRELESS COMMUNICATION NETWORK - Patent application
Patent Information
- Application Number
- JP2023534287
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-12-07
- Filing Date
- 2021-12-07
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2041-12-07
Smart Images

Figure 0007579979000034 
Figure 0007579979000035 
Figure 0007579979000036
Abstract
Description
[Technical field]
[0001] The embodiments of the present specification relate to a network node and a method in the network node. Further, a computer program and a computer-readable storage medium are also provided herein. In particular, the embodiments of the present specification relate to handling one or more services for one or more UEs. [Background technology]
[0002] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STAs) and / or user equipment (UEs), communicate through a radio access network (RAN) to one or more core networks (CNs). The RAN covers a geographical area that is divided into service areas or cell areas, sometimes called beams or beam groups, and each service area or cell area is served by a radio network node, such as a radio access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may be denoted as a "Node B" or an "eNode B" or a "gNB". A service area or cell area is a geographical area where radio coverage is provided by a radio network node. The radio network node communicates with wireless devices within range of the radio network node over an air interface operating on radio frequencies.
[0003] The Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) communications network that evolved from the second-generation (2G) Global System for Mobile Communications (GSM). Specifications for the Evolved Packet System (EPS), also called fourth-generation (4G) networks, or Long Term Evolution (LTE), have been finalized within the Third Generation Partnership Project (3GPP), and this work continues, for example, in upcoming 3GPP releases to specify fifth-generation (5G) New Radio (NR) networks and upcoming releases.
[0004] Quality of Experience (QoE) measurements are specified for LTE and UMTS. The purpose of application layer measurements is to measure the end-user experience when using several applications. Currently, QoE measurements for streaming services and for Mobility Telephony Service for IP Multimedia Subsystem (IMS) (MTSI) services are supported.
[0005] The solutions in LTE and UMTS have similar overall principles: Quality of Experience measurement collection enables the configuration of application layer measurements in the UE and the transmission of QoE measurement result files by Radio Resource Control (RRC) signaling. The RAN receives application layer measurement configurations encapsulated in transparent containers from the Operation and Maintenance (OAM) or CN, which the RAN forwards to the UE in downlink RRC messages. Similarly, the "modem", or access stratum part of the UE, e.g. an RRC layer or entity, receives application layer measurement results encapsulated in transparent containers from higher layers of the UE, e.g. the application layer, and sends them to the network in uplink RRC messages. The RAN then forwards the result containers to a Trace Collection Entity (TCE) or Measurement Collection Entity (MCE).
[0006] In 3GPP Release 17, a new research item for NR, "Study on NR QoE Management and Optimization for Diverse Services" was approved. The purpose of the research item is to study solutions for QoE measurement in NR. QoE management in NR will not only collect experience parameters of streaming services, but also consider the general performance requirements of diverse services, e.g., Augmented Reality / Virtual Reality (AR / VR) and Ultra-Reliable Low Latency Communications (URLLC). Based on the requirements of the services, the NR study will also include a more adaptive QoE management scheme that enables the network to implement intelligent optimization to satisfy the user experience for diverse services.
[0007] Measurements can be initiated from the OAM node towards the RAN for QoE measurements in an area and / or for a service in a management-based manner, i.e. in a generic, i.e. non-UE specific manner, for example for a group of UEs, or measurements can also be initiated in a signaling-based manner, i.e. from the CN to the RAN, in which case the configuration communicated from the CN points to one or more specific UEs, e.g. a single UE, that should be configured for QoE measurements. The measurement configuration includes the measurement details, which are encapsulated in a container that is transparent to the RAN as well as to lower layers in the UE, i.e. the "modem" or access stratum part of the UE, but is interpretable by the application layer in the UE.
[0008] When initiated via the core network, measurements are started towards a particular UE. In the case of LTE, a "trace start" S1AP message is used, which carries, among other things, details about the measurement configuration that the application should collect in a "container for application layer measurement configuration" information element (IE) that is transparent to the RAN, and details to reach the trace collection entity to which the measurements should be sent.
[0009] The RAN is not aware when a streaming session is in progress, and the UE access stratum is also not aware when measurements are in progress. It is an implementation decision when the RAN stops measurements. Typically, this is done when the UE moves outside the configured measurement area.
[0010] Also, one opportunity offered by legacy solutions is the ability to preserve QoE measurements for the entire application session, even during handover situations.
[0011] QoE Measurements in Enhanced Universal Terrestrial Radio Access (E-UTRAN) E-UTRAN- Application Layer Measurement Capabilities: In E-UTRAN, UE capability transfer is used to transfer UE radio access capability information from the UE to the E-UTRAN. Figure 1 shows a signaling chart for UE capability transfer in E-UTRAN.
[0012] The UE-EUTRA-Capability IE is used to convey E-UTRA UE radio access capability parameters and feature group indicators for mandatory features to the network.
[0013] In the response message "UECapabilityInformation", the UE may include a "UE-EUTRA-Capability" IE, which may include a UE-EUTRA-Capability-v1530-IE that may be used by the UE to indicate whether the UE supports QoE measurement collection for streaming services and / or MTSI services, as detailed in the "MeasParameters-v1530" encoding below.
[0014] Contribution document CR4297 (R2-2004624) for 3GPP TS36.331 v16.0.0 at 3GPP TSG RAN2 Meeting #110 proposes an extension to the "UE-EUTRA-Capability" IE, which may include a "measParameters-v16xy" that includes a qoe-Extensions-r16 IE within the "UE-EUTRA-Capability-v16xy-IE". The qoe-Extensions-r16 IE may be used to indicate whether the UE supports Release 16 extensions for QoE measurement collection, i.e., whether the UE supports more than one QoE measurement type at a time, and whether the UE supports the signaling of withinArea, sessionRecordingIndication, qoe-Reference, temporaryStopQoE, and restartQoE. MeasParameters-v1530 encoding: TIFF0007579979000001.tif45170TIFF0007579979000002.tif58170
[0015] qoe-MeasReport: indicates whether the UE supports QoE measurement collection for streaming services. qoe-MTSI-MeasReport: indicates whether the UE supports QoE measurement collection for MTSI services. qoe-Extensions: indicates whether the UE supports Release 16 extensions for QoE measurement collection, i.e. support for more than one QoE measurement type at a time, as well as signaling of withinArea, sessionRecordingIndication, qoe-Reference, temporaryStopQoE, and restartQoE. temporaryStopQoE: indicates that reporting, but not collection, of QoE measurements shall be temporarily stopped. The withinArea: field indicates, at handover, for each application layer measurement, whether the new cell is within the area for the measurement, i.e. whether the UE is allowed to start new measurements in the cell. restartQoE: indicates that QoE measurements may be reported again after a temporary suspension.
[0016] The QoE-Reference includes the parameter QoE-Reference defined in 3GPP TS28.405. TIFF0007579979000003.tif44170
[0017] E-UTRAN- Application Layer Measurement Reporting: The purpose of the "Application Layer Measurement Reporting" procedure described in 3GPP TS 36.331 and shown in Figure 2 is to inform the E-UTRAN about application layer measurement reporting.
[0018] A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when application layer measurements are configured, i.e. when measConfigAppLayer is configured by E-UTRAN.
[0019] Upon initiating the procedure, the UE shall: 1> If application layer measurement is configured, SRB4 is configured, and the UE receives application layer measurement report information from higher layers, 2> Set measReportAppLayerContainer in the MeasReportAppLayer message to the value of the application layer measurement report information; 2> Set serviceType in the MeasReportAppLayer message to the type of application layer measurement report information; 2> Submit a MeasReportAppLayer message to the lower layer for transmission via SRB4.
[0020] E-UTRAN- QoE measurement configuration setup and release-RRC signaling: The RRCConnectionReconfiguration message is used to reconfigure the UE to set up or release the UE for application layer measurements. This is signaled in the measConfigAppLayer-15 IE within the "OtherConfig" IE.
[0021] The setup includes a transparent container measConfigAppLayerContainer, which specifies the QoE measurement configuration for the application of interest and a serviceType IE to indicate the application or service for which the QoE measurement is configured. Supported services are streaming and MTSI.
[0022] Contribution document CR4297 (R2-2004624) for 3GPP TS36.331 v16.0.0 at 3GPP TSG RAN2 Meeting #110 proposed extending the QoE measurement configuration.
[0023] The measConfigAppLayerToAddModList-r16 may be used to add or modify multiple QoE measurement configurations up to maxQoE-Measurement-r16. The measConfigAppLayerToReleaseList-r16 IE may be used to remove multiple QoE measurement configurations up to maxQoE-Measurement-r16.
[0024] Below are details of the OtherConfig IEs related to measConfigAppLayer-r15, measConfigAppLayerToAddModList-r16, and measConfigAppLayerToReleaseList-r16. TIFF0007579979000004.tif190170TIFF0007579979000005.tif77170
[0025] ServiceType contains the service type of a certain QoE measurement as specified in TS 28.405: TIFF0007579979000006.tif45170
[0026] In E-UTRAN, an example of desired UE behavior upon reception of an "OtherConfig" IE in an RRCReconfiguration message is described in CR4297 (R2-2004624). 1> If the received otherConfig contains measConfigAppLayerToAddModList, 2> For each serviceType and qoe-Reference included in measConfigAppLayerToAddModList, 2> Given the serviceType, forward measConfigAppLayerContainer, qoe-Reference, and serviceType to upper layers; 2> considers itself configured to send application layer measurement reports in accordance with 5.6.19, 2> If received, forward withinArea to upper layer; 2> If received, forward temporaryStopQoE to upper layers; 2> If received, forward restartQoE to upper layers; 1> If the received otherConfig contains measConfigAppLayerToReleaseList, 2> For each serviceType and qoe-Reference included in measConfigAppLayerToReleaseList, 2> Inform upper layers to clear any associated stored application layer measurement configurations; 2> Discarding the received relevant application layer measurement report information from the upper layer; 2> considers itself not configured to send relevant application layer measurement reports for that serviceType and qoe-Reference.
[0027] E-UTRAN- QoE Measurement Reporting- RRC Signalling: As specified in 3GPP TS 36.331, the MeasReportAppLayer RRC message is used by the UE to send QoE measurement results of an application or service to an E-UTRAN node. The service for which the report is being sent is indicated in the "serviceType" IE.
[0028] Contribution document CR4297 (R2-2004624) for 3GPP TS36.331 v16.0.0 at 3GPP TSG RAN2 Meeting #110 proposed to extend the MeasReportAppLayer IE introducing a QoE reference that includes a PLMN identity and an identifier for the QoE measurement collection.
[0029] The following are details about the MeasReportAppLayer message, which is sent using the signaling radio bearer SRB4: MeasReportAppLayer Message TIFF0007579979000007.tif110170TIFF0007579979000008.tif77170TIFF0007579979000009.tif67170
[0030] In E-UTRAN, an example of desired UE behavior for application layer measurement reporting is described in CR4297 (R2-2004624).
[0031] A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when application layer measurements are configured, i.e. when measConfigAppLayer is configured by E-UTRAN. Upon initiating the procedure, the UE shall: 1> If application layer measurement is configured, SRB4 is configured, and the UE receives application layer measurement report information from higher layers, 2> Set measReportAppLayerContainer in the MeasReportAppLayer message to the value of the application layer measurement report information; 2> Set serviceType in the MeasReportAppLayer message to the type of application layer measurement report information; 2> Set the qoe-Reference in the MeasReportAppLayer message to the value received from the upper layer; 2> Set recordingSessionIndication in the MeasReportAppLayer message to the value received from the upper layer; 2> Submit a MeasReportAppLayer message to the lower layer for transmission via SRB4.
[0032] The "UE Application Layer Measurement Configuration" IE is described in 3GPP TS36.413 v16.3.0 and TS36.423 v16.3.0.
[0033] According to 3GPP TS 28.405, the area scope parameter specifies the area in terms of cells or tracking area / routing area / location area where QMC shall take place. If the parameter is not present, QMC shall take place over the entire PLMN specified in the PLMN target.
[0034] The area scope parameters in UMTS are either: - A list of cells, identified by a Cell Group Identifier (CGI). Up to 32 CGIs may be defined. - A list of Routeing Areas, identified by their Routeing Area Identifiers (RAIs). Up to eight RAIs may be defined. - A list of location areas, identified by their Location Area Identifiers (LAIs). Up to eight LAIs may be defined.
[0035] The area scope parameters in LTE are either: - A list of cells, identified by the E-UTRAN-CGI. Up to 32 CGIs may be defined. - A list of tracking areas, identified by their Tracking Area Codes (TACs). Up to eight TACs may be defined.
[0036] The parameter is mandatory if area-based QMC is required. Summary of the Invention
[0037] Current solutions lack support for configuring network nodes, such as RAN nodes, with multiple QoE measurement configurations.
[0038] It is therefore an object of embodiments herein to provide an improved method for handling application layer measurement configurations, for example, handling multiple Quality of Experience (QoE) measurement configurations in a wireless communication network.
[0039] According to an embodiment herein, the object is achieved by providing a method implemented by a first network node for handling one or more services in a wireless communication network, the first network node receiving an indication from a second network node relating to application layer measurement configurations for one or more services for one or more UEs, the indication may be an application layer measurement configuration, for example a list of multiple Quality of Experience (QoE) measurement configurations in the wireless communication network.
[0040] According to an embodiment herein, the object is achieved by providing a method implemented by a second network node for handling one or more services in a wireless communication network, the second network node sending an indication to a first network node relating to application layer measurement configurations for one or more services for one or more UEs, the indication may be a list of application layer measurement configurations.
[0041] According to an embodiment herein, a first network node and a second network node are provided for performing the above method, respectively.
[0042] Thus, a first network node, e.g., a RAN node, may receive a list of application layer measurement configurations, e.g., a list of QoE measurement configurations for the same or a different service type, from a second network node, e.g., an OAM node or a CN node or another RAN node.
[0043] Current solutions further lack support for configuring RAN nodes with multiple Measurement Collection Entities (MCEs) or Trace Collection Entities (TCEs) to which application layer measurement reports may be sent. According to embodiments herein, the first network node may further receive an indication from the MCE or TCE for services for which application layer measurement reports should be reported. Each UE to be configured may then be provided with some or all of the application layer measurement configurations, e.g., denoted as a set of QoE measurement configurations.
[0044] The list of application layer measurement configurations may be concurrent or non-concurrent. The term "concurrent" does not necessarily mean that the measurements configured by the QoE measurement configurations are performed in parallel. The term "concurrent" means that the UE should store all received QoE measurement configurations and should be prepared to have all or a subset of the QoE measurement configurations active simultaneously. In that case, which of the QoE measurement configurations are active simultaneously may depend on which application sessions or media components in the application sessions are active simultaneously.
[0045] Each application layer measurement configuration may include an indication of whether the configuration is for a legacy QoE measurement configuration, i.e. with a QMC configuration field, or for a lightweight QoE measurement configuration, e.g. a reduced QoE measurement configuration including a reduced number of parameters to be considered when determining the QoE. Furthermore, each application layer measurement configuration may include an indication of whether the application layer measurement configuration may be stored and applied or executed in parallel with a legacy QoE measurement configuration in the UE. As yet another option, each application layer measurement configuration may include an indication of whether the application layer measurement configuration may be stored and applied or executed in parallel with a lightweight QoE measurement configuration in the UE. As yet another option, each application layer measurement configuration may include an indication of whether the application layer measurement configuration may be stored and applied or executed in parallel with another application layer measurement configuration (QoE measurement configuration) in the UE, regardless of the type of the other QoE measurement configuration.
[0046] Each application layer measurement configuration, including a configuration for quality of experience metric measurements, may include an indication indicating the type of QoE measurement: whether the QoE measurement configuration is a signaling-based QoE measurement, a management-based QoE measurement, or a hybrid version, i.e. a combination of signaling-based and management-based QoE measurements.
[0047] The first network node, e.g., a RAN node, may then forward the QoE measurement configuration to one or more UEs.
[0048] Identified scenarios in which the proposed solution according to the embodiments herein may be applied are at least the following: Scenario: "Multiple QoE measurement configurations in a setup". In this scenario, the first network node may be a RAN node, and the second network node may be, for example, a RAN node, a 5GC node, for example, an AMF, an OAM node, an SMO node. Scenario: "Multiple QoE measurement configurations in mobility", e.g. due to handover, cell change or UE context retrieval. In this scenario, the first network node may be a second RAN node and the second network node may be the first RAN node. Scenario: "Multiple QoE measurement configurations in multi-connectivity", e.g. in case of SgNB addition. In this scenario, the first network node may be a first RAN node and the second network node may be a second RAN node.
[0049] In addition to methods for the provision of multiple QoE measurement settings in the form of a list of QoE measurement settings, embodiments herein also include methods supporting independent addition of QoE measurement setting(s) to the set of QoE measurement setting(s) and removal of QoE measurement setting(s) from the set of QoE measurement setting(s).
[0050] The proposed solution according to the embodiments herein allows network operators to run multiple QoE measurement campaigns simultaneously for different services.
[0051] Example embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. [Brief description of the drawings]
[0052] [Figure 1] FIG. 1 is a signaling diagram showing UE capability transfer in E-UTRAN. [Diagram 2] FIG. 1 is a signaling diagram showing application layer measurement reporting in E-UTRAN. [Figure 3a] 1 is a schematic block diagram illustrating an embodiment of a communication network. [Figure 3b] 1 is a combined signaling schema and flow chart according to an embodiment herein. [Figure 4]FIG. 1 is a signaling diagram illustrating an example embodiment of multiple QoE settings sent from an OAM to a RAN node via 5GC, where different QoE settings are sent to different UEs. [Diagram 5] FIG. 1 is a signaling diagram illustrating an example embodiment of multiple QoE settings sent from an OAM to a RAN node via 5GC, where different QoE settings are sent to the same UE. [Figure 6] FIG. 1 is a signaling diagram illustrating an example embodiment of mobility in which multiple QoE settings for the same UE are sent from a second network node, gNB1, to a first network node, AMF. [Figure 7] FIG. 1 is a signaling diagram illustrating an example embodiment of mobility where multiple QoE settings for the same UE are sent from a second network node, gNB1, to a first network node, gNB2. [Figure 8] FIG. 1 is a signaling diagram illustrating an example embodiment of multiple QoE settings fetched from a node hosting a UE context. [Figure 9] FIG. 13 is a signaling diagram illustrating an example embodiment of multiple QoE settings sent with SgNB addition in dual connectivity. [Figure 10] FIG. 1 is a signaling diagram illustrating an example embodiment of multiple QoE settings sent with trace start in dual connectivity. [Figure 11] FIG. 2 is a schematic block diagram illustrating an embodiment of a first network node. [Figure 12] FIG. 2 is a schematic block diagram illustrating an embodiment of a second network node. [Figure 13] FIG. 1 illustrates a schematic diagram of a communications network connected to a host computer via an intermediate network. [Figure 14] FIG. 1 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection. [Figure 15]1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 16] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 17] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 18] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0053] It should be noted that the terms "UE," "terminal equipment," "wireless terminal," and "terminal" are used interchangeably. · The terms "QoE Measurement Report", "QoE Report", "Measurement Report" and "Report" are used interchangeably. The terms “QoE measurement configuration”, “QoE measurement”, “QoE configuration” and “application layer measurement configuration” are used interchangeably. · The terms "Service" and "Application" are used interchangeably. · The terms "MCE" and "TCE" are used interchangeably.
[0054] The embodiments herein generally relate to communication networks. Figure 3a is an overview showing a communication network 300. The communication network 300 may be a wireless communication network comprising one or more RANs and one or more CNs. The communication network 300 may use several different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE Advanced, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Advanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations. Although the embodiments herein relate to recent technology trends of particular interest in the 5G context, the embodiments are also applicable in further development of existing wireless communication systems, such as WCDMA and LTE.
[0055] In the wireless communication network 300, one or more wireless devices, e.g., user equipment 330, such as mobile stations, non-access point (non-AP) STAs, STAs, user equipment and / or wireless terminals, communicate to one or more core networks (CNs) via one or more access networks (ANs), e.g., RANs. It should be understood by those skilled in the art that a "wireless device" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, machine-type communication (MTC) device, D2D (Device to Device) terminal, or node, e.g., smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even small base station, that communicates within a cell. The terms user equipment 330, UE, UE 330 and wireless device 330 are used interchangeably herein.
[0056] Network nodes such as a first network node 311 and a second network node 312 operate in the wireless communication network 300. The RAN node may be any of a gNB, an eNB, an en-gNB, an ng-eNB, a gNB central unit (gNB-CU), a gNB-CU-control plane (gNB-CU-CP), a gNB-CU-user plane (gNB-CU-UP), an eNB central unit (eNB-CU), an eNB-CU-control plane (eNB-CU-CP), an eNB-CU-user plane (eNB-CU-UP), an integrated radio access backhaul transmission (IAB) node, an IAB-donor distribution unit (IAB-donor DU), an IAB-donor CU, an IAB-DU, an IAB mobile termination (IAB-MT), an open RAN central unit (O-CU), an O-CU-CP, an O-CU-UP, an O-DU, an O-RAN radio unit (O-RU), an O-eNB. The first network node 311 provides wireless coverage over a geographical area, service area 11, sometimes referred to as a beam or beam group, where the group of beams covers a service area of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi, or the like. The second network node 312 provides wireless coverage over a geographical area, service area 12, sometimes referred to as a beam or beam group, where the group of beams covers a service area of a first or second radio access technology (RAT), such as 5G, LTE, Wi-Fi, or the like. It should be noted that the network nodes may be RAN nodes, CN nodes, or OAM nodes.
[0057] The first network node 311 and the second network node 312 may be transmitting and receiving points, e.g., wireless network access nodes such as wireless local area network (WLAN) access points or access point stations (AP STAs), access controllers, base stations, e.g., radio base stations such as Node B, gNB, evolved Node B (eNB, eNode B), base transceiver stations, wireless remote units, access point base stations, base station routers, radio base station transmission arrangements, standalone access points, or any other network units capable of communicating with wireless devices within a service area served by the respective first network node 311 and second network node 312 depending, e.g., on the first radio access technology and terminology used. The first network node 311 and the second network node 312 may be referred to as source and target wireless network nodes, respectively, and may communicate with the wireless device 330 using downlink (DL) transmissions to the user equipment 330 and uplink (UL) transmissions from the wireless device 330.
[0058] 3b illustrates a schematic combined signaling scheme according to some embodiments of the present disclosure, thus illustrating a solution for handling one or more services in a wireless communication network 300.
[0059] Action 351. A second network node 312, such as an OAM node or a CN node, obtains, for example receives, multiple application layer measurement configurations for one or more services.
[0060] Action 352. The second network node 312 sends an instruction to the first network node 311 indicating a plurality of application layer measurement configurations for one or more services. Thus, the first network node 311 receives an instruction from the second network node relating to application layer measurement configurations for one or more services for one or more UEs. The instruction may be a list of application layer measurement configurations. The list of application layer measurement configurations may include sets of QoE measurement configurations for the same or different service types. The list of application layer measurement configurations may further include one or more instructions for one or more measurement collection entities (MCEs) and / or trace collection entities (TCEs) for receiving QoE measurement reports for the UEs.
[0061] Action 353. The first network node may then determine all or a portion of a plurality of application layer measurement configurations for the UE 10.
[0062] Action 354. Upon determining the first network node 311, the first network node 311 may send one or more application layer measurement configurations from the list of application layer measurement configurations to one or more UEs (or send an indication of the determined one or more application layer measurement configurations).
[0063] Action 355. The first network node 311 may then send the QoE measurement report from the UE to the corresponding MCE and / or TCE based on the application layer measurement configuration.
[0064] According to some embodiments herein, each application layer measurement configuration in the list of application layer measurement configurations may include an indication for indicating one or more of the following: a) whether the application layer measurement configuration is a legacy or lightweight QoE measurement configuration; b) whether application layer measurements may be stored, applied or performed in parallel with legacy QoE measurement configurations in the wireless communication device; c) whether application layer measurements may be stored, applied or performed in parallel with the lightweight QoE measurement configuration in the wireless communication device; d) Type of QoE measurement configuration.
[0065] According to an embodiment herein, there is provided a method implemented by a second network node 312 for handling one or more services in a wireless communication network 300. The second network node 312 sends an indication related to application layer measurement configuration for one or more services for one or more UEs to the first network node 311. The indication may be a list of application layer measurement configurations.
[0066] Exemplary embodiments are described below.
[0067] Scenario: An embodiment related to "Multiple QoE measurement configurations in a setup"
[0068] In this scenario, the first network node 311 may be a RAN node, for example a gNB or an eNB, and the second network node 312 may be another RAN node, a 5GC node, an OAM, an SMO, or an NMS.
[0069] The first network node 311 receives a list of QoE measurement configurations from the second network node 312, for example in an NGAP Initial Context Setup Request message or an X2AP SGNB Addition Request message, or from an OAM node. Each QoE measurement configuration includes one or more of the following: A container for application layer measurement configurations. · Identifier of the application layer measurement configuration, i.e. an identifier outside the container that refers to this particular configuration. For example, area scope directives as specified in 36.413 v16.3.0. · One identifier indicating the service type of the UE application layer measurements, or a list of service type identifiers, for example if a common set of QoE metrics is applicable for a set of services. An identifier or a list of identifiers for one or more specific UEs. An instruction, e.g. a list of IP addresses or URLs or instructions that can be used by the RAN node to send QoE measurement reports to the MCE. An indication of the type of application layer measurement configuration, the indication indicating whether the configuration is a legacy QoE measurement configuration including a QMC configuration file, or a lightweight QoE measurement configuration. An indication indicating the type of QoE measurement configuration: the indication indicates whether the QoE measurement configuration is a signaling-based QoE measurement configuration, a management-based QoE measurement configuration or a hybrid version, i.e. a combined management-based QoE measurement and signaling-based QoE measurement. A priority indication to be used to prioritize between multiple QoE measurement configurations in case a UE receiving a QoE measurement configuration at some point is not able to perform QoE measurements according to all configured QoE measurement configurations whose conditions for execution are met, e.g. due to resource constraints or conflicting configuration instructions.
[0070] The first network node may use the list of application layer measurement configurations to configure one or more UEs to perform application layer measurements according to the received information.
[0071] The network node may also identify the specific QoE configuration and know if two containers contain the same QoE configuration. Furthermore, a network node receiving a QoE measurement configuration may be able to detect the type of configured measurement, i.e., legacy QoE measurement or lightweight QoE measurement. Moreover, a network node receiving a list of application layer measurement configurations may detect whether the configured QoE measurement configuration relates to signaling-based QoE or management-based QoE.
[0072] 4 illustrates an example of a signaling flow for QoE settings according to an embodiment of the present specification. Multiple QoE settings are sent from OAM to a RAN node via 5GC. Different QoE settings are sent to different UEs.
[0073] As shown in Fig. 4, in step 2) indicated by the dotted box, which is affected according to an embodiment herein, a list of QoE measurement configurations relates to two services, service 1 and service 2, and two different MCEs are indicated, so that for example, a QoE report for service 1 will be sent from the RAN node to MCE1 and a QoE report for service 2 will be sent from the RAN node to MCE2. The QoE measurement configurations related to service 1 will be used to configure UE1 and the QoE measurement configurations related to service 2 will be used to configure UE2.
[0074] Figure 5 illustrates another example of a signaling flow for QoE configuration according to an embodiment of the present specification. The situation is similar to the previous example in Figure 4, but in this case, both the QoE measurement configuration related to service 1 and the QoE measurement configuration related to service 2 are used to configure UE1, i.e., different QoE configurations are sent to the same UE.
[0075] Scenario: An embodiment related to "Multiple QoE measurement configurations in mobility"
[0076] In this scenario, the first network node 311 is a first RAN node and the second network node 312 is a second RAN node.
[0077] This scenario is applicable at least in the following cases: a) Mobility, e.g. XnAP handover preparation, X2AP SgNB change or XnAP SCell addition procedures; b) Retrieval of UE context between RAN nodes, e.g. between gNBs or eNBs, e.g. in case of RRC re-establishment or RRC restart.
[0078] In the case of mobility according to embodiments herein, the first network node 311 is the RAN node targeted by the mobility procedure, i.e. the target RAN node, and the second network node 312 is the RAN node that initiates the mobility procedure, i.e. the source RAN node.
[0079] The source RAN node sends a message to the target RAN node containing a list of QoE measurement configurations, e.g., XnAP HANDOVER REQUEST message, X2AP SGNB CHANGE REQUIRED message. Each of the multiple QoE measurement configurations may contain the same information as detailed for the scenario "Multiple QoE measurement configurations in a setup".
[0080] The target RAN node may acknowledge the request, e.g., via an XnAP Handover Request Acknowledge message, an X2AP SGNB Change Confirm message, to indicate that the list of QoE measurement configurations has been accepted, or the target RAN node may indicate that the preparation has failed, e.g., using an XnAP Handover Preparation Fail message, an X2AP SGNB Change Reject message.
[0081] An example of a signaling flow for the case of mobility via XnAP according to an embodiment herein is shown in Figure 6, where gNB1 is the source RAN node and gNB2 is the target RAN node. As shown in Figure 6, the procedure in steps 4) and 5) indicated by the dotted box is affected according to an embodiment herein. A list of QoE measurement configurations related to two services, e.g., service 1 and service 2, as well as contact information for two different MCEs are transferred from the source RAN node to the target RAN node as part of the handover preparation procedure, e.g., in an XnAP handover request message.
[0082] As shown in Figure 6, multiple QoE configurations for the same UE are sent from a second network node 312, exemplified as a first RAN node gNB1, to a first network node, exemplified as a second RAN node gNB2. Note that prior to the first message in this exemplary signaling flow, gNB1 has received a QoE measurement configuration from an OAM node or a core network node.
[0083] Another example of a signaling flow for the case of mobility via NGAP according to an embodiment herein is provided in Figure 7, where gNB1 is the source RAN node and gNB2 is the target RAN node. Similar to the XnAP procedure in Figure 6, also in this case, a list of QoE measurement configurations related to two services, e.g., service 1 and service 2, and contact information for two different MCEs are transferred from the source RAN node to the target RAN node. As shown in Figure 7, the procedures in steps 4) and 7) indicated by the dotted boxes are affected according to an embodiment herein.
[0084] As shown in Figure 7, multiple QoE configurations for the same UE are sent from a second network node 312, such as a first RAN node gNB1, to a first network node 311, such as an AMF, which forwards it to a second RAN node gNB2. Note that prior to the first message in this example signaling flow, gNB1 has received a QoE measurement configuration from an OAM node or a core network node.
[0085] In the case of retrieving a UE context according to an embodiment herein, the first network node 311 is the RAN node from which the UE context needs to be fetched, i.e. the target RAN node, and the second network node 312 is the RAN node that hosts the UE context, i.e. the source RAN node.
[0086] The target RAN node requests the source RAN node to fetch the UE context, for example in an XnAP UE Context Retrieve Request message or in an X2AP UE Context Retrieve Request message.
[0087] The source RAN node may acknowledge the request and include the list of QoE measurement configurations in its response towards the target RAN node, for example in an XnAP UE Context Retrieval Response message or in an X2AP UE Context Retrieval Response message. Each of the multiple QoE measurement configurations may include the same information as detailed for the scenario "Multiple QoE measurement configurations in a setup".
[0088] An example of a signaling flow for the case of retrieving a UE context according to an embodiment herein is shown in Figure 8, where multiple QoE settings are fetched from a network node hosting the UE context. gNB1 is the source RAN node and gNB2 is the target RAN node. Note that prior to the first message in this example signaling flow, gNB1 has received a QoE measurement configuration from an OAM node or a core network node. As shown in Figure 8, the procedures in steps 6) and 7) indicated by the dotted boxes are affected according to an embodiment herein.
[0089] Scenario: An embodiment related to "Multiple QoE measurement configurations in multi-connectivity"
[0090] In this scenario, the first network node 311 is a first RAN node and the second network node 312 is a second RAN node.
[0091] This scenario is applicable at least in the following cases: a) Multi-connectivity related class 1 basic procedures, such as XnAP S-NG-RAN node addition preparation procedure, X2AP SgNB addition preparation procedure, and X2AP SeNB addition preparation procedure. b) Multi-connectivity relationship class 2 basic procedures, e.g., the trace start procedure.
[0092] For a multi-connectivity related procedure according to an embodiment herein, the first network node 311 is the RAN node targeted by the procedure, i.e. the target RAN node, and the second network node 312 is the RAN node that initiates the procedure, i.e. the source RAN node.
[0093] For multi-connectivity relationship class 1 basic procedures, The source RAN node sends to the target RAN node a request message, e.g., an X2AP SGNB Addition Request message or an XnAP S-Node Addition Request message, including multiple QoE measurement configurations, each of which may include the same information as detailed for the scenario "Multiple QoE measurement configurations in a setup". The target RAN node may accept the request, e.g. via an X2AP SGNB Addition Request Acknowledge message or an XnAP S-Node Addition Request Acknowledge message, to indicate that the QoE measurement configuration has been accepted, or may not accept the request and respond to the source RAN node, e.g. with an X2AP SGNB Addition Request Reject message or an XnAP S-Node Addition Request Reject message.
[0094] For multi-connectivity relationship class 2 basic procedures, The source RAN node sends a request message, e.g. a Trace Start message, to the target RAN node, including multiple QoE measurement configurations, each of which may include the same information as detailed for the scenario "Multiple QoE measurement configurations in a setup".
[0095] An example of a signaling flow for the SgNB addition case according to an embodiment herein is shown in Figure 9. eNB1 is the source RAN node and gNB1 is the target RAN node. The SGNB addition request message in step 4 is used to convey the QoE measurement configuration. In case of reconfiguration of the radio bearer used by the UE to report QoE measurements, for example, when RAN overload is detected in the source RAN node, the target RAN node will be able to forward such QoE reports towards the relevant MCE.
[0096] As shown in Figure 9, the procedure in steps 4) and 5) indicated by the dotted box is effected according to an embodiment herein, where multiple QoE settings are sent with the SgNB Addition Request message in dual connectivity. Note that prior to the first message in this example signaling flow, eNB1 has received QoE measurement settings from an OAM node or a core network node.
[0097] An example of a signaling flow for the trace start case according to an embodiment herein is shown in Figure 10. eNB1 is the source RAN node and gNB1 is the target RAN node. The trace start message in step 4 is affected according to an embodiment herein and is used to forward the QoE measurement configuration. In case of reconfiguration of the radio bearer used by the UE to report QoE measurements, for example when RAN overload is detected in the source RAN node, the target RAN node will be able to forward such QoE reports towards the concerned MCE.
[0098] As shown in Figure 10, multiple QoE settings are sent together with the trace start message in dual connectivity. Note that before the first message in this example signaling flow, gNB1 has received a QoE measurement configuration from an OAM node or a core network node.
[0099] Example implementation for LTE An example implementation is provided below for S1AP (TS36.413), with bold text relating to the embodiments herein.
[0100] The following table specifies the parameters related to trace activation (9.2.1.4 Trace Activation). TIFF0007579979000010.tif255170TIFF0007579979000011.tif227170TIFF0007579979000012.tif19170
[0101] Here, 9.xx is the measurement collection entity item. This information element indicates a measurement collection entity. TIFF0007579979000013.tif94170
[0102] The table below, 9.2.1.128 UE Application Layer Measurement Configuration, shows the IE that specifies configuration information for the QoE Measurement Collection (QMC) function. TIFF0007579979000014.tif243170TIFF0007579979000015.tif31170
[0103] An example implementation is provided below for X2AP (TS 36.423), with the bold text relating to the embodiments herein.
[0104] Table 9.2.2 Trace Activation below specifies parameters related to trace activation. TIFF0007579979000016.tif255170TIFF0007579979000017.tif222170TIFF0007579979000018.tif20170
[0105] Here, 9.xx is the measurement collection entity item. This information element indicates a measurement collection entity. TIFF0007579979000019.tif94170
[0106] Examples of implementations for NG-RAN: An example implementation is provided below for NGAP (TS 38.413), with the bolded text relating to the embodiments herein.
[0107] The following table, 9.3.1.14 Trace Activation, shows the IEs that specify parameters related to trace session activation. TIFF0007579979000020.tif255170TIFF0007579979000021.tif212170TIFF0007579979000022.tif15170
[0108] Here, 9.3.1.xxx is the UE application layer measurement configuration. The IE specifies the configuration information for the QoE Measurement Collection (QMC) function. TIFF0007579979000023.tif222170TIFF0007579979000024.tif30170TIFF0007579979000025.tif20170
[0109] Here, 9.xx is the measurement collection entity item. This information element indicates a measurement collection entity. TIFF0007579979000026.tif98170
[0110] An example implementation is provided below for XnAP (TS 38.423), with the bold text relating to the embodiments herein.
[0111] The table below, 9.2.3.55 Trace Activation, shows this IE, which specifies parameters related to trace session activation. TIFF0007579979000027.tif255170TIFF0007579979000028.tif203170TIFF0007579979000029.tif16170
[0112] 9.3.1.xxx UE application layer measurement configuration. The IE specifies configuration information for the QoE Measurement Collection (QMC) function. TIFF0007579979000030.tif228170TIFF0007579979000031.tif31170TIFF0007579979000032.tif20170
[0113] 9.xx Measurement Collection Entities This information element indicates a measurement collection entity. TIFF0007579979000033.tif103170
[0114] An embodiment relating to independent addition and removal of QoE measurement configurations. As previously described, multiple QoE measurement configurations may be conveyed to the RAN simultaneously, for example, from the OAM system, from the CN, or from another RAN node. Alternatively, different QoE measurement configurations may be sent to the RAN consecutively at different time points. In this case, at each occasion when the RAN receives one or more QoE measurement configurations, this may be a single QoE measurement configuration or a set of QoE measurement configurations. Each time, the RAN may receive the QoE measurement configuration(s) from either the OAM node or the CN node, or from another RAN node. When the QoE measurement configuration or the set of QoE measurement configurations is conveyed to the UE, the QoE measurement configuration or the set of QoE measurement configurations may include an indication of the previously provided QoE measurement configuration(s) to which the new QoE measurement configuration(s) may be present in parallel, i.e., in the same UE. In this way, multiple, possibly concurrent or parallel QoE measurement configurations may be added or removed independently at different occasions. The indication of previously provided QoE measurement configuration(s) may have the form of QoE measurement ID(s) or QoE measurement setting ID(s). As another option, for example, a set of QoE measurement settings that may be stored and applied concurrently may be given a common "QoE measurement setting set ID", and then any new QoE measurement settings to be added to that set may refer to a set with the same QoE measurement setting set ID.
[0115] As yet another option, a QoE measurement configuration provided to the RAN, e.g., provided after a previously provided QoE measurement configuration(s), may have an associated indication of whether that QoE measurement configuration may be combined with another, unspecified, possibly concurrent / parallel QoE measurement configuration, in which case the RAN may forward the QoE measurement configuration to a UE that already has one or more QoE measurement configurations, which will then store and potentially apply the new QoE measurement configuration.
[0116] As yet another option, the QoE measurement configuration may have an associated indication as to whether subsequent QoE measurement configuration(s) may be stored and applied concurrently or in parallel with the current QoE measurement configuration, which may be the same indication as in the previous option, with slightly different meaning depending on whether the QoE measurement configuration in question is the first or subsequent one provided to the UE.
[0117] As yet another option, when the CN node provides a signaling-based QoE measurement configuration to the RAN, indicating a particular UE to which the RAN should forward the QoE measurement configuration, the CN node can also indicate whether this UE may have previous or subsequent QoE measurement configurations stored and applied in parallel, e.g., whether the RAN node is enabled to forward the QoE measurement configuration to the UE even if the UE already has a QoE measurement configuration, in which case the QoE configurations may be stored and potentially applied in parallel. If the indication is that such concurrent QoE measurement configurations are not enabled for the UE, then if the UE already has a QoE measurement configuration, this old measurement configuration may be erased. Furthermore, if the instruction from the CN node is that such concurrent QoE measurement configuration is not enabled for the UE, the UE may be provided with the QoE measurement in question and then potentially forwarded to the UE. If another QoE measurement configuration is later provided from the CN or OAM to the RAN, this subsequent QoE measurement configuration may not be forwarded to the UE, but in some cases, the subsequent QoE measurement configuration may replace the old one if it is a signaling-based QoE measurement configuration that has been instructed to override or have a higher priority than the old one.
[0118] When a QoE measurement configuration is independently added to or removed from a set of QoE measurement configuration(s), in the RRC signaling between the RAN node and the UE, the information may be encoded using an add-mod-list construct, e.g., a QoE-MeasConfig-ToAddModList IE and / or a QoE-MeasConfigToRemoveList IE.
[0119] To implement the method in the first network node 311, the first network node 311 comprises the modules shown in Figure 11. The network node 311 comprises a receiving module 1110, a sending module 1120, a determining module 1130, a processing module 1140, a memory 1150, etc.
[0120] The first network node 311 is configured to receive an indication related to application layer measurement configurations for one or more services for one or more UEs from the second network node 312, e.g., by the receiving module 1110 being so configured. The indication may be a list of application layer measurement configurations. The list of application layer measurement configurations may include sets of QoE measurement configurations for the same or different service types.
[0121] The list of application layer measurement configurations may further include one or more instructions for one or more Measurement Collection Entities (MCEs) and / or Trace Collection Entities (TCEs) to receive the QoE measurement reports of the UE. The first network node 311 may send the QoE measurement reports to the corresponding MCEs and / or TCEs based on the configurations.
[0122] According to embodiments herein, the first network node 311 may be further configured to send one or more application layer measurement configurations from the list of application layer measurement configurations to one or more UEs, e.g., by the transmitting module 1120 being so configured.
[0123] The methods according to the embodiments herein may be implemented through one or more processors, such as the processor 1160 in the network node 311, with computer program code for performing the functions and actions of the embodiments herein. The above-mentioned program code may also be provided as a computer program product, for example in the form of a computer readable medium or data carrier 1180, which, when loaded into the network node 311, carries the computer program code 1170 shown in FIG. 11 for performing the embodiments herein. One such carrier may be in the form of a CD ROM disk. However, such a carrier may be realizable on other data carriers, such as a memory stick. The computer program code may further be provided as pure program code on a server or cloud and downloaded to the network node 311.
[0124] To implement the method in the second network node 312, the second network node 312 comprises the modules shown in Figure 12. The second network node 312 comprises a receiving module 1210, a transmitting module 1220, a determining module 1230, a processing module 1240, a memory 1250, etc.
[0125] The second network node 312 is configured to transmit an indication related to application layer measurement configuration for one or more services for one or more UEs to the first network node 311, e.g., by the transmitting module 1220 being so configured. The indication may be a list of application layer measurement configurations.
[0126] The methods according to the embodiments herein may be implemented through one or more processors, such as the processor 1260 in the second network node 312, with computer program code for performing the functions and actions of the embodiments herein. The above-mentioned program code may also be provided as a computer program product, for example in the form of a computer readable medium or data carrier 1280, which, when loaded into the second network node 312, carries the computer program code 1270 shown in FIG. 12 for performing the embodiments herein. One such carrier may be in the form of a CD ROM disk. However, such a carrier may be realizable on other data carriers, such as a memory stick. The computer program code may further be provided as pure program code on a server or cloud and downloaded to the second network node 312.
[0127] 13, according to one embodiment, a communication system includes a communication network 3210, such as a 3GPP type cellular network, comprising an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a number of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points, which are examples of radio network nodes 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, which is an example of a UE 330 located in the coverage area 3213c, is configured to wirelessly connect to or be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a can wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or connects to the corresponding base station 3212.
[0128] The communication network 3210 is itself connected to a host computer 3230, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connection 3221, 3222 between the communication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may proceed via an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 3220 may be a backbone network or the Internet, if any, and in particular the intermediate network 3220 may comprise two or more sub-networks (not shown).
[0129] The communication system of FIG. 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 networks 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 the routing of the uplink and downlink communications. For example, the base station 3212 may not or need not be informed regarding the past routing of an incoming downlink communication involving data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 3291 and destined for the host computer 3230.
[0130] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 14. In the communication system 3300, the host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 further comprises a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (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 is executable by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330 connecting via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to a remote user, the host application 3312 may provide user data that is transmitted using the OTT connection 3350.
[0131] The communication system 3300 further includes a base station 3320 provided in the communication system, the base station 3320 comprising hardware 3325 enabling the base station 3320 to communicate with the host computer 3310 and the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 3300, as well as a wireless interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 that is 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. The connection 3360 may be direct or the connection 3360 may pass through a core network (not shown in FIG. 14) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, 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 thereof (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.
[0132] The communication system 3300 further includes the UE 3330 already mentioned. The hardware 3335 of the UE 3330 may include a wireless 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 a processing circuit 3338, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 3330 further includes software 3331 stored in or accessible by the UE 3330 and executable by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide services to a human or non-human user via the UE 3330 with the support of the host computer 3310. At the host computer 3310, a running host application 3312 may communicate with a running client application 3332 via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing a service to a user, 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 the client application 3332 provides.
[0133] It should be noted that the host computer 3310, base station 3320 and UE 3330 shown in Figure 14 may be equivalent to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292, respectively, of Figure 13. That is, the inner workings of these entities may be as shown in Figure 14 and, separately, the surrounding network topology may be that of Figure 13.
[0134] 14, the OTT connection 3350 is depicted abstractly to show communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing 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 also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).
[0135] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function to reconfigure the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to fluctuations in the measurement results. The measurement procedures and / or the network function to reconfigure 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.
[0136] It should be noted that the host computer 3310, base station 3320 and UE 3330 shown in Figure 15 may be equivalent to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292, respectively, of Figure 14. That is, the inner workings of these entities may be as shown in Figure 15 and, separately, the surrounding network topology may be that of Figure 14.
[0137] 15, the OTT connection 3350 is depicted abstractly to show communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing 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 also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).
[0138] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may achieve an efficient RACH process, thereby providing benefits such as improved battery time and better responsiveness.
[0139] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may achieve efficient QoE reporting, thereby providing benefits such as improved UE experience and better responsiveness.
[0140] Measurement procedures may be provided for the purpose of monitoring data rates, latency and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to fluctuations in the measurement results. The measurement procedures and / or the network function 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. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 3350 passes, and the sensors may participate in the measurement procedures by providing values of the monitored quantities exemplified above, or other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 3320, and the reconfiguration may be unknown or imperceptible to the base station 3320. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 3311, 3331 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 3350 while the software 3311, 3331 monitors propagation times, errors, etc.
[0141] FIG. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 15 are included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.
[0142] FIG. 16 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 16 are included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.
[0143] FIG. 17 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 17 are included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in an optional third sub-step 3630. In a fourth step 3640 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.
[0144] FIG. 18 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only a drawing reference to FIG. 18 is included in this section. In an optional first step 3710 of the method, the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In an optional second step 3720, the base station initiates a transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.
[0145] The term "processing module" as used herein may refer to a processing circuit, a processing unit, a processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. As an example, a processor, ASIC, FPGA, or the like may comprise one or more processor kernels. In some examples, a processing module may be embodied by a software module or a hardware module. Any such module may be a determining means, an estimating means, a capturing means, an associating means, a comparing means, an identifying means, a selecting means, a receiving means, a transmitting means, or the like disclosed herein. As an example, the term "means" may be a module such as a determining module, a selecting module, or the like.
[0146] As used herein, the phrase "configured to" may mean that a processing circuit is configured or adapted, by software and / or hardware configuration, to perform one or more of the actions described herein.
[0147] As used herein, the term "memory" may refer to a hard disk, a magnetic storage medium, a portable computer diskette or disk, a flash memory, a random access memory (RAM), etc. Additionally, the term "memory" may refer to a processor's internal register memory, etc.
[0148] The term "computer-readable medium" as used herein may be a Universal Serial Bus (USB) memory, a DVD disc, a Blu-ray disc, a software module received as a stream of data, a flash memory, a hard drive, a memory stick, a memory card such as a multimedia card (MMC), etc.
[0149] It will be appreciated that the above description and accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the above description and accompanying drawings.
Claims
1. A method implemented in a first network node (311) for handling one or more services in a wireless communication network (300), said wireless communication network (300) comprising said first network node (311), a second network node (312) and one or more wireless communication devices (330, 331), said method comprising: receiving (352) from the second network node (312) an indication relating to application layer measurement configuration for one or more services for one or more wireless communication devices (330, 331); determining (353) a set of application layer measurement configurations for one or more wireless communication devices (330, 331) based on the received indications related to application layer measurement configurations; sending (354) the determined set of application layer measurement configurations, or an indication of the determined set of application layer measurement configurations, to the one or more wireless communication devices (330, 331); Including, the instructions relating to application layer measurement configurations include a list of application layer measurement configurations; Each application layer measurement configuration in the list of application layer measurement configurations comprises: a) whether the application layer measurement configuration is a legacy QoE measurement configuration or a lightweight QoE measurement configuration; b) whether application layer measurements may be stored, applied or performed in parallel with legacy QoE measurement configurations in the wireless communication device; c) whether application layer measurements may be stored, applied or performed in parallel with the lightweight QoE measurement configuration in the wireless communication device; d) The type of QoE measurements, such as signaling-based QoE measurements, management-based QoE measurements, or a combination of signaling-based and management-based QoE measurements. [0036] including instructions for indicating one or more of: method.
2. The method of claim 1 , wherein the list of application layer measurement configurations includes a list of Quality of Experience (QoE) measurement configurations for the same or different service types.
3. The list of application layer measurement configurations includes one or more indications regarding measurement collection entities (MCEs) and / or trace collection entities (TCEs) for one or more service types to which application layer measurement reports should be sent, and the method further comprises: Sending (355) application layer measurement reports received from one or more wireless communication devices (330, 331) to a corresponding MCE and / or TCE based on said application layer measurement configuration. The method of claim 1 or 2, further comprising:
4. 4. The method according to claim 1, wherein the first network node (311) is a Radio Access Network (RAN) node and the second network node (312) is another RAN node, or a core network node, an Operation and Maintenance (OAM) node, a Service Management and Orchestration (SMO) node, a Network Management System (NMS) node.
5. 5. The method of claim 1, wherein the first network node (311) is a target Radio Access Network (RAN) node targeted by a mobility procedure and the second network node (312) is a source RAN node initiating the mobility procedure.
6. 5. The method according to claim 1, wherein the first network node (311) is a target Radio Access Network (RAN) node from which context of one or more wireless communication devices (330, 331) needs to be fetched and the second network node (312) is a source RAN node that hosts the context of one or more wireless communication devices (330, 331).
7. Each QoE measurement setting: a) a container for application layer measurement configuration; b) an identifier of the application layer measurement configuration; c) Area scope indication; d) an identifier or a list of identifiers of service types indicating the service type of application layer measurements; e) an identifier or list of identifiers of one or more specific wireless communication devices (330, 331); f) A priority indication to be used to prioritize between multiple said QoE measurement configurations. The method of claim 2 , further comprising one or more of:
8. receiving (352) from the second network node (312) an indication relating to application layer measurement configuration for one or more services for one or more wireless communication devices (330, 331); receiving a plurality of application layer measurement configurations simultaneously from the second network node (312); The method of any one of claims 1 to 7, comprising:
9. receiving (352) from the second network node (312) an indication relating to application layer measurement configuration for one or more services for one or more wireless communication devices (330, 331); Continuously receiving application layer measurement configurations at different points in time The method of any one of claims 1 to 7, comprising:
10. receiving application layer measurement configurations successively at different points in time; Receiving a single QoE measurement configuration or a set of QoE measurement configurations at each time.
10. The method of claim 9, comprising:
11. receiving application layer measurement configurations successively at different points in time; receiving, each time, one or more measurement configurations from either an OAM node or a CN node, or another RAN node; 10. The method of claim 9, comprising:
12. 12. The method of claim 9, wherein sending (354) an indication of the determined set of application layer measurement configurations to the one or more wireless communication devices (330, 331) comprises sending an indication of whether previously provided application layer measurement configuration(s) are to be provided in parallel with a current application layer measurement configuration(s) for the same wireless communication device (330, 331).
13. 12. The method of claim 9, wherein an application layer measurement configuration includes an associated indication of whether said application layer measurement configuration should be combined with another, unspecified concurrent or parallel QoE measurement configuration.
14. 12. The method of claim 9, wherein the application layer measurement configuration includes an associated indication of whether subsequent application layer measurement configuration(s) should be stored, combined or applied concurrently or in parallel with a current or another layer measurement configuration(s).
15. A first network node (311) for handling one or more services in a wireless communication network (300), said wireless communication network (300) comprising said first network node (311), a second network node (312) and one or more wireless communication devices (330, 331), said first network node (311) comprising: receiving from the second network node (312) an indication relating to application layer measurement configuration for one or more services for one or more wireless communication devices (330, 331); determining a set of application layer measurement configurations for one or more wireless communication devices (330, 331) based on the received indications related to application layer measurement configurations; sending the determined set of application layer measurement configurations, or an indication of the determined set of application layer measurement configurations, to the one or more wireless communication devices (330, 331); It is set to do the instructions relating to application layer measurement configurations include a list of application layer measurement configurations; Each application layer measurement configuration in the list of application layer measurement configurations comprises: a) whether the application layer measurement configuration is a legacy QoE measurement configuration or a lightweight QoE measurement configuration; b) whether application layer measurements may be stored, applied or performed in parallel with legacy QoE measurement configurations in the wireless communication device; c) whether application layer measurements may be stored, applied or performed in parallel with the lightweight QoE measurement configuration in the wireless communication device; d) The type of QoE measurements, such as signaling-based QoE measurements, management-based QoE measurements, or a combination of signaling-based and management-based QoE measurements. [0036] including instructions for indicating one or more of: A first network node (311).
16. A method implemented by a second network node (312) for handling one or more services in a wireless communication network (300), said wireless communication network (300) comprising a first network node (311), said second network node (312) and one or more wireless communication devices (330, 331), said method comprising: sending to the first network node (311) an indication relating to application layer measurement configurations for one or more services for one or more wireless communication devices (330, 331), the indication including a list of application layer measurement configurations. Including, the instructions relating to application layer measurement configurations include a list of application layer measurement configurations; Each application layer measurement configuration in the list of application layer measurement configurations comprises: a) whether the application layer measurement configuration is a legacy QoE measurement configuration or a lightweight QoE measurement configuration; b) whether application layer measurements may be stored, applied or performed in parallel with legacy QoE measurement configurations in the wireless communication device; c) whether application layer measurements may be stored, applied or performed in parallel with the lightweight QoE measurement configuration in the wireless communication device; d) The type of QoE measurements, such as signaling-based QoE measurements, management-based QoE measurements, or a combination of signaling-based and management-based QoE measurements. [0036] including instructions for indicating one or more of: method.
17. A second network node (312) for handling one or more services in a wireless communication network (300), said wireless communication network (300) comprising a first network node (311), said second network node (312) and one or more wireless communication devices (330, 331), said second network node comprising: sending to the first network node (311) an indication relating to application layer measurement configurations for one or more services for one or more wireless communication devices (330, 331), the indication including a list of application layer measurement configurations. It is set to do the instructions relating to application layer measurement configurations include a list of application layer measurement configurations; Each application layer measurement configuration in the list of application layer measurement configurations comprises: a) whether the application layer measurement configuration is a legacy QoE measurement configuration or a lightweight QoE measurement configuration; b) whether application layer measurements may be stored, applied or performed in parallel with legacy QoE measurement configurations in the wireless communication device; c) whether application layer measurements may be stored, applied or performed in parallel with the lightweight QoE measurement configuration in the wireless communication device; d) The type of QoE measurements, such as signaling-based QoE measurements, management-based QoE measurements, or a combination of signaling-based and management-based QoE measurements. [0036] including instructions for indicating one or more of: A second network node (312).
Citation Information
Patent Citations
Communication method, communication device, communication program and communication system
JP2019054478A
Notifying a management system of quality of experience measurement reporting status
WO2020128657A1
Communication method and apparatus, and readable storage medium, and system
WO2022083558A1
