Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. The method can include: a first device determining first information; and the first device sending the first information, which can indicate a cache-related capability of the first device, the cache-related capability being associated with a first function of the first device. In the method, the first device can send the first information indicating the cache-related capability of the first device, and the cache-related capability can be associated with the first function of the first device. Therefore, based on the first information, the network side can learn the cache-related capability of the first device, which helps to better control the first function of the first device.

Description

Technical Field

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

[0002] In certain communication scenarios, different communication devices within a communication system possess varying capabilities, which in turn affect the functionality of those devices. Therefore, how to better manage and control the functionality of communication devices remains a challenge. Summary of the Invention

[0003] This application provides a communication method and a communication device. The communication device can send first information indicating its own cached capabilities to ensure that the network side understands its capabilities, which helps the network side to better manage the function implementation of the first device.

[0004] Firstly, a communication method is provided, which can be applied to a first device.

[0005] The method may include: a first device determining first information; the first device sending the first information, the first information indicating the cache-related capabilities of the first device, the cache-related capabilities being associated with a first function of the first device.

[0006] In the above scheme, the first device can send first information indicating its own cache-related capabilities, and these cache-related capabilities can be associated with the first function of the first device. Therefore, based on the first information, the network side can understand the cache-related capabilities of the first device, which helps the network side to better manage the implementation of the first function.

[0007] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0008] By instructing the second device on one or more cache-related capabilities, the second device can more accurately manage the various functions of the first device.

[0009] In some possible implementations, the method may further include: receiving a response to first information from a second device, the response to the first information indicating whether the first function is enabled or disabled.

[0010] The response based on the first information helps the first device to determine whether the first function is turned on or off.

[0011] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0012] Instructions from the second device to enable or disable one or more functions of the first device help reduce the complexity of the first device's workflow and support scenarios where low-capacity and high-capacity first devices coexist.

[0013] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0014] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0015] Based on this, it helps the first device to determine whether to turn the first function on or off.

[0016] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0017] Optionally, the first capability requirement may refer to one or more of the following requirements for cache-related capabilities: size; state; type.

[0018] Based on the first condition, it helps to save on the cost of the first device.

[0019] Secondly, a communication method is provided that can be applied to a second device.

[0020] The method may include: a second device receiving first information, the first information indicating the cache-related capabilities of the first device, the cache-related capabilities being associated with a first function of the first device; and the second device determining the cache-related capabilities of the first device based on the first information.

[0021] In the above scheme, the second device can determine the cache-related capabilities of the first device based on the first information sent by the first device, and the cache-related capabilities can be associated with the first function of the first device. Therefore, based on the first information, the network side can understand the cache-related capabilities of the first device, which helps the network side to better manage the implementation of the first function.

[0022] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0023] By instructing the second device on one or more cache-related capabilities, the second device can more accurately manage the various functions of the first device.

[0024] In some possible implementations, the method may further include: a response from the second device to send first information, the response to the first information indicating whether the first function is enabled or disabled.

[0025] The response based on the first information helps the first device to determine whether the first function is turned on or off.

[0026] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0027] Instructions from the second device to enable or disable one or more functions of the first device help reduce the complexity of the first device's workflow and support scenarios where low-capacity and high-capacity first devices coexist.

[0028] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0029] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0030] Based on this, it helps the first device to determine whether to turn the first function on or off.

[0031] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0032] Optionally, the first capability requirement may refer to one or more of the following requirements for cache-related capabilities: size; state; type.

[0033] Based on the first condition, it helps to save on the cost of the first device.

[0034] Thirdly, a communication method is provided, which can be applied to a communication system including a first device, a second device, and a third device.

[0035] The method may include: a first device sending first information to a second device; the second device sending a response to the first information to the first device, the response indicating whether a first function is enabled or disabled;

[0036] Alternatively, the method may include: a third device sending first information to a second device; the second device sending second information to the first device, the second information indicating whether the first function is enabled or disabled;

[0037] The first information may indicate the cache-related capabilities of the first device, and the cache-related capabilities may be associated with the first function of the first device.

[0038] In the above scheme, the first device can send first information indicating its own cache-related capabilities to the second device, or the third device can send first information indicating the first device's cache-related capabilities to the second device. Furthermore, the cache-related capabilities of the first device can be associated with its first function. Therefore, based on the first information, the network side can understand the cache-related capabilities of the first device, which helps the network side better manage the implementation of the first function.

[0039] In some possible implementations, the activation or deactivation of the first function can be determined by the second device;

[0040] And / or, before the third device instructs the second device to enable or disable the first function, and before the second device sends a response or second information to the first device, the method may further include: the third device sending third information to the second device, the third information indicating whether the second function is enabled or disabled.

[0041] Based on the instructions from the third device, the second device can determine the first function.

[0042] In some possible implementations, the second function may differ from the first function determined by the second device.

[0043] Based on this, it helps the second and third devices to determine the first function according to their respective needs.

[0044] In some possible implementations, the first information sent by the third device may be associated with one or more of the following: device group ID, which may indicate the ID of the device group to which the first device belongs; device mask, which may be used to match one or more first devices; device ID, which may indicate the ID of the first device; deployment area information, which may indicate the deployment area of ​​the first device; and deployment time information, which may indicate the deployment time of the first device.

[0045] Based on this, it helps the third device to clearly indicate to the second device which cache-related capabilities of the first device are available.

[0046] In some possible implementations, before the third device sends the first information to the second device, the method may further include: the second device sending the device ID of the first device to the third device, the device ID being used to determine the first information.

[0047] Based on this, the third device can determine which cache-related capabilities of the first device the second device needs.

[0048] Fourthly, a communication device is provided, which is a first device.

[0049] The communication device may include a processing module and a transceiver module. The processing module may be used to determine first information; the transceiver module may be used to send the first information, which may indicate the cache-related capabilities of the first device, and the cache-related capabilities may be associated with a first function of the first device.

[0050] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0051] In some possible implementations, the transceiver module can also be used to receive a response to the first information from the second device, and the response to the first information can indicate whether the first function is enabled or disabled.

[0052] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0053] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0054] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0055] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0056] Fifthly, a communication device is provided, which is a second device.

[0057] The communication device may include a transceiver module and a processing module. The transceiver module may be used to receive first information, which may indicate the cache-related capabilities of the first device, and the cache-related capabilities may be associated with a first function of the first device; the processing module may be used to determine the cache-related capabilities of the first device based on the first information.

[0058] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0059] In some possible implementations, the transceiver module can also be used to send a response to the first information, which can indicate whether the first function is enabled or disabled.

[0060] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0061] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0062] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0063] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0064] In a sixth aspect, a communication device is provided, which may include at least one unit or module that can be used to perform the methods described in any of the foregoing aspects.

[0065] In a seventh aspect, a communication device is provided, which may include at least one processor coupled to at least one memory, the at least one memory being used to store computer programs or instructions, which, when executed by the at least one processor, may cause the communication device to implement the methods as described in any of the first aspects above.

[0066] In some possible implementations, the communication device also includes the at least one memory. Optionally, the memory and processor are integrated together.

[0067] In some possible implementations, the communication device is a chip or chip system.

[0068] Eighthly, a communication device is provided, which may include at least one processor coupled to at least one memory, the at least one memory being used to store computer programs or instructions, which, when executed by the at least one processor, may cause the communication device to implement the method as described in any of the second aspects above.

[0069] In some possible implementations, the communication device also includes the at least one memory. Optionally, the memory and processor are integrated together.

[0070] In some possible implementations, the communication device is a chip or chip system.

[0071] In a ninth aspect, a communication system is provided, which may include a first means, a second means, and a third means for performing the method of any one of the third aspects.

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

[0073] Eleventhly, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the methods described in any of the preceding aspects to be performed.

[0074] It is understood that the beneficial effects of aspects four through eleven above can be found in the relevant descriptions of aspects one through three above, and will not be repeated here. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0076] Figure 1 This is a schematic diagram of the structure of a communication system provided in an embodiment of this application.

[0077] Figure 2 This is a schematic diagram of another communication system provided in an embodiment of this application.

[0078] Figure 3 This is a schematic diagram of another communication system provided in the embodiments of this application.

[0079] Figure 4 This is a schematic diagram of the access process between the reader and the A-IoT terminal device provided in the embodiments of this application.

[0080] Figure 5 This is a schematic diagram of the basic inventory or access process of RFID provided in the embodiments of this application.

[0081] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application.

[0082] Figure 7 This is a schematic diagram of the topology between a base station and an A-IoT terminal provided in an embodiment of this application.

[0083] Figure 8 This is a schematic diagram of another topology between a base station and an A-IoT terminal provided in an embodiment of this application.

[0084] Figure 9 This is a schematic diagram of another topology between a base station and an A-IoT terminal provided in the embodiments of this application.

[0085] Figure 10 This is a schematic diagram of another topology between a base station and an A-IoT terminal provided in an embodiment of this application.

[0086] Figure 11 This is a flowchart illustrating another communication method provided in an embodiment of this application.

[0087] Figure 12 This is a flowchart illustrating another communication method provided in an embodiment of this application.

[0088] Figure 13This is a flowchart illustrating another communication method provided in an embodiment of this application.

[0089] Figure 14 This is a schematic diagram of the topology between a terminal device and an A-IoT terminal provided in an embodiment of this application.

[0090] Figure 15 This is a flowchart illustrating another communication method provided in an embodiment of this application.

[0091] Figure 16 This is a flowchart illustrating another communication method provided in an embodiment of this application.

[0092] Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0093] Figure 18 This is a schematic diagram of another communication device provided in an embodiment of this application.

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

[0095] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings.

[0096] It should be understood that the methods, situations, categories, and classifications of embodiments in this application are merely for descriptive convenience and should not constitute any particular limitation. Various methods, categories, situations, and features in embodiments can be combined without contradiction. It should also be understood that the terms "first," "second," "third," and "fourth" in the embodiments of this application are merely for distinction and should not constitute any limitation on this application. Furthermore, it should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0097] In this application embodiment, 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 mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, or b, or c, or a and b, or a and c, or b and c, or a and b and c, where a, b, or c can be single or multiple.

[0098] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0099] It should be noted that in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0100] The methods and apparatus provided in this application are based on the same or similar technical concepts. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and repeated parts will not be described again.

[0101] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Code Division Multiple Access (CDMA) systems, Wireless Local Area Network (WLAN), 5th Generation (5G) systems, New Radio (NR) systems, or future communication systems, etc.

[0102] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 This describes a communication system applicable to embodiments of this application. For example... Figure 1 As shown, the communication system includes a wireless access network 100. The wireless access network 100 may include at least one network device (such as...). Figure 1 110a, 110b and 110c in the above), may also include at least one terminal (such as Figure 1 (120a to 120g). It should be noted that... Figure 1 The communication system shown may also include a core network (not shown in the figure), which may consist of multiple core network elements or core network equipment.

[0103] The terminal device in this application embodiment may refer to user equipment (UE), station, access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, terminal (or terminal device), wireless communication equipment, user agent or user device, etc., or a device used to provide voice or data connectivity to users, or an Internet of Things device. For example, terminal devices include handheld devices with wireless connection functions, vehicle-mounted devices, etc., but this application embodiment does not limit this. The terminal device in this application embodiment may be a mobile phone, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, large screen, vehicle-mounted device (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), wearable device (e.g., smartwatch, smart bracelet, pedometer, smart glasses, etc.), machine type communication (MTC) terminal device, terminal device in 5G network, or terminal device in future evolved public land mobile network (PLMN), etc., and is not limited to this in this application embodiment.

[0104] The terminal device in the embodiments of this application may also be a tablet computer, a laptop computer, a handheld computer, a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a point of sale (POS) machine, customer-premises equipment (CPE), a light UE, a reduced capability UE (REDCAP UE), a wireless terminal in industrial control, a smart home device (e.g., a refrigerator, a television, an air conditioner, an electricity meter, etc.), a smart robot, a robotic arm, workshop equipment, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or a flying device (e.g., a smart robot, a hot air balloon, a drone, an airplane), etc. Terminal devices can also be vehicle devices, such as vehicle units, vehicle modules, vehicle chips, on-board units (OBUs), or telematics boxes (T-BOXs). Terminal devices can also be other devices with terminal functions. For example, a terminal device can also be a device that plays a terminal function in device-to-device (D2D) communication.

[0105] In some implementations, the terminal device can be used to act as a base station. Alternatively, the terminal device can act as a scheduling entity to provide sidelink signals between terminal devices in vehicle-to-everything (V2X) or D2D scenarios, for example, cellular phones and cars can communicate using sidelink signals, or cellular phones and smart home devices can communicate using sidelink signals without relaying communication signals through a base station.

[0106] The network device (i.e., access network device) in the embodiments of this application can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network, and can also be called a base station (BS). For example, the network device can be a NodeB, an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a radio network controller (RNC), a base station controller (BSC), a transmission reception point (TRP), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or a home Node B, HNB), an access point (AP), network devices in non-terrestrial networks (NTN) systems (such as satellites), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system, an access point (AP) in a base station or wireless fidelity (WiFi) system in a future mobile communication system, a radio controller, relay station, access point, vehicle-mounted equipment, wearable devices, or network devices in other future evolved communication systems, etc.

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

[0108] In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in an open radio access network (O-RAN) system, CU can also be called an O-RAN central unit (O-CU), DU can be called an O-RAN distributed unit (O-DU), CU-CP can be called an O-RAN central unit control plane (O-CU-CP), CU-UP can be called an O-RAN central unit user plane (O-CU-UP), and RU can be called an O-RAN radio unit (O-RU). Any of the units CU, DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. It should be understood that this application does not limit the specific technology or specific device form used in the network equipment.

[0109] In some implementations, the access network equipment may include a CU node, a DU node, or a RAN device that includes both CU and DU nodes. This RAN device, including both CU and DU nodes, separates the protocol layers of the eNB in ​​the LTE system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0110] In some implementations, the access network device may also be a reader / writer device.

[0111] Taking O-RAN as an example, the architecture of CU, DU, and RU can be as follows: Figure 2 As shown. Figure 2 An example diagram of an O-RAN system is shown. An O-RAN system may also include... Figure 2 Other components besides those shown.

[0112] like Figure 2 As shown, the access network equipment (RAN, such as an eNB, gNB, or next-generation access network equipment) communicates with the core network (CN) via a backhaul link, and communicates with the UE via an air interface. Equivalently, the BBU in the access network equipment communicates with the core network via a backhaul link, and the RU in the access network equipment communicates with at least one UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. Optionally, the BBU may include at least one CU and at least one DU, which can communicate via at least one midhaul link.

[0113] In some implementations, the CU (i.e., O-CU) of the O-RAN system is a logical node that carries the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the radio link control (RLC) layer and lower layers) through interfaces, which may be interfaces such as F1 interfaces. In some implementations, these interfaces (e.g., the F1 interface) can provide CP and UP functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (AP) is the application protocol of the F1 interface, defining the F1 signaling procedures in some implementations. The F1 interface supports control plane F1-C and user plane F1-U.

[0114] In some implementations, the CU of an O-RAN system can be split into CU-CP (i.e., O-CU-CP) and CU-UP (i.e., O-CU-UP). CU-CP is a logical node carrying the RRC layer and the PDCP control plane (PDCP-C) layer, and can be 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 (AMF) network elements, such as the AMF network element in a 5G system. AMF network elements can be used to handle mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and the PDCP user plane (PDCP-U) layer, and is 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. Network elements in the core network that implement user plane functions, such as the user plane function (UPF) in a 5G system, are responsible for forwarding and receiving data in terminal devices.

[0115] In some implementations, the DU (i.e., O-DU) of the O-RAN system is a logical node carrying the RLC layer, medium access control (MAC) layer, higher physical layer (higher PHY) layer, and other functions. In some implementations, the DU can control at least one RU. The DU connects to the RU through interfaces, which may be fronthaul interfaces. In some implementations, the higher PHY layer includes PHY layer processing functions, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0116] In some implementations, the RU (or O-RU) of an O-RAN system is a logical node carrying lower physical layer (PHY) and radio frequency (RF) processing. In some implementations, the RU may be a 3GPP TRP or RRH or other similar functional entity. In some implementations, the lower physical layer functions include portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link. The O-RU is similar to a 3GPP TRP or RRH, but includes lower physical layer functions such as FFT / IFFT or extraction of the physical random access channel (PRACH).

[0117] The DU and RU may or may not be co-located. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces, respectively providing the control plane (C-plane) and user plane (U-plane). In some implementations, the C-plane refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-plane) refers to non-real-time management operations between the DU and RU.

[0118] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU 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 PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0119] The above CU and DU configurations are merely examples; 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 only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and 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. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0120] In some implementations, the O-RAN system may also include an O-RAN cloud (O-cloud). The O-cloud can serve as a cloud computing platform, comprising physical infrastructure nodes for hosting O-RAN functions such as the RAN intelligent controller (RIC), O-DU, etc. Furthermore, the O-cloud can support the management and orchestration of software components (such as operating systems, virtual machine monitoring, and container runtimes).

[0121] In some implementations, the network device can be fixed or mobile, and this application does not limit this. For example, a helicopter or drone can be configured as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, a helicopter or drone can be configured as a device to communicate with another network device.

[0122] In some implementations, network devices can be deployed on land or in the air, and this application does not limit this. For example, network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites.

[0123] In some implementations, the communication system may include a RIC module. For example, an application framework involving a RIC module under an O-RAN architecture may be as follows: Figure 3 As shown. RICs in a communication system can include near-real-time RICs (Near-RT RICs) and non-real-time RICs (Non-RT RICs).

[0124] Near real-time RICs can be used to achieve near real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, they enable near real-time control and optimization of O-RAN modules and resources. For example, in an O-RAN architecture, a near real-time RIC can obtain information from at least one of the network-side and terminal-side information from at least one of the RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and terminals. This information can be used as training data or inference data. Optionally, the near real-time RIC can deliver inference results to at least one of the RAN nodes and terminals. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs. For example, the near real-time RIC delivers the inference results to the DU, and the DU sends them to the RU.

[0125] Non-real-time RICs enable non-real-time intelligent management of RAN functions. They facilitate artificial intelligence (AI) / machine learning (ML) workflows, including model training and updates, and guide applications / functions within the Near-RT RIC based on policies. The Non-RT RIC resides within the Service Management and Orchestration Framework (SMO) module, which functions similarly to network management. For example, a Non-real-time RIC can be used to train an AI model and perform inference. Exemplarily, in an O-RAN architecture, a Non-real-time RIC can obtain information from at least one of the network-side and terminal-side information from at least one of the RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and terminals. This information can serve as training data or inference data, and the inference results can be delivered to at least one of the RAN nodes and terminals. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs; for example, the Non-real-time RIC can deliver inference results to a DU, which then forwards them to an RU.

[0126] Near real-time RICs or non-real-time RICs can also be configured as separate network elements. Optionally, near real-time RICs or non-real-time RICs can also be part of other devices. For example, near real-time RICs can be set in RAN nodes (e.g., CU, DU), while non-real-time RICs can be set in operation administration and maintenance (OAM) systems, cloud servers, core network devices, or other network devices.

[0127] These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in OAM, may be equipped with one or more AI modules (not shown in the figure). Access network nodes may be standalone RAN nodes or may include multiple RAN nodes, for example, CUs and DUs. At least one of the CUs and DUs may also be equipped with one or more AI modules. Optionally, a CU may be further divided into CU-CP and CU-UP, and at least one of CU-CP and CU-UP may also be equipped with one or more AI models.

[0128] AI modules can be used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. The model of an AI module can be configured with different parameters, enabling the module to perform different functions. The model of an AI module can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or bias in the activation function); input parameters (e.g., at least one of the following: type of input parameter and dimension of input parameter); or output parameters (e.g., at least one of the following: type of output parameter and dimension of output parameter). The bias in the activation function can also be referred to as the bias of the neural network.

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

[0130] The meanings of the interfaces (not shown in the figure) included in the above O-RAN system can be seen as follows.

[0131] A1 Interface: The interface between Non-RT RIC and Near-RT RIC, which can be used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RIC provides policies, rich information, and ML model updates to Near-RT RIC through the A1 interface, while Near-RT RIC provides policy feedback to Non-RT RIC through the A1 interface.

[0132] E2 Interface: The E2 interface is an open interface between two endpoints, used to connect the Near-RT RIC and the RAN node. RAN nodes include, for example, CU and DU in 5G, O-RAN compatible eNB in ​​4G, O-CU (at least one of O-CU-CP and O-CU-UP) in O-RAN, and / or O-DU, etc. The RIC can obtain RAN node data collection and feedback through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.

[0133] O1 Interface: The interface between the management entity in the SMO and the O-RAN module. It can be used for operation management, and FCAPS management, software management, and file management can be achieved through this interface.

[0134] O2 Interface: The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functionality.

[0135] The open fronthaul (CUS-plane) interface includes the control plane (C-plane), user plane (U-plane), and synchronization plane (S-plane) interfaces. The control plane is used for real-time control between the O-DU and O-RU, such as transmitting beamforming weights from the O-DU to the O-RU or performing power control from the O-DU to the O-RU. The user plane is used to transmit communication data between the DU and RU for access network equipment and terminals. The synchronization plane is used by the O-DU to provide clock synchronization for the O-RU.

[0136] NG interface: The interface between NR RAN equipment (such as base stations, CUs, CU-CPs, or CU-UPs) and the NR core network; among them, NG-u is the user plane NG interface, and NG-c is the control plane NG interface.

[0137] Xn interface: The interface between NR RAN devices (such as base stations, CUs, CU-CPs, or CU-UPs); where Xn-u is the user plane Xn interface and Xn-c is the control plane Xn interface.

[0138] X2 Interface: The interface between LTE RAN devices; X2-u is the user plane X2 interface, and X2-c is the control plane X2 interface. In NR, the X2 interface is mainly used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device that connects to the LTE core network through the X2 interface.

[0139] E1 interface: The interface between CU-CP and CU-UP.

[0140] F1-C interface: The interface between CU-CP and DU.

[0141] F1-U interface: The interface between CU-UP and DU.

[0142] In this embodiment, the terminal device or network device may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment.

[0143] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0144] It should be understood that the above communication system is illustrated using a 5G system as an example. Of course, this application can also be applied to other 3rd generation partnership project (3GPP) communication systems, such as future wireless communication systems. The embodiments of this application are not limited in this respect.

[0145] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0146] It should be understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that with the evolution of network architecture, the embodiments of this application can also be applied to similar technical problems.

[0147] In certain communication scenarios (such as the Ambient Internet of Things (A-IoT) scenario), different communication devices in a communication system have varying capabilities, which in turn affect the functionality of these devices. How to better manage the functionality of communication devices remains a challenge.

[0148] The following section will take the A-IoT scenario as an example to explain the above issues in detail.

[0149] With the development of communication technology, 3GPP defined A-IoT technology. A-IoT in A-IoT technology can include readers and A-IoT terminal devices. In other words, an A-IoT-based communication system can include readers and A-IoT terminal devices. Typically, readers are also called reader-writers or network devices, and A-IoT terminal devices are also called Class I terminal devices, tags, or A-IoT terminals. A reader is a device that can be handheld or fixed to read (and sometimes write) information from A-IoT terminals; it can be understood as a device that communicates with A-IoT terminals.

[0150] A-IoT terminal devices can be divided into three categories: deviceA, deviceB, and deviceC.

[0151] Device A (similar to a passive A-IoT terminal) has no energy storage function and no independent signal generation / amplification function. For example, the communication technology used by device A can be backscattering transmission technology.

[0152] Device B (similar to a semi-passive A-IoT terminal) has energy storage capabilities but no independent signal generation capabilities. For example, device B may employ backscattering transmission technology, and the energy stored in device B can be used to amplify the reflected signal.

[0153] Device C (similar to an active A-IoT terminal) has energy storage capabilities and independent signal generation capabilities. For example, device C may include active radio frequency components for transmission.

[0154] Both readers and A-IoT terminal devices in A-IoT technology can be implemented based on cellular network infrastructure. In other words, both readers and A-IoT terminal devices can be devices within a cellular network. For example, a reader can be a terminal device, access network device (such as a base station), headend, pico remote radio unit (pRU / pRRU), TRP, or a node transmitting signals within a cellular network, or a device with read / write capabilities. Similarly, a reader can also be an integrated access and backhaul (IAB) node, a smart repeater, or a relay node. Likewise, A-IoT terminal devices can be terminal devices within a cellular network, such as ultra-low power, ultra-low complexity terminal devices.

[0155] In A-IoT technology, readers and A-IoT terminal devices can communicate without contact, allowing the reader to read information from and / or write information to the A-IoT terminal device. A-IoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, and command. Command services can implement write or lock processes. In terms of application scope, A-IoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring. The number of readers and A-IoT terminal devices is not limited in A-IoT business scenarios. For example, there can be one or more A-IoT terminal devices. Similarly, there can be one or more readers.

[0156] For example, in inventory management, the reader can access A-IoT terminal devices within its coverage area. Successfully connected A-IoT terminal devices need to send their unique identifier to the reader. The unique identifier of the A-IoT terminal device can be an identifier that the reader can recognize, such as the electronic product code (EPC) in passive radio frequency identification (RFID).

[0157] For example, in a location service, the reader can use some location signals to locate the position of the A-IoT terminal device.

[0158] For example, in a sensing service, an A-IoT terminal device can report sensing data to a reader, such as temperature data.

[0159] For example, in the command service, the reader can send operation instructions to the A-IoT terminal device to implement write and lock processes. In the write process, the reader can send downlink instructions and data to the A-IoT terminal device, instructing it to write data into its own memory. In the lock process, the reader can send downlink instructions to the A-IoT terminal device, instructing it to lock a specified address in its memory. Once locked, the content at that address cannot be modified and / or read.

[0160] The following section provides a detailed overview of the workflow of the air interface / access stratum (AS) in A-IoT technology, mainly involving the connection between the reader and A-IoT terminal devices.

[0161] For example, such as Figure 4 As shown, the connection between the reader and the A-IoT terminal device may include step AC.

[0162] Step A: The reader sends an A-IoT paging message to perform A-IoT paging. The reader can send an A-IoT paging message according to the service request and indicate the A-IoT terminals that need to respond.

[0163] It should be noted that "A-IoT paging message" can also be "(initial) trigger message".

[0164] Step B: The triggered A-IoT terminal connects to the reader via the A-IoT random access procedure or without using the A-IoT random access procedure (such as contention-free resolution), and transmits its device identification (ID) to the reader through device-to-reader (D2R) data transmission.

[0165] Step C may include steps C1 and C2.

[0166] Step C1: Possible data transmission from the reader to the A-IoT terminal device (reader to device, R2D) (e.g., the reader sends commands such as read, write, lock, deactivate, sense, etc.).

[0167] Step C2: Possible D2R data transmission (e.g., the A-IoT terminal device's response to the reader's command, such as responding to the data read by a read command, or providing feedback on the success / failure of a write command).

[0168] The above process can support inventory and command application scenarios in the following ways:

[0169] For inventory-only scenarios, the baseline approach may include steps A and B.

[0170] For inventory and command scenarios, the baseline scheme may include steps A, B, C1, and C2.

[0171] For command-only scenarios, steps A, B, C1, and C2 can be used as a baseline scheme for support.

[0172] Alternatively, for command-only scenarios, support can be provided through steps A' and C2.

[0173] In step A', the reader performs A-IoT paging. The reader can send an A-IoT paging message containing commands based on a service request, instructing the device to process / respond to the commands.

[0174] In step C2, the A-IoT terminal device performs possible D2R data transmission (e.g., transmitting device ID or corresponding response to a reader's command) with or without the A-IoT random access procedure.

[0175] The following section introduces the A-IoT paging function of the reader.

[0176] At the AS layer, the reader's A-IoT paging function can indicate which A-IoT terminal devices need to respond. A-IoT paging messages can be identified by an identifier that identifies the A-IoT terminal device or group of A-IoT terminal devices included or associated with the message.

[0177] As an example, an A-IoT paging message can contain a single A-IoT terminal identifier (ID), indicating that a single A-IoT terminal needs to respond to the A-IoT paging message.

[0178] As another example, an A-IoT paging message can contain a group ID mapped to multiple A-IoT terminals, indicating that multiple A-IoT terminals in an A-IoT terminal group need to respond to the A-IoT paging message.

[0179] As another example, an A-IoT paging message may not contain any identifier, that is, it indicates that all A-IoT terminals that can receive the A-IoT paging message need to respond to the A-IoT paging message.

[0180] As another example, an A-IoT paging message can contain multiple A-IoT terminal identifiers, indicating that multiple A-IoT terminals need to respond to the A-IoT paging message.

[0181] Optionally, the A-IoT paging message may also indicate information for determining the resources (such as at least one of time-domain resources and frequency-domain resources) used by the A-IoT terminal for the D2R response message.

[0182] Optionally, the paging function of the A-IoT terminal can be understood as not supporting traditional paging messages, traditional paging timing, and traditional discontinuous reception (DRX) from NR. It can be assumed that the A-IoT terminal can receive A-IoT paging as long as it has sufficient power.

[0183] As described above, A-IoT terminals can be randomly connected to readers. The following section introduces the random connection of A-IoT terminals.

[0184] Random access by A-IoT terminals can be triggered by a reader. This random access can include access triggered by a single A-IoT terminal, a group of A-IoT terminals, or all A-IoT terminals covered by the reader. For example, the slotted-ALOHA protocol can serve as the baseline for the A-IoT random access process.

[0185] During the process of an A-IoT terminal accessing a reader, when the A-IoT terminal responds according to the paging message, the A-IoT terminal can execute the following process:

[0186] Step 1: Determine the random access type and access timing based on the paging message. The timing can also be replaced with resources.

[0187] -If the random access is contention-free random access (CFRA):

[0188] ■ Select the D2R timing / resource indicated by the paging message;

[0189] ■ Skip the race resolution in step 2 and proceed to step 3 to perform data transmission.

[0190] - If it is contention-based random access (CBRA):

[0191] ■ Determining / selecting the timing / resources for access, such as random selection;

[0192] ■ Step 2 of the competition resolution process.

[0193] Step 2: Contention-based random access contention resolution:

[0194] - To address contention-based random access issues, the following two solutions are available:

[0195] ■Option 1: No data in A-IoT message 1 (Msg1):

[0196] ◆A-IoT Msg1: When an A-IoT terminal recognizes the start of its access occasion, it can send a randomly generated ID (excluding other data) to the reader via Msg1.

[0197] ● It's important to note that there are no restrictions on how A-IoT terminals generate random IDs. For example, A-IoT terminals can generate random IDs randomly or based on the device ID. There are also no restrictions on the size of the random ID; for instance, the random ID can be a 16-bit random number.

[0198] ■A-IoT Message 2 (Msg2): The reader responds with a random ID indicating successful reception.

[0199] If the A-IoT terminal receives A-IoT Msg2 containing a random ID, and that random ID is the same as the one previously sent in A-IoTMsg1, then the A-IoT terminal can consider the competition successful.

[0200] ● It should be noted that A-IoT Msg2 can be used for contention resolution. Here, it is assumed that the size (i.e., the range of values) of the random ID in A-IoT Msg1 is sufficient for contention resolution. If the probability that A-IoT terminals choosing the same access time / resource send the same random ID value in A-IoT Msg1 is low enough, the range of values ​​for the random ID can be considered large enough.

[0201] ■Option 2: A-IoT Msg1 has data:

[0202] ◆A-IoT Msg1: When an A-IoT terminal recognizes the start of its own access event, it can send an A-IoT Msg1 containing upper-layer data, which can be at least one of the device ID and any other upper-layer data. Optionally, in Scheme Two, the A-IoT Msg1 may or may not include a random ID.

[0203] ◆A-IoT Msg2: The reader can respond with at least one of the following upon successful reception: Random ID; Device ID

[0204] (Partial or complete); Acknowledgment (ACK) message. Alternatively, the reader may not respond; if the A-IoT terminal does not receive a signal indicating failure, reconnection, or retransmission, the A-IoT terminal...

[0205] The IoT terminal then considers the connection successful / data transmission successful / service successful.

[0206] ◆If the A-IoT terminal receives an A-IoT Msg2 containing at least one of the following: a random ID; a device ID (partial or complete); or an ACK, and if this information includes a portion of the previously sent information in A-IoT Msg1, or if this information is generated based on A-IoT Msg1 (e.g., by hashing Msg1), then the A-IoT terminal can consider the race condition resolved successfully.

[0207] Step 3: Data Transfer

[0208] - If contention-based random access is used, or if contention-free access is used, the A-IoT terminal can perform upper-layer data transmission with the reader after it considers the contention to be resolved successfully. The upper-layer data can be at least one of the device ID and any other upper-layer data (if any).

[0209] - In step 3, it can be understood that subsequent R2D transmissions after a D2R transmission do not always need to be sent. The use / existence of subsequent R2D transmissions is not limited; for example, subsequent R2D transmissions can be used to handle retransmissions or reconnections after a D2R transmission failure (due to various reasons).

[0210] As mentioned earlier, the slotted-ALOHA protocol can serve as a baseline for the random access process in A-IoT. For example, RFID technology employs slotted-ALOHA, which will be discussed below.

[0211] An RFID system can include readers and tag devices, also known as electronic tags. Readers can interact with tag devices to manage them. For example, a reader can read information from a tag device or write information that the tag device needs to store.

[0212] Typically, readers and tags can communicate without contact. However, tags have limited functionality and require activation from the reader to send information. Tags convert the wireless signals emitted by the reader into energy, which powers them. Tag devices can support power consumption in the microwatt or even hundreds of microwatts, limiting their ability to support complex designs.

[0213] For example, if RFID is applied to a mobile communication system, such as a 5G system, then the base station can act as a reader / writer to perform the functions of a reader / writer.

[0214] Currently, the main application scenarios for RFID technology are identity recognition or target identification, and it can also be used for data reading and writing. For example, the basic inventory or access process for RFID can be as follows: Figure 5 As shown, it includes steps 1-7.

[0215] Step 1: The reader sends a Select message. The Select message can be used to select a set of tags. The Select message can carry information such as the stored session, action, and mask.

[0216] The session and flag bits are bound together; each flag bit corresponds to a session, and the reader can specify which session's flag bit it is. The action specifies how to set the flag bit. For example, the action value can be 1 or 0, corresponding to setting the flag bit corresponding to session A (action = 1) or B (action = 0), respectively. The mask can be used to filter which tags are selected. For example, if a tag stores a complete 96-bit identifier, the mask can indicate that tags with the first 16 bits being 111…111 are selected. If the mask matches, the tag can further set its flag bit according to the action and then listen for subsequent query messages.

[0217] Suppose the Select message indicates session: S0, action = 0, meaning it instructs the tag to set the flag of session S0 to A. If the mask matches, the corresponding tag can set its flag to A. If the tag successfully transmits the EPC in a later step, the flag will flip to B. Thus, tags with flag A have not yet transmitted the EPC, and tags with flag B have successfully transmitted the EPC.

[0218] Step 2: The reader sends a query message, which may carry the Q-value, session, and flag. Assuming the session in the query message is S0 and the flag is A, when the tag's session matches the flag, the tag can randomly generate a value between 0 and 2 based on the Q-value. Q-1 A random number is used as the initial value for the counter.

[0219] Step 3: If no tag sends a response, the reader continues to send a query repeat (QueryRep). After a tag receives a QueryRep, its counter is decremented by 1, i.e., counter = counter - 1.

[0220] Step 4: If the tag's counter value is 0, the tag can send a 16-bit random number (RN16) to the reader. RN16 can be used for contention resolution. Optionally, the tag can also send an 8-bit random number to the reader. If the tag's counter value is not 0, the tag does not respond to the reader.

[0221] If the reader does not receive RN16, the reader can continue to send QueryRep; if the tag receives (may receive multiple) QueryRep (QueryRep does not need to carry content, i.e., it does not need to carry Q value, session, flag bits) and the counter is decremented to 0, the tag will send back RN16; if the counter is not decremented to 0, the tag will not respond to the reader.

[0222] For example, each QueryRep corresponds to the start or end of an access time slot. Each time a tag receives a QueryRep, it signifies the end of the previous time slot and the start of the next time slot. The tag can randomly select an access time slot to initiate access or send uplink (UL) data (e.g., EPC) or receive downlink (DL) data in the corresponding access time slot.

[0223] Step 5: If the reader receives RN16 and there is no conflict (i.e., only one tag sent RN16), the reader can send back ACK, where the ACK can include the received RN16 to indicate that contention resolution was successful.

[0224] Step 6: If the tag receives an ACK and RN16 matches, the tag can send back an EPC; otherwise, the tag will not send back an EPC.

[0225] If a tag sends an EPC and receives a QueryRep, the tag considers the EPC transmission successful. The tag can toggle a flag bit, switching it from A to B. This flag bit can prevent previously stored tags from being stored again; tags with toggleed flag bits will not respond to a Query indicating flag bit A.

[0226] As mentioned earlier, there may be multiple A-IoT terminals in an A-IoT business scenario. Different A-IoT terminals may have different capabilities, which will affect the functionality of the A-IoT terminals. How to better manage the functionality of A-IoT terminals is a problem that needs to be solved.

[0227] To address one or more of the aforementioned technical problems, this application proposes a communication method. In this communication method, a first device can send first information indicating its own cache-related capabilities, and these cache-related capabilities can be associated with a first function of the first device. Therefore, based on the first information, the network side can understand the cache-related capabilities of the first device, which helps to better manage the first function of the first device.

[0228] The following describes an embodiment of the communication method of this application with reference to the accompanying drawings.

[0229] Figure 6 A communication method 600 provided in an embodiment of this application is illustrated. Exemplarily, the communication method 600 can be applied to a first device, a second device, and a third device.

[0230] The first device can be a terminal device, which can be an entity on the user side used to receive or transmit signals, such as a UE or an A-IoT terminal.

[0231] Alternatively, the first device may be a component or device of the terminal equipment (e.g., a processor, chip, or chip system).

[0232] Alternatively, the first device can also be a logic module or software that can realize all or part of the functions of the terminal equipment, such as an RRC signaling interaction module (for sending and receiving RRC signaling), a MAC signaling interaction module (for sending and receiving MAC-control element (CE) signaling), and a physical layer (PHY) signaling and data interaction module (for sending uplink control signaling; receiving uplink control signaling; sending downlink control signaling; receiving downlink control signaling, where control signaling can be replaced by data), etc.

[0233] The second device can be an access network device, which can be an entity on the access network side used to transmit or receive signals, such as a gNB.

[0234] Alternatively, the second device may be a component or device of the access network equipment (e.g., a processor, chip, or chip system).

[0235] Alternatively, the second device can be a logic module or software that can realize all or part of the access network functions, such as an RRC signaling interaction module (for sending and receiving RRC signaling), a MAC signaling interaction module (for sending and receiving MAC-CE signaling), a PHY signaling and data interaction module (for sending and receiving uplink / downlink control signaling and uplink / downlink data), etc.

[0236] The third device can be core network equipment, which can be various functional entities on the network side used to manage users, data transmission and base station configuration, such as AMF network elements, UPF network elements, session management function (SMF) network elements, tag management function (TMF) network elements, etc.

[0237] Optionally, if the first device is an A-IoT terminal, the second device can be an access network device or a terminal device. The A-IoT terminal can be located within the coverage area provided by the second device (i.e., the reader). For example, when the reader is a terminal device, the communication between the reader and the A-IoT terminal can be considered as transmission between terminals. Similarly, when the reader is an access network device, the communication between the reader and the A-IoT terminal can be through the Uu interface, i.e., air interface communication.

[0238] Optionally, the number of the first device and the second device in the communication method 600 is not limited.

[0239] like Figure 6 As shown, method 600 may include steps S610-S620.

[0240] In step S610, the first device determines first information, which may indicate the cache-related capabilities of the first device.

[0241] It should be noted that the terms cache, temporary cache, save, temporary save, storage, and temporary storage in this application can be used interchangeably.

[0242] Optionally, the first device may generate the first information on its own.

[0243] Optionally, the cache-related capabilities of the first device can be associated with the first function of the first device.

[0244] Optionally, the cache-related capabilities of the first device may refer to the cache-related capabilities of the first device, such as the capabilities related to data caching.

[0245] Optionally, the first function may refer to the function involved in the normal operation of the first device.

[0246] For example, the first device is an A-IoT terminal, and the first function can be the function involved in data transmission by the A-IoT terminal.

[0247] Optionally, the first information can be an instruction.

[0248] In step S620, the first device sends first information. Correspondingly, the second device can receive the first information sent by the first device.

[0249] Optionally, the second device may pass through or forward the cache-related capabilities of the first device to the third device.

[0250] Optionally, the cache-related capabilities that the second device can pass through or forward to the third device can be associated with the device ID of the first device.

[0251] For example, the second device can transmit or forward: Capability 1 (associated with device ID1), where Capability 1 is the cache-related capability of the first device corresponding to device ID1.

[0252] Optionally, the second device may transmit or forward one or more cache-related capabilities of the first device to the third device, and the cache-related capabilities are associated with the device ID of the first device.

[0253] For example, the second device can pass through or forward: Capability 1 (associated with device ID1) and Capability 2 (associated with device ID2).

[0254] Optionally, the cache-related capabilities that the second device can pass through or forward to the third device can also be associated with the group ID of the first device group.

[0255] Optionally, if a first device group has the same cache-related capabilities, the second device may pass through or forward the cache-related capabilities and group ID of the first device group to the third device.

[0256] For example, the second device can pass through or forward: Capability 1 (associated with group ID1), where Capability 1 is the cache-related capability of the first device group corresponding to group ID1.

[0257] Optionally, the second device may transmit or forward one or more cache-related capabilities of the first device group to the third device, and the cache-related capabilities are associated with the group ID of the first device.

[0258] For example, the second device can transmit or forward: Capability 1 (associated with group ID1) and Capability 2 (associated with group ID2).

[0259] Optionally, the third device may determine at least one of the following based on the buffering capabilities of the first device: whether to segment the downlink data sent to the first device; how many segments to divide the downlink data into for transmission; the content of each segment of downlink data transmitted; whether the first device performs encryption operations; and whether the first device performs integrity protection operations.

[0260] For example, the downlink data sent by the third device to the first device is a write command, which instructs the first device to write 120 bits of data to its storage area. The third device can determine that the first device's maximum cache or available cache is 40 bits based on cache-related capabilities (or relevant information determined by the second device based on cache-related capabilities indicated by the first information). Therefore, the third device can divide the 120 bits of data into three transmissions, each instructing the first device to write 40 bits to its own storage area.

[0261] Optionally, the first device may send multiple first messages. Correspondingly, the second device may receive multiple first messages sent by the first device.

[0262] Optionally, the different first messages sent by the first device indicate different cache-related capabilities.

[0263] For example, the first message sent by the first device can indicate capability 1 (first capability, second capability), and the second message sent by the first device can indicate capability 2 (third capability, fourth capability).

[0264] Optionally, the different first messages sent by the first device indicate different cache-related capabilities, and the different first messages are adapted to different scenarios.

[0265] For example, in inventory management, the first information sent by the first device may only indicate capability 1 (the first capability, the second capability). In other scenarios, the first information sent by the first device may indicate capability 2, which may include some specified cache-related capabilities or optional cache-related capabilities. These other scenarios may refer to command-line operations (such as read or write commands) or other specified operations.

[0266] For example, when the first device sends the first information by default, the first information may only indicate capability 1 (the first capability, the second capability). However, when the network side instructs or requests the first device to send the first information, the first information may include some specified cache-related capabilities or optional cache-related capabilities. Here, the network side can be an access network device or a core network device.

[0267] Optionally, the different first messages sent by the first device indicate the same cache-related capabilities, but the content of the same cache-related capabilities is updated by the first messages sent later.

[0268] For example, the first message sent by the first device can indicate capability 1 (a first capability and a second capability), and the second message sent by the first device can also indicate capability 1 (a first capability and a second capability). However, at least one of the first and second capabilities indicated by the second message is different from the content indicated by the first message. For example, at least one of the first and second capabilities can be a cache-related capability that changes over time, i.e., a dynamic capability, while the remaining capabilities can be cache-related capabilities that do not change over time, i.e., static capabilities.

[0269] Optionally, the different first messages sent by the first device indicate at least one cache-related capability that is the same, and the content of the same cache-related capability is updated by the subsequent first messages. That is, different first messages may include both the same cache-related capability and different cache-related capabilities.

[0270] For example, the first message sent by the first device can indicate capability 1 (first capability, second capability), and the second message sent by the first device can indicate capability 2 (first capability, fourth capability). However, the first capability indicated by the second message is different from the first capability indicated by the first message, that is, the first capability is a dynamic capability.

[0271] The following section provides a detailed explanation of the association between the cache-related capabilities of the first device and its first function.

[0272] Optionally, the association between the cache-related capabilities of the first device and the first function of the first device may mean that the cache-related capabilities of the first device include capabilities related to the first function of the first device.

[0273] Alternatively, the association between the cache-related capabilities of the first device and the first function of the first device can mean that the cache-related capabilities of the first device include the capabilities required by the first device to implement the first function.

[0274] Alternatively, the association between the cache-related capabilities of the first device and the first function of the first device can mean that the cache-related capabilities of the first device include the capability to support the first device in implementing the first function.

[0275] It should be noted that the association between the cache-related capabilities of the first device and the first function of the first device can also be understood as: the first function of the first device is associated with the cache-related capabilities of the first device.

[0276] Alternatively, the association between the cache-related capabilities of the first device and the first function of the first device can also be understood as: there is a relationship between the cache-related capabilities of the first device and the first function of the first device.

[0277] Optionally, the cache-related capabilities of the first device may include one or more capabilities.

[0278] Optionally, the first function of the first device may include one or more functions.

[0279] Optionally, a cache-related capability of the first device can be associated with multiple first functions of the first device.

[0280] Optionally, the various cache-related capabilities of the first device can be associated with a first function of the first device.

[0281] Alternatively, a cache-related capability of the first device may be associated with a first function of the first device.

[0282] The following section provides a detailed explanation of how the first piece of information indicates cache-related capabilities.

[0283] Optionally, the first information may indicate one or more of the size, status, and type of the cache-related capabilities of the first device.

[0284] As an example, for cache-related capabilities that can be quantified, the first piece of information can indicate the size of the cache-related capabilities.

[0285] Alternatively, the size of the cache-related capacity can be indicated directly.

[0286] For example, the first information may indicate that the first device can buffer 16 bits.

[0287] For example, the first information can also indicate the number of bits that the first device can buffer.

[0288] For example, different levels of the number of bits that the first device can buffer can be indicated by different indices. For instance, index=00 indicates a buffer size of 1 to 50 bits; index=01 indicates a buffer size of 51 to 100 bits; index=10 indicates a buffer size of 101 to 150 bits; and index=11 indicates a buffer size greater than 150 bits.

[0289] It should be noted that the values ​​of index and buffer size here are only examples and are not specifically limited in this application.

[0290] Alternatively, the size of cache-related capabilities can also be indicated indirectly.

[0291] Alternatively, the size of cache-related capabilities can be indicated by their relationship to a threshold.

[0292] For example, if the threshold related to the cache size of the first device is 50 bits, then this threshold can divide the cache size capability of the first device into two capabilities: <50 bits and >=50 bits. These two capabilities can be referred to as the first capability and the second capability. Assuming that the cache size of the first device is 30 bits (<50 bits), then the first information can indicate that the first device has the first capability.

[0293] As another example, for cache-related capabilities that cannot be quantified, the first information may indicate the status or type of the cache-related capabilities of the first device.

[0294] For example, for cache-related capabilities that can represent the energy level of a first device, the first information indicating the capability can indicate the energy state of the first device.

[0295] For example, for cache-related capabilities that can indicate the access type of the first device, the first information indicating the capability can indicate the access type of the first device.

[0296] Optionally, the first information can indicate cache-related capabilities via information cells. For example, the first information can indicate the relationship between cache-related capabilities and threshold values ​​via information cells.

[0297] For example, the first information can indicate that the number of bits that the first device can currently cache is less than 16 bits by using information cell 1=0, and can indicate that the number of bits that the first device can currently cache is greater than or equal to 16 bits by using information cell 1=1. It should be noted that the number of bits that can be cached here can also be replaced by the maximum cached data size.

[0298] Optionally, a single information element can indicate one or more cache-related capabilities. For example, the first information element can indicate the relationship between multiple cache-related capabilities and their respective corresponding thresholds.

[0299] Optionally, the thresholds corresponding to caching capabilities can be agreed upon through a protocol.

[0300] Alternatively, the threshold corresponding to the cache-related capabilities can be indicated to the first device by the second device. For example, the second device can indicate the threshold corresponding to the cache-related capabilities to the first device via a paging message.

[0301] Optionally, the cache-related capabilities indicated by the first information may be effective in at least one of a certain time and a certain process.

[0302] For example, the cache-related capabilities indicated by the first information can be valid for two days after the second device receives the first information.

[0303] For example, if the first device is an A-IoT terminal, the cache-related capabilities indicated by the first information can be effective in one inventory or paging process of the second device, but invalid in the next inventory or paging process initiated by the second device.

[0304] Optionally, the first information may include at least one of the validity period and validity process of cache-related capabilities.

[0305] Alternatively, the first device may also indicate at least one of the effective time and effective process of the cache-related capabilities through other indication information.

[0306] Alternatively, at least one of the effective time and effective process of caching-related capabilities can be agreed upon by the protocol.

[0307] Alternatively, at least one of the validity period and validity process of cache-related capabilities can be configured by a second or third device, and the configuration method is not limited. It should be noted that the configuration here can be replaced by an instruction.

[0308] Optionally, the method of carrying the first information is not limited.

[0309] As an example, the first information can be carried separately in a single uplink message. For instance, the first information can be carried separately in the MAC header or MAC CE.

[0310] As another example, the first information can also be carried together with other information that needs to be sent to the second device in a single uplink message.

[0311] For example, the first piece of information can be carried in Msg1 in the A-IOT random access procedure described above.

[0312] For example, the first information can also be carried in the uplink message (e.g., Msg3) following Msg1 or Msg2 in the A-IOT random access procedure described above.

[0313] It should be noted that Msg1 here can be replaced with a message used by the first device to access the second device or a message used by the first device to initiate random access; the message name is not limited. Msg1 can include a random number (e.g., a 16-bit random number) or other identification information of the first device. Msg1 can also include upper-layer data such as the device ID. Msg2 here can be replaced with a message indicating that the first device has resolved contention or a message indicating that the first device has successfully accessed the device; the message name is not limited. Msg2 can include a random number (e.g., a 16-bit random number) or other identification information of the first device. The name of Msg3 is not limited; Msg3 can include upper-layer data such as the device ID.

[0314] Alternatively, the initial information can also be carried in other uplink data.

[0315] Alternatively, the first information can also be carried in the MAC header or MAC CE. Unlike the first information being carried separately in the MAC header or MAC CE, this refers to the first information being carried together with other data in the MAC header or MAC CE.

[0316] Alternatively, the initial information can also be carried in upper-layer data such as non-access stratum (NAS) messages or application layer messages.

[0317] It should be noted that the first information in the embodiments of this application can also be called capability information, capability reporting information, etc.

[0318] In some possible implementations, the cache-related capabilities of the first device may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size; buffer status report (BSR) capability; energy status; device type; random access (RA) type.

[0319] Storage capacity, downlink data size, and BSR capability can be quantified. For example, the storage capacity, downlink data size, and BSR capability of the first device can be described using the number of bits.

[0320] However, downlink segmentation capability, energy state, and RA type cannot be quantified.

[0321] For example, the downlink segmentation capability of the first device may include two states: supporting downlink segmentation and not supporting downlink segmentation.

[0322] For example, the energy state of the first device can include two states: the first device has enough energy to complete the subsequent data transmission and the first device does not have enough energy to complete the subsequent data transmission.

[0323] For example, the RA type of the first device may include two types: CBRA and CFRA.

[0324] Storage capacity

[0325] Optionally, the storage capacity of the first device may refer to the amount of data that can be stored in at least one of the following areas of the first device: buffer; storage area; user area; register.

[0326] Accordingly, the storage capacity of the first device can be understood as the cache size of the first device.

[0327] For example, the amount of data that the buffer of the first device can store can be determined based on the buffer size of the first device.

[0328] For example, the amount of data that the storage area of ​​the first device can store can be determined based on the size of the storage area of ​​the first device.

[0329] For example, the amount of data that the user area of ​​the first device can store can be determined based on the size of the user area of ​​the first device.

[0330] For example, the amount of data that the registers of the first device can store can be determined based on the register size of the first device.

[0331] Alternatively, the storage capacity of the first device may also refer directly to the size of one or more of the aforementioned regions of the first device.

[0332] Alternatively, the storage capacity of the first device may also refer to the currently available cache size or the remaining cache size of the first device.

[0333] For example, the storage capacity of the first device may refer to the size currently available in at least one of the following areas of the first device: buffer; storage area; user area; register.

[0334] For example, the storage capacity of the first device can refer to the current remaining size of at least one of the following areas of the first device: buffer; storage area; user area; register.

[0335] Alternatively, the storage capacity of the first device may also refer to the maximum cache size that the first device can support.

[0336] For example, the storage capacity of the first device may refer to the size of at least one of the following areas supported by the first device: buffer; storage area; user area; register.

[0337] Optionally, the storage capacity of the first device may also refer to the temporary storage capacity of the first device, that is, the amount of data that the first device can temporarily store (e.g., in bits or bytes, or without limitation on the unit), which is the caching capacity of the first device.

[0338] It should be noted that the cache here can refer to the first device storing information in at least one of the following areas: buffer; storage area; user area; register; capacitor; latch.

[0339] Optionally, the temporary storage capability of the first device may refer to the first device's ability to store information relying on electrical charge or energy.

[0340] This can be understood as the first device no longer maintaining the temporarily stored information under at least one of the following conditions: the first device's power is depleted; the first device's energy is depleted; the first device's power is insufficient; the first device's energy is insufficient; the first device's power is below a threshold; the first device's energy is below a threshold.

[0341] Alternatively, the first device may maintain the temporarily stored information under at least one of the following conditions: the first device's power is not depleted; the first device's energy is not depleted; the first device's power is above a threshold; the first device's energy is above a threshold; the first device's power is sufficient; or the first device's energy is sufficient.

[0342] Alternatively, the storage capacity of the first device may also refer to the ability of the first device to retain information without relying on electricity or energy, that is, the ability of the first device to permanently store information.

[0343] Storage capacity is an important capability of the first device, especially for low-complexity first devices, where storage capacity can be related to various functions of the first device.

[0344] Optionally, storage capacity can be indicated by the number of bits or bits in increments. See the previous text for details, which will not be repeated here.

[0345] Alternatively, storage capacity can also be indicated based on its relationship to a threshold. For example, the first information could indicate that the buffer size of the first device is greater than a corresponding threshold.

[0346] Based on storage capacity, the second device can determine whether the first device supports various functions, which helps the second device manage the various functions of the first device.

[0347] Downlink segmentation capability

[0348] Downlink segmentation capability refers to whether the first device supports downlink segmentation from the second device to the first device. Downlink segmentation from the second device to the first device means that the second device sends data to the first device in segments.

[0349] For example, the first device is an A-IoT terminal, the second device is a base station, and the downlink segmentation capability from the second device to the first device is the R2D segmentation capability.

[0350] The prerequisite for the second device to send data to the first device in segments is that the first device can cache each data segment. Therefore, the downlink segmentation capability is also related to the cache of the first device.

[0351] Optionally, the first device can directly indicate whether it supports downlink segmentation through the first information.

[0352] In other words, the first information can directly indicate that the first device supports downlink segmentation, or the first information can directly indicate that the first device does not support downlink segmentation.

[0353] For example, the first information can indicate the downlink segmentation capability of the first device through a number of bits. When the number of bits is 1, it can indicate that the first device supports downlink segmentation, and conversely, when the number of bits is 0, it can indicate that the first device does not support downlink segmentation.

[0354] Based on downlink segmentation capability, the second device can determine whether to send data to the first device in segments.

[0355] Downlink data size

[0356] Downlink data size indicates the amount of downlink data supported by the first device, i.e., the amount of data sent from the second device to the first device. It should be noted that data size here refers to the amount of data (i.e., data length), not the numerical value of the data.

[0357] For example, the first device is an A-IoT terminal, the second device is a base station, and the downlink data size from the second device to the first device is the R2D data size (which can be simply referred to as R2D size).

[0358] The size of downlink data supported by the first device depends on the size of data that the first device can cache, so the size of downlink data is also related to the cache size of the first device.

[0359] Optionally, the downlink data size can be indicated by the number of bits or a range of bit counts supported by the first device. See the preceding text for details, which will not be repeated here.

[0360] Alternatively, the downlink data size can also be indicated based on its relationship to a threshold. For example, the first information could indicate that the downlink data size supported by the first device is greater than a corresponding threshold.

[0361] Based on the downlink data size, the second device can determine the size of the data to be sent to the first device.

[0362] BSR Ability

[0363] BSR capability indicates the size of data to be transmitted that the first device can support. The larger the amount of data buffered by the first device, the larger the amount of data to be transmitted that the first device can support.

[0364] It should be noted that BSR capability can also be referred to as the buffer size of uplink data to be transmitted.

[0365] Optionally, the BSR capability can be indicated by the number of bits of data to be transmitted supported by the first device, or by a bit count setting. See the preceding text for details, which will not be repeated here.

[0366] Alternatively, BSR capability can also be indicated based on its relationship with a threshold. For example, the first information could indicate that the size of the data to be transmitted that the first device can support is greater than the corresponding threshold.

[0367] Based on the BSR capability, the second device can determine the size of the data to be transmitted that the first device can support.

[0368] Energy state

[0369] The energy status can indicate whether the first device has sufficient energy to complete subsequent data transmission.

[0370] For example, if the energy of the first device is greater than the corresponding threshold, the first device can complete the subsequent data transmission; otherwise, the first device cannot complete the subsequent data transmission.

[0371] The energy state of the first device can affect the retention time of the cached information in the first device.

[0372] For example, information cached by the first device may be lost when the first device's power is depleted (or the power is below a threshold), meaning that the first device can only cache data when the power is sufficient.

[0373] Optionally, the energy status can also indicate the electrical status of the first device.

[0374] For example, the state of energy can also indicate whether the first device has sufficient power.

[0375] For example, the state of energy can also indicate how long the first device's electrical charge can sustain its operation.

[0376] For example, the energy status can also indicate how many bits of data the first device has enough power to sustain the transmission of.

[0377] Optionally, the energy status can also indicate the buffering capacity that the first device's power can support.

[0378] For example, the energy state can also indicate that the first device has enough power to cache N bits.

[0379] For example, the energy state can also indicate that the first device has enough power to buffer N bits and hold them for T time.

[0380] Optionally, the energy status can also indicate whether the first device has enough energy to activate the corresponding function, such as a high-energy-consuming function (e.g., activating a timer, transmitting more data, activating encryption, or enabling integrity protection).

[0381] Optionally, the energy status can be indicated based on a direct indication of whether the first device has sufficient energy to complete subsequent data transmission. That is, the first information can indicate whether the first device has enough or insufficient energy to complete subsequent data transmission.

[0382] For example, the first information can indicate the energy status of the first device through a number of bits. When the number of bits is 1, it means that the energy of the first device is sufficient to complete the subsequent data transmission. Conversely, when the number of bits is 0, it means that the energy of the first device is insufficient to complete the subsequent data transmission.

[0383] Based on the energy state, the second device can determine whether the first device is able to complete the subsequent data transmission.

[0384] Equipment type

[0385] Equipment type can refer to the type of the first device classified according to its capabilities or power consumption.

[0386] Taking the first device as an A-IoT terminal as an example, the device types of the A-IoT terminal can include device A, device B, and device C.

[0387] Alternatively, the device type of an A-IoT terminal can also include passive device, semi-passive device, and active device.

[0388] Alternatively, the device types of A-IoT terminals can also include device1 (representing device A or passive device), device2a (representing device B or semi-passive device), device2b (representing device B or semi-passive device), and device3 (representing active device or device C).

[0389] It should be noted that device2b consumes more power than device2a, and the hardware designs of device2b and device2a are different.

[0390] The name of the device type for the first device here is not restricted, and other names can also be used.

[0391] Different types of A-IoT terminals differ in at least one of their power consumption and energy storage.

[0392] For example, device 1 has low power consumption (around 1 microwatt), device 2a has higher power consumption (around 100 microwatts), device 2b has even higher power consumption than device 2a (around milliwatts), and device 3 has even higher power consumption. Accordingly, the higher the power consumption, the more energy it stores.

[0393] Different types of A-IoT terminals have different capabilities, including storage capacity, caching capacity, transmission rate, coverage, and application scenarios.

[0394] For example, device1 and device2a support reflection communication but do not support active signal transmission, device2b supports active signal transmission, and device3 has even stronger capabilities.

[0395] For example, device2a can support indoor scenes, while device2b can support outdoor scenes.

[0396] The cache size of the first device can be determined based on the device type. For example, for an A-IoT terminal, the cache sizes of device A, device B, and device C increase sequentially from smallest to largest.

[0397] Optionally, the device type of the first device can be indicated based on the number of bits. For example, different device types can be represented by different numbers of bits.

[0398] Based on the device type, the second device can determine the capabilities or power consumption of the first device.

[0399] RA type

[0400] RA type can refer to the RA type of the first device randomly connected to the second device.

[0401] For example, the RA type can include the CBRA or CFRA mentioned above.

[0402] For example, the RA type can also include the access type of the first device in different steps of the random access procedure, such as the access type of the first device in step 2 of the access procedure described above being CBRA, and the access type in step 3 of the access procedure described above being CBRA.

[0403] Optionally, the RA type of the first device can be indicated based on a number of bits.

[0404] For example, when the number of bits is 1, it can indicate that the RA type of the first device is CBRA, and conversely, when the number of bits is 0, it can indicate that the RA type of the first device is CFRA.

[0405] Based on the RA type, it helps the second device to determine how the first device connects to the second device.

[0406] Optionally, the cache-related capabilities of the first device may also include the capabilities related to the sampling clock frequency offset (SFO) of the first device.

[0407] For example, the SFO-related capabilities of the first device can be determined through the SFO of the first device. The SFO-related capabilities of the first device will affect the timing accuracy of the first device, and thus affect the corresponding functions of the first device.

[0408] Optionally, the SFO-related capabilities can be replaced with timing offset. The larger the SFO of the first device, the larger the timing offset of the first device. Accordingly, when the second device schedules time resources for the first device, it needs to reserve a larger time redundancy to allow for deviations in the first device. Consequently, the first device also needs to cache a larger amount of time information.

[0409] As an example, the first device is an A-IoT terminal, and the second device is a base station.

[0410] Base station for SFO=10 5 For an A-IoT terminal with a PPM (parts per million) rating, scheduling a 100ms time resource (e.g., when the A-IoT terminal transmits a D2R message at 100ms) requires reserving a 10% time margin. This means that due to SFO (Schedule Forwarding), the A-IoT terminal's D2R transmission time will be between 90 and 110ms. Similarly, the larger the SFO, the greater the total scheduling time for the base station.

[0411] If the base station needs to instruct the A-IoT terminal to send a D2R message (e.g., Msg1) using 10 time resources, considering the time offset, these 10 time resources will increase as the SFO of the A-IoT terminal increases. The longer the scheduling time, the more time information the A-IoT terminal needs to cache.

[0412] For example, the time resources scheduled by the base station are in units of 1ms. The 2-bit cache of the A-IoT terminal can cache time information from 0 to 3ms, and the 3-bit cache can cache time information from 0 to 7ms. If the A-IoT terminal needs to cache 127ms of time information, it needs to have a 7-bit cache.

[0413] Optionally, the SFO-related capabilities of the first device can also be replaced with timing capabilities. The longer the timing duration or the more accurate the timing of the first device, the more time information the first device needs to cache.

[0414] Based on the SFO-related capabilities, the second device can determine whether the first device supports the corresponding functions that require accurate timing.

[0415] Optionally, the indications among the above-mentioned cache-related capabilities can be combined with each other.

[0416] For example, the energy state can be combined with storage capacity, and the first information can indicate how many bits of cache the first device has sufficient energy state to maintain.

[0417] By instructing the second device on one or more cache-related capabilities, the second device can more accurately manage the various functions of the first device.

[0418] In some possible implementations, method 600 may further include: a response from the first device receiving first information from the second device.

[0419] Optionally, the response to the first information can indicate whether the first function is enabled or disabled.

[0420] Accordingly, the second device sends a response to the first information.

[0421] Optionally, the activation or deactivation of the first function can be determined by the second device.

[0422] Optionally, the second device can determine whether the first device should enable or disable the first function based on the cache-related capabilities of the first device indicated by the first information, that is, determine the response to the first information.

[0423] For example, if the cache-related capabilities of the first device can support the implementation of the first function, the second device can instruct the first device to enable the first function through the response to the first information. Otherwise, if the cache-related capabilities of the first device cannot support the implementation of the first function, the second device can instruct the first device to disable the first function through the response to the first information.

[0424] Optionally, the second device may also determine whether the first device should enable or disable the first function based on the cache-related capabilities of the first device indicated by the first information and the needs of the second device.

[0425] For example, if the cache-related capabilities of the first device can support the implementation of the first function, and the second device requires the first device to enable the first function, then the second device can instruct the first device to enable the first function through the response of the first information.

[0426] For example, if the cache-related capabilities of the first device can support the implementation of the first function, but the second device does not require the first device to enable the first function, the second device can instruct the first device to disable the first function through the response of the first information.

[0427] Accordingly, if the first device activates the first function, the first device can execute the workflow corresponding to the first function.

[0428] Alternatively, if the first device disables the first function, the first device may not execute the workflow corresponding to the first function, but instead execute a workflow other than the workflow corresponding to the first function (which may be called the baseline workflow).

[0429] Optionally, the activation or deactivation of the first function can also be indicated by the third device to the second device.

[0430] Accordingly, before the second device sends a response to the first device by sending the first information, the communication method 600 may further include: the third device sending a third information to the second device, the third information indicating whether the second function is enabled or disabled.

[0431] In other words, whether the first device turns the first function on or off can also be determined by the third device. It is understandable that the second function is the first function determined by the third device.

[0432] Correspondingly, the second device can also determine the response to the first information based on the third information.

[0433] Alternatively, the second device can directly transmit or forward the third information to the first device.

[0434] Alternatively, the second and third devices may jointly determine the first function.

[0435] Accordingly, the second device can instruct the first device, in response to the first information, to enable or disable the first function it determines, and to enable or disable the first function (i.e., the second function) determined by the third device.

[0436] Optionally, the first functions determined by the second and third devices may be the same or different.

[0437] For example, both the second and third devices can determine whether to enable the segmentation and retransmission functions of the first device.

[0438] For example, the second device can determine whether to enable the segmentation function of the first device, and the second device can determine whether to disable the retransmission function of the first device.

[0439] It should be noted that the difference in the first function determined by the second device and the third device can be understood as the difference in the second function and the first function determined by the second device.

[0440] Optionally, the response to the first information may also indicate the duration for which the first function is turned on or off. That is, the second or third device can determine the duration for which the first device turns the first function on or off.

[0441] Optionally, the third information from the third device may also indicate the duration for which the second function is turned on or off.

[0442] Optionally, the second or third device may determine whether to enable or disable the first function based on at least one of the following: size; status; type, corresponding to the cache-related capabilities.

[0443] Optionally, the response to the first information may also indicate the maximum number of time resources that the first device can randomly access the second device for.

[0444] In other words, the second device can also determine the maximum number of time resources that the first device can randomly access the second device based on the first information.

[0445] Optionally, the maximum number of time resources that the first device can randomly access the second device can be indicated by an R2D message or a random access trigger message. It should be noted that "indication" here can be replaced by "association" or "trigger".

[0446] The response based on the first information helps the first device to determine whether the first function is turned on or off.

[0447] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0448] Segmentation function

[0449] The segmentation function can refer to the data segmentation function between the second device and the first device.

[0450] For example, the segmentation function can be a downlink segmentation function, that is, the second device sends data to the first device in segments.

[0451] For example, the segmentation function can also be an uplink segmentation function, that is, the first device sends data to the second device in segments.

[0452] If the first device enables the segmentation function, it needs to buffer the segmented data received from the second device. Furthermore, the first device segments the data to be sent and buffers its own segmented data. It should be noted that the segmented messages, data packets, and segmented data in this application are interchangeable.

[0453] Accordingly, the first device needs to reassemble the segmented data sent by the second device from the cache.

[0454] For downlink segmentation, if the second device performs downlink segmentation transmission, after the first device receives each downlink message sent by the second device, since it has not received a complete message, the first device needs to buffer each segmented message.

[0455] Accordingly, if the first device receives an indication of segmented data (e.g., an indication that the data is segmented or that the data transmission is incomplete), the first device can buffer the segmented data. And / or, the first device can submit the segmented data to an upper layer for processing (e.g., the MAC layer or physical layer of the first device passes the segmented data to an upper layer (e.g., NAS or application layer)) so that the upper layer can parse the segmented data (e.g., read the content of the segment).

[0456] Optionally, the first device may also cache information related to downlink segment data, such as one or more of the following: (read or write) the location information of the downlink segment data, the size of the downlink segment data that has been transmitted (or the size of the downlink segment data to be transmitted), and the status of the downlink segment transmission being performed.

[0457] Accordingly, after receiving all segmented messages, the first device reassembles or merges all segmented messages to obtain a complete message, which is then processed or delivered to an upper layer (such as the NAS layer or application layer) through a lower layer (such as the MAC layer).

[0458] For example, if the downlink segmented data received by the first device indicates that the segmented data is the last segment of data, the first device can cache the downlink segmented data, merge all the received downlink segmented data, and submit the merged data to the upper layer for processing.

[0459] Therefore, the downlink segmentation function requires the first device to be able to cache a certain amount of data.

[0460] If the buffer size of the first device is insufficient to cache each segment of data, then the first device cannot support downlink segmentation.

[0461] For example, if the information related to downlink segmentation data is 50 bits, but the buffer size available to the first device is only 20 bits, then the first device cannot support downlink segmentation; conversely, if the buffer size available to the first device is not less than 50 bits, then the first device can support downlink segmentation.

[0462] For uplink segmentation, if the first device has insufficient transport blocks (TBS), the first device can perform uplink segmentation transmission and send uplink segmented data.

[0463] Accordingly, the first device may cache information related to the uplink segment data, such as one or more of the following: the location information of the uplink segment data, the size of the uplink segment data that has been transmitted (or the size of the uplink segment data to be transmitted), and the status of the uplink segment transmission being performed.

[0464] Correspondingly, the uplink segmentation function also requires the first device to be able to cache a certain amount of data. For details, please refer to downlink segmentation, which will not be elaborated here.

[0465] Conversely, if the first device disables the segmentation function, then the first device will not buffer the segmented data received from the second device. Furthermore, the first device will not segment the data to be transmitted.

[0466] Accordingly, if the first device receives an indication of segmented data (e.g., an indication that the data is segmented or that the data has not been fully transmitted), the first device discards the data.

[0467] retransmission function

[0468] The retransmission function can refer to the data retransmission function between the second device and the first device.

[0469] For example, the retransmission function can be a downlink retransmission function, that is, the function of the second device retransmitting the data that failed to be transmitted to the first device.

[0470] For example, the retransmission function can also be an uplink retransmission function, that is, the function of the first device to retransmit the data that failed to be transmitted to the second device.

[0471] It should be noted that retransmission includes retransmission of both unsegmented and segmented data.

[0472] If the first device enables the segmentation function, the retransmission function refers to the retransmission of segmented data between the second device and the first device.

[0473] Conversely, if the first device disables the segmentation function, the retransmission function refers to the retransmission of unsegmented data between the second device and the first device.

[0474] If the first device enables the retransmission function, the first device will correspondingly cache the unsegmented or segmented data sent by the second device, as well as the unsegmented or segmented data sent by the first device.

[0475] Taking uplink retransmission as an example, after the first device sends uplink data to the second device, it needs to buffer the data that has been transmitted (or has not yet been confirmed as successfully transmitted).

[0476] If the first device receives a negative acknowledgement (NACK) message from the second device, indicating that the data transmission of the first device has failed, the first device needs to resend the cached data.

[0477] It should be noted that the transmission failure here can refer to the failure of the first device to send or the failure of the second device to receive, and the name of the NACK message here is not limited.

[0478] Alternatively, if the first device determines that the data transmission has timed out or that the data transmission has failed, the first device also needs to retransmit the cached data.

[0479] If the buffer size of the first device is sufficient to buffer data that has been transmitted (or whose transmission has not yet been confirmed as successful), then the first device can support uplink retransmission.

[0480] Optionally, for uplink segmented retransmission, the first device needs to buffer one or more of the following: the data transmitted by the first device in the previous segment (i.e., the previous segment data); the starting position of the previous segment transmission by the first device; the size or sequence number of the data transmitted by the first device in the previous segment; multiple segments of data transmitted by the first device before; the starting position of the multiple segments of data transmitted by the first device before; the size or sequence number of the multiple segments of data transmitted by the first device before; the data transmitted in each segment by the first device; the starting position of each segment transmission by the first device; the size or sequence number of the data transmitted in each segment by the first device; the status of each segment transmission by the first device (including success, failure, or unacknowledged); and the size or sequence number of the data that the first device has successfully transmitted.

[0481] For example, when the first device receives a NACK message from the second device, the first device needs to retransmit the previous segment of data.

[0482] Conversely, when the first device receives an ACK message from the second device, the first device needs to transmit the next segment of data.

[0483] For example, when the first device receives a NACK message associated with the SN number from the second device, the first device needs to transmit segmented data associated with that SN number.

[0484] Taking downlink retransmission as an example, after the first device receives downlink data sent by the second device, it needs to cache the relevant information of the received data.

[0485] Optionally, for downlink segmented retransmission, the first device needs to buffer one or more of the following: the data transmitted by the second device in the previous segment (i.e., the previous segment data); the starting position of the previous segment transmission by the second device; the size or SN number of the data transmitted by the second device in the previous segment; the multiple segments of data transmitted by the second device before; the starting position of the multiple segments of data transmitted by the second device before; the size or SN number of the multiple segments of data transmitted by the second device before; the data transmitted in each segment by the second device; the starting position of each segment transmission by the second device; the size or SN number of each segment transmission by the second device; the status of each segment transmission by the second device (including success, failure, or unacknowledged); and the size or SN number of the data that the second device has successfully transmitted.

[0486] For example, the first device can send a NACK message associated with the SN to the second device to indicate to the second device that the downlink segment data transmission associated with the SN has failed.

[0487] It should be noted that the segmented data here can be segmented message packets or lower-level MAC packets.

[0488] It should be noted that the starting position here can be a relative position within the entire data to be transmitted. For example, for a complete 500-bit data to be transmitted, the starting position can be any position within those 500 bits (which can be replaced with bytes or bits, etc., and the unit is not limited).

[0489] Alternatively, the starting position here can also be the corresponding position in the storage area of ​​the first device (which can be replaced by bytes or bits, etc., and the unit is not limited).

[0490] It should be noted that the segmented data here can be segmented from upper-layer (such as NAS or application layer) data, such as segmenting NAS protocol data unit (PDU) or MAC service data unit (SDU).

[0491] Alternatively, the segmented data here can also be segmented packets of MAC layer data, such as segmenting MAC PDUs.

[0492] Optionally, the first device may indicate in the first information or other uplink message how many segments the first device supports, where the segments may be at least one of uplink segments and downlink segments.

[0493] For example, the first device can indicate that it supports one, two, or three segments.

[0494] Optionally, the first device may also indicate in the first information or other uplink message how many segments the first device supports for retransmission, where the segments can be at least one of uplink segments and downlink segments.

[0495] For example, the first device can indicate that it supports retransmission of one, two, or three segments.

[0496] If the buffer size of the first device is insufficient to buffer the transmitted (or the transmitted data has not yet been confirmed as successfully transmitted) data, the first device cannot support uplink retransmission.

[0497] If the buffer size of the first device is insufficient to cache the relevant information of the received data, the first device cannot support downlink retransmission.

[0498] Conversely, if the first device disables the retransmission function, then the first device will not cache the received unsegmented or segmented data sent by the second device, nor will it cache the unsegmented or segmented data sent by the first device.

[0499] Accordingly, taking uplink retransmission or uplink segmented retransmission as an example, if the first device disables the retransmission function, after the first device sends uplink data to the second device, it does not buffer the transmitted data.

[0500] Accordingly, taking downlink retransmission or downlink segmented retransmission as an example, if the first device disables the retransmission function, after receiving downlink data sent by the second device, the first device will not cache the relevant information of the received data.

[0501] Multi-service functions

[0502] Multi-service function can refer to the ability of the first device to perform multiple services in parallel.

[0503] For example, "the first device performs multiple services in parallel" can mean that the first device processes multiple services within a certain period of time. These services can be interleaved in time; for instance, the second service might be initiated before the first service has finished. It should be noted that "processing" here can also be replaced with "performing" or "participating."

[0504] Taking the first device as an A-IoT terminal as an example, the multi-service function can refer to the function of the first device to perform multiple services such as inventory and positioning in parallel.

[0505] Alternatively, the multiple services mentioned here may not be multiple types of services, but can be understood as multiple service requests from the core network.

[0506] For example, each service request can be associated with a session ID (or service ID, transaction ID, or task ID, with no restrictions on the name). This ID can be assigned by the core network or by the reader, without any restrictions.

[0507] It should be noted that the term "business" here can be replaced with "task," "session," "request," "transmission," "process," "procedure," "service," etc., and this application embodiment does not limit the terminology.

[0508] For example, inventory operations can also be called inventory tasks, inventory requests, inventory processes, or inventory transactions.

[0509] The business here can also refer to the process-related business that the first device executes based on a message associated with the business, which may include at least one of the following processes: access process, data transmission process (hereinafter referred to as data transmission process), etc., or it can be understood that the business is to perform the corresponding process.

[0510] The access procedure can be a random access procedure, such as contention-based random access or contention-free random access. The access procedure and the data transmission procedure are not strictly distinguished. The data transmission procedure is executed after the access procedure is completed. Alternatively, data transmission can occur within the access procedure itself.

[0511] For example, the first device can report service-related uplink data, such as device ID, during the access process.

[0512] It is worth noting that in this application, not every service corresponds to a single primary identifier such as a session ID or transaction ID. Instead, each service corresponds to a single process, which is assigned a session ID or transaction ID. Subsequent processes (such as a core network re-triggered or a "newly initiated" (not a retransmission) service request or paging) can be considered different session IDs or transaction IDs, even if they are the same type of service. Different session IDs or transaction IDs can correspond to different primary services. For example, if the core network initiates two inventory management services, the trigger messages or request messages (such as service requests or paging) corresponding to these two inventory management services can carry different session IDs or transaction IDs.

[0513] If the first device enables multiple services, it needs to distinguish whether each service has been successfully completed.

[0514] For example, if the first device has successfully reported the device ID in the first inventory service, but has not successfully reported the device ID in the second inventory service, then the first device does not need to respond to the first inventory service again.

[0515] To address this, the first device needs to cache each service and its corresponding state. The first device needs to cache at least the IDs of multiple services, such as session IDs or service IDs.

[0516] The status of each service here can include two states: successful data transmission and unsuccessful data transmission. Here, "transmitted data" can be replaced with "access". Accordingly, the first device can cache the status of each service using one bit.

[0517] Alternatively, the status of each service here can also include three states: paged and successfully transmitted data, paged but failed to transmit data, or not paged. Here, "paged" can be replaced by "stored," "selected," or "triggered," and "transmitted data" can be replaced by "accessed." Accordingly, the first device can cache the status of each service using 2 bits.

[0518] It should be noted that, here, being paging refers to the identification information of the first device satisfying or matching the paging message.

[0519] Taking session ID as an example, if the buffer size of the first device can only cache one session ID or does not support caching session ID, then the first device cannot support multiple service functions.

[0520] If the buffer size of the first device supports caching two session IDs, then the first device can support running two services in parallel, and so on.

[0521] Optionally, the first device may indicate the number of session IDs (without name limitation) that can be cached in the first message or other uplink message.

[0522] Alternatively, the first device may indicate the number of services that can be supported in the first information or other uplink messages.

[0523] Conversely, if the first device disables the multi-service function, then the first device will only cache the ID of the latest service, and will not cache the IDs of multiple services.

[0524] Alternatively, if the first device disables multi-service functionality, then the first device does not cache the service ID.

[0525] Accordingly, if the first device starts a new service, the first device can discard the ID of the original service.

[0526] Optionally, the number of services that the first device can execute in parallel can be indicated by the second or third device.

[0527] Optionally, the second or third device may also instruct the first device to release or reset the IDs of multiple cached services, so as to prevent the first device from caching the IDs of useless services for too long.

[0528] Optionally, the first device can also release or reset the IDs of services that have been cached for a certain period of time.

[0529] Optionally, the time of the ID of the service cached by the first device can be specified by the protocol, or the time of the ID of the service cached by the first device can be indicated to the first device by the second device or the third device.

[0530] Multi-process functionality

[0531] Multi-process functionality can refer to the ability of a first device to perform multiple processes in parallel, without limiting the number of processes.

[0532] If the first device enables multi-process functionality, then the first device caches multiple process IDs accordingly.

[0533] If the buffer size of the first device can only cache one process ID or does not support caching process IDs, then the first device cannot support multi-process functionality.

[0534] If the buffer size of the first device supports caching two process IDs, then the first device can support running two processes in parallel, and so on.

[0535] Optionally, the first device may indicate the number of process IDs that can be cached in the first message or other uplink message.

[0536] Alternatively, the first device may indicate the number of processes that can be supported in the first message or other uplink message.

[0537] Conversely, if the first device disables the multi-process function, then the first device will only cache the latest process ID, and will not cache multiple process IDs.

[0538] Alternatively, if the first device disables multi-process functionality, then the first device does not cache process IDs.

[0539] Accordingly, if the first device starts a new process, the first device can discard the original process ID.

[0540] Optionally, the number of processes in which the first device performs multiple processes in parallel can be indicated by the second or third device.

[0541] Optionally, the second or third device may also instruct the first device to release or reset the cached multi-process IDs to prevent the first device from caching useless process IDs for too long.

[0542] Optionally, the first device can also release or reset process IDs that have been cached for a certain period of time.

[0543] Optionally, the time for caching the process ID in the first device can be specified by the protocol, or the time for caching the process ID in the first device can be indicated to the first device by the second device or the third device.

[0544] Functionality to save the context of communication with multiple second devices

[0545] The function of saving the context of communication with multiple second devices can refer to the context caching function when the first device communicates with multiple second devices.

[0546] If the first device enables the function of saving the context of communication with multiple second devices, then the first device caches the context of communication with multiple second devices.

[0547] The context of communication between the first device and the second device may include the ID of the second device (an identifier used to identify different second devices, the name of which is not limited), transmission parameters associated with each second device (such as AS ID, transmission configuration such as encoding method, code length, bandwidth, etc.), and information such as the allocation of transmission resources (time domain, frequency domain, code domain resources, etc. used for transmission or access).

[0548] If the buffer size of the first device only supports communication under one second device, then the first device only needs to cache the context related to the second device, and / or the first device does not need to cache the identification information of the second device.

[0549] If the buffer size of the first device supports communication under multiple second devices, then the first device needs to cache the context related to multiple second devices.

[0550] If the buffer size of the first device can only cache the context of communication with one second device or does not support caching the context of communication with the second device, then the first device cannot support the function of saving the context of communication with multiple second devices.

[0551] If the buffer size of the first device can cache the context between the two second devices, then the first device can support the function of saving the context of communication with the two second devices, and so on.

[0552] Optionally, the first device may indicate the number of contexts that can be supported for caching in the first message or other uplink message.

[0553] Alternatively, the first device may indicate the number of second devices that can support communication in the first message or other uplink message.

[0554] Conversely, if the first device disables the function of saving the context of communication with multiple second devices, the first device only caches the context of the most recently communicated second device, and does not cache the context when communicating with multiple second devices.

[0555] Alternatively, if the first device disables the function of saving the context of communication with multiple second devices, then the first device does not cache the context when communicating with the second devices.

[0556] It should be noted that the second device with which the first device is most recently communicated can be replaced by the second device that successfully paged the first device.

[0557] Alternatively, if the first device disables the function of saving the context of communication with multiple second devices, then the first device does not cache the context of communication with the second devices.

[0558] Accordingly, if the first device initiates communication with the new second device, the first device can discard the original communication context.

[0559] Optionally, the number of second devices corresponding to the communication context cached by the first device can be indicated by the second device or the third device.

[0560] Optionally, the second or third device may also instruct the first device to release or reset the cached communication context to prevent the first device from caching useless context for too long.

[0561] Optionally, the first device may also release or reset communication contexts that have been cached for a certain period of time.

[0562] Optionally, the time for the first device to cache the communication context can be specified by the protocol, or the time for the first device to cache the communication context can be indicated to the first device by the second or third device.

[0563] Function to save encrypted parameters

[0564] The function of saving encrypted parameters can refer to the function of the first device caching encrypted parameters in the secure operation process. The encrypted parameters can be security keys or fresh numbers, etc.

[0565] For example, a secure operation process can refer to the encryption process at the NAS layer or the application layer; the encryption process can also be called an encryption operation.

[0566] For example, a security operation procedure can also refer to the integrity protection procedure at the NAS layer or the application layer. The integrity protection procedure can also be called an integrity protection operation.

[0567] Optionally, the first device may determine the encryption parameters based on at least one of the following: instruction from the second device; instruction from the third device; or generation by the first device.

[0568] If the first device enables the function of saving encrypted parameters, then the first device needs to cache the encrypted parameters.

[0569] Accordingly, the first device can send encrypted parameters to the second device, and the second device can forward or transmit the encrypted parameters to the third device.

[0570] Accordingly, the first device needs to encrypt the uplink data (e.g., perform hash processing) and decrypt the downlink data.

[0571] Taking the first device as an A-IoT terminal as an example, the encryption parameters can refer to the encryption parameters configured by the network (at least one of the reader and the core network), such as keys, freshness numbers, random numbers, etc. Encryption parameters can be used to encrypt data; for example, using the parameters as input, an algorithm can be used to encrypt the data. The encryption parameters need to be cached on the A-IoT terminal side for subsequent data encryption.

[0572] If the buffer size of the first device is sufficient to cache the encrypted parameters, then the first device can support the function of saving the encrypted parameters.

[0573] If the buffer size of the first device is insufficient to cache the encrypted parameters, then the first device cannot support the function of saving the encrypted parameters.

[0574] For example, if the key length of the encryption parameter is 100 bits, but the buffer size available to the first device is only 50 bits, then the first device cannot complete the caching of the encryption parameter.

[0575] Conversely, if the first device disables the function of saving encrypted parameters, then the first device will not cache the encrypted parameters.

[0576] Optionally, the number of encrypted parameters cached by the first device can be indicated by the second or third device.

[0577] Optionally, the second or third device may also instruct the first device to release or reset the cached encryption parameters to prevent the first device from caching useless encryption parameters for too long.

[0578] Optionally, the first function may also include the ability to send encrypted parameters.

[0579] Optionally, the first device can also release or reset encrypted parameters that have been cached for a certain period of time.

[0580] Optionally, the time for the first device to cache the encrypted parameters can be specified by the protocol, or the time for the first device to cache the encrypted parameters can be indicated to the first device by the second or third device.

[0581] Function to save integrity protection parameters

[0582] The function of saving integrity protection parameters can refer to the function of the first device in the security operation process of the integrity protection parameters, which may include the key, freshness number, etc. in the integrity protection process.

[0583] Optionally, the first device may determine the integrity protection parameters based on at least one of the following: indication by the second device; indication by the third device; or generation by the first device.

[0584] If the first device enables the function of saving integrity protection parameters, then the first device needs to cache the integrity protection parameters.

[0585] Accordingly, the first device can send the generated integrity protection parameters to the second device, and the second device can forward or pass through the integrity protection parameters to the third device.

[0586] Accordingly, the first device needs to perform integrity protection processing on the uplink data (such as hash processing) and integrity verification (removal of integrity protection) processing on the downlink data.

[0587] If the buffer size of the first device is sufficient to cache the integrity protection parameters, then the first device can support the function of saving the integrity protection parameters.

[0588] If the buffer size of the first device is insufficient to cache the integrity protection parameters, then the first device cannot support the function of saving the integrity protection parameters.

[0589] Conversely, if the first device disables the function of saving integrity protection parameters, then the first device does not cache the integrity protection parameters.

[0590] Optionally, the number of integrity protection parameters cached by the first device can be indicated by the second or third device.

[0591] Optionally, the second or third device may also instruct the first device to release or reset the cached integrity protection parameters to prevent the first device from caching useless integrity protection parameters for too long.

[0592] Optionally, the first device may also release or reset integrity protection parameters that have been cached for a certain period of time.

[0593] Optionally, the time for the first device to cache the integrity protection parameters may be specified by the protocol, or the time for the first device to cache the integrity protection parameters may be indicated to the first device by the second or third device.

[0594] Optionally, the first function may also include the ability to send integrity protection parameters.

[0595] Optionally, the first function may also include one of the following: verification; authentication; registration.

[0596] If the first device enables the verification function, then the first device needs to execute the corresponding verification process.

[0597] Conversely, if the first device disables the verification function, then the first device does not need to execute the corresponding verification process.

[0598] If the first device enables the authentication function, then the first device needs to execute the corresponding authentication process.

[0599] Conversely, if the first device disables the authentication function, then the first device does not need to execute the corresponding authentication process.

[0600] If the first device enables the registration function, then the first device needs to execute the corresponding registration process.

[0601] Conversely, if the first device disables the registration function, then the first device does not need to execute the corresponding registration process.

[0602] For example, the first device needs to send a registration request to the core network so that the core network can confirm whether the first device is legitimate or whether the first device's identity authentication has passed.

[0603] Accordingly, if the first device is legitimate or its identity is successfully authenticated, the first device can continue with subsequent processes, such as data transmission.

[0604] It should be noted that the aforementioned "first device activating different first functions" can be replaced by the first device receiving the Xth information instructing it to activate the corresponding function, or the aforementioned "first device activating different first functions" can be replaced by the first device receiving the ACK from the second device for the first information. Alternatively, the aforementioned "first device activating different first functions" can be replaced by the second device activating the first function by default, for example, the second device activating downlink segmentation by default. When the first device receives segmented data sent by the second device, the first device can know that the second device has activated the downlink segmentation function.

[0605] Furthermore, the aforementioned first device disabling different first functions can be replaced by the first device receiving the Y information indicating that the corresponding function should be disabled, or the aforementioned first device disabling different first functions can be replaced by the first device receiving the NACK from the second device for the first information, or the aforementioned first device disabling different first functions can be replaced by the second device disabling the first function by default, for example, the second device disabling downlink segmentation by default. When the first device receives unsegmented data sent by the second device, the first device can know that the second device has disabled the downlink segmentation function.

[0606] Instructions from the second device to enable or disable one or more functions of the first device help reduce the complexity of the first device's workflow and support scenarios where low-capacity and high-capacity first devices coexist.

[0607] The following section provides a detailed explanation of the relationship between caching capabilities and the primary function.

[0608] As mentioned above, a cache-related capability of the first device can be associated with multiple first functions of the first device, or multiple cache-related capabilities of the first device can be associated with a first function of the first device, or a cache-related capability of the first device can be associated with a first function of the first device.

[0609] As an example, the segmentation function of the first device can be associated with the downlink segmentation capability, storage capacity, downlink data size, energy status, etc., in the cache-related capabilities of the first device.

[0610] For example, downlink segmentation capability can determine whether the first device can support downlink segmentation.

[0611] For example, if the first device can support downlink segmentation, then the second device can segment the downlink data, that is, the downlink segmentation function of the first device can be enabled.

[0612] Conversely, if the first device cannot support downlink segmentation, the second device will not segment the downlink data, that is, the downlink segmentation function of the first device can be turned off.

[0613] For example, storage capacity can determine the amount of data that the first device can cache, which in turn limits the size of each piece of data that the first device can receive.

[0614] For example, in downlink communication between the first device and the second device, if the length of the unsegmented downlink data exceeds the storage capacity of the first device, the second device can segment the downlink data, that is, the downlink segmentation function of the first device can be enabled.

[0615] Conversely, if the length of the unsegmented downlink data does not exceed the storage capacity of the first device, the second device may not segment the downlink data, i.e., the downlink segmentation function of the first device may be turned off.

[0616] For example, the relationship between the downlink data size and storage capacity can determine whether downlink segmentation is necessary.

[0617] For example, if the size of the downlink data is greater than the storage capacity, meaning the first device cannot cache the complete downlink data, the second device can segment the downlink data, that is, the downlink segmentation function of the first device can be enabled.

[0618] Conversely, if the size of the downlink data is not greater than the storage capacity, that is, if the first device can cache the complete downlink data, then the second device does not segment the downlink data, that is, the downlink segmentation function of the first device can be turned off.

[0619] Taking the first device as an A-IoT terminal as an example, the size of the unsegmented downlink data is 32 bits, which requires the A-IoT terminal to be able to cache 32 bits of data. However, since temporary caching will bring additional power consumption and hardware costs, some A-IoT terminals may not support caching 32 bits of data and can only support writing 16 bits at a time. In this case, the reader can segment the downlink data.

[0620] For example, the energy state can determine whether the first device is able to reassemble segmented data received from the second device.

[0621] For example, if the first device has high energy, it can reassemble segmented data, and the second device can segment downlink data, thus enabling the downlink segmentation function of the first device.

[0622] Conversely, if the first device has low energy, it cannot reassemble the segmented data. In this case, the second device can choose not to segment the downlink data, which means it can disable the downlink segmentation function of the first device.

[0623] It should be noted that the downlink segmentation capability, storage capacity, downlink data size, and energy status of the first device can jointly determine the segmentation function of the first device.

[0624] As another example, the retransmission function of the first device can be associated with the storage capacity, energy status, etc., of the first device's cache-related capabilities.

[0625] For example, storage capacity can determine whether the first device is able to save data sent and received each time.

[0626] For example, if the first device can save the data sent and received each time, then the first device can retransmit the data, that is, the retransmission function of the first device can be enabled.

[0627] Conversely, if the first device cannot save the data sent and received each time, then the first device cannot retransmit the data, that is, the retransmission function of the first device can be turned off.

[0628] For example, the energy state can determine whether the first device can retransmit uplink data that failed to be transmitted.

[0629] For example, if the first device has high energy, it can retransmit failed uplink data, and the retransmission function of the first device can be enabled.

[0630] Conversely, if the first device has low energy, it will be unable to retransmit the failed uplink data, and the retransmission function of the first device can be turned off.

[0631] It should be noted that the storage capacity and energy state of the first device can jointly determine the retransmission function of the first device.

[0632] As another example, the multi-service functions and multi-process functions of the first device can be associated with the storage capacity, energy status, etc. of the first device.

[0633] For example, storage capacity can determine how many service IDs or process IDs the first device can store.

[0634] For example, if the first device can store the IDs of multiple services or multiple process IDs, then the first device can enable multi-service functionality or multi-process functionality.

[0635] Conversely, if the first device cannot save the IDs of multiple services or multiple process IDs, the first device can disable the multi-service function or the multi-process function.

[0636] For example, the state of energy can determine whether the first device can support the parallelism of multiple services or the parallelism of multiple processes.

[0637] For example, if the first device can support the parallel operation of multiple services or the parallel operation of multiple processes, then the first device can enable the multi-service function or the multi-process function.

[0638] Conversely, if the first device cannot support the parallel operation of multiple services or the parallel operation of multiple processes, the first device can disable the multi-service function or the multi-process function.

[0639] It should be noted that the storage capacity and energy status of the first device can jointly determine the multi-service function or multi-process function of the first device.

[0640] As yet another example, the first device's ability to save the context of communication with multiple second devices, its ability to save encryption parameters, and its ability to save integrity protection parameters can be associated with the first device's storage capacity, etc.

[0641] For example, storage capacity can determine whether the first device is able to save at least one of the following: communication context with multiple second devices; encryption parameters; integrity protection parameters.

[0642] For example, if the first device can save the communication context with multiple second devices, then the first device can enable the function of communicating with multiple second devices.

[0643] Conversely, if the first device cannot save the communication context with multiple second devices, the first device can disable the function of communicating with multiple second devices.

[0644] The functions of saving encryption parameters or saving integrity protection parameters are similar and will not be elaborated here.

[0645] It is worth noting that in some possible implementations, the first device may not indicate its own cache-related capabilities through the first information.

[0646] As an example, the second device may execute a certain process of the first function on the first device and determine whether the first device has cache-related capabilities associated with the first function based on the response of the first device.

[0647] Accordingly, if the first device has cache-related capabilities associated with the first function, the first device can respond to the process of the second device (e.g., send an ACK message to the second device).

[0648] Alternatively, if the first device does not have cache-related capabilities associated with the first function, the first device may not respond to the process of the second device, or the first device may send a NACK message to the second device.

[0649] For example, the first device is an A-IoT terminal, and the second device is a base station. The base station can send downlink segmented data (i.e., the process of executing downlink segmentation function) to the A-IoT terminal.

[0650] Accordingly, if the A-IoT terminal has the capability to support downlink segmentation, such as downlink segmentation capability in the cache-related capabilities, then the A-IoT terminal can send an ACK message to the base station in response.

[0651] Alternatively, if the A-IoT terminal does not have the downlink segmentation capability or other capabilities that support downlink segmentation, the A-IoT terminal can send a NACK message to the base station or not respond to the base station.

[0652] Accordingly, the base station can determine whether the A-IoT terminal has the capability to support downlink segmentation, such as downlink segmentation capability, in the cache-related capabilities based on the A-IoT terminal's response.

[0653] Optionally, the base station may send the capabilities of the A-IoT terminal, determined based on the response of the A-IoT terminal, to the CN.

[0654] Optionally, when the base station transmits the A-IoT terminal's capabilities to the CN, it can associate a device ID to identify the A-IoT terminal.

[0655] Alternatively, the base station may send the capabilities of the A-IoT terminal group, determined based on the responses of the A-IoT terminals in the A-IoT terminal group, to the CN.

[0656] For example, the first device is an A-IoT terminal, and the second device is a base station. The base station can send downlink segmented data to the A-IoT terminal group.

[0657] Accordingly, if all A-IoT terminals in the A-IoT terminal group respond to the base station, the base station can determine that all A-IoT terminals in the A-IoT terminal group have the downlink segmentation capability and other capabilities that support downlink segmentation functionality.

[0658] Alternatively, if all A-IoT terminals in the A-IoT terminal group send a NACK message to the base station or none of them respond to the base station, the base station can determine that none of the A-IoT terminals in the A-IoT terminal group have the downlink segmentation capability or other capabilities that support downlink segmentation functions, which are related to caching capabilities.

[0659] Accordingly, when the base station sends the capability of the A-IoT terminal group to the CN, it can associate the group ID to identify the A-IoT terminal group.

[0660] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off.

[0661] In other words, the second device can directly instruct the first device to turn the first function on or off by receiving the response to the first information (i.e., the first response).

[0662] Alternatively, in some other possible implementations, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate that the first function is turned on or off.

[0663] In other words, the second device can instruct the first device to turn the first function on or off through additional instructions (i.e., second information), in addition to the response indicating receipt of the first information (i.e., the first response).

[0664] Optionally, the response to the second or first information can be indicated by a single bit to enable or disable the first function.

[0665] For example, a value of 1 in this bit position can indicate that the first function is enabled. Conversely, a value of 0 in this bit position can indicate that the first function is disabled.

[0666] Optionally, if the second device instructs the first device to enable the first function, the second information or the response to the first information may instruct the first device to execute the configuration information of the first function.

[0667] In other words, the second device may not directly instruct the first device to enable the first function, but may indirectly instruct the first device to enable the first function by instructing the first device to execute the configuration information corresponding to the first function.

[0668] For example, if the first function is a multi-process function, then the response to the second or first information can indicate the number of processes in the multi-process function.

[0669] Optionally, the response to the second or first information may indicate to enable or disable one or more first functions.

[0670] Based on this, it helps the first device to determine whether to turn the first function on or off.

[0671] It should be noted that in some other possible implementations, the second device may not instruct the first device to enable or disable the first function, but instead enable or disable the first function by default based on the cache-related capabilities of the first device.

[0672] For example, if the second device determines that the first device can support downlink segmentation based on the cache-related capabilities of the first device, then the second device can send data to the first device in segments.

[0673] For example, if the second device determines that the first device cannot support multi-service functions based on the cache-related capabilities of the first device, then the second device may not initiate a multi-service process to the first device.

[0674] Accordingly, in this implementation, the second device may not respond to the first information from the first device.

[0675] Therefore, the second device does not need to indicate whether the first function is turned on or off, which helps to save the instruction cost of the second device.

[0676] The timing of sending the first message will be explained in detail below.

[0677] In some possible implementations, the first device may send first information based on the capability reporting request of the second device. That is, before step S610, method 600 may further include: the first device receiving the capability reporting request of the second device.

[0678] Optionally, the capability reporting request of the second device may indicate the reporting of one or more capabilities.

[0679] Optionally, the capability reporting request of the second device can indicate the capability that the first device needs to report through one or more information cells.

[0680] Optionally, the second device may indicate one or more capabilities via a cell.

[0681] Optionally, the method of transmitting the capability reporting request of the second device is not limited.

[0682] As an example, a capability reporting request can be carried out in a single message.

[0683] For example, if the first device is an A-IoT terminal, the capability reporting request can be carried in a single R2D message, which can be called a "capability request message".

[0684] As another example, a capability reporting request can also be carried in a single message along with other information that needs to be sent to the first device.

[0685] For example, if the first device is an A-IOT terminal, the capability reporting request can be carried in the paging message, which is compatible with CBRA and CFRA in the A-IOT random access procedure described above.

[0686] Alternatively, the capability reporting request can also be carried in Msg2 in the A-IOT random access procedure described above, which is suitable for CBRA in step 3 of the A-IOT random access procedure described above.

[0687] Alternatively, the capability reporting request can be carried in at least one of the R2D scheduling message and the D2R scheduling message. The R2D scheduling message can be used to schedule R2D messages or R2D transmissions, and the D2R scheduling message can be used to schedule D2R messages or D2R transmissions.

[0688] Optionally, the capability reporting request can also be sent from the third device to the second device, and then transmitted or forwarded by the second device to the first device.

[0689] It should be noted that the messages, information, signaling, and data in the embodiments of this application are interchangeable and this application does not impose any limitations.

[0690] Based on the capability reporting request, the first device can determine the timing of sending the first information.

[0691] In some other possible implementations, the first information may be a response from the first device to the fourth information from the second device, which may indicate the cache-related capabilities of the first device.

[0692] For example, the second device can indicate the cache-related capabilities it needs through the fourth information, and if the first device has the cache-related capabilities, the first device can respond through the first information.

[0693] Accordingly, the second device can determine, based on the first information, that the first device has the cache-related capabilities indicated by the fourth information.

[0694] Optionally, the timing of the second device sending the fourth information is not limited.

[0695] For example, the second device can send a fourth message during the paging process, which can be carried in the paging message (random access trigger message).

[0696] For example, the second device can also send a fourth message before paging.

[0697] For example, the second device can also send a fourth message during the time between paging and receiving the first message.

[0698] Based on the fourth piece of information, it helps to save on the reporting costs of the first device.

[0699] In some other possible implementations, the first device may send the first information by default, without relying on requests from the second or third device.

[0700] For example, the first device periodically sends first information, and the duration of the period is not limited.

[0701] Therefore, the second or third device does not need to send capability reporting requests, which helps to save the cost of the second or third device.

[0702] In some possible implementations, the first information can be sent when the cache-related capabilities meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0703] In other words, when the cache-related capabilities meet the first condition, the first device can send the first information.

[0704] Alternatively, if the cache-related capabilities do not meet the first condition, the first device may not send the first information.

[0705] Optionally, the first capability requirement may refer to one or more of the following requirements for cache-related capabilities: size; state; type.

[0706] As an example, for quantifiable cache-related capabilities, the first capability requirement can refer to the requirement for the size of cache-related capabilities.

[0707] For example, the first capability requirement can refer to the requirement regarding the relationship between cache-related capabilities and the corresponding threshold. For instance, the first capability requirement could require that the cache-related capabilities be greater than the corresponding threshold. Alternatively, the first capability requirement could also require that the size of the cache-related capabilities be within the range of the corresponding threshold.

[0708] As another example, for cache-related capabilities that cannot be quantified, the first capability requirement can refer to a limitation on the state or type of the cache-related capability. For example, for the RA type, the first capability requirement could be that the RA type is CBRA. Similarly, for energy state, the first capability requirement could be that the energy state is sufficient.

[0709] Optionally, the first capability requirement can be agreed upon through an agreement.

[0710] Alternatively, the first capability requirement may be indicated to the first device by the second or third device.

[0711] Optionally, in this implementation, the first information can be sent based on the capabilities of the second or third device, and a reporting request can be sent.

[0712] In other words, after receiving a capability reporting request, if the first device determines that the cache-related capability meets the first condition, the first device can send the first information.

[0713] Conversely, if the first device determines that the cache-related capabilities do not meet the first condition after receiving the capability reporting request, the first device may not send the first information.

[0714] Alternatively, in this implementation, the first information can be sent by default by the first device, meaning that the second or third device does not need to send a capability reporting request to the first device.

[0715] In other words, if the first device determines that the cache-related capabilities meet the first condition, the first device can send the first information.

[0716] Conversely, if the first device determines that the cache-related capabilities do not meet the first condition, the first device may not send the first information.

[0717] Based on the first condition, it helps to save on the cost of the first device.

[0718] In some possible implementations, if the first device does not support the quantization of cache-related capabilities, it can indicate that its cache-related capabilities are set to default by using the first information. It is worth noting that quantization here can also be replaced by calculation or determination.

[0719] Default capabilities can refer to the most basic or fundamental capabilities of a first device. For example, default capabilities could be the capabilities possessed by a first device with the simplest configuration or the lowest complexity. It is worth noting that default capabilities can also be called basic capabilities or fundamental capabilities.

[0720] As an example, for quantifiable cache-related capabilities, the default cache-related capability can be understood as the cache-related capability being the default value.

[0721] Optionally, the default value for cache-related capabilities can be the minimum value. For example, if the first device does not support quantizing its own buffer size, the first device can indicate that its own buffer size is the minimum buffer size through the first information.

[0722] Optionally, the default values ​​for caching-related capabilities can be based on protocol agreements.

[0723] Alternatively, the default value for cache-related capabilities can be indicated to the first device by the second or third device.

[0724] As another example, for cache-related capabilities that cannot be quantified, the default cache-related capability can be understood as a basic capability.

[0725] For example, if the first device does not support determining its own RA type, the first device can indicate its own RA type through the first information as the RA type of the first device with the simplest configuration.

[0726] Optionally, the default capabilities of the first device can be based on protocol agreements.

[0727] Alternatively, the default capability of the first device may be indicated to the first device by the second or third device.

[0728] Based on this, it is helpful to adapt to different first devices to ensure the normal operation of the first device.

[0729] In some possible implementations, the first information may also be sent from the third device to the second device.

[0730] In other words, the cache-related capabilities of the first device can also be indicated to the second device by the third device.

[0731] Optionally, the third device may send multiple first messages corresponding to the first device to the second device.

[0732] Based on this, it helps the second device to acquire the cache-related capabilities of multiple first devices.

[0733] Optionally, the timing of the third device sending the first information to the second device is not limited.

[0734] As an example, the third device can send the first message to the second device before the second device is paged.

[0735] For example, the third device may send the first information to the second device via a service request message or other messages before the second device is paged.

[0736] Optionally, the first message sent by the third device before the second device pagees may indicate at least one of the following: cache-related capabilities and the device ID of the first device having the cache-related capabilities; or the group ID of the group of first devices having the cache-related capabilities.

[0737] For example, the first information of the third device may indicate capability 1, the device ID of the first device having capability 1, and the group ID of the group of the first devices having capability 1. Capability 1 may indicate one or more capabilities as described above.

[0738] Accordingly, after receiving the first information sent by the third device before paging, the second device can also indicate at least one of the device ID and group ID in the first information in the paging message. It should be noted that the device ID and group ID here can be passed through by the second device to the first device.

[0739] Accordingly, when the second device paging, the first device indicated by at least one of the device ID and group ID in the paging message can respond according to the paging message, that is, the first device responding to the paging message of the second device is the first device with capability 1.

[0740] Accordingly, the first device with capability 1 can participate in subsequent random access, data transmission and other processes.

[0741] As another example, the third device may also send the first message to the second device after the second device has paged it.

[0742] For example, the third device may send the first information to the second device after the first device has connected to the second device.

[0743] Optionally, the second device may send the device ID of the first device or other uplink data for identifying the first device to the third device after paging, so that the third device can determine the buffer-related capabilities of the first device based on the device ID and instruct the second device through the first information.

[0744] Optionally, the device ID of the first device can be reported to the second device after the first device connects to the second device.

[0745] For example, the first device is an A-IoT terminal and the second device is a base station. The first device can indicate its device ID to the second device in the Msg3 of the random access procedure described above, and the second device can correspondingly send the device ID of the first device to the third device through uplink data.

[0746] It should be noted that the third device may also instruct the second device on the cache-related capabilities of the first device through information other than the first information. For example, the other information besides the first information may be information related to the cache capabilities of the first device or the Nth information, and the name of the other information is not limited. The corresponding content of the other information besides the first information can be found in the first information, and will not be repeated here.

[0747] It should be noted that in this implementation, the second device can send second information to the first device based on the first information sent by the third device or other information besides the first information mentioned above. The second information can instruct the first function to be turned on or off.

[0748] In other words, the second device can determine whether the first function is enabled or disabled based on the cache-related capabilities of the first device as indicated by the third device.

[0749] Optionally, the third device may also indicate the cache-related capabilities of the first device to the second device through multiple first messages or other messages besides the aforementioned first messages. See also the example of the first device sending multiple first messages, which will not be repeated here.

[0750] Instructing the first device on its cache-related capabilities via the third device to the second device helps reduce air interface overhead between the first and second devices.

[0751] In some possible implementations, the first information may also be sent to the second device by both the third device and the first device.

[0752] In other words, both the third device and the first device can send first information to the second device to indicate the cache-related capabilities of the first device.

[0753] Optionally, the first information sent by the third device and the first information sent by the first device may be the same or different.

[0754] In other words, the cache-related capabilities indicated by the third device and the cache-related capabilities indicated by the first device can be the same or different.

[0755] For example, both the third device and the first device can indicate the storage capacity of the first device through the first information.

[0756] For example, the third device can indicate the storage capacity of the first device through the first information, and the first device can indicate the device type of the first device through the first information.

[0757] Optionally, the first information sent by the third device may be associated with one or more of the following: device group ID, which may indicate the ID of the device group to which the first device belongs; device mask, which may be used to match one or more first devices; device ID, which may indicate the ID of the first device; deployment area information, which may indicate the deployment area of ​​the first device; and deployment time information, which may indicate the deployment time of the first device.

[0758] For example, the third device can send the first information corresponding to the first device of a device group corresponding to the device group ID to the second device through the device ID.

[0759] For example, a third device can send first information to a second device that corresponds to a first device with a device mask.

[0760] For example, the third device can send the first information corresponding to the first device, which corresponds to the device ID, to the second device.

[0761] For example, the third device can send first information corresponding to multiple first devices deployed in a deployment area to the second device.

[0762] For example, the third device can send the first information corresponding to multiple first devices deployed within a certain deployment period to the second device.

[0763] Based on this, it helps the third device to clearly indicate to the second device which cache-related capabilities of the first device are available.

[0764] Optionally, before the third device sends the first information to the second device, the second device may send the device ID of the first device to the third device, and the device ID may be used to determine the first information.

[0765] In other words, the second device can indicate to the third device which cache-related capabilities of the first device it needs.

[0766] Based on this, the third device can determine which cache-related capabilities of the first device the second device needs.

[0767] The following is combined with Figures 7-16 The communication method 600 is illustrated by example. For instance, in the following example, the first device is an A-IoT terminal.

[0768] As an example, when the first device is an A-IoT terminal, the second device can be a base station in a 5G communication system (i.e., the base station acts as a reader), and the third device can be core network equipment.

[0769] The topology between the base station and the A-IoT terminal can be as follows: Figure 7 As shown in the diagram. In this topology, the base station and the A-IoT terminal can communicate directly in both directions, and the communication between the base station and the A-IoT terminal can include A-IoT data.

[0770] This topology can include base stations that send data to A-IoT terminals and base stations that receive data from A-IoT terminals, meaning that there is uplink and downlink data between the base stations and A-IoT terminals.

[0771] Alternatively, the topology between the base station and the A-IoT terminal can also be as follows: Figure 8 As shown in the diagram. In this topology, the base station and the A-IoT terminal can communicate bidirectionally based on the intermediate node between them.

[0772] In this topology, intermediate nodes can be repeaters, IAB nodes, terminal devices, etc., and these intermediate nodes can implement A-IoT technology. Intermediate nodes can transmit A-IoT data between base stations and A-IoT terminals.

[0773] Alternatively, the topology between the base station and the A-IoT terminal can also be as follows: Figure 9 or Figure 10 As shown in the diagram. In both topologies, the base station and the A-IoT terminal can communicate unidirectionally based on auxiliary nodes between the base station and the A-IoT terminal.

[0774] exist Figure 9 In the topology shown, the A-IoT terminal sends data to the base station and receives data from the base station from the auxiliary node.

[0775] exist Figure 10 In the topology shown, the A-IOT terminal receives data from the base station and sends data back to the base station through the auxiliary node.

[0776] In both of these topologies, auxiliary nodes can be repeaters, IABs, terminal devices, etc., which can implement A-IoT technology.

[0777] When communication method 600 is applied in this example, it can be as follows: Figure 11 As shown, it includes steps 1-3.

[0778] In step 1, the BS sends a paging message to the A-IOT terminal, which carries a capability reporting request.

[0779] In step 2, the A-IoT terminal reports cache-related capabilities to the BS through device capability messages (i.e., the first information). Cache-related capabilities may include buffer size, R2D size, energy status, and other capabilities.

[0780] Optionally, the BS can pass through or forward the cache-related capabilities reported by the A-IOT terminal to the CN.

[0781] In step 3, the BS sends an ACK message (i.e., a response to the first information) to the A-IOT terminal. The ACK message carries an indication to enable the first function.

[0782] Optionally, the first function can be indicated to the BS by the CN.

[0783] Alternatively, the caching capabilities of the A-IoT terminal can also be indicated to the BS by the CN.

[0784] For example, the CN can indicate the cache-related capabilities of the A-IoT terminal to the BS before paging. Therefore, when communication method 600 is applied in this example, it can also be as follows: Figure 12 As shown, it includes steps 1 through 6.

[0785] In step 1, CN sends a service request to BS. The service request carries the cache-related capabilities of the A-IoT terminal, which may include buffer size, R2D size, energy status, and other capabilities.

[0786] In step 2, the BS sends a paging message to the A-IOT terminal.

[0787] In step 3, the BS instructs the A-IOT terminal to enable or disable the first function.

[0788] Steps 4-6 describe the process of A-IOT terminals randomly accessing the BS, which will not be elaborated here.

[0789] Alternatively, the CN can also indicate the cache-related capabilities of the A-IoT terminal to the BS after the A-IoT terminal randomly accesses the BS. Therefore, when communication method 600 is applied in this example, it can also be as follows: Figure 13 As shown, it includes steps 1 through 7.

[0790] In step 1, the BS sends a paging message to the A-IOT terminal.

[0791] Steps 2-4 describe the process of A-IoT terminals randomly accessing the BS, which will not be elaborated here.

[0792] In step 5, the BS sends uplink data to the CN, which may include the device ID of the A-IoT terminal.

[0793] In step 6, CN indicates the cache-related capabilities of the A-IOT terminal to BS.

[0794] In step 7, the BS instructs the A-IOT terminal to enable or disable the first function.

[0795] Optionally, the first function can be indicated to the BS by the CN.

[0796] Optionally, the CN can indicate the first function to the BS via downlink data.

[0797] As another example, when the first device is an A-IoT terminal, the second device can also be a terminal device in a 5G communication system, and the third device can be a core network device.

[0798] The topology between terminal devices and A-IoT terminals can be as follows: Figure 14 As shown in the diagram. In this topology, the A-IoT terminal communicates bidirectionally with the terminal device, and the communication between the terminal device and the A-IoT terminal can include environmental IoT data.

[0799] In this example, the cache-related capabilities of the A-IOT terminal can be indicated by the CN to the BS, and the BS forwards them to the UE.

[0800] Alternatively, the caching capabilities of the A-IoT terminal can be sent from the CN to the UE, and then transparently transmitted from the BS to the UE.

[0801] Alternatively, the cache-related capabilities of the A-IoT terminal can be directly generated by the BS and sent to the UE.

[0802] There is no limitation on when to send the cache-related capabilities of the A-IOT terminal to the UE.

[0803] For example, the caching-related capabilities of an A-IoT terminal can be sent to the UE before the service, such as before paging, or in or before the service request.

[0804] Therefore, as Figure 15 As shown, when the communication method 600 is applied to this example, it may include steps 1-6.

[0805] In step 1, the BS indicates the cache-related capabilities of the A-IOT terminal to the UE via RRC signaling.

[0806] Optionally, caching-related capabilities can be indicated to the BS by the CN.

[0807] In step 2, the UE sends a paging message to the A-IOT terminal.

[0808] Steps 3-5 describe the process of A-IOT terminal randomly accessing UE, which will not be elaborated here.

[0809] In step 6, the UE instructs the A-IOT terminal to enable or disable the first function.

[0810] Alternatively, the caching capabilities of the A-IoT terminal can also be sent to the UE during service operation, such as after the CN receives UL data (e.g., UL data including the device ID) and sends it to the UE.

[0811] Therefore, as Figure 16 As shown, when the communication method 600 is applied to this example, it may include steps 1-7.

[0812] In step 1, the UE sends a paging message to the A-IOT terminal.

[0813] Steps 2-4 describe the process of A-IOT terminals randomly accessing the UE, which will not be elaborated here.

[0814] In step 5, the UE sends uplink data to the BS, which may include the device ID of the A-IOT terminal.

[0815] Optionally, the BS can forward or pass through the device ID to the CN.

[0816] In step 6, the BS indicates the cache-related capabilities of the A-IOT terminal to the UE.

[0817] Optionally, caching-related capabilities can be indicated to the BS by the CN.

[0818] In step 7, the UE instructs the A-IOT terminal to enable or disable the first function.

[0819] Optionally, the first function can be indicated by the CN to the BS, and by the BS to the UE.

[0820] Optionally, the CN can indicate the first function to the BS via downlink data.

[0821] As yet another example, when the first device is an A-IoT terminal, the second device can also be a 5G communication system including RIC (integrated circuitry). Figure 3 Taking the architecture shown as an example, the base station (equivalent to the base station being split into three modules: RIC, CU, and DU) and the third device can be core network equipment.

[0822] In this example, the RIC can determine the caching capabilities of at least one of the following A-IoT terminals based on prior information and instruct the CU accordingly: A-IoT terminals deployed within the current coverage area; A-IoT terminals deployed in a specific area; and A-IoT terminals deployed within a specific time period. The RIC can also instruct the CU to enable or disable the first function and for how long. The CU and DU modules can transmit this information accordingly.

[0823] Compared to other examples, this example adds signaling interaction where the RIC provides prior information to the CU or instructs the CU whether a function is enabled or disabled; the remaining steps are unaffected. The remaining steps can be found in other examples and will not be repeated here.

[0824] Optionally, RIC can collect relevant historical data to obtain prior information.

[0825] It should be noted that in the three examples above, the system may also include a helper or incentive source. The helper or incentive source can be a terminal, a base station, or a small station. This device only has downlink communication with the A-IoT terminal, but has uplink and downlink data transmission with the reader, which may be through an air interface or through a wired connection.

[0826] Based on the methods in the examples above, readers can determine which optional functions of the A-IoT terminal to enable based on their own needs and the caching capabilities of the A-IoT terminal, thereby reducing the complexity of the A-IoT terminal workflow and supporting scenarios where low-capability and high-capability A-IoT terminals coexist.

[0827] It should be noted that in the embodiments of this application, "downlink" can be replaced with "R2D" or "RD", and "uplink" can be replaced with "D2R" or "DR".

[0828] It should be noted that the signaling names involved in the embodiments of this application can be extended as follows.

[0829] Select signaling can be extended to paging, (initial)trigger message, and (initial)triggermessage indication.

[0830] Query signaling can be extended to access round trigger or access round indication.

[0831] QueryRep signaling can be extended to either (next) access occasion trigger or (next) access occasion indication.

[0832] RN signaling can be extended to random access ID.

[0833] ACK signaling can be extended to an access ID response.

[0834] EPC signaling can be extended to UL data or device ID.

[0835] It should be noted that the signaling functions involved in the embodiments of this application can be as follows.

[0836] The Query (which can be replaced with an extended signaling name) can be used to trigger at least one access opportunity, such as directly or indirectly indicating the total number of access opportunities, or it can be used to trigger the first access opportunity.

[0837] QueyRep (which can be replaced with an extended signaling name) can be used to trigger the next access opportunity, or it can be understood as indicating the boundary of an access opportunity (the boundary between the start and end).

[0838] The aforementioned access opportunity can also be described as access timing, access time slot, etc. Each access opportunity may allow the first device to perform at least one of the following processes: sending access (request); contention resolution; data transmission, etc.

[0839] Paging can be used to instruct A-IoT terminals (hereinafter referred to as devices) to access the reader.

[0840] For example, when the reader is a base station or access network device, paging can be used to indicate that the device is connected to the network;

[0841] For example, when the reader is a terminal device, paging can be used to instruct the device to connect to the terminal device. Optionally, the device can connect to the network through the terminal device.

[0842] Paging can also be used to trigger a device to send uplink data or to trigger a device to perform a first service, which may include at least one of the following: paging service, inventory service, command service (such as read, write, deactivate, lock, etc.), positioning service, sensing service, etc.

[0843] Paging, also known as (initial) DL trigger message, can be triggered by core network elements (such as AMF, ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), etc.).

[0844] For example, a core network element sends a first service request message or a paging message to a network device. The first service can be an inventory service, a command service, or a location service, etc. The network device confirms the first service (request) message or the paging (request) message and sends the first information.

[0845] RN (which can be replaced with an extended signaling name) can be used for contention resolution, or to distinguish different UEs during random access procedures or contention resolution.

[0846] ACK (which can be replaced with an extended signaling name) can be used to indicate whether contention resolution was successful. Optionally, ACK can be associated with the device by carrying a contention resolution identifier.

[0847] It should be noted that the trigger in the above signaling function description can also be replaced with indication, association or request.

[0848] The above combination Figures 7 to 16 This document describes in detail the communication method provided in the embodiments of this application. The following section, in conjunction with... Figures 17 to 19 This application provides a detailed description of the communication device provided in the embodiments of this application.

[0849] Figure 17 A schematic block diagram of a communication device 1700 provided in an embodiment of this application is shown. The device 1700 can be used to perform the communication method 600 described above.

[0850] The device 1700 may correspond to the first device described in the method 600 above, or it may correspond to a module or component of the first device.

[0851] The apparatus 1700 may include at least one unit or module for performing any one of the methods 600 described above.

[0852] Furthermore, each module or unit in the device 1700 can be used to perform the actions or processes performed by the first device in the method 600 described above.

[0853] like Figure 17 As shown, the communication device 1700 may include a processing module 1710 and a transceiver module 1720.

[0854] The processing module 1710 can be used to determine the first information.

[0855] The transceiver module 1720 can be used to send first information, which can indicate the buffer-related capabilities of the first device.

[0856] Optionally, the cache-related capabilities of the first device can be associated with the first function of the first device.

[0857] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0858] In some possible implementations, the transceiver module 1720 may also be used to receive a response to the first information from the second device, the response to the first information indicating whether the first function is enabled or disabled.

[0859] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0860] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0861] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0862] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0863] It should be understood that the processing module 1710 or the transceiver module 1720 can be used to execute the various actions or processing procedures performed by the first device in the above-described communication method 600.

[0864] It should be understood that the specific process of each module in device 1700 performing the above-mentioned corresponding steps is described in the previous description of communication method 600, and will not be repeated here.

[0865] Figure 18 A schematic block diagram of another communication device 1800 provided in an embodiment of this application is shown. This device 1800 can be used to perform the above-described communication method 600.

[0866] The device 1800 may correspond to the second device described in the above communication method 600, or it may correspond to a module or component of the second device.

[0867] The device 1800 may include at least one unit or module for performing any one of the communication methods 600 described above.

[0868] Furthermore, each module or unit in the device 1800 can be used to perform the actions or processes performed by the second device in the aforementioned communication method 600.

[0869] like Figure 18 As shown, the communication device 1800 may include a transceiver module 1810 and a processing module 1820.

[0870] The transceiver module 1810 can be used to receive first information, which can indicate the buffer-related capabilities of the first device.

[0871] Optionally, the cache-related capabilities of the first device can be associated with the first function of the first device.

[0872] The processing module 1820 can be used to determine the cache-related capabilities of the first device based on the first information.

[0873] In some possible implementations, cache-related capabilities may include one or more of the following: storage capacity; downlink segmentation capability; downlink data size, which can indicate the size of downlink data supported by the first device; BSR capability, which can indicate the size of data to be transmitted that the first device can support; energy status, which can indicate whether the energy of the first device is sufficient to complete subsequent data transmission; device type; RA type.

[0874] In some possible implementations, the transceiver module 1810 can also be used to send a response to the first information, which can indicate whether the first function of the first device is turned on or off.

[0875] In some possible implementations, the first function may include one or more of the following: segmentation function; retransmission function; multi-service function; multi-process function; function of saving the context of communication with multiple second devices; function of saving encryption parameters; function of saving integrity protection parameters.

[0876] In some possible implementations, the response to the first information may include a first response, which may indicate that the second device has received the first information and indicate whether the first function is turned on or off;

[0877] Alternatively, the response to the first information may include a first response and a second information, wherein the first response may indicate that the second device has received the first information, and the second information may indicate whether the first function is enabled or disabled.

[0878] In some possible implementations, the first information can be sent when the cache-related capabilities of the first device meet a first condition, which can be used to determine whether the cache-related capabilities of the first device meet the first capability requirements.

[0879] It should be understood that the transceiver module 1810 or the processing module 1820 can be used to perform the various actions or processing procedures performed by the second device in the above-described communication method 600.

[0880] It should be understood that the specific process of each module in device 1800 performing the above-mentioned corresponding steps is described in the previous description of communication method 600, and will not be repeated here.

[0881] It should be understood that the "units" in communication devices 1700 and 1800 can be implemented in hardware, software, or by hardware executing corresponding software. For example, a "unit" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a dedicated processor, or a group processor) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. Furthermore, a transmitting unit can be replaced by a transmitter, a receiving unit by a receiver, and other units such as a determining unit or an acquiring unit can be replaced by a processor or processing circuitry, each performing the transmitting and receiving operations and related processing operations in its respective method embodiment.

[0882] Figure 19A schematic block diagram of another communication device 1900 provided in an embodiment of this application is shown. This device 1900 may be an A-IoT terminal, a terminal device, or an access network device, or it may be a chip, chip system, or processor that supports the implementation of the above methods by the A-IoT terminal, terminal device, or access network device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0883] The device 1900 may include at least one processor 1910, which may also be referred to as a processing unit or processing module, and can implement certain control functions. The processor 1910 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control communication devices (such as base stations, baseband chips, user chips, DUs or CUs, etc.), execute software programs, and process data from the software programs.

[0884] In an alternative design, the processor 1910 may also store at least one of instructions and data, which can be executed by the processor 1910 to cause the device 1900 to perform the method described in the above method embodiments.

[0885] In another alternative design, the device 1900 may include a communication interface 1920 for implementing receiving and transmitting functions. For example, the communication interface 1920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals. Optionally, the communication interface 1920 may also be referred to as a communication unit.

[0886] Optionally, the device 1900 may include one or more memories 1930, which may store instructions that can be executed on the processor 1910, causing the device 1900 to perform the methods described in the above method embodiments. Optionally, the memory 1930 may also store data. Optionally, the processor 1910 may also store at least one of instructions and data. The processor 1910 and the memory 1930 may be configured separately or integrated together.

[0887] Those skilled in the art will understand that, for ease of explanation, Figure 19Only one memory and processor are shown. In actual terminal devices or access network devices, multiple processors and memories may exist. Memory may also be called storage medium or storage device, etc., and this application embodiment does not limit this.

[0888] For example, a processor may include a baseband processor and a central processing unit (CPU). The baseband processor is mainly used to process communication protocols and communication data, while the CPU is mainly used to control the entire terminal device or access network device, execute software programs, and process the data of the software programs. Figure 19 The processor integrates the functions of a baseband processor and a central processing unit (CPU). Those skilled in the art will understand that the baseband processor and CPU can also be independent processors interconnected via technologies such as buses. It will also be understood that terminal devices or access network devices can include multiple baseband processors to adapt to different network standards, and multiple CPUs to enhance their processing capabilities. The various components of the terminal device or access network device can be connected via various buses. The baseband processor can also be described as a baseband processing circuit or a baseband processing chip. The CPU can also be described as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored as a software program in a storage unit, with the processor executing the software program to implement the baseband processing function.

[0889] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0890] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0891] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), EPROM, electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0892] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the methods described in any of the foregoing aspects to be performed.

[0893] This application also provides a computer program product comprising a computer program or instructions that, when executed on a computer, cause the methods described in any of the foregoing aspects to be performed.

[0894] This application also provides a communication device, including a processor and an interface for transmitting and receiving signals at least one of the above, such that the processor performs various steps or processes in any of the methods described above.

[0895] This application also provides a communication system comprising a first means (such as an A-IoT terminal device), a second means (such as an access network device), and a third means (such as a core network device) for performing any of the methods described above.

[0896] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0897] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0898] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0899] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

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

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

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

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

[0904] In the above embodiments, the functions of each functional unit can be implemented 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. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

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

[0906] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first device determines the first information; The first device sends the first information, which indicates the cache-related capabilities of the first device, and the cache-related capabilities are associated with a first function of the first device.

2. The method according to claim 1, characterized in that, The cache-related capabilities include one or more of the following: Storage capacity; Downlink segmentation capability; Downlink data size, wherein the downlink data size indicates the size of downlink data supported by the first device; Buffer Status Report (BSR) capability, which indicates the size of data to be transmitted that the first device can support; Energy status, which indicates whether the first device has sufficient energy to complete subsequent data transmission; Equipment type; Random Access (RA) type.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The response to receiving the first information from the second device indicates whether the first function is enabled or disabled.

4. The method according to claim 3, characterized in that, The response includes a first response, which indicates that the second device has received the first information and indicates whether the first function is enabled or disabled. Alternatively, the response may include a first response and a second message, wherein the first response indicates that the second device has received the first message, and the second message indicates whether the first function is enabled or disabled.

5. The method according to any one of claims 1-4, characterized in that, The first function includes one or more of the following: Segmentation function; Retransmission function; Multiple service functions; Multi-process functionality; The ability to save the context of communication with multiple second devices; The function to save encrypted parameters; The function of saving integrity protection parameters.

6. The method according to any one of claims 1-5, characterized in that, The first information is sent when the cache-related capabilities meet a first condition, the first condition being used to determine whether the cache-related capabilities meet the first capability requirements.

7. A communication method, characterized in that, include: The second device receives first information, which indicates the cache-related capabilities of the first device and is associated with a first function of the first device. The second device determines the cache-related capabilities of the first device based on the first information.

8. The method according to claim 7, characterized in that, The cache-related capabilities include one or more of the following: Storage capacity; Downlink segmentation capability; Downlink data size, wherein the downlink data size indicates the size of downlink data supported by the first device; Buffer Status Report (BSR) capability, which indicates the size of data to be transmitted that the first device can support; Energy status, which indicates whether the first device has sufficient energy to complete subsequent data transmission; Equipment type; Random Access (RA) type.

9. The method according to claim 7 or 8, characterized in that, The method further includes: The second device sends a response to the first information, and the response indicates whether the first function is enabled or disabled.

10. The method according to claim 9, characterized in that, The response includes a first response, which indicates that the second device has received the first information and indicates whether the first function is enabled or disabled. Alternatively, the response may include a first response and a second message, wherein the first response indicates that the second device has received the first message, and the second message indicates whether the first function is enabled or disabled.

11. The method according to any one of claims 7-10, characterized in that, The first function includes one or more of the following: Segmentation function; Retransmission function; Multiple service functions; Multi-process functionality; The ability to save the context of communication with multiple second devices; The function to save encrypted parameters; The function of saving integrity protection parameters.

12. The method according to any one of claims 7-11, characterized in that, The first information is sent when the cache-related capabilities meet a first condition, the first condition being used to determine whether the cache-related capabilities meet the first capability requirements.

13. A communication method, characterized in that, include: The first device sends a first message to the second device, and, The second device sends a response to the first device for the first information, and the response indicates whether the first function is enabled or disabled; Alternatively, the third device sends the first information to the second device, and... The second device sends a second message to the first device, the second message indicating whether the first function is enabled or disabled; The first information indicates the cache-related capabilities of the first device, and the cache-related capabilities are associated with the first function of the first device.

14. The method according to claim 13, characterized in that, The activation or deactivation of the first function is determined by the second device; And / or, before the activation or deactivation of the first function is indicated by the third device to the second device, and before the second device sends the response or the second information to the first device, the method further includes: The third device sends a third message to the second device, the third message indicating whether the second function is enabled or disabled.

15. The method according to claim 14, characterized in that, The second function is different from the first function determined by the second device.

16. The method according to any one of claims 13-15, characterized in that, The first information sent by the third device is associated with one or more of the following: Device group identification ID, wherein the device group ID indicates the ID of the device group to which the first device belongs; A device mask, the device mask being used to match one or more of the first devices; Device ID, which indicates the ID of the first device; Deployment area information, wherein the deployment area information indicates the deployment area of ​​the first device; Deployment time information, which indicates the deployment time of the first device.

17. The method according to any one of claims 13-16, characterized in that, Before the third device sends the first information to the second device, the method further includes: The second device sends the device ID of the first device to the third device, the device ID being used to determine the first information.

18. A communication device, characterized in that, It includes at least one unit or module for performing the method as described in any one of claims 1-6 or 7-12.

19. A communication device, characterized in that, The communication device includes at least one processor coupled to at least one memory for storing a computer program or instructions, which, when executed by the at least one processor, cause the communication device to perform the method as described in any one of claims 1-6.

20. A communication device, characterized in that, The communication device includes at least one processor coupled to at least one memory for storing a computer program or instructions which, when executed by the at least one processor, cause the communication device to perform the method as described in any one of claims 7-12.

21. A communication system, characterized in that, It includes a first device, a second device, and a third device for performing the method as described in any one of claims 13-17.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1-6 or 7-12 to be performed.

23. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the method as described in any one of claims 1-6 or 7-12 to be performed.

Images