WO2021087802A1 - Fourniture de paramètres relatifs à une application - Google Patents

Fourniture de paramètres relatifs à une application Download PDF

Info

Publication number
WO2021087802A1
WO2021087802A1 PCT/CN2019/115954 CN2019115954W WO2021087802A1 WO 2021087802 A1 WO2021087802 A1 WO 2021087802A1 CN 2019115954 W CN2019115954 W CN 2019115954W WO 2021087802 A1 WO2021087802 A1 WO 2021087802A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
entity
identifier
parameters
container identifier
Prior art date
Application number
PCT/CN2019/115954
Other languages
English (en)
Inventor
Juan Zhang
Haris Zisimopoulos
Stefano Faccin
Gavin Bernard Horn
Sebastian Speicher
Hong Cheng
Miguel Griot
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2019/115954 priority Critical patent/WO2021087802A1/fr
Publication of WO2021087802A1 publication Critical patent/WO2021087802A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for providing application related parameters from a user equipment (UE) .
  • UE user equipment
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipments (UEs) .
  • a user equipment (UE) may communicate with a base station (BS) via the downlink and uplink.
  • the downlink (or forward link) refers to the communication link from the BS to the UE
  • the uplink (or reverse link) refers to the communication link from the UE to the BS.
  • a BS may be referred to as a Node B, a gNB, an access point (AP) , a radio head, a transmit receive point (TRP) , a New Radio (NR) BS, a 5G Node B, and/or the like.
  • New Radio which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • 3GPP Third Generation Partnership Project
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL) , using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink (UL) , as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple-input multiple-output
  • a method of wireless communication may include receiving a first message that includes an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application of the UE and where the container identifier is associated with reporting one or more parameters related to the application.
  • the method may include receiving a second message that indicates a linkage between the container identifier and the one or more parameters and receiving a request to report the one or more parameters, where the request includes the container identifier.
  • the method may include transmitting a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message.
  • a method of wireless communication may include receiving, from an application function (AF) entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application and associating the container identifier and an application identifier of the application based at least in part on receiving the request.
  • the method may include transmitting, to the AF entity, a response to the request, where the response includes the container identifier associated with the application.
  • the method may include transmitting, to the AF entity, a request for the one or more parameters and receiving, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters.
  • a method of wireless communication may include receiving, from a network entity, a container identifier associated with reporting, by a UE, one or more parameters related to an application of the UE and transmitting, to the UE, a first non-access stratum (NAS) message that includes the container identifier based at least in part on receiving the container identifier from the network entity.
  • AMF access and mobility management function
  • the method may include receiving, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the first NAS message to the UE and transmitting, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, where the response message is transmitted based at least in part on receiving the second NAS message from the UE.
  • a method of wireless communication may include receiving, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and wherein the container identifier is associated with reporting, by a UE, one or more parameters related to the application.
  • the method may include receiving, from the UE, a registration request and transmitting, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier.
  • a method of wireless communication may include transmitting, to a network entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application.
  • the method may include receiving, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters.
  • the method may include receiving, from the UE, an application layer registration message associated with the application and transmitting, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request.
  • a UE for wireless communication may include memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to receive a first message that includes an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application of the UE and where the container identifier is associated with reporting one or more parameters related to the application.
  • the memory and the one or more processors may be configured to receive a second message that indicates a linkage between the container identifier and the one or more parameters, receive a request to report the one or more parameters, where the request includes the container identifier, and transmit a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message.
  • a network entity for wireless communication may include memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to receive, from an AF entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application.
  • the memory and the one or more processors may be configured to associate the container identifier and an application identifier of the application based at least in part on receiving the request, and transmit, to the AF entity, a response to the request, where the response includes the container identifier associated with the application.
  • the memory and the one or more processors may be configured to transmit, to the AF entity, a request for the one or more parameters; and receive, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters.
  • an AMF entity for wireless communication may include memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to receive, from a network entity, a container identifier associated with reporting, by a UE, one or more parameters related to an application of the UE.
  • the memory and the one or more processors may be configured to transmit, to the UE, a first non-access stratum (NAS) message that includes the container identifier based at least in part on receiving the container identifier from the network entity and receive, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the first NAS message to the UE.
  • NAS non-access stratum
  • the memory and the one or more processors may be configured to transmit, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, where the response message is transmitted based at least in part on receiving the second NAS message from the UE.
  • a PCF entity for wireless communication may include memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to receive, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and where the container identifier is associated with reporting, by a UE, one or more parameters related to the application.
  • the memory and the one or more processors may be configured to receive, from the UE, a registration request, and transmit, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier.
  • an AF entity for wireless communication may include memory and one or more processors operatively coupled to the memory.
  • the memory and the one or more processors may be configured to transmit, to a network entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application.
  • the memory and the one or more processors may be configured to receive, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters.
  • the memory and the one or more processors may be configured to receive, from the UE, an application layer registration message associated with the application and transmit, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of a UE, may cause the one or more processors to receive a first message that includes an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application of the UE and where the container identifier is associated with reporting one or more parameters related to the application, receive a second message that indicates a linkage between the container identifier and the one or more parameters, receive a request to report the one or more parameters, where the request includes the container identifier, and transmit a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of a network entity, may cause the one or more processors to receive, from an AF entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, associate the container identifier and an application identifier of the application based at least in part on receiving the request, transmit, to the AF entity, a response to the request, where the response includes the container identifier associated with the application, transmit, to the AF entity, a request for the one or more parameters, and receive, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of an AMF entity, may cause the one or more processors to receive, from a network entity, a container identifier associated with reporting, by a UE, one or more parameters related to an application of the UE, transmit, to the UE, a first NAS message that includes the container identifier based at least in part on receiving the container identifier from the network entity, receive, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the first NAS message to the UE, and transmit, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, wherein the response message is transmitted based at least in part on receiving the second NAS message from the UE.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of a PCF entity, may cause the one or more processors to receive, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, receive, from the UE, a registration request, and transmit, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of an AF entity, may cause the one or more processors to: transmit, to a network entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, receive, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters, receive, from the UE, an application layer registration message associated with the application, and transmit, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request.
  • an apparatus for wireless communication may include means for receiving a first message that includes an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application of the apparatus and where the container identifier is associated with reporting one or more parameters related to the application, means for receiving a second message that indicates a linkage between the container identifier and the one or more parameters, means for receiving a request to report the one or more parameters, where the request includes the container identifier, and means for transmitting a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message.
  • an apparatus for wireless communication may include means for receiving, from an AF entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for associating the container identifier and an application identifier of the application based at least in part on receiving the request, means for transmitting, to the AF entity, a response to the request, where the response includes the container identifier associated with the application, means for transmitting, to the AF entity, a request for the one or more parameters, and means for receiving, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters.
  • an apparatus for wireless communication may include means for receiving, from a network entity, a container identifier associated with reporting, by a UE, one or more parameters related to an application of the UE, means for transmitting, to the UE, a first NAS message that includes the container identifier based at least in part on receiving the container identifier from the network entity, means for receiving, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the first NAS message to the UE, and means for transmitting, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, where the response message is transmitted based at least in part on receiving the second NAS message from the UE.
  • an apparatus for wireless communication may include means for receiving, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for receiving, from the UE, a registration request, and means for transmitting, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier.
  • an apparatus for wireless communication may include means for transmitting, to a network entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for receiving, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters, means for receiving, from the UE, an application layer registration message associated with the application, and means for transmitting, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings, specification, and appendix.
  • Fig. 1 is a block diagram illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure.
  • Fig. 2 is a block diagram illustrating an example of a base station in communication with a UE in a wireless communication network, in accordance with various aspects of the present disclosure.
  • Fig. 3A illustrates an example of a 5G architecture with respect to an application server and a UE.
  • Fig. 3B illustrates an example of a minimization of drive tests (MDT) /self-organizing network (SON) procedure for collecting parameters.
  • MDT minimization of drive tests
  • SON self-organizing network
  • Fig. 4 illustrates one or more examples of registration procedures for establishing an application identifier and a container identifier at a UE, in accordance with various aspects of the present invention.
  • Fig. 5 illustrates an example of registration procedures for a UE, in accordance with various aspects of the present invention.
  • Fig. 6 illustrates an example of an application layer based approach for providing application related parameters to an AF entity, in accordance with various aspects of the present invention.
  • Fig. 7 illustrates an example of an application layer based approach for providing application related parameters to an AF entity, in accordance with various aspects of the present invention.
  • Fig. 8 illustrates an example of an NAS based approach for providing application related parameters to an AF entity, in accordance with various aspects of the present invention.
  • Fig. 9 illustrates an example of an NAS based approach for providing application related parameters to an AF entity, in accordance with various aspects of the present invention.
  • Fig. 10 illustrates an example of a UE receiving a linkage between a container identifier and an application identifier, in accordance with various aspects of the present invention.
  • Fig. 11 illustrates an example of selecting one or more UEs for requesting application related parameters, in accordance with various aspects of the present invention.
  • Fig. 12 is a diagram illustrating an example process for providing application related parameters from a UE, in accordance with various aspects of the present disclosure.
  • Fig. 13 is a diagram illustrating an example process performed, for example, by a network entity, in accordance with various aspects of the present disclosure.
  • Fig. 14 is a diagram illustrating an example process performed, for example, by an AMF entity, in accordance with various aspects of the present disclosure.
  • Fig. 15 is a diagram illustrating an example process performed, for example, by a PCF entity, in accordance with various aspects of the present disclosure.
  • Fig. 16 is a diagram illustrating an example process performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Fig. 1 is a diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced.
  • the wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network.
  • the wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities.
  • a BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, a transmit receive point (TRP) , and/or the like.
  • Each BS may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG) ) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • a BS 110a may be a macro BS for a macro cell 102a
  • a BS 110b may be a pico BS for a pico cell 102b
  • a BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (e.g., three) cells.
  • eNB base station
  • NR BS NR BS
  • gNB gNode B
  • AP AP
  • node B node B
  • 5G NB 5G NB
  • cell may be used interchangeably herein.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.
  • the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.
  • Wireless network 100 may also include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS) .
  • a relay station may also be a UE that can relay transmissions for other UEs.
  • a relay station 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d.
  • a relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.
  • Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100.
  • macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts) .
  • a network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs.
  • Network controller 130 may communicate with the BSs via a backhaul.
  • the BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.
  • UEs 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like.
  • a UE may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet) ) , an entertainment device (e.g., a music or video device, or a satellite radio) , a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device) , or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices.
  • Some UEs may be considered a Customer Premises Equipment (CPE) .
  • UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular RAT and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, and/or the like.
  • a frequency may also be referred to as a carrier, a frequency channel, and/or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like) , a mesh network, and/or the like.
  • V2X vehicle-to-everything
  • the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 shows a block diagram of a design 200 of base station 110 and UE 120, which may be one of the base stations and one of the UEs in Fig. 1.
  • Base station 110 may be equipped with T antennas 234a through 234t
  • UE 120 may be equipped with R antennas 252a through 252r, where in general T ⁇ 1 and R ⁇ 1.
  • a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols.
  • MCS modulation and coding schemes
  • Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS) ) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS) ) .
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream.
  • TX transmit
  • MIMO multiple-input multiple-output
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream.
  • Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • the synchronization signals can be generated with location encoding to convey additional information.
  • antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280.
  • a channel processor may determine reference signal received power (RSRP) , received signal strength indicator (RSSI) , reference signal received quality (RSRQ) , channel quality indicator (CQI) , and/or the like.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSRQ reference signal received quality
  • CQI channel quality indicator
  • one or more components of UE 120 may be included in a housing 284.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, and/or the like) , and transmitted to base station 110.
  • modulators 254a through 254r e.g., for DFT-s-OFDM, CP-OFDM, and/or the like
  • the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120.
  • Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240.
  • Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
  • Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.
  • Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with providing application related parameters from the UE, as described in more detail elsewhere herein.
  • controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 1200 of Fig. 12 and/or other processes as described herein.
  • Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication.
  • a scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.
  • a network entity such as a 5G core function or an application server, may include components such as shown for network controller 130 in Fig. 2.
  • One or more instructions when executed by one or more processors of a network entity, may perform or direct operations of, for example, process 1300 of Fig. 13, process 1400 of Fig. 14, process 1500 of Fig. 15, process 1600 of Fig. 16, and/or other processes as described herein.
  • UE 120 may include means for receiving a first message that includes an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application of the UE and where the container identifier is associated with reporting one or more parameters related to the application, means for receiving a second message that indicates a linkage between the container identifier and the one or more parameters, means for receiving a request to report the one or more parameters, where the request includes the container identifier, means for transmitting a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message, and/or the like.
  • such means may include one or more components of UE 120 described in connection with Fig. 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and/or the like.
  • a network entity such as a network data analytics function (NWDAF) entity
  • NWDAF network data analytics function
  • a network entity may include means for receiving, from an application function (AF) entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for associating the container identifier and an application identifier of the application based at least in part on receiving the request, means for transmitting, to the AF entity, a response to the request, where the response includes the container identifier associated with the application, means for transmitting, to the AF entity, a request for the one or more parameters, means for receiving, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters, and/or the like.
  • such means may include one or more components described in connection with Fig. 2, such as communication unit 294, controller/processor 290, memory 292, and/or the
  • a network entity such as an access and mobility management function (AMF) entity, may include means for receiving, from a network entity, a container identifier associated with reporting, by a UE, one or more parameters related to an application of the UE, means for transmitting, to the UE, a first non-access stratum (NAS) message that includes the container identifier based at least in part on receiving the container identifier from the network entity, means for receiving, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the first NAS message to the UE, means for transmitting, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, where the response message is transmitted based at least in part on receiving the second NAS message from the UE, and/or the like.
  • such means may include one or more components described in connection with Fig. 2, such as communication unit 294, controller/process
  • a network entity such as a policy control function (PCF) entity
  • PCF policy control function
  • a network entity may include means for receiving, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for receiving, from the UE, a registration request, means for transmitting, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier, and/or the like.
  • such means may include one or more components described in connection with Fig. 2, such as communication unit 294, controller/processor 290, memory 292, and/or the like.
  • a network entity such as an AF entity, may include means for transmitting, to a network entity, a request for a container identifier for an application associated with the AF entity, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for receiving, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters, means for receiving, from the UE, an application layer registration message associated with the application, and means for transmitting, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request, and/or the like.
  • such means may include one or more components described in connection with Fig. 2, such as communication unit 294, controller/processor 290, memory 292, and/or the like.
  • a network entity such as an application server, may include means for transmitting, to a network entity, a request for a container identifier for an application associated with the application server, where the container identifier is associated with reporting, by a UE, one or more parameters related to the application, means for receiving, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters, means for receiving, from the UE, an application layer registration message associated with the application, and means for transmitting, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request, and/or the like.
  • such means may include one or more components described in connection with Fig. 2, such as communication unit 294, controller/processor 290, memory 292, and/or the like.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3A illustrates an example 300 of a 5G architecture with respect to an application server and a UE.
  • the 5G architecture may include a next generation radio access network (NG-RAN) , which may include one or more base stations, such as base station 110, that communicated with a UE, such as UE 120, over a Uu interface.
  • the Uu interface is a radio interface between the UE and the NG-RAN.
  • the 5G architecture may include a core network (5GC) that provides communications between the NG-RAN and the outside world, including application servers of companies that may provide data and services to the UE through applications on the UE.
  • NG-RAN next generation radio access network
  • 5GC core network
  • the 5GC may include a unified data management (UDM) entity that makes relevant data available to an AMF entity and a session management function (SMF) entity.
  • the AMF entity manages UE network registration, manages mobility, and maintains an NAS signaling connection with the UE, and manages a registration procedure of the UE with a network.
  • the SMF entity manages sessions and allocates IP addresses to the UE.
  • the 5GC includes a user plane function (UPF) entity that manages user traffic to and from the UE through the NG-RAN and enforces a quality of service (QoS) .
  • the 5GC includes a PCF entity that implements charging rules and flow control rules, and manages traffic priority and a QoS for user subscription services.
  • the 5GC may include a unified data repository (UDR) entity that stores structured data for exposure to network functions and a network exposure function (NEF) entity that securely exposes services and capabilities provided by 3GPP network functions.
  • UDR unified data repository
  • NEF network exposure function
  • the 5GC also includes an AF entity that supports application functionality, influences traffic routing, and interacts with the PCF entity.
  • Fig. 3A is provided as an example. Other examples may differ from what is described with regard to Fig. 3A.
  • Fig. 3B illustrates an example 310 of a minimization of drive tests (MDT) /self-organizing network (SON) procedure for collecting parameters.
  • MDT minimization of drive tests
  • SON self-organizing network
  • An NWDAF entity may request some UE parameters for data analytics.
  • the MDT/SON procedure may be one way of collecting some UE parameters.
  • the NWDAF entity requests a trace report for MDT parameters and receives a trace events report associated with the MDT parameters.
  • NWDAF entities request and receive parameter reports in order to analyze a network or an application utilizing the network.
  • the NWDAF entity requests a trace report from a management system.
  • the management system transmits a trace session activation message to an NG-RAN to start tracing a session and storing MDT parameters.
  • the NG-RAN starts tracing the session and storing the MDT parameters.
  • the NG-RAN decides an MDT procedure associated with the tracing.
  • the NG-RAN may collect supported parameters from a UE or from the NG-RAN itself.
  • the NG-RAN transmits a trace recording report for the MDT procedure to a trace collection entity (TCE) and/or operations, administration and management (OAM) entity.
  • TCE trace collection entity
  • OAM operations, administration and management
  • the OAM transmits the trace events report to the NWDAF.
  • Fig. 3B is provided as an example. Other examples may differ from what is described with regard to Fig. 3B.
  • an NWDAF entity may obtain parameters that are related to an application on a UE and that are provided by the UE.
  • the NWDAF entity may correlate information specific to the application on the UE and/or configure the UE for reporting application related parameters.
  • the UE may provide application related parameters to an AF entity using a transparent container identified by a container identifier.
  • a container may be specific to one parameter or support different parameters.
  • the container may be transparent to lower layers of the UE and the 5GC. That is, the lower layers may view a message with data in a parameter field, but the lower layers may not perform any operations with the data.
  • the AF entity may negotiate with the NWDAF entity for a container identifier for data analytics parameters viewed and/or stored by the AF entity.
  • the NWDAF entity may create a binding between the UE and the AF entity in order to route the container, using the container identifier, to the AF entity. This binding may include a linkage between an application identifier of the application and the container identifier.
  • the NWDAF entity may use an application based approach and/or an NAS based approach to request and receive the application related parameters from the UE.
  • the AF entity may configure the container identifier and the application related parameters during a registration of the UE to the AF entity.
  • the AF entity may send the application related parameters that are requested to the UE. If the AF entity receives a parameter request from the NWDAF, the AF entity may request the UE to report the parameters (with the container identifier) via application layer signaling.
  • the NWDAF and the 5GC may not need to operate on the application related parameters.
  • the NWDAF entity may configure the application related parameters to the UE as a transparent container via NAS signaling (e.g., UE configuration update) .
  • NAS signaling e.g., UE configuration update
  • the NWDAF entity may receive and request application related parameters by which an application designer for the application may improve performance and functionality of the. Improved performance may save power, processing, and signaling resources. Users may also have an improved user experience if the application has more functionality or offerings that are based at least in part on obtaining the application related parameters.
  • Fig. 4 illustrates one or more examples 400 of registration procedures for establishing an application identifier and a container identifier at a UE, in accordance with various aspects of the present invention.
  • Fig. 4 illustrates a UE 410 using a 5GC 420 to communicate with an AF entity 430.
  • AF entity 430 may coordinate communication with or represent an application server for a third-party (e.g., social media application company, telecommunications company, gaming company, products company, services company, and/or the like) .
  • a third-party e.g., social media application company, telecommunications company, gaming company, products company, services company, and/or the like.
  • 5GC 420 may establish an application identifier for an application associated with AF entity 430 and a container identifier for identifying a container in which application related parameters related to the application may be provided from UE 410 to AF entity 430.5GC 420 may transmit, via NAS signaling, a first message with the container identifier and the application identifier to an NAS signaling component 412 of UE 410.5GC 420 may also transmit the container identifier and the application identifier to the AF entity 430.
  • AF entity 430 may transmit, via application layer signaling, a second message with the application related parameters and the container identifier to an application layer component 414 of UE 410.
  • AF entity 430 and UE 310 may also negotiate the application related parameters.
  • UE 410 may link the application identifier and the application related parameters based at least in part on the container identifier in the first and second messages.
  • UE 410 may be prepared to collect and transmit the application related parameters to AF entity 430 in the container identified by the container identifier.
  • the container identifier is specific to the application.
  • the container identifier may be associated with a single parameter related to the application or multiple parameters related to the application.
  • the container identifier may be one of multiple container identifiers associated with the application, where each container identifier of the multiple container identifiers is associated with different parameters related to the application.
  • AF entity 430 may request the container identifier from an NWDAF entity, which may be responsible for allocation of container identifiers for different applications.
  • the container identifier may be unique in the NWDAF entity and may not be shared by multiple applications. The same container identifier may be used by different UEs.
  • the NWDAF entity, associated with 5GC 420, may use the container identifier to link the container identifier to AF entity 430, which may request the application related parameters from UE 410.
  • UE 410 may not see the application identifier in a request from AF entity 430 for the application related parameters, and UE 410 may use the link to identify the application identifier.
  • the UE 410 may use the application identifier to instruct the application identified by the application identifier to collect the application related parameters, which may include data and other information for parameters specified in a request from AF entity 430.
  • the NWDAF entity may use the container identifier to route information based on the application related parameters (e.g., optimization/analytics data) to the appropriate AF entity or application server, which in this example is AF entity 430.
  • AF entity 430 may provide the container identifier to a PCF entity.
  • UE 410 may transmit a registration request to the PCF entity.
  • the PCF entity may provide UE policy information (e.g., UE route selection policies (URSP) ) to UE 410.
  • the PCF entity may provide the container identifier in the URSP to UE 410 (in both NAS signaling and application layer based approaches) .
  • URSP UE route selection policies
  • Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
  • Fig. 5 illustrates an example 500 of registration procedures for a UE (e.g., UE 410) , in accordance with various aspects of the present invention.
  • Fig. 5 shows the UE registering with a 5GC (e.g., 5GC 420) and with an AF entity (e.g., AF entity 430) .
  • 5GC e.g., 5GC 420
  • AF entity e.g., AF entity 430
  • the UE may establish a Protocol Data Unit (PDU) session with the 5GC.
  • the UE may register an application with the AF entity at the application layer.
  • the UE may receive an acknowledgement of registration at the application layer.
  • the acknowledgement may include a container identifier and requested parameters related to the application.
  • the UE may receive separate container identifiers for respective applications. For example, the UE may receive a first container identifier (ID 1) corresponding to a quality of experience (QoE) of the application and a second container identifier (ID 2) corresponding to an uplink pending time for the application.
  • ID 1 a first container identifier
  • QoE quality of experience
  • ID 2 second container identifier
  • Fig. 5 is provided as an example. Other examples may differ from what is described with regard to Fig. 5.
  • Fig. 6 illustrates an example 600 of an application layer based approach for providing application related parameters to AF entity 430, in accordance with various aspects of the present invention.
  • Fig. 6 shows UE 410 providing the application related parameters to AF entity 430, at a request of an NWDAF entity 610 associated with 5GC 420.
  • NWDAF entity 610 may transmit an application parameter request to AF entity 430.
  • AF entity 430 may transmit, via application layer signaling, a parameter request with a container identifier to UE 410.
  • UE 410 may, based at least in part on receiving the parameter request with the container identifier, determine application related parameters and generate a report that includes the application related parameters.
  • UE 410 may provide the report in an application parameter container identified by the container identifier.
  • UE 410 may transmit, via application layer signaling, the application parameter container to AF entity 430.
  • AF entity 430 may transmit an application parameter response to NWDAF entity 610 with the application related parameters.
  • Fig. 6 is provided as an example. Other examples may differ from what is described with regard to Fig. 6.
  • Fig. 7 illustrates an example 700 of an application layer based approach for providing application related parameters to an AF entity (e.g., AF entity 430) , in accordance with various aspects of the present invention.
  • Fig. 7 shows a UE (e.g., UE 410) providing the application related parameters to the AF entity, at a request of an NWDAF entity (e.g., NWDAF 610) .
  • NWDAF entity e.g., NWDAF 610
  • a network function (NF) of an AMF entity may transmit a request to the NWDAF entity for analytics related to an application.
  • the NWDAF entity may transmit an application parameter request to the AF entity.
  • the application parameter request may be triggered by the NWDAF entity or other entities.
  • the AF entity may request, via application layer signaling, that the UE report on application related parameters.
  • the application layer signaling may include a container identifier.
  • the application layer signaling may also include a report threshold and/or a report period for one or more of the application related parameters.
  • the UE may report the application related parameters in an application parameter container to the AF entity via application layer signaling.
  • the AF entity may receive the application related parameters and transmit a response message to the NWDAF entity with the application related parameters.
  • Fig. 7 is provided as an example. Other examples may differ from what is described with regard to Fig. 7.
  • Fig. 8 illustrates an example 800 of an NAS based approach for providing application related parameters to AF entity 430, in accordance with various aspects of the present invention.
  • Fig. 8 shows UE 410 providing the application related parameters to AF entity 430, at a request of an NWDAF entity.
  • the NWDAF entity may be associated with 5GC 420 and request application related parameters.
  • AF entity 430 may transmit a parameter request with a container identifier to 5GC 420.
  • the parameter request may pass through to an AMF entity.
  • 5GC 420, or the respective AMF entity in 5GC 420 may transmit the parameter request to UE 410 via NAS signaling.
  • UE 410 may, based at least in part on receiving the parameter request with the container identifier, determine application related parameters and generate a report that includes the application related parameters.
  • UE 410 may provide the report in an application parameter container identified by the container identifier.
  • UE 410 may transmit, via NAS signaling, the application parameter container to 5GC 420, or the respective AMF entity in 5GC 420.
  • UE 410 may transmit, via NAS signaling, the application parameter container to AF entity 430.
  • the NWDAF entity may receive the application related parameters.
  • Fig. 8 is provided as an example. Other examples may differ from what is described with regard to Fig. 8.
  • Fig. 9 illustrates an example 900 of an NAS based approach for providing application related parameters to an AF entity (e.g., AF entity 430) , in accordance with various aspects of the present invention.
  • Fig. 9 shows a UE (e.g., UE 410) providing the application related parameters to the AF entity, at a request of an NWDAF entity (e.g., NWDAF entity 610) .
  • NWDAF entity e.g., NWDAF entity 610
  • the NWDAF entity may transmit an application parameter request to the AF entity.
  • the AF entity may transmit a request to the NWDAF entity for application related parameters from the UE with a container identifier.
  • the NWDAF entity may transmit the request to an AMF entity.
  • the AMF entity may transmit the request to the UE via NAS PDU delivery.
  • the UE may transmit the application parameter container to the AMF entity.
  • the AMF entity may transmit the application parameter container in a UE parameter response to the NWDAF entity.
  • the UE parameter response may be a message that includes the container identifier and a field that includes the parameters.
  • the application parameter container may be a transparent container.
  • the NWDAF entity may transmit the UE parameter response to the AF entity.
  • the AF entity may transmit an application parameter response with the application related parameters to the NWDAF entity.
  • the AF entity may perform some data handling to provide information to the NWDAF entity that the NWDAF entity may not have been able to obtain or process earlier, when passing along the (transparent) application parameter container.
  • Fig. 9 is provided as an example. Other examples may differ from what is described with regard to Fig. 9.
  • Fig. 10 illustrates an example 1000 of a UE (e.g., UE 410) receiving a linkage between a container identifier and an application identifier, in accordance with various aspects of the present invention.
  • a UE e.g., UE 410
  • an AF entity may request and receive a container identifier from a PCF entity.
  • the PCF entity may provide the container identifier and an application identifier in a registration response message to an NAS component of a UE.
  • the container identifier may be in a UE policy.
  • the AF entity may provide the container identifier and requested parameters to an application layer component of the UE.
  • the UE may link the application identifier and the requested parameters based at least in part on the container identifier.
  • an NWDAF entity may request application related parameters and any of the processes described in Figs. 6-9 may be used to provide the application related parameters of the UE to the NWDAF entity.
  • Fig. 10 is provided as an example. Other examples may differ from what is described with regard to Fig. 10.
  • Fig. 11 illustrates an example 1100 of selecting one or more UEs for requesting application related parameters, in accordance with various aspects of the present invention.
  • an NWDAF entity may transmit a request for application related parameters to an AF entity.
  • the AF entity may transmit a request for application related parameters for a UE to the NWDAF entity.
  • the NWDAF entity may transmit a UE identity request, with an application identifier and a UE application identifier, to a PCF entity.
  • the application identifier may identify the application (e.g., popular social media application) .
  • the UE application identifier may identify the UE, a user of the UE, or a user account of the UE in connection with the application (e.g., social application username associated with a UE session) .
  • the PCF entity may provide a response with a UE identifier, such as an international mobile subscriber identity (IMSI) of the UE.
  • IMSI international mobile subscriber identity
  • the UE identifier may identify the UE in connection with a network subscription, and may use the UE identifier for charging the UE according to a UE policy. For example, a byte counter may be used to determine a UE data usage (e.g., for a username the application received from the UE) .
  • the NWDAF entity may proceed with transmitting a request for application related parameters for the UE, based at least in part on the UE identifier (e.g., IMSI) , according to any of the procedures described in Figs. 6-10.
  • Fig. 11 is provided as an example. Other examples may differ from what is described with regard to Fig. 11.
  • Fig. 12 is a diagram illustrating an example process 1200 performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Example process 1200 is an example where a UE (e.g., UE 120, UE 410, and/or the like) performs operations associated with providing application related parameters from a UE.
  • a UE e.g., UE 120, UE 410, and/or the like
  • process 1200 may include receiving a first message that includes an application identifier and a container identifier that corresponds to the application identifier.
  • the application identifier identifies an application of the UE.
  • the container identifier is associated with reporting one or more parameters related to the application (block 1210) .
  • the UE e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like
  • the application identifier identifies an application of the UE.
  • the container identifier is associated with reporting one or more parameters related to the application.
  • process 1200 may include receiving a second message that indicates a linkage between the container identifier and the one or more parameters (block 1220) .
  • the UE e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like
  • process 1200 may include receiving a request to report the one or more parameters, wherein the request includes the container identifier (block 1230) .
  • the UE e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like
  • the request includes the container identifier.
  • process 1200 may include transmitting a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message (block 1240) .
  • the UE may transmit a report that includes the one or more parameters based at least in part on receiving the request, identifying the application for which the one or more parameters are to be reported based at least in part on the first message, and identifying the one or more parameters associated with the container identifier based at least in part on the second message, as described above.
  • Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the first message is received from the PCF entity based at least in part on transmitting the registration request, and the first message is a registration response that includes policy information.
  • the policy information is associated with a UE route selection policy.
  • the second message is received from the application function entity based at least in part on transmitting the application layer registration message, where the second message is an application layer registration acknowledgement.
  • the first message is received from a policy control function entity and the second message is received from an application function entity.
  • the request to report the one or more parameters is received in a first application layer signaling message received from an application function entity.
  • the report is transmitted to the application function entity in a second application layer signaling message.
  • the request to report the one or more parameters is received in a first NAS signaling message received from an AMF entity.
  • the report is transmitted to the AMF entity in a second NAS signaling message.
  • the report includes the container identifier.
  • the request indicates at least one of a reporting threshold for the report or a reporting periodicity for the report.
  • the report is transmitted based at least in part on at least one of the reporting threshold or the reporting periodicity.
  • the container identifier is specific to the application.
  • the container identifier is associated with a single parameter related to the application.
  • the container identifier is associated with multiple parameters related to the application.
  • the container identifier is one of multiple container identifiers associated with the application. In some aspects, each container identifier of the multiple container identifiers is associated with a different one or more parameters related to the application.
  • process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
  • Fig. 13 is a diagram illustrating an example process 1300 performed, for example, by a network entity, in accordance with various aspects of the present disclosure.
  • Example process 1300 is an example where a network entity (e.g., an NWDAF entity, and/or the like) performs operations associated with providing application related parameters from a UE.
  • a network entity e.g., an NWDAF entity, and/or the like
  • process 1300 may include receiving, from an AF entity, a request for a container identifier for an application associated with the AF entity (block 1310) .
  • the container identifier is associated with reporting one or more parameters related to the application.
  • the network entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the container identifier is associated with reporting one or more parameters related to the application.
  • process 1300 may include associating the container identifier and an application identifier of the application, based at least in part on receiving the request (block 1320) .
  • the network entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1300 may include transmitting, to the AF entity, a response to the request, where the response includes the container identifier associated with the application (block 1330) .
  • the network entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the response includes the container identifier associated with the application.
  • process 1300 may include transmitting, to the AF entity, a request for the one or more parameters (block 1340) .
  • the network entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1300 may include receiving, from the AF entity, the one or more parameters based at least in part on transmitting the request for the one or more parameters (block 1350) .
  • the network entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the network entity is a network data analytics function entity.
  • process 1330 further comprises performing one or more data analytics functions based at least in part on the one or more parameters, and the AF entity is identified based at least in part on associating the container identifier and the application identifier.
  • process 1300 further comprises receiving, from the AF entity, the container identifier based at least in part on transmitting the request for the one or more parameters to the AF entity, transmitting the container identifier to an AMF entity based at least in part on receiving the container identifier from the AF entity, receiving, from the UE via the AMF entity, a response message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the container identifier to the AMF entity; transmitting the response message to the AF entity, and receiving the one or more parameters from the AF entity based at least in part on transmitting the response message to the AF entity.
  • process 1300 further comprises transmitting, to a policy control function entity, a message that includes the application identifier and the container identifier.
  • process 1300 further comprises the UE application identifier identifying the UE or a user of the UE in connection with the application.
  • the request for the UE identifier includes the application identifier and the UE application identifier and the UE identifier identifies the UE in connection with a network subscription.
  • process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.
  • Fig. 14 is a diagram illustrating an example process 1400 performed, for example, by an AMF entity, in accordance with various aspects of the present disclosure.
  • Example process 1400 is an example where the AMF entity (e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like) performs operations associated with providing application related parameters from a UE.
  • the AMF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1400 may include receiving, from a network entity, a container identifier associated with reporting one or more parameters related to an application of the UE (block 1410) .
  • the AMF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1400 may include transmitting, to the UE, a first NAS message that includes the container identifier based at least in part on receiving the container identifier from the network entity (block 1420) .
  • the AMF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1400 may include receiving, from the UE, a second NAS message that includes the container identifier and a field that includes the one or more parameters, based at least in part on transmitting the first NAS message to the UE (block 1430) .
  • the AMF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1400 may include transmitting, to the network entity, a response message that includes the container identifier and a field that includes the one or more parameters, wherein the response message is transmitted based at least in part on receiving the second NAS message from the UE (block 1440) .
  • the AMF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the response message is transmitted based at least in part on receiving the second NAS message from the UE.
  • process 1400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 14. Additionally, or alternatively, two or more of the blocks of process 1400 may be performed in parallel.
  • Fig. 15 is a diagram illustrating an example process 1500 performed, for example, by a PCF entity, in accordance with various aspects of the present disclosure.
  • Example process 1500 is an example where a PCF entity performs operations associated with providing application related parameters from a UE.
  • process 1500 may include receiving, from a network entity, an application identifier and a container identifier that corresponds to the application identifier, where the application identifier identifies an application and wherein the container identifier is associated with reporting one or more parameters related to the application (block 1510) .
  • the PCF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the application identifier identifies an application.
  • the container identifier is associated with reporting one or more parameters related to the application.
  • process 1500 may include receiving, from the UE, a registration request (block 1520) .
  • the PCF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1500 may include transmitting, to the UE, a registration response that includes policy information associated with a UE route selection policy, where the policy information includes the application identifier and the container identifier (block 1530) .
  • the PCF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the policy information includes the application identifier and the container identifier.
  • Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the request for the UE identifier includes the application identifier and a UE application identifier that identifies the UE or a user of the UE in connection with the application; and the UE identifier identifies the UE in connection with a network subscription.
  • process 1500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 15. Additionally, or alternatively, two or more of the blocks of process 1500 may be performed in parallel.
  • Fig. 16 is a diagram illustrating an example process 1600 performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Example process 1600 is an example where an AF entity performs operations associated with providing application related parameters from a UE.
  • process 1600 may include transmitting, to a network entity, a request for a container identifier for an application associated with the AF entity, wherein the container identifier is associated with reporting one or more parameters related to the application (block 1610) .
  • the AF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the container identifier is associated with reporting one or more parameters related to the application.
  • process 1600 may include receiving, from the network entity, a response to the request, where the response includes the container identifier associated with the application and the one or more parameters (block 1620) .
  • the AF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • the response includes the container identifier associated with the application and the one or more parameters.
  • process 1600 may include receiving, from the UE, an application layer registration message associated with the application (block 1630) .
  • the AF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • process 1600 may include transmitting, to the UE, an application layer registration acknowledgement that indicates a linkage between the container identifier and the one or more parameters based at least in part on receiving the application layer registration message and the response to the request (block 1640) .
  • the AF entity e.g., using communication unit 294, controller/processor 290, memory 292, and/or the like
  • Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 1600 further comprises receiving, from the network entity, a request for the one or more parameters and transmitting the one or more parameters to the network entity based at least in part on receiving the request for the one or more parameters.
  • the request includes the container identifier
  • process 1600 further comprises receiving, from the UE, a report that includes the one or more parameters based at least in part on transmitting the request to report the one or more parameters, and transmitting the one or more parameters to the network entity based at least in part on receiving the report.
  • the request includes the container identifier; and process 1600 further comprises receiving, from the network entity, a response message that includes the container identifier and a field that includes the one or more parameters based at least in part on transmitting the request to report the one or more parameters, and transmitting the one or more parameters to the network entity based at least in part on receiving the response message.
  • process 1600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 16. Additionally, or alternatively, two or more of the blocks of process 1600 may be performed in parallel.
  • the appendix is provided as an example only, and is to be considered part of the specification.
  • a definition, illustration, or other description in the appendix does not supersede or override similar information included in the detailed description or figures.
  • a definition, illustration, or other description in the detailed description or figures does not supersede or override similar information included in the appendix.
  • the appendix is not intended to limit the disclosure of possible aspects.
  • ком ⁇ онент is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software.
  • a processor is implemented in hardware, firmware, and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

Landscapes

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

Abstract

De manière générale, divers aspects de l'invention concernent la communication sans fil. Selon certains aspects, un UE peut recevoir un premier message qui comprend un identifiant d'application ainsi qu'un identifiant de conteneur qui correspond à l'identifiant d'application. L'identifiant d'application identifie une application de l'UE et l'identifiant de conteneur est associé au signalement d'un ou de plusieurs paramètres liés à l'application. L'UE peut recevoir un second message qui indique une liaison entre l'identifiant de conteneur et les paramètres. L'UE peut recevoir une demande de signalement des paramètres, la demande comprenant l'identifiant de conteneur. L'UE peut transmettre un rapport qui comprend les paramètres. L'invention concerne de nombreux autres aspects.
PCT/CN2019/115954 2019-11-06 2019-11-06 Fourniture de paramètres relatifs à une application WO2021087802A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/115954 WO2021087802A1 (fr) 2019-11-06 2019-11-06 Fourniture de paramètres relatifs à une application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/115954 WO2021087802A1 (fr) 2019-11-06 2019-11-06 Fourniture de paramètres relatifs à une application

Publications (1)

Publication Number Publication Date
WO2021087802A1 true WO2021087802A1 (fr) 2021-05-14

Family

ID=75849411

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/115954 WO2021087802A1 (fr) 2019-11-06 2019-11-06 Fourniture de paramètres relatifs à une application

Country Status (1)

Country Link
WO (1) WO2021087802A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702798A (zh) * 2017-03-01 2018-10-23 华为技术有限公司 数据传输的方法与装置
US20190207778A1 (en) * 2017-12-28 2019-07-04 Weihua QIAO Service Type and Device Type-based Policy and Charging Control
CN110300006A (zh) * 2018-03-21 2019-10-01 中国移动通信有限公司研究院 数据处理方法及装置、功能实体及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702798A (zh) * 2017-03-01 2018-10-23 华为技术有限公司 数据传输的方法与装置
US20190207778A1 (en) * 2017-12-28 2019-07-04 Weihua QIAO Service Type and Device Type-based Policy and Charging Control
CN110300006A (zh) * 2018-03-21 2019-10-01 中国移动通信有限公司研究院 数据处理方法及装置、功能实体及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "IAB node Registration procedure", 3GPP DRAFT; S2-1910280_WAS_1909350_23.502_IAB-NODE REGISTRATION_R2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Split Croatia; 20191014 - 20191018, 17 October 2019 (2019-10-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051797040 *

Similar Documents

Publication Publication Date Title
EP4038973A1 (fr) Accès à un réseau privé autonome
WO2021040918A1 (fr) Techniques de gestion de regroupement de canaux de commande de liaison montante physique pour multiples points d'émission-réception
EP4032218A1 (fr) Techniques de planification d'un signal de référence d'informations d'état de canal de liaison latérale à chargement frontal
EP3785386B1 (fr) Rapport d'indicateur de qualité de canal (cqi) basé sur un accès multiple non orthogonal (noma)
WO2022036490A1 (fr) Modification d'un budget de retard de paquet de flux de qualité de service
WO2021011174A1 (fr) Règles de priorité associées à un quasi colocalisation de point d'émission/réception multiple basé sur des informations de commande de liaison descendante multiples
WO2022236464A1 (fr) Configuration d'identifiant pour prendre en charge des mesures de qualité d'expérience
WO2021120151A1 (fr) Fourniture de paramètres liés à l'application, via une signalisation de plan utilisateur
US20220190990A1 (en) Network-configured training procedure
WO2021253394A1 (fr) Recherche de réseau mobile terrestre public pour règle de politique de sélection d'itinéraire d'équipement utilisateur
WO2021232390A1 (fr) Configuration d'informations de commande de liaison descendante de signaux de référence de sondage communs d'un groupe
WO2021243690A1 (fr) Recherche de réseau mobile terrestre public après rejet d'unité de données de protocole
EP3888399B1 (fr) Affectation de ressources pour des ressources réservées
EP4097856A1 (fr) Techniques d'indication de faisceaux pour un rapport de faisceau d'équipement utilisateur
WO2021087802A1 (fr) Fourniture de paramètres relatifs à une application
WO2020206131A1 (fr) Indication de faisceau pour transmissions semi-persistantes
WO2020167555A1 (fr) Interdiction d'accès et connexion de commande de ressource radio dans une nouvelle radio pour reprise vocale d'évolution à long terme
WO2021243622A1 (fr) Association d'identifiants d'application à des tranches de réseau
WO2021232399A1 (fr) Restauration d'un service de données dans un réseau autonome
WO2021237690A1 (fr) Restauration d'un service de données dans un réseau autonome
WO2021207917A1 (fr) Restauration de connectivité de données après défaillance par libérations de connexions de rrc en réseau non autonome
WO2021232327A1 (fr) Gestion de liaison montante pour une configuration de porteuse radio de données divisées de liaison montante
WO2024011394A1 (fr) Temps d'application de faisceau (bat) pour le fonctionnement d'un point d'émission et de réception (mtrp) basé sur un indicateur de configuration de transmission (tci) unifié
WO2022198430A1 (fr) Traitement de consentement
WO2022027544A1 (fr) Commutation d'antenne de signal de référence de sondage (srs) pour un équipement utilisateur (ue) à émetteurs-récepteurs mutiples

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

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

Country of ref document: EP

Kind code of ref document: A1