Communication methods and communication apparatus

By sending paging messages to terminal devices for data acquisition configuration, the data transmission requirements of AI, ISAC, and DT in cellular networks are resolved, achieving efficient data acquisition and transmission and meeting the communication requirements of low latency and high reliability.

WO2026232562A1PCT designated stage Publication Date: 2026-11-12SHENZHEN TCL NEW-TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094036
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing cellular network data transmission solutions cannot meet the transmission requirements of new data types introduced by AI, ISAC, and DT, including requirements for arbitrary topology, in-band processing, large data packet transmission, low latency and high speed, and high reliability.

Method used

By sending a first paging message to the terminal device to configure data acquisition, the network device and the terminal device exchange data acquisition configuration information in the RRC idle or inactive state, and use the paging message to trigger the data acquisition process.

Benefits of technology

It enables efficient configuration of data acquisition in cellular networks, meeting the data transmission needs of AI, ISAC, and DT, and improving the flexibility and efficiency of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094036_12112026_PF_FP_ABST
    Figure CN2025094036_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application are communication methods and a communication apparatus, which enable configuration of configuration information for subsequent data collection by means of a first paging message sent to a terminal device. A communication method comprises: a network device sending a first paging message to a terminal device, wherein the first paging message is used for configuring data collection configuration information for the terminal device, and the terminal device is in a radio resource control (RRC) idle or inactive state.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods and communication devices Technical Field

[0001] This application relates to the field of communications, and more specifically, to communication methods and communication devices. Background Technology

[0002] With the continuous development of mobile cellular networks, in order to meet the ever-increasing business needs of users, cellular networks no longer only provide communication services, but also further enhance communication capabilities and user experience by introducing more new technologies (such as artificial intelligence (AI), communication-sensing integration (ISAC), and digital twins (DT)).

[0003] However, the introduction of AI, ISAC, and DT has also brought new demands to the network. Specifically, in the past, the transmitted data was either signaling data used for network transmission control (i.e., control plane data) or user service data (i.e., user plane data). With the introduction of AI, ISAC, and DT, the network now transmits AI, ISAC, and DT-related data (such as AI model parameter data, AI model gradient information, training data, inference data, monitoring data, and sensing data). This data is neither control plane data nor user plane data, but a new type of data. At the same time, the transmission requirements of this new data type differ from the existing control plane and user plane data transmission requirements. These requirements include: arbitrary topology, in-path processing, large packet transmission, low latency, high speed, and high reliability. Existing control plane and user plane data transmission schemes cannot fully support these requirements. Summary of the Invention

[0004] This application provides a communication method and a communication device, which can configure the configuration information for subsequent data collection by sending a first paging message to a terminal device.

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

[0006] Firstly, a communication method is provided. This method can be executed by a network device, or by a component of the network device, such as a processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the functions of the network device. Taking the method being executed by a network device as an example, the method includes: sending a first paging message to a terminal device, the first paging message being used to configure data acquisition configuration information to the terminal device, wherein the terminal device is in a Radio Resource Control (RRC) idle state or inactive state.

[0007] In this embodiment of the application, the network device sends a first paging message to the terminal device, and the terminal device receives the first paging message from the network device, thereby enabling the network device to configure the configuration information for subsequent data collection through the first paging message sent to the terminal device.

[0008] Secondly, a communication method is provided. This method can be executed by a terminal device, or by a component of the terminal device, such as the terminal device's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the terminal device's functions. Taking the method being executed by a terminal device as an example, the method includes: receiving a first paging message from a network device, wherein the terminal device is in a Radio Resource Control (RRC) idle state or inactive state; and obtaining data acquisition configuration information based on the first paging message.

[0009] In this embodiment of the application, the network device sends a first paging message to the terminal device, and the terminal device receives the first paging message from the network device, thereby enabling the network device to configure the configuration information for subsequent data collection through the first paging message sent to the terminal device.

[0010] Thirdly, a communication device is provided for implementing the various methods described above. This communication device may be a network device as described in the first aspect, or a device included in a network device, such as a chip; or, the communication device may be a terminal device as described in the second aspect, or a device included in a terminal device, such as a chip.

[0011] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0012] In some possible designs, the communication device may include a processing module and a communication module. The communication module may include an output module (or transmitting module) and an input module (or receiving module), respectively used to implement the output (or transmitting) and input (or receiving) functions in any of the above aspects and any possible designs. The processing module can be used to implement the processing functions in any of the above aspects and any possible designs.

[0013] Optionally, the communication device also includes a storage module for storing program instructions and data.

[0014] Fourthly, a communication device is provided, comprising: at least one processor configured to execute computer programs or instructions, or to cause the communication device to perform the method described in any of the preceding aspects via logic circuitry. The communication device may be a network device as described in the first aspect, or a device included in a network device, such as a chip; or, the communication device may be a terminal device as described in the second aspect, or a device included in a terminal device, such as a chip.

[0015] In some possible designs, the communication device also includes a memory for storing configuration files of computer instructions and / or logic circuits. Optionally, the memory is integrated with the processor, or the memory is independent of the processor.

[0016] In one possible design, the communication device also includes a communication interface for inputting and / or outputting signals.

[0017] In some possible designs, the communication interface is an interface circuit used to read and write computer instructions. For example, the interface circuit is used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0018] In some possible designs, this communication interface is used to communicate with modules outside the communication device.

[0019] In some possible designs, the communication device can be a chip system. When the communication device is a chip system, the chip system may include chips, or it may contain chips and other discrete components.

[0020] Fifthly, a communication device is provided, comprising: a logic circuit and an interface circuit; the interface circuit is used for inputting information and / or outputting information; the logic circuit is used to execute the method described in any of the preceding aspects, processing the input information and / or generating output information. The communication device may be a network device as described in the first aspect, or a device included in a network device, such as a chip; or, the communication device may be a terminal device as described in the second aspect, or a device included in a terminal device, such as a chip.

[0021] In a sixth aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed by a processor, cause the methods described in any of the preceding aspects to be performed.

[0022] In a seventh aspect, a computer program product is provided, which, when executed by a processor, causes the method described in any of the preceding aspects to be performed.

[0023] It is understood that when the communication device provided by any of the third to fifth aspects is a chip, the aforementioned sending action / function can be understood as output information, and the aforementioned receiving action / function can be understood as input information.

[0024] Eighthly, a communication system is provided, which includes one or more means according to any of the above aspects.

[0025] The technical effects of any of the design methods in aspects three through five can be found in the technical effects of different design methods in aspects one or two above, and will not be repeated here. Attached Figure Description

[0026] Figure 1 is a schematic diagram of use case 1 provided in the embodiments of this application;

[0027] Figure 2 is a schematic diagram of use case 2 provided in the embodiments of this application;

[0028] Figure 3 is a schematic diagram of use case 3 provided in the embodiments of this application;

[0029] Figure 4 is a flowchart of core network paging provided in an embodiment of this application;

[0030] Figure 5 is a flowchart of an example of access network paging provided in an embodiment of this application;

[0031] Figure 6 is a flowchart of another example of access network paging provided in the embodiments of this application;

[0032] Figure 7 is a schematic diagram of the anchor access network device provided in this application embodiment performing RAN paging by issuing signaling from 5GC;

[0033] Figure 8 is a flowchart of an example of RNA update in the access network paging process provided in an embodiment of this application;

[0034] Figure 9 is a flowchart of another example of RNA update in the access network paging process provided in the embodiments of this application;

[0035] Figure 10 is a user plane protocol stack architecture diagram corresponding to an uplink PDU session provided in an embodiment of this application;

[0036] Figure 11 is a schematic diagram of the communication system provided in an embodiment of this application;

[0037] Figure 12 is a schematic diagram of the structure of the communication device 1200 provided in an embodiment of this application;

[0038] Figure 13 is a flowchart illustrating an example of a communication method provided in an embodiment of this application;

[0039] Figure 14 is a schematic diagram of a specific embodiment of the terminal device in the RRC inactive state provided in this application;

[0040] Figure 15 is a schematic diagram of another specific embodiment of the terminal device provided in the present application in the RRC inactive state;

[0041] Figure 16 is a schematic diagram of another specific embodiment of the terminal device provided in this application in the RRC inactive state;

[0042] Figure 17 is a schematic diagram of the first specific embodiment of the terminal device in the RRC idle state provided in this application;

[0043] Figure 18 is a schematic diagram of a second specific embodiment of the terminal device in the RRC idle state provided in this application;

[0044] Figure 19 is a schematic diagram of a third specific embodiment of the terminal device in the RRC idle state provided in this application;

[0045] Figure 20 is a schematic diagram of the fourth specific embodiment of the terminal device in the RRC idle state provided in this application;

[0046] Figure 21 is a schematic diagram of the fifth specific embodiment of the terminal device in the RRC idle state provided in this application;

[0047] Figure 22 is a schematic diagram of the sixth specific embodiment of the terminal device in the RRC idle state provided in this application;

[0048] Figures 23 to 49 are schematic diagrams of the protocol layer entity architecture processing flow provided in the embodiments of this application;

[0049] Figure 50 is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

[0057] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0058] To facilitate understanding, the relevant technologies of the embodiments of this application will be briefly introduced first.

[0059] I. Use cases for data transmission in access networks.

[0060] 1. Use Case 1.

[0061] The OAM (Operation, Administration, and Maintenance) unit needs to optimize the network, which requires a large amount of air interface channel information as the basis for optimization. Therefore, the OAM requests air interface data from the data service function network elements in the mobile network. A use case scenario is shown in Figure 1.

[0062] Among them, the data service function network element requests data collection from one or more designated access network devices based on the data requirements of OAM.

[0063] The access network device configures data collection and reporting rules for designated terminal devices or self-determined eligible terminal devices based on data collection requests. If the designated terminal device or self-determined eligible terminal device is in an IDLE or INACTIVE state, the access network device must first restore such terminal devices to a CONNECTED state.

[0064] Once the terminal device completes data acquisition and meets the reporting rules, it transmits the collected air interface channel information to the access network equipment. If necessary, the access network equipment then transmits the data to the data processing unit for further data processing (such as fusion and extraction). After processing, the data processing unit delivers the processed data to the OAM (Operational Information Management) unit for network optimization.

[0065] 2. Use Case 2.

[0066] Terminal device A needs to deploy an AI-based beam management model and requests the corresponding AI model from the AI ​​function network element. If the AI ​​function network element does not have a model that meets the needs of terminal device A locally, then it needs to train a model for terminal device A to meet its requirements. First, the AI ​​function network element needs a large amount of relevant air interface channel data for training. Therefore, the AI ​​function network element requests air interface channel data for beam management model training from the data service function network element. The use case scenario is shown in Figure 2.

[0067] Similar to Use Case 1, the data service function network element requests data collection from one or more designated access network devices based on the needs of the AI ​​function network element. The access network then identifies and configures data collection and reporting rules for designated terminal devices or autonomously determined eligible terminal devices based on the data collection request. Once the terminal device completes data collection and meets the reporting rules, it transmits the collected air interface channel information to the access network devices.

[0068] Since the air interface data transmission during the data acquisition process serves the needs of terminal device A, UE A can be charged based on the network resource usage during air interface transmission.

[0069] Additionally, if necessary, the access network equipment can transmit the data to the data processing unit for further data processing (such as fusion and extraction). After processing, the data processing unit delivers the processed data to the AI ​​functional network element for model training.

[0070] Figure 3 illustrates a one-to-many transmission scenario that requires meeting different transmission needs. In this scenario, the AI ​​network element collects channel data from terminal device 1 and terminal device 2 for training the AI ​​model; the digital twin system network element (DT) collects channel data from terminal device 1 and terminal device 2 to build and update the virtual twin network; and the access network device collects and merges channel data from terminal device 1 and terminal device 2 to perceive environmental information and provide users with awareness and warning services. Here, the channel information data collected by AI, DT, and BS exhibits a high degree of redundancy.

[0071] According to the 6G SA1 proposal (S1-250087), the Virtual Twin Network (DT) needs to achieve real-time simulation of the physical network (including the physical world, mobile devices, access network, and core network) via a virtual twin network for performance monitoring and dynamic optimization. Therefore, the DT needs to acquire real-time data from network nodes (such as terminal devices, access network devices, network nodes, and sensors) to dynamically update the virtual twin network. Simultaneously, the physical network needs to provide real-time network status data to the DT to verify the effectiveness of decisions. Therefore, in the scenario shown in Figure 3, the DT requires terminal device 1 and terminal device 2 to provide ultra-low latency data collection services to ensure ultra-low latency synchronization between the physical network and the DT network.

[0072] According to the 6G SA1 proposals (S1-250178 and S1-250286), awareness-based warning services need to meet the requirements of low-latency transmission and processing to provide low-latency awareness services for scenarios such as UAV and V2X.

[0073] According to the 6G SA1 proposal (S1-250178), AI services need to meet the requirements of reliable, high-throughput, and long-term data transmission. In this use case, the AI ​​network element collects channel data from terminal device 1 and terminal device 2 for training the AI ​​model. Ensuring transmission reliability is crucial because the channel quality varies across different areas of the terminal devices. If transmission reliability is not guaranteed, there will be relatively less data in areas with poor channel quality, resulting in the training dataset focusing on areas with better channel quality. This further leads to poor performance of the trained AI network model in areas with poor channel quality. Therefore, the AI ​​data collection service needs to meet reliability requirements.

[0074] Therefore, the new data transmission requirements of access network devices include:

[0075] 1) Access network equipment needs to support restoring designated or non-designated terminal devices from IDLE or INACTIVE state to CONNECTED state according to the tasks of data service function network elements, and can perform data collection configuration on terminal devices according to tasks.

[0076] 2) In order to reduce the data duplication and energy consumption on the air interface, the terminal equipment needs to transmit channel data to the network side in one air interface transmission as much as possible, while meeting the data transmission requirements (latency, reliability) of different data requesters.

[0077] 2. Paging.

[0078] 1. Core network paging process.

[0079] Figure 4 is a flowchart of the core network paging process provided in an embodiment of this application. As shown in Figure 4, when the terminal device is in RRC-IDLE state, if the UPF has data to send to the terminal device, the AMF initiates core network paging to the access network devices within the specified range. Then, after the access network devices within the specified range receive the paging message from the AMF through the NGAP interface, they send paging information within the coverage area through the RRC paging message (carrying core network UE ID information). If the terminal device receives the core network paging message, it will initiate a connection establishment process and attempt to transition from the RRC-IDLE state to the RRC-CONNECTED state.

[0080] 2. Access network paging process.

[0081] Figures 5 and 6 are flowcharts of access network paging provided in embodiments of this application. As shown, access network paging is RAN paging. When the terminal device is in the RRC-INACTIVE state, after the anchor access network device (i.e., the last serving gNB) receives downlink data or downlink signaling from the 5GC (5G core network), the anchor access network device and its neighboring access network devices in the RNA (RAN Notification Area) will send RAN Paging messages. After receiving RAN paging, the terminal device will initiate the process of transitioning from the RRC-INACTIVE state to the RRC-CONNECTED state.

[0082] If the anchor access network device performs RAN paging by issuing signaling from 5GC, the signaling flow is shown in Figure 7.

[0083] 3. RNA update in the access network paging process.

[0084] Figures 8 and 9 are flowcharts of RNA updates in the access network paging process provided in the embodiments of this application. As shown in the figures, since the range of RAN paging depends on the RNA, the RNA also needs to be updated as the terminal device moves. Among them, there are two RNA update methods for terminal devices in the RRC-INACTIVE state: event-based RNA update (i.e., the terminal device leaves the RNA region, as shown in Figure 8) and periodic RNA update (as shown in Figure 9).

[0085] 4. Physical layer process of paging.

[0086] The paging message is carried in the PDSCH, and its time-frequency position and decoding method are indicated by a specific DCI in the PDCCH. The CRC encoding of this DCI uses P-RNTI for CRC scrambling. P-RNTI is a globally uniform RNTI with a value of 0xFFFE.

[0087] The DCI for Paging messages belongs to DCI1_0, and its format is shown in Table 1 (the details of DCI1_0 can be found in 38.212->7.3.1.2.1). If the Short Messages Indicator is set to 10 (Short Messages Only), then all fields except Short Messages Indicator, Short Messages, and TRS availability indication are reserved. That is, in mode 10 (Short Messages Only), DCI1_0 will appear alone and will not be associated with any content in the PDSCH.

[0088] Table 1

[0089] The Short Messages (8 bits) in DCI1_0 can contain the following information. Bit 1 indicates a change in system information, requiring the terminal device to immediately receive and update. Bit 2 indicates the presence of ETWS and CMAS messages, requiring the terminal device to immediately receive and update SIB6. Bit 3 indicates that the terminal device needs to stop listening to paging messages to save power. Bit 4 is an enhanced version of Bit 1, used to support eDRX.

[0090] The primary design motivation for Short Messages is to enable devices to update information faster or to make devices more energy-efficient.

[0091] III. Inventory Process.

[0092] In AIoT (Ambient IoT) scenarios, access network devices or terminal devices can perform an inventory process on the device based on requests from the core network to obtain local device information. Currently, the specific message content for the inventory process in AIoT scenarios is not yet defined; it is only stated that it needs to include the ID of the AIoT device to be inventoried.

[0093] IV. Wireless bearer transmission scheme based on a single RLC entity.

[0094] In existing standard user plane transmission, data transmission between a source node (UE) and a destination node (DN) requires the establishment of a PDU session. The PDU session uses different radio bearers (RBs) to meet the different air interface transmission requirements (such as reliability, latency, etc.) of different data streams.

[0095] Specifically, the network side can configure the corresponding air interface protocol stack entities according to the transmission requirements of each radio bearer, and the same data stream will only be transmitted through one RB. When an RB is associated with only one RLC entity, that RLC entity is generally either in UM mode or AM mode. UM mode focuses on low-latency transmission requirements, while AM ​​mode focuses on high-reliability transmission requirements. This means that a radio bearer transmission scheme based on a single RLC entity can only support one transmission requirement for the same data stream.

[0096] Figure 10 is a user plane protocol stack architecture diagram corresponding to an uplink PDU session provided in an embodiment of this application. As shown in Figure 10, it includes multiple RBs, each RB corresponding to a transmission requirement.

[0097] V. Replication and transmission scheme for multiple RLC entities with the same configuration.

[0098] To support the service requirements of URLLC (Ultra-Reliable Low Latency), existing standards allow multiple RLC entities to be associated under a PDCP entity in an RB for air interface transmission, namely DC duplication (dual connection duplication) and CA duplication (carrier aggregation duplication).

[0099] Specifically, the PDCP entity transmitting URLLC service data copies the data received from the upper layer and distributes it to each associated RLC entity. Each associated RLC entity performs its own subsequent processing according to the same configuration. When one of the sending RLC entities receives a report of successful reception from the receiving end, the PDCP entity notifies other associated RLC entities to discard the corresponding data, thereby avoiding unnecessary duplicate transmissions.

[0100] In this scheme, data streams within the same RB will be transmitted through multiple RLC entities to meet the same transmission requirements.

[0101] VI. Routing and transmission schemes for multiple RLC entities with the same configuration.

[0102] Based on the multi-RLC entity replication transmission scheme, the standard also supports a PDCP entity within an RB (Replication Block) to distribute different parts of the same data stream to multiple associated RLC entities, thereby enhancing data transmission rate; this is known as DC routing (dual-connectivity routing). In this scheme, different RLC entities still use the same configuration parameters, and each RLC entity transmits data independently. Simultaneously, at the receiving end, different RLC entities submit the received data upwards to the same PDCP entity, which then reorders the RLC SDUs and delivers the reordered packets to the upper layer as needed.

[0103] In this scheme, data streams within the same RB will be transmitted through multiple RLC entities to meet the same transmission requirements.

[0104] 7. Routing and transmission schemes for multiple RLC entities with different configurations.

[0105] In XR (Augmented Reality) scenarios, to support the different transmission requirements of different data streams within the same Resource Controller (RB), the PDCP entity associates with multiple Resource Controller (RLC) entities supporting different transmission needs and distributes the different data streams to the corresponding RLC entities. Then, each of the multiple RLC entities transmits its data independently. At the receiving end, different RLC entities forward the received data to the same PDCP entity.

[0106] In this scheme, different data streams in the same RB will be transmitted through multiple RLC entities to meet different transmission requirements, and at the receiving end, they will be aggregated into the same PDCP entity to be delivered to the same destination node.

[0107] Figure 11 is a schematic diagram of a communication system provided in an embodiment of this application. As shown in Figure 11, the communication system includes network equipment and terminal equipment.

[0108] In this embodiment of the application, the network device is used to send a first paging message to the terminal device.

[0109] In this embodiment of the application, the terminal device is used to receive a first paging message from the network device and obtain data collection configuration information based on the first paging message.

[0110] The terminal device is in the Radio Resource Control (RRC) idle state or inactive state.

[0111] Optionally, the terminal equipment involved in this application may be user equipment (UE), access terminal, terminal unit, user station, terminal station, mobile station, mobile station, remote station, remote terminal, user terminal equipment (TE), mobile device, wireless communication device, terminal agent, tablet computer, handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, vehicle-mounted communication module, wearable device, or terminal device in a 5G network or a public land mobile network (PLMN) evolved after 5G. The access terminal may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, drone, robot, point of sale (POS) machine, customer-premises equipment (CPE), or wearable device, virtual reality (VR) device. Wireless terminals can be categorized into various types, including VR (Augmented Reality) terminal devices, wireless terminals in industrial control, self-driving, remote medical, smart grid, transportation safety, smart city, and smart home. Alternatively, a terminal can be a communication-enabled terminal within the Internet of Things (IoT), such as a V2X terminal (e.g., vehicle-to-everything (V2X) terminal, a D2D communication terminal, or an M2M communication terminal. Terminals can be mobile or fixed. Furthermore, this application does not limit the device form of the terminal; the apparatus used to implement the terminal device's function can be the terminal device itself, or it can be an apparatus capable of supporting the terminal device in implementing that function, such as a chip system. This apparatus can be installed in the terminal device or used in conjunction with the terminal device. In this application, the chip system can consist of chips or include chips and other discrete components.

[0112] Optionally, the network equipment involved in this application can be an evolved NodeB (or eNB or e-NodeB) in a long-term evolution (LTE) system or an enhanced LTE (LTE-A) system, such as a traditional macro base station (eNB) and a micro base station (eNB) in a heterogeneous network scenario. Alternatively, it can include a next-generation node B (gNB) in a new radio (NR) system. Alternatively, it can include a transmission reception point (TRP), a home base station (e.g., a home evolved NodeB, or a home Node B, HNB), a base band unit (BBU), a base band pool, or a wireless fidelity (WiFi) access point (AP), etc. Alternatively, it can include base stations in non-terrestrial networks (NTNs), i.e., those deployed on flying platforms or satellites. In NTNs, access network devices can act as Layer 1 (L1) relays, base stations, or integrated access and backhaul (IAB) nodes. Alternatively, access network devices can be devices that implement base station functions in IoT, such as those implementing base station functions in drone communication, V2X, D2D, or machine-to-machine (M2M) communication.

[0113] In some possible scenarios, network devices can also be modules or units capable of performing some of the functions of a base station. For example, the first network device can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be set up separately or included in the same network element, such as in a baseband unit (BBU). The RU can be included in radio equipment or radio units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0114] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a network device can be a network device or a module of a network device in an Open Radio Access Network (ORAN) system. In an ORAN system, CU can also be called open (O)-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of a software module and a hardware module.

[0115] Optionally, the base station in the embodiments of this application may include various forms of base stations, such as: macro base station, micro base station (also known as small station), relay station, access point, home base station, TRP, transmitting point (TP), mobile switching center, etc., and the embodiments of this application do not specifically limit them.

[0116] Optionally, the user plane function network element involved in this application can be a UPF network element of the 5G communication architecture, or a network element with user plane function network element function in other communication systems. The access and mobility management function network element involved in this application can be an AMF network element of the 5G communication architecture, or a network element with session management function network element function in other communication systems. This application does not limit this.

[0117] The functions of the network devices and terminal devices involved in this application can be implemented by the communication device 1200 shown in FIG12. FIG12 is a schematic diagram of the structure of the communication device 1200 provided in the embodiment of this application. The communication device 1200 includes one or more processors 1201, a communication line 1202, and at least one communication interface (FIG12 is only an example illustrating the inclusion of a communication interface 1204 and a processor 1201), and optionally may also include a memory 1203.

[0118] The processor 1201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0119] The communication line 1202 may include a path for connecting different components.

[0120] The communication interface 1204 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module can be a transceiver or a similar device. Optionally, the communication interface 1204 can also be a transceiver circuit located within the processor 1201, used to implement the processor's signal input and signal output.

[0121] The memory 1203 can be a device with storage function. For example, it can be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions; random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via communication line 1202. The memory can also be integrated with the processor.

[0122] The memory 1203 stores computer execution instructions for implementing the scheme of this application, and the processor 1201 controls the execution. The processor 1201 executes the computer execution instructions stored in the memory 1203, thereby implementing the communication method provided in the embodiments of this application.

[0123] Alternatively, in this embodiment, the processor 1201 may execute the processing-related functions of the communication method provided in the following embodiments of this application, and the communication interface 1204 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0124] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0125] In a specific implementation, as one embodiment, processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG12.

[0126] In a specific implementation, as one embodiment, the communication device 1200 may include multiple processors, such as processor 1207 and processor 1201 in FIG. 12. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0127] In a specific implementation, as one embodiment, the communication device 1200 may further include an output device 1205 and an input device 1206. The output device 1205 communicates with the processor 1201 and can display information in various ways. For example, the output device 1205 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1206 communicates with the processor 1201 and can receive user input in various ways. For example, the input device 1206 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0128] The aforementioned communication device 1200 may sometimes be referred to as a communication device, which can be a general-purpose device or a special-purpose device. For example, the communication device 1200 may be a desktop computer, a portable computer, a web server, a handheld computer (personal digital assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure to that shown in Figure 12. The embodiments of this application do not limit the type of communication device 1200.

[0129] Furthermore, the composition shown in Figure 12 does not constitute a limitation on the communication device. In addition to the components shown in Figure 12, the communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0130] The communication method provided in the embodiments of this application will now be described with reference to the communication system shown in Figure 11.

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

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

[0133] Figure 13 is a schematic diagram of an example of the communication method provided in this application embodiment. This method can be applied to the communication system shown in Figure 11, and is illustrated using the interaction between a network device and a terminal device as an example. Of course, the entity executing the network device action in this method can also be a device / module within the network device, such as a chip, processor, or processing module within the network device; similarly, the entity executing the terminal device action in this method can also be a device / module within the terminal device, such as a chip, processor, or processing module within the terminal device. This application embodiment does not specifically limit this. In this application embodiment, a single executing entity (e.g., the processing performed by the network device or the terminal device) can also be divided into multiple executing entities, which can be logically and / or physically separated. As shown in Figure 13, the communication method 1300 includes:

[0134] S1310, the network device sends a first paging message to the terminal device. Correspondingly, the terminal device receives the first paging message from the network device.

[0135] In this embodiment of the application, the first paging message is used to configure the data collection configuration information to the terminal device. It can be understood that the first paging message is used to trigger the network device to configure the data collection configuration information to the terminal device, that is, the network device sends the first paging message to the terminal device. Furthermore, in subsequent steps, the network device configures the data collection configuration information to the terminal device.

[0136] The terminal device is in the RRC idle state or the RRC inactive state.

[0137] In this embodiment of the application, the first paging message includes one or more of the following: paging reason, task type, or capability information required by the terminal device.

[0138] The paging reason may include one or more of the following: signaling configuration, data transmission, broadcast paging (e.g., broadcast paging or inventory), or other reasons, which are not limited in this application embodiment.

[0139] The task type identifies the task to be performed. Optionally, the task type can be distinguished by a task ID. For example, if the first paging message includes a task ID, the terminal device can know the task type. For example, the task type can be data acquisition, data transmission, or other task types, which are not limited in this embodiment.

[0140] Among them, the capability information required by the terminal device indicates the terminal device that must have the capability. Optionally, the capability information required by the terminal device can be distinguished by the capability ID.

[0141] Optionally, the first paging message may also include the paging identifier ID information of the terminal device or other information, which is not limited in this embodiment.

[0142] For example, the paging ID information of the terminal device can be I-RNTI or 5G-TMSI, etc., and this application embodiment does not limit this.

[0143] In this embodiment of the application, the configuration information for data collection may include one or more of the following: data task identifier, data collection reporting trigger condition, data collection reporting method, data volume threshold, duration threshold, or reporting time.

[0144] The data collection and reporting trigger conditions include one or more of the following: the amount of data collected reaches the data volume threshold, the collection duration reaches the duration threshold, or the reporting time is reached (or the time point reaches the specified reporting time point).

[0145] The data collection and reporting methods include one or more of the following: control plane transmission, user plane transmission, or data plane transmission.

[0146] For example, control plane transmission can be data transmission via RRC messages, user plane transmission can be data transmission via user plane function network elements, and data plane transmission can be direct point-to-point data transmission, such as direct data transmission between terminal devices and network devices.

[0147] The data task identifier can correspond to the data task in the above task types (e.g., data acquisition, and / or data transmission task), which will not be elaborated further in this application embodiment.

[0148] In this embodiment, the data task identifier may have one or more of the following functions: indicating a data task ID, indicating a data task type, associating with a data task (e.g., one or more data acquisition, storage, retrieval, transmission, and / or processing tasks), associating with an object of a data service, serving as a basis for retrieving user-subscribed data, serving as a basis for session authentication and / or authorization, or serving as a basis for session dynamic policy decisions, etc. For example, the data task identifier may be a Data Task ID, or other identifiers; this embodiment does not limit this.

[0149] S1320, the terminal device obtains the data collection configuration information based on the first paging message.

[0150] In some embodiments, the terminal device is in an RRC inactive state, or it can be referred to as an RRC-INACTIVE state. The communication method provided in this application embodiment will be described below when the terminal device is in an RRC inactive state.

[0151] Optionally, in one possible implementation, the first paging message is an access network paging message, which is a paging directly from the network device to the designated terminal device. As shown in Figure 14, the communication method provided in this embodiment further includes:

[0152] S1430, the terminal device sends a connection restoration request to the network device. Correspondingly, the network device receives the connection restoration request from the terminal device.

[0153] In S1320, the terminal device obtains the data collection configuration information based on the first paging message, including:

[0154] S1420, the terminal device receives a connection release message from the network device and obtains the data collection configuration information included in the connection release message.

[0155] Alternatively, in other words, for network devices, the network device sends a connection release message to the terminal device, which includes configuration information for data collection.

[0156] In this embodiment of the application, after the network device sends a connection release message to the terminal device, the terminal device either returns to the RRC inactive state or switches to the RRC idle state.

[0157] In this implementation, the network device directly pages the designated terminal device that is in the RRC inactive state, thereby configuring the terminal device's data collection configuration information during the connection recovery process. After the configuration is completed, the terminal device returns to the RRC inactive state, or the terminal device is in the RRC idle state.

[0158] Optionally, in another possible implementation, the first paging message is an access network paging message, i.e., RAN paging as described in the related technologies above, which is a paging directly from the network device to the designated terminal device. As shown in Figure 15, the communication method provided in this application embodiment further includes:

[0159] S1530, the terminal device sends a connection restoration request to the network device. Correspondingly, the network device receives the connection restoration request from the terminal device.

[0160] In S1320, the terminal device obtains the data collection configuration information based on the first paging message, including:

[0161] S1520, the terminal device receives a connection restoration message from the network device and obtains the data collection configuration information included in the connection restoration message.

[0162] Alternatively, in other words, for network devices, the network device sends a connection restoration message to the terminal device, which includes configuration information for data acquisition.

[0163] In this embodiment of the application, after the network device sends a connection recovery message to the terminal device, the terminal device can restore the RRC connection state, or it can be said that the terminal device is in the RRC-CONNECTED state. This embodiment of the application does not limit this.

[0164] Optionally, for this implementation, the communication method provided in the embodiments of this application further includes:

[0165] S1540, the terminal device sends a connection restoration complete message to the network device. Correspondingly, the network device receives the connection restoration complete message from the terminal device.

[0166] In this embodiment of the application, the connection restoration completion message includes one or more of the following: an indication that the configuration information for data acquisition has been successfully configured, or a data task identifier.

[0167] In this implementation, the network device directly sends a first paging message to the designated terminal device in the RRC inactive state, thereby restoring the terminal device from the RRC inactive state to the RRC connected state. During the restoration process, the terminal device is configured with data collection configuration information.

[0168] Optionally, in another possible implementation, the first paging message is a broadcast paging message (it should be noted that when the first paging message is a broadcast paging message, the paging reason corresponding to the first paging message may include broadcast paging), which is a paging directly performed by the network device to a non-designated terminal device, that is, the network device can send the first paging message to at least one terminal device (i.e., a non-designated terminal device) within a certain range. As shown in Figure 16, the communication method provided in this application embodiment further includes:

[0169] S1630, the terminal device sends a connection restoration request to the network device. Correspondingly, the network device receives the connection restoration request from the terminal device.

[0170] It should be noted that for terminal devices whose source network device is not this network device (or, the source network device can also be referred to as the anchor network device in related technologies, and the name is not limited in this application embodiment):

[0171] After receiving the first paging message, if the first paging message is a broadcast paging message (i.e., not a paging message for a specific terminal device), and if there are relevant parameters such as a task ID or capability ID, and the terminal device can complete the specified task or meet the corresponding terminal device capability level, then the terminal device can initiate a connection recovery request.

[0172] Optionally, if the first paging message only indicates a broadcast paging message (i.e., paging is not performed by a designated terminal device), the terminal device may initiate a connection restoration request.

[0173] S1640, the network device obtains the context information of the terminal device.

[0174] In this embodiment of the application, the network device can obtain the context information of the terminal device in the following ways:

[0175] Step 1: The network device sends a context retrieval request for the terminal device to the source network device of the terminal device.

[0176] Step 2: The source network device of the terminal device sends the context retrieval response of the terminal device to the network device.

[0177] The terminal device obtains the data collection configuration information based on the first paging message, including:

[0178] S1620, the terminal device receives a connection restoration message from the network device and obtains the data collection configuration information included in the connection restoration message.

[0179] Alternatively, in other words, for network devices, the network device sends a connection restoration message to the terminal device, which includes configuration information for data acquisition.

[0180] In this embodiment of the application, after the network device sends a connection recovery message to the terminal device, the terminal device can restore the RRC connection state, or it can be said that the terminal device is in the RRC-CONNECTED state. This embodiment of the application does not limit this.

[0181] Optionally, for this implementation, the communication method provided in the embodiments of this application further includes:

[0182] In step S1650, the terminal device sends a connection restoration complete message to the network device. Correspondingly, the network device receives the connection restoration complete message from the terminal device.

[0183] In this embodiment of the application, the connection restoration completion message includes one or more of the following: an indication that the configuration information for data acquisition has been successfully configured, or a data task identifier.

[0184] Optionally, the communication method provided in this application embodiment further includes:

[0185] The network device sends a path handover request to the access and mobility management function (AM) network element. Correspondingly, the AM AM network element receives the path handover request from the network device.

[0186] Optionally, the communication method provided in this application embodiment further includes:

[0187] The access and mobility management function (AMU) network element sends a path handover response to the network device. Correspondingly, the network device receives the path handover response from the AMU network element.

[0188] Optionally, the communication method provided in this application embodiment further includes:

[0189] The network device sends a context release message for the terminal device to the source network device. Correspondingly, the source network device receives the context release message for the terminal device from the network device.

[0190] Furthermore, the source network device can release the context information of the terminal device.

[0191] Optionally, the first paging message may include indication information of the resources for random access by the terminal device. That is, the network device may indicate the random access resources to non-designated terminal devices in a broadcast message (e.g., an SIB message). This can prevent a large number of terminal devices from occupying a large amount of random access resources for the random access process due to broadcast messages, thereby avoiding affecting other terminal devices that are normally performing random access.

[0192] In this implementation, the network device can page a non-designated terminal device that is in an RRC inactive state, thereby converting the terminal device that meets the paging conditions from the RRC inactive state to the RRC connected state, and then configuring the configuration information for data collection of the terminal device during the connection restoration process.

[0193] It should be noted that, in the embodiments of this application, for the above three possible implementation methods, the connection recovery request can be, for example, an RRC Resume Request message; the connection release message including data collection configuration information can be, for example, an RRC Release message (the terminal device can enter the RRC idle state); or, the connection release message including data collection configuration information can be, for example, an RRC Release with suspend configuration message (the terminal device can enter the RRC inactive state); the connection recovery message can be, for example, an RRC Resume message; the connection recovery completion message can be, for example, an RRC Resume Complete message; or, the above messages can also be other messages, and the embodiments of this application do not limit them.

[0194] In some embodiments, the terminal device is in an RRC idle state, or it may be referred to as an RRC-IDLE state. The communication method provided in this application embodiment will be described below when the terminal device is in an RRC idle state.

[0195] Optionally, in one possible implementation, the first paging message is a core network paging, which is a request from a network device to an access and mobility management function network element to paging a designated terminal device, as shown in Figure 17. The communication method provided in this application embodiment further includes:

[0196] S1730, the Access and Mobility Management Function (AMS) network element sends a second paging message to the network device. Correspondingly, the network device receives the second paging message from the AMS network element.

[0197] Optionally, before step S1730, the communication method provided in this application embodiment further includes:

[0198] The network device sends a paging request message to the access and mobility management function (AMU) network element. Correspondingly, the AMU network element receives the paging request message from the network device.

[0199] In this embodiment, the paging request message may include one or more of the following: paging reason, task type, capability information required by the terminal device, or paging ID information of the terminal device. For a description of the task type and capability information required by the terminal device included in the paging request message, please refer to the description of the aforementioned messages included in the first paging message; this embodiment will not repeat it here.

[0200] In this embodiment, the paging reason may include one or more of the following: paging a fixed terminal device, a requirement for the number of paging terminal devices, signaling configuration, or data transmission, etc., which are not limited in this embodiment. The requirement for the number of paging terminal devices may be used to specify one or more of the following: the number of fixed terminal devices the network device wishes to paging, an upper limit, or a lower limit. Optionally, a fixed terminal device may refer to a stationary terminal device.

[0201] In this embodiment of the application, the paging ID information of the terminal device may include one or more of the following: RAN UE NGAP ID identifier, SUPI, or other information, which are not limited in this embodiment of the application.

[0202] In one possible implementation of this application, the Access and Mobility Management (AMM) network element can retrieve and / or confirm terminal devices based on the aforementioned information. Optionally, the AMM network element can also send a second paging message to the network device based on the paging reason. In this application embodiment, the fields included in the second paging message are shown in Table 2. The TAI field is optional; in this way, the network device can paging only terminal devices within its own scope.

[0203] Table 2

[0204] In one possible implementation, when the paging reason in the paging request message is paging a fixed terminal device, and the Access and Mobility Management Function (AMS) network element finds one or more fixed terminal devices in RRC idle state within the range of the network device, the AMS network element can send a second paging message to the network device. In another possible implementation, when the paging reason in the paging request message is paging a terminal device with a specified terminal device ID, and the AMS network element finds the context information corresponding to that terminal device, the AMS network element can send a second paging message to the network device. Alternatively, the above can be referred to as the conditions for the AMS network element to send a second paging message to the network device.

[0205] In this embodiment of the application, step S1730 can be replaced by:

[0206] The access and mobility management function (AMU) network element sends a failure response to the network device. Correspondingly, the network device receives the failure response from the AMU network element.

[0207] In one possible implementation, when the paging reason in the paging request message is paging a fixed terminal device, and the access and mobility management function (AMU) network element does not find one or more fixed terminal devices in RRC idle state within the network device's range, the AMU network element can send a failure response to the network device. In another possible implementation, when the paging reason in the paging request message is paging a terminal device with a specified terminal device ID, and the AMU network element does not find the context information corresponding to that terminal device, the AMU network element can send a failure response to the network device. Alternatively, the above can be referred to as the conditions under which the AMU network element sends a failure response to the network device.

[0208] In one possible implementation, step S1730 occurs before step S1310, wherein S1310, where the network device sends a first paging message to the terminal device, includes: S1710, where the network device sends the first paging message to the terminal device based on a second paging message. Correspondingly, the terminal device receives the first paging message from the network device.

[0209] The first paging message sent by the network device to the terminal device based on the second paging message may include one or more of the following: paging reason, task type, or capability information required by the terminal device. This information can be referred to the relevant descriptions in the above embodiments and will not be repeated here. The first paging message sent by the network device to the terminal device based on the second paging message may also include the terminal device's paging ID information, which may be 5G-TMSI, etc., and this application embodiment does not limit this.

[0210] Alternatively, in another possible implementation, if the network device has information to directly initiate core network paging to the terminal device (e.g., 5G-TMSI), then step S1730 and the step of the network device initiating a paging request message to the access and mobility management function network element can be omitted, and the network device can send a first paging message to the terminal device based on the information to initiate core network paging.

[0211] In this implementation, the network device can request the access and mobility management function (AMU) network element to page a designated terminal device or a terminal device of a designated type (such as a fixed terminal device) in the RRC idle state, thereby changing the designated terminal device or terminal device of a designated terminal device type (e.g., a fixed terminal device) from the RRC idle state to the RRC connected state. Alternatively, based on the embodiments of this application, the network device can directly page a designated UE in the RRC idle state, thereby changing the terminal device from the RRC idle state to the RRC connected state.

[0212] After the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 17, in step S1320, the terminal device obtains the data collection configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives the data collection configuration information from the network device. That is, this step can be:

[0213] S1740, the network device sends data acquisition configuration information to the terminal device. Correspondingly, the terminal device receives the data acquisition configuration information from the network device.

[0214] Furthermore, optionally, the communication method provided in the embodiments of this application further includes:

[0215] S1750, the terminal device sends a configuration completion message corresponding to the data acquisition configuration information to the network device. Correspondingly, the network device receives the configuration completion message from the terminal device.

[0216] In this embodiment of the application, the configuration completion message includes one or more of the following: data task identifier, configuration success indication, data reporting request, session establishment request, or data collection.

[0217] The data reporting request includes one or more of the following: the duration of data collection, or the amount of data collected.

[0218] The session establishment request includes one or more of the following: transmission type (i.e., indicating whether the collected data is reported and transmitted through the user plane or the data plane), the target node ID for data transmission, or the data task identifier.

[0219] For example, the destination node identifier for data transmission (such as UE Requested Target Node ID) can be used to indicate the identifier of the network device or other destination node. This identifier can be a unique identifier within the mobile network, such as an IP address or MAC address.

[0220] For example, Transmission Type: This indicates the transmission type, which may include one or more of the following: data plane transmission, user plane transmission, etc.

[0221] For example, data plane transmission indicates that the terminal device needs to establish a direct transmission channel with the destination node (e.g., a network device). This field option allows the terminal device and network device to use a data plane protocol stack for configuration and transmission. The data management function requires session configuration for both the terminal device and the network device.

[0222] For example, user plane transmission indicates that the terminal device needs to establish a transmission channel with the destination node (e.g., a network device) through user plane function network elements, and the terminal device forwards data with the network device through user plane function network elements. This field option allows the network device and terminal device to use the user plane protocol stack for configuration and transmission. The data management function requires session configuration for the network device, terminal device, and user plane function network elements.

[0223] For example, this field can also indicate that the destination node of the session is inside the mobile network, i.e., not in the DN.

[0224] In this implementation, the network device can configure the data collection and reporting of terminal devices in the RRC connection state. The terminal device can respond, request data reporting, request session establishment, and / or report collected data through the configuration completion message.

[0225] Alternatively, after the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 18, in step S1320, the terminal device obtains the data acquisition configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives a connection release message from the network device, wherein the connection release message includes the data acquisition configuration information. That is, this step can be:

[0226] In step S1840, the network device sends a connection release message to the terminal device. Correspondingly, the terminal device receives the connection release message from the network device.

[0227] In this embodiment of the application, the connection release message includes configuration information for data acquisition.

[0228] Then, the terminal device switches to the RRC idle state, or the terminal device switches to the RRC inactive state.

[0229] In this implementation, the network device can configure the data collection configuration information of the terminal device in the connection release message and switch the connection state of the terminal device to the RRC idle state or the RRC inactive state.

[0230] Alternatively, in another possible implementation, the first paging message is a core network paging, which is a paging performed by the network device according to the data acquisition instructions of the network functional element, as shown in Figure 19. The communication method provided in this application embodiment further includes:

[0231] S1930, the network function element sends a data acquisition command to the network device. Correspondingly, the network device receives the data acquisition command from the network function element.

[0232] In this embodiment of the application, the data acquisition instruction includes one or more of the following: data task identifier, task type, task content, capability information required by the terminal device, location range information, paging identifier ID of the terminal device, or a list of available terminal devices.

[0233] The data task identifier, the capability information required by the terminal device, and the relevant description of the task type can be referred to in the above embodiments, and will not be repeated here.

[0234] The task content may include one or more of the following: measurement configuration, or the content of the reported results, etc., which are not limited in this application embodiment.

[0235] The location range information indicates the area where data needs to be collected, which can be distinguished by region ID and / or location coordinates.

[0236] Among them, the paging ID of the terminal device represents the terminal device ID information required to paging the idle terminal device, such as 5G-TMSI.

[0237] The list of available terminal devices indicates which network devices can be configured to perform data collection processes on the terminal devices in the list.

[0238] For example, the terminal devices in the list of available terminal devices may be in CM-CONNECTED and / or CM-IDLE states, and this application embodiment does not limit this.

[0239] It should be noted that step S1930 occurs before step S1310. Step S1310, in which the network device sends a first paging message to the terminal device, includes: S1910, where the network device sends a first paging message to the terminal device according to a data acquisition instruction. Correspondingly, the terminal device receives the first paging message from the network device.

[0240] In this embodiment, the network device receives a data acquisition command from a network function element. If configuration is required for a terminal device in the RRC idle state, the network device can perform a core network paging of the specified terminal device based on the paging ID of the terminal device in the data acquisition command, that is, the network device sends a first paging message to the terminal device.

[0241] In this implementation, the network device can page a designated terminal device in the RRC idle state according to the instructions of the network function element, thereby changing the terminal device from the RRC idle state to the RRC connected state.

[0242] After the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 19, in step S1320, the terminal device obtains the data collection configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives the data collection configuration information from the network device. That is, this step can be:

[0243] In step S1940, the network device sends data acquisition configuration information to the terminal device. Correspondingly, the terminal device receives the data acquisition configuration information from the network device.

[0244] Furthermore, optionally, the communication method provided in the embodiments of this application further includes:

[0245] S1950, the terminal device sends a configuration completion message corresponding to the data acquisition configuration information to the network device. Correspondingly, the network device receives the configuration completion message from the terminal device.

[0246] In this embodiment of the application, the configuration completion message can be referred to the relevant description in step S1750, and will not be repeated here.

[0247] In this implementation, the network device can configure the data collection and reporting of terminal devices in the RRC connection state. The terminal device can respond, request data reporting, request session establishment, and / or report collected data through the configuration completion message.

[0248] Alternatively, after the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 20, in step S1320, the terminal device obtains the data acquisition configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives a connection release message from the network device, wherein the connection release message includes the data acquisition configuration information. That is, this step can be:

[0249] In step S2040, the network device sends a connection release message to the terminal device. Correspondingly, the terminal device receives the connection release message from the network device.

[0250] In this embodiment of the application, the connection release message includes configuration information for data acquisition.

[0251] Furthermore, the terminal device can switch to the RRC idle state, or the terminal device can switch to the RRC inactive state.

[0252] In this implementation, the network device can configure the data collection configuration information of the terminal device in the connection release message and switch the connection state of the terminal device to the RRC idle state or the RRC inactive state.

[0253] Alternatively, in another possible implementation, the first paging message is a broadcast paging message (it should be noted that when the first paging message is a broadcast paging message, the paging reason corresponding to the first paging message may include broadcast paging), which is a paging directly performed by the network device to a non-designated terminal device, that is, the network device can send the first paging message to at least one terminal device (i.e., a non-designated terminal device) within a certain range.

[0254] In this embodiment of the application, for a terminal device, the terminal device receives a first paging message from a network device and can switch from the RRC idle state to the RRC connected state according to the first paging message.

[0255] For a terminal device in RRC idle state, in one possible implementation, after receiving the first paging message, if the first paging message is a broadcast paging message (i.e., not paging a specific terminal device), and if it contains relevant parameters such as a task ID or capability ID, and the terminal device can complete the specified task or meet the corresponding capability level, then the terminal device can initiate a connection establishment request (RRC Setup Request) to switch from RRC idle state to RRC connected state. In another possible implementation, if the first paging message only indicates that it is a broadcast paging message (i.e., not paging a specific terminal device), then the terminal device can initiate a connection establishment request.

[0256] In this implementation, the network device can page non-designated terminal devices in the RRC idle state, thereby changing the terminal devices that meet the paging conditions from the RRC idle state to the RRC connected state.

[0257] After the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 21, in step S1320, the terminal device obtains the data collection configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives the data collection configuration information from the network device. That is, this step can be:

[0258] S2130, the network device sends data acquisition configuration information to the terminal device. Correspondingly, the terminal device receives the data acquisition configuration information from the network device.

[0259] Furthermore, optionally, the communication method provided in the embodiments of this application further includes:

[0260] S2140, the terminal device sends a configuration completion message corresponding to the data acquisition configuration information to the network device. Correspondingly, the network device receives the configuration completion message corresponding to the data acquisition configuration information from the terminal device.

[0261] In this embodiment of the application, the configuration completion message can be referred to the relevant description in step S1750, and will not be repeated here.

[0262] In this implementation, the network device can configure the data collection and reporting of terminal devices in the RRC connection state. The terminal device can respond, request data reporting, request session establishment, and / or report collected data through the configuration completion message.

[0263] Alternatively, after the terminal device switches from the RRC idle state to the RRC connected state according to the first paging message, optionally, in one possible implementation, as shown in Figure 22, in step S1320, the terminal device obtains the data acquisition configuration information according to the first paging message, including: the terminal device establishes an RRC connected state according to the first paging message and receives a connection release message from the network device, wherein the connection release message includes the data acquisition configuration information. That is, this step can be:

[0264] S2230, the network device sends a connection release message to the terminal device. Correspondingly, the terminal device receives the connection release message from the network device.

[0265] In this embodiment of the application, the connection release message includes configuration information for data acquisition.

[0266] Furthermore, the terminal device can switch to the RRC idle state, or the terminal device can switch to the RRC inactive state.

[0267] In this implementation, the network device can configure the data collection configuration information of the terminal device in the connection release message and switch the connection state of the terminal device to the RRC idle state or the RRC inactive state.

[0268] For the above embodiments, the downlink control information (DCI) corresponding to the first paging message includes one or more of the following: terminal device level information, terminal device type information, or paging reason.

[0269] In this application embodiment, the level of the terminal device includes one or more of the following: the capability level of the terminal device, or the power consumption or energy saving level of the terminal device.

[0270] In this application embodiment, the type of terminal device includes one or more of the following: sensor, low-power device, other terminal device types besides sensor and low-power device, or all terminal device types.

[0271] In this embodiment of the application, the paging reason may include one or more of the following: unicast paging, or broadcast paging, etc.

[0272] Unicast paging indicates that the first paging message corresponding to this DCI is sent to a specific terminal device. Broadcast paging indicates that the first paging message corresponding to this DCI is sent to unspecified terminal devices.

[0273] In this embodiment of the application, the level information of the terminal device includes one or more of the following: a specified terminal device level, the upper limit of the terminal device level, or the lower limit of the terminal device level, or other level information, which is not limited in this embodiment of the application.

[0274] The terminal device type information may include one or more of the following: a specified terminal device type, or a terminal device type other than the specified terminal device type, or other terminal device types. This application embodiment does not limit this.

[0275] For example, if the paging reason in the DCI received by the terminal device is a broadcast paging, the terminal device can directly initiate the connection establishment or connection restoration process.

[0276] For example, the terminal device can determine whether to continue decoding the first paging message based on the terminal device's level information, terminal device type information, or paging reason in the DCI.

[0277] For example, terminal device level information, terminal device type information, or paging reason can be indicated using at least 1 bit.

[0278] For example, terminal device level information, terminal device type information, or paging reason can be directly carried in the DCI message fields. Table 3 provides an example containing the above key fields.

[0279] Table 3

[0280] For example, terminal device level information, terminal device type information, or paging reason can be carried in the Short Messages field of the DCI message. Table 4 gives an example containing the above key fields.

[0281] Table 4

[0282] In this way, the terminal device can more quickly determine the purpose of the first paging message based on the DCI message, and can choose not to further decode the first paging message and / or not to respond to the first paging message, thereby reducing energy consumption. In addition, the terminal device can also directly initiate the connection establishment or recovery process based solely on the DCI message, thus reducing the decoding process of the first paging message and further reducing energy consumption.

[0283] In this embodiment, the network device sends a first paging message to the terminal device. The terminal device receives the first paging message from the network device, thereby enabling the network device to configure subsequent data collection configuration information based on the first paging message sent to the terminal device.

[0284] This application also provides the entity architecture and processing procedures for the sending end's RRC / SDAP / other upper-layer protocol layers.

[0285] In this embodiment of the application, RRC, SDAP or other protocol layer entities can transmit the same data stream to multiple designated lower protocol layer entities according to the RRC configuration, as shown in Figure 23.

[0286] In one possible embodiment a, SDAP configuration messages (e.g., SDAP-Config messages) can configure the same QFI (QoS Stream ID) for different radio bearers under the same PDU session (e.g., the same PDU session ID).

[0287] In one possible sub-implementation a1, multiple radio bearer SDAP configuration message (e.g., SDAP-Config message) instances under the same PDU session can be configured with the same QFI through mappedQoS-FlowsToAdd.

[0288] In one possible sub-implementation a2, the QFI of the data streams carried in multiple radio bearers within the same PDU session is completely identical.

[0289] In one possible sub-implementation a3, after receiving data from the upper layer, the SDAP layer protocol stack entity can send data to one or more specified lower layer protocol stack entities (e.g., PDCP entities) based on the data's QFI.

[0290] In one possible embodiment b, the configuration message of the DRB (Data Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more lower-layer protocol stack entities (e.g., PDCP entities) for the same DRB (e.g., having the same DRB ID).

[0291] In one possible sub-implementation b1, the configuration message of the DRB (e.g., the DRB-ToAddMod field in the RadioBearerConfig message) can include a list of lower-layer protocol stack entities (e.g., PDCP-Config-list) to associate the DRB with one or more lower-layer protocol stack entities (e.g., PDCP entities) and configure them accordingly.

[0292] In one possible sub-implementation b2, the configuration of one or more lower-level protocol stack entities (e.g., PDCP entities) associated with the same DRB can be configured by adding the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-level protocol stack entity (e.g., RLC entity) to associate it with the lower-level protocol stack entity (e.g., RLC entity).

[0293] In one possible sub-implementation b3, after receiving data from the upper layer, the SDAP layer protocol stack entity can send the data to one or more lower layer protocol stack entities (e.g., PDCP entities) associated with the corresponding DRB.

[0294] In one possible embodiment c, the configuration message of the SRB (Signaling Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more lower-level protocol stack entities (e.g., PDCP entities) for the same SRB (e.g., having the same SRB ID).

[0295] In one possible sub-implementation c1, the configuration message of the SRB (e.g., the SRB-ToAddMod field in the RadioBearerConfig message) can be supplemented with a list of lower-level protocol stack entities (e.g., PDCP-Config-list) to associate the SRB with one or more lower-level protocol stack entities (e.g., PDCP entities) and configure them accordingly.

[0296] In one possible sub-implementation c2, the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-level protocol stack entity (e.g., RLC entity) can be added to the configuration of one or more lower-level protocol stack entities (e.g., PDCP entities) associated with the same SRB to associate with the RLC entity.

[0297] In one possible sub-implementation c3, after receiving the data to be sent, the RRC layer protocol stack entity can send the data to one or more lower layer protocol stack entities (e.g., PDCP entities) associated with the corresponding SRB.

[0298] In one possible embodiment d, an RRC, SDAP, or other protocol layer entity can be associated with one or more lower protocol layer entities (e.g., PDCP entities) according to an RRC configuration. The associated lower protocol layer entities (e.g., PDCP entities) can belong to the same radio bearer or different radio bearers.

[0299] In one possible scenario, the embodiments of this application can implement the following process:

[0300] (1) According to embodiments a, a1 and a2, an SDAP entity may be associated with multiple lower-layer protocol stack entities (e.g., PDCP entities), and each of the multiple lower-layer protocol stack entities (e.g., PDCP entities) belongs to a different radio bearer, and the QFI of the QoS streams carried by the multiple lower-layer protocol stack entities (e.g., PDCP entities) is completely consistent.

[0301] (2) According to embodiment a3, after receiving data from the upper layer, if the QFI of the data is consistent with the QFI configuration of the multiple lower layer protocol stack entities (e.g., PDCP entities), the SDAP entity can send data to the multiple lower layer protocol stack entities (e.g., PDCP entities) according to the QFI of the data.

[0302] In one possible scenario, the embodiments of this application can implement the following process:

[0303] (1) According to embodiments b, b1 and b2, an SDAP entity may be associated with multiple lower-level protocol stack entities (e.g., PDCP entities), and these multiple lower-level protocol stack entities (e.g., PDCP entities) belong to the same DRB. At the same time, these multiple lower-level protocol stack entities (e.g., PDCP entities) can be associated with their respective lower-level protocol stack entities (e.g., RLC entities) through the LCH ID of the lower-level protocol stack entities (e.g., RLC entities).

[0304] (2) According to embodiment b3, after receiving data from the upper layer, the SDAP entity can send the data to multiple lower layer protocol stack entities (e.g., PDCP entities) associated with the DRB.

[0305] In one possible scenario, embodiments of this application can implement one or more of the following processes:

[0306] (1) According to embodiments c, c1 and c2, an RRC entity can be associated with multiple lower-level protocol stack entities (e.g., PDCP entities), and these multiple lower-level protocol stack entities (e.g., PDCP entities) belong to the same SRB. At the same time, these multiple lower-level protocol stack entities (e.g., PDCP entities) can be associated with their respective lower-level protocol stack entities (e.g., RLC entities) through the LCH ID of the lower-level protocol stack entities (e.g., RLC entities).

[0307] (2) According to embodiment c3, after receiving data from the upper layer, the RRC entity can send the data to multiple lower layer protocol stack entities (e.g., PDCP entities) associated with the SRB.

[0308] It should be noted that the RRC configuration mentioned above can also be other types of configuration information. In this application embodiment, RRC configuration is used as an example for illustration, and this application embodiment does not limit it.

[0309] Based on the embodiments of this application, RRC, SDAP, or other protocol layer entities can copy and distribute data received from the upper layer and / or generated by this layer to different lower layer protocol stack entities, thereby enabling the same data stream to enter a bearer processing process that meets different transmission requirements.

[0310] This application also provides the PDCP protocol layer entity architecture and processing procedure for the sending end in the embodiments.

[0311] In this embodiment, a PDCP entity can be associated with one or more RLC entities according to RRC configuration, and the PDCP entity can transmit data to a specified RLC entity according to the RRC configuration, as shown in Figure 24. Here, the number of "specified RLC entities" can be less than or equal to the number of RLC entities associated with the PDCP entity, and this embodiment does not limit this.

[0312] In one possible embodiment a, the PDCP configuration message (e.g., the PDCP-Config message) can be supplemented with the RLC's LCH ID field to associate the primary RLC entity.

[0313] In one possible sub-implementation a1, the PDCP entity determines the primary RLC entity based on the RLC LCH ID field (e.g., primary Logical Channel Identity) in the PDCP configuration message (e.g., PDCP-Config message), and only sends data to the primary RLC entity, without sending data to other auxiliary RLC entities.

[0314] In one possible sub-implementation a2, if the PDCP configuration message (e.g., PDCP-Config message) does not contain an RLC LCH ID field (e.g., primary Logical Channel Identity) that can be associated with the primary RLC entity, then the PDCP entity sends data to all associated RLC entities.

[0315] Based on embodiments a, a1, and / or a2, the PDCP entity can send data received from the upper layer only to the main RLC entity, thereby enabling only the data of the main RLC entity to be transmitted over the air interface.

[0316] In one possible embodiment b, when the PDCP entity at the sending end receives a PDCP Status Report message from one or more associated RLC entities, the PDCP entity will discard the successfully received PDCP SDU only if all the PDCP Status Report messages reported by the PDCP entity's associated RLC entities indicate the successful reception of a PDCP SDU.

[0317] In one possible sub-implementation b1, if the PDCP entity does not meet the requirement that all associated RLC entities of the PDCP entity have reported a successful PDCP SDU in their PDCP Status Report messages, the PDCP entity will perform a discard operation based on the discard timer of the PDCP SDU.

[0318] Based on embodiments b and / or b1, the sending PDCP entity can process PDCP Status Report messages from one or more associated RLC entities.

[0319] In one possible embodiment c, when the PDCP entity at the sending end needs to send a PDCP SN Gap Report message to the PDCP entity at the receiving end, the PDCP entity at the sending end can send the PDCP SN Gap Report message to all associated RLC entities.

[0320] Based on embodiment c, if the receiving end has multiple PDCP entities associated with a PDCP entity of the sending end, the sending end's PDCP entity can send a PDCP SN Gap Report message to each associated receiving end PDCP entity.

[0321] In one possible embodiment d, when the PDCP entity at the transmitting end receives UDC feedback from one or more associated RLC entities, it can determine whether to process the UDC feedback based on a timer state and a specified threshold. If the timer state meets the threshold condition, the PDCP entity processes the UDC feedback. If the timer state does not meet the threshold condition, the PDCP entity does not process the UDC feedback.

[0322] In one possible sub-implementation d1, the timer state is reset after the PDCP entity processes a UDC feedback.

[0323] Based on embodiments d and / or d1, the PDCP entity at the sending end can avoid duplication and / or frequent processing of UDC feedback messages.

[0324] It should be noted that the lower-level protocol layer entity associated with the aforementioned PDCP entity can also be other lower-level protocol stack entities that have some of the functions of the RLC entity.

[0325] This application also provides the RLC protocol layer entity architecture and processing procedure for the sending end in the embodiments.

[0326] In this embodiment, two or more RLC protocol layer entities are associated. One RLC protocol layer entity is the primary RLC entity, and the others are secondary RLC entities. The associated RLC entities may belong to the same radio bearer or different radio bearers.

[0327] In one possible embodiment a, the association between RLC entities and / or the designation of primary and secondary RLC entities are configured by RRC signaling and / or other signaling.

[0328] In one possible sub-implementation a1, whether the corresponding RLC entity is a primary RLC entity or a secondary RLC entity can be indicated in one or more of the following ways:

[0329] (1) Fields (e.g., primary RLC) can be added to RLC configuration messages (e.g., RLC-BearerConfig) to indicate whether the corresponding RLC entity is the primary RLC entity.

[0330] (2) Fields (e.g., secondary RLC) can be added to the RLC configuration message (e.g., RLC-BearerConfig) to indicate whether the corresponding RLC entity is a secondary RLC entity.

[0331] In one possible sub-implementation a2, the association between the main RLC entity and the auxiliary RLC entity can be indicated in one or more of the following ways:

[0332] (1) Fields (e.g., primary RLC LCH ID) can be added to the RLC configuration message (e.g., RLC-BearerConfig) of the secondary RLC entity to indicate the corresponding primary RLC entity.

[0333] (2) A field (e.g., secondary RLC LCH ID) can be added to the RLC configuration message (e.g., RLC-BearerConfig) of the primary RLC entity to indicate the corresponding secondary RLC entity.

[0334] (3) After determining that the main RLC entity and / or the auxiliary RLC entity are the same upper-layer protocol stack entity and / or the same radio bearer RLC entities, the main RLC entity and the auxiliary RLC entity can be associated.

[0335] In one possible embodiment b, data interaction can occur between the primary RLC entity and the secondary RLC entity.

[0336] In one possible embodiment c, the primary RLC entity is the RLC UM sending entity, and the secondary RLC entity is the RLC AM entity, as shown in Figures 25 and 27.

[0337] In one possible embodiment d, the main RLC entity is an RLC AM entity and the auxiliary RLC entity is an RLC AM entity, as shown in Figures 26 and 28.

[0338] In one possible sub-implementation d1, the configurations of the main RLC entity and the auxiliary RLC entity can be different.

[0339] In one possible embodiment e, the secondary RLC entity can be one or more RLC AM entities. If the secondary RLC entity is multiple RLC AM entities, the configuration of each RLC AM entity can be different.

[0340] In one possible embodiment f, a designated RLC protocol layer entity (RLC entity 1 in Figures 25 and 26, i.e., the "primary RLC entity") can, according to the RRC configuration, send control information to other designated RLC protocol layer entities (RLC entity 2 in Figures 25 and 26, i.e., the "secondary RLC entity"), and / or receive data from the upper protocol layer entity.

[0341] In one possible sub-implementation f1, the primary RLC entity may send one or more of the following to the secondary RLC entity according to the RRC configuration: received data from the upper protocol layer entity, SN (sequence number) information corresponding to the received data from the upper protocol layer entity, ACK (acknowledgment) information, other control information, etc.

[0342] In one possible sub-implementation f1-1, the ACK (acknowledgment) information comes from the reception status report of the receiver corresponding to the main RLC entity.

[0343] In one possible sub-implementation f1-2, the ACK (acknowledgment) message is used to indicate whether the data transmission of the main RLC entity was successful and / or failed.

[0344] In one possible sub-implementation f1-3, if the auxiliary RLC entity is an RLC AM entity and the auxiliary RLC entity receives the ACK information sent by the main RLC entity, the transmission window parameters of the auxiliary RLC entity are updated according to the successful reception status indicated by the ACK information (e.g., the status variable TX_Next_Ack (used to indicate the next SDU to be acknowledged)).

[0345] Beneficial effects: Examples f1-1, f1-2, and / or f1-3 can be mainly used to send ACK information to the auxiliary RLC entity to update parameters and / or reset timers when the receiving end master RLC entity sends a reception status report to the sending end master RLC entity, in order to avoid the receiving end auxiliary RLC entity repeatedly sending the reception status report.

[0346] In one possible sub-implementation f1-4, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (such as duplicate Transmit Config) to indicate what the primary RLC entity sends to the secondary RLC entity. This field may contain one or more of the following:

[0347] (1) Data: Data received from the upper protocol layer entity.

[0348] (2) SN: The SN (sequence number) information corresponding to the data received from the upper protocol layer entity.

[0349] (3) ACK: ACK (acknowledgment) information.

[0350] In one possible sub-implementation f2, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as duplicate Transmit) added to indicate whether the primary RLC entity needs to send control information and / or data.

[0351] In one possible sub-implementation f3, the primary RLC entity sends the received data from the upper protocol layer entity and its corresponding RLC SN (sequence number) information to the secondary RLC entity by maintaining state variables and according to a specified threshold.

[0352] In one possible sub-implementation f3-1, the primary RLC entity resets its state variables after sending the received data from the upper protocol layer entity and its corresponding RLC SN (sequence number) information to the secondary RLC entity.

[0353] In one possible sub-implementation f3-2, the specified threshold may be one or more of the following: 1. A threshold for the number of SDU data received from the upper layer. 2. A threshold for the number of initial SDU data sent to the lower layer. 3. A timer timing threshold.

[0354] In one possible sub-implementation f3-3, the state variable can be one or more of the following: 1. The number of SDU data received from the upper layer. 2. The number of SDU data initially transmitted to the lower layer. 3. The timer's timing result.

[0355] Beneficial effects: Based on embodiments f, f3, f3-1, f3-2 and / or f3-3, the primary RLC entity can periodically or non-periodically send the data received from the upper protocol layer entity and its corresponding RLC SN (sequence number) information to the secondary RLC entity. This can provide the secondary RLC entity with the RLC SN number corresponding to the SDU data on the primary RLC entity side, so that the secondary RLC entity can use this information to synchronize with the RLC SN number corresponding to the primary RLC entity data.

[0356] In one possible embodiment g, an RLC protocol layer entity (RLC entity 2 in Figures 25 and 26, i.e., "secondary RLC entity") can receive control information and / or data from a designated other RLC protocol layer entity (RLC entity 1 in Figures 25 and 26, i.e., "primary RLC entity") according to the RRC configuration.

[0357] In one possible sub-implementation g1, the auxiliary RLC entity may receive one or more of the following from the primary RLC entity according to the RRC configuration: received data from the upper protocol layer entity, SN (sequence number) information corresponding to the received data from the upper protocol layer entity, ACK (acknowledgment) information, other control information, etc.

[0358] In one possible sub-implementation g1-1, the ACK (acknowledgment) information comes from the reception status report of the receiver corresponding to the main RLC entity.

[0359] In one possible sub-implementation g1-2, the ACK (acknowledgment) message is used to indicate whether the data transmission of the main RLC entity was successful and / or failed.

[0360] In one possible sub-implementation g1-3, if the auxiliary RLC entity is an RLC AM entity and the auxiliary RLC entity receives the ACK information sent by the main RLC entity, the sending window parameters of the auxiliary RLC entity (such as the status variable TX_Next_Ack (used to indicate the next SDU to be acknowledged)) are updated according to the successful reception status of the receiving end indicated by the ACK information.

[0361] Beneficial effects: Examples g1-1, g1-2, and / or g1-3 can be mainly used so that when the receiving end master RLC entity sends a reception status report to the sending end master RLC entity, in order to avoid the receiving end auxiliary RLC entity repeatedly sending the reception status report, the sending end auxiliary RLC entity can receive ACK information from the master RLC entity to update parameters and / or reset timers.

[0362] In one possible sub-implementation g1-4, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (such as duplicate Transmit Config) to indicate what the primary RLC entity sends to the secondary RLC entity. This field may contain one or more of the following:

[0363] (1) Data: Data received from the upper protocol layer entity.

[0364] (2) SN: The SN (sequence number) information corresponding to the data received from the upper protocol layer entity.

[0365] (3) ACK: ACK (acknowledgment) information.

[0366] In one possible sub-implementation g2, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as duplicate Transmit) added to indicate whether the secondary RLC entity needs to receive control information and / or data.

[0367] In one possible sub-implementation g3, the auxiliary RLC entity receives data and its corresponding RLC SN (sequence number) information from the upper protocol layer entity from the primary RLC entity.

[0368] In one possible sub-implementation g3-1, the secondary RLC entity compares the data received from the primary RLC entity and its RLC SN with the data directly received from the upper-layer protocol entity (e.g., the PDCP entity) and its RLC SN, ensuring that the RLC SNs corresponding to the same data are identical. If a discrepancy is found, the secondary RLC entity needs to update the state variables associated with the SN so that the SNs of subsequent data can also be aligned with the SNs of the primary RLC entity. If there is RLC SDU data within the secondary RLC entity whose SN cannot be corrected, the secondary RLC entity discards this data.

[0369] In one possible sub-implementation g3-1-1, the secondary RLC entity uses the data received from the primary RLC entity and its RLC SN number only for SN number synchronization. The data sent down to the lower layer by the secondary RLC entity comes directly from the upper layer protocol stack entity (e.g., the PDCP entity).

[0370] Beneficial effects: Based on embodiments g, g3, g3-1, and / or g3-1-1, the auxiliary RLC entity can synchronize the SN numbers between the primary and auxiliary RLC entities according to the data received from the primary RLC entity and its RLC SN number. Furthermore, in the event of SN mismatch, the auxiliary RLC entity will perform SN updates and / or data discarding operations.

[0371] In one possible embodiment h, the RLC protocol layer entity can buffer received data and temporarily withhold it from the lower-level protocol stack entity according to the RRC configuration. The RLC protocol layer entity can be a secondary RLC entity.

[0372] In one possible sub-implementation h1, the received data may come from the main RLC entity and / or from an upper protocol layer entity.

[0373] In one possible sub-implementation h2, the RLC protocol layer entity can generate and cache the corresponding RLC header simultaneously when caching the received data.

[0374] In one possible sub-implementation h3, when the configuration in the RLC configuration message (e.g., RLC-BearerConfig) meets one or more of the following conditions, the auxiliary RLC entity will buffer the received data and temporarily not send it to the lower-layer protocol stack entity:

[0375] (1) The field secondary RLC indicates that the RLC entity is a secondary RLC entity.

[0376] (2) The field secondary RLC LCH ID indicates the ID of the secondary RLC entity and is consistent with the RLC entity.

[0377] (3) The duplicate Transmit field indicates that the RLC entity needs to receive control information and / or data from the main RLC entity.

[0378] (4) The duplicate Transmit Config field indicates the type of content that this RLC entity needs to receive from the main RLC entity.

[0379] (5) The field "no first transmit" indicates that the RLC entity will buffer the received data and not send it to the lower protocol stack entity for the time being.

[0380] In one possible embodiment i, the RLC protocol layer entity can be configured according to RRC to not trigger the transmission of data to be transmitted when the transmission window changes. Here, the RLC protocol layer entity can be a secondary RLC entity. ("Data to be transmitted" here refers to SDU data that has not been assigned a serial number because the untransmitted data exceeds the transmission window.)

[0381] In one possible sub-implementation i1, the auxiliary RLC entity will not trigger the transmission of data to be transmitted when the transmission window changes, provided that one or more of the following conditions are met in the RLC configuration message (such as RLC-BearerConfig):

[0382] (1) The field secondary RLC indicates that the RLC entity is a secondary RLC entity.

[0383] (2) The field secondary RLC LCH ID indicates the ID of the secondary RLC entity and is consistent with the RLC entity.

[0384] (3) The duplicate Transmit field indicates that the RLC entity needs to receive control information and / or data from the main RLC entity.

[0385] (4) The duplicate Transmit Config field indicates the type of content that this RLC entity needs to receive from the main RLC entity.

[0386] (5) The field "no transmit with window varying" indicates that the RLC entity will not trigger the transmission of data to be transmitted when the transmit window changes.

[0387] In one possible embodiment j, the RLC protocol layer entity, according to the RRC configuration, allocates SN numbers to the data to be transmitted based on the remaining available SN numbers when the transmission window changes, and puts the data with the newly allocated SN numbers into the buffer. The RLC protocol layer entity can be a secondary RLC entity. (Here, "data to be transmitted" refers to SDU data that has not been allocated an SN number because the untransmitted data exceeds the transmission window.)

[0388] In one possible sub-implementation j1, when the configuration in the RLC configuration message (e.g., RLC-BearerConfig) satisfies one or more of the following conditions, the auxiliary RLC entity will allocate SN numbers for the data to be transmitted based on the remaining available SN numbers when the transmission window changes, and put the data with the newly allocated SN numbers into the buffer:

[0389] (1) The field secondary RLC indicates that the RLC entity is a secondary RLC entity.

[0390] (2) The field secondary RLC LCH ID indicates the ID of the secondary RLC entity and is consistent with the RLC entity.

[0391] (3) The duplicate Transmit field indicates that the RLC entity needs to receive control information and / or data from the main RLC entity.

[0392] (4) The duplicate Transmit Config field indicates the type of content that this RLC entity needs to receive from the main RLC entity.

[0393] (5) The field buffer with window varying indicates that when the transmission window changes, the auxiliary RLC entity will allocate SN numbers for the data to be transmitted based on the remaining available SN numbers, and put the data with the newly allocated SN numbers into the buffer.

[0394] In one possible implementation k, the RLC PDU in UM mode needs to include an SN number.

[0395] In one possible embodiment k1, the RLC PDU structure in UM mode can be shown in Figures 29 to 34.

[0396] Beneficial effects: Based on embodiment k, and / or k1, in the UM-AM structure, the SN numbers of the data sent by the RLC entities of UM and AM can be synchronized, thereby enabling cooperation between the main RLC entity and the auxiliary RLC entity.

[0397] In one possible embodiment m, when the sending end's primary RLC entity receives a control message to discard SDU data from the upper-layer protocol stack entity (e.g., the PDCP entity), if the SDU data or its fragments to be discarded have not yet been sent down to the lower layer, regardless of whether the primary RLC entity is in UM mode or AM mode, the primary RLC entity needs to discard the SDU data. At the same time, the primary RLC entity needs to update the SN number to avoid the occurrence of SN gap.

[0398] In one possible sub-implementation m1, if the RRC is configured to send SDU discard control information from the primary RLC entity to the secondary RLC entity, when the primary RLC entity needs to discard SDU data, the primary RLC entity at the sending end can send control information (such as the PDCP of the SDU to be discarded and / or the SN number of the RLC, and / or the SDU data to be discarded, etc.) to the secondary RLC entity to instruct the secondary RLC entity to discard the corresponding SDU.

[0399] In one possible sub-implementation m1-1, when the secondary RLC entity needs to discard SDU data, the secondary RLC entity needs to update the SN number to avoid the occurrence of SN gap.

[0400] In one possible sub-implementation m1-2, the RLC configuration message (e.g., RLC-BearerConfig) may have a field (such as discard SDU relay) added to indicate whether the primary RLC entity needs to send control information for SDU discarding to the secondary RLC entity.

[0401] Beneficial effects: Based on embodiments m, m1, m1-1, and / or m1-2, the primary RLC entity and the secondary RLC entity associated with the same transmitting PDCP entity can discard the corresponding SDU according to the discard SDU instruction from the PDCP entity. Furthermore, the RLC entities can ensure SN synchronization between RLC entities while avoiding SN gaps.

[0402] In one possible embodiment n, both the primary RLC entity and the secondary RLC entity possess data transmission and reception functions. The UM-AM structure is shown in Figure 35, and the AM-AM structure is shown in Figure 36. In Figure 35, RLC entity 1 is the UM transmitting entity, RLC entity 2 is the AM entity, and RLC entity 3 is the UM receiving entity. In Figure 36, both RLC entity 1 and RLC entity 2 are AM entities. In Figure 35, 1 corresponds to Figure 26, and 2 corresponds to Figure 27. In Figure 36, 1 corresponds to Figure 26, and 2 corresponds to Figure 28. The specific transmission and reception processes of the UM-AM and AM-AM structures in Figures 29 and 30 can be found in the above embodiments.

[0403] In one possible scenario, the embodiments of this application can implement the following process:

[0404] (1) According to embodiments a to e and their sub-embodiments, two RLC protocol layer entities can be associated, and the primary RLC entity and the secondary RLC entity, as well as their respective radio bearers, can be determined. Additionally, the type of the RLC entity can be determined, for example, UM or AM. In this possible scenario, the primary RLC entity is a UM RLC entity, and the secondary RLC entity is an AM RLC entity, as shown in Figure 25.

[0405] (2) During the transmission phase, the primary RLC entity performs relevant operations according to embodiments f and f1, transmitting the data received from the upper layer to the secondary RLC entity. Simultaneously, because the primary RLC entity is a UM RLC, it generates an RLC header based on the data received from the upper layer and stores the data and header in the transmission buffer. When the lower layer has a transmission opportunity, the primary RLC entity performs possible segmentation operations and modifies the RLC header according to the transmission opportunity. Finally, the primary RLC entity adds an RLC header before the corresponding RLC SDU or RLC SDU segment and transmits it to the lower layer.

[0406] (3) During the transmission phase, the auxiliary RLC entity performs relevant operations according to embodiments g and g1 to receive data from the upper layer from the primary RLC entity. Then, according to embodiment h, the auxiliary RLC entity buffers the received data and does not send it to the lower layer protocol stack entity for the time being. At the same time, the auxiliary RLC entity generates the corresponding RLC packet header according to embodiment h2 and buffers it.

[0407] (4) During the transmission phase, since the auxiliary RLC entity is an AM RLC entity, it will receive a reception status report from the AM RLC entity of the receiving end.

[0408] (a) If the reception status report indicates a successfully received packet, the secondary RLC entity will discard the packet that has successfully arrived at the receiver and update the relevant parameters of the transmission window. Meanwhile, according to embodiments i and j, the secondary RLC entity will not trigger the transmission of data to be transmitted when the transmission window changes, and will allocate SN numbers for the data to be transmitted based on the remaining available SN numbers, and put the data with the newly allocated SN numbers into the buffer.

[0409] (b) If the reception status report indicates a failed reception packet, the secondary RLC entity will send the indicated failed reception packet. Specifically, when there is a transmission opportunity at the lower layer, the secondary RLC entity will perform possible segmentation operations on the packets to be sent and modify the RLC header according to the transmission opportunity at the lower layer. Then, the secondary RLC entity will add the RLC header before the corresponding RLC SDU or RLC SDU segment and transmit it to the lower layer.

[0410] It should be noted that the upper protocol layer entity of the RLC layer entity in the embodiments of this application can be a PDCP layer entity or other protocol layer entities.

[0411] It should be noted that the lower protocol layer entity of the RLC layer entity in the embodiments of this application can be a MAC layer entity or other protocol layer entities.

[0412] Beneficial effects: Based on the embodiments of this application, the primary RLC entity and the secondary RLC entity of the sending end can achieve successful transmission only once on the air interface through the cooperation mechanism. That is, only the failure of the primary RLC entity's transmission may cause multiple transmissions (i.e., retransmission) until the transmission is successful. At the same time, the embodiments of this application also meet different transmission requirements, so that the data meets both low latency and high reliability during the transmission process.

[0413] This application also provides the RLC protocol layer entity architecture and processing procedure of the receiving end in the embodiments.

[0414] In this embodiment, two or more RLC protocol layer entities are associated. One RLC protocol layer entity is the primary RLC entity, and the others are secondary RLC entities. The associated RLC entities may belong to the same radio bearer or different radio bearers.

[0415] In one possible embodiment a, the association between RLC entities and / or the designation of primary and secondary RLC entities are configured by RRC signaling and / or other signaling.

[0416] In one possible sub-implementation a1, whether the corresponding RLC entity is a primary RLC entity or a secondary RLC entity can be indicated in one or more of the following ways:

[0417] (1) Fields (e.g., primary RLC) can be added to RLC configuration messages (e.g., RLC-BearerConfig) to indicate whether the corresponding RLC entity is the primary RLC entity.

[0418] (2) Fields (e.g., secondary RLC) can be added to the RLC configuration message (e.g., RLC-BearerConfig) to indicate whether the corresponding RLC entity is a secondary RLC entity.

[0419] In one possible sub-implementation a2, the association between the main RLC entity and the auxiliary RLC entity can be indicated in one or more of the following ways:

[0420] (1) Fields (e.g., primary RLC LCH ID) can be added to the RLC configuration message (e.g., RLC-BearerConfig) of the secondary RLC entity to indicate the corresponding primary RLC entity.

[0421] (2) A field (e.g., secondary RLC LCH ID) can be added to the RLC configuration message (e.g., RLC-BearerConfig) of the primary RLC entity to indicate the corresponding secondary RLC entity.

[0422] (3) Associating entities in the same upper-layer protocol stack and / or RLC entities in the same radio bearer: After determining the main RLC entity and / or auxiliary RLC entity, the main RLC entity and auxiliary RLC entity can be associated.

[0423] In one possible embodiment b, data interaction can occur between the primary RLC entity and the secondary RLC entity.

[0424] In one possible embodiment c, the primary RLC entity is an RLC UM receiving entity, and the secondary RLC entity is an RLC UM receiving entity, as shown in Figure 37.

[0425] In one possible sub-implementation c1, the configurations of the main RLC entity and the auxiliary RLC entity can be different.

[0426] In one possible embodiment d, the primary RLC entity is the RLC UM receiving entity, and the secondary RLC entity is the RLC AM entity, as shown in Figure 38.

[0427] In one possible embodiment e, the main RLC entity is an RLC AM entity, and the auxiliary RLC entity is an RLC AM entity, as shown in Figure 39.

[0428] In one possible sub-implementation e1, the configurations of the main RLC entity and the auxiliary RLC entity can be different.

[0429] In one possible embodiment f, the secondary RLC entity can be one or more RLC AM entities. If the secondary RLC entity is multiple RLC AM entities, the configuration of each RLC AM entity can be different.

[0430] In one possible embodiment g, a designated RLC protocol layer entity (RLC entity 1 in Figures 37, 38 and 39, i.e., the "primary RLC entity") can, according to the RRC configuration, send control information and / or received data from lower protocol layer entities to other designated RLC protocol layer entities (RLC entity 2 in Figures 37, 38 and 39, i.e., the "secondary RLC entity").

[0431] In one possible sub-implementation g1, the primary RLC entity may send one or more of the following to the secondary RLC entity according to the RRC configuration: received data from the lower protocol layer entity, SN (sequence number) information corresponding to the received data from the lower protocol layer entity, ACK (acknowledgment) information, other control information, etc.

[0432] In one possible sub-implementation g1-1, the ACK (acknowledgment) information is used to indicate whether the data reception of the master RLC entity was successful and / or failed.

[0433] In one possible sub-implementation g1-2, the ACK (acknowledgment) information is used to indicate whether the data reception was successful or failed, as contained in the reception status report sent by the receiving master RLC entity to the sending master RLC entity.

[0434] In one possible sub-implementation g1-3, if the auxiliary RLC entity is an RLC AM entity and the auxiliary RLC entity receives the ACK information sent by the main RLC entity, the auxiliary RLC entity updates its receive window parameters (such as timer t-Reassembly (used to trigger the sending of the receive status report) and / or status variable RX_Next_Status_Trigger (used to trigger the running of timer t-Reassembly)) according to the successful reception status indicated by the ACK information.

[0435] Beneficial effects: Examples g1-1, g1-2, and / or g1-3 can be mainly used to send ACK information to the auxiliary RLC entity to update parameters and / or reset timers when the receiving end master RLC entity sends a reception status report to the sending end master RLC entity, in order to avoid the auxiliary RLC entity repeatedly sending the reception status report.

[0436] In one possible sub-implementation g1-4, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive Config) to indicate what the primary RLC entity sends to the secondary RLC entity. This field may contain one or more of the following:

[0437] (1) Data: Data received from the lower protocol layer entity.

[0438] (2) SN: The SN (sequence number) information corresponding to the data received from the lower protocol layer entity.

[0439] (3) ACK: ACK (acknowledgment) information.

[0440] In one possible sub-implementation g2, the RLC configuration message (e.g., RLC-BearerConfig) may have a field (such as duplicate Receive) added to indicate whether the primary RLC entity needs to send control information and / or data to the secondary RLC entity.

[0441] In one possible embodiment h, the RLC protocol layer entity (RLC entity 2 in Figures 37, 38 and 39, i.e., the “secondary RLC entity”) can receive control information and / or data from the lower layer from other designated RLC protocol layer entities (RLC entity 1 in Figures 37, 38 and 39, i.e., the “primary RLC entity”) according to the RRC configuration.

[0442] In one possible sub-implementation h1, the auxiliary RLC entity may receive one or more of the following from the primary RLC entity according to the RRC configuration: received data from the lower protocol layer entity, SN (sequence number) information corresponding to the received data from the lower protocol layer entity, ACK (acknowledgment) information, other control information, etc.

[0443] In one possible sub-implementation h1-1, the ACK (acknowledgment) information is used to indicate whether the data reception of the main RLC entity was successful and / or failed.

[0444] In one possible sub-implementation h1-2, the ACK (acknowledgment) information is used to indicate whether the data reception was successful or failed, as contained in the reception status report sent by the receiving master RLC entity to the sending master RLC entity.

[0445] In one possible sub-implementation h1-3, if the auxiliary RLC entity is an RLC AM entity and the auxiliary RLC entity receives ACK information sent by the main RLC entity, the auxiliary RLC entity updates its receive window parameters (e.g., timer t-Reassembly (used to trigger the sending of a receive status report) and / or status variable RX_Next_Status_Trigger (used to trigger the execution of timer t-Reassembly) etc.) according to the successful reception status indicated by the ACK information.

[0446] Beneficial effects: Examples h1-1, h1-2, and / or h1-3 can be mainly used so that when the receiving end master RLC entity sends a reception status report to the sending end master RLC entity, in order to avoid the auxiliary RLC entity repeatedly sending the reception status report, the receiving end auxiliary RLC entity can receive ACK information from the master RLC entity to update parameters and / or reset timers.

[0447] In one possible sub-implementation h1-4, the RLC configuration message (e.g., RLC-BearerConfig) may have a field (such as duplicate Receive Config) added to indicate what the primary RLC entity sends to the secondary RLC entity. This field may contain one or more of the following:

[0448] (1) Data: Data received from the lower protocol layer entity.

[0449] (2) SN: The SN (sequence number) information corresponding to the data received from the lower protocol layer entity.

[0450] (3) ACK: ACK (acknowledgment) information.

[0451] In one possible sub-implementation h2, the RLC configuration message (e.g., RLC-BearerConfig) may have a field (such as duplicate Receive) added to indicate whether the secondary RLC entity needs to receive control information and / or data from the primary RLC entity.

[0452] In one possible sub-implementation h3, the auxiliary RLC entity can receive data from the lower protocol layer entity according to the RRC configuration.

[0453] In one possible sub-implementation h3-1, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (such as receive from lower layer) to indicate whether the auxiliary RLC entity needs to receive data from the lower protocol layer entity.

[0454] In one possible embodiment i, the RLC protocol layer entity can perform different processing procedures based on whether the data comes from other RLC protocol layer entities or directly from lower-level protocol layer entities, according to the RRC configuration. The RLC protocol layer entity can be a secondary RLC entity.

[0455] In one possible sub-implementation i1, data from other RLC protocol layer entities needs to enter an additional receive buffer compared to data directly from lower protocol layer entities, as shown in Figure 40.

[0456] In one possible sub-implementation i1-1, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as buffer for duplicate Receive) added to indicate whether the secondary RLC entity needs to put data from other RLC protocol layer entities into an additional receive buffer.

[0457] In one possible sub-implementation i1-2, the receiving process in FIG40 can specifically be the process shown in FIG41, that is, the receiving process consists of receiving window, removing RLC packet header, SDU reassembly and other processes.

[0458] In one possible sub-implementation i1-2-1, if the data in the receive buffer in Figure 41 falls outside the receive window, the data in the receive buffer will not enter the receive window temporarily until the data falls inside the receive window.

[0459] In one possible embodiment j, the RLC protocol layer entity can be configured according to RRC, and its receive window can process data from other RLC protocol layer entities and / or data from lower-level protocol layer entities. The RLC protocol layer entity can be a secondary RLC entity.

[0460] In one possible sub-implementation j1, the RLC configuration message (e.g., RLC-BearerConfig) may have one or more of the following fields added to indicate whether the receive window of the secondary RLC entity can process data from other RLC protocol layer entities and / or data from lower protocol layer entities.

[0461] (1) The receive window input field (e.g., 2 bits) is used to indicate the processing content of the receive window of the auxiliary RLC entity, which may involve one or more of the following: 1. It can process data from other RLC protocol layer entities and data from lower protocol layer entities; 2. It can process data from other RLC protocol layer entities; 3. It can process data from lower protocol layer entities; 4. It does not process any data.

[0462] (2) The field duplicate receive window input is used to indicate whether the receive window of the secondary RLC entity needs to process data from other RLC protocol layer entities.

[0463] (3) The field lower layer window input is used to indicate whether the receiving window of the auxiliary RLC entity needs to process data from the lower protocol layer entity.

[0464] In one possible implementation k, the RLC PDU in UM mode needs to include an SN number.

[0465] In one possible embodiment k1, the RLC PDU structure in UM mode can be shown in Figures 29 to 34.

[0466] Beneficial effects: Based on embodiments k and / or k1, in the UM-AM structure, the SN numbers of the data received by the RLC entities of UM and AM can be synchronized, thereby enabling cooperation between the main RLC entity and the auxiliary RLC entity.

[0467] In one possible scenario, the embodiments of this application can implement the following process:

[0468] (1) According to embodiments a to f and their sub-embodiments, two RLC protocol layer entities can be associated, and the primary RLC entity and the secondary RLC entity, as well as their respective radio bearers, can be determined. Additionally, the type of the RLC entity can be determined, for example, UM or AM. In this possible scenario, the primary RLC entity is a UM RLC entity, and the secondary RLC entity is an AM RLC entity, as shown in Figure 44.

[0469] (2) During the receiving phase, the primary RLC entity performs relevant operations according to embodiments g and g1, transmitting the data received from the lower layer to the secondary RLC entity. Simultaneously, because the primary RLC entity is a UM RLC,

[0470] (a) If the data received from the lower layer is SDU fragment data, the primary RLC entity will place it in the receive window and perform RLC header removal and reassembly through the receive window. For the reassembled SDU, the primary RLC entity will deliver it to the upper layer.

[0471] (b) If the data received from the lower layer is complete SDU data, the main RLC entity will directly access the RLC header and submit it to the upper layer.

[0472] (3) During the receiving phase, the auxiliary RLC entity performs relevant operations according to embodiments h, h1, and h2 to receive data from the lower layer from the main RLC entity and / or the lower layer protocol stack entity. Specifically, according to embodiments i to j and their sub-embodiments, the data received from the lower layer protocol stack entity directly enters the receiving window for SDU reassembly; while the data received from the main RLC entity needs to first enter the receiving buffer, and then enter the receiving window for SDU reassembly based on whether the data falls into the receiving window.

[0473] (a) If the SDU fragment is reassembled or the SDU is a complete SDU, the auxiliary RLC entity will remove the RLC header and submit it to the upper layer.

[0474] (b) If a polling signal (i.e., a receive status report request signal) is received from the sender and / or the receiver's timer times out, the auxiliary RLC entity will conditionally trigger the sending section (RLC 2 sender processing in Figure 41) to send a receive status report to the sender. The receive status report contains packets that have been successfully received and / or packets that are yet to be received in the auxiliary RLC entity.

[0475] Beneficial Effects: Based on the embodiments of this application, the primary RLC entity and the secondary RLC entity at the receiving end can meet multiple transmission requirements by receiving data once over the air interface through a cooperative mechanism. Specifically, the primary RLC entity copies and distributes data and / or control information to the secondary RLC entity, which can then configure and maintain its receiving process according to different transmission requirements. Therefore, the embodiments of this application satisfy different transmission requirements with a single air interface data reception, ensuring both low latency and high reliability during data transmission.

[0476] This application also provides the PDCP protocol layer entity architecture and processing procedure for the receiving end.

[0477] In this embodiment of the application, multiple PDCP protocol layer entities can be in the same radio bearer to receive data uploaded by a designated lower protocol layer entity according to the RRC configuration, as shown in Figure 42.

[0478] In one possible embodiment a, the configuration message of the DRB (Data Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more PDCP layer protocol stack entities for the same DRB (e.g., having the same DRB ID).

[0479] In one possible sub-implementation a1, the configuration message of the DRB (e.g., the DRB-ToAddMod field in the RadioBearerConfig message) can be supplemented with a PDCP layer protocol stack entity configuration list (e.g., PDCP-Config-list) to associate the DRB with one or more PDCP layer protocol stack entities and configure them accordingly.

[0480] In one possible sub-implementation a2, the configuration of one or more PDCP layer protocol stack entities associated with the same DRB can be added with the LCH ID (Logical Channel Identifier) ​​of the corresponding lower layer protocol stack entity (e.g., RLC entity) to associate it with the lower layer protocol stack entity (e.g., RLC entity).

[0481] In one possible embodiment b, the configuration message of the SRB (Signaling Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more PDCP layer protocol stack entities for the same SRB (e.g., having the same SRB ID).

[0482] In one possible sub-implementation b1, the configuration message of the SRB (e.g., the SRB-ToAddMod field in the RadioBearerConfig message) can include a PDCP layer protocol stack entity configuration list (e.g., PDCP-Config-list) to associate the SRB with one or more PDCP layer protocol stack entities and configure them accordingly.

[0483] In one possible sub-implementation b2, the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-level protocol stack entity (e.g., RLC entity) can be added to the configuration of one or more PDCP layer protocol stack entities associated with the same SRB to associate them with the RLC entity.

[0484] In one possible scenario, the embodiments of this application can implement the following process:

[0485] (1) According to embodiments a, a1 and a2, a DRB can be associated with multiple PDCP layer protocol stack entities, that is, the multiple PDCP layer protocol stack entities belong to the same DRB. At the same time, the multiple PDCP layer protocol stack entities can be associated with their respective lower layer protocol stack entities (such as RLC entities) through the LCH ID of the lower layer protocol stack entities (e.g., RLC entities).

[0486] In one possible scenario, the embodiments of this application can implement the following process:

[0487] (1) According to embodiments b, b1 and b2, an SRB can be associated with multiple PDCP layer protocol stack entities, that is, the multiple PDCP layer protocol stack entities belong to the same SRB. At the same time, the multiple PDCP layer protocol stack entities can be associated with their respective lower layer protocol stack entities (such as RLC entities) through the LCH ID of the lower layer protocol stack entities (such as RLC entities).

[0488] It should be noted that the lower-level protocol layer entity associated with the aforementioned PDCP entity can also be other lower-level protocol stack entities that have some of the functions of the RLC entity.

[0489] Beneficial effects: Based on the embodiments of this application, PDCP entities that meet different transmission requirements can receive lower-layer data from their respective associated RLC entities in the same radio bearer, thereby enabling the same data stream to be processed at the receiving end with different transmission requirement configurations.

[0490] This application also provides the entity architecture and processing procedures for the receiving end's RRC / SDAP / other upper-layer protocol layers.

[0491] In the embodiments of this application, RRC, SDAP or other protocol layer entities may receive and / or process the same data stream uploaded from multiple lower protocol layer entities in the same radio bearer and / or different radio bearers, as shown in Figure 43, according to the RRC configuration.

[0492] In one possible embodiment a, the configuration message of the DRB (Data Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more lower-layer protocol stack entities (e.g., PDCP entities) for the same DRB (e.g., having the same DRB ID).

[0493] In one possible sub-implementation a1, the configuration message of the DRB (e.g., the DRB-ToAddMod field in the RadioBearerConfig message) can include a list of lower-layer protocol stack entities (e.g., PDCP-Config-list) to associate the DRB with one or more lower-layer protocol stack entities (e.g., PDCP entities) and configure them accordingly.

[0494] In one possible sub-implementation a2, after receiving data from the lower layer, the SDAP layer protocol stack entity can map the same data stream (such as data of the same QFI) uploaded by different lower layer protocol entities in the same radio bearer to different QoS streams, different radio bearers, and / or different PDU sessions according to the RRC configuration.

[0495] In one possible sub-implementation a2-1, after receiving data from the lower layer, the SDAP layer protocol stack entity combines the LCH ID corresponding to the lower layer protocol stack entity (e.g., PDCP entity) to map the same data stream (e.g., data of the same QFI) from different lower layer protocol stack entities to different QoS streams, different radio bearers, and / or different PDU sessions.

[0496] In one possible embodiment b, the configuration message of the SRB (Signaling Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more lower-level protocol stack entities (e.g., PDCP entities) for the same SRB (e.g., having the same SRB ID).

[0497] In one possible sub-implementation b1, the configuration message of the SRB (such as the SRB-ToAddMod field in the RadioBearerConfig message) can add a list of lower-level protocol stack entities (such as PDCP-Config-list) to associate the SRB with one or more lower-level protocol stack entities (e.g., PDCP entities) and configure them accordingly.

[0498] In one possible sub-implementation b2, after receiving data from the lower layer, the RRC layer protocol stack entity can, according to the RRC configuration, map the same data stream (e.g., data of the same QFI) uploaded by different lower layer protocol entities in the same radio bearer to different QoS streams, different radio bearers, different PDU sessions, and / or for processing by the RRC layer.

[0499] In one possible sub-implementation b2-1, after receiving data from the lower layer, the RRC layer protocol stack entity combines the LCH ID corresponding to the lower layer protocol stack entity (e.g., PDCP entity) to map the same data stream (e.g., data of the same QFI) from different lower layer protocol stack entities to different QoS streams, different radio bearers, different PDU sessions, and / or for processing by the RRC layer.

[0500] In one possible embodiment c, after receiving data from the lower layer (e.g., data from PDCP entities of different radio bearers), the SDAP layer protocol stack entity can map the same data stream (e.g., data of the same QFI) uploaded by different lower layer protocol entities in different radio bearers to different QoS streams, different radio bearers, and / or different PDU sessions according to the RRC configuration.

[0501] In one possible sub-implementation c1, after receiving data from the lower layer (e.g., data from PDCP entities of different radio bearers), the SDAP layer protocol stack entity combines the LCH ID corresponding to the lower layer protocol stack entity (e.g., PDCP entity) to map the same data stream (e.g., data of the same QFI) from different lower layer protocol stack entities to different QoS streams, different radio bearers, and / or different PDU sessions.

[0502] In one possible scenario, the embodiments of this application can implement the following process:

[0503] (1) According to embodiments a and a1, an SDAP layer protocol stack entity may be associated with multiple lower layer protocol stack entities (e.g., PDCP entities), and the multiple lower layer protocol stack entities (e.g., PDCP entities) belong to the same DRB.

[0504] (2) According to embodiments a2 and a2-1, after receiving data from the lower layer, the SDAP layer protocol stack entity combines the LCH ID corresponding to the lower layer protocol stack entity (e.g., PDCP entity) to map the data from different lower layer protocol stack entities to different QoS streams, different radio bearers, and / or different PDU sessions.

[0505] In one possible scenario, the embodiments of this application can implement the following process:

[0506] (1) According to embodiments b and b1, an RRC layer protocol stack entity may be associated with multiple lower layer protocol stack entities (such as PDCP entities), and the multiple lower layer protocol stack entities (e.g., PDCP entities) belong to the same SRB.

[0507] (2) According to embodiments b2 and b2-1, after receiving data from the lower layer, the RRC layer protocol stack entity combines the LCH ID corresponding to the lower layer protocol stack entity (such as the PDCP entity) to map the data from different lower layer protocol stack entities to different QoS streams, different radio bearers, different PDU sessions, and / or for RRC layer processing.

[0508] In one possible scenario, the embodiments of this application can implement the following process:

[0509] (1) According to embodiments c and c1, after receiving data from PDCP entities of different radio bearers, the SDAP layer protocol stack entity combines the LCH ID corresponding to the PDCP entity to map data with the same QFI from different PDCP entities to different QoS streams, different radio bearers, and / or different PDU sessions.

[0510] Beneficial effects: Based on the embodiments of this application, RRC, SDAP or other protocol layer entities can divert the same data stream received from different lower-level protocol stack entities to the identifiers corresponding to different data requesters, thereby avoiding confusion between the same data streams from different lower-level protocol stack entities.

[0511] This application also provides an entity architecture and processing procedure for the receiver PDCP and RLC protocol layers based on inter-layer cooperation, as shown in Figure 44.

[0512] In this embodiment, two or more RLC protocol layer entities are associated. One RLC protocol layer entity is the primary RLC entity, and the others are secondary RLC entities. The associated RLC entities may belong to the same radio bearer or different radio bearers.

[0513] In one possible embodiment a, one or more PDCP protocol layer entities may be in the same radio bearer to receive data uploaded by a designated lower protocol layer entity (e.g., an RLC entity) according to the RRC configuration.

[0514] In one possible sub-implementation a1, a PDCP entity can be associated with one or more RLC entities according to the RRC configuration.

[0515] In one possible sub-implementation a2, the configuration message of the DRB (Data Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more PDCP layer protocol stack entities for the same DRB (e.g., having the same DRB ID).

[0516] In one possible sub-implementation a2-1, the configuration message of the DRB (e.g., the DRB-ToAddMod field in the RadioBearerConfig message) can include a PDCP layer protocol stack entity configuration list (e.g., PDCP-Config-list) to associate the DRB with one or more PDCP layer protocol stack entities and configure them accordingly.

[0517] In one possible sub-implementation a2-2, the configuration of one or more PDCP layer protocol stack entities associated with the same DRB can be added with the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-layer protocol stack entity (e.g., RLC entity) to associate it with the lower-layer protocol stack entity (e.g., RLC entity).

[0518] In one possible sub-implementation a3, the configuration message of the SRB (Signaling Radio Bearer) (e.g., RadioBearerConfig message) can configure one or more PDCP layer protocol stack entities for the same SRB (e.g., having the same SRB ID).

[0519] In one possible sub-implementation a3-1, the configuration message of the SRB (e.g., the SRB-ToAddMod field in the RadioBearerConfig message) can include a PDCP layer protocol stack entity configuration list (e.g., PDCP-Config-list) to associate the SRB with one or more PDCP layer protocol stack entities and configure them accordingly.

[0520] In one possible sub-implementation a3-2, the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-level protocol stack entity (e.g., RLC entity) can be added to the configuration of one or more PDCP layer protocol stack entities associated with the same SRB to associate them with the RLC entity.

[0521] In one possible embodiment b, the PDCP protocol layer entity can receive data uploaded from a designated lower-level protocol layer entity (e.g., an RLC entity) of a different radio bearer, according to the RRC configuration.

[0522] In one possible sub-implementation b1, a PDCP entity can be associated with one or more RLC entities according to RRC configuration. The associated RLC entities can belong to the same radio bearer as the PDCP entity, or they can belong to different radio bearers.

[0523] In one possible sub-implementation b2, the configuration of the PDCP layer protocol stack entity can include the LCH ID (Logical Channel Identifier) ​​of the corresponding lower-level protocol stack entity (such as the RLC entity) to associate it with the lower-level protocol stack entity (e.g., the RLC entity).

[0524] In one possible embodiment c, the primary RLC entity (RLC 1 in FIG44) can send control information and / or data from the lower layer to one or more associated PDCP entities (PDCP 1 and PDCP 2 in FIG44) according to the RRC configuration.

[0525] In one possible sub-implementation c1, the data transmitted from the lower layer may be a complete RLC SDU and / or an RLC SDU fragment.

[0526] In one possible sub-implementation c2, the control information sent may be the SN (sequence number) and / or SO (segment offset) number of the complete RLC SDU and / or RLC SDU segment.

[0527] In one possible sub-implementation c3, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive Config to upper layer) to indicate what the main RLC entity sends to the upper-layer protocol stack entity (e.g., PDCP entity). This field may contain one or more of the following:

[0528] (1) Data1 from RLC: The main RLC entity receives and / or reassembles complete RLC SDU data from the lower protocol layer entity.

[0529] (2) Data2 from RLC: RLC SDU fragments received by the main RLC entity from the lower protocol layer entity.

[0530] (3) SN1 from RLC: The main RLC entity receives and / or reassembles the SN (sequence number) information corresponding to the complete RLC SDU data from the lower protocol layer entity.

[0531] (4)SN2 from RLC: The SN (Sequence Number) information corresponding to the RLC SDU fragment received by the main RLC entity from the lower protocol layer entity.

[0532] (5) SO from RLC: SO (fragment offset) information corresponding to the RLC SDU fragment received by the main RLC entity from the lower protocol layer entity.

[0533] In one possible sub-implementation c4, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as duplicate Receive to upper layer) added to indicate whether the main RLC entity needs to send control information and / or data to the upper-layer protocol stack entity (e.g., PDCP entity).

[0534] In one possible embodiment d, the PDCP entity (PDCP 2 in Figure 50) can receive control information and / or data from the associated primary RLC entity (RLC 1 in Figure 44) according to the RRC configuration.

[0535] In one possible sub-implementation d1, the data received from the lower layer is a complete RLC SDU and / or an RLC SDU fragment.

[0536] In one possible sub-implementation d2, the received control information may be the SN and / or SO number of the complete RLC SDU and / or RLC SDU segment.

[0537] In one possible sub-implementation d3, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive Config to upper layer) to indicate what the PDCP entity receives from the main RLC entity. This field may contain one or more of the following:

[0538] (1) Data1 from RLC: The main RLC entity receives and / or reassembles complete RLC SDU data from the lower protocol layer entity.

[0539] (2) Data2 from RLC: RLC SDU fragments received by the main RLC entity from the lower protocol layer entity.

[0540] (3) SN1 from RLC: The main RLC entity receives and / or reassembles the SN (sequence number) information corresponding to the complete RLC SDU data from the lower protocol layer entity.

[0541] (4)SN2 from RLC: The SN (Sequence Number) information corresponding to the RLC SDU fragment received by the main RLC entity from the lower protocol layer entity.

[0542] (5) SO from RLC: SO (fragment offset) information corresponding to the RLC SDU fragment received by the main RLC entity from the lower protocol layer entity.

[0543] In one possible sub-implementation d4, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as duplicate Receive to upper layer) added to indicate whether the PDCP entity needs to receive control information and / or data from the main RLC entity.

[0544] In one possible sub-implementation d5, the PDCP entity can be configured according to RRC, and its receive window can process data (e.g., complete RLC SDUs, etc.) from the primary RLC protocol layer entity and / or the secondary RLC protocol layer entity.

[0545] In one possible sub-implementation d5-1, the PDCP configuration message (e.g., the PDCP-Config message) may have one or more of the following fields added to indicate whether the receive window of the PDCP entity can process data from the primary RLC entity and / or data from the secondary RLC entity.

[0546] (1) The field receive window input for PDCP (e.g., 2 bits) is used to indicate the processing content of the receive window of the PDCP entity, which may involve one or more of the following: 1. Data from the primary RLC entity and data from the secondary RLC entity can be processed; 2. Data from the primary RLC entity can be processed; 3. Data from the secondary RLC entity can be processed; 4. No data is processed.

[0547] (2) The field "duplicate receive window input for PDCP" is used to indicate whether the receive window of the PDCP entity needs to process data from the main RLC entity.

[0548] (3) The field lower layer window input for PDCP is used to indicate whether the receiving window of the PDCP entity needs to process data from the auxiliary RLC entity.

[0549] In one possible embodiment e, the PDCP entity (PDCP 2 in FIG44) can send control information and / or data from the lower layer to the associated auxiliary RLC entity (RLC 2 in FIG44) according to the RRC configuration.

[0550] In one possible sub-implementation e1, the data transmitted from the lower layer is a complete RLC SDU and / or an RLC SDU fragment.

[0551] In one possible sub-implementation e2, the control information sent may be the SN and / or SO number of the complete RLC SDU and / or RLC SDU segment.

[0552] In one possible sub-implementation e3, the control information and / or data from the lower layer sent by the PDCP entity to the associated secondary RLC entity comes from the primary RLC entity.

[0553] In one possible sub-implementation e4, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive Config to lower layer) to indicate what the PDCP entity sends to the secondary RLC entity. This field may contain one or more of the following:

[0554] (1) Data1 to RLC: The PDCP entity receives and / or reassembles complete RLC SDU data from the lower protocol layer entity.

[0555] (2) Data2 to RLC: RLC SDU fragments received by the PDCP entity from the lower protocol layer entity.

[0556] (3) SN1 to RLC: The PDCP entity receives and / or reassembles the SN (Sequence Number) information corresponding to the complete RLC SDU data from the lower protocol layer entity.

[0557] (4) SN2 to RLC: The SN (Sequence Number) information corresponding to the RLC SDU fragment received by the PDCP entity from the lower protocol layer entity.

[0558] (5) SO to RLC: SO (fragment offset) information corresponding to the RLC SDU fragment received by the PDCP entity from the lower protocol layer entity.

[0559] In one possible sub-implementation e5, the RLC configuration message (e.g., RLC-BearerConfig) may have fields (such as duplicate Receive to lower layer) added to indicate whether the PDCP entity needs to send control information and / or data to the auxiliary RLC entity.

[0560] In one possible embodiment f, the auxiliary RLC entity (RLC 2 in Figure 44, or RLC 2 in Figures 45 and 46) can receive control information and / or data from the associated PDCP entity (PDCP 2 in Figure 44) according to the RRC configuration.

[0561] In one possible sub-implementation f1, the data received from the lower layer is a complete RLC SDU and / or an RLC SDU fragment.

[0562] In one possible sub-implementation f2, the received control information may be the SN and / or SO number of the complete RLC SDU and / or RLC SDU segment.

[0563] In one possible sub-implementation f3, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive Config to lower layer) to indicate what the secondary RLC entity receives from the upper-layer protocol stack entity (e.g., PDCP entity). This field may contain one or more of the following:

[0564] (1) Data1 to RLC: The PDCP entity receives and / or reassembles complete RLC SDU data from the lower protocol layer entity.

[0565] (2) Data2 to RLC: RLC SDU fragments received by the PDCP entity from the lower protocol layer entity.

[0566] (3) SN1 to RLC: The PDCP entity receives and / or reassembles the SN (Sequence Number) information corresponding to the complete RLC SDU data from the lower protocol layer entity.

[0567] (4) SN2 to RLC: The SN (Sequence Number) information corresponding to the RLC SDU fragment received by the PDCP entity from the lower protocol layer entity.

[0568] (5) SO to RLC: SO (fragment offset) information corresponding to the RLC SDU fragment received by the PDCP entity from the lower protocol layer entity.

[0569] In one possible sub-implementation f4, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., duplicate Receive to lower layer) to indicate whether the secondary RLC entity needs to receive control information and / or data from the upper-layer protocol stack entity (such as a PDCP entity).

[0570] In one possible sub-implementation f5, the auxiliary RLC entity is configured according to RRC, and its receive window can be updated and / or reassembled based on data received from the upper-layer PDCP entity (e.g., complete RLC SDUs and / or RLC SDU fragments) and / or control information (e.g., the SN and / or SO numbers of complete RLC SDUs and / or RLC SDU fragments).

[0571] In one possible sub-implementation f6, the auxiliary RLC entity can be configured according to RRC, and its receiving window can process control information and / or data (e.g., complete SDU data, SDU fragment data, SN information, SO information, etc.) from upper-layer protocol layer entities (e.g., PDCP entities) and / or control information and / or data from lower-layer protocol layer entities.

[0572] In one possible sub-implementation f6-1, the RLC configuration message (e.g., RLC-BearerConfig) may have one or more of the following fields added to indicate whether the receive window of the auxiliary RLC entity can process control information and / or data from the upper-layer PDCP entity and / or from the lower-layer protocol layer entity.

[0573] (1) The field receive window input for RLC (e.g., 2 bits) is used to indicate the processing content of the receive window of the auxiliary RLC entity, which may involve one or more of the following: 1. It can process control information and / or data from the upper PDCP protocol layer entity and from the lower protocol layer entity; 2. It can process control information and / or data from the upper PDCP protocol layer entity; 3. It can process control information and / or data from the lower protocol layer entity; 4. It does not process any control information and / or data.

[0574] (2) The field "duplicate receive window input for RLC" is used to indicate whether the receive window of the secondary RLC entity needs to process control information and / or data from the upper PDCP protocol layer entity.

[0575] (3) The field "lower layer window input for RLC" is used to indicate whether the receiving window of the auxiliary RLC entity needs to process control information and / or data from the lower protocol layer entity.

[0576] In one possible embodiment f7, when the auxiliary RLC entity completes the reassembly of the RLC SDU fragment and / or receives the complete RLC SDU data, the auxiliary RLC entity can submit the reassembled and / or received complete RLC SDU data to the upper-layer protocol layer entity (e.g., the PDCP layer).

[0577] In one possible sub-implementation f7-1, the auxiliary RLC entity can submit complete RLC SDU data to the upper layer PDCP entity, in addition to the complete RLC SDU data already received by the upper layer PDCP entity.

[0578] In one possible sub-implementation f7-1-1, the PDCP entity can indicate to the auxiliary RLC entity, in one or more of the following ways, the complete RLC SDU data that the PDCP entity has received:

[0579] (1) Indicate by sending the SN number to the auxiliary RLC entity through the PDCP entity.

[0580] (2) Instructions are given by sending RLC SDU fragments to the auxiliary RLC entity via the PDCP entity.

[0581] (3) Send a complete RLC SDU to the auxiliary RLC entity via the PDCP entity to indicate.

[0582] In one possible embodiment g, the primary RLC entity is the RLC UM receiving entity, and the secondary RLC entity is the RLC AM entity, as shown in Figure 45.

[0583] In one possible embodiment h, the main RLC entity is an RLC AM entity, and the auxiliary RLC entity is an RLC AM entity, as shown in Figure 46.

[0584] In one possible sub-implementation h1, the configurations of the main RLC entity and the auxiliary RLC entity can be different.

[0585] In one possible embodiment i, the RLC protocol layer entity can perform different processing procedures based on whether the data (e.g., complete RLC SDUs and / or RLC SDU fragments) and / or control information (e.g., the SN and / or SO numbers of complete RLC SDUs and / or RLC SDU fragments) originates from an upper-layer protocol layer entity (e.g., a PDCP entity) or directly from a lower-layer protocol layer entity, according to the RRC configuration. The RLC protocol layer entity can be a secondary RLC entity.

[0586] In one possible sub-implementation i1, data and / or control information from an upper protocol layer entity (e.g., a PDCP entity) needs to enter an additional receive buffer compared to data directly from a lower protocol layer entity, as shown in Figure 47.

[0587] In one possible sub-implementation i1-1, the RLC configuration message (e.g., RLC-BearerConfig) may have an added field (e.g., buffer for duplicate Receive from upper layer) to indicate whether the secondary RLC entity needs to put data and / or control information from the upper protocol layer entity (e.g., PDCP entity) into an additional receive buffer.

[0588] In one possible sub-implementation i1-2, the receiving process in FIG47 can specifically be the process shown in FIG48, that is, the receiving process consists of receiving window, removing RLC packet header, SDU reassembly and other processes.

[0589] In one possible sub-implementation i1-2-1, if the data and / or control information in the receive buffer in FIG48 falls outside the receive window, the data and / or control information in the receive buffer will not enter the receive window temporarily until the data and / or control information falls inside the receive window.

[0590] It should be noted that the embodiments in this application may include one or more of the above embodiments a, b, f, g, h, i, j, k and their sub-embodiments.

[0591] In one possible scenario, the embodiments of this application can implement the following process:

[0592] (1) According to embodiments b and g and their sub-embodiments, a PDCP entity (PDCP 2 in Figure 44) can be associated with RLC entities in different radio bearers (RLC 1 in Figure 44) and RLC entities in the same radio bearer (RLC 2 in Figure 44). Another PDCP entity (PDCP 1 in Figure 44) can be associated with RLC entities in the same radio bearer (RLC 1 in Figure 44). That is, PDCP 1 and RLC 1 in Figure 44 are in the same radio bearer, and PDCP 2 and RLC 2 are in the same radio bearer. Among them, RLC 1 is the primary RLC entity and is also in UM mode; RLC 2 is the secondary RLC entity and is also in AM mode.

[0593] (2) According to embodiment c and its sub-embodiments, the main RLC entity sends the same complete RLC SDU and corresponding SN number to PDCP 2 at the same time as sending the complete RLC SDU to PDCP 1.

[0594] (3) According to Embodiments d and e and their sub-embodiments, PDCP 2 receives complete RLC SDU data from the primary RLC entity and performs PDCP processing, while sending the SN number received from the primary RLC to the secondary RLC entity (i.e., RLC 2).

[0595] (4) According to Embodiments f and i and their sub-embodiments, the auxiliary RLC entity receives the SN number from PDCP 2 and puts the received SN number into the receive buffer. When the SN number in the receive buffer falls into the receive window, the auxiliary RLC entity updates the parameters of the receive window (e.g., status variables and / or timers, etc.) according to the SN number. Since the auxiliary RLC entity is in AM mode, if it receives a polling signal (i.e., a receive status report request signal) from the transmitter and / or the receiver's timer times out, the auxiliary RLC entity will conditionally trigger the transmitting part (RLC 2 transmitter processing in Figure 45) to send a receive status report to the transmitter. The receive status report indicates the packets that have been successfully received and / or the packets that are yet to be received in the auxiliary RLC entity. Then, the transmitter will retransmit the corresponding data packets according to the information of the packets yet to be received in the receive status report, and the auxiliary RLC entity needs to receive these data packets and update the parameters of the receive window (e.g., status variables and / or timers, etc.). If the secondary RLC completes the reception and / or reassembly of RLC SDUs other than those that have been fully received as indicated by the PDCP, the secondary RLC entity submits these new, complete RLC SDU data to the upper-layer PDCP entity.

[0596] In one possible scenario, the embodiments of this application can implement the following process:

[0597] (1) According to embodiments a and g and their sub-embodiments, a PDCP entity (PDCP in Figure 49) can be associated with two RLC entities (RLC 1 and RLC 2 in Figure 49) in the same radio bearer. Among them, RLC 1 is the primary RLC entity and is also in UM mode; RLC 2 is the secondary RLC entity and is also in AM mode.

[0598] (2) According to embodiment c and its sub-embodiments, the main RLC entity will send the complete RLC SDU and the corresponding SN number to the PDCP entity.

[0599] (3) According to Embodiments d and e and their sub-embodiments, the PDCP entity receives complete RLC SDU data from the main RLC entity and performs PDCP processing, while sending the SN number received from the main RLC to the auxiliary RLC entity (i.e. RLC 2).

[0600] (4) According to embodiments f and i and their sub-embodiments, the auxiliary RLC entity receives the SN number from the PDCP entity and puts the received SN number into the receive buffer. When the SN number in the receive buffer falls into the receive window, the auxiliary RLC entity updates the parameters of the receive window (e.g., status variables and / or timers, etc.) according to the SN number. Since the auxiliary RLC entity is in AM mode, if it receives a polling signal (i.e., a receive status report request signal) from the transmitter and / or the receiver's timer times out, the auxiliary RLC entity will conditionally trigger the transmitting part (RLC 2 transmitter processing in Figure 45) to send a receive status report to the transmitter. The receive status report indicates the packets that have been successfully received and / or the packets that are yet to be received in the auxiliary RLC entity. Then, the transmitter will retransmit the corresponding data packets according to the information of the packets yet to be received in the receive status report, and the auxiliary RLC entity needs to receive these data packets and update the parameters of the receive window (e.g., status variables and / or timers, etc.). If the secondary RLC completes the reception and / or reassembly of RLC SDUs other than those that have been fully received as indicated by the PDCP, the secondary RLC entity submits these new, complete RLC SDU data to the upper-layer PDCP entity.

[0601] Beneficial Effects: Based on the embodiments of this application, the primary RLC entity, secondary RLC entity, and / or PDCP entity at the receiving end can meet multiple transmission requirements by receiving data once over the air interface through a cooperative mechanism. Specifically, the primary RLC entity distributes data and / or control information to the PDCP entity, which then sends relevant information to the secondary RLC entity, and / or the primary RLC entity distributes data and / or control information to the secondary RLC entity. Thus, the secondary RLC entity can configure and maintain its receiving process according to different transmission requirements. Therefore, the embodiments of this application meet different transmission requirements with a single data reception over the air interface, ensuring both low latency and high reliability during data transmission.

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

[0603] For example, Figure 19 is a schematic diagram of a communication device provided in an embodiment of this application, wherein the communication device includes a transceiver module 1910 and a processing module 1920. The transceiver module 1910, also known as a transceiver unit, is used to implement the transceiver function, and may be a transceiver circuit, transceiver, transceiver device, or communication interface.

[0604] Taking the communication device as an example, which is a network device (which may be a chip of the network device, a module of the network device, or an internal device of the network device) in the above method embodiment:

[0605] In this embodiment of the application, the processing module 5020 is used to determine the first paging message.

[0606] In this embodiment of the application, the transceiver module 5010 is used to send a first paging message to the terminal device.

[0607] The first paging message is used to configure data collection configuration information to the terminal device, which is in a Radio Resource Control (RRC) idle state or inactive state.

[0608] In one possible implementation of this application embodiment, the first paging message includes one or more of the following: paging reason, task type, and capability information required by the terminal device.

[0609] In one possible implementation of this application embodiment, the terminal device is in the RRC inactive state, and the first paging message is an access network paging message.

[0610] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0611] Receive a connection restoration request from the terminal device;

[0612] Send a connection release message to the terminal device; wherein the connection release message includes the configuration information for the data acquisition.

[0613] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0614] Receive a connection restoration request from the terminal device;

[0615] A connection restoration message is sent to the terminal device; wherein the connection restoration message includes the configuration information for the data acquisition.

[0616] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0617] Receive a connection restoration completion message from the terminal device, the connection restoration completion message including one or more of the following: an indication that the configuration information for data acquisition was successfully configured, or a data task identifier.

[0618] In one possible implementation of this application embodiment, the terminal device is in the RRC inactive state, and the first paging message is a broadcast message.

[0619] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0620] Receive a connection restoration request from the terminal device;

[0621] Obtain the context information of the terminal device;

[0622] A connection restoration message is sent to the terminal device, the connection restoration message including the configuration information of the data collection.

[0623] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0624] Receive a connection restoration completion message from the terminal device, the connection restoration completion message including one or more of the following: an identifier of the data task, or a configuration success indication.

[0625] In one possible implementation of this application embodiment, the terminal device is in the RRC idle state, and the first paging message is a core network paging message.

[0626] In one possible implementation of this application embodiment, before sending the first paging message to the terminal device, the transceiver module is further configured to:

[0627] Send a paging request message to the access and mobility management function network element. The paging request message includes one or more of the following: the paging identifier ID information of the terminal device, the paging reason, the task type, or the capability information required by the terminal device.

[0628] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0629] Receive a second paging message from the access and mobility management function network element, wherein the second paging message is determined based on the paging request message;

[0630] Sending the first paging message to the terminal device includes: sending the first paging message to the terminal device according to the second paging message.

[0631] In one possible implementation of this application embodiment, before sending the first paging message to the terminal device, the transceiver module is further configured to:

[0632] Receive data collection instructions from network function elements, wherein the data collection instructions include one or more of the following: data task identifier, task type, task content, capability information required by the terminal device, location range information, paging identifier ID of the terminal device, or a list of available terminal devices;

[0633] Sending the first paging message to the terminal device includes: sending the first paging message to the terminal device according to the data acquisition instruction.

[0634] In one possible implementation of this application embodiment, the terminal device is in the RRC idle state, and the first paging message is a broadcast message.

[0635] In one possible implementation of this application embodiment, after the terminal device establishes an RRC connection state based on the first paging message, the transceiver module is further configured to:

[0636] The configuration information for data collection is sent to the terminal device.

[0637] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0638] Receive a configuration completion message corresponding to the configuration information of the data collection from the terminal device. The configuration completion message includes one or more of the following: data task identifier, configuration success indication, data reporting request, session establishment request, or data collection.

[0639] In one possible implementation of this application embodiment, the data reporting request includes one or more of the following: the duration of the collected data, or the amount of collected data;

[0640] The session establishment request includes one or more of the following: transmission type, target node ID for data transmission, or data task identifier.

[0641] In one possible implementation of this application embodiment, after the terminal device establishes an RRC connection state based on the first paging message, the transceiver module is further configured to:

[0642] A connection release message is sent to the terminal device, the connection release message including the configuration information of the data collection.

[0643] In one possible implementation of this application embodiment, the configuration information for data collection includes one or more of the following: data task identifier, data collection reporting trigger condition, data collection reporting method, data volume threshold, duration threshold, or reporting time.

[0644] In one possible implementation of this application embodiment, the data collection reporting triggering conditions include one or more of the following: the amount of data collected reaches the data amount threshold, the collection duration reaches the duration threshold, or the reporting time is reached.

[0645] The data collection and reporting methods include one or more of the following: control plane transmission, user plane transmission, or data plane transmission.

[0646] In one possible implementation of this application, the downlink control information corresponding to the first paging message includes one or more of the following: terminal device level information, terminal device type information, or paging reason.

[0647] In one possible implementation of this application embodiment, the level of the terminal device includes one or more of the following: the capability level of the terminal device, or the power consumption level of the terminal device;

[0648] The type of terminal device includes one or more of the following: sensor, low-power device, other terminal device types besides the sensor and the low-power device, or all terminal device types;

[0649] The paging reason includes one or more of the following: unicast paging, or broadcast paging.

[0650] In one possible implementation of this application embodiment, the level information of the terminal device includes one or more of the following: a specified terminal device level, an upper limit of the terminal device level, or a lower limit of the terminal device level;

[0651] The terminal device type information includes one or more of the following: a specified terminal device type, or a terminal device type other than the specified terminal device type.

[0652] Optionally, the communication device may further include a storage module 5030, which can be used to store instructions and / or data, and the processing module 5020 can read the instructions and / or data in the storage module 5030.

[0653] In this embodiment, the network device is presented as an integrated functional module. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device can take the form of the communication device 1200 shown in FIG. 4.

[0654] For example, the processor 1201 in the communication device 1200 shown in FIG12 can call the computer execution instructions stored in the memory 1203 to make the communication device 1200 execute the communication method in the above method embodiment.

[0655] Specifically, the functions / implementation processes of the transceiver module 5010 and processing module 5020 in Figure 50 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203. Alternatively, the functions / implementation processes of the processing module 5020 in Figure 50 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203, and the functions / implementation processes of the transceiver module 5010 in Figure 50 can be implemented by the communication interface 1204 in the communication device 1200 shown in Figure 12.

[0656] Alternatively, taking the communication device as an example, which is the terminal device in the above method embodiment (which may be a chip of the terminal device, a module of the terminal device, or an internal device of the terminal device):

[0657] In this embodiment of the application, the transceiver module 5010 is used to receive a first paging message from a network device, wherein the terminal device is in a Radio Resource Control (RRC) idle state or an inactive state.

[0658] In this embodiment of the application, the processing module 5020 is used to obtain the configuration information for data collection based on the first paging message.

[0659] In one possible implementation of this application embodiment, the first paging message includes one or more of the following: paging reason, task type, and capability information required by the terminal device.

[0660] In one possible implementation of this application embodiment, the terminal device is in the RRC inactive state, and the first paging message is an access network paging message.

[0661] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0662] Send a connection restoration request to the network device;

[0663] The step of obtaining the configuration information for data collection based on the first paging message includes:

[0664] Receive a connection release message from the network device and obtain the configuration information for data collection included in the connection release message.

[0665] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0666] Send a connection restoration request to the network device;

[0667] The step of obtaining the configuration information for data collection based on the first paging message includes:

[0668] Receive a connection restoration message from the network device and obtain the configuration information for the data collection included in the connection restoration message.

[0669] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0670] Send a connection restoration completion message to the network device. The connection restoration completion message includes one or more of the following: an indication that the configuration information for data acquisition was successfully configured, or a data task identifier.

[0671] In one possible implementation of this application embodiment, the terminal device is in the RRC inactive state, and the first paging message is a broadcast message.

[0672] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0673] Send a connection restoration request to the network device;

[0674] The step of obtaining the configuration information for data collection based on the first paging message includes:

[0675] Receive a connection restoration message from the network device and obtain the configuration information for the data collection included in the connection restoration message.

[0676] In one possible implementation of this application embodiment, the transceiver module 5010 is further configured to:

[0677] Send a connection restoration completion message to the network device. The connection restoration completion message includes one or more of the following: an identifier of the data task, or a configuration success indication.

[0678] In one possible implementation of this application embodiment, the terminal device is in the RRC idle state, and the first paging message is a core network paging message.

[0679] In one possible implementation of this application embodiment, the first paging message is determined by the network device based on a second paging message from the access and mobility management function network element, and the second paging message is determined by the access and mobility management function network element based on the paging request message of the network device.

[0680] In one possible implementation of this application embodiment, the first paging message is determined by the network device based on a data acquisition instruction from a network function element. The data acquisition instruction includes one or more of the following: data task identifier, task type, task content, capability information required by the terminal device, location range information, paging identifier ID of the terminal device, or a list of available terminal devices.

[0681] In one possible implementation of this application embodiment, the terminal device is in the RRC idle state, and the first paging message is a broadcast message.

[0682] In one possible implementation of this application embodiment, the step of obtaining the data collection configuration information based on the first paging message includes:

[0683] Establish an RRC connection state based on the first paging message and receive the configuration information for data collection from the network device.

[0684] In one possible implementation of this application embodiment, the transceiver module is further configured to:

[0685] Send a configuration completion message corresponding to the configuration information for data collection to the network device. The configuration completion message includes one or more of the following: data task identifier, configuration success indication, data reporting request, session establishment request, or data collection.

[0686] In one possible implementation of this application embodiment, the data reporting request includes one or more of the following: the duration of the collected data, or the amount of collected data;

[0687] The session establishment request includes one or more of the following: transmission type, target node ID for data transmission, or data task identifier.

[0688] In one possible implementation of this application embodiment, the step of obtaining the data collection configuration information based on the first paging message includes:

[0689] An RRC connection state is established based on the first paging message, and the configuration information for the data acquisition is received from the connection release message from the network device.

[0690] In one possible implementation of this application embodiment, the configuration information for data collection includes one or more of the following: data task identifier, data collection reporting trigger condition, data collection reporting method, data volume threshold, duration threshold, or reporting time.

[0691] In one possible implementation of this application embodiment, the data collection reporting triggering condition includes one or more of the following: the amount of data collected reaches the data amount threshold, the collection duration reaches the duration threshold, or the reporting time is reached.

[0692] The data collection and reporting methods include one or more of the following: control plane transmission, user plane transmission, or data plane transmission.

[0693] In one possible implementation of this application, the downlink control information corresponding to the first paging message includes one or more of the following: the level of the terminal device, the type of the terminal device, or the paging reason.

[0694] In one possible implementation of this application embodiment, the level of the terminal device includes one or more of the following: the capability level of the terminal device, or the power consumption level of the terminal device;

[0695] The type of terminal device includes one or more of the following: sensor, low-power device, other terminal device types besides the sensor and the low-power device, or all terminal device types;

[0696] The paging reason includes one or more of the following: unicast paging, or broadcast paging.

[0697] In one possible implementation of this application embodiment, the level information of the terminal device includes one or more of the following: a specified terminal device level, an upper limit of the terminal device level, or a lower limit of the terminal device level;

[0698] The terminal device type information includes one or more of the following: a specified terminal device type, or a terminal device type other than the specified terminal device type.

[0699] Optionally, the communication device may further include a storage module 5030, which can be used to store instructions and / or data, and the processing module 5020 can read the instructions and / or data in the storage module 5030.

[0700] In this embodiment, the terminal device is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device can take the form of the communication device 1200 shown in FIG. 12.

[0701] For example, the processor 1201 in the communication device 1200 shown in FIG12 can call the computer execution instructions stored in the memory 1203 to make the communication device 1200 execute the sensing method in the above method embodiment.

[0702] Specifically, the functions / implementation processes of the transceiver module 5010 and processing module 5020 in Figure 50 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203. Alternatively, the functions / implementation processes of the processing module 5020 in Figure 50 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203, and the functions / implementation processes of the transceiver module 5010 in Figure 50 can be implemented by the communication interface 1204 in the communication device 1200 shown in Figure 12.

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

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, Applied to network devices, including: A first paging message is sent to the terminal device. The first paging message is used to configure the terminal device with configuration information for data collection, wherein the terminal device is in the Radio Resource Control (RRC) idle state or inactive state.

2. The method according to claim 1, characterized in that, The first paging message includes one or more of the following: paging reason, task type, and capability information required by the terminal device.

3. The method according to claim 1 or 2, characterized in that, The terminal device is in the RRC inactive state, and the first paging message is an access network paging message.

4. The method according to claim 3, characterized in that, The method further includes: Receive a connection restoration request from the terminal device; Send a connection release message to the terminal device; wherein the connection release message includes the configuration information for the data acquisition.

5. The method according to claim 3, characterized in that, The method further includes: Receive a connection restoration request from the terminal device; A connection restoration message is sent to the terminal device; wherein the connection restoration message includes the configuration information for the data acquisition.

6. The method according to claim 5, characterized in that, The method further includes: Receive a connection restoration completion message from the terminal device, the connection restoration completion message including one or more of the following: an indication that the configuration information for data acquisition was successfully configured, or a data task identifier.

7. The method according to claim 1 or 2, characterized in that, The terminal device is in the RRC inactive state, and the first paging message is a broadcast message.

8. The method according to claim 7, characterized in that, The method further includes: Receive a connection restoration request from the terminal device; Obtain the context information of the terminal device; A connection restoration message is sent to the terminal device, the connection restoration message including the configuration information of the data collection.

9. The method according to claim 8, characterized in that, The method further includes: Receive a connection restoration completion message from the terminal device, the connection restoration completion message including one or more of the following: an identifier of the data task, or a configuration success indication.

10. The method according to claim 1 or 2, characterized in that, The terminal device is in the RRC idle state, and the first paging message is a core network paging message.

11. The method according to claim 10, characterized in that, Before sending the first paging message to the terminal device, the method further includes: Send a paging request message to the access and mobility management function network element. The paging request message includes one or more of the following: the paging identifier ID information of the terminal device, the paging reason, the task type, or the capability information required by the terminal device.

12. The method according to claim 11, characterized in that, The method further includes: Receive a second paging message from the access and mobility management function network element, wherein the second paging message is determined based on the paging request message; Sending the first paging message to the terminal device includes: sending the first paging message to the terminal device according to the second paging message.

13. The method according to claim 10, characterized in that, Before sending the first paging message to the terminal device, the method further includes: Receive data collection instructions from network function elements, wherein the data collection instructions include one or more of the following: data task identifier, task type, task content, capability information required by the terminal device, location range information, paging identifier ID of the terminal device, or a list of available terminal devices; Sending the first paging message to the terminal device includes: sending the first paging message to the terminal device according to the data acquisition instruction.

14. The method according to claim 1 or 2, characterized in that, The terminal device is in the RRC idle state, and the first paging message is a broadcast message.

15. The method according to any one of claims 10 to 14, characterized in that, After the terminal device establishes an RRC connection state based on the first paging message, the method further includes: The configuration information for data collection is sent to the terminal device.

16. The method according to claim 15, characterized in that, The method further includes: Receive a configuration completion message corresponding to the configuration information of the data collection from the terminal device. The configuration completion message includes one or more of the following: data task identifier, configuration success indication, data reporting request, session establishment request, or data collection.

17. The method according to claim 16, characterized in that, The data reporting request includes one or more of the following: the duration of the collected data, or the amount of collected data; The session establishment request includes one or more of the following: transmission type, target node ID for data transmission, or data task identifier.

18. The method according to any one of claims 10 to 14, characterized in that, After the terminal device establishes an RRC connection state based on the first paging message, the method further includes: A connection release message is sent to the terminal device, the connection release message including the configuration information of the data collection.

19. The method according to any one of claims 1 to 18, characterized in that, The configuration information for data collection includes one or more of the following: data task identifier, data collection reporting trigger condition, data collection reporting method, data volume threshold, duration threshold, or reporting time.

20. The method according to claim 19, characterized in that, The data collection and reporting trigger conditions include one or more of the following: the amount of data collected reaches the data amount threshold, the collection duration reaches the duration threshold, or the reporting time is reached. The data collection and reporting methods include one or more of the following: control plane transmission, user plane transmission, or data plane transmission.

21. The method according to any one of claims 1 to 20, characterized in that, The downlink control information corresponding to the first paging message includes one or more of the following: terminal device level information, terminal device type information, or paging reason.

22. The method according to claim 21, characterized in that, The level of the terminal device includes one or more of the following: the capability level of the terminal device, or the power consumption level of the terminal device; The type of terminal device includes one or more of the following: sensor, low-power device, other terminal device types besides the sensor and the low-power device, or all terminal device types; The paging reason includes one or more of the following: unicast paging, or broadcast paging.

23. The method according to claim 22, characterized in that, The terminal device's level information includes one or more of the following: a specified terminal device level, the upper limit of the terminal device's level, or the lower limit of the terminal device's level; The terminal device type information includes one or more of the following: a specified terminal device type, or a terminal device type other than the specified terminal device type.

24. A communication method, characterized in that, Applied to terminal devices, including: Receive a first paging message from a network device, wherein the terminal device is in a Radio Resource Control (RRC) idle state or an inactive state; The configuration information for data collection is obtained based on the first paging message.

25. The method according to claim 24, characterized in that, The first paging message includes one or more of the following: paging reason, task type, and capability information required by the terminal device.

26. The method according to claim 24 or 25, characterized in that, The terminal device is in the RRC inactive state, and the first paging message is an access network paging message.

27. The method according to claim 26, characterized in that, The method further includes: Send a connection restoration request to the network device; The step of obtaining the configuration information for data collection based on the first paging message includes: Receive a connection release message from the network device and obtain the configuration information for data collection included in the connection release message.

28. The method according to claim 26, characterized in that, The method further includes: Send a connection restoration request to the network device; The step of obtaining the configuration information for data collection based on the first paging message includes: Receive a connection restoration message from the network device and obtain the configuration information for the data collection included in the connection restoration message.

29. The method according to claim 28, characterized in that, The method further includes: Send a connection restoration completion message to the network device. The connection restoration completion message includes one or more of the following: an indication that the configuration information for data acquisition was successfully configured, or a data task identifier.

30. The method according to claim 24 or 25, characterized in that, The terminal device is in the RRC inactive state, and the first paging message is a broadcast message.

31. The method according to claim 30, characterized in that, The method further includes: Send a connection restoration request to the network device; The step of obtaining the configuration information for data collection based on the first paging message includes: Receive a connection restoration message from the network device and obtain the configuration information for the data collection included in the connection restoration message.

32. The method according to claim 31, characterized in that, The method further includes: Send a connection restoration completion message to the network device. The connection restoration completion message includes one or more of the following: an identifier of the data task, or a configuration success indication.

33. The method according to claim 24 or 25, characterized in that, The terminal device is in the RRC idle state, and the first paging message is a core network paging message.

34. The method according to claim 33, characterized in that, The first paging message is determined by the network device based on the second paging message from the access and mobility management function network element, and the second paging message is determined by the access and mobility management function network element based on the paging request message from the network device.

35. The method according to claim 33, characterized in that, The first paging message is determined by the network device based on the data acquisition instruction from the network function element. The data acquisition instruction includes one or more of the following: data task identifier, task type, task content, capability information required by the terminal device, location range information, paging identifier ID of the terminal device, or a list of available terminal devices.

36. The method according to claim 24 or 25, characterized in that, The terminal device is in the RRC idle state, and the first paging message is a broadcast message.

37. The method according to any one of claims 33 to 36, characterized in that, The step of obtaining the configuration information for data collection based on the first paging message includes: Establish an RRC connection state based on the first paging message and receive the configuration information for data collection from the network device.

38. The method according to claim 37, characterized in that, The method further includes: Send a configuration completion message corresponding to the configuration information for data collection to the network device. The configuration completion message includes one or more of the following: data task identifier, configuration success indication, data reporting request, session establishment request, or data collection.

39. The method according to claim 38, characterized in that, The data reporting request includes one or more of the following: the duration of the collected data, or the amount of collected data; The session establishment request includes one or more of the following: transmission type, target node ID for data transmission, or data task identifier.

40. The method according to any one of claims 33 to 36, characterized in that, The step of obtaining the configuration information for data collection based on the first paging message includes: An RRC connection state is established based on the first paging message, and the configuration information for the data acquisition is received from the connection release message from the network device.

41. The method according to any one of claims 24 to 40, characterized in that, The configuration information for data collection includes one or more of the following: data task identifier, data collection reporting trigger condition, data collection reporting method, data volume threshold, duration threshold, or reporting time.

42. The method according to claim 41, characterized in that, The data collection and reporting trigger conditions include one or more of the following: the amount of data collected reaches the data amount threshold, the collection duration reaches the duration threshold, or the reporting time is reached. The data collection and reporting methods include one or more of the following: control plane transmission, user plane transmission, or data plane transmission.

43. The method according to any one of claims 24 to 42, characterized in that, The downlink control information corresponding to the first paging message includes one or more of the following: the level of the terminal device, the type of the terminal device, or the paging reason.

44. The method according to claim 43, characterized in that, The level of the terminal device includes one or more of the following: the capability level of the terminal device, or the power consumption level of the terminal device; The type of terminal device includes one or more of the following: sensor, low-power device, other terminal device types besides the sensor and the low-power device, or all terminal device types; The paging reason includes one or more of the following: unicast paging, or broadcast paging.

45. The method according to claim 44, characterized in that, The terminal device's level information includes one or more of the following: a specified terminal device level, the upper limit of the terminal device's level, or the lower limit of the terminal device's level; The terminal device type information includes one or more of the following: a specified terminal device type, or a terminal device type other than the specified terminal device type.

46. ​​A communication device, characterized in that, The communication device includes a module for performing the method according to any one of claims 1 to 23, or includes a module for performing the method according to any one of claims 24 to 45.

47. A communication device, characterized in that, The communication device includes a processor; the processor is configured to perform the method according to any one of claims 1 to 23, or to cause the communication device to perform the method according to any one of claims 24 to 45.

48. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed, cause the method according to any one of claims 1 to 23 to be implemented, or cause the method according to any one of claims 24 to 45 to be implemented.

49. A computer program product, characterized in that, The computer program product includes instructions that, when executed, cause the method according to any one of claims 1 to 23 to be implemented, or cause the method according to any one of claims 24 to 45 to be implemented.

50. A communication system, characterized in that, The communication system includes the communication device as described in claims 46 and 47.