Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: a first device feeds back, to a core network device, first information associated with a data volume that can be transmitted between the first device and a second device; and the core network device determines second information on the basis of the first information, and sends the second information to the first device. A data volume of the second information can meet the requirement of a wireless channel between the first device and the second device on a data volume, thereby avoiding the problem that the first device cannot complete the transmission of upper-layer information (such as the second information).

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411600962.0, filed on November 8, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Current wireless communication systems, such as ambient internet of things (A-IoT) systems or internet of things (IoT) systems, can consist of readers (e.g., access devices) and tag devices (e.g., A-IoT devices). The readers and tag devices communicate non-contactly; for example, the reader can read information from the tag device or write information to the tag device. Key functions include inventory management, positioning, sensing, and command. Typical applications include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. How the readers (referred to as the first devices) communicate with core network equipment is a research direction. Summary of the Invention

[0005] In a first aspect, a communication method is provided, wherein the executing entity of the method is a first device, or a module, unit, or component (e.g., a chip, chip system, circuit, processor, or others) applied in the first device. For example, the executing entity of the method may also be a chip, which can be applied in the first device, comprising: sending first information to a core network device, the first information being associated with the amount of data that can be transmitted between the first device and a second device, or the first information being associated with the amount of data that can be transmitted between the core network device and the first device; receiving second information from the core network device; optionally, the second information is determined based on the first information.

[0006] Through the above design, the first device feeds back first information to the core network device, which is related to the amount of data that can be transmitted between the first device and the second device. The core network device determines the second information based on the first information and sends the second information to the first device. The amount of data in the second information can meet the data volume requirements of the wireless channel between the first device and the second device, thus avoiding the problem that the first device cannot complete the transmission of upper-layer information (such as the second information).

[0007] In one possible design, when the first information is associated with the amount of data that can be transmitted between the first device and the second device, the first information includes at least one of the following: a first data amount, a first transport block size (TBS), or first channel quality information; wherein the first data amount is the amount of data that can be transmitted between the first device and the second device, the first TBS is the TBS that can be transmitted between the first device and the second device, and the first channel quality information is the quality information of the wireless channel between the first device and the second device.

[0008] In one possible design, when the first information is associated with the amount of data that can be transmitted between the core network device and the first device, the first information includes: a second amount of data, the second amount of data being the amount of data that can be transmitted between the core network device and the first device.

[0009] In one possible design, the amount of data in the second information is determined based on the first information.

[0010] In one possible design, the method further includes sending third information to the second device, the third information being determined based on the second information, the data volume of the third information satisfying the data volume requirements of the wireless channel between the first device and the second device.

[0011] In one possible design, the scheduling information included in the second information is determined based on the first information, and the scheduling information is used to schedule the second device to send information to the first device.

[0012] In one possible design, the method further includes: sending third information to the second device, the third information being determined based on the second information, the third information including scheduling information for scheduling the second device to send fourth information; and receiving fourth information from the second device, the data amount of the fourth information satisfying the data amount requirements of the wireless channel between the first device and the second device.

[0013] In one possible design, the second information, the third information, or the fourth information includes first indication information, which indicates the quantity of information containing the first indication information.

[0014] In one possible design, the second information, the third information, or the fourth information includes second indication information, which is used to indicate whether the information containing the second indication information is transmitted in segments.

[0015] In one possible design, the second information, the third information, or the fourth information includes third indication information, which is used to indicate whether the information containing the third indication information has been transmitted.

[0016] Through the above design, the first instruction information, the second instruction information, or the third instruction information can notify the first device or the second device that the above multiple information (such as N information) are for a single service, thus preventing the first device or the second device from prematurely ending the service or responding to the transmission of other services.

[0017] In one possible design, before sending the first information to the core network device, the method further includes: receiving fifth information from the core network device; the fifth information does not meet the data volume requirements of the wireless channel between the first device and the second device.

[0018] Secondly, as a countermeasure to the first aspect, with beneficial effects as described in the first aspect, a communication method is provided. The execution subject of this method is a core network device, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the core network device. For example, if the execution subject of this method is a chip, the chip can be applied in the core network device, including: receiving first information from a first device, the first information being associated with the amount of data that can be transmitted between the first device and a second device, or the first information being associated with the amount of data that can be transmitted between the core network device and the first device; sending second information to the first device; optionally, the second information is determined based on the first information.

[0019] In one possible design, when the first information is associated with the amount of data that can be transmitted between the first device and the second device, the first information includes at least one of the following: a first data amount, a first transport block size (TBS), or first channel quality information; wherein the first data amount is the amount of data that can be transmitted between the first device and the second device, the first TBS is the TBS that can be transmitted between the first device and the second device, and the first channel quality information is the quality information of the wireless channel between the first device and the second device.

[0020] In one possible design, when the first information is associated with the amount of data that can be transmitted between the core network device and the first device, the first information includes: a second amount of data, the second amount of data being the amount of data that can be transmitted between the core network device and the first device.

[0021] In one possible design, the amount of data in the second information is determined based on the first information.

[0022] In one possible design, the scheduling information included in the second information is determined based on the first information, and the scheduling information is used to schedule the second device to send information to the first device.

[0023] In one possible design, the second information includes first indication information, which indicates the quantity of the second information.

[0024] In one possible design, the second information includes second indication information, which is used to indicate whether the second information is transmitted in segments.

[0025] In one possible design, the second information includes third indication information, which is used to indicate whether the transmission of the second information is complete.

[0026] In one possible design, before receiving the first information from the first device, the method further includes: sending a fifth message to the first device, the fifth message not meeting the data volume requirements of the wireless channel between the first device and the second device.

[0027] Thirdly, a communication method is provided, wherein the execution subject of the method is a second device, or a module, unit or component (e.g., chip, chip system, circuit, processor, or others) applied in the second device. For example, if the execution subject of the method is a chip applied in the second device, the method includes: receiving multiple pieces of information from a first device; if the multiple pieces of information are not continuous, discarding the multiple pieces of information.

[0028] With the above design, in the event of a transmission anomaly, such as when the second device receives multiple segments of paging messages that are not continuous, the second device can directly discard the multiple segments of paging messages that are experiencing the transmission anomaly, thereby reducing the additional / temporary buffering overhead of the second device and reducing the impact of temporary buffering on device power consumption.

[0029] In one possible design, each of the plurality of information contains a serial number, and the discontinuity of the plurality of information includes: the serial numbers contained in the plurality of information are not consecutive.

[0030] In one possible design, the multiple pieces of information are transmitted in segments, and the method further includes: ceasing to receive other information in that segment.

[0031] In one possible design, the multiple messages are segmented paging messages used to page or select the second device.

[0032] In one possible design, the method further includes sending a response message to the first device, the response message indicating that at least one of the plurality of messages failed to be received.

[0033] In one possible design, the response information includes a sequence number of the information indicating a failed reception.

[0034] In one possible design, at least one of the plurality of information includes first indication information, which indicates the quantity of the plurality of information.

[0035] In one possible design, at least one of the plurality of information includes second indication information, which is used to indicate that the plurality of information be transmitted in segments.

[0036] In one possible design, at least one of the plurality of information includes third indication information, which is used to indicate whether the service transmission corresponding to the plurality of information is completed or not.

[0037] Fourthly, an apparatus is provided capable of implementing the methods of any one of the first to third aspects described above. For example, the apparatus includes modules, units, or components corresponding to performing the methods described in any one of the first to third aspects. The modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0038] In one design, the device includes a unit that performs any one of the methods described in the first to third aspects.

[0039] In one design, the device includes a processor for implementing the methods of any one of the first to third aspects described above. Optionally, the device further includes a memory, with the processor coupled to the memory, the processor executing computer programs or instructions stored in the memory, causing the device to implement the methods of any one of the first to third aspects described above.

[0040] In one design, the device includes a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor implements the methods of any one of the first to third aspects described above through logic circuits or executing code instructions.

[0041] In one design, the device may be a first device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the methods / operations / steps / actions described in the first, second, or third aspects of the first device, or a device that can be used in conjunction with the first device.

[0042] Fifthly, a computer-readable storage medium is provided, storing a computer program or instructions that, when executed on a computer, cause the computer to implement the methods of any one of the first to third aspects described above.

[0043] A sixth aspect provides a computer program product, including a computer program or instructions that, when executed by a computer, cause the methods of any one of the first to third aspects to be performed.

[0044] A seventh aspect provides a chip including a processor for implementing the methods of any one of the first to third aspects described above. Optionally, the chip further includes a memory, the processor being coupled to the memory, the processor executing computer programs or instructions stored in the memory, causing the chip to implement the methods of any one of the first to third aspects described above.

[0045] Eighthly, a communication system is provided, comprising: a first communication device and a second communication device; wherein the first communication device is used to implement the method of the first aspect described above; and the second communication device is used to implement the method of the second aspect described above. Alternatively, the first communication device is used to implement the method of the third aspect described above; and the second communication device is used to implement the method corresponding to the first device. Attached Figure Description

[0046] Figure 1 is a schematic diagram of a communication system (such as an RFID system / A-IoT system / IoT system) provided in an embodiment of this application;

[0047] Figures 2, 3, 4a, 4b and 5 are schematic diagrams of the network architecture provided in the embodiments of this application;

[0048] Figure 6 is a schematic diagram of the ORAN system provided in an embodiment of this application;

[0049] Figure 7 is a schematic diagram of the protocol layer division of the ORAN device provided in the embodiment of this application;

[0050] Figure 8 is a schematic diagram of the protocol layer division of the access network device provided in the embodiment of this application;

[0051] Figures 9a and 9b are schematic diagrams of the current solution provided in this application;

[0052] Figure 10 is a schematic diagram of a process provided in this application;

[0053] Figure 11 is a schematic diagram of the protocol layer structure provided in this application;

[0054] Figure 12 is a schematic diagram of another process provided in this application;

[0055] Figure 13 is a schematic diagram of another process provided in this application;

[0056] Figure 14 is a flowchart of a specific example corresponding to the process in Figure 13;

[0057] Figure 15 is another schematic diagram of the ORAN architecture provided in an embodiment of this application;

[0058] Figures 16 and 17 are schematic diagrams of the structure of the device provided in the embodiments of this application. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The specific operating methods and functional descriptions in the method embodiments can also be applied to the device embodiments or system embodiments.

[0060] In this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship; in the formulas of this application, the character " / " indicates that the preceding and following related objects have a "division" relationship. "Including at least one of A, B, or C" or similar expressions can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C, where A, B, and C can be singular or plural.

[0061] In the embodiments of this application, the various numerical designations are used for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic. The ordinal numbers such as "first" and "second" used in the embodiments of this application are used to distinguish multiple objects and do not limit the size, order, timing, priority, or importance of the multiple objects.

[0062] Radio Frequency Identification (RFID) systems consist of readers and tags. Readers can read information from tags or write information to tags. The reader and tag communicate non-contactly. Tags are simple in function, requiring excitation from the reader to transmit information; that is, the tag converts the wireless signal emitted by the reader into energy to power itself. Tags support microwatt-level or hundreds of microwatt-level functionality and cannot support complex designs. Tags can also be called electronic tags, RFID tags, or simply tags. In the following description, the term "tag" will be used primarily.

[0063] As shown in Figure 1, the reader can send a carrier signal to the tag, and the tag receives the carrier signal through its antenna. The solid line in Figure 1 represents the carrier signal sent by the reader, and the dashed line represents the signal transmitted by the tag based on the reflection of the carrier signal. The tag can adjust the information to be transmitted in the reflected signal. Through this method, the tag uses a low-precision, low-power mid-to-low frequency ring oscillator or a completely oscillator-less method to receive downlink signals, further reducing the power consumption of downlink reception. The tag is a miniature wireless transceiver device, mainly consisting of a built-in tag antenna, coupling elements, and a chip. The tag's chip has storage space that supports the reader in reading or writing tag data. After the tag receives the radio frequency signal sent by the reader through its antenna, it can couple the radio frequency signal through the coupling element. This coupler channel can then provide power to the tag's chip and feed back the data stored in the chip to the reader through the antenna.

[0064] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. A-IoT is an extremely low-power, low-complexity IoT technology, which can be understood as an extension of RFID within 3GPP. Although A-IoT and RFID share some principles, 3GPP introduces more value scenarios.

[0065] In A-IoT, both readers and tags can be implemented based on cellular network infrastructure. In other words, both readers and tags can be devices within the cellular network. For example, the functionality of a reader can be implemented by access network devices, such as base stations. Tags can be implemented by terminals within the cellular network, such as ultra-low power, ultra-low complexity IoT terminals. Access network devices and terminals can perform contactless data communication, thereby reading information from the terminal and / or writing information that needs to be stored into the terminal. In A-IoT technology, the terminal can be an ultra-low power, ultra-low complexity IoT terminal, which can be called an A-IoT device or an A-IoT terminal.

[0066] Figure 2 illustrates a schematic diagram of a communication system applicable to an embodiment of this application. As shown in Figure 2, the communication system includes an access network device and an A-IoT device. The A-IoT device can be a standalone device or integrated with a terminal device, i.e., the A-IoT device is part of the terminal device. In this communication system, the access network device can function as a reader, and the A-IoT device can function as a tag. The access network device can communicate with the A-IoT device, which functions as a tag, as a reader. The communication interface between the access network device and the A-IoT device is a Uu interface, i.e., an air interface.

[0067] Figure 3 illustrates a schematic diagram of another communication system applicable to embodiments of this application. As shown in Figure 3, the communication system includes an access network device, an intermediate node, and an A-IoT device. The access network device and the A-IoT device communicate through an intermediate node, which can be considered a relay node, primarily acting as a relay. For example, the intermediate node can forward signaling and / or data sent by the access network device to the A-IoT device, or forward signaling and / or data sent by the A-IoT device to the access network device. The intermediate node can be a repeater, an integrated access and backhaul (IAB) node, or a terminal device, etc., without limitation. The A-IoT device can be a standalone device, or it can be integrated with a terminal. The access network device and the intermediate node are connected via a Uu interface, and the intermediate node and the A-IoT device are directly connected. In one interpretation, the access network device may have a reader / writer function, and the A-IoT device may have a tag function. Access network devices can send data and / or signaling to A-IoT devices through intermediate nodes, and A-IoT devices can send data and / or signaling to access network devices through intermediate nodes. Alternatively, in another interpretation, intermediate nodes can function as readers, and A-IoT devices can function as tags. For example, access network devices can pre-configure the communication resources of intermediate nodes, and intermediate nodes can use these pre-configured communication resources to communicate with A-IoT devices.

[0068] Figure 4a or Figure 4b illustrates a schematic diagram of another communication system applicable to embodiments of this application. As shown in Figure 4a or Figure 4b, the communication system includes an access network device, an auxiliary node, and an A-IoT device. The auxiliary node can be a repeater, an IAB node, or a terminal device, etc. The access network device or auxiliary node may have a reader / writer function, and the A-IoT device may have a tag function. The communication interface between the access network device and the auxiliary node can be a Uu interface. The auxiliary node assists in the communication between the access network device and the A-IoT device. Figure 4a is a schematic diagram of downlink assistance. During downlink assistance, the access network device communicates with the A-IoT device through the auxiliary node. For example, the access network device can send downlink data to the auxiliary node, and the auxiliary node forwards the downlink data to the A-IoT device. Figure 4b is a schematic diagram of uplink assistance. During uplink assistance, the A-IoT device can send uplink data to the auxiliary node, and the auxiliary node forwards the uplink data to the access network device.

[0069] Figure 5 illustrates a schematic diagram of another communication system applicable to embodiments of this application. As shown in Figure 5, the communication system includes a terminal device and an A-IoT device. The A-IoT device can be a standalone device or integrated with the terminal device. In this communication system, the terminal device can have a reader / writer function, the terminal can have a tag function, and the terminal device and the A-IoT device can communicate via a sidelink.

[0070] Figure 6 is a schematic diagram of the open radio access network (O-RAN or ORAN) system to which this application applies. As shown in Figure 6, the ORAN system includes: core network equipment, access network equipment, and terminals. The access network equipment communicates with the core network equipment via a backhaul link and with the terminals via an air interface. The access network equipment includes a baseband unit (BBU) and a radio unit (RU). The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. Specifically, the BBU communicates with the core network equipment via the backhaul link, and the RU communicates with the terminals via an air interface. The BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link. In the ORAN system, the CU can also be called an open CU (O-CU), and the DU can also be called an open DU (O-DU).

[0071] Figure 7 is a schematic diagram of the network element function division and protocol layer structure of the ORAN equipment to which this application applies. It can be understood that the access network equipment adopts the ORAN architecture, and the access network equipment can be referred to as ORAN equipment, which is used to realize the wireless access of terminals. The communication between the access network equipment and the terminal follows a certain protocol layer structure. This protocol layer structure can include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure can include the functions of protocol layers such as the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer. For example, the user plane protocol layer structure can include the functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the physical layer. In one possible implementation, a service data adaptation protocol (SDAP) layer can also be included above the PDCP layer.

[0072] As shown in Figure 7, the access network equipment includes logical nodes such as CU, DU, and RU. The CU can connect to the core network via an interface, for example, an E2 interface. Optionally, the CU may possess some core network functions. The CU can control at least one DU, and the CU can connect to the DU via an interface, for example, an F1 interface. Further, the control plane (CP) interface can be called F1-C, and the user plane (UP) interface can be called F1-U. The DU can control at least one RU, and the DU can connect to the RU via an interface, for example, a fronthaul interface.

[0073] 1. CU

[0074] A CU can be a logical node that carries the RRC layer, SDAP layer, PDCP layer, and other control functions of access network equipment. In other words, a CU can implement the functions of the RRC layer, SDAP layer, PDCP layer, and certain control functions.

[0075] Furthermore, the CU can be divided into CU-CP and CU-UP. Referring to Figure 7, CU-CP is a logical node carrying the control plane (control plane part of PDCP, PDCP-C) of the RRC and PDCP layers, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements, such as the access and mobility management function (AMF) in a 5G communication system. Continuing to refer to Figure 7, CU-UP is a logical node carrying the data plane (user plane part of PDCP, PDCP-U) of the SDAP and PDCP layers, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions, such as the user plane function (UPF) in a 5G communication system.

[0076] 2. DU

[0077] A DU can be a logical node that carries the RLC layer, MAC layer, higher physical layer (Higher PHY) layer, and other functions. For example, the higher physical layer may include some of the processing functions of the PHY layer, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation. In other words, a DU can implement the functions of the RLC layer, MAC layer, higher physical layer, and other functions.

[0078] It is understood that the above CU and DU configurations are merely examples, and the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0079] 3. RU

[0080] An RU can be a logical node that carries both lower physical layer (PHY) and radio frequency (RF) chain processing. For example, the lower physical layer includes some of the processing functions of the physical layer, such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering. In other words, an RU can implement both physical layer and RF functions.

[0081] In one possible implementation, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entity. The RU communicates with one or more terminals via a wireless link.

[0082] The DU and RU can be co-located or non-co-located, without restriction. Referring to Figure 7, the relationship between the DU and RU may include the O-RAN control user and synchronization (CUS-Plane) and the O-RAN management plane (M-Plane). The O-RAN CUS plane can be simply referred to as the CUS plane, and the O-RAN management plane can be simply referred to as the management plane. Further, the CUS plane can be divided into a control plane (C-Plane) and a user plane (U-Plane). Optionally, the control plane refers to the real-time control plane between the DU and RU. The management plane refers to the non-real-time management operations between the DU and RU.

[0083] Referring to Figure 7, the DU and RU exchange control plane and user plane information via the lower-layer split CUS-Plane (LLS-CUS) interface through the fronthaul link. Furthermore, the LLS-CUS interface may include an LLS-C interface corresponding to the control plane and an LLS-U interface corresponding to the user plane. The DU and RU exchange management plane information through the LLS-M interface of the fronthaul link. Referring to Figure 7, the LLS-M interface can also connect to an external management system.

[0084] It is understandable that DUs and RUs can cooperate to implement physical layer functions. A DU can be connected to one or more RUs. The functions of DUs and RUs can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the physical layer, and an RU can be configured to implement lower-level functions in the physical layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0085] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0086] 1. Access network equipment

[0087] Access network equipment can be devices in a wireless network used to help terminals access the wireless network. For example, access network equipment is a radio access network (RAN) node that connects a terminal to the wireless network, and can also be called an RAN node. Access network equipment includes, but is not limited to: base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment in open radio access networks (O-RANs), next-generation base stations or base stations in future communication networks, or access nodes in wireless fidelity (WiFi) systems, etc. Access network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. This application does not limit the specific technologies or specific equipment forms used in the access network equipment.

[0088] Alternatively, the access network equipment can also be a device that implements the functions of the access network equipment. For example, the access network equipment can be a module or unit that performs some of the functions of the base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP), or a central unit user plane (CU-UP). As shown in Figure 8, in some implementations, the access network equipment can include a central unit (CU) and a distributed unit (DU). This includes access network equipment with CU nodes and DU nodes that separates the protocol layer of the gNB in ​​the new radio (NR) system. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Furthermore, the CU can also be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for the control plane functions, mainly including radio resource control (RRC) and the packet data convergence protocol (PDCP) (i.e., PDCP-C) corresponding to the control plane. PDCP-C is primarily responsible for control plane data encryption / decryption, integrity protection, and data transmission. CU-UP handles user plane functions, mainly including the Service Data Adaptation Protocol (SDAP) and the corresponding PDCP (PDCP-U). SDAP primarily processes core network data and maps flows to bearers. PDCP-U is mainly responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. CU-CP and CU-UP are connected via the E1 interface. CU-CP represents the access network device connecting to the core network via the NG interface and to the DU via the F1 interface control plane (F1-C). CU-UP connects to the DU via the F1 interface user plane (F1-U).

[0089] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in O-RAN or ORAN systems, CU may also be called open CU (O-CU), DU may also be called open DU (O-DU), CU-CP may also be called O-CU-CP, and CU-UP may also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples.

[0090] In some embodiments, the access network device may further include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for handling non-real-time protocols and services, implementing the functions of the RRC layer. The DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer.

[0091] 2. Terminal

[0092] A terminal is a device with specific wireless transceiver capabilities, such as a handheld device or in-vehicle device with wireless connectivity. Terminals can also be called terminal equipment, user equipment (UE), mobile station, or mobile terminal. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart homes, smart offices, wearable devices, intelligent transportation, and smart cities.

[0093] Currently, some examples of terminals include: mobile phones, satellite mobile terminals, cellular phones, smartphones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. Wireless terminals in the home (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes), terminals in 5G networks, or terminals in future evolved public land mobile networks (PLMNs), etc., the embodiments of this application do not limit the device form of the terminal.

[0094] A terminal can also be a device that implements terminal functions. For example, a terminal can be a module, unit, or component that implements terminal functions, such as a chip, chip system, circuit, or processor applied to the terminal. For instance, a terminal can be a chip or a system on a chip (SOC), which can be installed in the terminal.

[0095] 3. Environmental Internet of Things (A-IoT)

[0096] A-IoT, a communication infrastructure based on cellular networks, consists of readers and A-IoT devices. For example, in a cellular network, access network equipment (such as base stations and relays) can function as readers, or terminals can function as readers, such as smartphone terminals in 3GPP Release 15 (R15) or Release 16 (R16), or reduced-capability (RedCap) terminals in Release 17 (R17). Even intermediate or auxiliary nodes can function as readers; for details on intermediate or auxiliary nodes, please refer to Figure 3 or Figures 4a / 4b above.

[0097] In A-IoT, typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring. The main business operations include at least one of the following: inventory, positioning, sensing, and command. Command operations can be understood to include at least one of read, write, or lock operations. Inventory operations, also known as inventory checks, obtain tag identification information. For example, a reader can use query or acknowledge (ACK) commands to obtain tag identification information. Read operations: Read operations can read the electronic product code (EPC), tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's storage area. Write operations: Write operations can write data to the tag's storage area. Kill operations: Kill operations can permanently disable the tag. Lock operations: Lock operations can lock the tag's information, preventing read or write operations on the tag. Alternatively, locking can also lock a storage area, preventing or allowing read or write operations on that area. The above are just examples; other operations or services can be performed between the tag and the reader, which will not be illustrated here.

[0098] 4. A-IoT devices

[0099] An A-IoT device is a device with receiving or reflecting capabilities. For example, an A-IoT device can be a terminal in an IoT system. IoT is an important component of future information technology development, its main technical characteristic being the connection of objects to networks via communication technology, thereby achieving intelligent networks that enable human-machine and machine-to-machine interconnection. An A-IoT device can also be called an A-IoT terminal, and it can be a terminal with extremely low power consumption and low complexity. Some examples of A-IoT devices include sensors such as smart speakers, train detectors, gas stations, and inventory tags. Their main functions include collecting data, receiving control information and downlink data from access network devices or terminals, and sending uplink data to access network devices or terminal devices.

[0100] In one classification method, A-IoT devices can be categorized into passive, semi-passive, and active A-IoT devices. Passive and semi-passive A-IoT devices can employ backscatter-based communication. For example, these types of A-IoT devices do not generate uplink signals but support reflection. Access network devices, auxiliary terminals, or intermediate nodes can send carrier signals to the A-IoT devices. The A-IoT devices reflect the received carrier signals to achieve uplink transmission. For instance, the A-IoT devices can adjust the received carrier signals to carry specific uplink information, and then reflect the adjusted carrier signals. Access network devices or intermediate nodes can obtain the uplink information based on the received reflected signals. Alternatively, within a given time period, the A-IoT devices may reflect carrier signals at certain times and not at other times. During this period, when the access network device or intermediate node receives a reflected signal, it can identify the uplink signal as 1; when no reflected signal is received, it identifies the uplink signal as 0, thus achieving the purpose of uplink information transmission. The main difference between passive and semi-passive A-IoT devices is that passive A-IoT devices have no energy storage, while semi-passive A-IoT devices have energy storage and support amplification of reflected signals. Active A-IoT devices use an active carrier-generating communication method. For example, active A-IoT devices have energy storage and support amplification of uplink and / or downlink signals. The access network device or intermediate node can indicate uplink transmission resources to the A-IoT device, which can generate an uplink signal and transmit it on the indicated uplink transmission resources.

[0101] In another classification method, A-IoT devices can be divided into the following three types:

[0102] Device A or Device 1: It has no energy storage, cannot generate signals independently, and uses backscatter to transmit signals; its function is similar to that of a passive A-IoT device.

[0103] Device B or Device 1b: It has energy storage but cannot generate signals independently. It uses backscatter to transmit signals. The stored energy can amplify the reflected signal. Its function is similar to that of a semi-passive A-IoT device.

[0104] Device C or Device 2: It has energy storage, can generate signals independently, and has active radio frequency components for transmission. Its function is similar to that of an active A-IoT device.

[0105] The solutions provided in this application can be applied to various mobile communication systems, such as the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), fourth-generation (4G) communication systems (e.g., Long Term Evolution, LTE), fifth-generation (5G) communication systems (e.g., 5G New Radio, NR), hybrid LTE and NR architectures, and new communication systems emerging in future communication developments. The communication system can also include machine-to-machine (M2M) networks, machine-type communication (MTC), or other networks. For example, the methods and apparatus provided in the embodiments of this application can be applied to communication systems that support ambient IoT (AIoT) or Internet of Things (IoT) technologies.

[0106] The communication system and business scenarios (or application scenarios) described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios (or new application scenarios), the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0107] The core network device can send downlink data (DL data) to the first device. The first device can process this downlink data and generate a corresponding message, which may be called an R2D message or an A-IoT message, etc. The first device then sends this message to the second device. The first device is a device with reader functionality, and the second device is a device / tag functionality. For example, in the network architecture of Figure 9a, the first device is an access network device that implements the reader function. The second device is a terminal or an A-IoT device that implements the device function. Alternatively, in the network architecture of Figure 9b, the first device is a terminal that implements the reader function. The second device is a terminal or an A-IoT device that implements the device function. It can be understood that in the network architecture of Figure 9b, the core network sends downlink data to the first device through the access network device.

[0108] Under the condition of ensuring a certain coverage, the actual amount of data / bits transmitted via the wireless channel between the reader (e.g., the first device) and the device (e.g., the second device) is related to various factors, such as wireless channel quality, transmission parameters (e.g., encoding method, code rate, code length, bit repetition count, level repetition count, etc.), and transmission power. The size of the information transmitted between the first device and the second device may be larger than the transport block size (TBS) that the physical channel between the first device and the second device can transmit. For example, the maximum TBS that the wireless channel between the first device and the second device can transmit is less than 1000 bits, but the downlink data received by the first device from the core network occupies 1000 bits, which may cause the first device to be unable to complete the transmission of the uplink message, which can be understood as the message corresponding to the downlink data received by the first device from the core network.

[0109] This application provides a communication method and apparatus. The principle is as follows: a first device feeds back first information to a core network device, which relates to the amount of data that can be transmitted between the first device and the second device. The core network device determines second information based on the first information and sends the second information to the first device. The amount of data in the second information can meet the data volume requirements of the wireless channel between the first device and the second device, thus avoiding the problem that the first device cannot complete the transmission of upper-layer information (such as the second information).

[0110] In the following description, the method provided in this application is illustrated using the execution entity as a first device, a second device, or a core network device as an example. It is understood that the operations performed by the first device, the second device, or the core network device can also be implemented through the processor, circuit, chip, or chip system of the corresponding device, or through a functional module, component, or unit. Furthermore, the processing performed by a single execution entity can also be divided among multiple execution entities, which can be logically and / or physically separated. For example, when the first device is an access network device implementing a reader / writer function, the processing performed by the access network device can be divided among at least one of a CU, DU, RU, etc.

[0111] In the description of this application, "sending information to (such as core network equipment)" can be understood as the destination of the information being the core network equipment. This can include sending information directly or indirectly to (such as core network equipment). "Receiving information from (such as core network equipment)" can be understood as the source of the information being the core network equipment, which can include receiving information directly or indirectly from the core network equipment. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0112] In the description of this application, "transmit" or "receive" indicates the direction of information / signals. "Transmit" or "receive" can also be understood as "input" or "output." "Transmit" or "receive" can occur between devices, for example, between a first device and a second device via a wireless channel. "Transmit" or "receive" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface. For example, "transmit" can also be understood as the "output" of a chip interface, and "receive" can be understood as the "input" of a chip interface.

[0113] As shown in Figure 10, a flowchart is provided, including:

[0114] Step 1010: The core network device sends the fifth information to the first device, and the first device receives the fifth information from the core network device.

[0115] Step 1010 is optional. In the description of this application, the core network device can be a control plane network element, such as an AMF network element or an AIoTMF network element, or the core network device can be a data plane network element, such as a UPF network element. The full name of the AIoTMF network element is AIoT management function network element. The first device can be a device with a reader function, and the second device can be a device with device / AIoT device / tag function. In different network architectures, the specific devices corresponding to the first and second devices are different. For example, in the network architecture of Figure 2, the first device is an access network device, and the second device is an AIoT device. In this application, A-IoT device and AIoT device have the same meaning and can be used interchangeably. In the network architecture of Figure 3, the first device is an access network device or an intermediate node, and the second device is an AIoT device. In the network architecture of Figure 4a or Figure 4b, the first device is an access network device or an auxiliary node, and the second device is an AIoT device. In the network architecture of Figure 5, the first device is a terminal device, and the second device is an AIoT device.

[0116] There are no restrictions on the name of the fifth piece of information. For example, the fifth piece of information can be or be carried in a Next Generation Application Protocol (NGAP) message, or an A-IoT NGAP message, or XXAP, where XX is any name. For example, the fifth piece of information can be an NGAP message, or carried / included in an NGAP message. Optionally, the interface between the core network device and the first device can be an NG interface, and the protocol name NGAP is a combination of the NG interface and the application layer protocol (AP). This NGAP can be the application layer protocol between the first device and the core network device. Furthermore, the fifth piece of information can be a service request, a paging message, or downlink data, etc. A service request is used to request the first device to execute a corresponding service. This service can be: environmental IoT service, inventory, positioning, sensing, command (such as read service, write service, or lock service), etc., without restriction. In this case, the service request can be specifically described as: environmental IoT service request, inventory service request, positioning service request, sensing service request, or command service request, etc. In one interpretation, the service request includes a paging message or downlink data that the first device needs to send to the second device.

[0117] In one interpretation, the fifth message needs to be sent from the first device to the second device. Before the first device sends the fifth message to the second device, the first device determines whether the fifth message meets the data volume requirements of the wireless channel between the first and second devices. If the fifth message does not meet the data volume requirements of the wireless channel between the first and second devices—for example, if the fifth message is longer than the length that can be transmitted in one R2D message (which can be understood as a message sent from the first device (reader) to the second device (device); or if the fifth message includes the identifiers of one or more devices, and these identifiers are longer than the TBS that can be transmitted in one R2D message; or if the downlink data in the fifth message that needs to be forwarded to the second device is longer than the TBS that can be transmitted in one R2D message—then the first device executes step 1020, sending the first message to the core network device. If the fifth message meets the data volume requirements of the wireless channel between the first and second devices, then the first device can send the fifth message to the second device. For example, if the first device processes the received fifth message and sends the processed information to the second device, it can be understood that the processed information contains at least the fifth message.

[0118] In another interpretation, the fifth information can be understood as a triggering message. For example, the fifth information is used to trigger the first device to send the first information to the core network device. When / after receiving the fifth information, the first device executes step 1020, sending the first information to the core network device. Alternatively, the first device can proactively send the first information to the core network device; that is, in the process of Figure 10, step 1010 may not be executed. Therefore, step 1010 is optional; it can be executed in the process of Figure 10, or it may not be executed in the process of Figure 10.

[0119] In one possible implementation, the core network device may send information related to the amount of data in the second information (for ease of description, this information can be referred to as the Xth information, where X can be an integer greater than 6). For example, the Xth information could be the size of the NAS PDU included in the second information, or a rough estimate of the second information's data size, the expected data size, the anticipated data size, the precise data size, the maximum data size, or an approximate data size. In another understanding, the Xth information can be interpreted as the fifth information. For instance, the Xth information could be one way to trigger the first device to send the first information, or it could be another piece of information that the core network device can send before, after, or together with the fifth information to the first device. Accordingly, the first device can determine whether to send the first information based on the Xth information.

[0120] In the description of this application, "information" can also be replaced with names such as message, signal, and data. For example, fifth information can be replaced with fifth message, fifth signal, or fifth data. Similarly, the first information / second information, etc. in the following text can be replaced with first message / second message, first signal / second signal, or first data / second data, etc.

[0121] It is understood that in this application, the first device and the core network device can directly communicate and transmit information, such as directly transmitting the fifth information, the first information or the second information mentioned below. For example, if the first device is an access network device, the core network device and the access network device can directly communicate and transmit information. Alternatively, the first device and the core network device can indirectly communicate and transmit information through other devices / network elements. For example, in the network architecture of Figure 5, the first device is a terminal device (which can be simply referred to as the terminal), and the terminal and the core network device transmit the fifth information, the first information or the second information mentioned below, etc., through the access network device.

[0122] Step 1020: The first device sends the first information to the core network device, and the core network device receives the first information from the first device.

[0123] In one possible implementation, the first information is associated with the amount of data that can be transmitted between the first device and the second device. This data amount could be a rough estimate, a desired amount, an estimated amount, a precise amount, a maximum amount, or an approximate amount. In one understanding, when the fifth information received by the first device from the core network device does not meet the requirements for the amount of data that can be transmitted by the wireless channel or air interface transmission between the first and second devices, or the amount of data that the allocated resources can transmit, the first device feeds back the first information to the core network device to measure the amount of data that can (or is desired or suggested) be transmitted between the first and second devices. Alternatively, the core network device requests or triggers the first device to send the first information, and the first device feeds back the first information to the core network device to measure the amount of data that can (or is desired or suggested) be transmitted between the first and second devices. Or, the first device proactively feeds back the first information to the core network device to measure the amount of data that can (or is desired or suggested) be transmitted between the first and second devices. Based on the first information, the core network device feeds back the second information that meets the requirements to the first device (this process can be referred to in the description of step 1030).

[0124] In one possible implementation, the first information includes either an acknowledgment or a rejection message, serving as feedback to the fifth / Xth information. For example, after the core network device sends the fifth and / or the Xth information, the first device determines whether the current channel can transmit a sufficient amount of data. If so, the first device sends the first information (e.g., an acknowledgment), indicating that it can transmit the information from the core network device. For instance, if the amount of data that the first and second devices can transmit is greater than or equal to the amount of data in the fifth information, the first information sent by the first device includes an acknowledgment, such as an acknowledgment (ACK) (response). Alternatively, if the amount of data that the first and second devices can transmit is less than the amount of data in the fifth information, the first information sent by the first device includes a rejection message, such as a negative acknowledgment (NACK) (response).

[0125] For example, the first information includes at least one of the following:

[0126] First data volume / first data packet size: The first data volume / first data packet size can be understood as the amount of data / data packet size that can (or is expected or suggested) be transmitted between the first device and the second device. For example, the first data volume / first data packet size may include the data packet / data volume size that can be transmitted in reader-to-device (R2D) messages or downlink channels. For example, the downlink channel may be a physical reader-to-device channel (PR2DCH). And / or, the first data volume / first data packet size may include the data packet / data volume size that can be transmitted in device-to-reader (D2R) messages or uplink channels. For example, the uplink channel may be a physical device-to-reader channel (PD2RCH). In the uplink / D2R scenario, the first data volume / first data packet size can specifically be: the data volume / data packet size of the D2R messages that the first device schedules the second device to send to the first device. For example, the first data volume / first data packet size can be determined based on the size of the time domain and / or frequency domain resources allocated / scheduled / configured between the first device and the second device. For instance, with the same transmission parameters, the more time domain and / or frequency domain resources allocated / scheduled / configured, the larger the first data volume / first data packet size can be transmitted between the first device and the second device.

[0127] First TBS: The first TBS is the TBS that can (or is expected or suggested) be transmitted between the first device and the second device; if the first TBS includes a downlink TBS, such as at least one of the maximum value of the downlink TBS, the minimum value of the downlink TBS, the maximum value of the current downlink TBS, or the minimum value of the current downlink TBS, the corresponding transmission direction for the downlink is R2D; and / or, the first TBS includes an uplink TBS, such as at least one of the maximum value of the uplink TBS, the minimum value of the uplink TBS, the maximum value of the current uplink TBS, or the minimum value of the current uplink TBS, the corresponding transmission direction for the uplink is D2R. In one understanding, what is transmitted between the MAC layer and the PHY layer is a MAC PDU, which can also be understood as a transport block TB. The aforementioned first TBS can refer to the size of the transport block TB or MAC PDU transmitted between the MAC layer and the PHY layer. In this application, the MAC PDU or TB must satisfy the first TBS, for example, the size of the MAC PDU / TB does not exceed the first TBS. For example, the first TBS is Y bytes / bit, and the size of the MAC PDU / TB should not exceed Y bytes / bit, where Y is any rational number. For instance, data sent from the core network device to the first device (such as the fifth information) is sent as part of a MAC PDU (e.g., the information sent from the core network to the first device could be a NAS PDU / upper layer data, which is part of the MAC PDU), and then sent to the second device through the first device. If the size of the MAC PDU or TB is greater than the first TBS, the first device sends the first information to the core network device. That is, when the first device receives the fifth information and / or the Xth information from the core network device, if the fifth information or the Xth information can be a NAS PDU or upper layer data, the first device can encapsulate the NAS PDU or upper layer data (e.g., at least MAC layer encapsulation) to obtain the corresponding MAC PDU or TB. If the MAC PDU or TB is greater than the first TBS, the first device sends the first information back to the core network device.

[0128] TBS-related information: TBS-related information is used to determine the TBS, which can refer to the uplink TBS and / or downlink TBS, without limitation. For example, TBS-related information includes at least one of the following: modulation order, code rate, transmission resource information (such as the number of subcarriers or resource blocks (RBs), time-domain resources and / or frequency-domain resources, etc.).

[0129] First Channel Quality Information: First channel quality information refers to the quality information of the wireless channel between the first device and the second device. It is used to measure the channel conditions / quality of the transmission channel between the first device (reader) and the second device (device). There are no restrictions on the specific content / format of the first channel quality information. For example, the first channel quality information may include at least one of the following: signal-to-interference-plus-noise ratio (SINR), signal-to-noise ratio (SNR), or channel state information (CSI) of the transmission channel between the first device (reader) and the second device (device).

[0130] Understandably, the above possible implementations can be applied to downlink or R2D transmission scenarios, or uplink or D2R transmission scenarios. For example, in a downlink or R2D transmission scenario, the core network device sends downlink information (such as second information) to a first device. This second information satisfies the data packet / data volume requirements of the wireless channel between the first and second devices. The first device can send the second information to the second device, or the first device can process the second information accordingly. The information obtained from this processing at least includes the second information, and the first device sends the processed information to the second device. The downlink information or R2D message sent by the first device to the second device can satisfy the data volume requirements of the wireless channel between the first and second devices. For example, the transport block size (TB) or MAC PDU size of the downlink information or R2D message is less than or equal to the maximum TBS. As another example, in an uplink or D2R transmission scenario, the core network device sends downlink information (such as second information) to a first device. This first information contains information used for scheduling / controlling / instructing the second device to send uplink data. For example, the second information contains command data to instruct the reading of data from the second device. The first device forwards the downlink information to the second device, and the second device sends uplink information, such as the read data, to the first device according to the instructions of the downlink information. The uplink information meets the requirements of the wireless channel between the first device and the second device for data volume / data packets.

[0131] In another possible implementation, the first information is associated with the amount of data that can be transmitted between the core network device and the first device. This data amount can be understood as: a rough data amount, a desired data amount, an expected data amount, a precise data amount, a maximum data amount, or an approximate data amount, etc. For example, the first information may include a second data amount, which is the amount of data that can be transmitted between the core network device and the first device. In one understanding, when the fifth information received by the first device from the core network device does not meet the data amount requirements for wireless channel or air interface transmission between the first device and the second device, the first device feeds back the first information to the core network device to measure the amount of data that can (or is expected or suggested) be transmitted between the core network device and the first device. Alternatively, the core network device requests or triggers the first device to send the first information, and the first device feeds back the first information to the core network device to measure the amount of data that can (or is expected or suggested) be transmitted between the core network device and the first device. Or, the first device proactively feeds back the first information to the core network device to measure the amount of data that can (or is expected or suggested) be transmitted between the core network device and the first device. Optionally, the amount of data that can be transmitted between the core network device and the first device is determined based on the amount of data that can be transmitted between the first device and the second device. This possible implementation is applicable to downlink or R2D transmission scenarios.

[0132] Step 1030: The core network device sends the second information to the first device, and the first device receives the second information from the core network device. The second information is determined based on the first information.

[0133] [Downlink or R2D transmission scenarios]

[0134] In one possible implementation, the solution of this application is applied to downlink or R2D transmission scenarios. By adopting the solution of this application, it can be guaranteed that the information sent by the first device to the second device (e.g., referred to as an R2D message) meets the data volume requirements of the wireless channel or air interface transmission between the first and second devices, or the data volume that the allocated resources can transmit, such as meeting the maximum TBS requirement of the first device. R2D can be abbreviated as RD.

[0135] In one example, upon receiving the first information, the core network device can determine the quantity / data volume of the second information based on the first information. This is described as follows: the quantity / data volume of the second information is determined based on the first information. In step 1030, the core network device sends at least one piece of second information to the first device, the quantity of which can be determined based on the first information fed back by the first device. For example, the core network device can segment the information to be transmitted based on the first information fed back by the first device to obtain at least one piece of second information. Each piece of second information can be considered a segmented piece of information, and each piece of second information satisfies the requirements of the first information.

[0136] For example, the first information returned by the first device is the TBS size, which is 200 bits. The service request to be sent by the core network device is a command message, which occupies 1000 bits. The core network device can divide the command message into 5 segments, each occupying 200 bits, based on the first information. Each segment of command message can be considered an example of the second information in step 1030. That is, in this example, the core network device sends the second information to the first device 5 times, and each time the second information sent is different; these 5 sent segments of second information can form a complete command message. Optionally, the core network device can resend the second information, for example, if the transmission of the third information sent by the first device to the second device fails, the core network device can resend the second information to the first device.

[0137] This application does not impose any restrictions on the segmentation method of the core network equipment. For example, the core network equipment can simply divide complete information into multiple segments, without restricting whether each segment includes a complete header. Alternatively, when segmenting complete information, the core network equipment needs to ensure that each segment includes a complete header, and that the data portions of multiple segments can form the data portion of the complete information, etc.

[0138] In another example, upon receiving the first information, the core network device can determine the content carried / contained by the second information. For instance, the first information might be the downlink TBS size. Based on the first information (downlink TBS size), the core network device can determine at least one of the following information carried in each / every second message: device ID, length, type, or mask quantity (or length), etc. It can be understood that the second information could be a paging message in this case. For example, the core network device has four device IDs to be sent, each occupying 200 bits, for a total of 800 bits. The downlink TBS size corresponding to the first information returned by the first device is 400 bits. Therefore, the core network device can send / paging two device IDs each time, completing the entire service in two paging sessions. That is, the core network device sends two second messages, each containing two device IDs, which occupy 400 bits, satisfying the downlink TBS requirement. As another example, the core network device determines the length of the second information based on the first information (downlink TBS size). For example, the second message might be a write command. The core network device needs to write 400 bits of data. Since the downlink TBS size is 200 bits, the core network device can divide this 400-bit write data into two segments, each containing 200 bits. The core network device sends two write commands to the first device, each containing 200 bits of write data. In this case, the core network device sends two second messages to the first device; these two second messages represent two segmented write commands / write data. As another example, if the second message is a read command, the length of the read data should not exceed the amount of data that can be transmitted between the first and second devices associated with the first message.

[0139] In another example, upon receiving the first information, the core network device can determine the size of the second information based on the first information. For example, the first information might be the downlink data volume. The size of the second information could be less than or equal to the downlink data volume indicated by the first information, or the size of the second information could be less than or equal to the downlink data volume indicated by the first information minus an offset value. This offset value could be protocol-specified, predefined, or determined by the core network device.

[0140] Step 1040a: The first device sends third information to the second device. The third information is determined based on the second information. The data volume of the third information meets the requirements of the wireless channel or air interface transmission between the first device and the second device for the amount of data or the amount of data that the allocated resources can transmit.

[0141] For example, the first device generates third information based on the second information. The first device then sends the third information to the second device. For instance, the data size of the third information may be less than or equal to the maximum data size that the wireless channel between the first and second devices can transmit, which may be specified by the protocol. Alternatively, the data size of the third information may be less than or equal to the actual data size that the current wireless channel between the first and second devices can transmit.

[0142] In one possible implementation, the first information fed back by the first device to the core network device can directly indicate the data size, such as 1 to 1024 bits or 1 to 128 bytes. Alternatively, the first information can indirectly indicate the data size, for example, through a mapping relationship between an index and the data size. For instance, index = 0 corresponds to a data size of 1 byte, index = 1 corresponds to a data size of 2 bytes, and so on.

[0143] Optionally, if the first device can determine the size of the second information data based on the fifth information / Xth information, then the first information can indicate its relationship with the second information (such as a difference or multiple). For example, if the size of the second information data is M bytes / bit, then the first information can indicate that the amount of data that can be transmitted between the first and second devices is half, one-third, or one-quarter of M bytes / bit, or meets the requirement of M bytes / bit transmission, etc., or the first information can also indicate that it is N bytes / bit less (or more) than M bytes / bit, etc. Specifically, the relationship between the data amount indicated by the first information and M is not limited; the above is only an example and will not be elaborated further.

[0144] In one interpretation, the second information sent by the core network device to the first device can be a non-access stratum (NAS) protocol data unit (PDU), an upper-layer data packet, or a NAS data packet, etc. In the description of this application, the name of NAS is not limited; for example, NAS can also be called AIoT NAS, etc. Taking a NAS PDU as an example, as shown in Figure 11, in one protocol layer structure, the protocol layer structure of the first device, from top to bottom, includes: an upper layer and an access layer. For example, the upper layer includes the application layer and / or the non-access layer, etc. The access layer, from top to bottom, includes: a MAC layer and a PHY layer. Whether other protocol layers are included above the MAC layer in the access layer is not limited. The first device encapsulates the NAS PDU in the access layer, generates third information, and sends the third information to the second device. In the access layer encapsulation, the MAC layer generates a MAC PDU and transmits the MAC PDU to the PHY layer for further encapsulation. The MAC PDU can be considered a transport block (TB). When the size of the TB (i.e., TBS) exceeds the maximum TBS, the first device may be unable to send the corresponding R2D message to the second device due to insufficient TBS. The maximum TBS can be understood as the maximum TBS specified by the protocol, or the currently transmittable TBS, etc. In this application, the first device sends first information to the core network device, for example, the first information may refer to the maximum TBS. This allows the core network device to segment the information to be transmitted based on the feedback first information, ensuring that each segment meets the maximum TBS requirement and avoiding the problem of being unable to send the R2D message to the second device due to insufficient TBS.

[0145] In one example, the core network device sends a fifth piece of information to the first device. This fifth piece of information could be a service request, a paging message, or downlink data. Upon receiving the fifth piece of information, the first device sends back a first piece of information to the core network device. This first piece of information could be the TBS size, which could refer to the downlink TBS size and / or the uplink TBS size. Taking the downlink TBS size as an example, the core network device determines the size of the second piece of information based on the TBS size and sends this second piece of information to the first device. The first device generates a third piece of information based on the second piece of information and sends this third piece of information to the second device. This third piece of information satisfies the downlink TBS requirements. For example, when the second piece of information is a service request, the third piece of information could be a paging message. Or, when the second piece of information is downlink data, the third piece of information could be data, which could be a command, such as a read command or a write command.

[0146] In one possible implementation, the first information fed back by the first device is used to indicate the maximum / recommended value of the data packets that can be transmitted by the R2D message / PR2DCH. The core network device can obtain the maximum / recommended value of the data packets that can be transmitted by the R2D message / PR2DCH from the first information; based on the maximum / recommended value, it generates the size of the second information sent by the core network device to the first device.

[0147] In another possible implementation, the first information fed back by the first device is used to indicate the maximum value of information transmitted between the core network device and the first device, such as the maximum value of a NAS PDU. In this case, the second information sent by the core network device to the first device is less than or equal to the data size indicated by the first information.

[0148] In one example, the second information is information, messages, or PDUs generated by the core network; for example, the second information is a NAS PDU. The third information is an air interface message sent from the first device to the second device. When / after receiving the second information from the core network device, the first device processes the second information at the MAC and PHY layers, generates the third information, and sends it to the second device. For example, the third information = the second information + access layer information + other information. This other information is optional; for example, other information may be padding information. The access layer information may include MAC layer information (such as MAC CE or MAC header) and / or physical layer information (such as preamble or postamble). MAC CE stands for Media Access Control (MAC) Control Element (CE).

[0149] [Uplink or D2R transmission scenarios]

[0150] In uplink or D2R transmission scenarios, when the core network device receives the first information from the first device, it can generate second information based on the first information, such as scheduling information contained in the second information. This can be described as follows: the scheduling information in the second information is generated based on the first information, and the scheduling information is used to schedule the second device to send information to the first device, such as sending a D2R message, or the fourth information mentioned below. In the description of this application, "scheduling" can also be referred to as "control." For example, if a piece of information contains scheduling information, it can be replaced with: if a piece of information contains control information; furthermore, if the scheduling information is used to schedule the second device to send information to the first device, it can be replaced with: the control information is used to control the second device to send information to the first device, etc. D2R can be abbreviated as DR.

[0151] Step 1040b: The first device sends third information to the second device, and the second device receives the third information from the first device.

[0152] For example, upon receiving the second information, the first device can generate the third information based on the second information, a process described in the downlink / R2D transmission instructions. The third information may include the second information, or at least include the scheduling information from the second signaling. It is understood that the scheduling information included in the third information is used to schedule the second device to send the fourth information to the first device. Upon receiving the third information, the second device sends the fourth information to the first device according to the scheduling of the third information. Optionally, the third information may also indicate time-domain and / or frequency-domain scheduling resources. It is understood that the time-domain and / or frequency-domain scheduling resources indicated by the third information are used by the second device to send uplink data (such as the fourth information). For example, the third information may indicate that the second device sends a response uplink message (such as the fourth information) after time t, and / or, through parameters or by directly indicating frequency-domain resources (such as frequency shift information, frequency position, transmission parameters affecting frequency-domain resources, such as level repetition count, code length, or number of subcarriers). The fourth piece of information can indicate the amount of data in a D2R message, such as uplink TBS, or indicated by the MAC header or control element CE, or by the physical layer sequence.

[0153] It is understood that steps 1040a and 1040b can be two parallel steps, or steps 1040a and 1040b can be the same step. For example, the third information contains scheduling information for downlink data / paging messages and uplink data. In this case, if the second device obtains downlink data / paging messages in the third information, it is considered that the downlink / R2D scenario transmission is complete. Furthermore, the second device can also send uplink data (such as in the fourth information) according to the aforementioned scheduling data, at which point it is considered that the uplink / D2R scenario transmission is complete.

[0154] In one interpretation, the third information can be a paging message or a segment of a paging message. Alternatively, the third information can be downlink data or R2D data, such as command, lock, disable, etc.

[0155] Step 1050b: Random access procedure.

[0156] The second device performs random access and connects to the first device. This random access can be contention-based or contention-free. Alternatively, it can be a four-step random access or a two-step random access, without limitation. Step 1050b is optional; for example, the second device may have already completed random access and connected to the first device before executing the procedures of this application. Alternatively, the first device may indicate resources for sending the fourth information to the second device, in which case the second device may not need to execute the random access procedure in step 1050b, and the second device can directly send uplink data (such as the fourth information).

[0157] In one possible implementation, the core network device can indicate the type of random access to a first device (reader). Optionally, the core network device can determine the type of random access based on first information. Optionally, the first device indicates or notifies a second device of the type of random access. The second device performs the corresponding type of random access based on the indication or notification from the first device. It is understood that the above-described scheme of the core device indicating the type of random access to the first device can be implemented alone or in combination with other schemes provided in this application, without limitation. For example, the random access type includes at least one of the following:

[0158] 1-step random access / 1-step contention-based random access (CBRA);

[0159] 2-step random access / 2-step contention-based random access resolution (2-step(CB)RA);

[0160] 3-step random access / 3-step contention-based random access resolution (3-step(CB)RA);

[0161] 4-step random access / 4-step contention-based random access resolution (4-step(CB)RA);

[0162] 5. Contention-free random access (CFRA) solution.

[0163] For example:

[0164] A 1-step CBRA can be understood as follows: During / after an access occasion, the second device sends message 1 (msg1), which may contain a random number, device ID, and / or upper layer data. The second device may then choose not to receive message 2 (msg2). msg2 can be used to indicate successful contention resolution, for example, by carrying a contention resolution flag.

[0165] The 2-step CBRA can be understood as follows: During / after an access occasion, the second device sends message 1 (msg1). Then, the second device receives message 2 (msg2).

[0166] The 3-step CBRA can be understood as follows: During / after an access occasion, the second device sends message 1, receives message 2 (msg2), and then sends message 3 (msg3). Message 3 carries the device ID and / or upper layer data. The second device does not need to receive message 4 (msg4). Message 4 is used to indicate whether message 3 was successfully or failed to be transmitted.

[0167] The 4-step CBRA can be understood as follows: During / after an access occasion, the second device sends message 1, the second device receives message 2 (msg2), then the second device sends message 3 (msg3), and the second device receives message 4 (msg4).

[0168] CFRA can be understood as follows: During or after an access occasion, the second device does not need to send message 1 for contention resolution; it can directly send the device ID and / or upper layer data.

[0169] Step 1060b: The second device sends the fourth information to the first device, and the first device receives the fourth information from the second device. The amount of data in the fourth information meets the data volume requirements of the wireless channel between the first device and the second device.

[0170] For example, the fourth information could be upstream data or a response to different commands. It can be understood that the fourth information is scheduled by the third information, or described as the fourth information being determined based on the third information. For instance, if the third information sent by the first device to the second device is a read command, then the first device can determine the content of the fourth information based on information such as the storage location and / or the length of data to be read contained / indicated in the third information.

[0171] In one example, the first information fed back by the first device to the core network device may be the maximum / recommended value of the data packets that can be transmitted via D2R messages or PD2RCH. The core network device can determine the size of the fourth information that it expects the second device to send to the first device based on this maximum or recommended value. Further, based on the expected size of the fourth information, the corresponding second information is determined, such as scheduling information within the second information. The core network device sends the second information to the first device, and the first device generates third information based on the second information, and sends the third information to the second device. The third information contains the second information, or at least the scheduling information within the second information. The second device, based on the scheduling of the third information, sends the fourth information to the first device, which satisfies the maximum or recommended value fed back by the first information.

[0172] In another example, the core network device can determine the data size / length / content of the fourth information based on the first information fed back by the first device. For example, the first information fed back by the first device to the core network device can be the uplink TBS. The core network device determines the size of the data to be read each time based on the uplink TBS. For example, if the core network device wants to read 400 bits of data and the uplink TBS size is 200 bits, then the core network device reads 200 bits of data each time, reading the complete data in two separate reads. In some descriptions, the uplink TBS may also be called the uplink scheduling TBS. In the above example, it can be considered that the core network device sends the second information twice to the first device; these two second messages can be considered two read commands, each reading 200 bits of data. Upon receiving each second message, the first device generates a third message based on the second message; this third message can be considered a read command. Similarly, the first device sends the third message twice to the second device, i.e., two read commands. Upon receiving each read command, the second device reports 200 bits of data to the first device; through two read commands, it reports 400 bits of data to the first device. This can be described as follows: based on the uplink TBS (Transmission Block System) feedback from the first information, the size / length / content of the data read in each read command can be determined.

[0173] In one possible implementation, the second, third, or fourth information includes first indication information, which indicates the quantity of information containing the first indication information. For example, in a downlink / R2D transmission scenario, the core network device can segment the information to be transmitted, generating at least one second piece of information. This second information can be considered a portion of the segmented transmission. For instance, if the complete information is divided into N segments, each segment corresponding to one second piece of information, where N is an integer greater than 2, then one or more of the aforementioned N second pieces of information can carry the first indication information, which indicates the size of N.

[0174] In another possible implementation, the second, third, or fourth information includes second indication information, which indicates whether the information containing the second indication information is to be transmitted in segments. For example, in a downlink / R2D transmission scenario: when the core network device segments the information to be transmitted, the second indication information included in the second information can be a first value, which indicates segmented transmission, such as a first value of 1. Alternatively, when the core network device does not segment the information to be transmitted, the second indication information included in the second information can be a second value, which indicates unsegmented transmission, such as a second value of 0; or, in the unsegmented scenario, the second information may not contain the second indication information.

[0175] In another possible implementation, the second, third, or fourth information contains a third indication information, which is used to indicate whether the information containing the third indication information has been transmitted successfully. For example, in a downlink / R2D transmission scenario: the core network device divides the complete data packet into N segments and generates N corresponding second information segments. The third indication information contained in the first N-1 second information segments is used to indicate that the transmission is not complete; or, the first N-1 second information segments do not contain a third indication information. The third indication information contained in the last of the N second information segments is used to indicate that the transmission is complete.

[0176] The advantage of the above operation is that it notifies the first or second device that the above multiple pieces of information (such as N pieces of information) are for a single service, thus preventing the first or second device from prematurely ending the service or responding to the transmission of other services.

[0177] In another possible implementation, the second, third, or fourth information includes a fourth indication information. This fourth indication information indicates that multiple pieces of information belong to the same service, the same complete information, the same receiving end (such as the second device), or the same packet. For example, the name of the fourth indication information can be the access stratum (AS ID) or a new identifier. Taking the example of each of the multiple third pieces of information sent from the first device to the second device carrying / containing the fourth indication information: In one scenario, the core network device divides a complete piece of information into two segments. The first device can then acquire / generate two pieces of third information, referred to as information 1 and information 2, respectively. The first device sends segment 1 of information 1 in time slot 1. Due to certain reasons, such as insufficient power of the first device, the first device sends segment 2 of information 2 in time slot 2. Both information 1 and information 2 contain the aforementioned fourth indication information. When the second device receives information 1 and information 2 in different time slots, it can associate information 1 and information 2 according to the fourth indication information. For example, it can consider information 1 and information 2 to belong to a complete message, or information 1 and information 2 to correspond to the same receiving end (such as the second device). It is understood that in downlink or R2D transmission scenarios, the aforementioned first indication information, second indication information, third indication information, or fourth indication information can be generated by the core network or by the reader / writer, without restriction.

[0178] Taking the fourth indication information as the AS ID as an example. The AS ID can be generated by a second device (such as a device), for example, a random number sent during random access. Alternatively, it can be generated by a first device (such as a reader). Optionally, the first device can assign the generated AS ID to the second device, for example, by carrying the AS ID in the ACK, or by combining both (for example, if the second device (device) generates it by default, then if the first device (reader) assigns it, the AS ID assigned by the first device (reader) will replace the AS ID generated by the second device (device)). Or, the logical node RIC in the access network device can also generate the AS ID.

[0179] In the schematic diagram of Figure 10, the core network device and the first device can communicate directly; for example, the first device is an access network device. As shown in Figure 12, this application also provides a process, which differs from the process in Figure 10 in that the core network device communicates with the first device through the access network device, such as when the first device is a terminal. The difference lies in the uplink transmission: during the process of the first device sending first information to the core network device, the first device sends the first information to the core network device through the access network device. For example, in step 1020a: the first device sends the first information to the access network device; and in step 1020b: the access network device sends the first information to the core network device. In one possible implementation, the first information in step 1020a can be transmitted via RRC messages / MAC messages. If the first information is carried / included in the RRC messages / MAC messages, the access network device can process the RRC messages / MAC messages accordingly to obtain the first information, and in step 1020b, the access network device sends the first information to the core network device. The downlink transmission process is similar. The core network device sends second or fifth information to the access network device, which can then encapsulate the second or fifth information in an RRC / MAC message and send it to the first device. Alternatively, the access network device can forward / transmit messages between the core network device and the first device without interpreting the content. For example, the core network device and the first device can transmit corresponding information through NAS messages on the control plane or PDU sessions on the user plane.

[0180] In the description of this application, the first information can be carried in an NGAP message, or an A-IoT NGAP message, or XXAP, where XX is any name. For example, the first information can be an NGAP message, or the first information can be carried in an NGAP message. Optionally, steps 1020a and 1020b can be implemented using different messages, that is, the first information is carried in different messages in 1020a and 1020b, such as an NGAGP message or an RRC / MAC message, respectively. Optionally, the fifth information transmitted by 1010a and 1010b can be implemented using different messages, such as corresponding to an NGAP message and an RRC / MAC message, respectively. Optionally, the second information transmitted by 1030a and 1030b can be implemented using different messages, such as corresponding to an NGAP message and an RRC / MAC message, respectively.

[0181] Through the above design, the first device, acting as a reader / writer, feeds back first information to the core network device: In the downlink / R2D scenario, the core network device can generate second information that meets the data volume requirements of PR2DCH based on the first information, thereby enabling the third information generated by the first device based on the second information to meet the data volume requirements of PR2DCH and avoid the problem of insufficient TBS; In the uplink / D2R scenario, the core network device determines the scheduling information carried in the second information based on the first information, thereby enabling the scheduling information to schedule the fourth information sent by the second device to meet the data volume requirements of PD2RCH.

[0182] This application also provides a communication method and apparatus, the principle of which is: when multiple pieces of information received by a second device are not continuous, the second device discards all of the information. Compared with the current solution, in the event of a transmission anomaly, the receiving end (such as the second device) sends uplink feedback (such as UL NACK) to the sending end (such as the first device), which can reduce the additional / temporary buffer overhead of the device in abnormal scenarios. Since temporary buffering has a significant impact on device power consumption, discarding multiple pieces of information in advance can reduce temporary buffering, thereby reducing the impact of temporary buffering on device power consumption. NACK stands for Negative Acknowledgment.

[0183] Figure 13 shows a flowchart of a communication method, including:

[0184] Step 1310: The core network device sends information to the first device, and the first device receives the information from the core network device.

[0185] This information can be a service request, a paging message, or downlink data. In this process description, "information" can be replaced with names such as message, signal, or data. The descriptions of the core network device, the first device, and the second device can be found in the process description in Figure 10 above. Additionally, the first device is a device that implements the reader / writer function, and the second device is a device that implements the device, AIoT device, or tag function. If the first device is an access network device, the core network device can directly send information to the first device (e.g., the access network device). Alternatively, the first device is a terminal, and the core network device sends information to the terminal through the access network device. Step 1310 is optional. For example, when the first device receives information sent by the core network device, the first device executes step 1320 to send multiple messages to the second device. Alternatively, the first device can directly send multiple messages to the second device.

[0186] In one possible implementation, the first device can segment the information to be transmitted, obtaining multiple pieces of information. For example, the first device can segment the information to be transmitted according to the TBS (Transmission Block Size), obtaining multiple pieces of information, each of which is less than or equal to the TBS. In this case, the multiple pieces of information can be considered as segmented information. Another example is that the multiple pieces of information contain corresponding sequence numbers (SNs). The last piece of information contains an end marker. For instance, the first device obtains three pieces of information through segmentation. The first piece of information contains (SN=1), the second piece of information contains (SN=2), and the third piece of information contains (SN=3, the end marker). For the receiving end (such as the second device), upon receiving the end marker, it is considered that the multiple signals transmitted in segments have been successfully received. The multiple pieces of information can be merged to obtain complete information, which is then delivered to the upper layer for processing. Of course, this application focuses on the processing of multiple pieces of information received by the second device when they are discontinuous, such as when the SNs of the multiple pieces of information are discontinuous.

[0187] Step 1320: The first device sends multiple messages to the second device, and the second device receives multiple messages from the first device.

[0188] Step 1330: When multiple pieces of information are discontinuous, the second device discards multiple pieces of information and / or stops receiving other information. Optionally, the other information can be considered as segmented other information. This other information and the previously received multiple pieces of information may belong to the same data, which is complete data that is not segmented.

[0189] In the description of this application, "multiple pieces of information are discontinuous" in step 1330 can specifically mean that two adjacent pieces of information received by the second device are discontinuous. For example, multiple pieces of information include first information and second information, and the first information and the second information are received adjacently. If the first information and the second information are discontinuous, then the multiple pieces of information are considered discontinuous. Optionally, the sequence number SN can be used to measure whether multiple pieces of information are continuous, such as multiple pieces of information being discontinuous including: the sequence numbers contained in the multiple pieces of information are discontinuous. For example, the SN contained in the first information is discontinuous with the SN contained in the second information. For example, the SN contained in the first information is 1, and the SN contained in the second information is 3, etc.

[0190] For example, a first device can sequentially send multiple messages to a second device, and the second device can sequentially receive these multiple messages. For instance, these multiple messages may be N messages, where N is an integer greater than 1. The second device receives the first message from the N messages and saves it. The second device receives the second message from the N messages and determines whether the first and second messages are consecutive, such as whether their serial numbers (SN) are consecutive. If they are consecutive, the second message is saved, and the third message is received. If they are not consecutive, the first and second messages are discarded. Optionally, the first device may stop receiving other messages from the N messages. In one description, the multiple messages mentioned above are segmented transmissions. The second device stopping receiving other messages from the N messages can be described as: the second device stops receiving other messages from that segment.

[0191] For example, each of the multiple pieces of information above may contain a serial number (SN). Specifically, the SN may be located at the access layer of each piece of information, such as the MAC header, or the SN may be located at a layer above the access layer of each piece of information (such as the NAS layer and / or the application layer). Alternatively, a specific sequence contained in each piece of information may be used to indicate different SNs. For example, different SNs may be distinguished by a specific sequence contained in the physical layer of each piece of information, such as a preamble, postamble, or midamble sequence.

[0192] For example, if the second device successfully receives information 1, which includes serial number 1, the second device saves serial number 1. If the second device successfully receives information 2, which includes serial number 2, and if serial number 2 is a consecutive serial number with serial number 1 (e.g., serial number 1 = 1, serial number 2 = 2), the second device saves serial number 2. Optionally, the second device discards / releases serial number 1. If the second device successfully receives information 4, which includes serial number 4, and serial number 4 is not consecutive with the currently saved serial number or any other serial number (e.g., serial number 4 is not consecutive with currently saved serial numbers 2 or 2, 1), the second device discards information 1, information 2, and information 4. Optionally, the second device stops receiving / responding to other segmented information.

[0193] Optionally, the second device can process each segmented information simultaneously upon successful reception, or it can merge all received information and process them together; there is no restriction. Optionally, if the second device receives and processes segmented information simultaneously, it can discard the processed information. If the second device receives a non-contiguous sequence number, it will no longer respond to or receive other segmented information.

[0194] Optionally, when / after the first device discards the multiple first messages: the second device may wait for an instruction from the network (such as the first device). The second device performs corresponding operations based on the network's instruction, such as re-accessing or re-receiving information, depending on the network-side implementation. For example, the network side, such as the first device, may send a first instruction to the second device, which the second device receives. The first instruction may be named a re-access indication. This first indication can be carried in retransmitted paging messages or other downlink messages without restriction. The second device may re-access the first device based on the first indication, in which case the first indication instructs the second device to re-access the first device. Alternatively, the second device may re-receive multiple messages based on the first indication, in which case the first indication instructs the second device to re-receive multiple messages. Alternatively, the second device may proactively report the reception failure to the first device. Upon receiving the feedback from the second device, the first device may retransmit the failed reception information or retransmit all the information, depending on the first device's implementation. For example, the second device may send an acknowledgment message to the first device, indicating that at least one of the multiple messages failed to be received. For example, the response message can be NACK, or any other name, without restriction. Optionally, the response message may include the sequence number of the failed reception message. For example, SN=2.

[0195] In one possible implementation, at least one of the multiple pieces of information includes first indication information, which indicates the quantity of the multiple pieces of information. At least one of the multiple pieces of information includes second indication information, which indicates that the multiple pieces of information will be transmitted in segments. At least one of the multiple pieces of information includes third indication information, which indicates whether the service transmission corresponding to the multiple pieces of information is complete or incomplete. At least one of the multiple pieces of information includes fourth indication information, which indicates whether the multiple pieces of information belong to a single service, are the same complete piece of information, belong to the same receiving end (such as a second device), or belong to the same packet, etc.

[0196] Taking a paging message, in which multiple messages are transmitted in segments, and used to page or select a second device, as an example, Figure 14 provides a flowchart of a communication method. It is understood that the flowchart in Figure 14 can be an example of the flowchart in Figure 13; the flowchart in Figure 14 includes:

[0197] Step 1410: The core network device sends a service request to the first device, and the first device receives the service request from the core network device.

[0198] Step 1420: The first device segments the paging message according to the TBS to obtain a paging message in 3 segments.

[0199] For example, a paging message consisting of three segments includes a serial number (SN), and the last segment contains an end marker. This three-segment paging message can be represented / described as: Paging Message (SN=1), Paging Message (SN=2), Paging Message (SN=3, End Marker), where the end marker can be called "end marker".

[0200] In the description of this application, SN is used as one implementation method to determine whether two adjacent / continuously received information are continuous or whether other information was missed. Other methods can also be used to determine / identify / judge whether multiple pieces of information received by the second device are continuous. For example, the continuity of information received by the second device can be determined by the physical layer sequence, or by using information related to the previous information indicating the next information, such as an identifier or sequence, to determine whether the next received information is continuous with the previous information. Optionally, two pieces of information received adjacently or consecutively by the second device can be understood as: the second device did not receive other information or did not successfully receive / parse (e.g., successfully descramble) other information between the two received pieces of information.

[0201] Step 1430: The first device sends a three-segment paging message to the second device, and the second device receives the three-segment paging message from the first device.

[0202] As shown in the schematic diagram in Figure 14, the second device successfully received paging messages (SN=1) and (SN=3, end marker). The second device did not receive / failed to receive paging message (SN=2). When the second device received paging message (SN=3, end marker), it found that the SN of this paging message (SN=3, end marker) was not continuous with the previously received paging message (SN=1). Therefore, the second device can discard the two successfully received paging messages, i.e., discard paging message (SN=1) and paging message (SN=3, end marker).

[0203] In one possible implementation, the second device can receive segmented paging messages sequentially. For example, the second device can submit each segmented paging message received to the upper layer for processing, where the upper layer determines whether the serial numbers (SNs) are continuous. Alternatively, the second device can determine whether the SNs are continuous each time it receives a segmented paging message; if they are continuous, it submits the message to the upper layer for processing; if the SNs are not continuous, it stops receiving other segmented paging messages and does not respond to subsequent segmented paging messages.

[0204] As is understandable, the process described in Figure 14 above focuses on the process of discarding multiple segments of paging messages when the serial numbers (SNs) of the multiple segments of paging messages received by the second device are discontinuous.

[0205] For scenarios involving segmented paging message transmission, this application embodiment also provides a solution: when the second device receives a segmented paging message, it determines whether the identification information contained in that segmented paging message is associated with the second device; if associated, it responds to that segmented paging message, performs random access, and the second device may no longer receive / respond to subsequent segmented paging messages. Optionally, the identification information contained in the paging message can be a device identifier, a mask, or a group identifier, etc., without limitation.

[0206] In a specific example, a complete paging message contains six device identifiers. The first device divides this complete paging message into six segments, each containing one device identifier. It can be understood that the first device broadcasts the paging message. When the second device receives a paging message (which is a segmented paging message), it determines whether the identifiers contained in the segmented paging message match its own device identifier. If they match, the device responds to the paging message and performs random access. Other segmented paging messages are no longer received or responded to.

[0207] Of course, the above scheme may have limitations. Before random access, the second device can obtain the resource configuration, transmission parameters, and other configurations related to random access. This is because the second device needs to perform random access based on the aforementioned resource configuration, transmission parameters, and other configurations. For example, it could be specified that the aforementioned random access-related configurations and / or parameters are carried in the first segment of the paging message; or, in each segment of the paging message; or, in the last segment of the paging message, etc., without restriction. In short, when the second device determines that it has been paged (i.e., the device identifier contained in the paging message is associated with the second device), it needs to further parse / obtain the aforementioned random access-related configurations / parameters. It is understandable that if the aforementioned random access-related configurations / parameters are carried in the paging messages transmitted in subsequent segments, the second device needs to continue receiving the corresponding segment paging messages.

[0208] For scenarios involving segmented paging message transmission, this application provides another solution, primarily applicable to situations where the second device successfully receives multiple segmented paging messages. For example, each time the second device receives a segmented paging message, it caches / saves that segment. When the transmission of multiple segmented paging messages is complete / successful—for instance, when the second device receives a paging message containing an end marker, or when the received paging message contains a transmission completion marker—the second device can submit the received multiple segmented paging messages to an upper layer (such as the non-access layer) for processing. For example, the second device's MAC layer can receive multiple segmented paging messages and merge them into a single NAS data packet (such as a PDU) before submitting it to the upper layer for processing.

[0209] With the above design, in the event of a transmission anomaly, such as when the second device receives multiple segments of paging messages that are not continuous, the second device can directly discard the multiple segments of paging messages that are experiencing the transmission anomaly, thereby reducing the additional / temporary buffering overhead of the second device and reducing the impact of temporary buffering on device power consumption.

[0210] As shown in Figure 15, this application provides another ORAN architecture, where the access network equipment includes logical nodes such as RU, DU, CU, and RIC. RIC stands for Radio Access Network Intelligent Controller (RIC). The RIC can include near real-time RIC and / or non-real-time RIC. The CU can be further divided into CU-CP and CU-UP. The RU can connect / communicate with the terminal via the air interface. In the scheme of this application, when the access network equipment implements the function of a reader / writer, that is, when the first device is an access network equipment: the CU and / or DU can send corresponding information to the second device. The CU can receive corresponding information from the core network equipment. Optionally, the RIC can generate the first, second, third, or fourth indication information mentioned above, specifically, it can be generated by a near real-time RIC or a non-real-time RIC, without limitation.

[0211] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of the interaction between the first device, the second device, and the core network device. To implement the functions of the methods provided by the embodiments of this application, the first device, the second device, or the core network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the design constraints of the specific application of the technical solution.

[0212] Based on the same conceptual framework as the above-described method embodiments, Figures 16 and 17 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can implement the functions of the first device, second device, or core network device in the above-described method embodiments, and therefore may achieve the beneficial effects of the above-described method embodiments. In the embodiments of this application, the communication device may be a first device, a second device, or a core network device, or a unit, module, or component (such as a chip, chip system, circuit, processor, or others) applied in the first device, second device, or core network device. In the following description, the term "unit" will be used as an example. For example, in the following description, the communication device includes a processing unit and a transceiver unit as an example. The processing unit in the following description can also be replaced by: a processing module or a processing component, etc. The transceiver unit can also be replaced by: a transceiver unit or a transceiver component. For example, a transceiver component may refer to a communication module.

[0213] As shown in Figure 16, the communication device 1600 includes a processing unit 1610 and a transceiver unit 1620.

[0214] Alternatively, the transceiver unit 1620 may also be referred to as an output unit, an interface unit, or a communication unit, etc. In one possible implementation, the transceiver unit 1620 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc.

[0215] When the communication device 1600 is used to implement the function of the first device in FIG10 or FIG12, specifically: the transceiver unit 1620 is used to send first information to the core network device, the first information being associated with the amount of data that can be transmitted between the first device and the second device, or the first information being associated with the amount of data that can be transmitted between the core network device and the first device; the transceiver unit 1620 is also used to receive second information from the core network device, the second information being determined based on the first information.

[0216] When the communication device 1600 is used to implement the functions of the core network device in Figure 10 or Figure 12, specifically: the transceiver unit 1620 is used to receive first information from the first device, the first information being associated with the amount of data that can be transmitted between the first device and the second device, or the first information being associated with the amount of data that can be transmitted between the core network device and the first device; the transceiver unit 1620 is also used to send second information to the first device, the second information being determined based on the first information.

[0217] When the communication device 1600 is used to implement the function of the second device in FIG13 or FIG14, specifically: the transceiver unit 1620 is used to receive multiple messages from the first device; the processing unit 1610 is used to discard the multiple messages when they are discontinuous.

[0218] For details on the implementation of the transceiver unit 1620 and the processing unit 1610, please refer to the description of the method embodiments above.

[0219] It is understood that the division of units in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. In addition, the functional units in this application embodiment can be integrated into a physical device (e.g., in a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional module, etc.

[0220] As shown in Figure 17, the communication device 1700 includes a processor 1710 and an interface circuit 1720. The processor 1710 and the interface circuit 1720 are coupled to each other. It is understood that the interface circuit 1720 can be a transceiver or an input / output interface. Optionally, the communication device 1700 may also include a memory 1730 for storing instructions executed by the processor 1710, or storing input data required by the processor 1710 to execute instructions, or storing data generated after the processor 1710 executes instructions.

[0221] When the communication device 1700 is used to implement the method shown in FIG10, FIG12, FIG13 or FIG14, the processor 1710 is used to implement the function of the processing unit 1610, and the interface circuit 1720 is used to implement the function of the transceiver unit 1620.

[0222] When the aforementioned communication device is a module applied to the first device, the module implements the functions of the first device in the above method embodiments. Taking the first device as an access network device as an example, the module receives information from other modules (such as radio frequency modules or antennas) in the access network device, which is information sent from the core network device to the access network device; or, the module sends information to other modules (such as radio frequency modules or antennas) in the access network device, which is information sent from the access network device to the second device. The module here can be the baseband chip of the base station, or it can be a DU or other modules. The DU here can be a DU under the open radio access network (O-RAN) architecture.

[0223] When the aforementioned communication device is a chip applied to the second device, the second device chip implements the functions of the second device in the above method embodiments. The second device chip receives information from other modules (such as radio frequency modules or antennas) in the second device, which is information sent from the first device to the second device; or, the second device chip sends information to other modules (such as radio frequency modules or antennas) in the second device, which is information sent from the second device to the first device.

[0224] When the aforementioned communication device is a module applied to a core network device, the module implements the functions of the core network device in the above method embodiments. The module receives information from other modules within the core network device, the information being sent to the core network device by the first device; or, the module sends information to other modules within the core network device, the information being sent to the first device by the core network device.

[0225] This application also provides a communication device, which includes a processor for implementing the functions of the first device or core network device in FIG10 or FIG12, or the functions of the second device in FIG13 or FIG14. Optionally, the communication device further includes a memory, with the processor coupled to the memory. The processor executes computer programs or instructions stored in the memory to implement the functions of the first device or core network device in FIG10 or FIG12, or the functions of the second device in FIG13 or FIG14. Optionally, the communication device may be a chip or a chip system.

[0226] This application embodiment also provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor is used to implement the functions of the first device or core network device in FIG10 or FIG12, or the functions of the second device in FIG13 or FIG14, through logic circuits or execution code instructions.

[0227] This application also provides a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program code, etc. These instructions, when executed on a computer, cause the computer to perform the functions of the first device or core network device in Figure 10 or Figure 12, or the functions of the second device in Figure 13 or Figure 14.

[0228] This application also provides a computer program product, including a computer program or instructions, which, when run on a computer, implement the functions of the first device or core network device in FIG10 or FIG12, or the functions of the second device in FIG13 or FIG14.

[0229] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0230] The memory in the embodiments of this application may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), register, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art.

[0231] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an ASIC.

[0232] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0233] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method, characterized in that, The method is applied to a first device, or a chip in the first device, and includes: Send first information to the core network device, wherein the first information is associated with the amount of data that can be transmitted between the first device and the second device, or the first information is associated with the amount of data that can be transmitted between the core network device and the first device; Receive second information from the core network device, the second information being determined based on the first information.

2. The method as described in claim 1, characterized in that, When the first information is associated with the amount of data that can be transmitted between the first device and the second device, the first information includes at least one of the following: first data amount, first transport block size (TBS), or first channel quality information; Wherein, the first data volume is the amount of data that can be transmitted between the first device and the second device, the first TBS is the TBS that can be transmitted between the first device and the second device, and the first channel quality information is the quality information of the wireless channel between the first device and the second device.

3. The method as described in claim 1, characterized in that, When the first information is associated with the amount of data that can be transmitted between the core network device and the first device, the first information includes: a second amount of data, where the second amount of data is the amount of data that can be transmitted between the core network device and the first device.

4. The method according to any one of claims 1 to 3, characterized in that, The amount of data in the second information is determined based on the first information.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: A third message is sent to the second device, the third message being determined based on the second message, and the data volume of the third message meeting the data volume requirements of the wireless channel between the first device and the second device.

6. The method as described in claim 1 or 2, characterized in that, The scheduling information included in the second information is determined based on the first information, and the scheduling information is used to schedule the second device to send information to the first device.

7. The method as described in claim 1, 2, or 6, characterized in that, The method further includes: Send a third message to the second device, the third message being determined based on the second message, the third message including scheduling information for scheduling the second device to send a fourth message; The system receives fourth information from the second device, the amount of which satisfies the data volume requirements of the wireless channel between the first device and the second device.

8. The method according to any one of claims 1 to 7, characterized in that, The second information, the third information, or the fourth information includes first indication information, which is used to indicate the quantity of information containing the first indication information.

9. The method according to any one of claims 1 to 8, characterized in that, The second information, the third information, or the fourth information includes second indication information, which is used to indicate whether the information containing the second indication information is transmitted in segments.

10. The method according to any one of claims 1 to 9, characterized in that, The second information, the third information, or the fourth information includes third indication information, which is used to indicate whether the information containing the third indication information has been transmitted.

11. The method according to any one of claims 1 to 10, characterized in that, Before sending the first information to the core network equipment, the method further includes: Receive the fifth message from the core network device; The fifth piece of information does not meet the data volume requirements of the wireless channel between the first device and the second device.

12. A communication method, characterized in that, The method is applied to core network equipment, or a chip in the core network equipment, and includes: Receive first information from a first device, the first information being associated with the amount of data that can be transmitted between the first device and the second device, or the first information being associated with the amount of data that can be transmitted between the core network device and the first device; Send a second message to the first device, the second message being determined based on the first message.

13. The method as described in claim 12, characterized in that, When the first information is associated with the amount of data that can be transmitted between the first device and the second device, the first information includes at least one of the following: first data amount, first transport block size (TBS), or first channel quality information; Wherein, the first data volume is the amount of data that can be transmitted between the first device and the second device, the first TBS is the TBS that can be transmitted between the first device and the second device, and the first channel quality information is the quality information of the wireless channel between the first device and the second device.

14. The method as described in claim 12, characterized in that, When the first information is associated with the amount of data that can be transmitted between the core network device and the first device, the first information includes: a second amount of data, where the second amount of data is the amount of data that can be transmitted between the core network device and the first device.

15. The method according to any one of claims 12 to 14, characterized in that, The amount of data in the second information is determined based on the first information.

16. The method as described in claim 12 or 13, characterized in that, The scheduling information included in the second information is determined based on the first information, and the scheduling information is used to schedule the second device to send information to the first device.

17. The method according to any one of claims 12 to 16, characterized in that, The second information includes first indication information, which is used to indicate the quantity of the second information.

18. The method according to any one of claims 12 to 17, characterized in that, The second information includes a second indication information, which is used to indicate whether the second information is transmitted in segments.

19. The method according to any one of claims 12 to 18, characterized in that, The second information includes a third indication information, which is used to indicate whether the transmission of the second information is complete.

20. The method according to any one of claims 12 to 19, characterized in that, Before receiving the first information from the first device, the method further includes: A fifth message is sent to the first device, which does not meet the data volume requirements of the wireless channel between the first device and the second device.

21. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 20.

22. A communication device, characterized in that, Includes a processor configured to cause the communication device to perform the method as claimed in any one of claims 1 to 11, or the method as claimed in any one of claims 12 to 20.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed, cause the communication device to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 20.

24. A computer program product, characterized in that, The computer program product includes instructions that, when executed, cause the communication device to perform the method as described in any one of claims 1 to 11, or to perform the method as described in any one of claims 12 to 20.

Images