Data collection method, data collection apparatus and user equipment

Abstract

The present application discloses a data collection method, a data collection apparatus and a user equipment. The data collection method comprises: a user equipment receives first configuration information sent by a network side device, wherein the first configuration information comprises at least one of the following: first instruction information used for instructing to establish an air interface data plane protocol stack for data collection; and second instruction information used for instructing to establish an air interface data bearer for transmitting collected data.

Description

Data collection method, data collection device and user equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410389025.9 filed in China on April 1, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data collection method, a data collection device and a user equipment. Background Art

[0004] With the reduction of computing and storage costs, and the emergence of a large number of low-latency services and local area applications, the basic functions of mobile communication networks have also begun to shift from information transmission to data management and control platforms; in particular, as artificial intelligence and perception gradually become new capabilities of mobile communication networks, the demand for data collection in mobile communication networks is increasing. In the solutions provided in the related technologies, the data collection needs are mainly implemented by the user plane protocol in the communication system. When configuring data collection and reporting the collected data, the radio signaling bearer (SRB) method in the related technologies is used, that is, the interaction between user equipment and base stations can be achieved through radio resource control (RRC) signaling or non-access stratum (NAS) signaling. As the demand for data collection increases, the solutions provided in the above-mentioned related technologies can no longer meet the growing data collection needs of mobile communication networks. Summary of the Invention

[0005] The embodiments of the present application provide a data collection method, a data collection device and a user device, as well as a network-side device, a readable storage medium and a program product, to provide a technical solution that can meet the growing data collection needs of mobile communication networks.

[0006] In a first aspect, a data collection method is provided, comprising:

[0007] The user equipment receives first configuration information sent by the network side device, where the first configuration information includes at least one of the following:

[0008] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0009] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0010] Configuration parameters of the air interface data plane protocol stack;

[0011] Configuration parameters of air interface data bearer;

[0012] The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer;

[0013] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0014] The mapping relationship between high-layer data and air interface data;

[0015] Valid cell list;

[0016] Valid location area;

[0017] The current cell is valid;

[0018] Valid within the inactive RAN area;

[0019] Data collection configuration information.

[0020] In a second aspect, a data collection device is provided, comprising:

[0021] The first receiving module is configured to receive first configuration information sent by a network-side device, where the first configuration information includes at least one of the following:

[0022] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0023] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0024] Configuration parameters of the air interface data plane protocol stack;

[0025] Configuration parameters of air interface data bearer;

[0026] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0027] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0028] The mapping relationship between high-layer data and air interface data;

[0029] Valid cell list;

[0030] Valid location area;

[0031] The current cell is valid;

[0032] Valid within the inactive RAN area;

[0033] Data collection configuration information.

[0034] A third aspect provides a data collection method, comprising:

[0035] The network-side device sends first configuration information to the user equipment, where the first configuration information includes at least one of the following:

[0036] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0037] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0038] Configuration parameters of the air interface data plane protocol stack;

[0039] Configuration parameters of air interface data bearer;

[0040] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0041] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0042] The mapping relationship between high-layer data and air interface data;

[0043] Valid cell list;

[0044] Valid location area;

[0045] The current cell is valid;

[0046] Valid within the inactive RAN area;

[0047] Data collection configuration information.

[0048] In a fourth aspect, a data collection device is provided, comprising:

[0049] The first sending module is configured to send first configuration information to the user equipment, where the first configuration information includes at least one of the following:

[0050] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0051] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0052] Configuration parameters of the air interface data plane protocol stack;

[0053] Configuration parameters of air interface data bearer;

[0054] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0055] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0056] The mapping relationship between high-layer data and air interface data;

[0057] Valid cell list;

[0058] Valid location area;

[0059] The current cell is valid;

[0060] Valid within the inactive RAN area;

[0061] Data collection configuration information.

[0062] A fifth aspect provides a data collection method, comprising:

[0063] The second base station receives first configuration information sent by the first base station, where the first configuration information is sent by the first base station to the user equipment when the user equipment resides in the cell of the first base station;

[0064] The second base station generates second configuration information based on the first configuration information;

[0065] The second base station sends second configuration information to the user equipment through cell handover signaling, where the first configuration information and the second configuration information both include at least one of the following:

[0066] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0067] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0068] Configuration parameters of the air interface data plane protocol stack;

[0069] Configuration parameters of air interface data bearer;

[0070] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0071] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0072] The mapping relationship between high-layer data and air interface data;

[0073] Valid cell list;

[0074] Valid location area;

[0075] The current cell is valid;

[0076] Valid within the inactive RAN area;

[0077] Data collection configuration information.

[0078] In a sixth aspect, a data collection device is provided, comprising:

[0079] A second receiving module is configured to receive first configuration information sent by a first base station, where the first configuration information is sent by the first base station to the user equipment when the user equipment resides in a cell of the first base station;

[0080] a configuration generating module, configured to generate second configuration information based on the first configuration information;

[0081] The second sending module is configured to send second configuration information to the user equipment through cell handover signaling, where the first configuration information and the second configuration information each include at least one of the following:

[0082] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0083] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0084] Configuration parameters of the air interface data plane protocol stack;

[0085] Configuration parameters of air interface data bearer;

[0086] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0087] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0088] The mapping relationship between high-layer data and air interface data;

[0089] Valid cell list;

[0090] Valid location area;

[0091] The current cell is valid;

[0092] Valid within the inactive RAN area;

[0093] Data collection configuration information.

[0094] In a seventh aspect, a user device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the data collection method described in the first aspect are implemented.

[0095] In the eighth aspect, a network side device is provided, including a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the data collection method described in the third aspect are implemented; or the steps of the data collection method described in the fifth aspect are implemented.

[0096] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by the processor of the user device, the steps of the data collection method as described in the first aspect are implemented; or, when the program or instruction is executed by the processor of the network side device, the steps of the data collection method as described in the third aspect are implemented; or, when the program or instruction is executed by the network side device of the fifth aspect, the steps of the data collection method as described in the fifth aspect are implemented.

[0097] In the tenth aspect, a wireless communication system is provided, including: a user device and a network function, wherein the user device is the user device of the seventh aspect, and the network side device is the network side device of the eighth aspect.

[0098] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the data collection method described in the first aspect; or the steps of the data collection method described in the third or fifth aspect.

[0099] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data collection method described in the first aspect; or the steps of the data collection method described in the third or fifth aspect.

[0100] In an embodiment of the present application, by configuring data plane functions on the user equipment, such as establishing an air interface data plane protocol stack capable of independently performing data collection and establishing at least one of an air interface data bearer capable of independently performing data transmission, it is possible to avoid relying entirely on the user plane protocol in the relevant technology in the data collection and data transmission links. At least one aspect of data collection or data transmission can be executed using independent solutions, and these independent solutions can be matched with the actual needs of data collection and data transmission, thereby providing a technical solution that can meet the growing data collection needs of mobile communication networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] FIG1 shows a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0102] FIG2 is a flow chart of a data collection method according to an embodiment of the present application;

[0103] FIG3 is a flow chart of another data collection method in an embodiment of the present application;

[0104] FIG4 is a flow chart of another data collection method according to an embodiment of the present application;

[0105] FIG5 is a flow chart of another data collection method in an embodiment of the present application;

[0106] FIG6 is a schematic diagram of the architecture of a specific embodiment of this embodiment;

[0107] FIG7 is a second schematic diagram of the architecture of a specific embodiment of this embodiment;

[0108] FIG8 is a third schematic diagram of the architecture of a specific embodiment of this embodiment;

[0109] FIG9 is a flow chart of another data collection method according to an embodiment of the present application;

[0110] FIG10 is a schematic diagram of a process for collecting data when a user device is in a connected state according to an embodiment of the present application;

[0111] FIG11 is a flow chart of a data collection device according to an embodiment of the present application;

[0112] FIG12 is a flow chart of another data collection device according to an embodiment of the present application;

[0113] FIG13 is a flow chart of another data collection device according to an embodiment of the present application;

[0114] FIG14 is a flow chart of another data collection device according to an embodiment of the present application;

[0115] FIG15 is a schematic structural diagram of a user equipment according to an embodiment of the present application;

[0116] FIG16 is a schematic structural diagram of a network-side device in an embodiment of the present application. DETAILED DESCRIPTION

[0117] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0118] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe the order or precedence of the targets. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0119] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0120] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0121] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a user device 110 and a network-side device 120. The user device 110 may be a mobile phone, a tablet computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (a household appliance with wireless communication capabilities, such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side device. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit, etc. It should be noted that the specific type of user equipment 110 is not limited in the embodiments of the present application.

[0122] The network-side device 120 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS), or a wireless fidelity (WiFi) node. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to the target technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0123] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.But not limited to at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network equipment in the NR system is introduced as an example, and the specific type of the core network equipment is not limited.

[0124] With the increasing demand for data collection in mobile communication networks, solutions provided in related technologies, such as the Minimization of Drive Tests (MDT) measurement result collection method or the Quality of Experience (QoE) measurement collection method, are mainly implemented by the user plane protocol in the communication system. When configuring data collection and reporting the collected data, the Signaling Radio Bearer (SRB) method in the related technology is utilized, that is, it is transmitted through RRC signaling or NAS signaling. Because the user plane protocol is not designed specifically for data collection, there are a series of problems when using the user plane for data collection. For example, RRC signaling requires mandatory ASN.1 encoding and decoding, and NAS signaling also requires encoding and decoding of the corresponding signaling format. In addition, encryption and integrity protection functions are mandatory. Therefore, processing information related to data collection requires a large amount of processing resources and a long delay. Furthermore, SRB in related technologies only supports a maximum data length of approximately 9000 bytes. Data exceeding this length requires signaling segmentation, which is redundant at the signaling level and at the L2 processing level, reducing efficiency. Furthermore, SRB defaults to the highest transmission priority and a very high guaranteed bit rate, disrupting the transmission and resource utilization of other normal services when the collected data is unimportant. During handover, SRB resets and clears the cache, causing all data collection to be interrupted once the user device switches. Retransmission at the target cell not only reduces resource efficiency but also increases latency, significantly undermining system efficiency.

[0125] In response to the technical problems existing in the above-mentioned related technologies, the embodiments of the present application provide a solution. The main idea is to configure data plane functions on the user equipment, such as establishing an air interface data plane protocol stack that can independently perform data collection and establishing at least one of air interface data bearers that can independently perform data transmission. This can avoid relying entirely on the user plane protocol in the related technology in the data collection and data transmission links, and at least one aspect of data collection or data transmission can be executed using independent solutions, and these independent solutions can be matched with the actual needs of data collection and data transmission. In addition, for at least one of the above-mentioned establishment of an air interface data plane protocol stack capable of independently performing data collection and establishment of an air interface data bearer capable of independently performing data transmission, it may usually not be a basic feature of the user equipment. In an embodiment of the present application, the user equipment can be configured with parameters when the network side deems it necessary, and a corresponding technical solution is provided in an embodiment of the present application; at the same time, it is also taken into account that the user equipment's own capabilities and communication capabilities are different when it is in a connected state, an idle state, and an inactive state. Some capabilities of the user equipment in the latter two states will be limited, so the configuration parameters when the user equipment performs data collection or data transmission will also be different; and whether it is necessary to reconfigure the parameters for data collection and transmission when the user equipment undergoes cell switching, the embodiments of the present application provide corresponding technical solutions.

[0126] The following is a detailed description of the technical solution of the data collection method provided in the embodiments of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0127] FIG2 is a flow chart of a data collection method according to an embodiment of the present application. This step may be performed by a data collection device, which may be set in a user device. As shown in FIG2 , the method includes the following steps:

[0128] Step 201: Receive first configuration information sent by a network-side device. The first configuration information includes at least one of the following:

[0129] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0130] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0131] Configuration parameters of the air interface data plane protocol stack;

[0132] Configuration parameters of air interface data bearer;

[0133] The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer;

[0134] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0135] The mapping relationship between high-layer data and air interface data;

[0136] Valid cell list;

[0137] List of valid location areas;

[0138] The current cell is valid;

[0139] Valid within the inactive RAN area;

[0140] Data collection configuration information.

[0141] The embodiments of the present application can be applicable to application scenarios in which data plane functions are established in three states: connected state, idle state, and inactive state. The network side device can be a first base station. In some cases, such as for a user device in an idle state, it can also implement data plane functions by receiving public signaling. At this time, the network side can be other network side devices that can send public signaling. The technical solution of this application scenario can be referred to the embodiment shown in the subsequent Figure 10. In other embodiments, the first base station is used as the network side device for explanation.

[0142] Therefore, in the embodiment shown in Figure 2, the first base station can send first configuration information to the user equipment when determining to establish at least one of an air interface data plane protocol stack for data collection and an air interface data bearer for transmitting the collected data with the user equipment. At the same time, the first configuration information can directly include at least one of the above two indications. The first base station can be the first configuration information determined based on the capability information of the user equipment, which will be introduced in subsequent embodiments.

[0143] There are three specific situations:

[0144] The first case is when the first configuration information only includes an instruction to establish an air interface data plane protocol stack for data collection. In this case, an independent air interface data plane protocol stack needs to be established on the user equipment to replace the traditional user plane protocol, such as the RRC layer for data collection. As for the transmission of the collected data, that is, the data collection results, it can still be transmitted using the signaling in the related technology, such as SRB signaling.

[0145] The second situation is that when the first configuration information only includes an instruction to establish an air interface data bearer for transmitting collected data, it is necessary to establish an air interface data bearer with the base station, including but not limited to the first base station, on the user side, to replace the traditional SRB signaling to transmit data. However, for the data collection function, the original data plane protocol can still be used. The air interface data bearer can be established between the user equipment and the base station, and a corresponding air interface protocol bearer is also established on the base station, so that the data sent by the user equipment can be processed and used on the base station, thereby realizing localized processing and use of the collected data. The data transmission is usually carried out by the user plane protocol, where the data uploaded by the user equipment reaches the base station, and the base station uses a transparent transmission method to directly send it to other network side devices, and cannot be processed and used locally. The embodiment of the present application can obviously support this situation where the base station performs processing and use.

[0146] In the third case, the first configuration information indicates to establish the above-mentioned air interface data plane protocol stack and air interface data bearer at the same time, providing a new data collection and transmission solution.

[0147] In some embodiments, if the user equipment receives the first configuration information, it may perform an operation of establishing at least one of an air interface data plane protocol stack and an air interface data bearer according to the first configuration information.

[0148] Specifically, as shown in FIG3 , FIG3 is a flow chart of another data collection method in an embodiment of the present application. As shown in FIG3 , the method may include the following steps:

[0149] Step 203: When the first configuration information includes an instruction to establish an air interface data plane protocol stack, the user equipment establishes the air interface data plane protocol stack according to the configuration parameters of the air interface data plane protocol stack. In the embodiment of the present application, the air interface data plane protocol stack established in this step may specifically be a data service application (DSAP) entity.

[0150] Step 204: When the first configuration information includes an instruction to establish an air interface data bearer, the user equipment establishes an air interface data bearer according to the configuration parameters of the air interface data bearer; in this embodiment of the present application, the air interface data bearer established in this step may specifically be a Collection Radio Bearer (CRB).

[0151] According to the above three situations included in the first configuration information, at least one of steps 203 and 204 in the embodiment of the present application can also be selected for execution.

[0152] In the embodiment shown in Figure 2 or Figure 3 of the present application, the user equipment is directly instructed to establish an air interface data plane protocol stack and / or an air interface data bearer through the first configuration information. Other parameter information, on the one hand, can be used as parameters required to establish the above two, and can be sent simultaneously through the first configuration information, or in other ways, such as using a pre-configured or default configuration method, and sent to the user equipment by other messages. This time, only the establishment indication needs to be sent; on the other hand, the above parameters can also be used as an implicit indication to establish the air interface data plane protocol stack and the air interface data bearer. When receiving the above parameters, at least one of the air interface data plane protocol stack and the air interface data bearer can also be established.

[0153] Specifically, the configuration parameters of the above-mentioned air interface data plane protocol stack are mainly used to limit the establishment of the air interface data plane protocol stack. In the embodiment of the present application, the number of air interface data plane protocol stacks established on the user device can be one or more. When the number of air interface data plane protocol stacks is multiple, different types of data can be collected separately. The air interface data plane protocol stack in the embodiment of the present application mainly collects various types of data generated by the user device, such as data collected by sensors on the user device, data generated by software running on the user device, data calculated by computing resources on the user device, etc. This is not limited in the embodiment of the present application. The air interface protocol stack in the embodiment of the present application can collect data generated in the above-mentioned various situations and generate corresponding data packets, and then send them to the corresponding data bearer. Based on the functions that the above-mentioned air interface data plane protocol stack needs to complete, its configuration parameters may include whether to carry header data (Header), the value range and length of each field in the header data, the maximum supported data packet size, whether to support data segmentation, whether to support in-order delivery, and the data quality of service (QoS) flow identifier or parameters mapped to the air interface data plane protocol stack.

[0154] In an embodiment of the present application, an air interface data plane protocol stack can be established according to the above configuration parameters. In some scenarios, the establishment can also be represented by starting, enabling, activating or enabling.

[0155] The above-mentioned configuration parameters of the air interface data bearer are mainly used to limit the establishment of the air interface data bearer. For the air interface data bearer in the embodiment of the present application, one or more air interface data bearers can also be established according to actual needs; and after a smaller number of air interface data bearers are established, more air interface data bearers can be added according to actual data transmission needs. In the embodiment of the present application, the configuration parameters for the air interface data bearer may include whether security operations are required, such as encryption and / or integrity protection; whether header compression is required; maximum transmission delay parameters, such as a discard timer; supported transmission modes, such as AM or UM transmission mode; sequence number (SN) length in the L2 layer data packet; and may also include parameters such as the length of the L2 layer reordering timer, transmission priority, parameters related to the transmission guarantee bit rate, and data processing methods during switching.

[0156] The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer is mainly for the case where there are multiple air interface data bearers. It is necessary to consider which air interface data bearer the data collected by the air interface data plane protocol corresponds to. Especially when there are multiple air interface data plane protocol stacks, the above mapping relationship can enable more orderly data transmission.

[0157] The mapping relationship between the data collected by the wireless resource control layer and the air interface data bearer is mainly when the air interface data plane protocol stack is established, or even if the air interface data plane protocol stack is established, some data is still collected by the wireless resource control layer. At this time, a mapping relationship between it and the air interface data bearer is required, so that the collected data can be transmitted smoothly when there are multiple air interface data bearers.

[0158] The mapping relationship between high-level data and air interface data bearer, whether it is the RRC layer or the air interface data plane protocol stack in the embodiment of the present application, can be the L2 layer. In some cases, other higher-level data can also be transmitted through the established multiple air interface data bearers. For example, some high-level data is related to the data collected by the air interface data plane protocol stack, and it is preferably sent at the same time. At this time, there will be a need to transmit other high-level data. At this time, a mapping relationship between high-level data and air interface data bearer can be established to smoothly transmit high-level data.

[0159] Data collection configuration information, which may include information such as the type of data to be collected, how to measure and collect, and how to report data. In an embodiment of the present application, the data collection configuration information can implicitly indicate that the user equipment needs to establish any one of the air interface data plane protocol stack or air interface data bearer.

[0160] In addition, in an embodiment of the present application, when a user device is able to interact with a base station to obtain corresponding first configuration information, the state of the user device may generally be in a connected state. In addition to the connected state, the user device may also be in an idle state or an inactive state. Therefore, for the parameters included in the above-mentioned first configuration information, it may be set explicitly or implicitly, and it may be specified in which specific state of the user device it is valid. Alternatively, the above-mentioned first configuration information may include parameters that are valid in different states, and even for the same parameter, different parameter values ​​may be set in different states.

[0161] In addition, during the movement of the user equipment, there may be cell switching or reselection. For example, the cell of the first base station in the present application is the current cell of the user equipment. If the user equipment sends a cell switching or reselection, the base station communicating with it may switch or reselect to the second base station. In an embodiment of the present application, for the case of cell switching or reselection, the effective range of the above-mentioned first configuration information can be set. For example, the current cell can be set to be valid, then the above-mentioned first configuration information is only valid in the current cell. If cell switching or reselection occurs, since the air interface data plane protocol stack and the air interface bearer are not basic features of the user equipment, the air interface data plane protocol stack and the air interface data bearer established by the above-mentioned first configuration information will also be deleted, and it is necessary to resend the configuration information in the new cell by a new base station, such as the second base station, to re-establish at least one of the air interface data plane protocol stack and the air interface data bearer.

[0162] In some cases, a valid cell list may be further configured so that the first configuration information is valid in all cells shown in the list. After the user equipment establishes at least one of the air interface data plane protocol stack and the air interface data bearer according to the first configuration information, even if a cell handover or reselection occurs, at least one of the air interface data plane protocol stack and the air interface data bearer established above can still be retained;

[0163] In some cases, a valid location area can also be configured so that the first configuration information is valid within the valid location area. After the user equipment establishes at least one of the air interface data plane protocol stack and the air interface data bearer according to the first configuration information, even if a cell handover or reselection occurs, and the user equipment switches or reselects to another cell, as long as it is still within the above-mentioned valid location area, the at least one of the air interface data plane protocol stack and the air interface data bearer can still be retained; if it exceeds the above-mentioned valid location area, at least one of the established air interface data plane protocol stack and the air interface data bearer will be deleted. It should be noted that any of the current cell validity, valid cell list, or valid location area configured in the first configuration information can be set to apply in which state, for example, it can be applicable in at least one state such as connected state, idle state, and inactive state. In the set state, if a cell handover or reselection occurs due to the movement of the user equipment, the air interface data plane protocol stack and / or air interface data bearer will still be retained or deleted according to the above-mentioned setting. The cell handover in each embodiment of the present application can also be referred to as cell selection. For the inactive state, it can be assumed that the first configuration information of the user equipment can be continuously used within the inactive RAN area. When the user equipment is in the inactive state, it is equivalent to being in a RAN area. When moving within the RAN area, the base station of any cell can obtain the context configuration of the user equipment at any time, thereby continuing to support the user equipment to maintain at least one of the established air interface data plane protocol stack and air interface data bearer valid when it is in the inactive state. Specifically, in some embodiments, for example, when the user equipment is in the connected state, if the user equipment is handed over from the first base station to the second base station, the first configuration information includes that the current cell is valid, or the cell of the second base station is not in the valid cell list, or the cell of the second base station is not in the valid location area, then the second base station will determine whether to configure the data plane protocol for the user equipment based on its own support for the air interface data plane protocol stack and / or air interface data bearer. If it supports the above two, it will also send second configuration information. Specifically, for the user equipment, it may include the steps of:

[0164] The user equipment receives second configuration indication information sent by the second base station, where the second configuration information includes at least one of the following:

[0165] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0166] The second indication information is used to instruct establishment of an air interface data bearer for transmitting the collected data.

[0167] In this embodiment, the second configuration information further includes at least one of the following:

[0168] Configuration parameters of the air interface data plane protocol stack;

[0169] Configuration parameters of air interface data bearer;

[0170] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0171] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0172] The mapping relationship between high-layer data and air interface data;

[0173] Valid cell list;

[0174] Valid location area;

[0175] The current cell is valid;

[0176] Valid within the inactive RAN area;

[0177] Data collection configuration information.

[0178] The second configuration information sent by the second base station can be equivalent to the first configuration information sent by the above-mentioned first base station. However, since the first configuration information sent by the first base station becomes invalid with the cell switching, the second configuration information needs to be resent to indicate the establishment of at least one of an air interface data plane protocol stack for data collection and an air interface data bearer for transmitting the collected data on the user equipment.

[0179] The content included in the second configuration information, the solution executed by the user equipment based on the second configuration information, and the introduction related to the first configuration information in the above embodiment are not repeated in this embodiment.

[0180] In an embodiment of the present application, the user equipment usually receives the first configuration information sent by the first base station in the connected state, and then establishes at least one of the above-mentioned air interface data plane protocol stack and air interface data bearer according to the first configuration information. If the user equipment is released from the connected state to the idle state or the inactive state, it can be selected according to the actual situation to use any one of the above-mentioned established air interface data plane protocol stack and air interface data bearer for data collection and transmission, or other parameters for data collection and transmission, or directly give up data collection.

[0181] In the above-mentioned embodiment of the present application, it may be that the user equipment receives the first configuration information of the first base station when it is in a connected state, thereby configuring the data plane function, that is, establishing at least one of the air interface data plane protocol stack and the air interface data bearer; then, in addition to being in a connected state, the user equipment may also be released to an idle state or an inactive state.

[0182] For user equipment in an idle state, network-side equipment is usually unable to obtain the capability information of the user equipment, making it difficult to accurately configure the data plane functions of the user equipment in this state. Typically, when the user equipment is released from the connected state to the idle state, at least one of the air interface data plane protocol stack and the air interface data bearer is established in the connected state according to the first configuration information provided in the above embodiment, thereby enabling the execution of some long-term, non-real-time data measurement and data collection tasks. Specifically, if the user equipment is in the connected state when the air interface data plane protocol stack and the air interface data bearer are established, then when the user equipment is released from the connected state to the idle state, the method executed by the user equipment may include at least one of the following:

[0183] The user equipment deletes, releases or retains the air interface data plane protocol stack;

[0184] The user equipment collects data according to the data collection configuration parameters in the idle state;

[0185] The user equipment deletes, releases or reserves at least part of the air interface data bearer.

[0186] Specifically, the user equipment deletes, releases, or retains the air interface data plane protocol stack, which may include the following situations:

[0187] First, the user equipment may delete, release or retain the air interface data plane protocol stack according to a preset default configuration by way of a default configuration;

[0188] Second, if the user equipment has configuration parameters of an air interface data plane protocol stack that is valid in the idle state, the air interface data plane protocol stack may be retained; otherwise, the air interface data plane protocol stack may be deleted or released.

[0189] The configuration parameters of the air interface data plane protocol stack are parameters included in the first configuration information, and can be set to be valid in which user equipment states, for example, set to be valid only in the connected state, or set to be valid in the connected state and the idle state. If the latter is the case, the user equipment can retain the air interface data plane protocol stack. If the former is the case, the air interface data plane protocol stack can be deleted or released;

[0190] Third, it can be set that when the user equipment is released to the idle state, it still receives an instruction from the network side device, instructing the user equipment to delete, release or retain the air interface data plane protocol stack, and the user equipment can execute according to the instruction.

[0191] In some other embodiments, if the user equipment retains the air interface data plane protocol stack through the above technical solution, default configuration parameters can be set in the user equipment to adjust the configuration parameters of the air interface data plane protocol stack to pre-set default configuration parameters;

[0192] Alternatively, in some embodiments, if the user equipment retains at least part of the air interface data bearers through the above technical solution, the configuration parameters of at least part of the air interface data bearers are adjusted to preset default configuration parameters.

[0193] In an embodiment of the present application, whether the user equipment deletes, releases or retains at least part of the air interface data bearer may be determined based on the default configuration, the user equipment having configuration parameters of the air interface data bearer that is valid in the idle state, or the received instructions from the network side device.

[0194] In addition to the situations described in the above embodiments, there are some feasible technical solutions, namely, special parameters can be configured specifically for data collection of user devices in idle state. For example, when the user device is released to the idle state, data collection can be performed according to the data collection configuration parameters in the idle state. The data collection configuration parameters in the idle state can be stored in the above-mentioned first configuration information, or can be sent separately in other ways.

[0195] The technical solution provided by the above-mentioned embodiments of the present application can explicitly or implicitly indicate in the first configuration information generated to the user equipment in the connected state that the above-mentioned configuration is applicable to the idle state, that is, the IDLE state, which can also be called the non-connected state; when the user equipment is released from the connected state to the IDLE state, the previous data plane function configuration can be retained, such as retaining the DSAP entity and / or CRB, and continuing to execute the data collection requirements applicable to the IDLE state.

[0196] Releasing the device to the IDLE state to perform some long-term, non-real-time data measurement and data collection tasks is a relatively cost-effective approach, both in terms of power consumption of the user device and resource loss of the network-side device. The user device continues to perform data measurement and data collection tasks in the IDLE state according to the dedicated configuration required for data collection previously obtained in the connected state. At this time, the DSAP of the user device can continue to work. The only parameters used by the user device side in the DSAP can continue to maintain the configuration in the previous connected state, while all parameters related to interaction with the network-side device in the DSAP can be reset to default parameter values. Because for user devices in the IDLE state, the network-side device generally does not save the user device's dedicated configuration context information, the network-side device can only use the default parameters to interact with the user device. For example, if data collection configuration is performed for DSAP, the UE is required to measure a certain measurement quantity, and there is a set measurement period or measurement trigger threshold and reporting rules, etc., the user equipment can continue to execute. When the user equipment needs to report to the network side, it can indicate which measurement result it is, and optionally carry the measurement period or measurement trigger threshold, reporting reason, etc., and when the reporting format has certain configurable parameters, in order to report quickly and concisely, the user equipment needs to adopt the default format, because the base station of the current user equipment service cell interprets it in the default format, and can obtain the correct reporting data. As for the CRB that transmits the data collection results, in order for the user equipment to use the small data transmission function in the IDLE state, or to quickly report after the user equipment enters the connected state, the CRB can use the default configuration, such as the default logical channel identifier (LCID) and the default L2 parameters. The advantage of this is that for the user equipment that has just entered the connected state, there is no need for the network side device to configure a special bearer, and the default LCID and L2 parameters can be used to report the data collection results. The network side device can identify this as a CRB bearer through the default LCID, which carries the DSAP data collection results and uses the default L2 parameters for reception, avoiding the signaling overhead and delay of the process of reconfiguring the RRC. Of course, if there is data with security requirements, it can be reported using the CRB after security activation. Or, in this case, if the user equipment has just entered the connected state from the IDLE and needs to quickly report the DSAP data collection results, it can use existing bearers such as SRB1 for reporting.

[0197] In some embodiments, a user device can be released from the connected state to an inactive state, or INACTIVE state. The INACTIVE state is a state intermediate between the idle and connected states. In this state, the user device performs mobility management and other operations similar to those of a user device in the IDLE state. However, all data plane function configurations of the user device in the connected state can be retained or suspended. This suspension can also be referred to as deactivation. This allows for faster data transmission when the connection is restored and facilitates the completion of small data transfers without transitioning to the connected state.

[0198] Therefore, inactive user equipment can more conveniently maintain the air interface data plane protocol stack and air interface data bearer configuration when in connected state, such as DSAP and CRB configuration. The network side equipment will perform context management for each inactive user equipment. Even if the user equipment moves to a new cell, when initiating connection recovery, the network side equipment can also correctly forward the user equipment configuration data between the cell base station storing the user equipment context and the base station of the current serving cell through the inter-base station process to meet transmission requirements.

[0199] Specifically, if the user equipment is in a connected state when the air interface data plane protocol stack and the air interface data bearer are established, the user equipment is released from the connected state to the inactive state, and the method executed by the user equipment may include at least one of the following:

[0200] The user equipment suspends, deactivates or retains the air interface data plane protocol stack;

[0201] The user equipment collects data according to the data collection configuration parameters in the inactive state;

[0202] The user equipment suspends, deactivates, or reserves at least some air interface data bearers.

[0203] Specifically, the user equipment suspends, deactivates, or retains the air interface data plane protocol stack, which may include the following situations:

[0204] First, the user equipment can suspend, deactivate or retain the air interface data plane protocol stack according to the preset default configuration by means of default configuration;

[0205] Second, if the user equipment has configuration parameters of the air interface data plane protocol stack that are valid in the inactive state, the air interface data plane protocol stack may be retained; otherwise, the air interface data plane protocol stack may be suspended or deactivated.

[0206] The configuration parameters of the air interface data plane protocol stack are parameters included in the first configuration information, and can be set to be valid in which user equipment states, for example, set to be valid only in the connected state, or set to be valid in the connected state and the inactive state. If the latter is the case, the user equipment can retain the air interface data plane protocol stack. If the former is the case, the air interface data plane protocol stack can be suspended or deactivated;

[0207] Third, it is possible to set the user equipment to be released to an inactive state and still receive instructions from the network side device, instructing the user equipment to suspend, deactivate or retain the air interface data plane protocol stack, and the user equipment can execute according to the instructions.

[0208] In some other embodiments, if the user equipment retains the air interface data plane protocol stack through the above technical solution, default configuration parameters can be set in the user equipment to adjust the configuration parameters of the air interface data plane protocol stack to preset default configuration parameters;

[0209] Alternatively, in some embodiments, if the above technical solution enables the user equipment to retain at least part of the air interface data bearers, the configuration parameters of at least part of the air interface data bearers are adjusted to preset default configuration parameters.

[0210] In an embodiment of the present application, whether the user equipment suspends, deactivates or retains at least part of the air interface data bearer can also be determined based on the default configuration method, the user equipment has configuration parameters of the air interface data bearer that is valid in the inactive state, or the instructions received from the network side device.

[0211] In addition to the situations described in the above embodiments, there are some feasible technical solutions, namely, special parameters can be configured for data collection of user devices in the inactive state. For example, when the user device is released to the inactive state, data collection can be performed according to the data collection configuration parameters in the inactive state. The data collection configuration parameters in the inactive state can be stored in the above-mentioned first configuration information, or can be sent separately in other ways.

[0212] In an embodiment of the present application, an inactive user device can achieve the continuation of relevant configurations by retaining the air interface data plane protocol stack, namely the DSAP entity, thereby avoiding the continuous reconfiguration process caused by the user device state transition, and saving signaling overhead; when the inactive user device has effective relevant configurations for data collection in an inactive state or other non-connected state, the inactive user device retains the DSAP even if it is also in an active state; or, deactivates or suspends the DSAP, but this allows the user device to still perform specified data collection work when it returns to a connected state, providing data collection for network side devices on demand with less power consumption and signaling overhead.

[0213] When the user equipment is released, it can be explicitly instructed by the first configuration information provided by the network side to deactivate, suspend or retain the DSAP, and the device can perform the corresponding action; otherwise, the default action can be performed. The network side can explicitly instruct the user equipment to behave when it returns to the inactive state, which can be done according to actual needs. If the user equipment in the inactive state continues to execute the configuration for data collection in the non-connected state such as the inactive state; specifically, it can be explicitly or implicitly indicated in the first configuration information whether it is applied to the inactive state, such as explicitly distinguishing the collection parameters for the inactive state, or explicitly indicating that the configuration parameters provided for the connected state can also be used for the inactive state, and the implicit indication method can be, for example, the corresponding data plane function configuration, such as the air interface data plane protocol stack and the air interface data bearer are not released, which means that it can continue to be executed in the inactive state.

[0214] In an embodiment of the present application, an inactive user device performs relevant data measurement or data collection according to the data collection-related configuration that is still valid in this state, and caches the measurement results as data collection results; the inactive user device retains the CRB in order to avoid unnecessary reconfiguration due to state transition; the inactive user device can also suspend the corresponding CRB. The reason for suspension is that in the normal inactive state, the user device does not need to transmit the data collection results of the data collection to the network measurement device, and the CRB may not be used, so it can be suspended.

[0215] In the above-mentioned case where the user equipment is released from the connected state to the idle state or the inactive state, it is possible that the user equipment retains the air interface data plane protocol stack, and the user equipment retains at least part of the air interface data bearer. At this time, based on the mapping relationship between the air interface data plane protocol stack and the air interface data bearer already configured in the above-mentioned first configuration information, in this case, the mapping relationship between the air interface data plane protocol stack and at least part of the air interface data bearer can continue to be retained, such as the mapping relationship between DSAP and CRB. The inactive user equipment retains the mapping relationship between DSAP and CRB, which can still achieve the purpose of saving configuration overhead and quickly transmitting data.

[0216] In addition, in some embodiments, whether the user equipment is in the idle state or the inactive state, it may select or reselect a cell during mobility. If the user equipment in the above embodiment retains the air interface data plane protocol stack, then during the cell selection or reselection process, it may also select or reselect a cell that supports the air interface data plane protocol stack, because only cells that support this function can process the air interface data bearers collected by the air interface data plane protocol stack for transmission. And / or, if the user equipment in the above embodiment retains at least some air interface data bearers, then during the cell selection or reselection process, it may also select or reselect a cell that supports the air interface data bearers, thereby avoiding erroneous packet deletion in cells that do not support the air interface data bearers due to the inability to collect data. In order to enable the user equipment to select or reselect a cell that supports the air interface data plane protocol stack, or select or reselect a cell that supports the air interface data bearers, the priority of the cell may be increased, for example, by setting a high priority for the cell that supports the air interface data plane protocol stack and / or the cell that supports the air interface data bearers, so that the user equipment can successfully select or reselect the cell, thereby increasing the probability of subsequent successful reporting.

[0217] Regarding how the user equipment in the above embodiment obtains the capabilities of other surrounding cells, that is, whether it supports at least one of the air interface data plane protocol stack and / or air interface data bearer, it can be that the network side device sends a cell capability indication, optionally, it can be sent through public signaling; at this time, the user equipment can receive the cell capability indication sent by the network side device through public signaling, and the cell capability indication is used to indicate whether the cell supports at least one of the air interface data plane protocol stack and / or air interface data bearer, thereby performing the above-mentioned selection or reselection.

[0218] In an embodiment of the present application, a first data reporting condition for the user device to report the collected data may also be set. When the first data reporting condition is met, the user device will enter a connected state to report the data or use small data transmission to report the data. If the user device enters a connected state, the air interface data plane protocol stack and / or air interface data bearer established in the above embodiment will be reused for data reporting. At the same time, the mapping relationship between the air interface data plane protocol stack and the air interface data bearer will be retained to quickly report the results, and security operations will be performed according to actual needs. Alternatively, in one embodiment, small data transmission may be used for data reporting, thereby improving the efficiency of data transmission.

[0219] The first data reporting condition in the above embodiment of the present application may include but is not limited to at least one of the following:

[0220] Event triggering conditions;

[0221] Periodic trigger conditions;

[0222] Leave the current cell;

[0223] Leaving the valid location area;

[0224] Leave the cell in the valid cell list.

[0225] The event triggering condition can be a certain triggering event set according to the task of user device data collection, such as collecting certain data, or collecting certain data exceeding a pre-set threshold, which can trigger data reporting.

[0226] Or in some other cases, a periodic reporting method may be used, that is, a certain time period is set, and data is reported every time the corresponding time period is reached.

[0227] In some other embodiments, for example, when the effective area of ​​the first configuration information is specifically configured, that is, it is configured to be effective in the current cell, or a valid cell list is configured, or a valid location area is configured, then for the above-mentioned idle or inactive user equipment, when it leaves the current cell, leaves the cell in the current valid cell list, or leaves the valid location area, it can be considered that the first data reporting condition is triggered, and the collected data needs to be reported. In other cases, data reporting can be performed according to event triggering conditions or periodic triggering conditions.

[0228] Although the first data reporting condition for data reporting is described in this embodiment based on the user equipment being in an idle state or an inactive state, those skilled in the art will understand that for a user equipment that has always been in a connected state, if it is configured to be valid in the current cell, or configured with a valid cell list, or configured with a valid location area, if it leaves the current cell, leaves a cell in the current valid cell list, or leaves the valid location area, it can be considered that the first data reporting condition has been triggered and data reporting can be performed. Leaving the current cell, leaving a cell in the current valid cell list, or leaving the valid location area as the first data reporting condition can effectively prevent the user equipment from affecting data reporting after the air interface data bearer configured according to the first configuration information is deleted, suspended, or deactivated. It can be used together with the time trigger condition and the periodic trigger condition to ensure that the data collected by the user equipment is reported reasonably and effectively. At the same time, the user equipment can delete the data that cannot be reported.

[0229] In the above embodiments of the present application, the data collection solution provided by the present application is mainly described from the user equipment side. Correspondingly, for the network device side, such as the first base station mentioned above, the technical solution implemented by it will be described in the following embodiments. Figure 4 is a flow chart of another data collection method in the embodiment of the present application, as shown in Figure 4, including the following steps:

[0230] Step 401: A first base station sends first configuration information to a user equipment. The first configuration information includes at least one of the following:

[0231] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0232] The second indication information is used to instruct establishment of an air interface data bearer for transmitting the collected data.

[0233] Configuration parameters of the air interface data plane protocol stack;

[0234] Configuration parameters of air interface data bearer;

[0235] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0236] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0237] The mapping relationship between high-layer data and air interface data;

[0238] Configure the valid cell list;

[0239] Configure a list of valid location areas;

[0240] The current cell is valid;

[0241] Valid within the inactive RAN area;

[0242] Data collection configuration information.

[0243] Specifically, this step corresponds to the embodiment shown in Figure 2 above, and can enable the first base station to send a first configuration information to the user equipment when determining to establish at least one of an air interface data plane protocol stack for data collection and an air interface data bearer for transmitting the collected data with the user equipment. At the same time, the first configuration information can include at least one of the above two indications, specifically including three situations, namely, the first configuration information only includes an indication to establish an air interface data plane protocol stack for data collection, the first configuration information only includes an indication to establish an air interface data bearer for transmitting the collected data, or the first configuration information simultaneously indicates to establish the above-mentioned air interface data plane protocol stack and air interface data bearer. For details, please refer to the embodiment shown in Figure 2 above.

[0244] In addition, as described in the above embodiment, the air interface data plane protocol stack and the air interface data bearer are not basic features of the user equipment, so they need to be configured when used. However, the capabilities of user equipment are not the same. Some user equipment do not have the basic capabilities to establish the air interface data plane protocol stack and the air interface data bearer. In this case, the base station does not need to send the first configuration information to it. Therefore, before the base station sends the above-mentioned first configuration information to the user equipment, it can also obtain the capability information of the user equipment, and then determine whether it is necessary to send the first configuration information to it based on the capability information of the user equipment. Figure 5 is a flow chart of another data collection method in an embodiment of the present application, as shown in Figure 5, which includes the following steps:

[0245] Step 402: The first base station obtains capability information of the user equipment, where the capability information of the user equipment includes whether the user equipment supports at least one of an air interface data plane protocol stack and / or an air interface data bearer.

[0246] In this step, the capability information of the user equipment acquired by the first base station mainly refers to whether the user equipment supports data plane functions, that is, whether it supports the relevant air interface data plane protocol stack and whether it supports air interface data bearer, and the specific support capabilities when supporting the above two. Specifically, the capability information of the user equipment may include at least one of the following:

[0247] Whether the user equipment supports the air interface data plane protocol stack;

[0248] Configuration parameters of the air interface data plane protocol stack supported by the user equipment;

[0249] Whether the user equipment supports air interface data bearer;

[0250] Configuration parameters of air interface data bearers supported by the user equipment;

[0251] The maximum number of air interface data bearers supported by the user equipment.

[0252] Specifically, in this step, when the user equipment accesses, the first base station queries and reports the data plane function-related capability information to the first base station together with other capability information of the user equipment during the initial capability query phase. The capability information can be queried independently or triggered by an event. An event trigger is an event triggered by other network-side devices, such as a core network entity or a third-party device. As described in the above embodiment, the air interface data plane protocol stack can be DSAP, and the air interface data bearer can be CRB.

[0253] Step 403: The first base station generates first configuration information according to the capability information of the user equipment.

[0254] After acquiring the capability information of the user equipment, the first base station can learn the capability information of the user equipment and can generate first configuration information matching the capability information according to the capability information.

[0255] Step 401: A first base station sends first configuration information to a user equipment.

[0256] Specifically, in this step, the first base station sends the first configuration information to the user equipment, which can be sent through a message in the relevant technology or a newly added message. The signaling in the relevant technology can be RRC dedicated signaling (RRC dedicated), such as RRC configuration signaling (RRC Reconfiguration) to send the above-mentioned first configuration information, thereby realizing the configuration of only one DSAP entity or CRB on the user equipment.

[0257] In some embodiments, the event triggering initiated by the core network entity or the third-party device, that is, before the above step 402, may also include the following situations:

[0258] The first base station receives a first data collection request sent by a core network entity or a third-party device, where the first data collection request includes a target user equipment;

[0259] In this case, the core network entity or the third-party device hopes to initiate a data collection configuration or request to the target user equipment through the first base station. For example, for the core network entity, it can be that the core network entity sends the above-mentioned first data receipt request to the first base station. For the third-party device, it can first send the above-mentioned first data receipt request to the first base station, and the above-mentioned first data collection request includes the target user equipment, that is, the user equipment that has been selected for data collection configuration or request. For the first base station, in order to smoothly transmit data and collect data with the user equipment, it also needs to establish at least one of the air interface data plane protocol stack and air interface data bearer on the local air interface, that is, at least one of the above-mentioned DSAP entity or CRB.

[0260] Or in another case, the following steps may also be included:

[0261] The first base station receives a second data collection request sent by the core network entity or the third-party device;

[0262] The first base station determines a target user equipment based on the second data collection request.

[0263] In this case, the core network entity or the third-party device initiates the configuration or request for data collection to the first base station, and does not specify the target user equipment. For example, for the core network entity, it can be that the core network entity sends the above-mentioned second data receipt request to the first base station. For the third-party device, it can first send the above-mentioned second data receipt request to the first base station, and the above-mentioned first data collection request does not include the target user equipment. The first base station needs to determine the target user equipment. At the same time, for the first base station, in order to smoothly transmit data and collect data with the user equipment, it also needs to establish at least one of the air interface data plane protocol stack and the air interface data bearer on the local air interface, that is, at least one of the above-mentioned DSAP entity or CRB.

[0264] After being triggered by the network side device or the third-party device through the above two situations, the first base station can start querying the capability information of the user equipment, and can send the first configuration information to the user equipment indicating the data plane function.

[0265] The core network entity in the embodiment of the present application may be, for example, an operations, administration, and maintenance (OAM) entity, and the third-party device therein may also be referred to as a third-party node.

[0266] In some embodiments, the user equipment may undergo cell handover from the first base station to the second base station. In this case, the embodiment may further include:

[0267] The first base station sends the above-mentioned first configuration information to the second base station, that is, it can send the first configuration information for configuring the data plane function of the user equipment to the second base station, so that the second base station can continue to configure the data plane function of the first base station according to the above-mentioned first configuration information.

[0268] As described above, in the above embodiments of the present application, the data plane function is not a basic feature of the user equipment. Therefore, the base station can configure it when necessary. For example, the first configuration information can be sent to the user equipment in combination with the embodiment shown in Figure 4 or Figure 5 above to configure the data plane function on the user equipment, that is, to establish at least one of the air interface data plane protocol stack and the air interface data bearer. The operations performed on the user equipment can refer to the contents of the embodiment shown in Figure 2 or Figure 3.

[0269] The following describes, in conjunction with the contents shown in FIG. 2 to FIG. 5 , how the base station configures the data plane function for the user equipment in the connected state.

[0270] Specifically, the base station may use RRC dedicated signaling, such as RRC reconfiguration signaling, to send the first configuration information, and instruct the user equipment to establish at least one of the DSAP and the CRB in the first configuration information;

[0271] In some cases, such as when the demand for data collection on the user device is relatively simple, or when the demand has a large overlap with the configuration process of data collection using the RRC layer in the related technology, such as measurement configuration, the RRC layer in the related technology can be directly used to perform data collection configuration and result processing. However, for this part of the collected data, it can also use CRB for data transmission to meet the specific requirements of the collected data transmission, such as priority, bit rate guarantee, security and switching processing.

[0272] Specifically, Figure 6 is an architectural diagram of a specific embodiment of this embodiment. As shown in Figure 6, the user equipment can include, from bottom to top, a physical layer (Physical Layer, PHY), a data link layer, i.e., an L2 layer, also referred to as a Lower L2, a Higher L2 layer to enhance the processing capability of the L2 layer, and an upper RRC layer. As described above, the data collection function can still be completed by the RRC layer, and only a CRB1 is added in parallel with the traditional SRB (SRB1) for transmitting data for data transmission.

[0273] In some cases, one or more DSAPs may be established based on the first configuration information. In this case, one or more CRBs may be established based on the defined configuration information. Alternatively, in some cases, if no CRB is established, the RRC signaling or NAS signaling in the relevant technology may be used to complete the transmission of the data collected by the DSAP. In the case where one or more CRBs are established, the configuration or results of the data collected by the DASP may be mapped to one or more CRBs for carrying. The specific mapping relationship may be configured by a network-side device, such as the base station mentioned above, or may be determined by other simple agreements such as preset or default, such as mapping DSAPs and CRBs one to one in sequence.

[0274] If the user device establishes multiple DSAPs based on the first configuration information, each DSAP can perform different types of data collection and result processing. For example, DSAP1 can perform perception-related data collection and result processing, DSAP2 can perform AI-related data collection, DSAP3 can perform data collection and result processing related to perception use case 1, DSAP4 can perform data collection and result processing related to perception use case 2, DSAP5 can perform data collection related to AI use case 1, and DSAP6 can perform data collection and result processing related to AI use case 1, etc. Each DSAP is then mapped to one or more CRBs for data carrying. Generally speaking, a CRB is not configured to carry data collected by multiple DSAPs.

[0275] Specifically, for the case of setting only one DSAP or multiple DSAPs, it can be shown in Figure 7 or Figure 8.

[0276] Figure 7 is a second architectural diagram of a specific embodiment of this embodiment. As shown in Figure 7, the difference from Figure 6 is that a DSAP is provided at the same layer as the RRC layer, and the data collection function is completed by the DSAP, and the collected data can be collected by one or more CRBs. Figure 7 shows a situation including CRB1-CRB3 (CRB1-3), a total of 3 CRBs.

[0277] Figure 8 is a third architectural diagram of a specific embodiment of this embodiment. As shown in Figure 8, the difference from Figure 7 is that multiple DSAPs are located at the same layer as the RRC layer, and the data collection function is completed by the DSAP, and the multiple DSAPs also complete data transmission by different CRBs. Specifically, for the data collected by the first DSAP, it can be transmitted by CRB1-CRB3 (CRB1-3), and for the data collected by the second DASP, it can be transmitted by CRB4 and CRB5 (CRB4-5).

[0278] In the embodiment of the present application, there may be an interactive interface between the RRC layer and the DSAP, so that the DSAP is equivalent to a sublayer of the RRC layer, which is used to undertake certain data collection requirements configuration and result processing. In some cases, the DSAP and the RRC layer can also cooperate, for example, the RRC layer performs the data collection requirements configuration, and the DSAP performs the result processing. The result processing can be the result of the data collection. In order to facilitate the identification of the results, the DSAP can also share the results with the RRC layer for further use by the RRC layer. For example, in one case, the existing measurement configuration of the RRC layer can complete the data collection requirements configuration, and the data collection requirements can be directly performed using RRC signaling, such as sending the first configuration information in the above embodiment. Since there are special transmission requirements for the results, they can be transmitted to the DSAP on the base station side through the CRB configured on the user equipment; or in some cases, for example, in order to speed up the configuration of data collection, the RRC layer can carry the data collection configuration before or at the same time as the DSAP is established, and the subsequent results are collected through the DSAP.

[0279] In addition, as recorded in the embodiment shown in Figure 5 above, the data collection demand may be a data collection demand from the core network or a third-party node. Therefore, the DSAP or RRC layer in this application may also carry data collection configuration and data collection results from the core network entity or the third-party node. The data collection configuration and data reception results are directly transmitted end-to-end between the user equipment and the above-mentioned core network entity or the third-party node. The DSAP or RRC layer may be encapsulated and transmitted in a container manner. In particular, it may carry routing information so that the data collection configuration and data reception results can be correctly transmitted to the core network node or RRC layer.

[0280] For user equipment that supports data plane functions, if a cell handover occurs from a first base station to a second base station in a connected state, the first base station can send relevant configuration information of the data plane function of the user equipment to the second base station. For the second base station of the cell after the handover, the specific configuration of the air interface data plane protocol stack and air interface data bearer of the user equipment can be understood based on the above-mentioned first configuration information, which is conducive to reconfiguring the above-mentioned user equipment. Figure 9 is a flow diagram of another data collection method in an embodiment of the present application, such as can be executed in a data collection device, and specifically can be executed in a second base station, as shown in Figure 9, including the following steps:

[0281] Step 901: A second base station receives first configuration information sent by a first base station. Specifically, the first configuration information is sent by the first base station to a user equipment when the user equipment resides in a cell of the first base station.

[0282] Step 902: The second base station generates second configuration information based on the first configuration information.

[0283] Since the first configuration information is generated by the first base station after learning the capability information of the user equipment, the second base station can refer to the first configuration information to generate the second configuration information when configuring data plane functions for the user equipment.

[0284] Step 903: The second base station sends second configuration information to the user equipment. The first configuration information and the second configuration information each include at least one of the following:

[0285] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0286] The second indication information is used to instruct establishment of an air interface data bearer for transmitting the collected data.

[0287] In this step, the second base station may send the second configuration information to the user equipment directly through cell switching signaling, for example, when the cell is switched, or signaling in other related technologies, such as the RRC dedicated signaling (RRC dedicated) described in the above embodiment, so that the user equipment can select at least one of the air interface data plane protocol stack for data collection and the air interface data bearer for transmitting the collected data according to the second configuration information.

[0288] The first configuration information and the second configuration information mentioned above also include at least one of the following:

[0289] Configuration parameters of the air interface data plane protocol stack;

[0290] Configuration parameters of air interface data bearer;

[0291] The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer;

[0292] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0293] The mapping relationship between high-layer data and air interface data;

[0294] Valid cell list;

[0295] Valid location area;

[0296] The current cell is valid;

[0297] Valid within the inactive RAN area.

[0298] For the introduction of the first configuration information in this embodiment, reference may be made to the records in the above embodiment. For the introduction of the second configuration information, which is the same as the first configuration information, reference may also be made to the records in the above embodiment, and no further details will be given in the embodiments of this application.

[0299] In some embodiments, in the case where the first configuration information includes an area where the configuration parameters are valid, when switching from the first base station to the second base station in this embodiment occurs, if the effective restrictive constraints of the current cell, the effective cell list and the effective location area are configured, then when the cell switching occurs, a judgment will be made based on the above-mentioned effective restrictive constraints, such as whether to leave the current cell, whether to leave the cell in the valid cell list, or whether to leave the valid location area. If so, at least one of the air interface data plane protocol stack and the air interface data bearer originally established according to the first configuration information will be invalidated, and then the new base station, such as the second base station, will resend the second configuration information to reconfigure data collection and transmission.

[0300] If a cell switch occurs, but the cell still belongs to the valid cell list or is located in the valid location area, the previous configuration of at least one of the air interface data plane protocol stack and the air interface data bearer will continue to be effective, the relevant measurement and data collection actions will continue, and the air interface data bearer will continue to be used for data transmission; optionally, the second base station after switching can explicitly indicate in the switching command that the data plane function configured by the first base station continues to be effective. Of course, in some cases, some invalid configurations can also be deleted. For the configuration that continues to be effective, the relevant measurements and data collection will continue to be performed.

[0301] In addition, for the data results collected during the measurement and data collection process after the first base station is configured with the data plane function, if there is any data that has not been reported or has not been successfully reported to the first base station, it can be processed in two ways:

[0302] One approach is to default that the data collection results are only valid in the current cell. Therefore, once a cell handover occurs, all data results collected in the cell are invalidated by default, and the relevant cache is deleted. The air interface data plane protocol stack and air interface data bearers, such as DSAP and CRB, are reset and cleared.

[0303] The second approach is to continuously transmit the aforementioned data collection results across multiple cells. For example, the first configuration information may include a valid location area or a valid cell list. When a user switches within the valid location area or valid cell list, the data collection results may be continuously transmitted. Alternatively, the handover command may explicitly indicate that after the handover, at least one of the air interface data plane protocol stack and air interface data bearer, i.e., DSAP and / or CRB, is reestablished, while simultaneously retaining caches, state variables, etc., and retransmitting data collection results that were not successfully transmitted within the cell of the first base station, thereby maintaining service continuity and reliability requirements for the data collection results. For an inactive user equipment, it may be assumed that the first or second configuration information of the user equipment can be continuously used within the inactive RAN area. When the user equipment is in an inactive state, it is equivalent to being in a RAN area. When the user equipment moves within the RAN area, the base station of any cell can obtain the user equipment's context configuration at any time, thereby continuing to support the user equipment in maintaining at least one of the established air interface data plane protocol stack and air interface data bearer validity when in an inactive state.

[0304] In the above embodiment of the present application, if the user equipment is configured with data plane functions in the connected state, then when it is released to the idle state, the above data plane functions can also be transferred to it, that is, at least one of the air interface data plane protocol stack and the air interface data bearer is retained. However, in some cases, if the user equipment is not configured with the above data plane functions when it is released to the connected state, the embodiment of the present application also provides a corresponding technical solution. Figure 10 is a schematic diagram of the process of data collection when the user equipment is in the connected state in an embodiment of the present application, as shown in Figure 10, including the following steps:

[0305] Step 1001: A user equipment in an idle state receives third configuration information sent by a network-side device through public signaling. The third configuration information may be a special case of the first configuration information in the embodiment shown in FIG. 2 , and includes less information. Specifically, the third configuration information includes at least one of the following:

[0306] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0307] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0308] Data collection configuration information.

[0309] The data collection method provided in the example of the present application is a technical solution for establishing a data plane function on a user device in an idle state. For the user device in the idle state, the third configuration information sent by the network side device is received through public signaling. The above-mentioned public signaling includes but is not limited to system message block (System Information Block, SIB) signaling or new public control signaling, such as data collection control channel (Data Collection Control Channel, DCCCH) signaling, sending relevant public configuration indications or collection configuration-related information content, wherein the public configuration indication may be an instruction for the user device to establish at least one of an air interface data plane protocol stack and an air interface data bearer, and the collection configuration-related information content may be data collection configuration information, including information such as the type of data to be collected, how to measure and collect, and how to report data.

[0310] Since it is an instruction sent through public signaling, it is different from the first configuration information in the above embodiment in that it can instruct the user equipment to establish the data plane function through less data, while the user equipment in the idle state can establish the air interface data plane protocol stack and / or the air interface data bearer based more on the default configuration parameters. In some cases, if the third configuration information indicates the establishment of an air interface data plane protocol stack for data collection, the corresponding air interface data plane protocol stack will be established on the user equipment. If the third configuration information indicates the establishment of an air interface data bearer for transmitting the collected data, the corresponding air interface data bearer will be established on the user equipment. Alternatively, in some cases, the user equipment can directly collect and report data according to the data collection configuration information, and then establish at least one of the above-mentioned air interface data plane protocol stack and air interface data bearer according to pre-set parameters. Through any of the above methods, the functions of data collection and data transmission can be implemented on the user equipment, thereby meeting the network side equipment's requirements for using the idle state user equipment for data collection.

[0311] In the embodiment of the present application, for the case of cell handover, the valid range of the third configuration information can be set, wherein the third configuration information can further include at least one of the following:

[0312] The current cell is valid;

[0313] Valid cell list;

[0314] List of valid location zones.

[0315] If the above-mentioned current cell is valid, then the above-mentioned third configuration information is only valid in the current cell. If a cell switching occurs, since the air interface data plane protocol stack and air interface bearer are not basic features of the user equipment, the air interface data plane protocol stack and air interface data bearer established by the above-mentioned third configuration information will also be deleted, and the data collection configuration information will also become invalid.

[0316] In some cases, a valid cell list can also be configured so that the third configuration information is valid in the cells shown in the list. After the user equipment establishes at least one of the air interface data plane protocol stack and the air interface data bearer according to the third configuration information, even if a cell switch occurs and switches to other cells, at least one of the above-established air interface data plane protocol stack and the air interface data bearer can still be retained and will not become invalid until the user equipment switches to other cells outside the valid cell list; the same requirement applies to data collection configuration information, which is valid in the cells in the valid cell list and invalid in the cells outside the valid cell list.

[0317] In some cases, the valid location area can also be configured so that the third configuration information is valid within the valid location area. After the user equipment establishes at least one of the air interface data plane protocol stack and the air interface data bearer according to the third configuration information, even if a cell switch occurs and switches to another cell, as long as it is still within the above-mentioned valid location area, at least one of the established air interface data plane protocol stack and the air interface data bearer can still be retained; if it exceeds the above-mentioned valid location area, it will cause the deletion of at least one of the established air interface data plane protocol stack and the air interface data bearer; the same requirement applies to the data collection configuration information, which is valid within the valid location area and invalid outside the valid location area.

[0318] In addition, in some embodiments, for the above-mentioned idle state user equipment, it is possible to select or reselect a cell during the movement process. In order to enable the user equipment to continue to use the data plane function, during the cell selection or reselection process, it is also possible to select or reselect a cell that supports the air interface data plane protocol stack; and / or, it is also possible to select or reselect a cell that supports air interface data bearer. And in order to enable the user equipment to successfully select or reselect the above-mentioned cell, the priority of the cell of this category can be increased, for example, setting the cell that supports the air interface data plane protocol stack to have a high priority, and / or, setting the cell that supports air interface data bearer to have a high priority, so that the user equipment can successfully select or reselect the above-mentioned cell for residence.

[0319] Regarding how the user equipment in the above embodiment obtains the capabilities of other surrounding cells, that is, whether it supports at least one of the air interface data plane protocol stack and / or the air interface data bearer, it can be that the network side device sends a cell capability indication through public signaling. These public signalings can also be, for example, the above-mentioned SIB signaling or DCCCH signaling. At this time, the user equipment can receive the cell capability indication sent by the network side device through public signaling. The cell capability indication is used to indicate whether the cell supports at least one of the air interface data plane protocol stack and / or the air interface data bearer, thereby performing the above-mentioned selection or reselection.

[0320] In an embodiment of the present application, a second data reporting condition may be set for the user equipment to report the collected data. When the second data reporting condition is met, the user equipment will enter a connected state to report the data or use small data transmission to report the data. If the user equipment enters a connected state, it may use the air interface data bearer established in the above embodiment, or use one of RRC signaling or NAS signaling in the related art to report the data; or in one embodiment, it may also use small data transmission to report the data.

[0321] The second data reporting condition in the above embodiment of the present application may include but is not limited to at least one of the following:

[0322] Event triggering conditions;

[0323] Periodic trigger conditions;

[0324] Leave the current cell;

[0325] Leaving the valid location area;

[0326] Leave the cell in the valid cell list.

[0327] The event triggering condition can be a certain triggering event set according to the task of user device data collection, such as collecting certain data, or collecting certain data exceeding a pre-set threshold, which can trigger data reporting.

[0328] Or in some other cases, a periodic reporting method may be used, that is, a certain time period is set, and data is reported every time the corresponding time period is reached.

[0329] In some other embodiments, for example, when the effective area of ​​the third configuration information is specifically configured, that is, it is configured to be effective in the current cell, or a valid cell list is configured, or a valid location area is configured, then for the above-mentioned idle or inactive user equipment, when it leaves the current cell, leaves the cell in the current valid cell list, or leaves the valid location area, it can be considered that the second data reporting condition is triggered, and the collected data needs to be reported. In other cases, data reporting can be performed according to event triggering conditions or periodic triggering conditions.

[0330] In addition, if the user equipment leaves the current cell, leaves a cell in the current valid cell list, or leaves the valid location area, the user equipment may also delete at least one of the air interface data plane protocol stack and the air interface data bearer configured according to the third configuration information. At the same time, the user equipment may delete data that has not been reported according to the above solution.

[0331] For the embodiments of the present application, the validity of the above-mentioned valid cell list or valid location range means that within the relevant cell or location range, the network side device and the user equipment will have the same data plane function configuration information, and the user equipment can use the previous relevant configuration to perform data collection work and the reporting process of data collection results. When the user equipment leaves the valid cell or valid location area, in general, the relevant data plane function configuration on the user equipment will immediately become invalid, and the collected data in the cache can be cleared. Optionally, before leaving the above-mentioned valid cell or valid range, the user equipment can report the data collection results to the network side device for the last time to facilitate the effective use of the collected data, or the network side device can also set periodic reporting or event-triggered reporting in the process of configuring using the first configuration information, so as to ensure that the base station within the valid cell or valid location range periodically obtains the data collected by the user equipment, and for the user equipment outside the above-mentioned valid cell or valid location range, the collected data can be deleted.

[0332] FIG11 is a schematic diagram of a data collection device according to an embodiment of the present application, which is capable of executing the method shown in FIG2 . As shown in FIG11 , the device includes a first receiving module 11 , which is configured to receive first configuration information sent by a network-side device. The first configuration information includes at least one of the following:

[0333] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0334] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0335] Configuration parameters of the air interface data plane protocol stack;

[0336] Configuration parameters of air interface data bearer;

[0337] The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer;

[0338] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0339] The mapping relationship between high-layer data and air interface data;

[0340] Valid cell list;

[0341] Valid location area;

[0342] The current cell is valid;

[0343] Valid within the inactive RAN area;

[0344] Data collection configuration information.

[0345] In some embodiments, it further includes:

[0346] An establishment module is used to, when the first configuration information includes an instruction to establish an air interface data plane protocol stack, the user equipment establishes the air interface data plane protocol stack according to the configuration parameters of the air interface data plane protocol stack; when the first configuration information includes an instruction to establish an air interface data bearer, the user equipment establishes the air interface data bearer according to the configuration parameters of the air interface data bearer.

[0347] In some embodiments, the establishing module is specifically configured to establish at least one data service application entity, or to establish at least one radio network bearer.

[0348] In some embodiments, the apparatus further comprises at least one of the following:

[0349] A first processing module, configured to delete, release or retain the air interface data plane protocol stack;

[0350] A second processing module is used to collect data according to the data collection configuration parameters in the idle state;

[0351] The third processing module is configured to delete, release or retain at least part of the air interface data bearer.

[0352] In some embodiments, the first processing module is specifically configured to perform at least one of the following:

[0353] When the user equipment has configuration parameters of the air interface data plane protocol stack that are valid in the idle state, retain the air interface data plane protocol stack; otherwise, delete or release the air interface data plane protocol stack;

[0354] The user equipment deletes, releases, or retains the air interface data plane protocol stack according to an instruction received when the user equipment is released to the idle state;

[0355] The user equipment deletes, releases or retains the air interface data plane protocol stack according to a preset default configuration.

[0356] In some embodiments, it further includes:

[0357] A first parameter adjustment module is configured to adjust the configuration parameters of the air interface data plane protocol stack to preset default configuration parameters; and / or,

[0358] In some embodiments, if the user equipment retains at least part of the air interface data bearer, the method further includes:

[0359] The second parameter adjustment module is configured to adjust the configuration parameters of at least part of the air interface data bearer to preset default configuration parameters.

[0360] In some embodiments, if the state of the user equipment is released to an inactive state, the method further includes at least one of the following:

[0361] a fourth processing module, configured to suspend, deactivate or retain the air interface data plane protocol stack;

[0362] A fifth processing module, configured to collect data according to the data collection configuration parameters in the inactive state;

[0363] The fifth processing module is configured to suspend, deactivate or reserve at least part of the air interface data bearer.

[0364] In some embodiments, the fourth processing module specifically performs at least one of the following:

[0365] When the user equipment has configuration parameters of the air interface data plane protocol stack that are valid in the inactive state, retain the air interface data plane protocol stack; otherwise, suspend or deactivate the air interface data plane protocol stack;

[0366] The user equipment suspends, deactivates or retains the air interface data plane protocol stack according to an instruction received when the user equipment is released to the inactive state, or the user equipment suspends, deactivates or retains the air interface data plane protocol stack according to a preset default configuration.

[0367] In some embodiments, if the user equipment retains the air interface data plane protocol stack, the method further includes:

[0368] A third parameter adjustment module is configured to adjust the configuration parameters of the air interface data plane protocol stack to preset default configuration parameters; and / or,

[0369] If the user equipment retains at least part of the air interface data bearer, the method further includes:

[0370] The fourth parameter adjustment module is configured to adjust configuration parameters of at least part of the air interface data bearer to preset default configuration parameters.

[0371] In some embodiments, if the user equipment retains the air interface data plane protocol stack and the user equipment retains at least part of the air interface data bearer, the method further includes:

[0372] The mapping relationship retaining module is used to retain the mapping relationship between the air interface data plane protocol stack and the at least part of the air interface data bearer.

[0373] In some embodiments, it further includes:

[0374] A selection or reselection module is configured to select or reselect a cell that supports the air interface data plane protocol stack when the user equipment retains the air interface data plane protocol stack; and / or,

[0375] When the user equipment reserves at least part of the air interface data bearer, a cell supporting the air interface data bearer is selected or reselected.

[0376] In some embodiments, it further includes:

[0377] The data reporting module is configured to enter a connected state to report data or to use small data transmission to report data when a first data reporting condition is met.

[0378] In some embodiments, the first data reporting condition includes at least one of the following:

[0379] Event triggering conditions;

[0380] Periodic trigger conditions;

[0381] Leave the current cell;

[0382] Leaving the valid location area;

[0383] Leave the cell in the valid cell list.

[0384] In some embodiments, it further includes:

[0385] The capability indication receiving module is used to receive a cell capability indication sent by a network side device through public signaling, where the cell capability indication is used to indicate whether the cell supports at least one of an air interface data plane protocol stack and / or an air interface data bearer.

[0386] In some embodiments, the system further includes: a second receiving module configured to receive second configuration information sent by the second base station after the user equipment is handed over from the first base station to the second base station, wherein the second configuration information includes at least one of the following:

[0387] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0388] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0389] Configuration parameters of the air interface data plane protocol stack;

[0390] Configuration parameters of air interface data bearer;

[0391] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0392] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0393] The mapping relationship between high-layer data and air interface data;

[0394] Valid cell list;

[0395] Valid location area;

[0396] The current cell is valid;

[0397] Valid within the inactive RAN area;

[0398] Data collection configuration information.

[0399] FIG12 is a schematic diagram of the structure of another data collection device according to an embodiment of the present application, which is capable of executing the method according to the embodiment shown in FIG4 . As shown in FIG12 , the data collection device includes a first sending module 21, which is configured to send first configuration information to a user equipment. The first configuration information includes at least one of the following:

[0400] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0401] The second indication information is used to instruct establishment of an air interface data bearer for transmitting the collected data.

[0402] Configuration parameters of the air interface data plane protocol stack;

[0403] Configuration parameters of air interface data bearer;

[0404] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0405] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0406] The mapping relationship between high-layer data and air interface data;

[0407] Valid cell list;

[0408] Valid location area;

[0409] The current cell is valid;

[0410] Valid within the inactive RAN area;

[0411] Data collection configuration information.

[0412] In some embodiments, it further includes:

[0413] a capability acquisition module, configured to acquire capability information of the user equipment before sending the first configuration information to the user equipment, wherein the capability information of the user equipment includes whether the user equipment supports at least one of an air interface data plane protocol stack and / or an air interface data bearer;

[0414] The configuration information generating module is configured to generate the first configuration information according to the capability information of the user equipment.

[0415] In some embodiments, the capability information of the user equipment includes at least one of the following:

[0416] Whether the user equipment supports the air interface data plane protocol stack;

[0417] Configuration parameters of the air interface data plane protocol stack supported by the user equipment;

[0418] Whether the user equipment supports air interface data bearer;

[0419] Configuration parameters of the air interface data bearer supported by the user equipment;

[0420] The maximum number of air interface data bearers supported by the user equipment.

[0421] In some embodiments, it further includes:

[0422] A first request receiving module is configured to receive a first data collection request sent by a core network entity or a third-party device, where the first data collection request includes a target user equipment; or

[0423] A second request receiving module, configured to receive a second data collection request sent by a core network entity or a third-party device;

[0424] The first base station determines a target user equipment based on the second data collection request.

[0425] In some embodiments, it further includes:

[0426] The establishing module is used to establish at least one of an air interface data plane protocol stack and an air interface data bearer on a local air interface.

[0427] In some embodiments, it further includes:

[0428] The configuration information sending module is configured to send the first configuration information to the second base station after the user equipment is switched from the first base station to the second base station.

[0429] FIG13 is a schematic structural diagram of another data collection device in an embodiment of the present application, which is capable of executing the method of the embodiment shown in FIG9 . As shown in FIG13 , the data collection device includes a second receiving module 31, a configuration generating module 32, and a second sending module 33, wherein the second receiving module 31 is used to receive first configuration information sent by a first base station, where the first configuration information is sent by the first base station to the user equipment when the user equipment resides in the cell of the first base station; the configuration generating module 32 is used to generate second configuration information based on the first configuration information; and the second sending module 33 is used to send the second configuration information to the user equipment through cell handover signaling, where the first configuration information and the second configuration information each include at least one of the following:

[0430] The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection;

[0431] The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data;

[0432] Configuration parameters of the air interface data plane protocol stack;

[0433] Configuration parameters of air interface data bearer;

[0434] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0435] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0436] The mapping relationship between high-layer data and air interface data;

[0437] Valid cell list;

[0438] Valid location area;

[0439] The current cell is valid;

[0440] Valid within the inactive RAN area;

[0441] Data collection configuration information.

[0442] Figure 14 is a structural diagram of another data collection device in an embodiment of the present application, which is capable of executing the method of the embodiment shown in Figure 9. As shown in Figure 14, the data collection device includes a third receiving module 41, and the third receiving module 41 is used to receive third configuration information sent by the network side device through public signaling. The third configuration information includes at least one of the following: an indication of establishing an air interface data plane protocol stack for data collection; an indication of establishing an air interface data bearer for transmitting collected data; and data collection configuration information.

[0443] In some embodiments, the third configuration information further includes at least one of the following:

[0444] Valid cell list;

[0445] List of valid location areas;

[0446] The current cell is valid.

[0447] In some embodiments, the system further includes a selection or reselection module configured to perform at least one of the following:

[0448] The user equipment selects or reselects a cell that supports the air interface data plane protocol stack;

[0449] The user equipment selects or reselects a cell that supports air interface data bearing.

[0450] In some embodiments, the cell supporting the air interface data plane protocol stack selected or reselected by the user equipment has a high priority; and / or the cell supporting the air interface data bearer selected or reselected by the user equipment has a high priority.

[0451] In some embodiments, it further includes:

[0452] The data reporting module is configured to enter a connected state to report data or to report data using small data transmission when a second data reporting condition is met.

[0453] In some embodiments, the second data reporting condition includes at least one of the following:

[0454] Event triggering conditions;

[0455] Periodic trigger conditions;

[0456] Leave the current cell;

[0457] Leaving the valid location area;

[0458] Leave the cell in the valid cell list.

[0459] The device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 10 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0460] The present application also provides a user device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiments shown in Figures 2 and 10. This user device embodiment corresponds to the above-mentioned user device side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this user device embodiment and can achieve the same technical effect. Specifically, Figure 15 is a schematic diagram of the hardware structure of a user device implementing an embodiment of the present application.

[0461] The user equipment 1500 includes but is not limited to: a radio frequency unit 1501, a network module 1502, an audio output unit 1503, an input unit 1504, a sensor 1505, a display unit 1506, a user input unit 1507, an interface unit 1508, a memory 1509 and at least some of the components of the processor 1510.

[0462] Those skilled in the art will appreciate that user equipment 1500 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to processor 1510 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The user equipment structure shown in Figure 15 does not constitute a limitation of the user equipment. The user equipment may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0463] It should be understood that in an embodiment of the present application, the input unit 1504 may include a graphics processing unit (GPU) 15041 and a microphone 15042, and the graphics processor 15041 processes image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1506 may include a display panel 1061, and the display panel 15061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1507 includes a touch panel 15071 and at least one of other input devices 15072. The touch panel 15071 is also called a touch screen. The touch panel 15071 may include two parts: a touch detection device and a touch controller. Other input devices 15072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0464] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 1501 may transmit the data to the processor 1510 for processing. Furthermore, the radio frequency unit 1501 may send uplink data to the network-side device. Typically, the radio frequency unit 1501 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0465] The memory 1509 can be used to store software programs or instructions and various data. The memory 1509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1509 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1509 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0466] Processor 1510 may include one or more processing units. Optionally, processor 1510 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1510.

[0467] The processor 1510 is configured to receive first configuration information sent by a first base station, where the first configuration information includes at least one of the following:

[0468] Instructing to establish an air interface data plane protocol stack for data collection;

[0469] Instructing to establish an air interface data bearer for transmitting the collected data;

[0470] Configuration parameters of the air interface data plane protocol stack;

[0471] Configuration parameters of air interface data bearer;

[0472] The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried;

[0473] The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer;

[0474] The mapping relationship between high-layer data and air interface data;

[0475] Valid cell list;

[0476] Valid location area;

[0477] The current cell is valid;

[0478] Valid within the inactive RAN area;

[0479] Data collection configuration information.

[0480] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method user equipment side embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0481] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 4 and 9. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0482] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 16, network-side device 1600 includes an antenna 161, a radio frequency device 162, a baseband device 163, a processor 164, and a memory 165. Antenna 161 is connected to radio frequency device 162. In the uplink direction, radio frequency device 162 receives information via antenna 161 and sends the received information to baseband device 163 for processing. In the downlink direction, baseband device 163 processes the information to be transmitted and sends it to radio frequency device 162. Radio frequency device 162 processes the received information and then sends it through antenna 161.

[0483] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 163 , which includes a baseband processor.

[0484] The baseband device 163 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 16, one of the chips is, for example, a baseband processor, which is connected to the memory 165 through a bus interface to call the program in the memory 165 and execute the network device operations shown in the above method embodiment.

[0485] The network side device may further include a network interface 166 , which is, for example, a Common Public Radio Interface (CPRI).

[0486] Specifically, the network side device 1600 of the embodiment of the present application also includes: instructions or programs stored in the memory 165 and executable on the processor 164. The processor 164 calls the instructions or programs in the memory 165 to execute the methods executed by the modules shown in FIG12 or FIG13 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0487] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor of the user device, the various processes of the method embodiments shown in Figures 2, 3 and 10 are implemented. When the program or instruction is executed by the processor of the network side device, the various processes of the method embodiments shown in Figures 4, 5 and 9 are implemented and can achieve the same technical effect. To avoid repetition, they are not repeated here.

[0488] The processor is a processor in the user equipment or network-side device described in the above embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0489] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiments shown in Figures 2 to 10 above, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0490] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0491] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by a processor of at least one user device or a network-side device to implement the various processes of the above-mentioned data collection method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0492] An embodiment of the present application also provides a communication system, including: a user device and a network side device, wherein the above-mentioned user device can be used to execute the steps of the method shown in any one of Figures 2, 3 and 10 as described above; the above-mentioned network side device can be used to execute the steps of the method shown in any one of Figures 4, 5 and 9 as described above.

[0493] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0494] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for causing a user device or a network-side device to execute the methods described in each embodiment of the present application.

[0495] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data collection method comprising: The user equipment receives first configuration information sent by the network side device, where the first configuration information includes at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The first indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol stack and the air interface data bearer; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

2. The method according to claim 1, wherein Also includes: When the first configuration information includes an instruction to establish an air interface data plane protocol stack, the user equipment establishes the air interface data plane protocol stack according to the configuration parameters of the air interface data plane protocol stack; When the first configuration information includes an instruction to establish an air interface data bearer, the user equipment establishes the air interface data bearer according to the configuration parameters of the air interface data bearer.

3. The method according to claim 1, wherein The user equipment establishes the air interface data plane protocol stack, including: The user equipment establishes at least one data service application entity; and / or, The user equipment establishing the air interface data bearer includes: The user equipment establishes at least one radio network bearer.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises at least one of the following: The user equipment deletes, releases or retains the air interface data plane protocol stack; The user equipment collects data according to the data collection configuration parameters in the idle state; The user equipment deletes, releases or reserves at least part of the air interface data bearers.

5. The method according to claim 4, wherein The user equipment deletes, releases, or retains the air interface data plane protocol stack, including at least one of the following: When the user equipment has configuration parameters of the air interface data plane protocol stack that are valid in the idle state, retain the air interface data plane protocol stack; otherwise, delete or release the air interface data plane protocol stack; The user equipment deletes, releases, or retains the air interface data plane protocol stack according to an instruction received when the user equipment is released to the idle state; The user equipment deletes, releases or retains the air interface data plane protocol stack according to a preset default configuration.

6. The method according to claim 4, wherein: If the user equipment retains the air interface data plane protocol stack, the method further includes: Adjusting the configuration parameters of the air interface data plane protocol stack to preset default configuration parameters; and / or, If the user equipment retains at least part of the air interface data bearer, the method further includes: The configuration parameters of at least part of the air interface data bearer are adjusted to preset default configuration parameters.

7. The method according to any one of claims 1 to 3, wherein: The method further comprises at least one of the following: The user equipment suspends, deactivates or retains the air interface data plane protocol stack; The user equipment collects data according to the data collection configuration parameters in the inactive state; The user equipment suspends, deactivates or reserves at least part of the air interface data bearers.

8. The method according to claim 7, wherein: The user equipment suspending, deactivating or retaining the air interface data plane protocol stack includes: When the user equipment has configuration parameters of the air interface data plane protocol stack that are valid in the inactive state, retain the air interface data plane protocol stack; otherwise, suspend or deactivate the air interface data plane protocol stack; The user equipment suspends, deactivates or retains the air interface data plane protocol stack according to an instruction received when the user equipment is released to the inactive state, or the user equipment suspends, deactivates or retains the air interface data plane protocol stack according to a preset default configuration.

9. The method according to claim 7, wherein: If the user equipment retains the air interface data plane protocol stack, the method further includes: Adjusting the configuration parameters of the air interface data plane protocol stack to preset default configuration parameters; and / or, If the user equipment retains at least part of the air interface data bearer, the method further includes: The configuration parameters of at least part of the air interface data bearer are adjusted to preset default configuration parameters.

10. The method according to claim 4 or 7, wherein: If the user equipment retains the air interface data plane protocol stack and the user equipment retains at least part of the air interface data bearer, the method further includes: A mapping relationship between the air interface data plane protocol stack and at least part of the air interface data bearer is retained.

11. The method according to claim 4 or 7, wherein: Also includes: When the user equipment retains the air interface data plane protocol stack, selecting or reselecting a cell that supports the air interface data plane protocol stack; and / or, When the user equipment reserves at least part of the air interface data bearer, a cell supporting the air interface data bearer is selected or reselected.

12. The method according to claim 11, wherein Also includes: When the first data reporting condition is met, the user equipment enters a connected state to report data or uses small data transmission to report data.

13. The method according to claim 12, wherein: The first data reporting condition includes at least one of the following: Event triggering conditions; Periodic trigger conditions; Leave the current cell; Leaving the valid location area; Leave the cell in the valid cell list.

14. The method according to claim 11, wherein Also includes: The user equipment receives a cell capability indication sent by a network side device, where the cell capability indication is used to indicate whether the cell supports at least one of an air interface data plane protocol stack and / or an air interface data bearer.

15. The method according to any one of claims 1 to 3, wherein: The network side device is a first base station, and after the user equipment is switched from the first base station to the second base station, the method further includes: The user equipment receives second configuration information sent by the second base station, where the second configuration information includes at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; Second indication information, used to instruct establishment of an air interface data bearer for transmitting the collected data; configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

16. The method according to claim 1, wherein The user equipment receives first configuration information sent by the network side device, including: The user equipment in the idle state receives the first configuration information sent by the network side equipment through public signaling.

17. A data collection method comprising: The network-side device sends first configuration information to the user equipment, where the first configuration information includes at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

18. The method according to claim 17, wherein The network-side device is a first base station. Before the first base station sends the first configuration information to the user equipment, the method further includes: The first base station obtains capability information of the user equipment, where the capability information of the user equipment includes whether the user equipment supports at least one of an air interface data plane protocol stack and / or an air interface data bearer; The first base station generates the first configuration information according to the capability information of the user equipment.

19. The method according to claim 18, wherein The capability information of the user equipment includes at least one of the following: Whether the user equipment supports the air interface data plane protocol stack; Configuration parameters of the air interface data plane protocol stack supported by the user equipment; Whether the user equipment supports air interface data bearer; Configuration parameters of the air interface data bearer supported by the user equipment; The maximum number of air interface data bearers supported by the user equipment.

20. The method according to claim 18, wherein Before the first base station obtains the capability information of the user equipment, the method further includes: The first base station receives a first data collection request sent by a core network entity or a third-party device, where the first data collection request includes a target user equipment; or The first base station receives a second data collection request sent by the core network entity or the third-party device; The first base station determines a target user equipment based on the second data collection request.

21. The method according to any one of claims 17 to 20, wherein: Also includes: The first base station establishes at least one of an air interface data plane protocol stack and an air interface data bearer on a local air interface.

22. The method according to claim 17, wherein If the user equipment is handed over from the first base station to the second base station, the method further includes: The first base station sends the first configuration information to the second base station.

23. A data collection method comprising: The second base station receives first configuration information sent by the first base station, where the first configuration information is sent by the first base station to the user equipment when the user equipment resides in the cell of the first base station; The second base station generates second configuration information based on the first configuration information; The second base station sends second configuration information to the user equipment through cell handover signaling, where the first configuration information and the second configuration information both include at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

24. A data collection device comprising: The first receiving module is configured to receive first configuration information sent by a network-side device, where the first configuration information includes at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

25. The apparatus according to claim 24, wherein Also includes: A first processing module, configured to delete, release or retain the air interface data plane protocol stack; A second processing module is used to collect data according to the data collection configuration parameters in the idle state; The third processing module is configured to delete, release or retain at least part of the air interface data bearer.

26. The apparatus according to claim 24, wherein Also includes: a fourth processing module, configured to suspend, deactivate or retain the air interface data plane protocol stack; A fifth processing module, configured to collect data according to the data collection configuration parameters in the inactive state; The sixth processing module is configured to suspend, deactivate or reserve at least part of the air interface data bearer.

27. A data collection device comprising: The first sending module is configured to send first configuration information to the user equipment, where the first configuration information includes at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

28. The apparatus according to claim 27, wherein Also includes: A capability acquisition module, configured to acquire capability information of a user equipment, wherein the capability information of the user equipment includes whether the user equipment supports at least one of an air interface data plane protocol stack and / or an air interface data bearer; A configuration generation module is used to generate the first configuration information according to the capability information of the user equipment.

29. The apparatus according to claim 28, wherein The capability information of the user equipment includes at least one of the following: Whether the user equipment supports the air interface data plane protocol stack; Configuration parameters of the air interface data plane protocol stack supported by the user equipment; Whether the user equipment supports air interface data bearer; Configuration parameters of the air interface data bearer supported by the user equipment; The maximum number of air interface data bearers supported by the user equipment.

30. A data collection device comprising: A second receiving module is configured to receive first configuration information sent by a first base station, where the first configuration information is sent by the first base station to the user equipment when the user equipment resides in a cell of the first base station; a configuration generating module, configured to generate second configuration information based on the first configuration information; The second sending module is configured to send second configuration information to the user equipment through cell handover signaling, where the first configuration information and the second configuration information each include at least one of the following: The first indication information is used to instruct the establishment of an air interface data plane protocol stack for data collection; The second indication information is used to instruct to establish an air interface data bearer for transmitting the collected data; Configuration parameters of the air interface data plane protocol stack; Configuration parameters of air interface data bearer; The mapping relationship between the data collected by the air interface data plane protocol and the air interface data carried; The mapping relationship between the data collected by the radio resource control layer and the air interface data bearer; The mapping relationship between high-layer data and air interface data; Valid cell list; Valid location area; The current cell is valid; Valid within the inactive RAN area; Data collection configuration information.

31. A user device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data collection method according to any one of claims 1 to 16 are implemented.

32. A network side device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the program or instructions implement the steps of the data collection method according to any one of claims 17 to 22; or, when executed by the processor, the program or instructions implement the steps of the data collection method according to claim 23.

33. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor of a user device, implements the steps of the data collection method as described in any one of claims 1 to 16; or, when executed by a processor of a network side device, implements the steps of the data collection method as described in any one of claims 17 to 22; or, when executed by a processor of a network side device, implements the steps of the data collection method as described in claim 23.

34. A program product, which, when executed by a processor of a user device, implements the steps of the data collection method as described in any one of claims 1 to 16; or, when executed by a processor of a network-side device, implements the steps of the data collection method as described in any one of claims 17 to 22; or, when executed by a processor of a network-side device, implements the steps of the data collection method as described in claim 23.

Images