Communication method, communication device, storage medium, and program product

Abstract

This application discloses a communication method, communication device, storage medium, and program product, relating to the field of communication technology, capable of managing non-drone terminals flying in the air. The method includes: receiving first information; the first information includes the terminal's location information, or the terminal's location information and speed information, wherein the terminal is a non-drone terminal; and, if it is determined based on the terminal's location information, or the terminal's location information and speed information, that the terminal is in a first state, sending second information; the second information is used to indicate the terminal's identifier.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, communication device, storage medium, and program product. Background Technology

[0002] Communication equipment in flight is collectively referred to as airborne equipment, and its operation should be managed by the network elements of the unrewed aerial system (UAS) service provider (USS). Currently, there is a lack of an airborne management mechanism to identify and manage all airborne equipment. Summary of the Invention

[0003] This application provides a communication method, communication device, storage medium, and program product capable of managing over-the-air terminals.

[0004] To achieve the above objectives, this application provides the following technical solution:

[0005] Firstly, a communication method is provided. This method can be executed by a network device, or by a component of the network device, such as its processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the network device. The following explanation uses the execution of this method by a network device as an example. The communication method includes: after receiving first information to determine that a terminal is in a state requiring management, the network device sends a first identifier of the terminal to a first network element managing the terminal, indicating that the terminal is in a state requiring management. In this way, for a terminal requiring management, the UAV management system can report it to the first network element managing that terminal, enabling the first network element to manage the terminal. This solves the technical problem in related technologies of lacking the ability to manage all aerial devices.

[0006] In one possible implementation, the first information is sent by the network data analysis network element; or, the first information is sent by the operation and maintenance management network element; wherein, the functions of the operation and maintenance management network element include fault management, performance monitoring, and service assurance.

[0007] Based on this, network devices can obtain information from network data analysis network elements or operation and maintenance management network elements to determine whether the terminal is in the first state.

[0008] In one possible implementation, the first information includes a second identifier of the terminal and first instruction information; the second identifier corresponds to the first identifier.

[0009] Based on this, the network device can identify the terminal based on its second identifier and determine that the terminal is in a first state based on the first instruction information. Furthermore, the network device can convert the second identifier into a first identifier that the first network element can recognize, thereby enabling the first network element to correctly identify the terminal that needs to be managed.

[0010] In one possible implementation, the first indication information is also used to indicate the terminal's location information, or the terminal's location information and speed information.

[0011] In one possible implementation, the method further includes: the network device determining that the terminal is in a first state based on the first indication information in the first information.

[0012] Based on this, the network device can determine that the terminal is in a first state based on the terminal's location information indicated by the first instruction information, or the network device can determine that the terminal is in a first state based on the terminal's location information and speed information indicated by the first instruction information.

[0013] In one possible implementation, before sending the second information, the method further includes: the network device requesting a first identifier corresponding to the second identifier, and thereafter, the network device receiving an indication of the first identifier corresponding to the second identifier.

[0014] Based on this, after the network device receives the second identifier of the terminal, it requests to obtain the first identifier corresponding to the second identifier, and after obtaining the first identifier corresponding to the second identifier, it indicates the first identifier to the first network element.

[0015] In one possible implementation, before receiving the first information, the method further includes: sending a first subscription message to the operation and maintenance management network element, the first subscription message being used to request information about the terminal being in a first state; the operation and maintenance management network element has functions including fault management, performance monitoring, and service assurance; receiving a first subscription response message from the operation and maintenance management network element; the first subscription response message being used to indicate the status parameters of the successfully subscribed terminal.

[0016] Based on this, before receiving the first information, the network device subscribes to the information about the terminal being in the first state from the operation and maintenance management network element, so that after the maintenance management network element obtains the information about the terminal being in the first state, it sends the information to the network device.

[0017] In one possible implementation, the first identifier is the terminal's unique identifier.

[0018] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0019] Therefore, when instructing a terminal to a UAV system service provider's network element, the network device uses the terminal's unique identifier to prevent the UAV system service provider's network element from failing to correctly identify the terminal. When the terminal is within the management range of the UAV system service provider's network element, the network device uses a second identifier to identify the terminal, thereby avoiding the leakage of the terminal's unique identifier due to the use of the first unique identifier during air interface transmission.

[0020] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0021] Based on this, the second network element can manage terminals whose altitude is greater than the first threshold, or whose altitude is greater than the first threshold and whose speed is greater than the second threshold.

[0022] Secondly, a communication method is provided. This method can be executed by a network data analysis network element, or by a component of the network data analysis network element, such as its processor, chip, or chip system. It can also be implemented by a logic module or software capable of implementing all or part of the network data analysis network element. The following explanation uses the execution of this method by a network data analysis network element as an example. The communication method includes: the network data analysis network element receiving location information of a terminal, or the terminal's location information and speed information; subsequently, the network data analysis network element uses first information to determine that the terminal is in a first state.

[0023] In one possible implementation, the first information includes a second identifier of the terminal and first indication information, which is used to indicate that the terminal is in a first state.

[0024] In one possible implementation, the first indication information is used to indicate the terminal's location information, or the terminal's location information and speed information.

[0025] In one possible implementation, the first identifier is the terminal's unique identifier.

[0026] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0027] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0028] Thirdly, a communication method is provided. This method can be executed by a unified data management network element, or by a component of the unified data management network element, such as a processor, chip, or chip system of the unified data management network element. It can also be implemented by a logic module or software capable of implementing all or part of the unified data management network element. The following description uses the execution of this method by a unified data management network element as an example. The communication method includes: the unified data management network element receiving request information for requesting a first identifier corresponding to a second identifier; thereafter, the unified data management network element sending response information indicating the first identifier corresponding to the second identifier.

[0029] In one possible implementation, before receiving the first request message, the method further includes: receiving a second request message; the second request message is used to request the allocation of a second identifier for the terminal; sending a second response message; the second response message includes the second identifier allocated to the terminal.

[0030] In one possible implementation, the first identifier is the terminal's unique identifier.

[0031] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0032] Fourthly, a communication method is provided. This method can be executed by a terminal, or by a component of the terminal, such as the terminal's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the terminal. The following description uses the method executed by a terminal as an example. The communication method includes: the terminal receiving a second identifier; subsequently, the terminal sending fourth information; the fourth information includes the terminal's second identifier and first indication information; the first indication information is used to indicate the terminal's location information, or the terminal's location information and speed information.

[0033] In one possible implementation, the fourth information is carried in the minimum road test measurement data; or, the fourth information is carried in the measurement report.

[0034] In one possible implementation, the first identifier is the terminal's unique identifier.

[0035] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0036] Fifthly, a communication method is provided. This method can be executed by an access network device, or by a component of the access network device, such as the access network device's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the access network device. The following description uses the execution of this method by an access network device as an example. The communication method includes: the access network device receiving fourth information; the fourth information including a second identifier of the access network device and first indication information; the first indication information indicating the location information of the access network device, or the location information and speed information of the access network device; the access network device sending first information; the first information determining that the terminal is in a first state.

[0037] In one possible implementation, before receiving the fourth information, the method further includes sending a second identifier of the terminal to the terminal.

[0038] In one possible implementation, the first identifier is the terminal's unique identifier.

[0039] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0040] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0041] Sixthly, a communication method is provided. This method can be executed by an access and mobility management network element (AMU), or by a component of the AMU, such as a processor, chip, or chip system of the AMU, or by a logic module or software capable of implementing all or part of the AMU. The following description uses the execution of this method by an AMU as an example. The communication method includes: the AMU receiving first information; the first information used to determine that the terminal is in a first state; and the AMU sending the first information.

[0042] In one possible implementation, the method further includes: sending a second request message; the second request message is used to request the allocation of a second identifier for the terminal; receiving a second response message; the second response message includes the second identifier allocated to the terminal.

[0043] In one possible implementation, the method further includes: a second identifier of the sending terminal.

[0044] In one possible implementation, the first identifier is the terminal's unique identifier.

[0045] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0046] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0047] In a seventh aspect, a communication device is provided for implementing the various methods described above. This communication device may be a network device as described in the first aspect, or a device comprising the network device, or a device included in the network device, such as a chip. Alternatively, the communication device may be a terminal as described in the second aspect, or a device comprising the terminal, or a device included in the terminal, such as a chip. The communication device includes modules, units, or means (MAEns) corresponding to the methods described above. These modules, units, or MAEns may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0048] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, also referred to as a transceiver unit, is used to implement the transmission and / or reception functions in any of the above aspects and their possible implementations. The transceiver module may consist of transceiver circuits, transceivers, transceivers, or communication interfaces. The processing module can be used to implement the processing functions in any of the above aspects and their possible implementations.

[0049] In some possible designs, the transceiver module includes a sending module and a receiving module, which are used to implement the sending and receiving functions in any of the above aspects and any possible implementation methods.

[0050] Eighthly, a communication device is provided, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods of any of the preceding aspects. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be a network device as described in the first aspect, or a device comprising the network device, or a device included in the network device, such as a chip. Alternatively, the communication device may be a terminal as described in the second aspect, or a device comprising the terminal, or a device included in the terminal, such as a chip. In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0051] In one possible implementation, the processor includes logic circuitry and input and / or output interfaces. The output interfaces are used to perform the sending action in the corresponding method, and the input interfaces are used to perform the receiving action in the corresponding method.

[0052] In one possible implementation, the communication device further includes a communication interface and a communication bus, with the processor, memory, and communication interface connected via the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. The communication interface can also be called a transceiver. Optionally, the communication interface includes a transmitter and a receiver; in this case, the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.

[0053] In some possible designs, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components. When the communication device is a chip, the aforementioned transmitting action / function can be understood as an output, and the aforementioned receiving action / function can be understood as an input.

[0054] Ninthly, a chip is provided, the chip including a processor for implementing the functions involved in any of the foregoing aspects or any implementation thereof.

[0055] In some possible designs, the chip includes a memory for storing necessary program instructions and data.

[0056] In a tenth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods of any of the above aspects or any implementation thereof.

[0057] Eleventhly, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to execute any of the above-described methods or any implementation thereof.

[0058] In a twelfth aspect, a communication system is provided, which includes the network device described in the first aspect and the terminal described in the second aspect.

[0059] The technical effects of any of the implementation methods in aspects two through twelfth can be found in the technical effects of the corresponding implementation methods in aspect one, and will not be repeated here.

[0060] It should be noted that any of the possible implementations of any of the above aspects can be combined, provided that the solutions do not contradict each other. Attached Figure Description

[0061] Figure 1 This application provides a schematic diagram of a USS process for identifying airborne equipment.

[0062] Figure 2 A schematic diagram of a management-based MDT measurement process provided for this application;

[0063] Figure 3 A schematic diagram of a signaling-based MDT measurement process is provided for this application;

[0064] Figure 4 This application provides a schematic diagram of the process for NWDAF to acquire data from OAM;

[0065] Figure 5 A schematic diagram of an O-RAN architecture provided in this application;

[0066] Figure 6 A schematic diagram of the system architecture of a communication system provided in this application;

[0067] Figure 7 This application provides another schematic diagram of an O-RAN architecture;

[0068] Figure 8 A schematic diagram of the architecture of a communication system provided in this application;

[0069] Figure 9 A schematic diagram of the composition of a communication device provided in this application;

[0070] Figure 10 A flowchart illustrating a communication method provided in this application;

[0071] Figure 11 A flowchart illustrating yet another communication method provided in this application;

[0072] Figure 12 A flowchart illustrating yet another communication method provided in this application;

[0073] Figure 13 A flowchart illustrating yet another communication method provided in this application;

[0074] Figure 14 A flowchart illustrating yet another communication method provided in this application;

[0075] Figure 15 A flowchart illustrating yet another communication method provided in this application;

[0076] Figure 16 A flowchart illustrating yet another communication method provided in this application;

[0077] Figure 17 A flowchart illustrating yet another communication method provided in this application;

[0078] Figure 18 A flowchart illustrating yet another communication method provided in this application;

[0079] Figure 19 This is a schematic diagram of the structure of a communication device provided in this application. Detailed Implementation

[0080] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0081] 1. Flight Terminal Management

[0082] In this application, flight terminal management can be understood as managing flight terminals, such as managing the flight area, flight speed, and flight time of flight terminals.

[0083] In this application, the term "flight terminal" can be replaced with "airborne equipment" or "airborne terminal." Based on whether the flight terminal has specific flight capabilities, it can be divided into two categories: unmanned aerial vehicle (UAV) terminals and non-UAV terminals. UAV terminals, often abbreviated as UAVs, refer to terminals that possess flight components, can fly independently in the air, and have communication capabilities. Non-UAV terminals, often abbreviated as non-UAV terminals, refer to terminals that do not possess flight components but can be mounted on / assisted by other flight-capable equipment to fly in the air and possess communication capabilities.

[0084] Taking UAVs as an example, UAVs flying in the air may have certain impacts on public safety and aviation safety. Therefore, it is necessary to monitor UAVs in flight. Currently, UAVs are usually monitored by the USS (United States Security Service). In the monitoring process, the USS first needs to identify the UAV in the air, and then monitor the UAV in the air, such as monitoring its flight path. When identifying terminals in the air, if there are terminals communicating in the air, then the terminals communicating in the air will be identified as aerial devices (UAVs). Currently, the terminals defined in NR (Radio Normalization) include three types: R18 UAV (UAVs are defined in R18 and can also be simply referred to as UAVs), R18 non-UAVs (other terminals in R18 that do not meet the requirements of the UAV definition), and Pre-R18 terminals (terminals defined before R18).

[0085] For the aforementioned R18 UAV, network devices can identify whether the terminal is an airborne device by methods such as subscription messages / UE capabilities / measurement reports / flight path reports / handover frequencies, and report the UAV ID identified as an airborne device to the USS for monitoring.

[0086] However, for R18 non-UAVs and Pre-R18 UEs (collectively referred to as non-UAV terminals), these non-UAV terminals may also be in flight. Currently, there is no method to identify whether such non-UAV terminals are in flight, and therefore it is impossible to monitor non-UAV terminals in flight.

[0087] The USS process for identifying aerial equipment is as follows: Figure 1 As shown, both UAVs and non-UAV terminals (denoted as terminals) communicate normally with the network when in flight. Access network devices can communicate with both UAVs and terminals separately, acquire communication data, and report this data to the core network. However, because UAV identifiers are pre-assigned to UAVs in the USS, core network devices can report UAV communication data to the USS based on these identifiers. Conversely, since no identifiers are pre-assigned to terminals in the USS, the USS cannot correctly identify the terminals, resulting in the USS being unable to acquire their communication data.

[0088] 2. Minimization of drive tests (MDT)

[0089] MDT (Multi-Targeting Measurement) refers to a measurement method that obtains network performance parameters through terminals and / or network devices, reducing reliance on drive testing for network performance parameters. During MDT measurement, terminals supporting MDT tasks can report their location and speed information via information cells (such as CommonLocationInfo cells). Network devices can then use this location information to identify the terminal's position and movement status.

[0090] Current MDT measurement methods include: 2.1, management-based MDT measurement and 2.2, signaling-based MDT measurement, which will be described below.

[0091] 2.1 Management-Based MDT Measurement

[0092] Management-based MDT measurement can be applied to scenarios involving the measurement of cell radio quality. During management-based MDT measurement, all terminals supporting MDT measurement tasks within a preset range (such as a preset cell identifier or a preset trace area (TA)) need to perform MDT measurements (also known as MDT data acquisition and analysis).

[0093] like Figure 2 As shown, the management-based MDT measurement process includes the following steps:

[0094] Step 200: The access and mobility management function (AMF) sends terminal authorization information to the terminal. Correspondingly, the terminal receives the terminal authorization information.

[0095] Optionally, the terminal authorization information is used to indicate whether the terminal is an MDT contracted user.

[0096] As an example, terminal authorization information is carried in the INITIAL CONTEXT SETUP REQUEST message. During the initial terminal access process, the AMF sends the INITIAL CONTEXT SETUP REQUEST message to the terminal, indicating whether the terminal is a subscribed user of the MDT.

[0097] Step 201: The Mobile Broadband Automation Engine (MAE) client sends MDT subscription task configuration information to MAEMAE.

[0098] In some embodiments, users select to subscribe to MDT measurement events through the MAE interface displayed on the client and configure the configuration parameters of the MDT measurement events.

[0099] Step 202: MAE sends an MDT measurement event subscription message to the access network equipment.

[0100] In some embodiments, the MAE determines the MDT measurement subscription event based on the configuration operation of the relevant personnel, and sends the subscription message of the MDT measurement event to the access network equipment.

[0101] Step 203: The access network device sends the MDT measurement configuration to the terminal.

[0102] In some embodiments, the access network device selects all terminals that support MDT measurement (i.e., terminals that have subscribed to MDT measurement services) within a preset range (such as a preset cell identifier or preset TA) and sends MDT measurement configuration to the selected terminals.

[0103] Step 204: The terminal sends the MDT measurement results to the access network equipment.

[0104] In some embodiments, after receiving the MDT measurement configuration, the terminal performs MDT measurement based on the MDT measurement configuration and determines the MDT measurement result. The terminal then sends the MDT measurement result to the access network device.

[0105] Optionally, the above MDT measurement results may include the terminal's location information, or the terminal's location information and speed information.

[0106] Step 205: The access network equipment sends the MDT measurement results to the Operation Administration and Maintenance (OAM) system.

[0107] In some embodiments, the access network device periodically sends MDT measurement results to the OAM. The OAM then sends the MDT measurement results to the network optimization platform, enabling the network optimization platform to perform network optimization based on the MDT measurement results.

[0108] 2.2 Signaling-based MDT Measurement

[0109] Signaling-based MDT measurement can be applied to scenarios involving follow-up processing of user complaints. In a signaling-based MDT measurement process, a designated terminal supporting MDT measurement tasks (such as a terminal with a specified International Mobile Subscriber Identity (IMSI)) is required to perform the MDT measurement.

[0110] like Figure 3 As shown, the signaling-based MDT measurement process includes the following steps:

[0111] Step 300: AMF sends terminal authorization information to the terminal.

[0112] The specific implementation of step 300 can refer to the implementation of step 200 above, and this application does not limit it.

[0113] Step 301: The client sends the MDT subscription task configuration information to MAE.

[0114] The specific implementation of step 301 can refer to the implementation of step 201 above, and this application does not limit it.

[0115] Step 302: MAE sends an MDT measurement event subscription message to AMF.

[0116] In some embodiments, MAE determines the MDT subscription event based on the user's configuration operation and sends the subscription message of the MDT measurement event to AMF.

[0117] Step 303: The AMF sends a terminal selection message to the access network device.

[0118] In some embodiments, the AMF instructs the access network device to select a specified terminal that supports MDT measurement tasks (such as a specified IMSI terminal) to perform MDT measurements; the AMF also sends the MDT measurement configuration to the access network device.

[0119] Step 304: The access network device sends the MDT measurement configuration to the selected terminal.

[0120] In some embodiments, the access network device sends the MDT measurement configuration to the terminal specified above, so that the terminal performs MDT measurement.

[0121] Step 305: The terminal sends the MDT measurement results to the access network equipment.

[0122] The specific implementation of step 305 can refer to the implementation of step 204 above, and this application does not limit it.

[0123] Step 306: The access network device sends the MDT measurement results to the OAM.

[0124] The specific implementation of step 306 can refer to the implementation of step 205 above, and this application does not limit it.

[0125] While current MDT (Multi-Target Measurement) results include terminal location and speed information, access network devices report these results to the OAM (Operational Access Management) system after acquisition. However, the OAM system is not a network element in the 5G core network. In existing technology, core network elements cannot directly obtain the terminal location and speed information from the MDT results, thus making it impossible to determine whether the terminal is in the first state. Furthermore, in the current MDT measurement process, the terminal does not report its identifier simultaneously with the MDT measurement results, causing access network devices and the OAM system to be unable to identify the terminal corresponding to each MDT measurement result, and consequently, unable to determine the terminal's location and speed information.

[0126] 3. Terminal Identification

[0127] For the aforementioned UAVs, the network side allocates dedicated UAV IDs for UAV communication. Specifically, UAV IDs can include the 3rd Generation Partnership Project (3GPP) UAV identity (3GPP UAV ID) and the Civil Aviation Administration-level (CAA) UAV identity (CAA UAV ID). The 3GPP UAV ID is an identifier assigned to each UAV by the 3GPP system for identification within the 3GPP system. The CAA UAV ID is an identifier assigned to each UAV by the USS (United States Service) for unique identification within the USS's management scope. There is a mapping relationship between the 3GPP UAV ID and the CAA UAV ID. The USS can determine the corresponding CAA UAV ID from the 3GPP UAV ID in the UAV information reported through the 3GPP network, thereby enabling monitoring and management of UAVs based on the CAA UAV ID.

[0128] For non-UAV terminals, identifiers generally include temporary identifiers (such as Temporary Mobile Subscriber Identity (TMSI)) and permanent identifiers (such as IMSI). The temporary and permanent identifiers are typically assigned to the terminal by a unified data management network element (such as Unified Data Management, UDM). The TMSI is a temporary identifier assigned to the terminal by the core network when the terminal accesses the network. It is valid only for a certain period within a location area and is constantly changed. The more frequently the TMSI is changed, the better the security. The IMSI is used to uniquely identify the terminal globally; one IMSI uniquely identifies one terminal. As a unique and permanent identifier for the terminal, to protect user privacy, the use of IMSI in the air interface should be minimized to prevent interception during air interface transmission, which could lead to privacy leaks and affect user security. Using TMSI temporarily instead of IMSI can enhance system security and prevent unauthorized individuals or groups from stealing IMSI or tracking user location by monitoring signaling on the radio path.

[0129] Currently, non-UAV terminals lack a unique identifier within the USS (United States Service) similar to the UAV ID mentioned above. Applying the TMSI (Time Management System) to a non-UAV terminal in the first state is problematic because the TMSI is only valid for a limited time within a specific location area. Since flight terminals typically move quickly out of an area, the TMSI becomes unusable after changing locations during flight. Applying the IMSI (Information Management System) to a non-UAV terminal in the first state leads to frequent direct use of the IMSI over the air interface, posing a risk of IMSI leakage. Therefore, effective management of non-UAV terminal flights is currently impossible.

[0130] 4. Network Data Analysis Element

[0131] Network data analytics elements are used to collect, analyze, and predict data from various network functions (NFs), such as policy control elements, session management elements, user plane elements, access management elements, operation and maintenance management elements, and application function elements (through network capability opening function elements). In 5G communication systems, network data analytics elements can be network data analytics function (NWDAF) elements. In future communication systems, network data analytics elements may still be NWDAF elements, or may have other names; this application embodiment does not limit this.

[0132] The following section uses the Network Data Analysis (NWDAF) network element and the Operation, Maintenance and Management (OAM) network element as examples to explain in detail the process by which the NWDAF obtains data from the OAM. Figure 4 As shown, the specific process by which NWDAF obtains data from OAM includes:

[0133] Step 401: NWDAF sends a subscription request message to OAM. Correspondingly, OAM receives the subscription request message from NWDAF.

[0134] In some embodiments, NWDAF sends a subscription request message to OAM to request subscription to content required by NWDAF.

[0135] As an example, the subscription request message is: Subscribe(Input).

[0136] Step 402: OAM sends a subscription response message to NWDAF. NWDAF receives the subscription response message from OAM.

[0137] In some embodiments, OAM sends a subscription response message to NWDAF to notify NWDAF whether the subscription was successful.

[0138] As an example, the subscription response message is: Subscribe(Output).

[0139] Step 403: OAM data preparation.

[0140] In some embodiments, OAM prepares the data for the NWDAF subscription.

[0141] Step 404: OAM sends a notification message to NWDAF.

[0142] In some embodiments, OAM notifies NWDAF that the data it has subscribed to is ready, and NWDAF can retrieve the data via a specified file transfer protocol.

[0143] As an example, the notification message above is: Notification.

[0144] Due to issues such as data security, privacy protection, resource consumption, technical complexity, and maintenance costs, some core networks do not support NWDAF functionality. This results in network elements in core networks that do not support NWDAF being unable to access and collect data from OAM, and unable to obtain terminal location and status information.

[0145] 5. Measurement Report

[0146] Since base stations are currently configured with beams primarily radiating towards the ground, terminals communicating in the air can only access the network through beams reflected or refracted from the ground. Therefore, communication metrics differ significantly between air and ground-based communication. For example, parameters such as terminal trajectory, interference level, serving cell handover, and / or reference signal received power (RSRP) / reference signal received quality (RSRQ) distribution all differ markedly between air and ground communication. The measurement reports submitted by the terminal include this information, allowing access network equipment to identify whether the terminal is in flight.

[0147] To enable access and mobility management network elements (such as AMF) to promptly detect the inter-cell movement of connected users, a location report procedure is currently defined. The access and mobility management network elements subscribe to the location movement of terminals from the access network equipment through the location report procedure; when a terminal moves across cells, the access network equipment reports the inter-cell location movement event to the access and mobility management network elements.

[0148] If the access network equipment identifies the terminal as being in flight based on the measurement report, it can provide the terminal's flight status information to the access and mobility management network elements through the LOCATIONREPORT.

[0149] The current LOCATION REPORT does not carry terminal identifiers. Therefore, even when the access and mobility management network element receives information related to the terminal's flight status reported by the access network, the access and mobility management network element cannot determine the terminal's identity information, and thus cannot determine which terminals are in flight status, and therefore cannot notify the USS to monitor terminals in flight status.

[0150] 6. Open RAN (O-RAN or ORAN) architecture

[0151] Figure 5 This is a schematic diagram of an O-RAN architecture for an access network device provided in an embodiment of this application, as shown below. Figure 5 As shown, the core network and the terminal communicate through access network equipment in the O-RAN architecture, which includes: open central unit (O-CU), open distributed unit (O-DU), and open radio unit (O-RU).

[0152] The O-CU is responsible for handling the protocols of the control plane, including managing the Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and Radio Resource Control (RRC) protocol entities.

[0153] The O-DU has baseband processing capabilities and complete protocol layer functions, primarily responsible for higher-level protocol functions such as data encryption and integrity protection. It also has physical layer high-level processing capabilities.

[0154] The O-RU has physical layer low-level signal processing capabilities and is mainly responsible for the transmission and reception of radio frequency signals.

[0155] The following is a detailed description of the solutions provided in the embodiments of this application. Before introducing the embodiments of this application, the following points should be noted.

[0156] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0157] In the description of this application, A sending a message to B can be understood as A sending a message to B through one or more network elements.

[0158] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b and / or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0159] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0160] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0161] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0162] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0163] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0164] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application.

[0165] The technical solutions of this application embodiment can be used in various communication systems, including 3GPP communication systems such as 4th generation (4G) systems (e.g., Long Term Evolution (LTE) systems), 5th generation (5G) systems (e.g., New Radio (NR) systems), LTE and 5G hybrid networking systems, integrated communication and sensing systems, non-terrestrial networks (NTN), device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-type communication (MTC) systems, Internet of Things (IoT) systems, or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.

[0166] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0167] Figure 6 This is a schematic diagram illustrating one possible, non-limiting system. For example... Figure 6 As shown, the communication system includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (e.g., Figure 6 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 6 RAN100, denoted as RAN100, comprises RAN nodes 120a-120j, collectively referred to as RAN120. RAN100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 6 (Not shown in the image). Terminal 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network node in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0168] In one possible implementation, a core network node can refer to a device in the core network 200 that provides service support to terminal 120. In this embodiment, the core network node in the core network 200 includes sensing function (SF) network elements. SF network elements are mainly used to implement sensing functions, which may include sensing control functions and / or sensing computing functions. For example, an SF network element may sometimes be referred to as a communication device; for instance, an SF network element can be understood as a communication device with core network sensing functions. Furthermore, an SF network element may also be referred to as a sensing server, etc., without limitation. In one possible scenario, the function of the SF network element can be implemented by a network data analytics function (NWDAF) network element, or the SF network element and the NWDAF network element can be co-located.

[0169] Taking the core network of a 5G system as an example, the core network of a 5G system can include: Network Slice Selection Function (NSSF), Network Exposure Function (NEF) network elements, Network Data Repository Function (NRF) network elements, Policy Control Function (PCF) network elements, Unified Data Management (UDM) network elements, Application Function (AF) network elements, Authentication Server Function (AUSF) network elements, Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, and UPF network elements. For ease of description, AMF network elements, SMF network elements, UDM network elements, UPF network elements, and PCF network elements will be referred to as AMF, SMF, UDM, UPF, and PCF, respectively, in the following text.

[0170] Among them, NSSF is responsible for selecting the network slice used by user services.

[0171] NRF is responsible for the registration, discovery, and selection of network functions.

[0172] NEF is used to provide frameworks, authentication and interfaces related to network capability exposure, and to pass information between 5G system network functions and other network functions, such as exposing 5G network capabilities to external systems.

[0173] PCF is used to generate and manage user, session, and QoS processing policies; it also provides policies such as QoS policies and slice selection policies to AMF and SMF.

[0174] UDM is used to store and manage subscription information. For example, it is used to process 3GPP authentication and key agreement (AKA) credentials, user identification, access authorization, registration / mobility management, subscription management, SMS management, etc.

[0175] An Application Element (AF) is a functional network element used to provide various service operations. It can interact with the core network through Network Capability Opening (NEF) and with the policy management framework for policy management. An AF can be an application server, belonging to the operator or a third party. It primarily supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0176] AUSF is responsible for authenticating users' 3GPP and non-3GPP access.

[0177] AMF is mainly used for access management functions and is responsible for signaling processing, such as terminal registration management, terminal connection management, terminal reachability management, terminal access authorization and authentication, terminal security functions, terminal mobility management (such as terminal location update, terminal network registration, terminal handover, etc.), network slice selection, SMF selection, and terminal registration or deregistration.

[0178] SMF (Service Flow Framework) is used to create and delete user PDU sessions, and maintain PDU session context and user plane forwarding pipeline information. It can also be used to implement control plane functions for terminal session management, including UPF selection, control, and redirection; Internet Protocol (IP) address allocation and management; session QoS management; obtaining policy and charging control (PCC) policies from the PCF; and establishing, modifying, and releasing bearers or sessions.

[0179] The User-Defined Processing (UPP) is primarily responsible for packet forwarding, QoS control, and billing information statistics. When serving as the anchor point for a PDU session connection, it handles terminal data packet filtering, data transmission / forwarding, rate control, billing information generation, user plane QoS processing, uplink authentication, transmission class verification, downlink packet buffering, and downlink data notification triggering. The UPF can also serve as a branch point for multi-homed PDU sessions. The transmission resources and scheduling functions providing services to the terminal within the UPF are managed and controlled by the Service-Defined Processing (SMF).

[0180] A Radio Access Network (RAN) is a network composed of one or more access network devices (also known as RAN nodes or network devices). It implements radio physical layer functions, resource scheduling and radio resource management, radio access control and mobility management, quality of service management, data compression and encryption, and other functions. Access network devices are connected to the User Plane Interface (N3) and the User Platform Function (UPF) for transmitting terminal data. Access network devices establish control plane signaling connections with the Access Provider Interface (AMF) through the Control Plane Interface (N2) for implementing radio access bearer control and other functions.

[0181] DN refers to a network entity used to provide data services.

[0182] As an example, the connection relationships of the above network element functional entities are as follows: The terminal connects to the AMF via the N1 interface. The (R)AN connects to the AMF via the N2 interface. The (R)AN connects to the UPF via the N3 interface. The UPF connects to the SMF via the N4 interface. The UPF connects to the DN via the N6 interface.

[0183] The service-oriented architecture employs an IT-based bus: AMF connects to the bus via the service-based interface Namf. AUSF connects to the bus via the service-based interface Nausf. SMF connects to the bus via the service-based interface Nsmf. NSSF connects to the bus via the service-based interface Nnssf. NEF connects to the bus via the service-based interface Nnef. NRF connects to the bus via the service-based interface Nnrf. PCF connects to the bus via the service-based interface Npcf. UDM connects to the bus via the service-based interface Nudm. AF connects to the bus via the service-based interface Naf.

[0184] As another example, the functions of the N1, N2, N3, and N4 interfaces are as follows: The N1 interface is the interface between the UE (User Equipment) and the core network control plane, used for transmitting NAS signaling. The N2 interface is the communication interface between the access network element (AN) and the core network control plane. The N3 interface is the communication interface between the access network element (AN) and the core network user plane element (UPF), used for transmitting user data. The N4 interface is the communication interface between the control plane session management element (SMF) and the user plane element (UPF), used for policy configuration of the UPF, etc.

[0185] In one possible implementation, RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as a 4G, 5G mobile communication system, or a future-oriented evolution system. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), an NTN network (such as an NTN supporting pass-through mode and / or regenerative mode, or an NTN supporting eye-viewing mode (earth fixed cell) and / or non-eye-viewing mode (earth moving cell), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0186] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and assists terminals in achieving wireless access. Multiple RAN nodes 110 in RAN 100 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative, for example... Figure 6 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices, for example... Figure 6 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.

[0187] For RAN node 110, in one possible scenario, RAN node 110 can be a base station, an evolved NodeB (eNodeB, also known as eNB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a future communication base station in a future mobile communication system, or an access node in a WiFi system, etc. RAN node 110 can also be a macro base station (such as...) Figure 6 110a), micro base stations or indoor stations (such as Figure 6 The network equipment can be a relay node or donor node, or a wireless controller in a CRAN scenario. Examples include: satellite base stations, radio network controllers (RNCs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs, or home NodeBs, HNBs), relay stations, balloon stations, drone stations, wireless backhaul nodes, or grant nodes (G nodes) in satellite telemetry. It is understood that network equipment can be ground-based or non-ground-based (e.g., satellites, drones, high-altitude communication equipment). Furthermore, the names of network equipment with base station functions may differ in communication systems employing different wireless access technologies; this application does not limit this. Optionally, RAN node 110 can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). RAN node 110 is also known as the next generation-RAN (NG-RAN) node.

[0188] In another possible scenario, multiple RAN nodes 110 collaborate to assist the terminal in achieving wireless access, with each RAN node 110 implementing a portion of the base station's functions. For example, a RAN node 110 can be a CU, DU, CU-CP, CU-user plane (UP), or radio unit (RU), etc. CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0189] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0190] In one possible scenario, terminal 120 can be a device used to implement wireless communication functions, such as a terminal, a chip or circuit that can be used in the terminal, or an entity associated with the terminal. Specifically, terminal 120 can be user equipment (UE), access terminal, terminal unit, terminal station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, wireless communication equipment, terminal agent or terminal device, subscriber unit, smartphone, wireless data card, tablet computer, wireless modem, laptop computer, machine type communication (MTC) terminal, tag, etc., in a 5G network or a future evolved public land mobile network (PLMN). The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handset with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device or wearable device, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, or terminal node (T-node) in StarSpark, etc. In one possible implementation, terminal 120 can be mobile or fixed. It is understood that the terminal and the mobile user can be completely independent. All user-related information can be stored in a subscriber identity module (SIM) card, which can be used on the terminal device. The terminal can then interact with network-side devices by sending and / or receiving signals over the air interface.

[0191] The chip or circuit in the terminal includes components inside the terminal, such as at least one of a chip, a central processing unit (CPU), a network processing unit (NPU), and a terminal radio frequency module.

[0192] Entities associated with the terminal include terminal-side servers, computing / processing nodes, computing / processing entities, computing / processing units, and servers such as over-the-top (OTT) servers. OTT refers to various services provided to users by a third party other than the network operator via the operator's network. Examples of OTT services include OTT voice communication services, OTT multimedia services, and OTT data processing services. The terminal interacts with relevant information (e.g., data) through communication with this associated network entity. For example, this associated network entity and the terminal may belong to the same vendor. Since model training, model selection, etc., may not be executed on the terminal but rather on the terminal-side OTT server, the term "terminal" in this embodiment also includes the terminal-side OTT server.

[0193] It should be understood that the terminal in this embodiment may also be referred to as the "UE side" or the "UE part".

[0194] In one possible implementation, the network device (e.g., access node or core network node) and the terminal in this embodiment can also be referred to as communication devices. These devices can be general-purpose or dedicated devices. The network device may include an access node (RAN node), an operation administration and maintenance (OAM) device, or a core network node. For the OAM device, it may include devices in the element management system (EMS) or the network management system (NMS). It should be understood that the network device in this embodiment can also be referred to as a "network side" or a "network part." This embodiment does not specifically limit its use in this regard.

[0195] In one possible implementation, the relevant functions of the terminal or network device in this application embodiment can be implemented by one device, multiple devices working together, or one or more functional modules within a single device. This application embodiment does not specifically limit this. It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0196] It should be noted that a RAN node can be a device or a component within a device in the aforementioned NG-RAN, such as an ng-eNB node, a gNB node, or a transmission point (TP), transmission and reception point (TRP) within an ng-eNB node and a gNB node, or a central unit (CU) integrated into the NG-RAN. A RAN node can also be a network element with transmission capabilities, such as a transmission measurement function (TMF) network element. In some embodiments, a RAN node can also be an access node in an O-RAN system. A RAN typically consists of a series of modules, such as antennas, RRUs, and BBUs. Traditional RAN architectures define the overall reception and output of a RAN node but do not restrict the transmission and communication between internal modules. O-RAN architectures define the architectural connections and standardized interfaces between various modules within the RAN, allowing the RAN to be decoupled into multiple standard modules, thereby enabling the combination and replacement of modules.

[0197] For example, such as Figure 7The diagram illustrates a possible, non-limiting O-RAN system architecture. The Service Management and Orchestration Framework (SMO), as the network management device in the O-RAN, is used for the operation and management of devices within the O-RAN. The Non-Real-Time RAN Intelligent Controller (Non-RT RIC), located within the SMO module, implements non-real-time intelligent management of RAN functions, such as AI / ML workflows including model training and updates, and guides applications / functions within the Near-RT RIC based on policies. The Near-Real-Time RAN Intelligent Controller (Near-RT RIC) enables near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, it achieves near-real-time control and optimization of O-RAN modules and resources.

[0198] The O-RAN central unit (O-CU) comprises the O-RAN central unit control plane (O-CU-CP) and the O-RAN central unit user plane (O-CU-UP). The O-CU implements the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the service data adaptation protocol (SDAP) layer, and other control functions. Specifically, the O-CU-CP implements the RRC layer functions and the PDCP control plane functions. The O-CU-UP implements the SDAP layer functions and the PDCP user plane functions.

[0199] The O-RAN distributed unit (O-DU) is used to implement the radio link control (RLC) layer, media access control (MAC) layer, and higher physical layer (Higher PHY). The higher physical layer functions include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.

[0200] The O-RAN radio unit (O-RU) is used to implement lower physical layer (PHY) functions and radio frequency (RF) functions. These PHY functions include one or more of the following: Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (iFFT), digital beamforming, or extraction and filtering of the physical random access channel (PRACH). In other words, the O-RU possesses functions similar to TRP and RRH RF devices, as well as PHY processing capabilities. Furthermore, the O-RU, O-CU, and O-DU can also be used as a single unit, i.e., the O-eNB / gNB, to implement the aforementioned functions.

[0201] O-RAN cloud (O-Cloud) is a cloud computing platform that includes physical infrastructure nodes for hosting O-RAN functions such as RIC and O-DU. O-Cloud supports software components (such as operating systems, virtual machine monitoring, and container runtimes), management, and orchestration functions.

[0202] In one possible scenario, the O-RAN system also includes a sensing unit (SU). The SU is mainly used to implement sensing-related functions, such as sending sensing signals and / or receiving echo signals of sensing signals, performing corresponding signal processing based on the received echo signals to obtain sensing measurement data, and performing sensing-related processing, etc.

[0203] As one possible implementation, a RAN node may include at least one of CU, DU, SU, and RU. A communication interface exists between CU and SU. A communication interface may or may not exist between SU ​​and DU. If no communication interface exists between SU ​​and DU, SU and DU can communicate through CU.

[0204] In the O-RAN architecture, the module that receives the report of the difference between the twin channel and the measurement channel can be CU, RT RIC, Non-RT RIC, etc. DU is responsible for receiving signals, signal processing, multipath measurement, and channel difference calculation.

[0205] For example, an O-RAN system includes communication interfaces between newly added internal components and other communication interfaces. For instance, the A1 interface serves as the interface between Non-RT RICs and Near-RT RICs, used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RICs can provide policies, enriched information, and ML model updates to Near-RT RICs via the A1 interface, while Near-RT RICs can provide policy feedback to Non-RT RICs via the A1 interface.

[0206] The E2 interface is an open interface between two endpoints used to connect the Near-RT RIC and the RAN node. The RAN node includes the CU and DU in 5G, the O-RAN compatible eNB in ​​4G, and the O-CU (O-CU-CP and / or O-CU-UP) and / or O-DU in O-RAN. The Near-RT RIC can obtain data collection and feedback from the RAN node through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.

[0207] The O1 interface is the interface between the management entity in the SMO and the O-RAN module, used for operation management. This interface enables network management (such as fault management, configuration management, billing management, performance management, and security management, also known as FCAPS management), software management, and file management. The O2 interface is the interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functions.

[0208] The Open Fronthaul (FH) CUS-Plane interface includes a control plane (C-Plane), a user plane (U-Plane), and a synchronization plane (S-Plane). The control plane is used for real-time control between the O-DU and O-RU, such as transmitting beamforming weights from the O-DU to the O-RU or performing power control from the O-DU to the O-RU. The user plane is used to transmit communication data between the DU and RU for access network devices and terminals. The synchronization plane is used by the O-DU to provide clock synchronization to the O-RU. The Open FH M-Plane interface is the management plane interface, used for connection between the O-RU and O-DU, as well as the SMO, enabling management, monitoring, and configuration functions.

[0209] In addition, the NG interface is the interface between RAN nodes (e.g., base stations, CUs, CU-CPs, CU-UPs) and the core network; NG-u is the user plane NG interface; and NG-c is the control plane NG interface. The Xn interface is the interface between NR RAN nodes; Xn-u is the user plane Xn interface; and Xn-c is the control plane Xn interface. The X2 interface is the interface between LTE RAN nodes; X2-u is the user plane X2 interface; and X2-c is the control plane X2 interface. In NR systems, the X2 interface is mainly used in E-UTRA-NR dual connectivity scenarios (E-UTRA-NR dualconnectivity, EN-DC), where the primary base station is an LTE RAN node connected to the LTE core network via the X2 interface. The E1 interface is the interface between CU-CPs and CU-UPs; the F1-C interface is the interface between CU-CPs and DUs; and the F1-U interface is the interface between CU-UPs and DUs.

[0210] The communication method provided in this application can be applied to scenarios where terminals and network devices communicate. For example, as Figure 8 The diagram shown is an architectural schematic of a communication system 80 provided in an embodiment of this application. The communication system 80 includes a network device 801 and a terminal 802. The terminal 802 is a non-UAV terminal.

[0211] The network device 801 is used to acquire the location information of the terminal 802, or the location information and speed information of the terminal, and to identify whether the terminal 802 is in a first state based on the location information of the terminal 802, or the location information and speed information of the terminal. If the terminal 802 is identified as being in the first state, the network device 801 indicates the identifier of the terminal 802 to other network devices.

[0212] In some embodiments, when the terminal 802 is identified as being in a first state, the network device 801 indicates to other network devices that the terminal 802 is in a first state.

[0213] In some other embodiments, the network device 801 may indicate a terminal by means of a first identifier or a second identifier. The first identifier corresponds to the second identifier; the first identifier is used to uniquely identify the terminal within a first preset range; the second identifier is used to uniquely identify the terminal within a second preset range; the second preset range includes the first preset range.

[0214] As an example, the first identifier is used for flight management of terminal 802, and can also be called an anonymous identifier (Anonymous ID); the second identifier is used to uniquely identify terminal 802, for example, the second identifier can be IMSI.

[0215] In some other embodiments, network device 801 can obtain the location information of terminal 802, or the location and speed information of the terminal, through measurement information (such as MDT measurement information or measurement reports) of terminal 802. When network device 801 obtains the location information of terminal 802, or the location and speed information of the terminal, through MDT measurement information, network device 801 can be a network element in the core network (NWDAF network element) or a UAS network element; when network device 801 obtains the location information of terminal 802, or the location and speed information of the terminal, through measurement reports, network device 801 can be an access network device. This application does not limit this.

[0216] In some embodiments, the measurement information of terminal 802 includes an anonymous identifier of terminal 802. Network device 801 determines whether terminal 802 is in a first state using the anonymous identifier of terminal 802. If it is determined that terminal 802 is in the first state, network device 801 can query the unique identifier corresponding to the anonymous identifier of terminal 802 from a unified data management network element (such as a UDM network element) and send the unique identifier of terminal 802 to the device used to manage the flight terminal, so that the device used to manage the flight terminal can manage terminal 802 based on the unique identifier of terminal 802.

[0217] In one possible implementation, Figure 9 This is a schematic diagram illustrating the composition of a communication device 900 provided in an embodiment of this application. Figure 6 The network devices and terminals shown can all be used Figure 9 The shown composition structure, or including Figure 9 The component shown; or, Figure 6 The components (e.g., chips) in the network devices and terminals shown can all be adopted. Figure 9 The shown composition structure, or including Figure 9 The components are shown. It is understood that the communication device 900 includes necessary MAEns such as modules, units, elements, circuits, or interfaces, to be appropriately configured together to perform this solution.

[0218] like Figure 9 As shown, the communication device 900 includes one or more processors 91. The processors 91 are used to implement the processing and determination processes performed by the various devices in the following embodiments. The processor 91 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., a RAN node, terminal, or chip), execute software programs, and process data from the software programs.

[0219] Optionally, in one design, the processor 91 may include a program 93 (sometimes referred to as code or instructions) that can be run on the processor 91 to cause the communication device 900 to perform the methods described in the following embodiments.

[0220] Optionally, the communication device 900 may include one or more memories 92 storing a program 94 (sometimes referred to as code or instructions) that can be run on the processor 91 to cause the communication device 900 to perform the methods described in the following method embodiments.

[0221] Optionally, the processor 91 and / or memory 92 may include an artificial intelligence (AI) module 97 and an AI module 98, which are used to implement AI-related functions. These AI modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include an intelligent controller (RIC) module. For instance, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0222] Optionally, the processor 91 and / or memory 92 may also store data. The processor and memory may be configured separately or integrated together.

[0223] Optionally, the communication device 900 may further include a transceiver 95, which is used to implement the transmission and reception processes performed by the various devices in the following embodiments. The processor 91, sometimes referred to as a processing unit, controls the communication device (e.g., a RAN node or terminal). The transceiver 95, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, etc., may also include an antenna 96 in the communication device 900.

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

[0225] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0226] Furthermore, the actions, terms, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages between the various devices in the embodiments of this application are merely examples, and other names may be used in specific implementations without limitation.

[0227] The following is combined with Figures 1 to 9 The communication method provided in the embodiments of this application will be described.

[0228] It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between network elements are just examples. Other names may also be used in other embodiments. The communication method provided in this application does not specifically limit these names.

[0229] It is understood that in the embodiments of this application, each network element may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application.

[0230] It is understood that this application uses terminals and network devices as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the terminal in this application can also be executed by a module applied to the terminal (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the terminal's functions; similarly, the method executed by the network device in this application can also be executed by a module applied to the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the network device's functions. This application does not specifically limit these aspects.

[0231] The following is combined with Figure 10 The embodiments provided in this application Figure 8 The functions and actions performed by each device in the illustrated communication system are described. Figure 10 This is a flowchart illustrating a communication method provided in an embodiment of this application. In this embodiment, a network device acquires information to determine that a terminal is in a first state and indicates to a first network element the terminal's first identifier and the terminal's first state, thereby enabling the first network element to manage the terminal. The functions and actions performed by each device in the communication system provided in this embodiment are described below, such as... Figure 10 As shown, the communication method includes the following steps:

[0232] Step 1001: The network device receives the first information.

[0233] The first information is used to determine that the terminal is in the first state.

[0234] In some embodiments, the first information is first information sent by the network data analysis network element; or, the first information is first information sent by the operation and maintenance management network element; wherein the functions of the operation and maintenance management network element include fault management, performance monitoring, and service assurance. In other words, the network device receives the first information from the network data analysis network element. Or, the network device receives the first information from the operation and maintenance management network element.

[0235] As one implementation method, the terminal initiates a measurement (e.g., the terminal initiates an MDT measurement, or the terminal initiates a measurement of the measurement signal) and reports the measurement results. The network device obtains the measurement results and determines the first information.

[0236] As an example, the network data analysis element can specifically be an NWDAF element; the operation, maintenance and management element can be an OAM element.

[0237] Step 1002: The network device sends the second information to the first network element. Correspondingly, the first network receives the second information from the network device.

[0238] The second information includes the terminal's first identifier and first indication information; the first indication information is used to indicate that the terminal is in a first state; the first network element includes the function of managing the terminal.

[0239] In one implementation, after receiving the first information, the network device determines that the terminal is in a first state based on the first information. Then, the network device sends the terminal's identifier to the first network element and indicates that the terminal is in the first state, so that the first network element can manage the terminal based on the terminal's first state and the terminal's identifier.

[0240] In some embodiments, the first information includes a second identifier of the terminal and first indication information; the second identifier corresponds to the first identifier. Thus, after receiving the first information, the network device can convert the second identifier in the first information into a first identifier that the first network element can recognize, thereby enabling the first network element to correctly identify the terminal to be managed.

[0241] In some embodiments, the first identifier is a unique identifier for the terminal. The second identifier is used to identify the terminal within the management scope of the first network element. Network devices can indicate the terminal using either the second or the first identifier. This allows different identifiers to be used to indicate the terminal to other network devices in different scenarios. For example, the second identifier can be used to uniquely identify the terminal within a first preset scope; or the first identifier can be used to uniquely identify the terminal within a second preset scope, where the second preset scope includes the first preset scope. Thus, network devices can indicate the terminal using the appropriate identifier based on the applicable scope of the different identifiers for the terminal, in scenarios corresponding to the applicable scope of the identifier. For example, the second identifier may be applicable to the operator network (i.e., the first preset scope is the operator network), used to uniquely identify the terminal within the operator network; the first identifier may be applicable to any scenario (i.e., the second preset scope is an unrestricted scope), used to uniquely identify the terminal globally. Then, network devices can use the second identifier to represent the terminal when communicating within the operator network. When network devices interact with network elements in other networks, they use the first identifier to represent the terminal.

[0242] As an example, the second identifier is an anonymous identifier (Anonymous ID); the first identifier is the IMSI. This allows the terminal to communicate within the network using the anonymous identifier, preventing the terminal's unique IMSI from being leaked during transmission and improving IMSI privacy and security. Furthermore, the network device can also indicate the terminal's first identifier (i.e., IMSI) to the USS, enabling the USS to manage the terminal based on its IMSI. Since the USS is not a network element in the current core network, it may not be able to recognize the identifier of the terminal used in the communication network (such as the second identifier mentioned above). Therefore, the network device indicates the terminal's IMSI to the USS. The IMSI is a globally unique identifier for the terminal, allowing the USS to identify the terminal based on it and thus perform flight management.

[0243] As an example, the network device is a UAS network element, and the first network element is a USS network element. In this scenario, the UAS receives the first information and determines that the terminal is in flight mode based on the first information. The UAS indicates the terminal's IMSI and relevant parameters when the terminal is in flight mode to the USS. The USS manages the terminal based on the terminal's IMSI and relevant parameters when the terminal is in flight mode.

[0244] In this embodiment, after receiving first information to determine that a terminal is in a state requiring management, the network device sends the terminal's first identifier to the first network element managing the terminal, indicating that the terminal is in a state requiring management. Thus, for terminals requiring management, the UAV management system can report this to the first network element managing that terminal, enabling the first network element to manage the terminal. This solves the technical problem in related technologies of lacking the ability to manage all aerial devices.

[0245] In some embodiments, combined with Figure 10 ,like Figure 11 As shown, before the network device sends the second information to the first network element in step 1002, the method further includes:

[0246] Step 1101: The network device determines that the terminal is in the first state based on the first indication information in the first information.

[0247] In one implementation, the network device parses the first indication information to determine whether the terminal is in the first state. If the terminal is in the first state, the network device sends the terminal's first identifier to the first network element and indicates that the terminal is in the first state.

[0248] As another implementation, the first indication information is also used to indicate the terminal's location information, or the terminal's location information and speed information. In this scenario, the network device determines whether the terminal is in the first state based on the terminal's location information or the terminal's location information and speed information. If the terminal is in the first state, the network device sends the terminal's first identifier to the first network element and indicates that the terminal is in the first state.

[0249] Optionally, the terminal's location information includes at least one of the following: longitude, latitude, and altitude information of the terminal at at least one moment. The terminal's speed information includes at least one of the following: speed direction, vertical speed, and horizontal speed of the terminal at at least one moment.

[0250] Optionally, the first state satisfies at least one of the following: the terminal's altitude is greater than a first threshold; or, the terminal's altitude is greater than the first threshold, and the terminal's speed is greater than a second threshold. In other words, the first state can also be understood as a flight state; the terminal being in the first state means that the terminal is in a flight state, and the terminal is an airborne device at this time.

[0251] In one implementation, the network device determines whether the terminal's altitude is higher than a first altitude threshold based on at least one altitude information of the terminal; if the terminal's altitude is higher than the first altitude threshold, the network device determines that the terminal is in flight mode.

[0252] Alternatively, the network device determines whether the terminal's altitude is higher than a first altitude threshold based on the terminal's altitude information at least at one moment; and determines whether the terminal's speed is greater than a first speed threshold based on the terminal's speed direction, vertical speed, and horizontal speed at at least at one moment. If the terminal's altitude is higher than the first altitude threshold and the terminal's speed is greater than the first speed threshold, the network device determines that the terminal is in flight mode.

[0253] In some implementations, before the network device identifies whether the terminal is in the first state, the network device acquires a first height threshold and / or a first speed threshold. Afterward, the network device uses the first height threshold and / or the first speed threshold, along with the terminal's location information, or the terminal's location information and speed information, to identify whether the terminal is in the first state.

[0254] As one implementation, before the network device sends the terminal's first identifier to the first network element, the network device can query the first identifier corresponding to the second identifier from the unified data management network element, and then send the first identifier retrieved from the unified data management to the first network element. For example... Figure 11 As shown, the process by which a network device queries the first identifier corresponding to the second identifier from the unified data management can be specifically implemented through the following steps 1102 and 1103.

[0255] Step 1102: The network device sends a first request message to the unified data management network element. Correspondingly, the unified data management network element receives the first request message from the network device.

[0256] The first request message is used to request a query for the first identifier corresponding to the second identifier of the terminal;

[0257] Step 1103: The unified data management network element sends a first response message to the network device. Correspondingly, the network device receives the first response message from the unified data management network element.

[0258] The first response message includes a first identifier.

[0259] In some embodiments, the network device can pre-subscribe to the terminal's location information, or the terminal's location and speed information, from the operation and maintenance management network element; thus, after the operation and maintenance management network element obtains the terminal's location information, or the terminal's location and speed information, it can proactively send the terminal's location information, or the terminal's location and speed information, to the network device. For example... Figure 11 As shown, prior to step 1101 above, the method further includes:

[0260] Step 1104: The network device sends a first subscription message to the operation and maintenance management network element. Correspondingly, the operation and maintenance management network element receives the first subscription message from the network device.

[0261] The first subscription message is used to request the location information of the terminal to subscribe, or the location information and speed information of the terminal.

[0262] Step 1105: The operation and maintenance management network element sends a first subscription response message to the network device. Correspondingly, the network device receives the first subscription response message from the operation and maintenance management network element.

[0263] The first subscription response message indicates whether the subscription to the terminal's location information, or the terminal's location and speed information, was successful.

[0264] In some embodiments, the network device obtains measurement results differently depending on whether the terminal supports MDT measurement and whether a network data analysis element exists in the core network corresponding to the terminal. For example, in a scenario where the terminal supports MDT measurement and a network data analysis element exists in the core network (referred to as Scenario 1), the network device obtains the measurement results reported by the terminal from the network data analysis element; in a scenario where the terminal supports MDT measurement and no network data analysis element exists in the core network (referred to as Scenario 2), the network device obtains the measurement results reported by the terminal from the operation, maintenance, and management element; and in a scenario where the terminal does not support MDT measurement (referred to as Scenario 3), the network device obtains the measurement results reported by the terminal from the access network device.

[0265] Scenario 1: The terminal supports MDT measurement, and there is a network data analysis element in the core network.

[0266] In this scenario, the network data analysis element obtains the terminal's location information, or the terminal's location and speed information, from the operation, maintenance, and management element, and determines whether the terminal is in the first state. If the terminal is in the first state, it sends the first information to the network device.

[0267] Combination Figure 10 ,like Figure 12 As shown, step 1001 above, in which the network device receives the first information, specifically includes:

[0268] Step 1201: The operation and maintenance management network element sends third information to the network data analysis network element. Correspondingly, the network data analysis network element receives the third information from the operation and maintenance management network element.

[0269] The third type of information includes the terminal's location information, or the terminal's location information and speed information.

[0270] As an example, the third piece of information is the terminal's minimum drive test (MDT) measurement data, which includes the terminal's location information, or the terminal's location information and speed information. In other words, the terminal performs MDT measurements to determine its location information, or its location information and speed information, and reports the MDT measurement results to the operation and maintenance management network element. The MDT measurement results include the terminal's location information, or its location information and speed information. The operation and maintenance management network element sends the terminal's location information, or its location information and speed information, to the network device; the network device receives the terminal's location information, or its location information and speed information, from the operation and maintenance management network element.

[0271] As one implementation method, before the terminal performs MDT measurements, the AMF and access network equipment select the terminal to perform the MDT measurements and configure the MDT measurement configuration parameters. The process by which the AMF and access network equipment select the terminal to perform the MDT measurements can be understood by referring to the relevant technologies on management-based MDT measurements and signaling-based MDT measurements, and will not be elaborated here.

[0272] In some embodiments, the third information includes a second identifier of the terminal. Thus, the first network element can determine that the third information is terminal information based on the second identifier in the third information, and further determine the terminal's location information, or the terminal's location information and speed information, based on the third information.

[0273] Optionally, prior to step 1201, the network data analysis network element may pre-subscribe to the terminal's location information, or the terminal's location and speed information, from the operation and maintenance management network element. The specific process is similar to the process in steps 1104 and 1105 above where the network device subscribes to the terminal's location information from the operation and maintenance management network element; this application does not limit this process.

[0274] Step 1202: The network data analysis element sends the first information to the network device. Correspondingly, the network device receives the first information from the network data analysis element.

[0275] The first information is used to determine that the terminal is in the first state.

[0276] In some embodiments, the network data analysis element determines whether the terminal is in a first state based on the terminal's location information, or the terminal's location information and speed information. If the terminal is in the first state, the network data analysis element sends first information to the network device.

[0277] Scenario 2: The terminal supports MDT measurement, and there is no network data analysis element in the core network.

[0278] In scenario 2, network devices obtain measurement results reported by terminals from operation, maintenance, and management network elements; combined with... Figure 11 In step 1001 above, the network device receives the first information, specifically including:

[0279] Step 1106: The operation and maintenance management network element sends the first information to the network device. Correspondingly, the network device receives the first information from the operation and maintenance management network element.

[0280] Optionally, prior to step 1301, the network device may pre-subscribe to the terminal's location information from the operation and maintenance management network element through steps 1104 and 1105 above; this application does not limit this.

[0281] Scenario 3: The terminal does not support MDT measurement.

[0282] In scenario 3, the network device obtains the measurement results reported by the terminal from the access network device. Combined with... Figure 10 ,like Figure 13 As shown, the process specifically includes:

[0283] Step 1301: The terminal sends the fourth information to the access network device. Correspondingly, the access network device receives the fourth information from the terminal.

[0284] The fourth piece of information includes the terminal's second identifier and the first instruction information.

[0285] Step 1302: The access network device sends the first information to the network device. Correspondingly, the network device receives the first information from the access network device.

[0286] In one implementation, the terminal measures the measurement signal sent by the network device to obtain a measurement report. The measurement report includes the terminal's measured location information, or the terminal's location information and speed information. The terminal sends the measurement report to the network device. The network device obtains the terminal's second identifier and location information, or the terminal's location information and speed information, from the measurement report, and then determines the aforementioned first information based on the terminal's second identifier and location information, or the terminal's location information and speed information.

[0287] In some embodiments, the access network device sends first information to the network device through an access and mobility management network element. In other words, the access network device sends first information to the access and mobility management network element. The access and mobility management network element receives the first information from the access network device. The access and mobility management network element sends the first information to the network device. Correspondingly, the network device receives the first information from the access and mobility management network element.

[0288] It should be noted that, when the terminal supports MDT measurement, the fourth information is carried in the minimum drive test measurement data. In this case, the terminal sends its location information, or its location and speed information, to the access network device using the minimum drive test measurement data. The access network device sends the terminal's location information, or its location and speed information, to the operation and maintenance management network element, and the network device obtains the terminal's location information, or its location and speed information, from the operation and maintenance management network element according to the method described in scenario 1 or scenario 2 above. When the terminal does not support MDT measurement, the fourth information is carried in the measurement report. In this case, the terminal sends its location information, or its location and speed information, to the access network device using the measurement report. The access network device identifies that the terminal is in the first state based on the terminal's location information, or its location and speed information, generates the first information, and sends the first information to the network device.

[0289] In one possible implementation, before identifying whether the terminal is in the first state in this embodiment, a second identifier can be pre-assigned to the terminal, so that the terminal's location information, or the terminal's location information and speed information, can be transmitted over the air interface based on the second identifier. This avoids leaking the terminal's first identifier during air interface transmission. Figure 14 As shown, the process of assigning a second identifier to a terminal specifically includes:

[0290] Step 1401: The access and mobility management network element sends a second request message to the unified data management network element. Correspondingly, the unified data management network element receives the second request information from the access and mobility management network element.

[0291] The second request message is used to request the allocation of a second identifier for the terminal.

[0292] As one possible implementation, the access and mobility management network element sends a second request message to the unified data management network element during the initial access procedure (such as the initial context establishment procedure) to request the allocation of a second identifier for the terminal.

[0293] Step 1402: The unified data management network element sends a second response message to the access and mobility management network element. Correspondingly, the access and mobility management network element receives the second response message from the unified data management network element.

[0294] The second response message includes a second identifier assigned to the terminal.

[0295] Step 1403: The access and mobility management network element sends a second identifier to the access network device. Correspondingly, the access network device receives the second identifier from the access and mobility management network element.

[0296] Step 1404: The access network device sends a second identifier to the terminal. Correspondingly, the terminal receives the second identifier from the access network device.

[0297] In some embodiments, after receiving the second identifier, the terminal adds the second identifier to the measurement result (such as MDT measurement data or a measurement report) to indicate that the measurement result is a measurement process performed by the terminal. The terminal then sends the measurement result with the added second identifier to the access network device.

[0298] The communication method provided in the embodiments of this application has been described in detail above.

[0299] by Figure 8The communication system shown is applied to a 5G network. Taking the AMF (Access and Mobility Management) network element, OAM (Operation and Maintenance Management) network element, NWDAF (Network Data Analysis Function) network element, UDM (Unified Data Management) network element, USA (Unmanned Aerial Vehicle System) network element, and USS (USA Service Provider) network element as an example, the communication method provided in the embodiments of this application will be described in detail.

[0300] The following will describe the communication method provided in this application embodiment from the perspective of interaction between various network elements, combined with specific scenarios. The following will provide a detailed description of scenarios 4-6: Scenario 4: The terminal supports the MDT measurement process, and the network includes NWDAF network elements; Scenario 5: The terminal supports the MDT measurement process, but the network does not include NWDAF network elements; Scenario 6: The terminal does not support the MDT measurement process.

[0301] Scenario 4: The terminal supports the MDT measurement process, and the network includes NWDAF network elements.

[0302] When the terminal supports the MDT (Multi-Target Measurement) procedure, the terminal's location information, or its location and speed information, can be obtained based on the MDT procedure to identify whether the terminal is a flight terminal. In this scenario, if the network includes NWDAF (Non-Wide-Driving AF) elements, these elements can identify whether the terminal is a flight terminal based on its location information and / or speed. Figure 15 As shown, when the terminal supports the MDT measurement procedure and the network includes NWDAF network elements, the process of identifying whether the terminal is a flight terminal includes one or more of the following steps:

[0303] Step 1501: The AMF sends a second identification request message to the UDM. Correspondingly, the UDM receives the second identification request message from the AMF.

[0304] The second identifier request message is used to request the UDM to assign a second identifier to the terminal. Optionally, the second identifier is used to identify whether the terminal is in the first state.

[0305] In some embodiments, after the RRC connection is established, the terminal sends an RRCSetupComplete message to the access network device. The access network device selects the AMF and sends the NAS message carried in the RRCSetupComplete message to the AMF via the INITIAL UE MESSAGE, triggering the initial context establishment procedure. During the initial context establishment procedure, the AMF sends a second identifier request message to the UDM, requesting the UDM to allocate a second identifier for the terminal.

[0306] As an example, the second identifier is an anonymous identifier (Anonymous ID); the second identifier request message is: Anonymous ID Request.

[0307] Step 1502: UDM assigns a second identifier to the terminal.

[0308] In some implementations, the UDM assigns an Anonymous ID to the terminal based on the second identifier request message. In addition, the UDM obtains the terminal's first identifier (i.e., IMSI). The UDM establishes the mapping between the terminal's Anonymous ID and IMSI.

[0309] Step 1503: UDM sends the second identifier to AMF. Correspondingly, AMF receives the second identifier from UDM.

[0310] In some implementations, the UDM sends the Anonymous ID assigned to the terminal to the AMF. This allows for subsequent identification of whether the terminal is in the first state based on the Anonymous ID.

[0311] Step 1504: The AMF, access network devices, and terminals perform IDENTITY query, authentication, NAS security mode, and registration processes, and report the MDT subscription information to the AMF.

[0312] In some implementations, the AMF and the terminal perform IDENTITY queries, authentication, NAS security mode settings, and registration. The access network device transparently transmits the relevant messages for IDENTITY queries, authentication, NAS security mode settings, and registration between the AMF and the terminal. During this process, the AMF sends the Anonymous ID assigned to the terminal so that the terminal can perform MDT measurements based on the Anonymous ID during subsequent MDT measurements.

[0313] Step 1505: The AMF sends MDT (Multi-Level Device) Subscriber Indication Information to the access network equipment. Correspondingly, the access network equipment receives the MDT Subscriber Indication Information from the AMF.

[0314] Optionally, the MDT subscriber indication information is used to indicate whether the terminal is an MDT subscriber.

[0315] As an example, the MDT subscriber indication information is carried in the INITIAL CONTEXT SETUP REQUEST message. The AMF uses the INITIAL CONTEXT SETUP REQUEST message to indicate to the access network equipment whether the terminal is an MDT subscriber.

[0316] Optionally, the AMF can indicate to the access network equipment whether multiple terminals are MDT subscribers.

[0317] After the AMF indicates the MDT subscribed users to the access network equipment, relevant personnel can subscribe to MDT measurement events through the MAE. The MAE determines the MDT subscription event based on the configuration operations of the relevant personnel and sends the subscription message for the MDT measurement event to the access network equipment. Since the terminals selected in the management-based MDT measurement process and the signaling-based MDT measurement process are different, the following explanations are provided for different scenarios:

[0318] Scenario 1: Management-based MDT measurement

[0319] In Scenario 1, it is necessary to perform MDT measurements on all MDT-subscribed users within a specified range (such as Cell ID, TA, etc.). Scenario 1 can be applied to scenarios where there are multiple unknown non-UAV terminals within the target area, all of which may be in the first state of flight, and these unknown non-UAV terminals need to be identified and monitored individually while they are flying in the air.

[0320] The process of selecting a terminal in scenario 1 includes the following steps 1506-1508:

[0321] Step 1506: MAE sends a first MDT subscription command to the access network device. Correspondingly, the access network device receives the first MDT subscription command from MAE.

[0322] The first MDT subscription command is used to instruct all terminals within a specified range to report MDT measurement results.

[0323] Step 1507: Select terminal for access network equipment.

[0324] In some embodiments, the access network device determines the MDT subscribers indicated by the AMF and selects the terminals within the specified range as the terminals that need to report the MDT measurement results.

[0325] Optionally, the terminal is one of the terminals selected by the aforementioned access network equipment.

[0326] Step 1508: The access network device sends MDT configuration information to the selected terminal. Correspondingly, the terminal receives the MDT configuration information from the access network device.

[0327] Optionally, the access network device sends MDT configuration information to each terminal selected in step 1507 above, so that each selected terminal performs MDT measurement and reports the MDT measurement results.

[0328] Case 2: Signaling-based MDT measurement

[0329] In Scenario 2, specific terminals (such as terminals with a specific IMSI) are required for MDT measurements. Scenario 2 can be applied to monitoring whether a known non-UAV terminal is in the first state and to monitoring it when it is. The process for selecting a terminal in Scenario 2 includes the following steps 1509-1510:

[0330] Step 1509: MAE sends a second MDT subscription command to AMF. Correspondingly, AMF receives the second MDT subscription command from MAE.

[0331] The second MDT subscription command is used to instruct a specified terminal to report MDT measurement results. Optionally, the specified terminal may include other terminals.

[0332] Step 1510: AMF sends MDT configuration information to the access network equipment.

[0333] In some embodiments, the AMF sends MDT configuration information to the access network device, instructing the access network device to initiate MDT measurement to a designated terminal.

[0334] Optionally, the terminal is one of the terminals selected by the aforementioned access network equipment.

[0335] Step 1511: The access network device sends MDT configuration information to the designated terminal. Correspondingly, the terminal receives the MDT configuration information from the access network device.

[0336] Optionally, the access network device sends MDT configuration information to each terminal selected in step 1507 above, so that each selected terminal performs MDT measurement and reports the MDT measurement results.

[0337] Step 1512: The terminal performs MDT measurement.

[0338] After selecting a terminal based on the method described in Case 1 or Case 2 above, the terminal performs MDT measurement and reports the MDT measurement results.

[0339] The process of MDT measurement by the terminal can be referred to in the aforementioned related technologies. Figure 2 and Figure 3 The details of that will not be repeated here.

[0340] Step 1513: The terminal reports MDT measurement data to the access network device. The MDT measurement data carries an anonymous identifier (Anonymous ID).

[0341] Step 1514: The access network device reports MDT measurement data to the OAM. The MDT measurement data carries an anonymous identifier (Anonymous ID).

[0342] Step 1515: NWDAF sends the first MDT subscription configuration message to OAM. Correspondingly, OAM receives the first MDT subscription configuration message from NWDAF.

[0343] The first MDT subscription configuration message is used to subscribe to the location information of the terminal's MDT measurement data, or the terminal's location and speed information.

[0344] Step 1516: OAM sends the first MDT subscription response message to NWDAF. Correspondingly, NWDAF receives the first MDT subscription response message from OAM.

[0345] The first MDT subscription response message is used to indicate whether the location information of the terminal's MDT measurement data, or the terminal's location and speed information, has been successfully subscribed.

[0346] Step 1517: OAM prepares MDT measurement data.

[0347] In some embodiments, OAM selects MDT measurement data from multiple terminals. Alternatively, OAM selects MDT measurement data from multiple terminals. The multiple terminals include the terminal itself.

[0348] Step 1518: OAM sends MDT measurement data to NWDAF. Correspondingly, NWDAF receives the MDT measurement data from OAM.

[0349] Step 1519: NWDAF analyzes the received MDT measurement data to identify whether the terminal is in the first state.

[0350] In some embodiments, after receiving the MDT measurement data from the terminal, the NWDAF analyzes the terminal's position and velocity information in the MDT measurement data to determine whether the terminal is currently in a first state. If the NWDAF determines that the terminal is currently in a first state, it continues to execute step 1520; if the NWDAF determines that the terminal is not currently in a first state, it does not continue to execute the following steps.

[0351] Step 1520: The NWDAF sends the first indication information to the UAS. Correspondingly, the UAS receives the first indication information from the NWDAF.

[0352] The first indication information is used to indicate the second identifier of the terminal. Optionally, the first indication information is also used to indicate the flight information of the terminal.

[0353] Step 1521: The UAS sends a first request message to the UDM. Correspondingly, the UDM receives the first request message from the UAS.

[0354] The first request information is used to request the first identifier corresponding to the second identifier. For example, the UAS requests the IMSI of the terminal from the UDM based on the terminal's Anonymous ID.

[0355] Step 1522: UDM sends the first response information to UAS. Correspondingly, UAS receives the first response information from UDM.

[0356] The first response information includes the terminal's first identifier, such as IMSI.

[0357] Step 1523: The UAS sends a second message to the USS. Correspondingly, the USS receives the second message from the UAS.

[0358] The second information is used to indicate the terminal's first identifier, and optionally, the second information is also used to indicate the terminal's flight information.

[0359] After this, the USS can perform flight management on the terminal based on the terminal's IMSI and / or the terminal's flight information.

[0360] Scenario 5: The terminal supports the MDT measurement process, and the network does not include NWDAF network elements.

[0361] When the terminal supports the MDT (Multi-Target Measurement) procedure, the terminal's location information, or its location and speed information, can be obtained based on the MDT procedure to identify whether the terminal is a flight terminal. In this scenario, if the network does not include NWDAF (Non-Wide-Depth Availability Assist) network elements, the UAS (User-Available System) network elements can identify whether the terminal is a flight terminal based on its location information and / or speed. Figure 16 As shown, when the terminal supports the MDT measurement procedure and the network does not include NWDAF network elements, the process of identifying whether the terminal is a flight terminal includes one or more of the following steps:

[0362] Step 1601: The AMF sends a second identification request message to the UDM. Correspondingly, the UDM receives the second identification request message from the AMF.

[0363] The specific implementation of step 1601 can be referred to step 1501 above, and will not be elaborated here.

[0364] Step 1602: UDM assigns a second identifier to the terminal.

[0365] The specific implementation of step 1602 can be referred to step 1502 above, and will not be elaborated here.

[0366] Step 1603: UDM sends the second identifier to AMF. Correspondingly, AMF receives the second identifier from UDM.

[0367] The specific implementation of step 1603 can be referred to step 1503 above, and will not be elaborated here.

[0368] Step 1604: The AMF, access network devices, and terminals perform IDENTITY query, authentication, NAS security mode, and registration processes, and report the MDT subscription information to the AMF.

[0369] The specific implementation of step 1604 can be referred to step 1504 above, and will not be elaborated here.

[0370] Step 1605: The AMF sends MDT (Multi-Level Device) Subscriber Indication Information to the access network equipment. Correspondingly, the access network equipment receives the MDT Subscriber Indication Information from the AMF.

[0371] The specific implementation of step 1605 can be referred to step 1505 above, and will not be elaborated here.

[0372] After the AMF indicates the MDT subscribed users to the access network equipment, relevant personnel can subscribe to MDT measurement events through the MAE. The MAE determines the MDT subscription event based on the configuration operations of the relevant personnel and sends the subscription message for the MDT measurement event to the access network equipment. Since the terminals selected in the management-based MDT measurement process and the signaling-based MDT measurement process are different, the following explanations are provided for different scenarios:

[0373] Scenario 3: Management-based MDT measurement

[0374] In scenario 3, it is necessary to perform MDT measurements on all MDT-subscribed users within a specified range (such as Cell ID, TA, etc.). Scenario 3 can be applied to scenarios where there are multiple unknown non-UAV terminals within the target area, all of which may be in the first state of flight, and these unknown non-UAV terminals need to be identified and monitored individually while they are flying in the air.

[0375] The process for selecting a terminal in scenario 3 includes the following steps 1606-1608:

[0376] Step 1606: MAE sends a first MDT subscription command to the access network device. Correspondingly, the access network device receives the first MDT subscription command from MAE.

[0377] The specific implementation of step 1606 can be referred to step 1506 above, and will not be elaborated here.

[0378] Step 1607: Select terminal for access network equipment.

[0379] The specific implementation of step 1607 can be referred to step 1507 above, and this application will not elaborate on it.

[0380] Step 1608: The access network device sends MDT configuration information to the selected terminal. Correspondingly, the terminal receives the MDT configuration information from the access network device.

[0381] The specific implementation of step 1608 can be referred to step 1508 above, and will not be elaborated here.

[0382] Case 4: Signaling-based MDT measurement

[0383] In scenario 4, specific terminals (such as terminals with a specific IMSI) are required for MDT measurements. Scenario 4 can be applied to monitoring whether a known non-UAV terminal is in the first state and to monitoring it when it is. The process for selecting a terminal in scenario 4 includes the following steps 1609-1610:

[0384] Step 1609: MAE sends a second MDT subscription command to AMF. Correspondingly, AMF receives the second MDT subscription command from MAE.

[0385] The specific implementation of step 1609 can be referred to step 1509 above, and will not be elaborated here.

[0386] Step 1610: AMF sends MDT configuration information to the access network equipment.

[0387] The specific implementation of step 1610 can be referred to step 1510 above, and will not be elaborated here.

[0388] Step 1611: The access network device sends MDT configuration information to the designated terminal. Correspondingly, the terminal receives the MDT configuration information from the access network device.

[0389] The specific implementation of step 1611 can be referred to step 1511 above, and will not be elaborated here.

[0390] Step 1612: The terminal performs MDT measurement.

[0391] After selecting a terminal based on the method described in Case 3 or Case 4 above, the terminal performs MDT measurement and reports the MDT measurement results.

[0392] The specific implementation of step 1612 can be referred to step 1512 above, and will not be elaborated here.

[0393] Step 1613: The terminal reports MDT measurement data to the access network device. The MDT measurement data carries an anonymous identifier (Anonymous ID).

[0394] The specific implementation of step 1613 can be referred to step 1513 above, and will not be elaborated here.

[0395] Step 1614: The access network device reports MDT measurement data to the OAM. The MDT measurement data carries an anonymous identifier (Anonymous ID).

[0396] The specific implementation of step 1614 can be referred to step 1514 above, and will not be elaborated here.

[0397] Step 1615: The UAS sends a second MDT subscription configuration message to the OAM. Correspondingly, the OAM receives the second MDT subscription configuration message from the UAS.

[0398] The second MDT subscription configuration message is used to subscribe to the location information of the terminal's MDT measurement data, or the terminal's location and speed information.

[0399] In some embodiments, since the NWDAF network element is not included in the core network of Scenario 2, the UAS identifies whether the terminal is a flight terminal based on the terminal's location information and / or speed. In this case, the UAS subscribes to the OAM for the terminal's MDT measurement data location information, or the terminal's location information and speed information.

[0400] Step 1616: OAM sends a second MDT subscription response message to UAS. Correspondingly, UAS receives the second MDT subscription response message from OAM.

[0401] The second MDT subscription response message is used to indicate whether the location information of the terminal's MDT measurement data, or the terminal's location and speed information, has been successfully subscribed.

[0402] Step 16-17: OAM prepares MDT measurement data.

[0403] The specific implementation of step 1617 can be referred to step 1517 above, and will not be elaborated here.

[0404] Step 1618: OAM sends MDT measurement data to UAS. Correspondingly, UAS receives the MDT measurement data from OAM.

[0405] Step 1619: The UAS analyzes the received MDT measurement data to identify whether the terminal is in the first state.

[0406] In some embodiments, after receiving the MDT measurement data from the terminal, the UAS analyzes the terminal's position and speed information in the MDT measurement data to determine whether the terminal is currently in a first state. If the UAS determines that the terminal is currently in a first state, it continues to execute step 1620; if the UAS determines that the terminal is not currently in a first state, it does not continue to execute the following steps.

[0407] Step 1620: The UAS sends a first request message to the UDM. Correspondingly, the UDM receives the first request message from the UAS.

[0408] The specific implementation of step 1620 can be referred to step 1521 above, and will not be elaborated here.

[0409] Step 1621: UDM sends the first response information to UAS. Correspondingly, UAS receives the first response information from UDM.

[0410] The specific implementation of step 1621 can be referred to step 1522 above, and will not be elaborated here.

[0411] Step 1622: The UAS sends a second message to the USS. Correspondingly, the USS receives the second message from the UAS.

[0412] The specific implementation of step 1622 can be referred to step 1523 above, and will not be elaborated here.

[0413] Scenario 6: The terminal does not support the MDT measurement process.

[0414] If the terminal does not support the MDT measurement procedure, the terminal's location information, or its location and speed information, can be obtained based on the measurement report to identify whether the terminal is a flight terminal. In this scenario, such as... Figure 17 As shown, the process of identifying whether a terminal is a flight terminal includes one or more of the following steps:

[0415] Step 1701: The AMF sends a second identification request message to the UDM. Correspondingly, the UDM receives the second identification request message from the AMF.

[0416] The specific implementation of step 1701 can be referred to step 1501 above, and this application will not elaborate on it.

[0417] Step 1702: UDM assigns a second identifier to the terminal.

[0418] The specific implementation of step 1702 can be referred to step 1502 above, and will not be elaborated here.

[0419] Step 1703: UDM sends the second identifier to AMF. Correspondingly, AMF receives the second identifier from UDM.

[0420] The specific implementation of step 1703 can be referred to step 1503 above, and will not be elaborated here.

[0421] Step 1704: The AMF, access network devices, and terminals perform IDENTITY query, authentication, NAS security mode, and registration processes, and indicate the second identifier.

[0422] The specific implementation of step 1704 can be referred to step 1504 above, and will not be elaborated here.

[0423] Step 1705: The terminal sends a measurement report to the access network equipment.

[0424] Step 1706: The access network device analyzes the received measurement report and identifies whether the terminal is in the first state.

[0425] In some embodiments, after receiving the MDT measurement data from the terminal, the access network device analyzes the terminal's location and speed information in the MDT measurement data to determine whether the terminal is currently in a first state. If the access network device determines that the terminal is currently in a first state, it continues to execute step 1705; if the access network device determines that the terminal is not currently in a first state, it does not continue to execute the following steps.

[0426] Step 1707: The access network device sends a local report to the AMF.

[0427] In some embodiments, the location report includes the terminal's location information, or the terminal's location information and speed information, as well as indication information that the terminal is in a first state. Optionally, the local report includes a second identifier.

[0428] Step 1708: AMF sends a local report to UAS.

[0429] Optionally, a second identifier may be included in the local report.

[0430] Step 1709: The UAS sends a first request message to the UDM. Correspondingly, the UDM receives the first request message from the UAS.

[0431] The specific implementation of step 1707 can be referred to step 1521 above, and will not be elaborated here.

[0432] Step 1710: UDM sends the first response information to UAS. Correspondingly, UAS receives the first response information from UDM.

[0433] The specific implementation of step 1708 can be referred to step 1522 above, and will not be elaborated here.

[0434] Step 1711: The UAS sends a second instruction message to the USS. Correspondingly, the USS receives the second instruction message from the UAS.

[0435] The specific implementation of step 1709 can be referred to step 1523 above, and will not be elaborated here.

[0436] The communication process provided in the embodiments of this application has been described above in conjunction with scenarios 4 to 6.

[0437] In some embodiments, when the access network device is an O-RAN architecture, the process by which the core network element communicates with the terminal through the O-RAN architecture of the access network device is as follows: Figure 18 As shown, it includes:

[0438] Step 1801: The core network element sends the second identifier to the terminal through the O-CU, O-DU, and O-RU. Correspondingly, the terminal receives the second identifier from the core network element.

[0439] In some embodiments, when a terminal accesses the network, after the RRC connection is established, the terminal sends an RRCSetupComplete message to the O-RU of the access network device. The O-RU sends an RRCSetupComplete message to the O-CU through the O-DU. The O-CU determines that the RRC establishment is complete through the RRCSetupComplete message, selects an AMF node, and sends an INITIALUE MESSAGE to the core network element to trigger the initial context establishment.

[0440] As one implementation method, after the initial context establishment is triggered, the core network element assigns a second identifier to the terminal and sends the second identifier to the O-CU. The O-CU forwards the second identifier to the O-DU, the O-DU forwards the second identifier to the O-RU, and the O-RU forwards the second identifier to the terminal.

[0441] Step 1802: The core network element sends MDT (Multi-Dedicated User) subscription indication information to the O-CU. Correspondingly, the O-CU receives the MDT subscription indication information from the core network element.

[0442] Optionally, the MDT subscriber indication information is used to indicate whether the terminal is an MDT subscriber.

[0443] As an example, the MDT subscriber indication information is carried in the INITIAL CONTEXT SETUP REQUEST message. The AMF uses the INITIAL CONTEXT SETUP REQUEST message to indicate to the access network equipment whether the terminal is an MDT subscriber.

[0444] Optionally, the AMF can indicate to the access network equipment whether multiple terminals are MDT subscribers.

[0445] After the AMF indicates the MDT subscribed users to the access network equipment, relevant personnel can subscribe to MDT measurement events through the MAE. The MAE determines the MDT subscription event based on the configuration operations of the relevant personnel and sends the subscription message for the MDT measurement event to the access network equipment. Since the terminals selected in the management-based MDT measurement process and the signaling-based MDT measurement process are different, the following explanations are provided for different scenarios:

[0446] Scenario 5: Management-based MDT measurement

[0447] In scenario 5, it is necessary to perform MDT measurements on all MDT subscribers within a specified area (such as Cell ID, TA, etc.). Scenario 5 is applicable to scenarios where multiple unknown non-UAV terminals exist within the target area, all of which may be in the first state of flight. When these unknown non-UAV terminals are in flight, they need to be identified and monitored individually. The terminal selection process in scenario 5 includes the following steps 1803-1804:

[0448] Step 1803: Select terminal for O-CU.

[0449] In some embodiments, the access network device determines the MDT subscribers indicated by the AMF and selects the terminals within the specified range as the terminals that need to report the MDT measurement results.

[0450] Optionally, the terminal is one of the terminals selected by the aforementioned access network equipment.

[0451] Step 1804: The O-CU sends measurement configuration information to the terminal via the O-DU and O-RU. Correspondingly, the terminal receives the measurement configuration information from the O-CU.

[0452] As one implementation method, the process of O-CU sending measurement configuration information to the terminal is as follows: O-DU forwards measurement configuration information, O-DU forwards measurement configuration information to O-RU, and O-RU forwards measurement configuration information to the terminal.

[0453] Optionally, the access network device sends MDT configuration information to each terminal selected in step 1803 above, so that each selected terminal performs MDT measurement and reports the MDT measurement results.

[0454] Case 6: Signaling-based MDT measurement

[0455] In scenario 6, specific terminals (such as terminals with a specific IMSI) are required for MDT measurements. Scenario 6 can be applied to monitoring whether a known non-UAV terminal is in the first state and to monitoring it when it is. The process for selecting a terminal in scenario 6 includes the following steps 1805:

[0456] Step 1805: Core network elements send measurement configuration information to the terminal via O-CU, O-DU, and O-RU. Correspondingly, the terminal receives the measurement configuration information from the core network elements.

[0457] As one implementation method, after the core network element determines the measurement configuration information of the terminal, it sends the measurement configuration information to the O-CU, the O-CU forwards the measurement configuration information to the O-DU, the O-DU forwards the measurement configuration information to the O-RU, and the O-RU forwards the measurement configuration information to the terminal.

[0458] After selecting a terminal based on the method described in Case 5 or Case 6 above, the terminal performs MDT measurement and reports the MDT measurement results.

[0459] Step 1806: The terminal performs MDT measurement.

[0460] The specific implementation of step 1806 can be referred to step 1512 above, and will not be elaborated here.

[0461] Step 1807: The terminal sends MDT measurement data to the O-CU via the O-RU and O-DU. The MDT measurement data carries an anonymous identifier (Anonymous ID).

[0462] In one implementation, after the terminal performs MDT measurements and determines the MDT measurement data, it sends the MDT measurement data to the O-RU; the O-RU sends the MDT measurement data to the O-DU; and the O-DU sends the MDT measurement data to the O-CU. After this, the O-CU sends the MDT measurement data to the core network elements.

[0463] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between network elements. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. The communication device can be a terminal in the above method embodiments, or a device containing the terminal, or a component usable in a terminal; the communication device can be a network device in the above method embodiments, or a device containing the network device, or a component usable in a network device; or, the communication device can be a terminal in the above method embodiments, or a device containing the terminal, or a component usable in a terminal. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0464] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be understood that the module division in this application embodiment is illustrative and is only a logical functional division. In actual implementation, there may be other division methods.

[0465] for example, Figure 19 This is a schematic diagram of a communication device 1900 provided in an embodiment of this application. The communication device 1900 includes a transceiver module 1910. Optionally, it includes a processing module 1920. The transceiver module 1910, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, transceiver, transceiver device, or communication interface.

[0466] Taking the communication device 1900 as a network device in the above method embodiment, or a device containing the above network device, or a component that can be used in a network device as an example, then: the transceiver module 1910 is used to receive first information; the first information is used to determine that the terminal is in a first state; the transceiver module 1910 is also used to send second information to a first network element; the second information includes a first identifier of the terminal and first indication information; the first indication information is used to indicate that the terminal is in the first state; the first network element includes the function of managing the terminal.

[0467] In one possible implementation, the first information is sent by the network data analysis network element; or, the first information is sent by the operation and maintenance management network element; wherein, the functions of the operation and maintenance management network element include fault management, performance monitoring, and service assurance.

[0468] In one possible implementation, the first information includes a second identifier of the terminal and the first indication information; the second identifier corresponds to the first identifier.

[0469] In one possible implementation, the first indication information is further used to indicate the location information of the terminal, or the location information and speed information of the terminal.

[0470] In one possible implementation, the processing module 1920 is used to determine that the terminal is in the first state based on the first indication information in the first information.

[0471] In one possible implementation, the transceiver module 1910 is further configured to send a first request message; the first request message is used to request a first identifier corresponding to the second identifier; the transceiver module 1910 is further configured to receive a first response message; the first response message is used to indicate the first identifier corresponding to the second identifier.

[0472] In one possible implementation, the transceiver module 1910 is further configured to send a first subscription message to the operation and maintenance management network element, the first subscription message being used to request subscription to information about the terminal being in the first state; the operation and maintenance management network element has functions including fault management, performance monitoring, and service assurance; the transceiver module 1910 is further configured to receive a first subscription response message from the operation and maintenance management network element; the first subscription response message is used to indicate successful subscription to the terminal's state parameters.

[0473] In one possible implementation, the first identifier is a unique identifier for the terminal.

[0474] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0475] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold, and the speed of the terminal is greater than a second threshold.

[0476] Taking the communication device 1900 as a network data analysis network element in the above method embodiment, or a device containing the above network data analysis network element, or a component that can be used for network data analysis network elements, as an example: the transceiver module 1910 is used to receive third information; the third information includes the location information of the terminal, or the location information and speed information of the terminal; the transceiver module 1910 is also used to send first information; the first information is used to determine that the terminal is in a first state.

[0477] In one possible implementation, the first information includes a second identifier of the terminal and first indication information, wherein the first indication information is used to indicate that the terminal is in the first state.

[0478] In one possible implementation, the first indication information is used to indicate the location information of the terminal, or the location information and speed information of the terminal.

[0479] In one possible implementation, the first identifier is the terminal's unique identifier.

[0480] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0481] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0482] Taking the communication device 1900 as a unified data management network element in the above method embodiment, or a device containing the above unified data management network element, or a component that can be used in a unified data management network element, as an example, then: the transceiver module 1910 is used to receive a first request message; the first request message is used to request a first identifier corresponding to the second identifier; the transceiver module 1910 is also used to send a first response message; the first response message is used to indicate the first identifier corresponding to the second identifier.

[0483] In one possible implementation, the transceiver module 1910 is further configured to receive a second request message; the second request message is configured to request the allocation of the second identifier for the terminal; the transceiver module 1910 is further configured to send a second response message; the second response message includes the second identifier allocated to the terminal.

[0484] In one possible implementation, the first identifier is the terminal's unique identifier.

[0485] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0486] Taking the communication device 1900 as a terminal in the above method embodiment, or a device containing the above terminal, or a component that can be used in a terminal as an example, then: the transceiver module 1910 is used to receive the second identifier of the terminal; the transceiver module 1910 is also used to send fourth information; the fourth information includes the second identifier of the terminal and first indication information; the first indication information is used to indicate the location information of the terminal, or the location information and speed information of the terminal.

[0487] In one possible implementation, the fourth information is carried in the minimum road test measurement data; or, the fourth information is carried in the measurement report.

[0488] In one possible implementation, the first identifier is the terminal's unique identifier.

[0489] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0490] Taking the communication device 1900 as an access network device in the above method embodiment, or a device containing the above access network device, or a component that can be used in an access network device, as an example, then: the transceiver module 1910 is used to receive fourth information; the fourth information includes the second identifier of the terminal and first indication information; the first indication information is used to indicate the location information of the terminal, or the location information and speed information of the terminal; the transceiver module 1910 is also used to send first information; the first information is used to determine that the terminal is in a first state.

[0491] In one possible implementation, the transceiver module 1910 is further configured to send a second identifier of the terminal to the terminal.

[0492] In one possible implementation, the first identifier is the terminal's unique identifier.

[0493] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0494] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0495] Taking the communication device 1900 as an access and mobility management network element in the above method embodiment, or a device containing the above access and mobility management network element, or a component that can be used for access and mobility management network elements, as an example:

[0496] The transceiver module 1910 is further configured to receive first information; the first information is used to determine that the terminal is in a first state; the transceiver module 1910 is further configured to send the first information.

[0497] In one possible implementation, the transceiver module 1910 is further configured to send a second request message; the second request message is configured to request the allocation of the second identifier for the terminal; the transceiver module 1910 is further configured to receive a second response message; the second response message includes the second identifier allocated to the terminal.

[0498] In one possible implementation, the transceiver module 1910 is also used to send a second identifier of the terminal.

[0499] In one possible implementation, the first identifier is the terminal's unique identifier.

[0500] In one possible implementation, the second identifier is used to identify the terminal within the management scope of the first network element.

[0501] In one possible implementation, the first state satisfies at least one of the following: the altitude of the terminal is greater than a first threshold; or, the altitude of the terminal is greater than the first threshold and the speed of the terminal is greater than a second threshold.

[0502] All relevant content of each step involved in the above method embodiments can be referred to in the functional description of the corresponding functional module, and will not be repeated here. Optionally, the communication device 1900 may further include a storage module 1930, which can be used to store instructions and / or data, and the processing module 1920 can read the instructions and / or data in the storage module 1930.

[0503] In this embodiment, the communication device 1900 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory executing one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the aforementioned functions. In a simple embodiment, those skilled in the art will understand that the communication device can employ... Figure 9 The communication device shown is in the form of 900.

[0504] Specifically, Figure 19 The functions / implementation process of the transceiver module 1910 and the processing module 1920 can be obtained through... Figure 9 The processor 91 in the communication device 900 shown calls computer execution instructions stored in the memory 92 to implement the function. Alternatively, Figure 19 The function / implementation process of the processing module 1920 in the middle can be obtained through Figure 9The processor 91 in the communication device 900 shown calls computer execution instructions stored in the memory 92 to implement the communication. Figure 19 The function / implementation process of the transceiver module 1910 in the middle can be obtained through Figure 9 This is achieved through the transceiver 95 in the communication device 900 shown.

[0505] Since the communication device provided in this application embodiment can execute the above communication method, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0506] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0507] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a central processing unit (CPU), microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0508] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor for implementing the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0509] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0510] Optionally, embodiments of this application also provide a communication system, which includes the network device and the terminal described in the above method embodiments.

[0511] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another 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 can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs).

[0512] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0513] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: Receive first information; the first information is used to determine that the terminal is in a first state; Send second information to the first network element; the second information includes the first identifier of the terminal and first indication information; the first indication information is used to indicate that the terminal is in the first state; the first network element includes the function of managing the terminal.

2. The method according to claim 1, characterized in that, The first information is sent by the network data analysis network element; or, the first information is sent by the operation and maintenance management network element; wherein, the functions of the operation and maintenance management network element include fault management, performance monitoring, and service guarantee.

3. The method according to claim 1 or 2, characterized in that, The first information includes the second identifier of the terminal and the first indication information; the second identifier corresponds to the first identifier.

4. The method according to any one of claims 1-3, characterized in that, The first indication information is also used to indicate the location information of the terminal, or the location information and speed information of the terminal.

5. The method according to claim 4, characterized in that, After receiving the first information, the method further includes: Based on the first indication information in the first information, it is determined that the terminal is in the first state.

6. The method according to any one of claims 2-5, characterized in that, Before sending the second information, the method further includes: Send a first request message; the first request message is used to request a first identifier corresponding to the second identifier; Receive a first response message; the first response message is used to indicate the first identifier corresponding to the second identifier.

7. The method according to claim 5 or 6, characterized in that, Before receiving the first information, the method further includes: A first subscription message is sent to the operation and maintenance management network element, the first subscription message being used to request subscription to information about the terminal being in the first state; the functions of the operation and maintenance management network element include fault management, performance monitoring, and service assurance; Receive a first subscription response message from the operation and maintenance management network element; the first subscription response message is used to indicate the status parameters of the terminal that have been successfully subscribed.

8. The method according to any one of claims 1-7, characterized in that, The first identifier is the unique identifier of the terminal.

9. The method according to any one of claims 2-8, characterized in that, The second identifier is used to identify the terminal within the management scope of the first network element.

10. The method according to any one of claims 1-10, characterized in that, The first state satisfies at least one of the following: The altitude of the terminal is greater than the first threshold. Alternatively, the altitude of the terminal is greater than the first threshold, and the speed of the terminal is greater than the second threshold.

11. A communication method, characterized in that, The method includes: Receive third information; the third information includes the terminal's location information, or the terminal's location information and speed information; Send first information; the first information is used to determine that the terminal is in a first state.

12. The method according to claim 11, characterized in that, The first information includes a second identifier of the terminal and first indication information, the first indication information being used to indicate that the terminal is in the first state.

13. The method according to claim 12, characterized in that, The first indication information is used to indicate the location information of the terminal, or the location information and speed information of the terminal.

14. A communication method, characterized in that, The method includes: Receive a first request message; the first request message is used to request a first identifier corresponding to the second identifier; Send a first response message; the first response message is used to indicate the first identifier corresponding to the second identifier.

15. The method according to claim 14, characterized in that, Before receiving the first request message, the method further includes: Receive a second request message; the second request message is used to request that the second identifier be assigned to the terminal. Send a second response message; the second response message includes the second identifier assigned to the terminal.

16. A communication method, characterized in that, The method includes: The second identifier of the receiving terminal; Send a fourth message; the fourth message includes a second identifier of the terminal and a first indication message; the first indication message is used to indicate the location information of the terminal, or the location information and speed information of the terminal.

17. The method according to claim 16, characterized in that, The fourth information is contained in the minimum road test measurement data; Alternatively, the fourth piece of information may be contained in the measurement report.

18. A communication method, characterized in that, The method includes: Receive fourth information; the fourth information includes the second identifier of the terminal and first indication information; the first indication information is used to indicate the location information of the terminal, or the location information and speed information of the terminal; Send first information; the first information is used to determine that the terminal is in a first state.

19. The method according to claim 18, characterized in that, Before receiving the fourth information, the method further includes: Send the terminal's second identifier to the terminal.

20. A communication method, characterized in that, The method includes: Receive first information; the first information is used to determine that the terminal is in a first state; Send the first message.

21. The method according to claim 20, characterized in that, The method further includes: Send a second request message; the second request message is used to request that the second identifier be assigned to the terminal; Receive a second response message; the second response message includes the second identifier assigned to the terminal.

22. The method according to claim 20 or 21, characterized in that, The method further includes: Send the second identifier of the terminal.

23. A communication device, characterized in that, include: A functional unit for performing the method as described in any one of claims 1-22; wherein the action performed by the functional unit is implemented by hardware or by hardware executing corresponding software.

24. A communication device, characterized in that, include: processor; The processor is connected to a memory for storing computer execution instructions, and the processor executes the computer execution instructions stored in the memory to enable the communication device to implement the method as described in any one of claims 1-22.

25. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-22.

26. A chip, characterized in that, The chip includes a processor; the processor is connected to a memory for storing computer execution instructions, and the processor executes the computer execution instructions stored in the memory to enable the communication device to implement the method as described in any one of claims 1-22.

27. A computer program product containing instructions, characterized in that, When it is operated on a communication device, it causes the communication device to perform the method as described in any one of claims 1-22.

Images