Communication method and apparatus

Abstract

The embodiments of the present application relate to the field of communications. Provided are a communication method and apparatus, which can ensure that privacy data of a terminal is not leaked in a scenario where an RRC state transition or an RLF occurs. In the method, a terminal receives, from a first access network device, first information used for indicating a cell list in which the terminal is permitted to retain data collected during the service of the first access network device, such that when the terminal selects, after transitioning to an RRC idle state or an RRC inactive state or after the occurrence of an RLF, a cell to establish an RRC connection, the terminal determines, on the basis of the cell list indicated by the first information, whether a selected first cell for establishing the RRC connection is included in the cell list, so as to determine whether to retain or delete the data collected during the service of the first access network device; and when the first cell is included in the cell list, the terminal retains the data collected during the service of the first access network device, and sends first indication information to a second access network device corresponding to the first cell, so as to indicate that the terminal has available data.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510378327.0, filed on March 26, 2025, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] In different use cases (UC) based on artificial intelligence (AI), the terminal collects data and transmits the collected data to the network (such as access network equipment or network management) according to the network's request, so that the network can train AI / machine learning (ML) models based on the data collected by the terminal.

[0004] During data collection, the network may need to switch the terminal to a radio resource control (RRC) idle state or an RRC inactive state, or the terminal may experience a radio link failure (RLF), in which case the terminal will rebuild or restore the RRC connection.

[0005] However, the access network equipment used by the terminal to rebuild or restore the RRC connection may not belong to the same vendor as the access network equipment corresponding to the cell where the data is collected. If the terminal sends the data collected in the source serving cell to the access network equipment of another vendor, there will be a problem of data privacy leakage. Summary of the Invention

[0006] This application provides a communication method and apparatus that can ensure that the privacy data of the terminal is not leaked in scenarios where RRC state transition or RLF occurs.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] Firstly, a communication method is provided, which can be applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip). Taking the application of this method to a terminal as an example, in this method: receiving first information from a first access network device, the first information is used to indicate a list of cells in which the terminal is allowed to retain data collected during the service of the first access network device; determining the first cell for establishing an RRC connection after moving to a Radio Resource Control (RRC) idle state or an RRC inactive state, or after a Radio Link Failure (RLF) occurs; and if the first cell is included in the cell list, sending first indication information to the second access network device corresponding to the first cell, the first indication information being used to indicate that there is available data.

[0009] In this method, the terminal receives first information from the first access network device, which indicates that the terminal is allowed to retain data collected during the service of the first access network device. This allows the terminal to determine whether the first cell for establishing an RRC connection is included in the cell list indicated by the first information when moving to an RRC idle state or an RRC inactive state, or after an RLF occurs. This determines whether the data collected during the service of the first access network device needs to be retained or deleted. If the first cell is included in the cell list, the data collected during the service of the first access network device is retained, and a first indication message is sent to the second access network device corresponding to the first cell to indicate that the terminal has available data. Therefore, the privacy data of the source serving access network device is protected from leakage in scenarios involving RRC state transitions or RLF.

[0010] In one possible design, the communication method may further include: receiving second information from a first access network device, the second information indicating that data collected during service by the first access network device should be retained when the terminal moves to an RRC idle state, an RRC inactive state, or an RLF occurs. That is, the first access network device can be configured to retain, but not delete, the collected data when the terminal undergoes an RRC state transition and / or an RLF occurs, thereby enabling the terminal to determine, based on the cell list indicated by the first information, whether to indicate to the access network device establishing the RRC connection that it has available data when re-establishing the RRC connection, and to send the data collected during service by the first access network device to it.

[0011] In one possible design, the communication method may further include: retaining data collected during the service period of the first access network device if it is determined that the first cell belongs to a cell list. That is, if the first cell is a cell for which the terminal is allowed to retain or forward data collected during the service period of the first access network device, then the terminal can retain the data collected during the service period of the first access network device. At this time, the terminal sends a first indication message to the second access network device corresponding to the first cell to indicate that the terminal has available data.

[0012] In one possible design, the communication method may further include: deleting data collected during the service period of the first access network device if it is determined that the first cell is not included in the cell list. That is, if the first cell is a cell for which the terminal is not allowed to retain or forward data collected during the service period of the first access network device, then the terminal can delete or discard the data collected during the service period of the first access network device. In this case, the terminal does not need to send a first indication message to the second access network device corresponding to the first cell.

[0013] In one possible design, deleting data collected during the service period of the first access network device may include: deleting the data collected during the service period of the first access network device after establishing an RRC connection with the first cell. In some implementations, the terminal may also delete or discard the data collected during the service period of the first access network device immediately after determining that the first cell is not included in the cell list. That is, the terminal checks whether to delete or discard the data after each cell selection or reselection, or it may delete or discard the data collected during the service period of the first access network device before establishing an RRC connection with the first cell; there is no limitation on this.

[0014] In one possible design, cells in the cell list can be indicated by any of the following: Physical Cell Identifier (PCI), New Radio Cell Global Identifier (NCGI), Public Land Mobile Network (PLMN), or Notification Area (RNA) of the terminal based on the Radio Access Network (RAN).

[0015] In one possible design, the communication method may further include: deleting the cell list when a first event occurs; wherein the first event is one of the following: deleting data collected during the service period of the first access network device; or, powering off; or, successfully establishing an RRC connection with the first cell; or, receiving a new data collection configuration in the first cell. Therefore, by designing the validity of the cell list, the reliability of the information can be guaranteed.

[0016] In one possible design, the first information can be included in any of the following messages: Master Information Block (MIB) message, System Information Block (SIB1) message, RRC reconfiguration message, or RRC release message. This reduces signaling overhead.

[0017] In one possible design, when moving to the RRC idle state or the RRC inactive state, the first indication information can be included in any of the following messages and sent: RRC recovery request message, RRC establishment request message, RRC recovery complete message, or RRC establishment complete message. This reduces signaling overhead.

[0018] In one possible design, in the event of an RLF (Recurrent Range Failure), the first indication information can be sent in any of the following messages: RRC establishment request message, RRC reconstruction request message, RRC establishment complete message, or RRC reconstruction complete message. This reduces signaling overhead.

[0019] Secondly, a communication method is provided, which can be applied to the network side, such as access network equipment on the network side, modules (e.g., circuits, processors, chips, or chip systems) in the access network equipment, or logical nodes, logical modules, or software that can implement all or part of the functions of the access network equipment. Taking the application of this method to a first access network equipment as an example, in this method: first information is obtained, the first information being used to indicate the list of cells in which the terminal is allowed to retain data collected during the service of the first access network equipment; the first information is then sent to the terminal.

[0020] In one possible design, the communication method may further include: sending a second message to the terminal, the second message being used to indicate that the terminal retains data collected during service by the first access network device when it moves to an RRC idle state, an RRC inactive state, or an RLF occurs.

[0021] In one possible design, cells in the cell list can be indicated by any of the following: PCI, NCGI, PLMN, or the terminal's RNA.

[0022] In one possible design, the first information can be sent in any of the following messages: MIB message, SIB1 message, RRC reconfiguration message, or RRC release message.

[0023] The technical effects of the method described in the second aspect can be found in the relevant description of the technical effects of the method described in the first aspect above, and will not be repeated here.

[0024] Thirdly, a communication device is provided for implementing the various methods described above. This communication device can be a terminal as described in the first aspect, or a device containing the terminal, or a device included in the terminal, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the first aspect. These modules, units, or means can 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.

[0025] In some possible designs, the communication device includes a transceiver module and a processing module. The transceiver module is used to receive first information from a first access network device, the first information indicating a list of cells in which the terminal is allowed to retain data collected during the service of the first access network device. The processing module is used to determine the first cell for establishing an RRC connection after moving to a Radio Resource Control (RRC) idle state or an RRC inactive state, or after a Radio Link Failure (RLF) occurs. If the first cell is included in the cell list, the transceiver module is further used to send first indication information to the second access network device corresponding to the first cell, the first indication information indicating that data is available.

[0026] In one possible design, the transceiver module is further configured to receive second information from the first access network device. The second information is used to indicate that the data collected during the service of the first access network device should be retained when the terminal moves to the RRC idle state, the RRC inactive state, or when an RLF occurs.

[0027] In one possible design, the processing module is further configured to retain data collected during the service of the first access network device if it is determined that the first cell belongs to a cell in the cell list.

[0028] In one possible design, the processing module is further configured to delete data collected during the service of the first access network device if it is determined that the first cell is not included in the cell list.

[0029] In one possible design, the processing module, used to delete data collected during the service period of the first access network device, may include: a processing module used to delete data collected during the service period of the first access network device after completing the RRC connection establishment with the first cell.

[0030] In one possible design, cells in the cell list can be indicated by any of the following: Physical Cell Identifier (PCI), New Radio Cell Global Identifier (NCGI), Public Land Mobile Network (PLMN), or Notification Area (RNA) of the terminal based on the Radio Access Network (RAN).

[0031] In one possible design, the processing module is used to delete the cell list when a first event occurs; wherein the first event is one of the following: deleting data collected during the service of the first access network device; or, powering off; or, successfully establishing an RRC connection with the first cell; or, receiving a new data collection configuration in the first cell.

[0032] In one possible design, the first information can be sent in any of the following messages: Master Information Block (MIB) message, System Information Block (SIB1) message, RRC reconfiguration message, or RRC release message.

[0033] In one possible design, when moving to the RRC idle state or the RRC inactive state, the first indication information may be sent in any of the following messages: RRC recovery request message, RRC establishment request message, RRC recovery complete message, or RRC establishment complete message.

[0034] In one possible design, in the event of an RLF, the first indication information may be sent in any of the following messages: RRC establishment request message, RRC reconstruction request message, RRC establishment complete message, or RRC reconstruction complete message.

[0035] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device described in the third aspect, and the receiving module implements the receiving function of the communication device described in the third aspect.

[0036] In one possible design, the communication device described in the third aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device described in the third aspect can perform the method described in the first aspect.

[0037] Fourthly, a communication device is provided for implementing the various methods described above. This communication device can be an access network device as described in the second aspect, or a device comprising the access network device, or a device included in the access network device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the second aspect. These modules, units, or means can 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.

[0038] In some possible designs, the communication device includes a transceiver module and a processing module. The processing module is used to acquire first information, which indicates a list of cells from which the terminal is permitted to retain data collected during service by the first access network device. The transceiver module is used to send the first information to the terminal.

[0039] In one possible design, the transceiver module is further configured to send a second message to the terminal, the second message being used to indicate that the terminal retains the data collected during the service of the first access network device when it moves to the RRC idle state, the RRC inactive state, or when an RLF occurs.

[0040] In one possible design, cells in the cell list can be indicated by any of the following: PCI, NCGI, PLMN, or the terminal's RNA.

[0041] In one possible design, the first information can be sent in any of the following messages: MIB message, SIB1 message, RRC reconfiguration message, or RRC release message.

[0042] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device described in the fourth aspect, and the receiving module implements the receiving function of the communication device described in the fourth aspect.

[0043] In one possible design, the communication device described in the fourth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device described in the fourth aspect can perform the method described in the second aspect.

[0044] Fifthly, a communication device is provided, comprising an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the first or second aspect. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first or second aspect. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0045] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0046] In one possible design, the communication device may also include the memory.

[0047] The aforementioned communication device may be a terminal, a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0048] A sixth aspect provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the first or second aspect. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first or second aspect. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0049] In a seventh aspect, a communication system is provided, comprising: a terminal for performing the method described in the first aspect, and a first access network device for performing the method described in the second aspect.

[0050] Eighthly, a chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the method described in the first or second aspect to be implemented.

[0051] A ninth aspect provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform any of the possible designs of the first to second aspects described above.

[0052] In a tenth aspect, a computer program product containing instructions is provided, which, when read and executed by a computer, causes the computer to perform any of the possible designs in the first to second aspects described above. Attached Figure Description

[0053] Figure 1 is a schematic diagram of the architecture of an AI application framework in NR;

[0054] Figure 2 is a schematic diagram of a terminal performing RRC reconstruction.

[0055] Figure 3 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0056] Figures 4-6 are schematic flowcharts of a communication method provided in this application;

[0057] Figure 7 is a schematic diagram of a method flow under an O-RAN architecture provided in an embodiment of this application;

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

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

[0060] To better understand the embodiments of this application, the following points are explained before introducing the embodiments of this application.

[0061] First, in the embodiments of this application, "for indicating" can include both direct and indirect indication. When describing a certain "indication information" for indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information carries A.

[0062] The information indicated by the instruction is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.

[0063] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0064] Second, in the embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they distinguish different instruction information. As another example, the first instruction information and the second instruction information are only used to distinguish different areas and do not limit their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that the terms "first," "second," etc., are not necessarily different.

[0065] Third, in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the fact that the device (e.g., a terminal device or a network device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., a terminal device or a network device) to make a judgment action when implementing it, nor do they imply any other limitations.

[0066] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. 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.

[0067] Finally, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. The embodiments of this application will present various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include other devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these solutions can also be used.

[0068] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless fidelity (Wi-Fi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0069] The relevant technologies involved in the embodiments of this application will be described below.

[0070] 1. AI

[0071] AI is a technology that simulates complex calculations by mimicking the human brain. With the improvement of data storage and computing power, AI is being used more and more. The 3rd Generation Partnership Project (3GPP) proposes to apply AI to NR (Network Radio Network) to improve network performance and user experience through intelligent data collection and analysis. For example, an application framework of AI in NR is shown in Figure 1, which may include the following modules (or entities):

[0072] The data collection module collects and stores data from various entities, including next-generation Node-Bs (gNBs), gNB-central units (CUs), gNB-distributed units (DUs), user equipment (UEs), and other management entities, serving as a database for AI model training and data analysis inference. The model training module analyzes the training data provided by the data collection module to develop the optimal AI model. The model inference module uses the AI ​​model, based on the inference data provided by the data collection module, to provide reasonable AI-based predictions about network operation or guide network strategy adjustments. The decision / actor module executes the relevant strategy adjustments output by the model inference module and feeds back the network's performance (such as various performance parameters) after applying the relevant strategies to the data collection module for storage.

[0073] 2. AI-based application scenarios (use cases)

[0074] Currently, 3GPP has designed several basic application scenarios for AI on the RAN side from working groups such as Radio Access Network (RAN) 3 and RAN 1. RAN 3 includes energy saving, load balancing, and mobility optimization, while RAN 1 includes channel state information (CSI)-reference signal (RS) feedback enhancement, beam management enhancement, and positioning accuracy enhancements. The basic principles of these application scenarios are briefly introduced below.

[0075] (1) Energy saving

[0076] By collecting load, energy consumption, energy efficiency information from itself and neighboring cells, as well as terminal mobility information and measurement results, base stations can predict their own load trends. Combined with cell usage and key performance indicator (KPI) requirements, energy-saving measures can be implemented in a timely and appropriate manner without affecting network coverage or user access. The simplest energy-saving strategy includes directly deactivating the cell. Other strategies include carrier shutdown, channel shutdown, time slot shutdown, and reduced transmit power. More complex strategies involve combining these measures. When network coverage is affected or cannot meet terminal access and service requirements, the current energy-saving strategy needs to be modified, or the system should be restored to normal operation. In such cases, load prediction should be recalculated, or the AI ​​model used should be changed for re-inference.

[0077] (2) Load balancing

[0078] By collecting load, energy consumption, energy efficiency information, terminal mobility information, and measurement results from its own and neighboring cells, base stations predict their own load trends. Combined with cell usage and KPI requirements, they rationally select some terminals to switch to or receive terminals from neighboring cells, ensuring that the load levels among base stations across the entire network are similar. This reduces situations where some base stations are overloaded, affecting normal services, while others are idle. However, because the accuracy of prediction is not 100%, unreasonable terminal selection or incorrect target cells for handover can lead to handover failures or disruptions to terminal services. Inaccurate load prediction can also result in poor load balancing. Furthermore, temporary abnormal load fluctuations may render the original load balancing strategy inapplicable. In such cases, it is necessary to exit or modify the current load balancing strategy and consider re-predicting the load or changing the AI ​​model used for re-inference.

[0079] (3) Mobility optimization

[0080] By collecting historical mobility information from terminals at base stations and combining it with the terminals' measurement information, the future mobility of terminals can be predicted. Based on the predicted mobility information, it can determine in advance whether the terminal needs to handover, and send handover configurations and notify the target cell to prepare access resources in advance, reducing latency during the handover process and lowering the probability of handover or access failures. However, since mobility prediction accuracy is not 100%, when mobility is predicted incorrectly, it will lead to handover failure and service interruption. To address this, it is necessary to consider retraining the model and inference based on the abnormal situation, or to consider replacing the model, to avoid similar abnormal situations from occurring again in subsequent terminals.

[0081] (4) Enhanced CSI-RS feedback

[0082] The main process of CSI-RS feedback enhancement is as follows: a) The base station and the terminal first exchange a dictionary. Usually, the base station pre-trains a model based on the terminal's capabilities and its own requirements, and then sends an encoder and quantizer to the terminal; b) The terminal compresses and quantizes the matrix to be fed back according to the measured channel matrix and the existing dictionary, and sends the result B to the base station; c) The base station reverse-engineers the original channel matrix based on the dictionary and the data reported by the terminal.

[0083] (5) Enhanced beam management

[0084] The main process of beam management enhancement is as follows: a) Generation of the initial model: By having a certain number of terminals report the results of full beam scanning of the synchronization signal (SS) and physical broadcast channel (PBCH) block (SSB), a sparse scanning matrix (sparse model) is trained. This matrix is ​​usually unique to each cell; b) The base station sends the sparse model to the terminals (which can be done through system information block (SIB) messages, etc.), and the terminals perform beam scanning in the P1 phase based on this matrix; c) Based on the sparse scanning results of the terminals, the base station infers the optimal CSI-RS beam and starts P2 scanning of the terminals, and the terminals return the optimal CSI-RS beam ID.

[0085] (6) Enhanced positioning accuracy

[0086] The main process for enhancing positioning accuracy is as follows: a) Collect raw data using a reference terminal controlled by the operator; b) Train models for the location management function (LMF) (non-RAN side node) and gNB respectively. The model trained by the LMF can infer the final positioning (latitude and longitude, etc.), and the model trained by the gNB can infer the line of sight (LOS) / non-line of sight (NLOS) judgment results.

[0087] 3. Model Application Environment

[0088] For the different AI-based application scenarios mentioned above, the terminal can be configured to perform different functions. For example, for CSI-RS feedback enhancement, the terminal can be configured to perform CSI-RS-based channel prediction. Regarding how to implement a specific function, the terminal can choose from multiple models with the same functionality (meaning all can provide the required output). The selection can be configured on the network side or the terminal can choose based on its internal implementation. The selection is usually based on the application environment of the model.

[0089] In current standard discussions, there are many classifications based on the model's application environment, which typically include the following aspects:

[0090] (1) Macroscopic physical attributes of the terminal, such as the terminal's speed, direction of movement, geographical location, and height;

[0091] (2) The hardware and software attributes of the terminal, such as the terminal's effective power, computing power, storage space, and compilation environment of the supported AI models;

[0092] (3) The channel environment in which the terminal is located, such as urban macro (UMa), urban micro (UMi), and indoor hotspot (InH);

[0093] (4) Terminal and gNB communication configuration, such as the number of receiving antennas of the terminal and the number of transmitting ports of the gNB;

[0094] (5) Time and frequency domain resources for air interface communication, such as carrier frequency, subcarrier spacing, bandwidth, etc.

[0095] Even models that can achieve the same function may have different performance in different application environments. Therefore, it is usually necessary to select the most suitable model based on the actual application environment of the terminal.

[0096] 4. Data Collection

[0097] RAN2 is currently standardizing mechanisms for collecting radio measurements and related data, which will be used to train AI / ML models that will be executed on the network side (i.e., data collection for so-called network (NW) side models).

[0098] RAN2 agrees to reuse the Minimization of Drive Test (MDT) framework so that terminals can collect and transmit the necessary data to the network, for example, to gNBs or operation administration and maintenance (OAM) network elements (network management). However, due to the special nature of AI / ML-based data collection, some enhancements are also being specified.

[0099] To collect data for training AI / ML models deployed on the network side, the network issues data collection configurations to the terminal. The terminal can then perform signal measurements or other data collection operations according to these configurations and record the measurement results or collected data in its internal memory. After a period of time, the network can request the terminal to transmit the collected data back to the network, based on either the terminal's indication of data availability or the network's own determination (e.g., after a certain period). Upon receiving the network request, the terminal transmits the collected data to the gNB, which can then further forward the data, for example, to OAM, or directly use it to train the model within the gNB.

[0100] After the terminal collects some data, the network may need to move the terminal to the RRC idle state or RRC inactive state (e.g., due to no data activity of the terminal or due to cell congestion), that is, the terminal undergoes an RRC state transition (or RRC state migration), or the terminal experiences an RLF while in the RRC connected state. All of these will cause the terminal to redetermine the cell to establish an RRC connection.

[0101] For example, if a terminal experiences an RLF (Recovery Risk Failure), as shown in Figure 2, taking the terminal as a UE (User Equipment) as an example, the process of the terminal performing RRC reconstruction includes:

[0102] S201, The UE sends an RRC Reestablishment Request message to the serving gNB.

[0103] Accordingly, the serving gNB receives the RRC reconstruction request message from the UE.

[0104] When a UE in RRC connected state experiences an RLF, the terminal performs cell selection and sends an RRC re-establishment request message to the gNB (the new gNB, i.e. the current serving gNB) corresponding to the selected cell, attempting to re-establish the RRC connection in the selected cell.

[0105] S202. The serving gNB sends a Retrieve UE Context Request message to the previous serving gNB.

[0106] Accordingly, the previous serving gNB receives a UE context retrieval request message from the serving gNB.

[0107] After receiving the RRC rebuild request message, the new gNB (i.e., the serving gNB) will attempt to retrieve the UE context from the previous serving gNB (the old gNB, i.e., the previous serving gNB).

[0108] If the new gNB can recognize the previous serving gNB and the UE context retrieval is successful, the new gNB will send an RRC Reestablishment message to the UE and continue the RRC reestablishment process, as shown in S204-S205 below. If the new gNB cannot recognize the previous serving gNB, or if the UE context retrieval fails for other reasons, the new gNB can send an RRC Setup message to the UE. This means that a new RRC connection has been established, and the UE clears its stored RRC configuration.

[0109] S203. The previous serving gNB sends a Retrieve UE Context Response message to the serving gNB.

[0110] Accordingly, the serving gNB receives the UE context retrieval response message from the previous serving gNB.

[0111] S204. The serving gNB sends an RRC Reestablishment message to the UE.

[0112] Accordingly, the UE receives an RRC reconstruction message from the serving gNB.

[0113] S205, the UE sends an RRC Reestablishment Complete message to the serving gNB.

[0114] Correspondingly, the serving gNB receives the RRC reconstruction complete message from the UE.

[0115] Optionally, the RRC reconstruction process also includes:

[0116] S206. The serving gNB sends an RRC Reconfiguration message to the UE.

[0117] Accordingly, the UE receives an RRC reconfiguration message from the serving gNB.

[0118] S207. The UE sends an RRC Reconfiguration Complete message to the serving gNB.

[0119] Correspondingly, the serving gNB receives the RRC reconfiguration complete message from the UE.

[0120] Of course, in some scenarios, the RRC reconstruction process may not complete successfully, for example, if the UE cannot find a suitable cell, or if the new gNB does not respond in time. In this case, the UE clears its stored RRC configuration and moves to the RRC idle state.

[0121] RAN2 discusses the processing of data collected by the terminal during the service of the source base station when the terminal is in the process of handover (HO), and reaches the following agreement: the terminal retains the recorded data during the handover and indicates the availability of the recorded data during the handover (e.g., by carrying the data availability indication in the RRC reconfiguration completion message).

[0122] However, the above data processing procedures present potential data privacy issues. For example, if the two gNBs involved in the handover involve two different vendors, one vendor may not want the data collected under its gNB service to be visible to other vendors' gNBs. Even if the data is to be transparently transmitted from the target gNB to the source gNB, the standardized message structure means that this data may be interpreted by another vendor's gNB / network, which is undesirable because the data may contain confidential information about a vendor. For example, it may disclose information about the type of AI / ML model / algorithm used by a vendor, or infer information about the cell's radio configuration.

[0123] However, due to the mobility of the terminal, issues related to the aforementioned handover process may also exist after an RRC state switch or RLF (Recurrent Link Failure) occurs. For example, after the terminal moves to an RRC idle state or an RRC inactive state, it may establish or restore an RRC connection in a gNB (gNB) of another vendor. Similarly, after an RLF occurs, the terminal may rebuild the RRC connection in a gNB of another vendor.

[0124] To address data privacy issues during handover scenarios, a proposed approach is for the terminal to send a data availability indication along with a measurement report to the source gNB. If the source gNB cannot obtain the data before the handover, it can send a data deletion request to the UE. The UE can then discard the data collected under the source gNB's service based on this data deletion request, thus rendering the data unavailable to the target gNB.

[0125] However, the solutions described above for handover scenarios cannot address data privacy issues in RLF and RRC state transition scenarios. Because of RLF, the network cannot control which gNB the terminal attempts to re-establish the connection in, or if RRC reconstruction fails, the terminal may move to an RRC idle state without network control. Alternatively, due to factors such as cell congestion, the terminal may need to be quickly moved to an RRC idle / inactive state. All of these factors can cause the source gNB to be unable to obtain data in a timely manner.

[0126] Therefore, embodiments of this application provide a communication method and apparatus to solve the data privacy issues in the aforementioned RLF and RRC state transition scenarios.

[0127] Referring to Figure 3, it is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 3, the communication system includes: a terminal, a first access network device, and a second access network device, which can communicate directly or indirectly with each other.

[0128] In this embodiment, the first access network device serves as the access network device for the current serving terminal. After the terminal accesses the network where the first access network device is located, it collects data during the service or coverage period of the first access network device. This collected data is used by the first access network device to train AI / ML models until the terminal disconnects the RRC connection with the first access network device, for example, when the terminal moves to an RRC idle state or an RRC inactive state, or when the terminal experiences an RLF (Recurrent Likelihood Failure). It should be understood that the name of the first access network device is not limited in this embodiment; for example, the first access network device may also be called the source serving access network device, the source access network device, the old access network device, etc.

[0129] Data collected by a terminal during the service or coverage period of the first access network device may include data collected by the terminal within each cell covered by the first access network device. The cell where the terminal is collecting data is the terminal's serving cell, which may change based on the terminal's mobility. An access network device may cover or correspond to at least one cell.

[0130] The second access network device, serving as the access network device for the next serving terminal, is the access network device that establishes / rebuilds / restores the RRC connection after the terminal experiences an RRC state transition or an RLF (Recurrent Link Failure). It should be understood that the name of the second access network device is not limited in this embodiment; for example, it can also be called the target serving access network device, the target access network device, the new access network device, etc.

[0131] The first access network equipment and the second access network equipment can belong to different manufacturers or to the same manufacturer; there is no restriction on this.

[0132] In some scenarios, the first access network device and the second access network device are the same access network device. This application mainly relates to schemes where the first access network device and the second access network device are different access network devices. For example, in the scenario shown in Figure 2 above, the first access network device is the previous serving gNB, and the second access network device is the serving gNB.

[0133] Access network equipment, also known as RAN nodes, network devices, RAN entities, or access nodes, is located on the network side of the aforementioned communication system. It assists terminals in achieving wireless access and is a device with wireless transceiver capabilities, or a chip or chip system that can be installed in the device. Access network equipment can include, but is not limited to: base stations, evolved NodeBs (eNodeBs), access points (APs), TRPs, gNBs, and base stations in future mobile communication systems. Access network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, and wireless controllers in open-radio access networks (O-RAN) or centralized-radio access networks (C-RAN) scenarios. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of the access network device.

[0134] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs). CUs and DUs can be set up 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).

[0135] 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 O-RAN 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.

[0136] In this application embodiment, the form of the access network device is not limited. The device used to implement the function of the access network device can be a network device; it can also be a device that supports the access network device in implementing the function, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device.

[0137] In this application embodiment, the terminal is a terminal that accesses the aforementioned communication system and has wireless transceiver functionality, or a chip or chip system that can be installed in the terminal. The terminal can also be referred to as a UE, user device, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. The terminal in the embodiments of this application can be a mobile phone, tablet computer, computer with wireless transceiver functionality, 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, vehicle-mounted terminal, RSU with terminal functionality, etc. The terminal of this application may also be an on-board module, on-board component, on-board chip, or on-board unit that is built into a vehicle as one or more components or units. The vehicle can implement the method provided in this application through the built-in on-board module, on-board component, on-board chip, or on-board unit.

[0138] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal can be the terminal itself; it can also be a device that supports the terminal in implementing the functions, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0139] In this embodiment, the terminal and access network device may have AI functionality, and AI modules may be deployed in the terminal and access network device. For example, the access network device includes a CU, a DU, and a RU, and at least one of the RU, CU, and DU may also be equipped with one or more AI modules. The CU may also be divided into CU-CP and CU-UP, and one or more AI modules may be configured in the CU-CP and / or CU-UP. As another example, the access network device includes an O-CU, an O-DU, and an O-RU, and at least one of the O-RU, O-CU, and O-DU may also be equipped with one or more AI modules. The O-CU may also be divided into O-CU-CP and O-CU-UP, and one or more AI modules may be configured in the O-CU-CP and / or O-CU-UP.

[0140] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. The models of AI modules can achieve different functions depending on the parameter configurations. The models of AI modules can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or biases in the activation function), input parameters (e.g., the type and / or dimension of the input parameters), or output parameters (e.g., the type and / or dimension of the output parameters). The biases in the activation function can also be referred to as the biases of the neural network.

[0141] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0142] For example, a terminal can collect data locally or obtain data from an access network device. This data can be used as training data to train an AI model, or as inference data to perform inference using the trained AI model. The inference result can then be delivered to the access network device or used locally. Similarly, an access network device can collect data locally or obtain data from the terminal. This data can be used as training data to train an AI model, or as inference data to perform inference using the trained AI model. The inference result can then be delivered to the terminal device, network management (such as OAM), or used locally.

[0143] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0144] The communication method provided in the embodiments of this application will be described in detail below with reference to Figures 4-7.

[0145] For example, Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application. It is understood that this application uses the terminal, the first access network device, and the second access network device shown in Figure 3 as examples to illustrate the execution of this interaction, but this application does not limit the execution of the interaction.

[0146] As shown in Figure 4, the communication method includes:

[0147] S401, The first access network device sends the first information to the terminal.

[0148] Correspondingly, the terminal receives the first information from the first access network device.

[0149] The first information is used to indicate the cell list in which the terminal is allowed to retain data collected during the service of the first access network device. That is, the first information indicates the cell list, which contains cells in which the terminal is allowed to retain data collected during the service of the first access network device. In this embodiment, the collected data can also be referred to as AI / ML data, which is used for training and / or inferring AI / ML models on the network side.

[0150] The data collected by the terminal during the service period of the first access network device can refer to the data collected by the terminal within the coverage area of ​​the first access network device while the first access network device is the terminal's currently serving access network device, with the cell of the first access network device where the terminal is located at the time of data collection serving as the terminal's serving cell. Therefore, the data collected by the terminal during the service period of the first access network device can include data collected by the terminal within at least one cell of the first access network device.

[0151] After the terminal connects to the first access network device, or in other words, after the terminal establishes an RRC connection with the first access network device, the terminal is in an RRC connected state. The first access network device will then send a data collection configuration to the terminal, enabling the terminal to perform corresponding data measurements according to this configuration, thus achieving data collection. It should be understood that the data type collected is related to the AI-based application scenario; please refer to the relevant descriptions of AI-based application scenarios above.

[0152] For example, the data collection configuration is carried in an RRC reconfiguration message, that is, the first access network device sends an RRC reconfiguration message to the terminal, and the terminal receives the RRC reconfiguration message from the first access network device, which contains the data collection configuration.

[0153] The cell list in which the terminal is allowed to retain data collected during the service of the first access network device can be understood as follows: when the terminal determines that the cell it is accessing belongs to a cell in the cell list, the terminal is allowed to retain the data collected during the service of the first access network device. For cells in which the terminal is allowed to retain data collected during the service of the first access network device, the terminal can indicate the use of the collected data to the access network device corresponding to that cell through a data availability indicator, as shown in S403 below.

[0154] In some designs, the list of cells in which the terminal is allowed to retain data collected during the service of the first access network device can also be represented as the list of cells in which the terminal is allowed to forward data collected during the service of the first access network device. The permission to forward is used to indicate permission to retain and transmit. That is, the first information can be replaced with a list of cells indicating that the terminal is allowed to forward data collected during the service of the first access network device.

[0155] Since the cells in the cell list are those that allow terminals to retain or forward data collected during the service of the first access network device, the access network devices corresponding to the cells in the cell list can belong to the same vendor as the first access network device, or the cell list can include all cells of the first access network device, in order to avoid data privacy leaks. For example, the cells in the cell list can include all cells belonging to the same access network device or belonging to a DU within the same access network device, and / or include all cells of access network devices belonging to the same vendor as the first access network device.

[0156] The first information is used to indicate the cell list, and this first information includes information indicating the cells in the cell list. In some possible implementations, the cells in the cell list can be indicated by any of the following: physical cell identifier (PCI), NR cell global identifier (NCGI), public land mobile network (PLMN), or the terminal's RAN-based notification area (RNA).

[0157] In other words, the first information may include a PCI list consisting of the PCIs of each cell in the cell list, or the first information may include an NCGI list consisting of the NCGIs of each cell in the cell list, or the first information may include a PLMN list consisting of the PLMNs of the access network devices corresponding to each cell in the cell list, or the first information may include the RNA of the terminal, with each cell in the cell list included in the RNA.

[0158] Optionally, the first information obtained by the first access network device may be configured locally by the first access network device, or it may be configured by the core network element or network management system to the first access network device.

[0159] In some designs, cells in the cell list can be configured as the serving cells for the terminal in RRC connected state.

[0160] In some possible implementations, the first information may be included in any of the following messages and sent: Master Information Block (MIB) message, System Information Block (SIB) 1 message, RRC Reconfiguration message, or RRC Release message.

[0161] For example, before the terminal connects to the first access network device, the first information can be sent in a MIB message or a SIB1 message. In this case, the first access network device sends the first information in a broadcast manner. If the first information is sent in a MIB message, the cells in the cell list can be indicated by PCI; if the first information is sent in a SIB1 message, the cells in the cell list can be indicated by NCGI.

[0162] For another example, after the terminal establishes an RRC connection with the first access network device, the first information can be sent in the RRC reconfiguration message.

[0163] As another example, the first access network device may also send the first information when the trigger terminal moves (or switches) from the RRC connected state to the RRC idle state or the RRC inactive state, that is, the first information is sent in the RRC release message.

[0164] It should be understood that, in addition to being carried in the aforementioned messages, the first information can also be carried in other messages that enable the terminal to receive the first information before an RRC state transition or RLF occurs, without limitation.

[0165] Optionally, the first access network device pre-configures whether the terminal retains the data collected during the service period of the first access network device when it moves to the RRC idle state and / or the RRC inactive state, and / or when the terminal experiences an RLF.

[0166] In one possible design, the first access network device sends second information to the terminal, and the terminal receives the second information from the first access network device. The second information instructs the terminal to retain data collected during the service period of the first access network device when it moves to an RRC idle state, an RRC inactive state, or experiences an RLF (Recurrent Leak). In other words, the first access network device can be configured to retain, but not delete, the collected data when the terminal experiences an RRC state transition and / or an RLF, allowing the terminal to determine, based on the cell list indicated by the first information, whether to indicate to the access network device establishing the RRC connection that it has available data and to send the data collected during the service period of the first access network device to the re-establishing RRC connection.

[0167] Of course, in some implementations, the first access network device may also delete the data collected during the service period of the first access network device when it moves to the RRC idle state, the RRC inactive state, or when an RLF occurs, by indicating the second information. In this case, when the terminal re-establishes the RRC connection, the terminal has no available data and will not send the data collected during the service period of the first access network device to the access network device that established the RRC connection.

[0168] Optionally, the second information may also be carried in the message carrying the first information and sent therein; there is no limitation on this.

[0169] In some implementations, the first information may have the function of the second information. In this case, the first access network device does not need to send the second information to the terminal, and the terminal can retain or delete the collected data based on the first information.

[0170] Therefore, after obtaining the cell list based on the first information, the terminal saves the cell list.

[0171] S402. After the terminal moves to the RRC idle state or RRC inactive state, or after an RLF occurs, it determines the first cell for establishing an RRC connection.

[0172] During data collection within the serving cell of the first access network device, if the first access network device instructs the terminal to undergo an RRC state transition from RRC connected state to RRC idle state or RRC inactive state—for example, if the first access network device requires the terminal to move to the RRC idle state or RRC inactive state due to cell congestion—the first access network device will send an RRC release message to the terminal, causing the terminal to move to the RRC idle state or RRC inactive state according to the RRC release message. At this time, after the RRC state transition, the terminal stops collecting data but retains the data collected during the service period of the first access network device before the RRC state transition.

[0173] For RLF, after the terminal establishes an RRC connection with the first access network device, it will initiate RLF detection, such as detecting the signal quality of the physical layer, using a timer to detect RLF, etc. After determining that an RLF has occurred, the terminal will stop collecting data and retain the data collected during the service period of the first access network device before the RLF occurred.

[0174] After the terminal moves to the RRC idle state or RRC inactive state, or after an RLF occurs, the terminal will decide to re-establish the RRC connection in the cell, perform cell selection, and determine the first cell to establish the RRC connection. Before initiating the RRC connection to the first cell, the terminal will determine whether to retain the data collected during the service of the first access network device according to the cell list. If it is determined that the data should be retained, the terminal can send a data availability indication to the access network device corresponding to the first cell when or after establishing the RRC connection to indicate that the terminal has available data, that is, execute the following S403.

[0175] It should be understood that when a terminal moves to an RRC idle state or an RRC inactive state, the establishment of an RRC connection can be understood as the terminal establishing or restoring an RRC connection; when an RLF occurs, the establishment of an RRC connection can be understood as the terminal rebuilding or establishing an RRC connection.

[0176] S403. If the first cell is included in the cell list, the terminal sends a first indication message to the second access network device corresponding to the first cell.

[0177] Correspondingly, the second access network device corresponding to the first cell receives the first indication information from the terminal.

[0178] The first indication information is used to indicate that there is available data. The first indication information can be called a data availability indication, without limitation.

[0179] After the terminal determines the first cell for establishing an RRC connection, the first cell may be different from the cell where the terminal was located when the RRC state transition or RLF occurred due to the terminal's mobility. Therefore, the terminal can determine whether the first cell is included in the cell list based on the cell list indicated by the first information. For example, the terminal can determine whether the first cell belongs to the cell list based on the PCI or NCGI of the first cell, or determine whether the first cell belongs to the cell in the RNA.

[0180] If the first cell is included in the cell list, then the first cell is the cell in which the terminal is allowed to retain or forward data collected during the service of the first access network device. In this case, the terminal can retain the data collected during the service of the first access network device. At this time, the terminal sends a first indication message to the second access network device corresponding to the first cell to indicate that the terminal has available data.

[0181] When the terminal moves to the RRC idle state or the RRC inactive state, in some possible implementations, the first indication information may be sent in any of the following messages: RRC Resume Request message, RRC Setup Request message, RRC Resume Complete message, or RRC Setup Complete message.

[0182] For example, after the terminal moves to the RRC idle state, it sends an RRC establishment request message to the second access network device. This RRC establishment request message includes first indication information. Alternatively, the RRC establishment request message may not carry the first indication information, but after the RRC connection is established, the first indication information is included in the RRC establishment completion message. That is, the terminal sends an RRC establishment completion message to the second access network device, and this RRC establishment completion message includes the first indication information. As another example, after the terminal moves to the RRC inactive state, it sends an RRC recovery request message to the second access network device. This RRC recovery request message includes the first indication information. Alternatively, the RRC recovery request message may not carry the first indication information, but after the RRC connection is restored, the first indication information is included in the RRC recovery completion message. That is, the terminal sends an RRC recovery completion message to the second access network device, and this RRC recovery completion message includes the first indication information.

[0183] In the event of an RLF (Recurrent Leakage) at the terminal, in some possible implementations, the first indication information may be sent in any of the following messages: RRC Setup Request, RRC Reestablishment Request, RRC Setup Complete, or RRC Reestablishment Complete.

[0184] For example, after an RLF (Recurrent Leak) occurs, the terminal first attempts to rebuild the RRC (Recurrent Route) connection. At this time, the terminal sends an RRC rebuild request message to the second access network device. This RRC rebuild request message includes first indication information. Alternatively, the RRC rebuild request message may not carry the first indication information, but after successful RRC rebuild, the terminal includes it in the RRC rebuild completion message. That is, the terminal sends an RRC rebuild completion message to the second access network device, which includes the first indication information. As another example, if the terminal's RRC rebuild attempt fails, the terminal moves to an RRC idle state and sends an RRC establishment request message to the second access network device. This RRC establishment request message includes the first indication information. Alternatively, the RRC establishment request message may not carry the first indication information, but after successful RRC connection establishment, the terminal includes it in the RRC establishment completion message. That is, the terminal sends an RRC establishment completion message to the second access network device, which includes the first indication information.

[0185] Thus, the terminal and the second access network device (first cell) successfully complete the RRC connection, and after the second access network device receives the first instruction information, the second access network device can send a data request to the terminal to request available data for model training or inference.

[0186] Conversely, if the first cell is not included in the cell list, then the first cell is the cell where the terminal is not allowed to retain or forward data collected during the service of the first access network device. In this case, the terminal can delete or discard the data collected during the service of the first access network device. The terminal does not need to send the first instruction information to the second access network device corresponding to the first cell.

[0187] In some possible implementations, the terminal may delete or discard the data collected during the service of the first access network device immediately after determining that the first cell is not included in the cell list. That is, the terminal may check whether to delete or discard the data after each cell selection or reselection. Alternatively, the terminal may delete or discard the data collected during the service of the first access network device before establishing an RRC connection with the first cell, or it may delete or discard the data collected during the service of the first access network device after completing the establishment of an RRC connection with the first cell. There are no limitations on this.

[0188] Optionally, if the first cell is not included in the cell list, the terminal may also retain the data collected during the service of the first access network device. For example, the terminal retains the data collected during the service of the first access network device after successfully establishing an RRC connection, but the terminal will still not send the first indication information. However, the retained data can be used to deal with the situation where the terminal establishes a connection in a qualified cell in the future.

[0189] Therefore, after the terminal successfully completes the RRC connection with the second access network device (first cell), it will not send the data collected during the service period of the first access network device to the second access network device.

[0190] It should be understood that after the RRC connection is completed, the first cell is the terminal's current serving cell.

[0191] It should be understood that the terminal may also fail to establish an RRC connection with the second access network device. In this case, the terminal can reselect a cell to establish an RRC connection and perform the relevant operations as described above for the first cell.

[0192] In some possible scenarios, the first cell can be the cell where the terminal is located when the RRC state transition or RLF occurs, or the first cell and the cell where the terminal is located when the RRC state transition or RLF occurs belong to the same access network device. In this case, the first access network device and the second access network device are the same access network device.

[0193] In this embodiment, the cell list received by the terminal has a validity period. When a first event occurs, the cell list is deleted. The first event can be one of the following: deleting data collected during the service period of the first access network device, such as when the data validity period timer expires or after the terminal successfully transmits data to the network; or, powering off / shutting down; or, successfully establishing an RRC connection with the first cell; or, receiving a new data collection configuration in the first cell.

[0194] In the communication method shown in Figure 4, the terminal receives first information from the first access network device, which indicates that the terminal is allowed to retain data collected during the service of the first access network device. This allows the terminal to determine whether the first cell for establishing an RRC connection is included in the cell list indicated by the first information when moving to an RRC idle state or an RRC inactive state, or after an RLF occurs. This determines whether the data collected during the service of the first access network device needs to be retained or deleted. If the first cell is included in the cell list, the data collected during the service of the first access network device is retained, and a first indication message is sent to the second access network device corresponding to the first cell to indicate that the terminal has available data. Therefore, the privacy data of the source serving access network device is protected from leakage in scenarios involving RRC state transitions or RLF.

[0195] The communication method shown in Figure 4 will be illustrated below with specific scenarios.

[0196] For example, referring to Figure 5, taking the determination of data availability in a scenario where the terminal undergoes an RRC state transition as an example, the communication method includes:

[0197] S501. The first access network device sends an RRC Reconfiguration message to the terminal.

[0198] Correspondingly, the terminal receives an RRC reconfiguration message from the first access network device.

[0199] The RRC reconfiguration message includes data collection configuration.

[0200] After the terminal completes the RRC connection with the first access network device, the first access network device can send an RRC reconfiguration message carrying data collection configuration to the terminal to configure the terminal to collect data during the service period of the first access network device.

[0201] S502, The first access network device sends an RRC Release message to the terminal.

[0202] Accordingly, the terminal receives an RRC release message from the first access network device.

[0203] The RRC release message includes the first piece of information.

[0204] During data collection by the terminal, the first access network device may send an RRC release message to the terminal due to reasons such as cell congestion, and carry first information in the RRC release message. After receiving the RRC release message containing the first information, the terminal transitions from the RRC connected state to the RRC idle state or the RRC inactive state. The following example shows the terminal transitioning to the RRC idle state. The terminal saves the cell list indicated by the first information so as to retain the data collected during the service period of the first access network device when establishing an RRC connection with a cell in the cell list. The specific description of the first information is as described in the above embodiment and will not be repeated here.

[0205] S503, The terminal determines the first cell for establishing an RRC connection.

[0206] S504. If the first cell is included in the cell list, the terminal sends an RRC Setup Request message to the second access network device corresponding to the first cell.

[0207] Correspondingly, the second access network device receives an RRC establishment request message from the terminal.

[0208] The RRC establishment request message includes a first indication message, which indicates that there is available data. See the relevant description in the above embodiments, which will not be repeated here.

[0209] After the terminal determines that the first cell belongs to the cell list, it can send an RRC establishment request message to the second access network device, and carry the first indication information in the RRC establishment request message to request the establishment of an RRC connection, and inform the second access network device that the terminal has available data and can request data from the terminal.

[0210] If the first cell is not included in the cell list, the terminal may delete the data collected during the service of the first access network device and not carry the first indication information in the RRC establishment request message.

[0211] S505, the second access network device sends an RRC Setup message to the terminal. Correspondingly, the terminal receives the RRC Setup message from the second access network device.

[0212] S506. The terminal sends an RRC Setup Complete message to the second access network device.

[0213] Correspondingly, the second access network device receives the RRC establishment completion message from the terminal.

[0214] Based on S504 to S506, the terminal and the second access network device complete the RRC connection. After the RRC connection is successfully completed, the second access network device can initiate a data request to the terminal according to the first instruction information to request the terminal to send available data.

[0215] For example, referring to Figure 6, taking the determination of data availability in a terminal RLF scenario as an example, the communication method includes:

[0216] S601, The first access network device sends an RRC Reconfiguration message #1 to the terminal.

[0217] Accordingly, the terminal receives RRC reconfiguration message #1 from the first access network device.

[0218] RRC reconfiguration message #1 includes data collection configuration. See the description of S501 above for S601; it will not be repeated here.

[0219] S602, The first access network device sends an RRC Reconfiguration message #2 to the terminal.

[0220] Correspondingly, the terminal receives RRC reconfiguration message #2 from the first access network device.

[0221] Among them, RRC reconfiguration message #2 includes the first information.

[0222] After establishing an RRC connection with the terminal, the first access network device can send the first information to the terminal via an RRC reconfiguration message during the terminal's data collection period.

[0223] S603, the terminal has encountered an RLF (Remote Message Password).

[0224] S604. The terminal determines the first cell for establishing an RRC connection.

[0225] S605. If the first cell is included in the cell list, the terminal sends an RRC Reestablishment Request message to the second access network device corresponding to the first cell.

[0226] Correspondingly, the second access network device receives an RRC reconstruction request message from the terminal.

[0227] The RRC reconstruction request message includes first indication information.

[0228] After the terminal determines that the first cell belongs to the cell list, it can initiate an RRC reconstruction request message to the second access network device, and carry the first indication information in the RRC reconstruction request message to request the reconstruction of the RRC connection, and inform the second access network device that the terminal has available data and can request data from the terminal.

[0229] If the first cell is not included in the cell list, the terminal may delete the data collected during the service of the first access network device and not carry the first indication information in the RRC reconstruction request message.

[0230] S606, the second access network device sends an RRC Reestablishment message to the terminal.

[0231] Correspondingly, the terminal receives an RRC reconstruction message from the second access network device.

[0232] S607. The terminal sends an RRC Reestablishment Complete message to the second access network device.

[0233] Correspondingly, the second access network device receives the RRC reconstruction completion message from the UE.

[0234] Based on the above steps S605-S607, the terminal and the second access network device complete RRC reconstruction. After successful RRC reconstruction, the second access network device can initiate a data request to the terminal according to the first instruction information to request the terminal to send available data. If the terminal and the second access network device fail to successfully complete RRC reconstruction, the terminal can switch to the RRC idle state and execute the relevant operations of S504-S506 above, which will not be elaborated further.

[0235] This application considers how to ensure the privacy of the source network's data is not leaked when a terminal establishes / restores / rebuilds a connection to an access network device from a different vendor during RRC state transitions or RLF scenarios. Specifically, it can be configured to allow the terminal (e.g., through the access network device) to retain data when it moves to an RRC idle / RRC inactive state. The access network device can also configure a cell list for the terminal, allowing the terminal to forward data to cells in the cell list. When the terminal moves to an RRC idle / RRC inactive state or encounters an RLF, it remembers the previously configured cell list. When the terminal decides to establish / restore / rebuild an RRC connection in a cell, it checks whether the cell established / restored by the UE belongs to the terminal's pre-configured cell list. The terminal can check the cell based on its PCI or NCGI, or check whether the connection is established / restored / rebuilt in the same RNA. If the connection is established / restored in a cell corresponding to the pre-configured cell list, the terminal retains the collected data and indicates data availability to the network. If the connection is established / restored in another cell, the terminal discards the collected data before continuing the establishment / restore procedure and does not send a data availability indication to the new access network device / cell.

[0236] Furthermore, this application also considers the implementation of the above scheme under the O-RAN architecture. As shown in Figure 7, the access network device includes an O-DU and an O-RU. The aforementioned first information, second information, a message carrying the first information, or a message carrying the second information can be generated by the O-DU in the first access network device and sent to the O-RU in the first access network device, and then sent to the terminal by the O-RU. The first indication information, the message carrying the first indication information, and data sent by the terminal can be received by the O-DU in the second access network device, or received by the O-RU in the second access network device and then sent to the O-CU in the second access network device; there is no limitation on this. In other words, the generation or decision-making of the aforementioned information or message can be executed by the O-DU in the access network device, then sent by the O-DU to the O-RU, and finally sent out through the O-RU.

[0237] It is understood that, in the above embodiments, the methods and / or steps implemented by the terminal can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the terminal; the methods and / or steps implemented by the access network device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the access network device.

[0238] The foregoing mainly describes the solutions provided in this application. Accordingly, this application also provides a communication device for implementing the various methods in the above method embodiments. This communication device can be a terminal as described in the above method embodiments, or a device containing a terminal, or a component that can be used in a terminal, such as a chip or chip system. Alternatively, the communication device can be an access network device as described in the above method embodiments, or a device containing an access network device, or a component that can be used in an access network device, such as a chip or chip system.

[0239] It is understood that, in order to achieve the aforementioned 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, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in 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.

[0240] 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 noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0241] Taking the communication device as an example, specifically the terminal or access network device in the above method embodiments, Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 8, the communication device 800 includes a processing module 801 and a transceiver module 802. The processing module 801 is used to execute the processing functions of the terminal or access network device in the above method embodiments. The transceiver module 802 is used to execute the transceiver functions of the terminal or access network device in the above method embodiments.

[0242] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0243] In one possible design, in this embodiment of the application, the transceiver module 802 may include a receiving module and a sending module (not shown in FIG8). The sending module and the receiving module are respectively used to implement the sending and receiving functions of the communication device 800.

[0244] In one possible design, the communication device 800 may further include a storage module (not shown in FIG8) that stores programs or instructions. When the processing module 801 executes the program or instructions, the communication device 800 can perform the functions of the terminal or access network device in any of the methods shown in FIG4-FIG7.

[0245] In some embodiments, the processing module 801 involved in the communication device 800 may be implemented by a processor or processor-related circuit components, and may be a processor or processing unit; the transceiver module 802 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver unit.

[0246] For example, Figure 9 is a schematic diagram of another communication device provided in an embodiment of this application. This communication device can be a terminal or access network device as described in the above method embodiments, or it can be a chip (system) or other component or assembly that can be disposed in the terminal or access network device. As shown in Figure 9, the communication device 900 may include a processor 901, a bus 902, a communication interface 903, and a memory 904. The processor 901, the memory 904, and the communication interface 903 communicate via the bus 902. It should be understood that this application does not limit the number of processors and memories in the communication device 900.

[0247] Bus 902 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 9, but this does not indicate that there is only one bus or one type of bus. Bus 902 can include pathways for transmitting information between various components of communication device 900 (e.g., memory 904, processor 901, communication interface 903).

[0248] Processor 901 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processing unit (DSP).

[0249] The memory 904 may include volatile memory, such as random access memory (RAM). The processor 901 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0250] The communication interface 903 uses transceiver modules, such as, but not limited to, network interface cards and transceivers, to enable communication between the communication device 900 and other devices or communication networks. The memory 904 stores executable program code, which the processor 901 executes to implement the functions of the terminal or access network device in the aforementioned method embodiments. That is, the memory 904 stores instructions for executing the aforementioned communication methods.

[0251] In another aspect, embodiments of this application also provide a computer program product containing instructions, including computer program code, which, when run on a communication device, enables the communication device to execute the methods described in any of the above embodiments.

[0252] Furthermore, embodiments of this application also provide a computer-readable storage medium. This computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in any of the above embodiments.

[0253] In another aspect, embodiments of this application also provide a communication system, including a terminal and an access network device for performing the above method embodiments.

[0254] 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., digital video disks, DVDs), or semiconductor media (e.g., SSDs), etc.

[0255] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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.

[0256] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0258] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0259] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0260] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0261] 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.

[0262] 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 spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this 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 the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method characterized by comprising: The method includes: Receive first information from a first access network device, the first information being used to indicate a list of cells in which the terminal is allowed to retain data collected during the service of the first access network device; After moving to the Radio Resource Control (RRC) idle state or RRC inactive state, or after a Radio Link Failure (RLF) occurs, determine the first cell for establishing an RRC connection; If the first cell is included in the cell list, a first indication message is sent to the second access network device corresponding to the first cell. The first indication message is used to indicate that there is available data.

2. The method according to claim 1, characterized in that, The method further includes: The terminal receives second information from the first access network device, the second information being used to indicate data collected during service by the first access network device when the terminal moves to an RRC idle state, an RRC inactive state, or an RLF occurs.

3. The method according to claim 1 or 2, characterized in that, The method further includes: If it is determined that the first cell belongs to one of the cells in the cell list, the data collected during the service period of the first access network device is retained.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: If it is determined that the first cell is not included in the cell list, the data collected during the service of the first access network device is deleted.

5. The method of claim 4, wherein, The deletion of data collected during the service period of the first access network device includes: After establishing an RRC connection with the first cell, delete the data collected during the service period of the first access network device.

6. The method according to any one of claims 1-5, characterized in that, The cells in the cell list are indicated by any of the following: Physical Cell Identifier (PCI), New Radio Cell Global Identifier (NCGI), Public Land Mobile Network (PLMN), or Notification Area (RNA) of the terminal based on the Radio Access Network (RAN).

7. The method according to any one of claims 1-6, characterized in that, The method further includes: When the first event occurs, the cell list is deleted; wherein the first event is one of the following: Delete the data collected during the service period of the first access network device; or... Turn off the computer; or, An RRC connection has been successfully established with the first cell; or, A new data collection configuration was received within the first cell.

8. The method according to any one of claims 1-7, characterized in that, The first information is sent in any of the following messages: Master Information Block (MIB) message, System Information Block (SIB1) message, RRC reconfiguration message, or RRC release message.

9. The method according to any one of claims 1-8, characterized in that, In the case of moving to the RRC idle state or the RRC inactive state, the first indication information is sent in any of the following messages: RRC recovery request message, RRC establishment request message, RRC recovery complete message, or RRC establishment complete message.

10. The method according to any one of claims 1-8, characterized in that, In the event of an RLF, the first indication information is sent in any of the following messages: RRC establishment request message, RRC reconstruction request message, RRC establishment complete message, or RRC reconstruction complete message.

11. A communication method, characterized in that, The method includes: Obtain first information, the first information being used to indicate a list of cells in which the terminal is permitted to retain data collected during the service of the first access network device; The first information is sent to the terminal.

12. The method according to claim 11, characterized in that, The method further includes: Send a second message to the terminal, the second message being used to instruct the terminal to retain data collected during the service of the first access network device when it moves to an RRC idle state, an RRC inactive state, or an RLF occurs.

13. The method according to claim 11 or 12, characterized in that, The cells in the cell list are indicated by any of the following: PCI, NCGI, PLMN, or the terminal's RNA.

14. The method according to any one of claims 11-13, characterized in that, The first information is sent in any of the following messages: MIB message, SIB1 message, RRC reconfiguration message, or RRC release message.

15. A communication device, characterized in that, include: A module for performing the method as described in any one of claims 1-10, or a module for performing the method as described in any one of claims 11-14.

16. A communication device, characterized in that, include: processor; The processor is configured to run computer programs or instructions to enable the implementation of the method as described in any one of claims 1-10, or to enable the implementation of the method as described in any one of claims 11-14.

17. A communication chip, characterized in that, The chip stores instructions that, when the chip is running on a communication device, cause the method as described in any one of claims 1-10 to be implemented, or cause the method as described in any one of claims 11-14 to be implemented.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1-10, or the method as described in any one of claims 11-14.

19. A computer program product, characterized in that, It includes computer program code, which, when run on a communication device, implements the method as described in any one of claims 1-10, or the communication device implements the method as described in any one of claims 11-14.

Images