Communication method, device and system

Abstract

The communication method provided by the embodiment of the invention is used for opening UE measurement data for a third-party server. Comprises: a first device receives a first request sent by a third device, the first request being used for requesting UE measurement data, the first request comprising information of a target UE, and the first device being a device supporting UE measurement data collection; the first device sends first data to the third device, the first data is determined by the first device according to the first request, and the first device can specifically be a device in a communication network, such as a core network device.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method, apparatus, and system. Background Technology

[0002] In wireless communication systems, third-party servers (OTT servers) need to collect UE measurement data for model training when training UE-side models. Since operators consider this UE measurement data used for model training to be network data, third-party servers cannot directly obtain this data from the UE and must accept operator control. Therefore, how OTT servers can obtain UE measurement data from the network for UE-side model training is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This application provides a communication method for opening UE measurement data to a third-party server, enabling the third-party server to train a UE-side model based on the UE measurement data.

[0004] In view of the above, in a first aspect, this application provides a communication method applied in a communication system or a communication network, comprising: a first device receiving a first request sent by a third device, the first request being used to request UE measurement data, the first request containing information about a target UE, the first device being a device that supports UE measurement data collection, typically; and the first device sending first data to the third device, the first data being determined by the first device according to the first request, the first device specifically being a device in the communication network, such as a core network device.

[0005] In this embodiment of the application, the first device in the communication network can open up the UE measurement data, so that the third device can send the UE measurement data to the third-party server, and the third-party server can train the UE-side model based on the received UE measurement data.

[0006] In one possible implementation, before the first device receives the first request sent by the third device, the aforementioned method may further include: the first device sending capability registration information to the second device, the capability registration information including a first indication, the first indication being used to indicate that the first device supports UE measurement data collection.

[0007] In this embodiment of the application, the first device can register its UE measurement data collection capability with the second device, so that other devices in the network can query the first device that supports UE measurement data collection from the second device.

[0008] In one possible implementation, the aforementioned capability registration information further includes the types of UE measurement data that can be collected, a first UE list, and one or more items in a first region. The first UE list includes information on at least one UE, which is a UE for which the first device can collect UE measurement data. The first region is the distribution range of UEs for which the first device can collect UE data. In this application embodiment, the first device can register detailed information about its supported capabilities, thereby enabling the second device to obtain more detailed capability information of the first device.

[0009] In one possible implementation, the first request carries a second instruction, which is used to instruct the collection of UE measurement data or to instruct the type of UE measurement data. That is, the third device can request the first device to collect UE measurement data or request the collection of a specified type of UE measurement data, so as to obtain the data required for model training.

[0010] In one possible implementation, the target UE information may indicate a list of target UE identifiers, target UE manufacturer information, or target UE chip identifier information, wherein the target UE chip identifier information includes the identifier of the chip in the target UE. In this application embodiment, the third device may directly provide the first device with a UE list, or provide target UE manufacturer information or chip manufacturer information, etc., to filter out the UE measurement data reported by more suitable UEs from the required dimensions.

[0011] In one possible implementation, the aforementioned method further includes: a first device sending a measurement data collection request to a target UE, the measurement data collection request including a third instruction, the target UE referring to at least one UE in a second UE list determined by the first device based on information of the target UE; the first device receiving UE measurement data sent by the target UE, the first data being determined by the first device based on UE measurement data sent by one or more target UEs, or the first data including UE measurement data sent by the one or more target UEs.

[0012] In this embodiment of the application, the first device may send a measurement data request to the target UE to request the UE to report UE measurement data. The first data sent by the first device to the third device is generated based on the UE measurement data, or the first data may include UE measurement data reported by one or more target UEs.

[0013] In one possible implementation, the aforementioned method further includes: a first device storing a list of UEs that support UE measurement data reporting capabilities, and determining a second UE list from the UE list information; or, the first device sending a first query request to a fourth device, the first query request being used to request UE information that supports UE measurement data reporting capabilities, the first query request containing information about the target UE, and receiving the second UE list sent by the fourth device.

[0014] In this application embodiment, multiple lists of UEs that can report UE measurement data are provided. Specifically, the first device may pre-store information on UEs that support UE measurement data reporting, or the information on UEs that support UE measurement data reporting may be queried from the fourth device, thereby improving the flexibility of the solution.

[0015] Secondly, this application provides a communication method applied to a communication system, comprising: a second device receiving a second query request from a third device, the second query request being used to request a query for a device that supports UE measurement data collection; the second device sending a query response to the third device, the query response including information about a first device, the first device being a device that supports UE measurement data collection.

[0016] In this embodiment of the application, when the second device receives a query request from the third device, it can provide the third device with the support of the first device for collecting UE measurement data, so that the third device can obtain UE measurement data from the first device and realize the opening of UE measurement data within the network.

[0017] In one possible implementation, the aforementioned method further includes: a second device receiving capability registration information sent by a first device, the capability registration information including a first indication, the first indication being used to indicate that the first device supports UE measurement data collection. In this embodiment, the first device can register UE measurement data collection capabilities with the second device, thereby enabling the second device to provide other devices with information about the first device supporting UE measurement data collection, thus achieving controlled opening of UE measurement data within the network.

[0018] In one possible implementation, the aforementioned second query request includes information about the target UE, which indicates a list of target UE identifiers, target UE manufacturer information, or target UE chip identifier information. In this application embodiment, when the third device queries a device that supports UE measurement data collection, it can directly provide a list of target UE identifiers, or it can provide the UE manufacturer or the manufacturer information of the chip in the UE, supporting multiple methods for querying devices that can provide the required UE measurement data.

[0019] Thirdly, this application provides a communication method, comprising: a third device receiving a first data subscription request sent by a fifth device, the first data subscription request being used to request UE measurement data; the third device sending a second query request to a second device, the second query request being used to request a device that supports the collection of UE measurement data, that is, querying the second device for a device that supports the collection of UE measurement data;

[0020] The third device receives a query response, which includes information about the first device, which is a device that supports UE measurement data collection, specifically a core network device within the network. The third device then sends a first request to the first device, which requests UE measurement data. The third device receives first data sent by the first device, which is determined by the first device based on the first request, including UE measurement data reported by one or more target UEs. The third device then sends the first data to the fifth device.

[0021] In this embodiment of the application, after the third device receives the first data subscription request sent from the fifth device, it can first query the second device for the first device that supports the collection of UE measurement data, and request UE measurement data from the first device. After the first device collects the UE measurement data, it can feed back the first data to the third device. The third device feeds back the first data to the fifth device to realize the opening of UE measurement data in the network.

[0022] In one possible implementation, the aforementioned first data subscription request includes information about the target UE, which indicates a list of target UE identifiers, target UE manufacturer information, or target UE chip identifier information. In this application embodiment, when the fifth device subscribes to UE measurement data, it can simultaneously provide information about the target UE, i.e., which UEs' reported UE measurement data it expects to receive.

[0023] Fourthly, this application provides a communication method, comprising: a fourth device receiving a first query request sent by a first device, the first query request being a list of UEs that support UE measurement data reporting capabilities, the first query request containing information about a target UE, the UE information indicating UE manufacturer information or UE chip identification information; and the fourth device sending a second UE list to the first device, the second UE list being determined based on the UE information.

[0024] In this embodiment of the application, after receiving the first query request sent by the first device, the fourth device can query the corresponding UE from the stored information and feed back the specific information of the UE that supports UE measurement data reporting to the first device.

[0025] In one possible implementation, the aforementioned method further includes: a fourth device receiving capability information sent by a UE, the UE capability information including a capability indication for indicating whether the UE supports uploading UE measurement data or UE manufacturer information or chip information used by the UE; and the fourth device determining a second UE list based on the UE capability information.

[0026] In this embodiment of the application, the fourth device can also receive the capability information of the UE, including whether the UE supports UE measurement data reporting, or the specific information of the UE, so that the UE in the network can register its capability information in the fourth device, which makes it easier to manage the information of the UE in the network.

[0027] Fifthly, this application provides a communication method, including: a UE sending capability information to a fourth device, the capability including a capability indication for indicating whether the UE supports uploading UE measurement data or UE manufacturer information or chip information used by the UE.

[0028] In this embodiment of the application, the UE can register capability information with the fourth device, thereby enabling the fourth device to store or manage the information of the UE in the network, so as to collect the UE measurement data in the network.

[0029] Sixthly, this application provides a communication device for use in a communication system, comprising:

[0030] The receiving module is used to receive a first request sent by a third device. The first request is used to request UE measurement data. The first request contains information about the target UE. The first device is a device that supports the collection of UE measurement data.

[0031] The sending module is used to send first data to the third device, wherein the first data is determined by the first device according to the first request.

[0032] The communication device can be used to perform the steps performed by the first device in the first aspect or any optional embodiment of the first aspect.

[0033] Seventhly, this application provides a communication device for use in a communication system, comprising:

[0034] The receiving module is configured to receive a second query request from a third device, wherein the second query request is used to request a device that supports the collection of UE measurement data;

[0035] The sending module is used to send a query response to the third device, the query response including information about the first device, which is a device that supports UE measurement data collection.

[0036] The communication device can be used to perform the steps performed by the second device in the second aspect or any optional embodiment of the second aspect described above.

[0037] Eighthly, this application provides a communication device, comprising:

[0038] The receiving module is used to receive a first data subscription request sent by the fifth device, the first data subscription request being used to request UE measurement data;

[0039] The sending module is used to send a second query request to the second device. The second query request is used to request a device that supports the collection of UE measurement data.

[0040] The receiving module is also used to receive a query response, which includes information about the first device, which is a device that supports the collection of UE measurement data.

[0041] The sending module is also used to send a first request to the first device, the first request being used to request UE measurement data;

[0042] The receiving module is also used to receive first data sent by the first device, wherein the first data is determined by the first device according to the first request;

[0043] The sending module is also used to send the first data to the fifth device.

[0044] The communication device can be used to perform the steps performed by the third device in the aforementioned third aspect or any optional embodiment of the third aspect.

[0045] Ninthly, this application provides a communication device, comprising:

[0046] The receiving module is used to receive a first query request sent by the first device. The first query request is a list of UEs that support the UE measurement data reporting capability. The first query request contains information about the target UE, and the UE information indicates the UE's manufacturer information or UE chip identification information.

[0047] The sending module is used to send a second UE list to the first device. The second UE list is determined based on the UE information.

[0048] The communication device can be used to perform the steps performed by the fourth device in the aforementioned fourth aspect or any optional embodiment of the fourth aspect.

[0049] In a tenth aspect, this application provides a user equipment, comprising:

[0050] The transmitting module is used to send capability information to the fourth device. The capability information includes a capability indication for indicating whether the UE supports uploading UE measurement data, or the UE's manufacturer information or the chip information used by the UE.

[0051] The user equipment can be used to perform the steps performed by the UE in the aforementioned fifth aspect or any optional implementation of the fifth aspect.

[0052] In one aspect, this application provides a communication system comprising at least two of a first device, a second device, a third device, a fourth device, or a user device;

[0053] The first device is configured to perform the method steps as claimed in the first aspect or any optional embodiment of the first aspect;

[0054] The second device is used to perform the method steps as described in any optional embodiment of the second aspect or the first aspect of the claim;

[0055] The third device is used to perform the method steps as described in any optional embodiment of the third aspect or the first aspect;

[0056] The fourth device is used to perform the method steps as described in any optional embodiment of the fourth aspect or the first aspect;

[0057] The user equipment is used to perform the method steps as claimed in the first aspect or any optional embodiment of the first aspect.

[0058] In a twelfth aspect, embodiments of this application provide a communication device, including a processor and a memory, wherein the processor and the memory are interconnected via a line, and the processor calls program code in the memory to perform processing-related functions in the method shown in any of the first aspects above. Optionally, the communication device may be a chip.

[0059] In a thirteenth aspect, embodiments of this application provide a communication device, including a processor and a memory, wherein the processor and the memory are interconnected via a line, and the processor calls program code in the memory to perform processing-related functions in the method shown in any of the second aspects above. Optionally, the communication device may be a chip.

[0060] In a fourteenth aspect, embodiments of this application provide a communication device, including a processor and a memory, wherein the processor and the memory are interconnected via a line, and the processor calls program code in the memory to perform processing-related functions in the method shown in any of the third aspects above. Optionally, the communication device may be a chip.

[0061] In a fifteenth aspect, embodiments of this application provide a communication device, including a processor and a memory, wherein the processor and the memory are interconnected via a line, and the processor calls program code in the memory to perform processing-related functions in the method shown in any of the fourth aspects above. Optionally, the communication device may be a chip.

[0062] In a sixteenth aspect, embodiments of this application provide a communication device, including a processor and a memory, wherein the processor and the memory are interconnected via a line, and the processor calls program code in the memory to perform processing-related functions in the method shown in any of the fifth aspects above. Optionally, the communication device may be a chip.

[0063] In a seventeenth aspect, embodiments of this application provide a communication device, which may also be referred to as a digital processing chip or a chip. The chip includes a processing unit and a communication interface. The processing unit obtains program instructions through the communication interface, and the program instructions are executed by the processing unit. The processing unit is used to perform processing-related functions as described in any of the optional embodiments of the first to fifth aspects above.

[0064] Eighteenthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method in any of the optional embodiments of the first to fifth aspects described above.

[0065] In a nineteenth aspect, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the method in any of the optional embodiments of the first to fifth aspects described above. Attached Figure Description

[0066] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0067] Figure 2 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0068] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0069] Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application;

[0070] Figure 5 A flowchart illustrating another communication method provided in an embodiment of this application;

[0071] Figure 6 A flowchart illustrating another communication method provided in an embodiment of this application;

[0072] Figure 7 A flowchart illustrating another communication method provided in an embodiment of this application;

[0073] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0074] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0075] Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0076] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0077] Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0078] Figure 13 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0079] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0080] The method provided in this application can be applied to various communication systems, such as 5th generation (5G) communication systems, new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, or other future communication systems such as 6G. This application exemplifies this method using a 5G communication system as an example.

[0081] Please see Figure 1 , Figure 1 This is a schematic diagram of the structure of the 3rd Generation Partnership Project (3GPP) network based on 5G communication technology. Figure 1The network shown mainly includes: radio access network (RAN) equipment, AMF network elements, user plane function (UPF) network elements, PCF network elements, terminal equipment, etc.

[0082] In a communication system, the portion operated by the operator can be called a PLMN (or operator network, etc.).

[0083] This network architecture can include three parts: terminal equipment, a PLMN (Public Utility Network Management System), and a data network (DN). The PLMN is primarily a public network provided by the mobile network operator (MNO) to users for mobile broadband access services. The PLMN described in this application can specifically be a network conforming to the 3rd Generation Partnership Project (3GPP) standards, or simply a 3GPP network. 3GPP networks typically include, but are not limited to, 5th-generation (5G) networks and 4th-generation (4G) networks.

[0084] The terminal equipment portion may include terminal equipment 110, which can also be referred to as user equipment (UE). The terminal equipment 110 in this application is a device with wireless transceiver capabilities, capable of communicating with one or more core network (CN) devices (or core devices) via access network equipment (or access devices) in the radio access network (RAN) 140. Terminal equipment 110 can also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. Terminal equipment 110 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal device 110 can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smartphone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc. Alternatively, terminal device 110 can also be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, in-vehicle device, wearable device, drone device, or a terminal in the Internet of Things (IoT), vehicle network, 5G network, or any form of terminal in future networks, relay user equipment, or a terminal in a future evolved PLMN, etc. Among these, relay user equipment can be, for example, a 5G residential gateway (RG). For example, terminal device 110 can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. This application does not limit the type or category of terminal device.

[0085] A PLMN may include: Network Exposure Function (NEF) 131, Network Function Repository Function (NRF) 132, Policy Control Function (PCF) 133, Unified Data Management (UDM) 134, Application Function (AF) 135, AUSF 136, AMF 137, Session Management Function (SMF) 138, User Plane Function (UPF) 139, and (Radio) Access Network ((R)AN) 140, NSSAAF 141, etc. The portion of the PLMN other than the (Radio) Access Network 140 can be referred to as the core network (CN) portion or core network portion.

[0086] Data network (DN) 120, also known as packet data network (PDN), is typically a network located outside the PLMN, such as a third-party network. For example, the PLMN can connect to multiple data networks DN 120. Various services can be deployed on the data networks DN 120 to provide data and / or voice services to the terminal devices 110. For instance, data network DN 120 could be a private network of a smart factory. Sensors installed in the workshop of the smart factory can be terminal devices 110. A control server for the sensors is deployed in the data network DN 120, providing services to the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. As another example, data network DN 120 could be an internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices 110, and the employees' mobile phones or computers can access information and data resources on the company's internal office network. Terminal devices 110 can access information and data resources through interfaces provided by the PLMN (e.g., ...). Figure 1Terminal device 110 establishes a connection with the PLMN (such as the N1 interface) and uses the data and / or voice services provided by the PLMN. Terminal device 110 can also access the data network DN 120 through the PLMN and use the operator services deployed on the data network DN 120, and / or services provided by third parties. These third parties can be service providers other than the PLMN and terminal device 110, and can provide other data and / or voice services to terminal device 110. The specific form of these third parties can be determined according to the actual application scenario and is not limited here.

[0087] For example, the network functionality in a PLMN is briefly described below.

[0088] (R)AN 140 is a subnetwork of the PLMN, serving as the implementation system between service nodes (or network functions) and terminal equipment 110 within the PLMN. For terminal equipment 110 to access the PLMN, it first goes through (R)AN 140, and then connects to the service nodes within the PLMN via (R)AN 140. The access network device in this embodiment is a device that provides wireless communication functionality to terminal equipment 110; it can also be referred to as an access device, (R)AN device, or network device, etc. Such access equipment includes, but is not limited to: next-generation node base stations (gNBs) in 5G systems, evolved node Bs (eNBs) in LTE systems, radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home evolved node Bs (or home node Bs (HNBs)), base band units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), small cell equipment (picos), mobile switching centers, or network equipment in future networks. It is understood that this application does not limit the specific type of access network equipment. In systems employing different wireless access technologies, the names of devices with access network equipment functions may differ.

[0089] Optionally, in some deployments of the access device, the access device may include a centralized unit (CU) and a distributed unit (DU), etc. In other deployments of the access device, the CU may be divided into a CU-control plane (CP) and a CU-user plane (UP), etc. In still other deployments of the access device, the access device may also be an open radio access network (ORAN) architecture, etc. This application does not limit the specific deployment method of the access device.

[0090] The Network Open Function (NEF) 131 (also known as NEF Network Function or NEF Network Function Entity) is a control plane function provided by the operator. NEF Network Function 131 securely exposes the PLMN's external interface to third parties. When SMF Network Function 138 needs to communicate with a third-party network function, NEF Network Function 131 can act as a relay for communication between SMF Network Function 138 and the third-party network entity. As a relay, NEF Network Function 131 can translate the identification information of subscribed users and the identification information of third-party network functions. For example, when NEF Network Function 131 sends a subscribed user's Subscriber Permanent Identifier (SUPI) from the PLMN to a third party, it can translate the SUPI into its corresponding External Identity (ID). Conversely, when NEF Network Function 131 sends an External ID (the third-party network entity ID) to the PLMN, it can translate it into a SUPI.

[0091] The Network Storage Function (NRF) 132 can be used to maintain real-time information for all network function services in the network.

[0092] The Policy Control Function (PCF) 133 is a control plane function provided by the operator to provide policies for Protocol Data Unit (PDU) sessions to the Session Management Function (SMF) 138. These policies can include billing-related policies, QoS-related policies, and authorization-related policies.

[0093] Unified Data Management (UDM) 134 is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), security context, and subscription data of subscribed users in the PLMN. Specifically, the subscribed user of the PLMN can be a user using services provided by the PLMN, such as a user using a China Telecom terminal device SIM card or a China Mobile terminal device SIM card. For example, the SUPI of a subscribed user can be the SIM card number. The security context can be data (cookies) or tokens stored on the local terminal device (e.g., a mobile phone). The subscription data of the subscribed user can be the associated services of the SIM card, such as the data plan of the SIM card.

[0094] The application function AF 135 is used for application data routing, accessing network open functions, and interacting with the policy framework for policy control.

[0095] The authentication server function AUSF 136 is a control plane function provided by the operator, typically used for Level 1 authentication, namely authentication between the terminal device 110 (the subscriber) and the PLMN.

[0096] The Network Slice Authentication and Authorization Function NSSAAF141 is a control plane function provided by the operator and is typically used for slice authentication in network slicing. Specifically, it involves slice authentication performed between the terminal device 110 and an authentication server (such as the authentication server of the operator's network or the authentication server of a third-party DN).

[0097] Access and Mobility Management Function (AMF) 137 is a control plane network function provided by the PLMN, responsible for access control and mobility management of terminal device 110 when it accesses the PLMN. This includes functions such as mobility state management, assigning temporary user identities, authenticating and authorizing users.

[0098] The Session Management Function (SMF) 138 is a control plane network function provided by the PLMN, responsible for managing the Protocol Data Unit (PDU) sessions of terminal device 110. A PDU session is a channel used to transmit PDUs; terminal devices need to exchange PDUs with DN 120 through PDU sessions. The SMF 138 is responsible for establishing, maintaining, and deleting PDU sessions. The SMF 138 includes session management (such as session establishment, modification, and release, including tunnel maintenance between UPF 139 and (R)AN 140), UPF 139 selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0099] The User Plane Function (UPF) 139 is a gateway provided by the operator, serving as the gateway for communication between the PLMN and DN 120. UPF139 includes user plane-related functions such as packet routing and transmission, packet inspection, service usage reporting, Quality of Service (QoS) processing, lawful interception, uplink packet inspection, and downlink packet storage.

[0100] Figure 1 The network functions in the PLMN shown can also include a network slice selection function (NSSF). Figure 1 (Not shown in the image), is responsible for determining network slice instances, selecting AMF network function 137, etc. Figure 1 The network functions in the PLMN shown may also include unified data repository (UDR), etc. This application embodiment does not limit other network functions included in the PLMN.

[0101] Figure 1 Nnef, Nausf, Nnssaaf, Nnrf, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. For example, the meaning of the above interface sequence numbers can be found in the definitions in the 3GPP standard protocols; this application does not limit the meaning of the above interface sequence numbers. It should be noted that... Figure 1 The example provided only uses terminal device 110 as the UE. Figure 1 The interface names between the various network functions in this application are merely examples. In actual implementations, the interface names of this system architecture may be other names, and this application does not limit them.

[0102] Furthermore, the network elements in the aforementioned network architecture are exemplarily classified in this application embodiment.

[0103] like Figure 2 As shown, for ease of understanding, the embodiments of this application have been simply classified into their structures, such as... Figure 2 As shown, the network elements may include terminal 110, network function (NF) 230, data collection coordination function (DCCF) 250, Messaging Framework Adapter Function (MFAF) 240, network data analytics function (NWDAF) 220, and other network elements 260 connected to the DCCF, such as network repository function (NRF), network exposure function (NEF), unified data management (UDM), or binding support function (BSF). NF network elements may specifically include access and mobility management function (AMF), session management function (SMF), or user plane function (UPF). Ndccf, Nmfaf, and Nndaf are interface sequence numbers for connections between network elements; details can be found in relevant standards and will not be elaborated here.

[0104] in:

[0105] NWDAF: A network element that provides data analysis functions for the 5G core network (5GC) NF and OAM. The 5GC NF or OAM can request network data analysis results from the NWDAF. After receiving the request, the NWDAF collects data from the relevant network elements and trains an AI model. Finally, it uses the AI ​​model to perform data inference and feeds back the inference results to the corresponding 5GC NF or OAM. Depending on its function, NWDAF can be divided into NWDAF supporting training (i.e., NWDAF (MTLF: Model training Logical Function)) and NWDAF supporting inference (i.e., NWDAF (AnLF: Analytics Logical Function)). The NWDAF (AnLF) can request AI model information from the NWDAF (MTLF) for data inference.

[0106] DCCF: Data Collection Coordination Function, used to coordinate the collection and distribution of data requested by NF consumers, and also has the function of preprocessing the collected data according to the parameters specified by the consumer.

[0107] MFAF: Enables adaptation with the message framework. It facilitates interaction between DCCF and the message framework, sending the data to be processed to the message framework, receiving the processed data from the message framework, and performing related data formatting and other processing.

[0108] NF: This includes network elements that generate data or need to obtain analysis data from NWDAF, such as AMF, SMF, UPF, etc.

[0109] Of course, the network architecture used in the method provided in this application embodiment may include those compared to the foregoing. Figure 1 or Figure 2 More or fewer network elements,

[0110] In light of the aforementioned network architecture, and with the optimization and enrichment of network functions, introducing AI models into the network is a development trend. For training UE-side models within the network, such as the UE-side model in a dual-end model, a positioning model for UE localization, or a beamforming model, the training entity is typically a third-party server (OTT server). However, training UE-side models usually requires UE measurement data, which is typically network-internal data. For network data security reasons, third-party servers are generally not allowed to directly obtain measurement data from the UE.

[0111] Therefore, this application provides a communication method that can provide UE measurement data to a third-party server, enabling the third-party server to obtain the UE measurement data required for model training.

[0112] The first device, second device, third device, fourth device, and fifth device mentioned below can be network elements in the aforementioned network architecture.

[0113] See Figure 3 The following is a flowchart illustrating a communication method provided in an embodiment of this application.

[0114] 300. The first device sends capability registration information to the second device.

[0115] The first device can be a network element in the aforementioned network architecture, specifically a core network element, such as an NWDAF with UE measurement data collection capabilities, or other network elements with UE measurement data collection capabilities.

[0116] The capability registration information may include a first indication, which can be used to indicate that the first device can perform UE measurement data collection, that is, it has the capability to collect UE measurement data. Typically, within the aforementioned network architecture, a device with UE measurement data collection capability can register with a second device, allowing the second device to store the first device with UE measurement data collection capability.

[0117] Optionally, the capability registration information may include, but is not limited to, the types of UE measurement data that can be collected, a first UE list information, one or more items in a first region, wherein the first UE list includes information on at least one UE, the at least one UE is a UE for which the first device can collect UE measurement data, and the first region is the distribution range of UEs for which the first device can collect UE data.

[0118] The second device can store information about one or more first devices with UE measurement data collection capabilities, thereby enabling unified storage or management of devices with UE measurement data collection capabilities within the network at the second device.

[0119] Optionally, in the network architecture, one or more first devices with UE measurement data collection capabilities can be deployed as needed, such as deploying one or more NWDAFs with UE measurement data collection capabilities, or setting one or more existing NWDAFs to have UE measurement data collection capabilities, thereby enabling the UE measurement data on the NWDAF side to be open to third-party servers.

[0120] Furthermore, the capability registration information may also include the type of UE measurement data that can be collected, a first UE list information, one or more items in a first region, information that the first UE list includes at least one UE, at least one UE is a UE for which the first device can collect UE measurement data, and the first region is the distribution range of UEs for which the first device can collect UE data.

[0121] Step 300 is an optional step. Specifically, step 300 can be executed when deploying the first device, when deploying the network architecture, or at other times. The specific timing can be determined based on the actual application scenario.

[0122] 301. The fifth device sends a first data subscription request to the third device.

[0123] The fifth device can be a third-party server or a network element connected to a third-party server, such as the aforementioned AF entity. The third device can be a control plane entity connected to the fifth device, which can be used to open UE measurement data to the third-party server; for example, the third device can be the aforementioned NEF entity.

[0124] Before training the UE measurement model, UE measurement data needs to be collected. This can be achieved by the fifth device sending a first data subscription request to the third device to request UE measurement data from the third device.

[0125] Optionally, the first data subscription request may include a fourth indication, which may be used to indicate UE measurement data collection or to indicate the type of UE measurement data.

[0126] Specifically, if the fourth instruction is used to instruct the collection of UE measurement data, that is, to indicate that the fifth device expects to obtain UE measurement data, the type of UE measurement data to be obtained can be the default type, or the type of UE measurement data that the fifth device continues to negotiate with the third device.

[0127] If the fourth indication is used to indicate the type of UE measurement data, it can represent the type of UE measurement data that the fifth device expects to acquire.

[0128] Optionally, the first data subscription request may also include target UE range information, that is, an indication of the range of target UEs for which the fifth device expects to acquire UE measurement data. The target UE range information may include one or more of the following: a third UE list, UE manufacturer information, or manufacturer information (or identifier) ​​of the chip in the UE.

[0129] For example, in one possible scenario, the range information of the target UE may include a list of UEs, referred to here as the third UE list, which may include the IDs of one or more target UEs, and can be used to determine the range of UEs for which UE measurement data needs to be obtained.

[0130] In one possible scenario, the range information of the target UE may include the UE's manufacturer information, indicating that the fifth device expects to acquire UE measurement data of UEs manufactured by that manufacturer.

[0131] In one possible scenario, the range information of the target UE may include the manufacturing information of the chip in the UE, indicating that the fifth device expects to acquire UE measurement data of a UE containing a chip manufactured by that manufacturer.

[0132] Therefore, in this application embodiment, the desired UE range can be identified by carrying the UE manufacturer information or the chip manufacturer information in the UE in the request, so that the third-party server can filter the UE range that reports UE measurement data according to actual needs, thereby obtaining a UE-side model that is more suitable for actual needs.

[0133] 302. The third device sends a second query request to the second device.

[0134] After receiving the first data subscription request, the third device needs to know the network elements that support UE measurement data collection. Since the second device stores information about the network elements that support UE measurement data collection, the third device can send a second query request to the second device to request the second device to query the devices that support UE measurement data collection.

[0135] The second query request may include, but is not limited to, the fifth indication or the range information of the target UE. The fifth indication may be used to indicate the device requesting support for UE measurement data collection or the type of requesting support for UE measurement data collection. The target UE information may indicate the range of the target UE for which the UE measurement data is expected to be obtained. Specifically, it may include information about a certain area, a list of target UE identifiers, the manufacturer information of the target UE, or the chip identifier information of the target UE.

[0136] 303. The second device sends a network element query response to the third device.

[0137] The second device stores capability information of one or more devices. After receiving the second query request, the second device can query the devices that support UE measurement data collection from the stored data and send a network element query response to the third device. The network element query response may include information about the devices that support UE measurement data collection, that is, information about the first device, such as the identifier or address of the first device.

[0138] 304. The third device sends the first request to the first device.

[0139] The third device can obtain information about the first device, such as its identifier or address, based on the network element query response sent by the second device. Then, it can send a first request to the first device based on this information. This first request may carry a second indication, which can be used to indicate UE measurement data or the type of UE measurement data.

[0140] Optionally, the first data subscription request may further include target UE range information, that is, an indication of the range of target UEs for which the fifth device expects to obtain UE measurement data. This target UE range information may include one or more of the following: a fourth UE list, UE manufacturer information, or chip manufacturer information within the UE. The fourth UE list includes information about the target UEs for which UE measurement data is expected to be obtained; this fourth UE list may be the same as, or different from, the aforementioned third UE list.

[0141] The scope information can be determined based on the information carried in the aforementioned first data subscription request. For example, if the first data subscription request carries a third UE list, that third UE list can be used as the fourth UE list, or the target UE information can be extracted from the third UE list to generate the fourth UE list, etc. If the first data subscription request carries the target UE's manufacturer information, that target UE's manufacturer information can also be carried in the scope information; or if the first data subscription request carries the chip manufacturer information of the target UE, that chip manufacturer information of the target UE can also be carried in the scope information, etc.

[0142] After receiving the first request, the first device needs to determine the specific range of the target UE that is reporting the UE measurement data.

[0143] In one possible scenario, the first request may carry a list of UEs, which may include information about the target UE. The first device can directly use this list of UEs as a second list of UEs containing the target UE, and then directly execute step 308, that is, send a measurement data collection request to the UE through the fourth device.

[0144] In another possible scenario, if the first request does not carry a UE list, or the UE information in the carried UE list is insufficient, the first device can obtain a second UE list with richer UE information by interacting with other devices or querying stored data.

[0145] Optionally, the first device can determine the specific range of the target UE based on locally stored data, i.e., step 307 below, or it can query the fourth device for the specific range of the target UE, i.e., steps 305 to 306 below. In actual scenarios, one of the methods can be selected, and they will be described below.

[0146] 305. The first device sends a first query request to the fourth device.

[0147] In one possible scenario, after the first device receives the first request, it can send a first query request to the fourth device based on the content requested in the first request. The first query request is used to request the fourth device to query the specific range of the target UE.

[0148] It is understandable that, typically, the first request received by the first device includes, but is not limited to, a second instruction, a fourth UE list, manufacturer information of the target UE, or manufacturer information of the chip in the target UE. These can be used to indicate the range of target UEs requesting UE measurement data from the first device. Based on the information carried in the first request, a first query request needs to be further generated to query the specific information of the target UEs. The fourth device typically stores information about the UEs within the communication network; therefore, the first device can request the fourth device to query the specific information of the target UEs to determine the specific range of target UEs for which UE measurement data needs to be reported.

[0149] The first query request may specifically carry information such as a sixth instruction, a fourth UE list, the manufacturer information of the target UE, or the manufacturer information of the chip in the target UE. This allows the fourth device to query the specific information of the target UE from the stored data based on the information carried in the first query request.

[0150] 306. The fourth device sends the second UE list to the first device.

[0151] After receiving the first query request, the fourth device can determine the second UE list based on the first query request and then send the second UE list back to the first device. The second UE list may include information about one or more target UEs.

[0152] Specifically, the first query request may carry a fourth UE list, which may include the identifiers or other identity information of one or more UEs. The fourth device can obtain the specific information of the UEs in the fourth UE list from the stored information, such as the UE address or the data type supported for measurement, and generate a second UE list.

[0153] If the target UE's manufacturer information is included in the first query request, the fourth device can query the target UE's specific information based on the target UE's manufacturer information. For example, the fourth device can store the UE's permanent equipment identification (PEI). The UE's PEI may include the UE's vendor (manufacturer) or an identifier indicating the UE's vendor, etc. The fourth device can query UEs whose PEI matches the vendor of the target UE carried in the first query request and generate a second UE list.

[0154] Accordingly, if the first query request carries the manufacturer information of the chip in the target UE, the fourth device can use PEI to match the UEs of the vendor of the chip in the target UE carried in the first query request and generate a second UE list.

[0155] If the first query request only carries the sixth instruction, the fourth device can generate a second UE list based on the information of all UEs that support UE measurement data reporting, or generate a second UE list based on the information of UEs that support reporting UE measurement data of the default type, etc.

[0156] 307. The first device determines the second UE list from the stored data.

[0157] In another possible scenario, after receiving the first request, the first device can read the target UEs that fall within the range represented by the first request from the stored data and generate a second UE list.

[0158] Optionally, before step 307, the fourth device may send the UE's capability information for registering with the fourth device to the first device, including the UE's specific information and the types of measurement data supported by the UE.

[0159] 308. The first device sends a measurement data collection request to the UE.

[0160] The UE is the target UE, which is a UE in the second UE list. This measurement data collection request is used to request the UE to report UE measurement data, and may carry a third indication to instruct or request the target UE to report UE measurement data.

[0161] Optionally, step 308 can be performed in various situations. For example, in one possible situation, after the first device determines the second UE list, it can establish a connection with the UEs in the second UE list and then send a measurement data collection request, or the measurement data collection request can be sent to the UEs in the second UE list through the fourth device. In another possible situation, the first device may not need to determine the second UE list. The first device can directly send the measurement data collection request to the UE through the fourth device. That is, the first device can send the measurement data collection request to the fourth device, and the fourth device can determine the target UE that reports the measurement data and send the measurement data collection request to the target UE.

[0162] 309. The UE sends UE measurement data to the first device.

[0163] The UE can report UE measurement data to the first device, or send UE measurement data to the first device through the fourth device.

[0164] Specifically, the UE measurement data may include data obtained by the UE through measurement, such as power delay profile (PDP), channel energy response (CER), channel impulse response (CIR), and sounding reference signal (SRS).

[0165] 310. The first device sends the first data to the fifth device.

[0166] The first data may include UE measurement data sent by one or more target UEs. This enables the fifth device to train a UE-side model based on the first data, or to send the first data to the device performing UE-side model training, thereby realizing the openness of UE measurement data.

[0167] The first data can be determined based on UE measurement data reported by the UE, or it can be read from stored data.

[0168] In one possible scenario, if the first data is data pre-saved by the first device, the aforementioned execution steps can be divided into several cases. For example, in one possible scenario, steps 305 to 309 do not need to be executed. The first request carries a UE list, and the first device uses this UE list as the second UE list. The first device can obtain the UE measurement data reported by the UEs in the second UE list from the stored data and feed it back to the fifth device. In another possible scenario, if the first request does not carry a UE list, or the UE information in the UE list carried in the first request is insufficient, the first device can execute the aforementioned steps 305-306 or 307 to determine the second UE list, read the UE measurement data reported by the UEs in the second UE list from the stored data, and feed it back to the fifth device. The specific execution process can be determined according to the actual application scenario, and this application does not limit it.

[0169] In this application embodiment, a device with UE measurement data collection capability, namely the first device, can be deployed in the network to realize the opening of UE measurement data within the network architecture, that is, to realize the opening of UE measurement data with controllable path, so that third-party servers can train a more suitable UE-side model based on the UE measurement data.

[0170] The foregoing has described the method flow provided in the embodiments of this application. The steps executed by each device in the foregoing method flow can be executed by each device in the foregoing network architecture, or the functions of each device can be deployed in each device in the network architecture. For example, the steps executed by the first device can be executed by NWDAF, the steps executed by the second device can be executed by NRF, the steps executed by the third device can be executed by NEF, the steps executed by the fourth device can be executed by AMF, and the steps executed by the fifth device can be executed by AF, etc. Of course, this application does not limit the specific network element types in which the first, second, third, fourth, and fifth devices are deployed in the network architecture, and can be determined according to the actual application scenario. The following embodiments are only illustrative and are not intended to limit the scope.

[0171] The steps performed by each device in the aforementioned network architecture will be described below.

[0172] The steps performed by each device can be optional or can be combined in different ways. Some possible implementation methods are described below.

[0173] Implementation Method 1

[0174] See Figure 4 The following is a flowchart illustrating another communication method provided in this application embodiment.

[0175] 401. AMF stores UE capability information.

[0176] In a network architecture, when a UE accesses the network or is deployed within the network architecture, the UE can send capability information to the AMF (Agency Management Frame). This information includes the UE's specific details and measurement capabilities. This capability information may include the types of measurement data the UE supports, such as PDP, CER, CIR, or SRS, or other information related to the UE's measurement activities.

[0177] Furthermore, the UE can request to register its measurement capabilities by sending a registration request to the AMF, which can include the UE's capability information. After successful registration, the AMF can also send a registration response to the UE to indicate that the UE has successfully registered with the AMF.

[0178] 402. DE-NWDAF sends capability registration information to NRF.

[0179] DE-NWDAF refers to an NWDAF with UE measurement data collection capability. The NWDAF can send capability registration information to the NRF to register its capability with the NRF, thereby registering the NWDAF's UE measurement data collection capability in the NRF when the NWDAF is deployed with UE measurement data collection capability.

[0180] The specific registration information for this capability may include, but is not limited to, one or more of the following: a first indication that supports UE measurement data collection, a data type, a first UE list, or a first region.

[0181] in,

[0182] The first indication is used to indicate that the NWDAF has the capability to collect UE measurement data. When the network uses user plane to collect UE measurement data, this capability can specifically refer to supporting user plane collection of UE measurement data. When collecting UE measurement data based on the user plane in the network requires exposing the NWDAF's user plane information (such as IP address or fully qualified domain name (FQDN)) to the UE, this indication shows that the NWDAF's user plane information (such as IP address or FQDN) can be exposed to the UE. When the NWDAF collects UE measurement data using a specific service (such as NWDAF_UEDataCollection), the capability registration information can also include the specific service NWDAF_UEDataCollection, that is, using this service to indicate that the NWDAF supports UE measurement data collection.

[0183] Data type indicates the type of UE measurement data that the NWDAF supports collecting. It specifies the types of measurement data that the NWDAF supports collecting from the UE, such as PDP, CER, CIR, or SRS data that the UE can specifically support.

[0184] The first UE list, also known as the UE ID list, refers to the range of UEs that NWDAF can support in collecting UE measurement data, or it can be understood as which UEs NWDAF supports collecting UE measurement data from.

[0185] The first area, also known as the area of ​​interest (AOI), indicates which areas NWDAF supports collecting UE measurement data from. The granularity of this AOI can be a specific map area or the cell coverage area within the access network.

[0186] In this embodiment of the application, the NWDAF can register its capabilities with the NRF, thereby enabling the NRF to store information on NWDAFs with UE measurement data collection capabilities within the network architecture, allowing other devices within the network to query NWDAFs that support UE measurement data collection from the NRF.

[0187] It should be noted that the implementation of this application does not limit the execution order of steps 401 and 402. Step 401 can be executed first, or step 402 can be executed first. The specific execution order can be determined according to the actual application scenario, and this application does not limit it.

[0188] 403. AF sends a data subscription request to NEF.

[0189] This data subscription request is also known as the first data subscription request mentioned above, which may include, but is not limited to, information about the target UE or a fourth indication.

[0190] Among them, the target UE information indicates the target UE's identifier list, the target UE's manufacturer information, or the chip identifier information in the target UE; the fourth indication can be used to indicate the collection of UE measurement data or to indicate the type of UE measurement data, etc.

[0191] Specifically, when the AF provides UE measurement data, it indicates that the AF wants to collect the measurement data that the UE can report from the NWDAF. The specific type of measurement data is not specified. All types of data or the default data type can be collected, or the AF can negotiate the type of measurement data to be collected with the UE according to the implementation.

[0192] In the first data subscription request, when the AF provides a UE measurement data type, it can indicate which type of UE measurement data the AF expects to collect from the NWDAF.

[0193] The target UE information may include UE list or AOI area information, which can be used to represent the range of UEs for which the AF provides UE measurement data.

[0194] Once the AF can confirm the UE ID list for obtaining UE measurement data, the AF can provide a specific list of UE IDs.

[0195] When the AF is unsure of the specific list of UEs, it can provide an AOI area, indicating that the AF expects to obtain UE measurement data of the UEs within that area.

[0196] Additionally, AF can also provide manufacturer (vendor) information.

[0197] Among them, the Vendor information is divided into UE vendor or chip vendor, etc.

[0198] The UE vendor indicates that the AF expects to obtain UE measurement data for UEs with a specific vendor in the region. The vendor can refer to the identifier of one or more UE equipment vendors.

[0199] Chip vendor: This vendor identifier refers to the identifier of the chip manufacturer in the UE that is expected to be acquired. For example, if the AF is a third-party application deployed by a certain manufacturer, and the AF wants to acquire measurement data from all UEs using chips from that manufacturer, then the vendor information provided by the AF is the chip vendor information.

[0200] Therefore, in this embodiment, AF can filter training data from the perspective of UE manufacturer or chip manufacturer in UE to obtain training data that is more compatible with third-party servers, thereby improving the training effect of the model. For example, for chip manufacturers, data can be collected at the chip granularity. Measurement data may be chip-related, and models can be trained for different chips to improve the model and network adaptability of UEs with different chips.

[0201] 404. NEF sends a network element query request to NRF.

[0202] The network element query request, also known as the aforementioned second query request, may include, but is not limited to, the fifth indication or the range information of the target UE. The fifth indication may be used to indicate the device requesting support for UE measurement data collection or the type of requesting support for UE measurement data collection. The target UE information may indicate the range of the target UE for which the UE measurement data is expected to be obtained. Specifically, it may include information about a certain area, a list of identifiers for the UE, the manufacturer information of the target UE, or the chip identifier information of the target UE.

[0203] Specifically, the network element query request may include, but is not limited to, the following: an indication that UE measurement data collection is supported, the type of UE measurement data that can be collected, and one or more of the UE ID list or AOI. The type of UE measurement data that can be collected, the UE ID list, or the AOI can be found in the description of step 403 above, and will not be repeated here.

[0204] 405. NRF sends a network element query response to NEF.

[0205] After receiving a network element query request from the NEF, the NRF queries its stored data for NWDAFs that support UE measurement data collection or NWDAFs that support the UE measurement data collection type or scope indicated in the query request. Based on the queried NWDAF, the NRF generates a network element query response and sends it to the NEF. For ease of distinction, this embodiment refers to NWDAFs that support UE measurement data collection as DE-NWDAFs. The network element query response may specifically include information such as the identifier or address of the DE-NWDAF.

[0206] 406. NEF sends a data subscription request to DE-NWDAF.

[0207] After receiving the network element query response from the NRF, the NEF can obtain information such as the identifier or address of the DE-NWDAF that supports UE measurement data collection. Then, it can send a data subscription request to the DE-NWDAF, which is the aforementioned first request, to request UE measurement data from the DE-NWDAF.

[0208] The data subscription request may include, but is not limited to, one or more of the following: a second instruction, a UE ID list, or an AOI. The fifth instruction may specifically be used to indicate the device requesting support for UE measurement data collection or the type of UE measurement data collection requested. The UE ID list or AOI can be found in the description of step 403 above, and will not be repeated here.

[0209] 407. DE-NWDAF sends a UE list query request to AMF.

[0210] After receiving a data subscription request from NEF, DE-NWDAF can send a UE list query request to AMF, namely the aforementioned first query request, to query AMF for specific information about UEs that meet NEF's UE measurement data collection requirements.

[0211] The UE list query may include, but is not limited to, one or more of the following: the sixth indication, the UE ID list, or the AOI. The sixth indication may specifically be used to indicate the device requesting support for UE measurement data collection or the type of request for support for UE measurement data collection, etc. The UE ID list or AOI can be found in the description of step 403 above, and will not be repeated here.

[0212] 408. AMF sends a UE list query response to DE-NWDAF.

[0213] Based on the received UE list query request, AMF queries the stored data for compatible UEs and generates a UE list to feed back to DE-NWDAF.

[0214] Specifically, if the UE list query request only includes the sixth instruction, the AMF can query information on UEs that support all types of UE measurement data and generate a UE list to be fed back to DE-NWDAF, or query information on UEs that support the default type of UE measurement data and generate a UE list to be fed back to DE-NWDAF, or when the sixth instruction indicates a request for support for the type of UE measurement data collection, the AMF can query UEs that support the type requested by the sixth instruction and generate a UE list to be fed back to DE-NWDAF.

[0215] If the UE list query request includes a UE ID list, the AMF can directly return the UE ID list as the UE list to the DE-NWDAF; alternatively, the AMF can verify the capabilities of the UEs in the UE ID list, filter out UEs that support UE measurement data reporting or support reporting of a specified type of UE measurement data, and return the filtered UE list to the DE-NWDAF, etc.

[0216] If the UE list query request includes an AOI, the AMF retrieves information about UEs within the coverage area of ​​that AOI from the stored data and generates a UE list to be fed back to the DE-NWDAF. For example, if the AOI includes a UE vendor, the AMF can retrieve UEs identified as belonging to that UE vendor from the stored data and generate a UE list to be fed back to the DE-NWDAF; if the AOI includes a chip vendor, the AMF can retrieve UEs identified as belonging to that chip vendor from the stored data and generate a UE list to be fed back to the DE-NWDAF.

[0217] Specifically, regarding the AOI carried in the UE list query request, the AMF can interact with the UDM to obtain the UE's PEI information, or the AMF can interact with the UE to obtain the UE's PEI information. PEI information typically represents various specific aspects of the UE. For example, the AMF can determine the terminal's vendor based on the first 8 digits of the PEI information corresponding to the type allocation code (TAC), ultimately determining a list of UEs that meet the requirements. For instance, the PEI can be represented as IMEI (International Mobile Equipment Identity) or IMEISV (International Mobile Equipment Identity and Software Version), where IMEI consists of 15-17 digits. The first part is the TAC: Type Allocation Code. The first part consists of 8 digits, distinguishing the terminal brand and model; the second part is the final assembly code (FAC): the final assembly code consists of 2 digits; the third part is the serial number (SNR): a 6-digit number starting from the 9th digit, distinguishing the production serial number of each terminal; the fourth part is the CD (check digit) verification code, which is calculated from the first 14 digits using the Luhn algorithm; the fifth part is the SVN software version number, distinguishing different software versions used when terminals of the same model leave the factory.

[0218] If the vendor in the UE list query request received by the AMF is a chip vendor, and if each UE model corresponds to a TAC in the UE's PEI information, then the model corresponding to the UE can be determined based on the TAC information. The AMF stores the chip information corresponding to each model, and the AMF can determine the chip vendor of the UE based on the model represented by the TAC and the stored chip information corresponding to the UE model, and finally determine the UE list that meets the requirements.

[0219] If the chip vendor of the corresponding UE cannot be determined based on the TAC, other methods can be used to determine the chip vendor of each UE. One possible method is that the UE reports its chip vendor through configuration updates; another is that the UE carries its chip vendor in the capability information of the registration message; or the AMF can interact with the UE to obtain the UE's chip vendor and store the chip vendor corresponding to that UE. Subsequently, when needed, the AMF determines the final list of UEs that meet the requirements based on the stored UE chip vendors.

[0220] Furthermore, the AMF stores UE measurement data reporting capability information. Different UEs may use different reporting methods depending on how they report their measurement data. For example, they may be categorized as supporting reporting via the control plane or supporting reporting via the user plane. User plane measurement data reporting refers to the UE reporting its measurement data to the network using the user plane method. Control plane measurement data reporting means the UE must report its measurement data to the network via the control plane method. The AMF sends the determined UE list information to the DE-NWDAF. The UE list information includes a list of UE IDs capable of reporting UE measurement data, and may further include a list of UE IDs capable of reporting UE measurement data using the user plane or a list of UE IDs capable of reporting UE measurement data using the control plane. In other words, when the AMF reports the UE list, it can distinguish UEs using different reporting methods so that the DE-NWDAF can identify the measurement data reporting method of each UE.

[0221] Based on the stored UE measurement data capability information, the AMF first determines a list of UE IDs capable of reporting UE measurement data. It can also further determine a list of UE IDs capable of reporting UE measurement data using the user plane. If all UEs in the UE list support user plane reporting of UE measurement data, the AMF can include an indication, referred to as the seventh indication, when sending the UE ID list information. This indication signifies that all UEs in the UE ID list support user plane reporting of UE measurement data. If the seventh indication is not included, and there is only one UE ID list, it means that all UEs in the list can only report UE measurement data using the control plane.

[0222] Accordingly, when DE-NWDAF receives the UE list, it can use different UE measurement data collection methods for UEs in the UE list that support different reporting methods. For example, the steps for reporting UE measurement data through the user plane can be as follows: steps 409 to 413. The steps for reporting UE measurement data through the control plane can be as follows: steps 414 to 416. These will be described below.

[0223] 409. DE-NWDAF identifies the UE collected through the user plane.

[0224] DE-NWDAF can identify UEs that can report UE measurement data via the user plane from the UE list. For easy distinction, this list is referred to as UE list 1 or UE ID list 1.

[0225] User plane measurement data reporting refers to the UE's ability to report its measurement data using the user plane method. In other words, when reporting UE measurement data, the UE can report it through the user plane path.

[0226] 410. DE-NWDAF sends an N2 message to AMF, carrying the user plane address of DE-NWDAF.

[0227] For UEs that support reporting UE measurement data from the user plane, DE-NWDAF can send an N2 message to the AMF, carrying the user plane address of DE-NWDAF, so that the user plane address of DE-NWDAF can be sent to the UE through the AMF.

[0228] This N2 message, also known as a UE measurement data collection request, can be forwarded to the UE via the AMF, thereby requesting the UE to report UE measurement data.

[0229] 411. The AMF sends an N2 message to the UE, carrying the user plane address of DE-NWDAF.

[0230] The AMF forwards the contents of the received N2 message to the UE, which means forwarding the user plane address of DE-NWDAF to the UE.

[0231] 412. The UE establishes a PDU session with DE-NWDAF.

[0232] After receiving the user plane address of DE-NWDAF, the UE can establish a PDU session with DE-NWDAF based on the address, that is, the UE establishes a data transmission channel with DE-NWDAF.

[0233] 413. The UE sends UE measurement data to the DE-NWDAF.

[0234] The UE can report UE measurement data to the DE-NWDAF through the established PDU session.

[0235] 414. DE-NWDAF identifies the UE collected through the control plane.

[0236] For DE-NWDAF, UEs that can report UE measurement methods through the control plane can be identified from the UE list. For easy distinction, this is called UE list 2 or UE ID list 2.

[0237] Specifically, DE-NWDAF can determine which UE measurement data needs to be collected through the control plane based on the information included in the UE ID list returned by the AMF. At the same time, DE-NWDAF assigns a correlationID for this UE measurement data collection.

[0238] 415. DE-NWDAF sends an N2 message to AMF, instructing the reporting of UE measurement data.

[0239] DE-NWDAF sends an N2 message to AMF. The content carried in the message may include, but is not limited to, at least one of the following: UE measurement data or indication of UE measurement data type, UE ID list2 (i.e., UE list 2), UE data reporting method, correlationID, etc.

[0240] The UE data reporting method refers to the way DE-NWDAF requires the UE to report UE measurement data, which can generally be divided into periodic reporting and non-periodic reporting. If the UE data reporting method is non-periodic, DE-NWDAF can also specify the reporting time of the last reported data, such as by including the reporting time in the N2 message. If the UE data reporting method is periodic, DE-NWDAF also indicates the reporting period for each reported data, such as by including the reporting period in the N2 message.

[0241] This N2 message, also known as a UE measurement data collection request, can be forwarded to the UE via the AMF, thereby requesting the UE to report UE measurement data.

[0242] 416. The AMF sends a NAS message to the UE, instructing it to report the UE measurement data.

[0243] After receiving the N2 message, AMF forwards the contents of the N2 message to each UE specified in UE ID list2 via a downlink non-access stratum (DL NAS) message.

[0244] The NAS message may contain at least one of the following: UE measurement data or an indication of the type of UE measurement data, UE data reporting method, or correlation ID.

[0245] The content carried in the NAS message sent by the AMF to the UE can be determined based on the content carried in the N2 message sent by the DE-NWDAF to the AMF. For example, if the N2 message sent by the DE-NWDAF to the AMF contains...

[0246] 417. The UE sends UE measurement data to the AMF.

[0247] According to the instructions of the received DL NAS message, the UE collects the corresponding UE measurement data, such as PDP, CER, CIR or SRS data, and sends the UL NAS message to the AMF in the manner specified in the UE data reporting method in the DL NAS message. The message carries the collected UE measurement data and may also carry the correlation ID.

[0248] 418. AMF sends UE measurement data to DE-NWDAF.

[0249] AMF forwards the UE measurement data reported by the UE to DE-NWDAF.

[0250] 419. DE-NWDAF sends the first data to AF.

[0251] DE-NWDAF can send UE measurement data received through the user plane or control plane to the AF, so that the AF can use the received UE measurement data to train the UE-side model.

[0252] In this embodiment, the DE-NWDAF is defined to support UE measurement data collection, and this capability is registered with the NRF. This allows the AF to obtain UE measurement data from the corresponding DE-NWDAF. Furthermore, since collecting UE measurement data using the user plane requires exposing the user plane address information of the DE-NWDAF, it is not necessary to expose all NWDAF user plane address information; only the user plane address information of the specific NWDAF capable of collecting UE measurement data needs to be exposed. This effectively avoids excessive exposure of internal network information. When collecting UE measurement data using the control plane, compatibility between different NWDAF versions is also ensured. In other words, this implements the NWDAF's ability to expose UE measurement data to third-party servers, enabling these servers to use the UE measurement data for UE-side model training.

[0253] Implementation Method 2

[0254] See Figure 5 The following is a flowchart illustrating another communication method provided in this application embodiment.

[0255] 501. AMF stores UE capability information.

[0256] 502. DE-NWDAF sends capability registration information to NRF.

[0257] 503. AF sends a data subscription request to NEF.

[0258] 504. NEF sends a network element query request to NRF.

[0259] 505. NRF sends a network element query response to NEF.

[0260] 506. NEF sends a data subscription request to DE-NWDAF.

[0261] Steps 501 to 506 can be described in conjunction with the aforementioned steps 401 to 406, and will not be repeated here.

[0262] 507. DE-NWDAF sends a UE measurement data collection request to AMF, which may carry the user plane address.

[0263] This UE measurement data collection request indicates that DE-NWDAF is requesting UE measurement data from AMF. For UEs that may support collecting UE measurement data from the user plane, the user plane address of DE-NWDAF can be provided in advance, so that AMF does not need to query the user plane address from DE-NWDAF in the future, thus reducing signaling overhead.

[0264] If the UE measurement data request does not include the user plane address, the AMF can query the DE-NWDAF for the user plane address, or it can determine that the UE reports the UE measurement data through the control plane. The specific choice can be made based on the actual application scenario.

[0265] In particular, step 508 and step 513 of the device are similar to the aforementioned steps 409 and 418, the difference being that... Figure 4 The steps performed by DE-NWDAF are replaced by those performed by AMF. Similarities will not be elaborated here; only some differences will be introduced below.

[0266] 508. AMF identifies the UEs collected through the user plane.

[0267] AMF can filter out UEs that support reporting UE measurement data from among the UEs that support reporting UE measurement data via the user plane.

[0268] 509. The AMF sends an N2 message to the UE, carrying the user plane address of DE-NWDAF.

[0269] For UEs that support reporting UE measurement data via the user plane, the AMF can send an N2 message to the UE, which carries the user plane address of DE-NWDAF.

[0270] 510. The UE establishes a PDU session with the DE-NWDAF.

[0271] After receiving the user plane address of DE-NWDAF sent by AMF, the UE can establish a PDU session with DE-NWDAF based on the user plane address of DE-NWDAF.

[0272] 511. The UE sends UE measurement data to the DE-NWDAF.

[0273] Steps 510 to 511 can be described in conjunction with the aforementioned steps 412 to 413, and will not be repeated here.

[0274] 512. AMF identifies the UEs collected through the control plane.

[0275] AMF can filter out UEs that support reporting UE measurement data from among the UEs that support reporting UE measurement data via the control plane.

[0276] 513. The AMF sends a NAS message to the UE, instructing it to report the UE measurement data.

[0277] 514. The UE sends UE measurement data to the AMF.

[0278] 515. AMF sends UE measurement data to DE-NWDAF.

[0279] 516. DE-NWDAF sends the first data to AF.

[0280] Steps 513 to 516 are similar to steps 416 and 419 mentioned above, and will not be described again here.

[0281] In this embodiment, data collection can be performed by the NWDAF, and the AMF selects the UE that reports UE measurement data. This allows the AF to obtain UE measurement data from the corresponding DE-NWDAF. Furthermore, since collecting UE measurement data using the user plane requires exposing the user plane address information of the DE-NWDAF, it is not necessary to expose all NWDAF user plane address information; only the user plane address information of the specific NWDAF capable of collecting UE measurement data needs to be exposed. This effectively avoids excessive exposure of internal network information. When collecting UE measurement data using the control plane, compatibility between different NWDAF versions is also ensured.

[0282] Implementation Method 3

[0283] See Figure 6 The following is a flowchart illustrating another communication method provided in this application embodiment.

[0284] 601. AMF stores UE capability information.

[0285] 602. DE-NWDAF sends capability registration information to NRF.

[0286] Steps 601 to 602 can be referred to the aforementioned steps 401 to 402, and will not be repeated here.

[0287] 603. DE-NWDAF sends an N2 message to AMF to subscribe to UE capability information.

[0288] DE-NWDAF can send an N2 message to the AMF to request subscription to UE capability information.

[0289] Step 603 is an optional step.

[0290] 604. AMF sends UE capability information to DE-NWDAF.

[0291] In one scenario, after receiving an N2 message from DE-NWDAF, the AMF can report the received UE, which contains capability information supporting UE measurement data, and the corresponding UE measurement data capability information and UE chip vendor information, to NWDAF via the N2 message.

[0292] In another scenario, after receiving the capability information reported by the UE, the AMF can proactively send the UE's capability information to the DE-NWDAF.

[0293] In another scenario, when the AMF receives a registration message containing the NWDAF container, it forwards the message to the NWDAF, and the UE capability information is contained in the NWDAF container.

[0294] 605. AF sends a data subscription request to NEF.

[0295] 606. NEF sends a network element query request to NRF.

[0296] 607. NRF sends a network element query response to NEF.

[0297] 608. NEF sends a data subscription request to DE-NWDAF.

[0298] Steps 605 to 608 can be referred to in steps 403 to 406 above, and will not be repeated here.

[0299] The DE-NWDAF locally stores the UE capability information sent by the AMF. Upon receiving a data subscription request from the NEF, it can determine the UE list based on the data subscription request. The information included in this UE list can be found in the UE list in step 408 above. The DE-NWDAF determines the UE list based on the capability information of the stored UE measurement data. If the received data subscription request includes AOI and vendor information, the NWDAF can also interact with the AMF to obtain the vendor information of the corresponding UE list, and determine the UE list based on this information and the capability information of the stored UE measurement data.

[0300] 609. DE-NWDAF identifies the UE collected through the user plane.

[0301] 610. DE-NWDAF sends a UE measurement data collection request to AMF, carrying the user plane address of DE-NWDAF.

[0302] 611. The AMF sends an N2 message to the UE, carrying the user plane address of DE-NWDAF.

[0303] 612. The UE establishes a PDU session with the DE-NWDAF.

[0304] 613. The UE sends UE measurement data to the DE-NWDAF.

[0305] 614. DE-NWDAF identifies the UEs collected through the control plane.

[0306] 615. DE-NWDAF sends a UE measurement data collection request to AMF, instructing the reporting of UE measurement data.

[0307] 616. The AMF sends a NAS message to the UE, instructing it to report the UE's measurement data.

[0308] 617. The UE sends UE measurement data to the AMF.

[0309] 618. AMF sends UE measurement data to DE-NWDAF.

[0310] 619. DE-NWDAF sends the first data to AF.

[0311] Steps 609 to 619 can be referred to in the aforementioned steps 409 to 419, and will not be repeated here.

[0312] In this embodiment, DE-NWDAF can subscribe to UE capability information from AMF in advance. Therefore, after receiving a data subscription request, the interface determines the suitable UE from the stored data, thereby realizing a more efficient UE measurement data collection process.

[0313] Implementation Method 4

[0314] See Figure 7 The following is a flowchart illustrating another communication method provided in this application embodiment.

[0315] 701. DE-NWDAF sends capability registration information to NRF.

[0316] Step 70001 can be referred to step 402 above, and will not be repeated here.

[0317] 702. PCF configures URSP for UE measurement data collection.

[0318] First, the PCF can configure a UE route selection policy (URSP) for UE measurement data collection. The URSP can include information such as the data network name (DNN), single network slice selection assistance information (S-NSSAI), or the user plane address of the DE-NWDAF, which can be used for communication between the UE and the DE-NWDAF.

[0319] 703. The UE sends a registration request to the AMF, carrying the UE capability information.

[0320] When a UE accesses the network or is deployed in the network architecture, it can send a registration request to the AMF, which carries UE capability information, including specific UE information and UE measurement capability information. This capability information may include the types of measurement data supported by the UE, such as PDP, CER, CIR, or SRS, or other information related to the UE's measurement capabilities.

[0321] 704. PCF sends URSP to AMF.

[0322] Once the PCF determines the URSP, it can send the URSP to the AMF, which means sending information such as the user plane address of the DNN, S-NSSAI, or DE-NWDAF to the AMF.

[0323] 705. The AMF sends a registration response to the UE, carrying the URSP.

[0324] In response to the registration request sent by the UE, the AMF can send back a registration response, which carries the URSP.

[0325] 706. The UE establishes a PDU session with the DE-NWDAF.

[0326] The UE establishes a PDU session with the DE-NWDAF based on the received URSP, and this PDU session can be used to transmit data between the UE and the DE-NWDAF.

[0327] 707. The UE reports UE measurement data to the DE-NWDAF.

[0328] The UE can report UE measurement data to the DE-NWDAF through the established PDU session.

[0329] 708. DE-NWDAF stores UE measurement data.

[0330] DE-NWDAF can store received UE measurement data.

[0331] 709. AF sends a data subscription request to NEF.

[0332] 710. NEF sends a network element query request to NRF.

[0333] 711. NRF sends a network element query response to NEF.

[0334] 712. NEF sends a data subscription request to DE-NWDAF.

[0335] 713. DE-NWDAF sends the first data to AF.

[0336] After receiving a data subscription request, DE-NWDAF can retrieve UE measurement data from locally stored data that matches the information carried in the data subscription request.

[0337] For example, if the data subscription request carries the UE vendor or chip vendor, the DE-NWDAF can obtain the measurement data reported by the UE corresponding to the UE vendor or chip vendor from the stored data, or negotiate with the AMF to determine the UE corresponding to the UE vendor or chip vendor, obtain the UE measurement data from the locally stored data, and feed the UE measurement data back to the AF.

[0338] In this embodiment of the application, the UE can report the UE measurement data to the DE-NWDAF in advance. After the DE-NWDAF receives the data subscription request, it can directly obtain the UE measurement data required by the AF from the stored data, thereby achieving more efficient UE measurement data feedback.

[0339] The foregoing has described the method flow provided in the embodiments of this application. The following describes the structure of the apparatus for executing the foregoing method flow.

[0340] See Figure 8 This application provides a schematic diagram of the structure of a communication device, applied in a communication system, including:

[0341] The receiving module 801 is used to receive a first request sent by a third device. The first request is used to request UE measurement data. The first request contains information about the target UE. The first device is a device that supports the collection of UE measurement data.

[0342] The sending module 802 is used to send first data to the third device, wherein the first data is determined by the first device according to the first request.

[0343] The communication device can be used to perform the steps executed by the first device in the aforementioned embodiments.

[0344] See Figure 9 The present application provides a schematic diagram of another communication device, applied to a communication system, comprising:

[0345] The receiving module 901 is configured to receive a second query request from a third device, wherein the second query request is used to request a device that supports the collection of UE measurement data;

[0346] The sending module 902 is used to send a query response to the third device, the query response including information about the first device, which is a device that supports UE measurement data collection.

[0347] The communication device can be used to perform the steps performed by the second device in the aforementioned embodiments.

[0348] See Figure 10 The present application provides another schematic diagram of the structure of a communication device, including:

[0349] The receiving module 1001 is used to receive a first data subscription request sent by the fifth device, the first data subscription request being used to request UE measurement data;

[0350] The sending module 1002 is used to send a second query request to the second device. The second query request is used to request a device that supports the collection of UE measurement data.

[0351] The receiving module 1001 is also used to receive a query response, which includes information about the first device, which is a device that supports the collection of UE measurement data.

[0352] The sending module 1002 is also configured to send a first request to the first device, the first request being used to request UE measurement data;

[0353] The receiving module 1001 is also used to receive first data sent by the first device, wherein the first data is determined by the first device according to the first request;

[0354] The sending module 1002 is also used to send the first data to the fifth device.

[0355] The communication device can be used to perform the steps performed by the third device in the aforementioned embodiments.

[0356] See Figure 11 The present application provides another schematic diagram of the structure of a communication device, including:

[0357] The receiving module 1101 is used to receive a first query request sent by the first device. The first query request is a list of UEs that support the UE measurement data reporting capability. The first query request contains information about the target UE. The UE information indicates the UE's manufacturer information or UE chip identification information.

[0358] The sending module 1102 is used to send a second UE list to the first device. The second UE list is determined based on UE information.

[0359] The communication device can be used to perform the steps executed by the fourth device in the aforementioned embodiments.

[0360] See Figure 12 The present application provides a schematic diagram of the structure of a user equipment, including:

[0361] The transmitting module 1201 is used to transmit capability information to the fourth device. The capability information includes a capability indication for indicating whether the UE supports uploading UE measurement data, or the UE's manufacturer information or the chip information used by the UE.

[0362] The user equipment can be used to perform the steps performed by the UE device in the aforementioned embodiments.

[0363] like Figure 13 The diagram shown is a hardware structure schematic of a communication device 130 provided in an embodiment of this application. This communication device 130 can be used to implement the functions of the various devices described in the aforementioned methods.

[0364] Figure 13 The communication device 130 shown may include a processor 1301, a memory 1302, a communication interface 1303, and a bus 1304. The processor 1301, the memory 1302, and the communication interface 1303 can be connected to each other via the bus 1304.

[0365] The processor 1301 is the control center of the communication device 130. It can be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor.

[0366] As an example, processor 1301 may include one or more CPUs, for example Figure 13 CPU 0 and CPU 1 are shown in the diagram.

[0367] The memory 1302 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0368] In one possible implementation, the memory 1302 may exist independently of the processor 1301. The memory 1302 can be connected to the processor 1301 via a bus 1304 and is used to store data, instructions, or program code. When the processor 1301 calls and executes the instructions or program code stored in the memory 1302, it can implement the method provided in the embodiments of this application.

[0369] In another possible implementation, the memory 1302 can also be integrated with the processor 1301.

[0370] The communication interface 1303 is used for the communication device 130 to connect with other devices via a communication network, which may be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The communication interface 1303 may include a receiving unit for receiving data and a transmitting unit for transmitting data.

[0371] The 1304 bus can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. This bus can be divided into address bus, data bus, and control bus, etc. For ease of representation, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0372] It should be pointed out that, Figure 13 The structure shown does not constitute a limitation on the communication device 130, except... Figure 13In addition to the components shown, the communication device 130 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0373] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0374] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0375] This application also provides a computer-readable storage medium storing a program for training a model or performing inference tasks, which, when run on a computer, causes the computer to perform the aforementioned... Figures 3 to 7 All or part of the steps in the method described in the embodiments shown.

[0376] This application also provides a digital processing chip. This digital processing chip integrates circuitry for implementing the aforementioned processor or processor functions, and one or more interfaces. When the digital processing chip integrates a memory, it can perform the method steps of any one or more of the foregoing embodiments. When the digital processing chip does not integrate a memory, it can be connected to an external memory via a communication interface. The digital processing chip implements the method steps of any one or more of the foregoing embodiments based on the program code stored in the external memory.

[0377] This application also provides a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0378] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include ROM, RAM, disk, or optical disk, etc.

[0379] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. The term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products, or devices. The naming or numbering of steps in this application does not imply that the steps in the method flow must be executed in the time / logical order indicated by the naming or numbering. The execution order of the named or numbered process steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effect can be achieved. The division of modules in this application is a logical division. In actual applications, there may be other division methods. For example, multiple modules may be combined into or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the modules shown or discussed may be through some ports, and the indirect coupling or communication connection between modules may be electrical or other similar forms, which are not limited in this application. Furthermore, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules. Some or all of the modules can be selected to achieve the purpose of the solution in this application according to actual needs.

Claims

1. A communication method, characterized in that, Applied in communication systems, including: The first device receives a first request sent by the third device. The first request is used to request UE measurement data. The first request contains information about the target UE. The first device is a device that supports the collection of UE measurement data. The first data sent by the first device to the third device is determined by the first device based on the first request.

2. The method according to claim 1, characterized in that, Before the first device receives the first request sent by the third device, the method further includes: The first device sends capability registration information to the second device, the capability registration information including a first indication, the first indication being used to indicate that the first device supports UE measurement data collection.

3. The method according to claim 2, characterized in that, The capability registration information also includes the types of UE measurement data that can be collected, a first UE list, one or more items in a first region, the first UE list including information on at least one UE, the at least one UE being a UE for which the first device can collect UE measurement data, and the first region being the distribution range of UEs for which the first device can collect UE data.

4. The method according to any one of claims 1-3, characterized in that, The first request carries a second instruction, which is used to instruct UE measurement data collection or to instruct the type of UE measurement data.

5. The method according to any one of claims 1-4, characterized in that, The information of the target UE indicates a list of target UE identifiers, the target UE manufacturer information, or the target UE chip identifier information.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The first device sends a measurement data collection request to the target UE, the measurement data collection request including a third instruction, the target UE referring to at least one UE from a second UE list determined by the first device based on the information of the target UE; The first device receives UE measurement data sent by the target UE, and the first data is determined by the first device based on UE measurement data sent by one or more target UEs.

7. The method according to claim 6, characterized in that, The method further includes: The first device stores a list of UEs that support UE measurement data reporting capabilities, and determines the second UE list from the UE list information; or, The first device sends a first query request to the fourth device. The first query request supports UE information that enables UE measurement data reporting. The first query request includes information about the target UE. The first device receives the second UE list sent by the fourth device.

8. A communication method, characterized in that, Applied to communication systems, including: The second device receives a second query request from the third device, the second query request being used to request a query for a device that supports UE measurement data collection; The second device sends a query response to the third device, the query response including information about the first device, which is a device that supports UE measurement data collection.

9. The method according to claim 8, characterized in that, The method further includes: The second device receives capability registration information sent by the first device, the capability registration information including a first indication, the first indication being used to indicate that the first device supports UE measurement data collection.

10. The method according to claim 8 or 9, characterized in that, The second query request includes information about the target UE, which indicates a list of target UE identifiers, target UE manufacturer information, or target UE chip identifier information.

11. A communication method, characterized in that, include: The third device receives a first data subscription request sent by the fifth device, the first data subscription request being used to request UE measurement data; The third device sends a second query request to the second device, the second query request being used to request a query for a device that supports UE measurement data collection; The third device receives a query response, which includes information about the first device, which is a device that supports UE measurement data collection. The third device sends a first request to the first device, the first request being used to request UE measurement data; The third device receives first data sent by the first device, the first data being determined by the first device based on a first request; The third device sends the first data to the fifth device.

12. The method according to claim 11, characterized in that, The first data subscription request includes information about the target UE, which indicates a list of target UE identifiers, target UE manufacturer information, or target UE chip identifier information.

13. A communication method, characterized in that, include: The fourth device receives a first query request sent by the first device. The first query request is a list of UEs that support UE measurement data reporting capabilities. The first query request contains information about the target UE, and the UE information indicates the UE's manufacturer information or UE chip identification information. The second UE list sent by the fourth device to the first device is determined based on the information of the UE.

14. The method according to claim 13, characterized in that, The method further includes: The fourth device receives capability information sent by the UE, the UE capability information including a capability indication for whether the UE supports uploading UE measurement data, or the manufacturer information of the UE, or the chip information used by the UE; The fourth device determines the second UE list based on the UE's capability information.

15. A communication method, characterized in that, include: The UE sends capability information to the fourth device. The capability information includes a capability indication for whether the UE supports uploading UE measurement data, or the manufacturer information of the UE, or the chip information used by the UE.

16. A communication device, characterized in that, Applied in communication systems, including: The receiving module is used to receive a first request sent by a third device. The first request is used to request UE measurement data. The first request contains information about the target UE. The first device is a device that supports the collection of UE measurement data. The sending module is used to send first data to the third device, wherein the first data is determined by the first device according to the first request.

17. The apparatus according to claim 16, characterized in that, The sending module is further configured to send capability registration information to the second device before the first device receives the first request sent by the third device. The capability registration information includes a first indication, which is used to indicate that the first device supports UE measurement data collection.

18. A communication device, characterized in that, Applied to communication systems, including: The receiving module is configured to receive a second query request from a third device, wherein the second query request is used to request a device that supports the collection of UE measurement data; The sending module is used to send a query response to the third device, the query response including information about the first device, which is a device that supports UE measurement data collection.

19. A communication device, characterized in that, include: The receiving module is configured to receive a first data subscription request sent by a fifth device, wherein the first data subscription request is used to request UE measurement data; The sending module is used to send a second query request to the second device, the second query request being used to request a device that supports the collection of UE measurement data; The receiving module is also configured to receive a query response, the query response including information about a first device, the first device being a device that supports UE measurement data collection; The sending module is further configured to send a first request to the first device, the first request being used to request UE measurement data; The receiving module is further configured to receive first data sent by the first device, wherein the first data is determined by the first device according to the first request; The sending module is also used to send the first data to the fifth device.

20. A communication device, characterized in that, include: The receiving module is configured to receive a first query request sent by the first device. The first query request includes a list of UEs that support UE measurement data reporting capabilities. The first query request contains information about the target UE, and the UE information indicates the UE's manufacturer information or UE chip identification information. The sending module is used to send the second UE list to the first device, the second UE list being determined based on the information of the UE.

21. A user equipment, characterized in that, include: The sending module is used to send capability information to the fourth device. The capability information includes a capability indication for indicating whether the UE supports uploading UE measurement data, or the manufacturer information of the UE, or the chip information used by the UE.

22. A communication system, characterized in that, It includes at least two of the first device, the second device, the third device, the fourth device, or the fifth device; The first device is used to perform the method as described in any one of claims 1-7; The second device is used to perform the method as described in any one of claims 8-10; The third device is used to perform the method as described in any one of claims 11 to 12; The fourth device is used to perform the method as described in any one of claims 13 to 14; The fifth device is used to perform the method as described in claim 15.

23. An apparatus, characterized in that, Includes a unit for performing the method as described in any one of claims 1 to 7.

24. An apparatus, characterized in that, Includes a unit for performing the method as described in any one of claims 8 to 10.

25. An apparatus, characterized in that, Includes a unit for performing the method as described in any one of claims 11 to 12.

26. An apparatus, characterized in that, Includes a unit for performing the method as described in any one of claims 13 to 14.

27. An apparatus, characterized in that, Includes units for performing the method as described in claim 15.

28. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1 to 7, 8 to 10, 11 to 12, 13 to 14 or 15.

29. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the method as described in any one of claims 1 to 7, 8 to 10, 11 to 12, 13 to 14 or 15.

Images