Communication method, communication device, communication system, storage medium and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium and a program product. The method comprises: determining communication parameters on the basis of a device type of a first terminal. In the method of the present disclosure, the first terminal can determine corresponding communication parameters on the basis of the device type thereof, such that the adaptation of the communication parameter to the device type is ensured, thereby improving the communication performance and communication efficiency of the first terminal.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] With the continuous development of IoT communication technology, the future of IoT communication aims to achieve low cost, low power consumption, sustainability and large-scale connectivity in various application scenarios. Summary of the Invention

[0003] With the development of the Internet of Things (IoT), there are low-capability or IoT terminals in different applications, and it is necessary to clarify the communication methods for these terminals.

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0005] In a first aspect, embodiments of this disclosure provide a communication method executed by a first terminal, the method comprising:

[0006] The communication parameters are determined based on the device type of the first terminal.

[0007] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0008] Configuration information is sent to a first terminal, the configuration information including communication parameters corresponding to the device type of the first terminal, wherein the configuration information is used by the first terminal to determine the corresponding communication parameters.

[0009] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0010] Fourthly, embodiments of this disclosure provide a communication system, including a first terminal and a network device, wherein,

[0011] The first terminal is configured to implement the method as described in the first aspect;

[0012] The network device is configured to implement the method as described in the second aspect.

[0013] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0014] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0015] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0016] In this embodiment of the disclosure, the first terminal can determine the corresponding communication parameters according to its own device type, thereby ensuring that the communication parameters are compatible with the device type and improving the communication performance and efficiency of the first terminal. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0018] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0019] Figure 2 is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure;

[0020] Figures 3A and 3B are exemplary interaction diagrams of the communication method provided according to embodiments of the present disclosure;

[0021] Figure 4A is a schematic diagram of the structure of a first terminal according to an embodiment of the present disclosure;

[0022] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure;

[0023] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0024] Figure 5B is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0025] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0026] In a first aspect, embodiments of this disclosure provide a communication method executed by a first terminal, the method comprising:

[0027] The communication parameters are determined based on the device type of the first terminal.

[0028] In the above embodiments, the first terminal can determine the corresponding communication parameters according to its own device type, thereby ensuring that the communication parameters are compatible with the device type and improving the communication performance and efficiency of the first terminal.

[0029] In conjunction with the embodiments of the first aspect, in some embodiments, the default values ​​of the communication parameters corresponding to the first terminals of different device types are different.

[0030] In the above embodiments, terminals of different device types correspond to different default values ​​of communication parameters. This improves the adaptability of the default values ​​of communication parameters to application scenarios and terminals in different application scenarios, thereby enhancing communication performance in the corresponding application scenarios.

[0031] In conjunction with the embodiments of the first aspect, in some embodiments, the peak rates corresponding to the first terminals of different device types are different.

[0032] In the above embodiments, different first terminals may have corresponding peak rates, thereby enabling the determination or differentiation of corresponding communication parameters based on the peak rates, so as to improve the communication performance in relevant application scenarios.

[0033] In conjunction with the embodiments of the first aspect, in some embodiments, determining the communication parameters based on the device type of the first terminal includes:

[0034] The system receives configuration information sent by a network device, the configuration information including communication parameters corresponding to the device type of the first terminal;

[0035] Determine the corresponding communication parameters based on the configuration information;

[0036] or,

[0037] According to the agreement, the communication parameters corresponding to the device type of the first terminal are determined.

[0038] In the above embodiments, the first terminal can determine the communication parameters corresponding to its device type based on the configuration information sent by the network or according to the protocol agreement. While ensuring that the communication performance is improved based on the communication parameters, the flexibility of determining the communication parameters can be improved.

[0039] In conjunction with the embodiments of the first aspect, in some embodiments, the configuration information configures the communication parameters on a per-device-type basis.

[0040] In the above embodiments, configuring communication parameters on a per-device-type basis can improve the adaptability of communication parameters to different terminal application scenarios.

[0041] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0042] The first terminal sends capability information to the network device, the capability information including candidate values ​​of communication parameters supported by the first terminal.

[0043] In the above embodiments, by sending candidate values ​​of communication parameters supported by the first terminal to the network device, the accuracy or rationality of the network device configuring communication parameters for the first terminal is improved, and communication parameters that it does not support are avoided for the first terminal.

[0044] In conjunction with the embodiments of the first aspect, in some embodiments, the candidate values ​​include default values ​​for the communication parameters supported by the first terminal; and / or,

[0045] The candidate values ​​include values ​​other than the default values ​​of the communication parameters.

[0046] In the above embodiments, the first terminal can report a default value from the candidate values, or it can report other values ​​besides the default value, thereby saving capability information resources.

[0047] In conjunction with the embodiments of the first aspect, in some embodiments, the capability information includes multiple capabilities, each capability corresponding to a candidate value; or, the capability information indicates different candidate values ​​through different bit values.

[0048] In the above embodiments, capability information can indicate candidate values ​​in a variety of ways, thereby improving information utilization.

[0049] In conjunction with the embodiments of the first aspect, in some embodiments, the communication parameters include at least one of the following:

[0050] Medium Access Control (MAC) layer parameters;

[0051] Radio Link Control (RLC) layer parameters;

[0052] Physical layer (PHY) parameters;

[0053] Radio Resource Control (RRC) layer parameters.

[0054] In the above embodiments, the communication parameters may include different protocol layer parameters, so that the first terminal can communicate based on appropriate communication parameters in different communication scenarios, thereby improving communication performance.

[0055] In conjunction with the embodiments of the first aspect, in some embodiments, the communication parameter is the number of Hybrid Automatic Repeat reQuest (HARQ) processes.

[0056] In conjunction with the embodiments of the first aspect, in some embodiments, the communication parameters are at least one of the following:

[0057] The first scaling factor used to determine the maximum data rate;

[0058] The second scaling factor is used to determine the layer 2 cache space.

[0059] In the above embodiments, the first terminal can determine the maximum data rate and / or layer 2 cache space based on the corresponding communication parameters, so that the first terminal of different device types can determine the maximum data rate and / or layer 2 cache space corresponding to its own device type, thereby improving communication performance.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the communication parameters are at least one of the following:

[0061] Buffer Status Report (BSR) parameters;

[0062] Power Headroom Report (PHR) parameters;

[0063] Timer parameters for out-of-step or rebuilding.

[0064] In the above embodiments, the first terminal can improve communication performance in relevant communication scenarios based on adapted communication parameters.

[0065] In conjunction with the embodiments of the first aspect, in some embodiments, the communication parameter is the number of Data Radio Bearers (DRBs).

[0066] In conjunction with the embodiments of the first aspect, in some embodiments, the device type includes at least one of the following:

[0067] Internet of Things (IoT) devices;

[0068] Low-capacity equipment;

[0069] Machine Type Communication (MTC) devices;

[0070] Devices with different peak rates.

[0071] In the above embodiments, any of the low-capability or IoT devices can determine the appropriate communication parameters based on the corresponding device type to improve the communication performance of different types of devices.

[0072] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0073] Configuration information is sent to a first terminal, the configuration information including communication parameters corresponding to the device type of the first terminal, wherein the configuration information is used by the first terminal to determine the corresponding communication parameters.

[0074] In the above embodiments, the network device can configure communication parameters corresponding to its device type for the first terminal, thereby ensuring that the communication parameters are compatible with the device type and improving the communication performance and efficiency of the first terminal.

[0075] In conjunction with the embodiments of the second aspect, in some embodiments, the default values ​​of the communication parameters corresponding to the first terminals of different device types are different.

[0076] In conjunction with the embodiments of the second aspect, in some embodiments, the peak rates corresponding to the first terminals of different device types are different.

[0077] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0078] The system receives capability information sent by the first terminal, the capability information including candidate values ​​of communication parameters supported by the first terminal.

[0079] In conjunction with the embodiments of the second aspect, in some embodiments,

[0080] The candidate values ​​include default values ​​for the communication parameters supported by the first terminal; and / or,

[0081] The candidate values ​​include values ​​other than the default values ​​of the communication parameters.

[0082] In conjunction with the embodiments of the second aspect, in some embodiments,

[0083] The capability information includes multiple capabilities, each capability corresponding to a candidate value; or...

[0084] The capability information indicates different candidate values ​​through different bit values.

[0085] In conjunction with embodiments of the second aspect, in some embodiments, the communication parameters include at least one of the following:

[0086] Media access control MAC layer parameters;

[0087] Radio Link Control (RLC) layer parameters;

[0088] Physical layer PHY parameters;

[0089] Radio Resource Control (RRC) layer parameters.

[0090] In conjunction with the embodiments of the second aspect, in some embodiments, the communication parameter is the number of Hybrid Automatic Repeat Request (HARQ) processes.

[0091] In conjunction with the embodiments of the second aspect, in some embodiments, the communication parameters are at least one of the following:

[0092] The first scaling factor used to determine the maximum data rate;

[0093] The second scaling factor is used to determine the layer 2 cache space.

[0094] In conjunction with the embodiments of the second aspect, in some embodiments, the communication parameters are at least one of the following:

[0095] Cache Status Report (BSR) parameters;

[0096] Power headroom report PHR parameters;

[0097] Timer parameters for out-of-step or rebuilding.

[0098] In conjunction with the embodiments of the second aspect, in some embodiments, the communication parameter is the number of Data Radio Bearer (DRB).

[0099] In conjunction with embodiments of the second aspect, in some embodiments, the device type includes:

[0100] Internet of Things (IoT) devices;

[0101] Low-capacity equipment;

[0102] Machine type: Communication MTC device;

[0103] Devices with different peak rates.

[0104] In conjunction with the embodiments of the second aspect, in some embodiments, the configuration information configures the communication parameters on a per-type basis for the first terminal.

[0105] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0106] Fourthly, embodiments of this disclosure provide a communication system, including a first terminal and a network device, wherein,

[0107] The first terminal is configured to implement the method as described in the first aspect;

[0108] The network device is configured to implement the method as described in the second aspect.

[0109] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0110] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0111] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0112] In a seventh aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0113] Eighthly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0114] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0115] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0116] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0117] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0118] In the embodiments disclosed herein, "multiple" refers to two or more.

[0119] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0120] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0121] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0122] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0123] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0124] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0125] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0126] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0127] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0128] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0129] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0130] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0131] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0132] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0133] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0134] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0135] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0136] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0137] As shown in Figure 1, the communication system 100 includes a first terminal 101 and a network device 102.

[0138] In some embodiments, the first terminal 101 may represent any terminal. Optionally, the first terminal 101 may be a low-capability terminal, an Internet of Things device, or a low-capability terminal in a future communication system.

[0139] Optionally, the first terminal 101 may include a narrowband Internet of Things (NB-IoT) device, an MTC device, a reduced capability (RedCap) device, an ambient IoT device (A-IoT), or an IoT device (IoT).

[0140] In some other embodiments, the first terminal 101 may also include at least a portion of conventional terminals. Conventional terminals include, but are not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication capabilities, smart car, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0141] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0142] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0143] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0144] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0145] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0146] In some embodiments, core network equipment includes network elements with specific functions, such as Access Management Function (AMF) and Service Management Function (SMF).

[0147] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0148] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0149] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0150] In some implementations, traditional IoT devices are typically powered by batteries with limited lifespans, which negatively impacts user experience. With the massive growth of IoT networks and the proliferation of IoT devices, maintenance costs, including labor and battery costs, are increasing. Only a small fraction of traditional batteries are effectively recycled, and the large number of discarded batteries has a harmful impact on the Earth's ecosystem. Maintaining IoT networks and replacing batteries can be extremely challenging under some extreme environmental conditions, leading to the development of battery-free IoT communication. Battery-free IoT communication can improve network performance and sustainability, and is more environmentally friendly and safer for users. Furthermore, eliminating traditional batteries can significantly reduce device size and cost, facilitating the expansion of new application scenarios.

[0151] In some implementations, to meet the growing demand, Low Power Wide Area (LPWA) technologies have developed rapidly. For example, MTC, NB-IoT, and RedCap achieve low cost, low power consumption, and massive connectivity, satisfying the needs of many applications. However, many use cases and applications remain unsuitable in the following situations: traditional battery-powered devices are not applicable, for example, under extreme environmental conditions (high voltage, extremely high / low temperatures, humid environments, etc.); maintenance-free devices are required, such as traditional batteries that do not require replacement; and ultra-low complexity, very small device size / form factor (e.g., thickness in mm), and longer lifespan are required.

[0152] In some implementations, future communications such as 6G define multi-dimensional requirements, including high connection density, varying data rates, low power consumption, mobility, extended coverage, and high security and reliability. Therefore, for different low-capability terminals in different applications, it is necessary to clearly define the communication methods for those terminals, such as how to design the user plane for different low-capability terminals.

[0153] Figure 2 is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure. As shown in Figure 2, the communication method of the present disclosure includes:

[0154] In step S2101, the first terminal 101 sends capability information to the network device 102.

[0155] In some embodiments, network device 102 receives capability information.

[0156] In some embodiments, the capability information includes candidate values ​​for communication parameters supported by the first terminal 101.

[0157] Optionally, the communication parameters may include multiple types, and the first terminal 101 may report candidate values ​​for each supported communication parameter through capability information.

[0158] Optionally, for each communication parameter, the first terminal 101 may report one or more candidate values ​​through capability information.

[0159] In some embodiments, for first terminals 101 of different device types, each first terminal 101 of a different device type can send capability information and report candidate values ​​of communication parameters it supports.

[0160] Optionally, this capability is a per-UE capability.

[0161] Optionally, the equipment types and their characteristics can be referred to Table 2-1. Table 2-1 is for illustrative purposes only and may also include other equipment types.

[0162] Table 2-1

[0163] In some embodiments, the device type of the first terminal 101 includes at least one of the following:

[0164] Internet of Things (IoT) devices;

[0165] Low-capacity equipment;

[0166] Machine type: Communication MTC device;

[0167] Devices with different peak rates.

[0168] In some embodiments, the peak rates corresponding to the first terminals of different device types are different.

[0169] For example, the peak rate for IoT devices is less than 25 Mbps, the peak rate for low-capacity devices is less than 50 Mbps or 150 Mbps, and the peak rate for MTC devices is less than 1 Mbps or 2 Mbps.

[0170] Optionally, different device types can be distinguished by peak rate. It should be noted that there may be other forms of peak rate classification. The above is just an example. This disclosure does not specifically limit how many types of first terminals are classified according to peak rate, or the specific values / ranges of peak rates for different types of first terminals.

[0171] In some embodiments, the device type classification or categorization method can be based on protocol definition, network device configuration, or the terminal reporting its corresponding device type to the network device.

[0172] In some embodiments, the communication parameters include at least one of the following:

[0173] Media access control MAC layer parameters;

[0174] Radio Link Control (RLC) layer parameters;

[0175] Physical layer PHY parameters;

[0176] Radio Resource Control (RRC) layer parameters.

[0177] In some examples, the communication parameter is the number of HARQ processes in the MAC layer.

[0178] In this example, taking the number of HARQ processes as an example, the first terminal 101 of different device types can support different numbers of HARQ processes.

[0179] In this example, the first terminal 101 of each type can report a candidate value for the number of HARQ processes it supports through capability information.

[0180] Optionally, candidate values ​​include default values ​​for communication parameters supported by the first terminal 101, such as the number of HARQ processes.

[0181] For example, the default value for the number of HARQ processes supported by the first type of first terminal 101 is 1; therefore, the candidate value for the number of HARQ processes reported by the first type of first terminal 101 in the capability information is 1. For example, the default value for the number of HARQ processes supported by the second type of first terminal 101 is 4; therefore, the candidate value for the number of HARQ processes reported by the second type of first terminal 101 in the capability information is 4. For example, the default value for the number of HARQ processes supported by the third type of first terminal 101 is 8; therefore, the candidate value for the number of HARQ processes reported by the third type of first terminal 101 in the capability information is 8. It should be noted that the default number of HARQ processes supported by the first terminal of the above different types is only an example; this disclosure does not specifically limit the default number of HARQ processes supported by the first terminal of different types.

[0182] For example, different device types can be distinguished by peak rate. For instance, the peak rate of the first type of first terminal 101 is less than 1 Mbps or 2 Mbps, the peak rate of the second type of first terminal 101 is less than 25 Mbps, and the peak rate of the third type of first terminal 101 is less than 50 Mbps or 150 Mbps. It should be noted that the peak rate classification may take other forms; the above is merely an example. This disclosure does not specifically limit the number of first terminal types to be classified based on peak rate, nor the specific values / ranges of peak rates for different first terminal types.

[0183] Optionally, in addition to classifying different types of first terminals based on peak rates, there may be other ways to distinguish between them, such as by at least one of the following: supported bandwidth, battery life, coverage, application scenarios, etc. This disclosure does not specifically limit how to distinguish different types of first terminals or how many different types to define.

[0184] Optionally, the default value for the number of HARQ processes supported by the first terminal 101 varies depending on the device type. For example, this default value can be understood as the first terminal 101 of that type must support at least the default number of HARQ processes; for instance, the first terminal 101 of the first type with the lowest capability needs to support the default number of HARQ processes.

[0185] Optionally, candidate values ​​include those other than the default values ​​for communication parameters such as the number of HARQ processes.

[0186] For example, the first terminal 101 of the first type supports 2, 4, 8, or 16 HARQ processes in addition to the default value (e.g., 1) mentioned above. In this case, the first terminal 101 of the first type can report one or more candidate values ​​of 2, 4, 8, or 16 for the number of HARQ processes in its capability information, without needing to report the default supported 1 HARQ process. Similarly, the first terminal 101 of the second type supports 8 or 16 HARQ processes in addition to the default value (e.g., 4) mentioned above. In this case, the first terminal 101 of the second type can report one or more candidate values ​​of 8 or 16 for the number of HARQ processes in its capability information, without needing to report the default supported 4 HARQ processes. The distinction between the first, second, and third types can be found in the description of the above embodiments, and will not be repeated here.

[0187] Optionally, candidate values ​​include default values ​​of communication parameters supported by the first terminal and other values ​​besides the default values ​​of communication parameters.

[0188] For example, the first terminal 101 of the first type can report one or more candidate values ​​for the number of HARQ processes in the capability information, including 1, 2, 4, 8, and 16. For example, the first terminal 101 of the second type can report one or more candidate values ​​for the number of HARQ processes in the capability information, including 4, 8, and 16.

[0189] In some examples, the communication parameters are at least one of the following:

[0190] The first scaling factor used to determine the maximum data rate;

[0191] The second scaling factor is used to determine the L2 buffer size.

[0192] Alternatively, the scaling factor can also be called a scaling parameter. For example, the two scaling factors mentioned above can be RLC layer parameters.

[0193] Optionally, the maximum data rate is the maximum downlink data rate (MaxDLDataRate), or the maximum data rate is the maximum uplink data rate (MaxULDataRate), or the maximum data rate includes both the maximum downlink data rate and the maximum uplink data rate.

[0194] Optionally, the maximum data rate determined based on the first scaling factor K1 can be expressed as K1*MaxDataRate, where MaxDataRate represents the maximum downlink data rate or the maximum uplink data rate calculated using a correlation method. For example, the first scaling factor K1 associated with the maximum downlink data rate and the maximum uplink data rate can be the same or different.

[0195] Optionally, the first scaling factor is less than 1.

[0196] Optionally, the layer 2 buffer space determined based on the second scaling factor K2 can be calculated using the following formula: K2*(MaxDLDataRate×RLC RTT+MaxULDataRate×RLC RTT); where MaxDLDataRate represents the maximum downlink data rate, MaxULDataRate represents the maximum uplink data rate, and RLC RTT represents the RLC round trip time. For example, the relationship between the value of RLC RTT and the subcarrier spacing SCS is shown in Table 2-2 below.

[0197] Table 2-2

[0198] Optionally, the second scaling factor is less than 1.

[0199] In this example, the first terminal 101 of different device types can support different first scaling factors, and / or, the first terminal 101 of different device types can support different second scaling factors.

[0200] In some examples, the communication parameters are at least one of the following:

[0201] The cache status report (BSR) parameter, where the BSR parameter is a MAC layer parameter;

[0202] The power margin report includes PHR parameters, where PHR parameters are MAC layer parameters;

[0203] Timer parameters for out-of-step or rebuilding, including PHY layer parameters.

[0204] Optionally, the BSR parameters include at least one of the BSR retransmission timer and the BSR periodic timer.

[0205] Optionally, the PHR parameters include at least one of the PHR periodic timer and the PHR disable timer.

[0206] Optionally, the timer parameters for out-of-sync or reconnection include at least one of the following: timer t310, variable n310, timer t311, and variable n311. Specifically, timer t310 is used to detect radio link failure; variable n310 indicates the maximum number of downlink out-of-sync indications received during timer t310; timer t311 is used to detect the RRC connection reconnection process after radio link failure; and variable n311 indicates the maximum number of downlink synchronization indications received during timer t311.

[0207] In this example, the first terminal 101 of different device types can support different MAC layer parameters and / or PHY layer parameters as described above.

[0208] In this example, the first terminal 101 of different device types can support the above-mentioned MAC layer parameters and / or PHY layer parameters with different default values.

[0209] In this example, the above-mentioned MAC layer parameters and / or PHY layer parameters can be defined for different types of first terminals 101 through the protocol.

[0210] In some examples, the communication parameters are RRC layer parameters: the number of Data Radio Bearer (DRBs).

[0211] In this example, the first terminal 101 of different device types can support different numbers of DRBs.

[0212] In this example, the first terminal 101 of each type can report the candidate value of the number of DRBs it supports through capability information.

[0213] Optionally, candidate values ​​include default values ​​for communication parameters supported by the first terminal 101, such as the number of DRBs.

[0214] For example, if the default value for the number of DRBs supported by the first type of first terminal 101 is 4, then the first type of first terminal 101 can report a candidate value of 4 for the number of DRBs in its capability information. Similarly, if the default value for the number of DRBs supported by the second type of first terminal 101 is 4, then the second type of first terminal 101 can report a candidate value of 4 for the number of DRBs in its capability information. And if the first type of first terminal 101 supports a candidate value of 16 for the number of DRBs, then the third type of first terminal can report a candidate value of 16 for the number of DRBs in its capability information.

[0215] Optionally, the distinction between the first type, the second type, and the third type can be found in the description of the foregoing embodiments, and will not be repeated here.

[0216] Optionally, the default value for the number of DRBs supported by the first terminal 101 varies depending on the device type. For example, this default value can be understood as the first terminal 101 of that type must support at least the default number of DRBs. For instance, the first terminal 101 of the first type with the lowest capability needs to support the default number of DRBs.

[0217] Optionally, candidate values ​​include values ​​other than the default values ​​for communication parameters such as the number of DRBs.

[0218] For example, the first terminal 101 of the first type supports 8 or 16 DRBs in addition to the default value (e.g., 4). In this case, the first terminal 101 of the first type can report one or more candidate values ​​of 8 or 16 for the number of DRBs in its capability information, without reporting the default supported value of 4. Similarly, the first terminal 101 of the second type supports 8 or 16 DRBs in addition to the default value (e.g., 4). In this case, the first terminal 101 of the second type can report one or more candidate values ​​of 8 or 16 for the number of DRBs in its capability information, without reporting the default supported value of 4.

[0219] Optionally, candidate values ​​include the default value for the DRB number and other values.

[0220] For example, the first terminal 101 of the first type can report one or more candidate values ​​for the DRB number in the capability information, including 4, 8, or 16. For example, the first terminal 101 of the second type can report one or more candidate values ​​for the DRB number in the capability information, including 4, 8, or 16.

[0221] In some embodiments, capability information indicates whether values ​​other than the default values ​​for communication parameters are supported.

[0222] For example, for a first terminal of type 2, the default supported number of HARQs is 4. This first terminal can indicate whether it supports 8 or 16 HARQ processes through its capability information. As another example, for a first terminal of type 2, the default supported number of HARQs is 8. This first terminal can indicate whether it supports 16 HARQ processes through its capability information. Similarly, for a first terminal of type 3, the default supported number of HARQs is 8. This first terminal can indicate whether it supports 16 HARQ processes through its capability information.

[0223] For example, the first terminal of the second type supports 4 DRBs by default, and the capability information can indicate whether it supports 8 or 16 DRBs; if the first terminal of the second type supports 8 DRBs by default, the capability information can indicate whether it supports 16 DRBs. The first terminal of the third type supports 8 DRBs by default, and the capability information can indicate whether it supports 16 DRBs.

[0224] In some embodiments, the capability information includes multiple capabilities, each corresponding to a candidate value.

[0225] Optionally, a capability information indicates a communication parameter, which may include multiple capabilities, each corresponding to a candidate value for the communication parameter.

[0226] In one example, the capability information reported by the first terminal 101 of the second type, which indicates the HARQ number, can correspond to a candidate value of 2, 4, 8 or 16 respectively through different capabilities.

[0227] For example, a first capability indicator may support 2 HARQ processes, a second capability indicator may support 4 HARQ processes, a third capability indicator may support 8 HARQ processes, and a fourth capability indicator may support 16 HARQ processes. For instance, if a first terminal 101 of the first type reports the first capability, it indicates that the first terminal 101 supports 2 HARQ processes; if it reports the second capability, it indicates that the first terminal 101 supports 4 HARQ processes; if it reports the third capability, it indicates that the first terminal 101 supports 8 HARQ processes; and if it reports the fourth capability, it indicates that the first terminal 101 supports 16 HARQ processes.

[0228] For example, the first terminal 101 of the second type supports 8 HARQ processes via a third capability indication and supports 16 HARQ processes via a fourth capability indication. For instance, if the first terminal 101 of the second type reports the third capability, it indicates that the first terminal 101 supports 8 HARQ processes; if it reports the fourth capability, it indicates that the first terminal 101 supports 16 HARQ processes.

[0229] In another example, the capability information reported by the first terminal 101 of the second type, which indicates the number of DRBs, can correspond to a candidate value of 4, 8 or 16 respectively through different capabilities.

[0230] For example, in the capability information reported by the first terminal 101 of the second type, the fifth capability indication supports 4 DRBs, the sixth capability indication supports 8 DRBs, and the seventh capability indication supports 16 DRBs. If the first terminal 101 reports the fifth capability, it means that the first terminal supports 4 DRBs; if it reports the sixth capability, it means that the first terminal supports 8 DRBs; and if it reports the seventh capability, it means that the first terminal supports 16 DRBs.

[0231] Optionally, a capability information may indicate multiple communication parameters, and the capability information may include multiple capabilities, each corresponding to a candidate value for a communication parameter. For example, the capability information reported by the first terminal 101 of the first type includes two capabilities: one capability indicates a candidate value of 8 for the number of supported HARQ processes, and the other capability indicates a candidate value of 16 for the number of supported DRBs. Optionally, in addition to the capabilities indicated by the capability information, the first terminal 101 may also support default values ​​for relevant communication parameters.

[0232] In some embodiments, capability information indicates different candidate values ​​through different bit values.

[0233] In one example, when the communication parameter is the number of HARQ processes, the capability information can occupy one or more bits. When the bit value of this capability information is the first value, it indicates that the candidate value for the number of HARQ processes is 4; when the bit value of this capability information is the second value, it indicates that the candidate value for the number of HARQ processes is 8. The first and second values ​​are different bit values; for example, when the capability information occupies 1 bit, the first value is 1 and the second value is 0, or the first value is 0 and the second value is 1.

[0234] In another example, when the communication parameter is the DRB number, the capability information can occupy one or more bits. When the bit value of the capability information is the third value, the candidate value for the DRB number is 8; when the bit value of the capability information is the fourth value, the candidate value for the DRB number is 16. The third and fourth values ​​are different bit values. Specifically, when the capability information occupies 1 bit, the third value can be the same as the first value, and the fourth value can be the same as the second value.

[0235] In step S2102, the first terminal 101 receives configuration information sent by the network device 102.

[0236] In some embodiments, network device 102 may send configuration information after receiving capability information.

[0237] In some embodiments, network device 102 may determine corresponding configuration information for first terminal 101 based on capability information.

[0238] Alternatively, the network device 102 can determine the configuration information of different types of first terminals 101 on its own, in which case step S2101 can be omitted.

[0239] In some embodiments, the configuration information includes communication parameters corresponding to the device type of the first terminal 101.

[0240] Optionally, based on the different capabilities of different device types, the configuration information corresponding to the first terminal 101 of different device types can be different.

[0241] For example, based on the capability information of the first terminal 101 of the first type, it can be known that the first terminal supports 2, 4, 8 or 16 HARQ processes. The network device 102 can configure the first terminal 101 to have 8 HARQ processes through the configuration information.

[0242] Based on the capability information of the first terminal 101 of the second type, it can be known that the first terminal supports 4, 8 or 16 HARQ processes. The network device 102 can configure the first terminal 101 to have 16 HARQ processes through the configuration information.

[0243] Optionally, in different communication scenarios, network device 102 can configure different communication parameters for the same first terminal 101.

[0244] In some embodiments, the configuration information is used by the first terminal 101 to determine the communication parameters corresponding to its device type.

[0245] Optionally, the first terminal 101 performs communication in the corresponding scenario according to the communication parameters in the configuration information.

[0246] In some embodiments, the network device 102 may determine the corresponding configuration information based on the default values ​​of the communication parameters supported by the first terminal of different device types.

[0247] Optionally, the default values ​​of the communication parameters for the first terminal of different device types are different, and the corresponding configuration information can be different.

[0248] In one example, taking the number of HARQ processes as a communication parameter, the default value of the number of HARQ processes supported by the first terminal 101 is different when it is a device with different peak rates. The number of HARQ processes indicated in the configuration information corresponding to the devices with different peak rates can be the same or different.

[0249] In another example, the communication parameter is a first scaling factor. The default value of the first scaling factor differs depending on whether the first terminal 101 is a device with a different peak rate. The first scaling factor indicated in the configuration information for devices with different peak rates can be the same or different. For example, the first scaling factor in the configuration information for the first type of first terminal 101 is k1; the first scaling factor in the configuration information for the second type of first terminal 101 is k2; and the first scaling factor in the configuration information for the third type of first terminal 101 is k3. Here, k1, k2, and k3 are all less than 1, and they can be different from each other or at least partially the same.

[0250] In some embodiments, configuration information configures communication parameters on a device type basis.

[0251] Alternatively, different device types may correspond to different communication parameters.

[0252] Optionally, each device type corresponds to a configuration information, and the communication parameters configured in the configuration information for the first terminal of different device types can be the same or different.

[0253] Optionally, for the first terminal of each device type, the network device can configure multiple communication parameters through one configuration information, or configure multiple communication parameters through different configuration information.

[0254] Optionally, for the first terminal of each device type, different communication parameters can be specified according to the protocol. In this case, step S2102 can be omitted.

[0255] Alternatively, some communication parameters are defined by the protocol, while others are configured by the configuration information of network device 102.

[0256] In step S2103, the first terminal 101 determines the corresponding communication parameters based on the configuration information.

[0257] In some embodiments, the first terminal 101 receives configuration information sent by the network device 102. The configuration information includes communication parameters corresponding to the device type of the first terminal 101. Thus, the first terminal 101 can determine the communication parameters corresponding to its own device type based on the configuration information.

[0258] In some embodiments, step S2103 can be replaced by: the first terminal 101 determining the communication parameters corresponding to the device type of the first terminal 101 according to the protocol.

[0259] Optionally, the first terminal 101 determines its own compatible communication parameters based on its own device type and Table 2-3.

[0260] Table 2-3

[0261] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0262] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0263] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0264] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0265] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0266] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2103. For example, step S2103 may be implemented as a standalone embodiment, but is not limited thereto.

[0267] In some embodiments, steps S2101 and S2102 are optional, and one of them may be selected for execution in different embodiments, or one or more of these steps may be omitted or substituted in different embodiments.

[0268] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0269] Figure 3A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 3A, the communication method of this embodiment includes:

[0270] In step S3101, network device 102 sends configuration information to first terminal 101.

[0271] In some embodiments, the implementation of step S3101 can be referred to the implementation of step S2102 in FIG2, and will not be repeated here.

[0272] In step S3102, the first terminal 101 determines the communication parameters according to the configuration information.

[0273] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2103 in FIG2, and will not be repeated here.

[0274] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0275] Figure 3B is a schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 3B, the communication method of the present disclosure includes:

[0276] Step S3201: The first terminal 101 determines the communication parameters according to the device type of the first terminal 101.

[0277] In some embodiments, the implementation of step S3201 can be referred to the implementation of step S2103 in FIG2, and will not be repeated here.

[0278] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0279] This disclosure provides a communication method that can offer communication processing options for different low-capability terminals, such as a user plane processing method that employs different user plane designs for different low-capability terminals. For ease of understanding of this disclosure, please refer to the following embodiments:

[0280] Example 1: Different types of first devices support different numbers of HARQ processes.

[0281] Optionally, the first terminal 101 may be a low-capability terminal device or an IoT device.

[0282] In some embodiments, the first terminal 101 reports the number of supported HARQ processes through capability information.

[0283] In some implementations, different types of first terminals 101 support different numbers of HARQ processes by default.

[0284] In one example, the first terminal 101 with a peak rate of less than 1M or 2M supports one or two HARQ processes by default. Optionally, the first terminal 101 with a peak rate of less than 1M or 2M can support four, eight or 16 HARQ processes.

[0285] Optionally, the first terminal 101 with a peak rate less than 1 Mbps or 2 Mbps reports the number of supported HARQ processes through capability information, such as 4, 8, or 16. Different numbers of HARQ processes can be indicated by different capability information; for example, supporting 4 HARQ processes, 8 HARQ processes, and 16 HARQ processes can be indicated by different capability information. This capability is a capability of each user equipment, and it can be optional or mandatory.

[0286] In another example, the first terminal 101 with a peak rate of less than 25M supports 4 or 8 HARQ processes by default. Optionally, if the default number of supported HARQ processes is 4, the capability information can indicate whether 8 or 16 HARQ processes are supported; if the default number of supported HARQ processes is 8, the capability information can indicate whether 16 HARQ processes are supported.

[0287] In another example, the first terminal 101 with a peak rate of less than 50M or 150M supports 8 or 16 HARQ processes by default. Optionally, if the default number of supported HARQ processes is 8, the capability information can indicate whether 16 HARQ processes are supported.

[0288] It should be noted that the number of HARQ processes supported by the first terminal 101 of different peak rates / types in the above example may have other values, and the number of HARQ processes supported indicated by the capability information may also have other values. This embodiment does not make specific limitations.

[0289] In some implementations, preset parameters are set to different values ​​to indicate the number of HARQ processes supported.

[0290] In one example, the first value indicates support for 4 HARQ processes, and the second value indicates support for 8 HARQ processes.

[0291] This embodiment does not specifically limit how the number of supported HARQ processes is indicated through capability information.

[0292] Example 2: Different types of first terminals 101 support different scaling parameters.

[0293] In some embodiments, different types of first terminals 101 use different first scaling parameters when calculating the maximum downlink data rate and / or the maximum uplink data rate.

[0294] Optionally, a first scaling parameter corresponding to each device type can be defined according to the device type of the first terminal 101.

[0295] In some embodiments, different types of first terminals 101 use different second scaling parameters when calculating the L2 buffer size.

[0296] Optionally, a second scaling parameter can be defined for each device type according to the device type of the first terminal 101.

[0297] The L2 buffer size is calculated as: MaxDLDataRate × RLC RTT + MaxULDataRate × RLC RTT, where MaxDLDataRate represents the maximum downlink data rate, MaxULDataRate represents the maximum uplink data rate, and RLC RTT represents the RLC connection latency.

[0298] Optionally, the first scaling parameter and / or the second scaling parameter may be less than 1. The specific values ​​of the first scaling parameter and / or the second scaling parameter are not specifically limited in this embodiment.

[0299] Example 3: Different types of first terminals 101 support different default Media Access Control (MAC) layer or Physical Layer (PHY) layer configuration parameters.

[0300] In some embodiments, different types of first terminals 101 have different MAC layer or PHY layer configuration parameters.

[0301] Optionally, default MAC layer or PHY layer parameters are defined for each device type according to the device type of the first terminal 101.

[0302] Optionally, this may include, but is not limited to, BSR parameters, such as the BSR retransmission timer and the BSR period timer.

[0303] Optionally, this may include, but is not limited to, PHR parameters, such as PHR periodic timers and PHR disable timers.

[0304] Optionally, including but not limited to the following timers or variables, such as timer t310, variable n310, timer t311, and variable n311.

[0305] Example 4: Different types of first terminals 101 support different numbers of data radio bearers (DRBs).

[0306] In some embodiments, the first terminal 101 reports the number of supported data radio bearers through capability information.

[0307] Optionally, the first terminal 101 may be a low-capability terminal or an IoT device.

[0308] In some implementations, different types of first terminals 101 support different numbers of DRBs by default.

[0309] In one example, the first terminal 101 with a peak rate of less than 1M or 2M indicates a default number of DRBs of 4. Optionally, the first terminal 101 with a peak rate of less than 1M or 2M can support 8 DRBs or 16 DRBs.

[0310] Optionally, the first terminal 101 with a peak rate less than 1M or 2M reports the number of DRBs it supports through capability information, such as 8 or 16. Different numbers of DRBs can be indicated by different capability information; for example, supporting 8 DRBs and supporting 16 DRBs can be indicated by different capability information. This capability is a capability of each user equipment, and it can be optional or mandatory.

[0311] In another example, the first terminal 101 with a peak rate of less than 25M supports 4 or 8 DRBs by default. Optionally, if the default supported DRBs are 4, the capability information can indicate whether 8 or 16 DRBs are supported; if the default supported DRBs are 8, the capability information can indicate whether 16 DRBs are supported.

[0312] In another example, the first terminal 101 with a peak rate of less than 50M or 150M supports 8 DRBs by default. Optionally, if the default supported DRBs are 8, the capability information can indicate whether 16 DRBs are supported.

[0313] It should be noted that the number of DRBs supported by the first terminal 101 of different peak rates / types in the above example may have other values, and the number of DRBs supported indicated by the capability information may also have other values. This embodiment does not make specific limitations.

[0314] In some implementations, preset parameters are set to different values ​​to indicate support for different numbers of DRBs.

[0315] In one example, the first value indicates support for 8 DRBs, and the second value indicates support for 16 DRBs.

[0316] This embodiment does not specifically limit how the number of DRBs supported is indicated through capability information.

[0317] In some embodiments, embodiments 1 to 4 described above can be implemented independently or in combination.

[0318] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0319] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0320] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0321] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0322] Figure 4A is a schematic diagram of a first terminal according to an embodiment of this disclosure. The first terminal 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the first terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the processing module 4102 is used to determine communication parameters according to the device type of the first terminal.

[0323] Optionally, the transceiver module 4101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first terminal in any of the above methods, which will not be described in detail here. Optionally, the processing module 4102 is used to perform at least one of the other steps performed by the first terminal in any of the above methods, which will not be described in detail here.

[0324] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send configuration information to a first terminal. The configuration information includes communication parameters corresponding to the device type of the first terminal, wherein the configuration information is used by the first terminal to determine the corresponding communication parameters.

[0325] Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be described in detail here. Optionally, the processing module 4202 is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be described in detail here.

[0326] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0327] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0328] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0329] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 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.

[0330] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0331] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0332] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0333] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (6) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (7) others, etc.

[0334] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0335] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0336] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0337] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0338] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0339] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 5100, cause the communication device 5100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0340] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by the communication device 5100, cause the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0341] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0342] The first terminal can determine the corresponding communication parameters according to its own device type, thereby ensuring that the communication parameters are compatible with the device type and improving the communication performance and efficiency of the first terminal.

Claims

1. A communication method, executed by a first terminal, the method comprising: The communication parameters are determined based on the device type of the first terminal.

2. The method as described in claim 1, wherein, The default values ​​of the communication parameters corresponding to the first terminal of different device types are different.

3. The method as described in claim 1 or 2, wherein, The peak rates corresponding to the first terminals of different device types are different.

4. The method as described in any one of claims 1 to 3, wherein, Determining communication parameters based on the device type of the first terminal includes: The system receives configuration information sent by a network device, the configuration information including communication parameters corresponding to the device type of the first terminal; Determine the corresponding communication parameters based on the configuration information; or, According to the agreement, the communication parameters corresponding to the device type of the first terminal are determined.

5. The method of claim 4, wherein, The configuration information configures the communication parameters on a per-device-type basis.

6. The method according to any one of claims 1 to 5, wherein, The method further includes: The first terminal sends capability information to the network device, the capability information including candidate values ​​of communication parameters supported by the first terminal.

7. The method of claim 6, wherein, The candidate values ​​include default values ​​for the communication parameters supported by the first terminal; and / or, The candidate values ​​include values ​​other than the default values ​​of the communication parameters.

8. The method of claim 6, wherein, The capability information includes multiple capabilities, each capability corresponding to a candidate value; or... The capability information indicates different candidate values ​​through different bit values.

9. The method according to any one of claims 1 to 8, wherein, The communication parameters include at least one of the following: Media access control MAC layer parameters; Radio Link Control (RLC) layer parameters; Physical layer PHY parameters; Radio Resource Control (RRC) layer parameters.

10. The method of claim 9, wherein, The communication parameter is the number of HARQ (Hybrid Automatic Repeat Request) processes.

11. The method of claim 9, wherein, The communication parameters are at least one of the following: The first scaling factor used to determine the maximum data rate; The second scaling factor is used to determine the layer 2 cache space.

12. The method of claim 9, wherein, The communication parameters are at least one of the following: Cache Status Report (BSR) parameters; Power headroom report PHR parameters; Timer parameters for out-of-step or rebuilding.

13. The method of claim 9, wherein, The communication parameter is the number of Data Radio Bearer (DRB).

14. The method as claimed in any one of claims 1 to 13, wherein, The device type includes at least one of the following: Internet of Things (IoT) devices; Low-capacity equipment; Machine type: Communication MTC device; Devices with different peak rates.

15. A communication method performed by a network device, the method comprising: Configuration information is sent to a first terminal, the configuration information including communication parameters corresponding to the device type of the first terminal, wherein the configuration information is used by the first terminal to determine the corresponding communication parameters.

16. The method of claim 15, wherein, The default values ​​of the communication parameters corresponding to the first terminal of different device types are different.

17. The method of claim 15 or 16, wherein, The peak rates corresponding to the first terminals of different device types are different.

18. The method as claimed in any one of claims 15 to 17, wherein, The method further includes: The system receives capability information sent by the first terminal, the capability information including candidate values ​​of communication parameters supported by the first terminal.

19. The method of claim 18, wherein, The candidate values ​​include default values ​​for the communication parameters supported by the first terminal; and / or, The candidate values ​​include values ​​other than the default values ​​of the communication parameters.

20. The method of claim 18, wherein, The capability information includes multiple capabilities, each capability corresponding to a candidate value; or... The capability information indicates different candidate values ​​through different bit values.

21. The method according to any one of claims 15 to 20, wherein, The communication parameters include at least one of the following: Media access control MAC layer parameters; Radio Link Control (RLC) layer parameters; Physical layer PHY parameters; Radio Resource Control (RRC) layer parameters.

22. The method of claim 21, wherein, The communication parameter is the number of HARQ (Hybrid Automatic Repeat Request) processes.

23. The method of claim 21, wherein, The communication parameters are at least one of the following: The first scaling factor used to determine the maximum data rate; The second scaling factor is used to determine the layer 2 cache space.

24. The method of claim 21, wherein, The communication parameters are at least one of the following: Cache Status Report (BSR) parameters; Power headroom report PHR parameters; Timer parameters for out-of-step or rebuilding.

25. The method of claim 21, wherein, The communication parameter is the number of Data Radio Bearer (DRB).

26. The method as claimed in any one of claims 14 to 25, wherein, The equipment types include: Internet of Things (IoT) devices; Low-capacity equipment; Machine type: Communication MTC device; Devices with different peak rates.

27. The method of any one of claims 14 to 26, wherein, The configuration information configures the communication parameters on a per-type basis for the first terminal.

28. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 14 or any one of claims 15 to 27.

29. A communication system, comprising a network device and a first terminal, wherein, The network device is configured to implement the method as described in any one of claims 1 to 14; The first terminal is configured to implement the method as described in any one of claims 15 to 27.

30. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 14 or any one of claims 15 to 27.

31. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 14 or any one of claims 15 to 27.

Images