WO2025123738A1 - Procédé et appareil d'aide à la collecte de données - Google Patents

Procédé et appareil d'aide à la collecte de données Download PDF

Info

Publication number
WO2025123738A1
WO2025123738A1 PCT/CN2024/112361 CN2024112361W WO2025123738A1 WO 2025123738 A1 WO2025123738 A1 WO 2025123738A1 CN 2024112361 W CN2024112361 W CN 2024112361W WO 2025123738 A1 WO2025123738 A1 WO 2025123738A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
request message
information
processor
dccf
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2024/112361
Other languages
English (en)
Inventor
Congchi ZHANG
Mingzeng Dai
Lizhuo ZHENG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/112361 priority Critical patent/WO2025123738A1/fr
Publication of WO2025123738A1 publication Critical patent/WO2025123738A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00—Machine learning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present disclosure relates to wireless communications, and more specifically to techniques of supporting data collection, e.g., user equipment (UE) side data collection.
  • UE user equipment
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as UE, or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • the request message indicates one or more of the following: indication on whether UE should transmit collected data over IP connection or not; destination address information; criteria information of interested data; description information of interested data; notification correlation identifier (ID) ; logging configuration on how UE should perform data logging; or reporting configuration on how UE should perform data reporting.
  • indication on whether UE should transmit collected data over IP connection or not indicates one or more of the following: indication on whether UE should transmit collected data over IP connection or not; destination address information; criteria information of interested data; description information of interested data; notification correlation identifier (ID) ; logging configuration on how UE should perform data logging; or reporting configuration on how UE should perform data reporting.
  • ID notification correlation identifier
  • Figure 5 illustrates an example of a UE in accordance with aspects of the present disclosure.
  • Figure 6 illustrates an example of a processor in accordance with aspects of the present disclosure.
  • Figure 7 illustrates an example of a network apparatus in accordance with aspects of the present disclosure.
  • Figure 8 illustrates a flowchart of method performed by a UE in accordance with aspects of the present disclosure.
  • Figure 9 illustrates a flowchart of method performed by a data consumer node in accordance with aspects of the present disclosure.
  • Figure 10 illustrates another flowchart of method performed by a CN entity in accordance with aspects of the present disclosure.
  • AI machine learning
  • ML machine learning
  • NNs training neural networks
  • CV computer vison
  • NLP nature language processing
  • Deep learning which is a subordinate concept of ML, utilizes multi-layered NNs as an “AI model” (or referred to as AI/ML model or the like) or "AI-based model” (or referred to as AI/ML based model or the like) to learn how to solve problems and/or optimize performance from vast amounts of data.
  • AI models used on AI-based methods are well trained, the AI-based methods can obtain better performance than the traditional methods.
  • 3GPP 3rd generation partnership program
  • AI/ML models at RAN side can be trained by gNB or OAM, and the data collection for training relies on existing layer 1 (L1) measurement report (e.g., channel state information (CSI) report) and layer 3 (L3) measurement report (e.g., radio resource control (RRC) measurement report) framework with enhancements.
  • L1 measurement report e.g., channel state information (CSI) report
  • L3 measurement report e.g., radio resource control (RRC) measurement report
  • RRC radio resource control
  • a CSI report is enhanced to convey the measurement results of more beams.
  • a RRC measurement report in RRC connected state is enhanced to support logging of measurement results and report the logged results later, because the data collection for AI/ML training has relaxed latency requirements.
  • the current UE side data collection is based on the legacy 5G framework via existing and/or enhanced control plane signaling, which is not suitable for collecting training data in a large size or scale.
  • UP user plane
  • data plane so that collecting data in a large size or scale will be more feasible.
  • An exemplary UE may receive a request message associated with data collection from a RAN node or a CN entity.
  • UE may receive a NAS message associated with data collection from a DCCF or an AMF, or receive a message (e.g., an application layer message) associated with data collection from a DCAF, or receive a RRC message associated with data collection from a gNB.
  • UE may perform data collection based on the received request message or already have collected and stored the requested data before receiving the request message.
  • UE may determine a destination address based on the request message, e.g., the address of DCCF, MFAF, DCAF or RAN node etc., and transmit the collected data to the destination address over an IP connection.
  • a data consumer node e.g., a RAN node, an over the top (OTT) server, a CN entity (e.g., an AF) or an OAM etc.
  • An exemplary data consumer node may transmit a request message associated with data collection, e.g., via the DCCF or directly to the UE (e.g., in the case of a RAN node as the data consumer node) .
  • the data consumer node may receive UE collected data in response to the request message over an IP connection, e.g., from the DCCF or MFAF or directly from the UE via user plane function (UPF) (e.g., in the case of a RAN node as the data consumer node) .
  • IP connection e.g., from the DCCF or MFAF or directly from the UE via user plane function (UPF) (e.g., in the case of a RAN node as the data consumer node) .
  • UPF user plane function
  • An exemplary CN entity e.g., a DCCF may receive a first request message associated with data collection from a data consumer node, e.g., from a RAN node, an OTT server, a CN entity or an OAM etc.
  • the DCCF may select a UE for data collection by itself based on the first request message, or transmit UE selection related information to another network node or entity, e.g., an AMF or a DCAF etc., based on the first request message, so that a UE for data collection will be selected by the AMF or DCAF etc.
  • FIG. 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more NE 102, one or more UE 104, and a CN 106.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • 5G network such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • 5G-A 5G-Advanced
  • 5G-UWB 5G ultrawideband
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN) , a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection.
  • an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area.
  • an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) .
  • NTN non-terrestrial network
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
  • the one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • An NE 102 may support communications with the CN 106, or with another NE 102, or both.
  • an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N3, or network interface) .
  • the NE 102 may communicate with each other directly.
  • the NE 102 may communicate with each other or indirectly (e.g., via the CN 106.
  • one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
  • NAS non-access stratum
  • the CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N3, or another network interface) .
  • the packet data network may include an application server.
  • one or more UEs 104 may communicate with the application server.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102.
  • the CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106) .
  • the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • a data consumer CN node can request data from DCCF, and DCCF will find the corresponding data source CN node and deliver the data from the data source CN node to the data consumer CN node.
  • NWDAF network data analytics function
  • DCCF will find the corresponding data source CN node and deliver the data from the data source CN node to the data consumer CN node.
  • the current 5GC data collection framework does not involve gNB or UE, and does not support UE side data collection.
  • Session management function may mainly include the following functionalities, wherein part or all of the SMF functionalities may be supported in a single instance of SMF or the like:
  • Session management e.g., session establishment, modifying and releasing, including tunnel maintain between UPF and access network (AN) node
  • UPF may mainly include the following functionalities, wherein part or all of the UPF functionalities may be supported in a single instance of UPF or the like:
  • Packet routing &forwarding e.g. support of uplink classifier to route traffic flows to an instance of a data network, support of Branching point to support multi-homed PDU Session, support of traffic forwarding within a 5G virtual network (VN) group (UPF local switching, via N6, via N19) )
  • VN virtual network
  • DCCF may mainly include the following functionalities, wherein part or all of the DCCF functionalities may be supported in a single instance of DCCF or the like:
  • MFAF may mainly include the following functionalities, wherein part or all of the MFAF functionalities may be supported in a single instance of MFAF or the like:
  • DCAF may mainly include the following functionalities, wherein part or all of the DCAF functionalities may be supported in a single instance of DCAF or the like:
  • RAN may mainly host the following functionalities, wherein part or all of the RAN functionalities may be supported in a single RAN node or the like:
  • radio bearer control radio admission control
  • connection mobility control dynamic allocation of resources to UEs in both uplink and downlink (scheduling)
  • the data that can be collected from UE side may be one or more of: L1 operation related data, L3 operation related data, or application layer operation related data.
  • Exemplary L1 operation related data may include one or more of the following:
  • - Identification information of the target UE e.g., subscription permanent identifier (SUPI) , or globally unique temporary identity (GUTI) or the like
  • ⁇ Cell information e.g., a list of interested cells
  • ⁇ SSB information e.g., a list of interested SSB indexes
  • ⁇ UE type information e.g., MIMO capable UE, IoT UE, stationary UE, moving UE
  • the DCCF may check or collect information related to the requested data collection. For example, the DCCF may check whether the data consumer is authenticated to perform UE side data collection for specific UE (s) , e.g., with the authentication server function (AUSF) (not shown) , check whether the related UE consent (s) is available, e.g., with the unified data management (UDM) (not shown) , and/or check whether any related policy (e.g., privacy policy) is available, e.g., with the point coordination function (PCF) or binding support function (BSF) (not shown) .
  • AUSF authentication server function
  • UDM unified data management
  • PCF point coordination function
  • BSF binding support function
  • the DCCF may determine or select a UE from which the interested data can be requested. For example, the DCCF may determine a UE based on one or more of the following: UE identification information, e.g., provided in the first request message, UE location related information, UE subscription information, or UE data collection policy information.
  • UE location related information e.g., current serving cell etc.
  • the DCCF may request the AMF to provide the UE information in a certain serving cell.
  • the UE subscription information it may be provided by the UDM, e.g., by the aforementioned checking.
  • the UE data collection policy information it may be provided by the PCF or BSF, e.g., by the aforementioned checking.
  • the DCCF may directly or indirectly request or subscribe UE side data from the selected UE, and accordingly, the UE may receive a message (hereinafter, second request message) that requests or subscribes UE side data.
  • second request message a message that requests or subscribes UE side data.
  • the DCCF may generate a NAS message as the second request message and directly transmit the NAS message to the UE in step 205.
  • the DCCF may transmit a message indicating information associated with generating the second request message to the AMF in step 207a.
  • the AMF may generate a NAS message as the second request message based on the information received from the DCCF, and then transmit the NAS message to the selected UE in step 207b.
  • exemplary address information may be a uniform resource identifier (URI) , an IP address, a port number, fully qualified domain name (FQDN) etc.; in addition, in the case of a RAN node as a data consumer, the data forwarding or notification to the RAN node may also be performed by the MFAF or DCCF, while UE does not need to know that the address is owned by which entity or node
  • - Reporting configuration on how UE should perform data reporting e.g., periodicity and/or duration etc., of data reporting; for example, UE should report the logged data every period of time within an overall duration.
  • the DCCF may even not select the UE by itself and need the AMF to determine the UE.
  • the DCCF may transmit UE selection related information, e.g., including identification information of target UE (s) , criteria information and/or the description information of the interested data etc., to the AMF step 207a.
  • the AMF may select the UE that fulfills the criteria information and/or the description information of interested data, e.g., if UE is served by a cell or frequency of interest.
  • the information that the AMF may use to determine the UE is similar to that used by the DCCF, and will not repeat.
  • the AMF may generate a NAS message as the second request message in the case that the DCCF also provides information associated with generating the second request message, and then transmit the NAS message to the selected UE in step 207b.
  • the AMF may report the selected UE to the DCCF.
  • the AMF may lack the information related to generation of the second request message, and the DCCF may generate and transmit a NAS message to the UE selected and reported by the AMF similar to that in step 205.
  • the DCCF may configure the additional CN entity, e.g., the MFAF with respect to messaging rules for data forwarding or notification.
  • the DCCF may generate a Nmfaf_3daDataManagmenet_Configure message to configure the MFAF with respect to the messaging rules, e.g., indicating address information for data notification and/or information that will be further carried together with received UE collected data to associate with the received UE collected data with a data notification address.
  • Exemplary address information for data notification may include a notification address, e.g., URI, IP address, port number and/or FQDN etc., of data consumer.
  • Exemplary information that will be further carried together with the received data from UE for the node or entity for data forwarding, e.g., MFAF may include: a) a notification correlation ID for the data consumer if the configuration is used for mapping analytics or data collection; and/or b) UE ID information e.g., SUPI etc. For example, if the MFAF receives data from the data source associated with the notification correlation ID indicated in the configuration information, the MFAF is expected to forward the received data to the associated notification URI.
  • UE may perform data collection (if necessary) as requested and transmit the collected data, e.g., as IP packets to the network according to the destination address over IP connection, e.g., to the MFAF in step 211a, or to the DCCF in step 211b, or to the RAN node (as the data consumer) in step 211c.
  • UE application layer, or data collection client entity inside UE, or a dedicated protocol layer (e.g., a layer above IP layer and below application layer) of UE may be responsible for collecting the data from access stratum (AS) and generate the IP packets.
  • the transmission of the collected data from UE to the network over the IP connection may be sent over a dedicated PDU session, or dedicated slice, or dedicated radio bearer.
  • IP connection between UE and the node or entity with the destination address it may be established before or after receiving the second request message.
  • MFAF MFAF
  • the given address information e.g., indicated in the second request message or by other means (e.g., a UE route selection policy (URSP) rule configured by PCF)
  • URSP UE route selection policy
  • UE may establish a secured IP connection with the MFAF. If the FQDN of the MFAF is sent to the UE, a DNS server or resolver is used to resolve the IP address of the MFAF, e.g.
  • EASDF edge application server discovery function
  • DNS local domain name system
  • UE may use the address of the MFAF, together with the information in the URSP, to determine the PDU session parameters. Then, UE may use the PDU session parameter to establish a PDU session.
  • SMF When SMF receives the request of establishing a PDU session, it may select a proper UPF based on the PDU session parameters, and establishes the connection between the UPF and MFAF.
  • the IP connection between the UE with other node or entity can be established similarly.
  • the MFAF or DCCF will forward the received data to the data consumer, e.g., to Consumer#1 in step 213a or 213b, or to the RAN node (not shown) .
  • the MFAF may forward the UE collected data to the corresponding data consumer as configured, which may be a gNB, CN entity, OTT server, or OAM etc., e.g., by transmitting a Nmfaf_3daDataManagmenet_Notify message.
  • Figure 3 illustrates another example of a UE side data collection procedure under scheme 1 in accordance with aspects of the present disclosure.
  • step 301 when a data consumer would like to collect data from UE, it may send a message (first request message) to the DCCF to request or subscribe UE side data.
  • a message (first request message) to the DCCF to request or subscribe UE side data.
  • Consumer#1 which is a non-RAN data consumer may transmit a first request message to the DCCF in step 301a, or a RAN node may transmit a first request message to the DCCF in step 301b.
  • the DCCF may check or collect information related to the requested data collection.
  • the DCCF may determine or select a UE from which the interested data can be requested.
  • the DCCF may directly or indirectly request or subscribe UE side data from the selected UE, and accordingly, the UE may receive a message (hereinafter, second request message) that requests or subscribes UE side data.
  • second request message a message that requests or subscribes UE side data.
  • the DCCF may generate a NAS message as the second request message and directly transmit the NAS message to the UE in step 305.
  • the DCAF rather than the AMF may be involved to generate and/or transmit the second request message, and/or even select the UE.
  • the DCCF may transmit a message indicating information associated with generating the second request message to the DCAF in step 307a.
  • the DCAF may generate a message, e.g., an application layer message as the second request message based on the information received from the DCCF, and then transmit the application layer message to the selected UE in step 307b.
  • the second request message transmitted from the DCAF to the UE and that transmitted from the AMF to the UE are mainly different in types, and thus will not repeat.
  • the DCCF may not select the UE by itself and need the DCAF to determine the UE.
  • the DCCF may transmit UE selection related information, e.g., including identification information of target UE (s) , criteria information and/or the description information of the interested data etc., to the DCAF step 307a.
  • the DCAF may select the UE that fulfills the criteria information and/or the description information of interested data, e.g., if UE is served by a cell or frequency of interest.
  • the information that the DCAF may use to determine the UE is similar to that used by the DCCF, and will not repeat.
  • the DCAF may generate a message, e.g., an application layer message as the second request message if the DCCF also provides information associated with generating the second request message, and then transmit the application layer message to the selected UE in step 307b.
  • the DCAF may report the selected UE to the DCCF.
  • the DCAF may lack the information related to generation of the second request message, and the DCCF may generate and transmit a NAS message to the UE selected and reported by the DCAF as in step 305.
  • the DCCF may configure the additional CN entity, e.g., the MFAF with respect to messaging rules for data forwarding or notification.
  • the DCCF may generate a Nmfaf_3daDataManagmenet_Configure message to configure the MFAF with respect to the messaging rules, which is similar to that illustrated in view of Figure 2 and will not repeat.
  • UE may perform data collection (if necessary) as requested and transmit the collected data, e.g., as IP packets to the network according to the destination address.
  • the request message is received from the DCCF, it is similar to that illustrated in view of Figure 2, and will not repeat.
  • UE may determine the address of the DCAF based on the received application layer message or the like, and transmit the collected data to the DCAF over IP connection established, e.g., in application layer in step 311. That is, the destination address for data transmitted from UE is the address of the DCAF.
  • the DCAF may transmit or forward the received data to the DCCF or MFAF as indicated by the DCCF.
  • the DCAF may transmit the received UE side data to the MFAF in step 313a (e.g., the DCCF provides the address of the MFAF as the destination address) , or to the DCCF in step 313b (e.g., the DCCF provides the address of the DCCF as the destination address) .
  • the MFAF or DCCF will forward the received data to the data consumer, e.g., to Consumer#1 in step 315a or 315b, or to the RAN node in step 317a or 317b.
  • UE side data collection may be configured by a RAN node, e.g., gNB, rather than the DCCF.
  • a RAN node e.g., gNB
  • the RAN node will then configure the UE.
  • the data collected from UE side it may be forwarded to the RAN node over the IP connection via the UPF, or further via the DCCF or MFAF etc. as illustrated in scheme 1.
  • Figure 4 illustrates an example of a UE side data collection procedure under scheme 2 in accordance with aspects of the present disclosure.
  • the RAN node may check or collect information related to the interested data collection. For example, the RAN node may check whether the RAN node is authenticated to perform UE side data collection for this particular UE, e.g., with the AUSF (not shown) , check whether the related UE consent (s) is available, e.g., with the UDM (not shown) , and/or check whether any related policy (e.g., privacy policy) is available, e.g., with the PCF or BSF (not shown) .
  • the RAN node may check whether the RAN node is authenticated to perform UE side data collection for this particular UE, e.g., with the AUSF (not shown) , check whether the related UE consent (s) is available, e.g., with the UDM (not shown) , and/or check whether any related policy (e.g., privacy policy) is available, e.g., with the PCF or BSF (not shown) .
  • the RAN node may configure the determined UE (or selected UE or target UE) to collect data, e.g., via RRC message. For example, in step 401, the RAN node may transmit a RRC message (the second request message) to the selected UE or target UE where the interested data is expected to be collected.
  • the RRC message towards the UE as the second request message and the NAS message or application layer message as the second request message towards UE are identical or similar except the types, and thus will not repeat.
  • NAS messages or RRS messages can be used for data transmission.
  • the data collected from the UE will be transmitted over the IP connection, it may be transmitted to a destination address in the form of IP packets as illustrated in scheme 1.
  • the destination address is the address of the DCCF.
  • the RAN node may configure the DCCF with respect to messaging rules for data forwarding or notification. For example, in step 403b, the RAN node may generate a Nmfaf_3daDataManagmenet_Configure message to configure the DCCF with respect to the messaging rules, e.g., indicating address information for data notification and/or information that will be further carried together with received UE collected data to associate with the received UE collected data with a data notification address.
  • the RAN node may establish a connection with UPF directly, and the destination address is the address of the RAN node.
  • the IP connection between UE and the RAN node it may be established before or after receiving the second request message.
  • the given address information e.g., indicated in the second request message or by other means (e.g., a URSP rule configured by PCF)
  • UE may establish a secured IP connection with the RAN node. If the FQDN of the RAN node is sent to the UE, a DNS server or resolver is used to resolve the IP address of the RAN node, e.g., EASDF or local DNS for local RAN node address resolution.
  • the processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof) .
  • the processor 502 may be configured to operate the memory 504.
  • the memory 504 may be integrated into the processor 502.
  • the processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.
  • the method may include receiving a first request message associated with data collection from a data consumer node.
  • the operations of step 1001 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1001 may be performed by a CN entity described with reference to Figure 7.
  • the method may include selecting a UE for data collection based on the first request message or transmit UE selection related information to another CN entity based on the first request message to select a UE for data collection.
  • the operations of step 1003 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1003 may be performed by a CN entity as described with reference to Figure 7.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Artificial Intelligence (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent un procédé et un appareil d'aide à la collecte de données. Un procédé donné à titre d'exemple mis en œuvre par un UE pour des communications sans fil peut consister à recevoir un message de demande associé à une collecte de données, et à transmettre des données collectées à une adresse de destination déterminée sur la base du message de demande sur une connexion IP.
PCT/CN2024/112361 2024-08-15 2024-08-15 Procédé et appareil d'aide à la collecte de données Pending WO2025123738A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112361 WO2025123738A1 (fr) 2024-08-15 2024-08-15 Procédé et appareil d'aide à la collecte de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112361 WO2025123738A1 (fr) 2024-08-15 2024-08-15 Procédé et appareil d'aide à la collecte de données

Publications (1)

Publication Number Publication Date
WO2025123738A1 true WO2025123738A1 (fr) 2025-06-19

Family

ID=96056404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/112361 Pending WO2025123738A1 (fr) 2024-08-15 2024-08-15 Procédé et appareil d'aide à la collecte de données

Country Status (1)

Country Link
WO (1) WO2025123738A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023180115A1 (fr) * 2022-03-25 2023-09-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédés d'exposition de données/analyse d'un réseau de communication dans des scénarios d'itinérance
WO2024078603A1 (fr) * 2022-10-14 2024-04-18 维沃移动通信有限公司 Procédé et appareil de collecte de données, dispositif de communication et support de stockage lisible
WO2024110081A1 (fr) * 2023-07-27 2024-05-30 Lenovo (Singapore) Pte. Ltd. Collecte et mise en rapport de données dans un système de communication sans fil
US20240188150A1 (en) * 2021-04-05 2024-06-06 Lg Electronics Inc. Efficient terminal data collection

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240188150A1 (en) * 2021-04-05 2024-06-06 Lg Electronics Inc. Efficient terminal data collection
WO2023180115A1 (fr) * 2022-03-25 2023-09-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédés d'exposition de données/analyse d'un réseau de communication dans des scénarios d'itinérance
WO2024078603A1 (fr) * 2022-10-14 2024-04-18 维沃移动通信有限公司 Procédé et appareil de collecte de données, dispositif de communication et support de stockage lisible
WO2024110081A1 (fr) * 2023-07-27 2024-05-30 Lenovo (Singapore) Pte. Ltd. Collecte et mise en rapport de données dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON, NOKIA, NOKIA SHANGHAI BELL: "KI#11 – Evaluation on data collection", 3GPP DRAFT; S2-2009378, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20201116 - 20201120, 22 November 2020 (2020-11-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051957998 *

Similar Documents

Publication Publication Date Title
US20240188014A1 (en) 5g delay tolerant data services
JP7662133B2 (ja) 第６世代（６ｇ）システムアーキテクチャ及び機能
CN117546449A (zh) 针对第五代(5g)系统的边缘计算网络部署
EP4395267A1 (fr) Procédé et appareil de traitement de trafic faisant appel à la classification de trafic dans un système de communication sans fil
CN116783882A (zh) 用于边缘计算应用的性能测量
WO2024079365A1 (fr) Gestion de notification pour activation d'apprentissage fédéré vertical
WO2024110081A1 (fr) Collecte et mise en rapport de données dans un système de communication sans fil
WO2024119964A1 (fr) Collecte de mesures pour apprentissage de modèle
WO2025209670A1 (fr) Architecture de collecte de données unifiée pour diverses technologies d'accès radio
US20250267080A1 (en) Adaptive monitoring of radio intelligent controller key performance indicators
WO2024207850A1 (fr) Collecte de données pour apprentissage ou surveillance de modèle
WO2025123738A1 (fr) Procédé et appareil d'aide à la collecte de données
WO2024087745A1 (fr) Procédé et appareil de prise en charge de rapport de temps d'arrivée de rafale (bat)
WO2024156388A1 (fr) Support d'enregistrement pour activation d'apprentissage fédéré vertical
US20250358703A1 (en) Method and apparatus for inter-network service continuity
WO2026056277A1 (fr) Mise en cache locale basée sur upf
WO2025185205A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2025200520A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
US20250358586A1 (en) Method and apparatus for inter-edge data network based service continuity
WO2026051407A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2025241608A1 (fr) Procédé et appareil de prise en charge d'interactions orientées service
WO2024146146A1 (fr) Service informatique dans des réseaux
WO2025241555A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2026036750A1 (fr) Procédé et appareil de configuration d'équipement utilisateur (ue)
US20260101175A1 (en) User equipment capability framework in a wireless communications system

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

Country of ref document: EP

Kind code of ref document: A1