Information processing method and apparatus, and communication device, communication system and storage medium

Abstract

Disclosed in the embodiments of the present disclosure are an information processing method and apparatus, which are used for determining a peak data rate of a terminal, wherein the type of the terminal is a first type, and the peak data rate is agreed by a protocol. A peak data rate of a first-type terminal is determined on the basis of a protocol agreement, and therefore ambiguity in determination performed by a network side and a terminal side regarding a peak rate is avoided, signaling overheads can be effectively reduced, and the communication efficiency of a system is improved.

Description

Information processing method and device, communication equipment, communication system, and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information processing method and apparatus, communication equipment, a communication system, and a storage medium. Background Art

[0002] The peak data rate (PDR) of a terminal is related to its capabilities and can be used to constrain the transmission block size (TBS) scheduled by the network device. Specifically, it can be the ratio of the sum of all TBSs of a terminal scheduled by the network device in a time slot to the duration of the slot, which must be within the PDR constraint.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide an information processing method and apparatus, a communication device, a communication system, and a storage medium.

[0005] A first embodiment of the present disclosure provides an information processing method, which is executed by a terminal and includes:

[0006] determining a peak data rate of the terminal;

[0007] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0008] A second aspect of the present disclosure provides an information processing method, which is executed by a network device and includes:

[0009] determining the peak data rate of the terminal;

[0010] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0011] A third aspect of the present disclosure provides an information processing method, the method comprising:

[0012] The terminal and the network device determine a peak data rate of the terminal;

[0013] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0014] A fourth aspect of the present disclosure provides a terminal, including:

[0015] a processing module, configured to determine a peak data rate of the terminal;

[0016] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0017] A fifth embodiment of the present disclosure provides a network device, the network device comprising:

[0018] a processing module, configured to determine a peak data rate of the terminal;

[0019] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0020] The solution proposed in the embodiment of the present disclosure determines the peak data rate of the terminal; wherein the type of the terminal is the first type, and the peak data rate is agreed upon by the protocol. The peak data rate of the first type of terminal can be determined based on the protocol agreement, thereby avoiding ambiguity in the determination of the peak rate between the network side and the terminal side, and can effectively save signaling overhead and improve the communication efficiency of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0022] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0023] FIG2A is an interactive schematic diagram of an information processing method provided by an embodiment of the present disclosure;

[0024] FIG3A is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0025] FIG3B is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0026] FIG4A is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0027] FIG4B is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0028] FIG5 is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0029] FIG6A is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure;

[0030] FIG6B is a schematic structural diagram of a network device provided by an embodiment of the present disclosure;

[0031] FIG7A is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0032] FIG7B is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0033] The embodiments of the present disclosure provide an information processing method and apparatus, a communication device, a communication system, and a storage medium.

[0034] In a first aspect, an embodiment of the present disclosure provides an information processing method, which is executed by a terminal and includes:

[0035] determining a peak data rate of the terminal;

[0036] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0037] In the above embodiment, the peak data rate of the first type of terminal can be determined based on the protocol agreement, which avoids ambiguity between the network side and the terminal side in determining the peak rate, can effectively save signaling overhead, and improve the communication efficiency of the system.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information of the terminal is sent to a network device;

[0039] The capability information includes at least one of the following:

[0040] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for uplink channels;

[0041] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for the downlink channel;

[0042] an uplink modulation order supported by the terminal;

[0043] downlink modulation order supported by the terminal;

[0044] Scale factor.

[0045] In the above embodiment, the peak data rate of the first type of terminal can be determined based on the protocol agreement, the terminal capability information reporting behavior is clarified, and ambiguity in the determination of the peak rate between the network side and the terminal side is avoided, which can effectively save signaling overhead and improve the communication efficiency of the system.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, at least one of the following information in the capability information is not applicable to the first type of terminal:

[0047] Uplink modulation order supported by the terminal;

[0048] Downlink modulation order supported by the terminal;

[0049] Scale factor.

[0050] In the above embodiment, the peak data rate of the first type of terminal can be determined based on the protocol agreement, and there is no need to report relevant parameters in the capability information to determine the peak data rate of the terminal, which can effectively save signaling overhead, reduce the calculation complexity of the terminal and network equipment, and improve the communication efficiency of the system.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the capability information is further used to determine a peak data rate of the second type of terminal.

[0052] In the above embodiment, the peak data rate of the second type of terminal can be determined based on the terminal capability, thereby improving the universality of the solution and the communication efficiency of the system.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

[0054] In the above embodiment, the protocol may stipulate that the data rate of the uplink channel and the data rate of the downlink channel of the first type of terminal are the same or different, which can improve the flexibility of the solution, increase channel utilization, and enhance system communication efficiency.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the peak data rate of the first type of terminal supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminal supporting full-duplex frequency division multiplexing FD-FDD.

[0056] In the above embodiment, the protocol may stipulate that the first type of terminal devices supporting half-duplex and full-duplex have the same peak data rate, which can reduce the computational complexity of the terminal and the network device and improve the communication efficiency of the system.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

[0058] In the above embodiment, the protocol may stipulate that the first type of terminals supporting different modulation orders have the same peak data rate, which can reduce the computational complexity of the terminals and network devices and improve the communication efficiency of the system.

[0059] In combination with some embodiments of the first aspect, in some embodiments, the peak data rate of multiple terminals of the first type is the same, wherein each terminal of the first type supports a different number of MIMO layers of uplink and / or downlink channels.

[0060] In the above embodiment, the protocol may stipulate that the first type of terminals supporting different numbers of MIMO layers have the same peak data rate, which can reduce the computational complexity of the terminals and network devices and improve the communication efficiency of the system.

[0061] In a second aspect, an embodiment of the present disclosure provides an information processing method, which is executed by a network device and includes:

[0062] determining the peak data rate of the terminal;

[0063] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0064] In the above embodiment, the peak data rate of the first type of terminal can be determined based on the protocol agreement, which avoids ambiguity between the network side and the terminal side in determining the peak rate, can effectively save signaling overhead, and improve the communication efficiency of the system.

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

[0066] receiving capability information of the terminal sent by the terminal;

[0067] The capability information includes at least one of the following:

[0068] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for uplink channels;

[0069] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for the downlink channel;

[0070] an uplink modulation order supported by the terminal;

[0071] downlink modulation order supported by the terminal;

[0072] Scale factor.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, at least one of the following information in the capability information is not applicable to the first type of terminal:

[0074] Uplink modulation order supported by the terminal;

[0075] Downlink modulation order supported by the terminal;

[0076] Scale factor.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is further used to determine a peak data rate of the second type of terminal.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the peak data rate of the first type of terminal supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminal supporting full-duplex frequency division multiplexing FD-FDD.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the peak data rate of multiple terminals of the first type is the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the peak data rate of multiple terminals of the first type is the same, wherein each terminal of the first type supports a different number of MIMO layers of uplink and / or downlink channels.

[0082] In a third aspect, an embodiment of the present disclosure provides an information processing method, the method comprising:

[0083] The terminal and the network device determine a peak data rate of the terminal;

[0084] The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0085] In the above embodiment, the peak data rate of the first type of terminal can be determined based on the protocol agreement, which avoids ambiguity between the network side and the terminal side in determining the peak rate, can effectively save signaling overhead, and improve the communication efficiency of the system.

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

[0087] The terminal sends the capability information of the terminal to the network device;

[0088] The capability information includes at least one of the following:

[0089] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for uplink channels;

[0090] The maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal for the downlink channel;

[0091] an uplink modulation order supported by the terminal;

[0092] downlink modulation order supported by the terminal;

[0093] Scale factor.

[0094] In conjunction with some embodiments of the third aspect, in some embodiments, at least one of the following information in the capability information is not applicable to the first type of terminal:

[0095] Uplink modulation order supported by the terminal;

[0096] Downlink modulation order supported by the terminal;

[0097] Scale factor.

[0098] In conjunction with some embodiments of the third aspect, in some embodiments, the capability information is further used to determine a peak data rate of the second type of terminal.

[0099] In combination with some embodiments of the third aspect, in some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

[0100] In combination with some embodiments of the third aspect, in some embodiments, the peak data rate of the first type of terminal supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminal supporting full-duplex frequency division multiplexing FD-FDD.

[0101] In combination with some embodiments of the third aspect, in some embodiments, the peak data rate of multiple terminals of the first type is the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

[0102] In combination with some embodiments of the third aspect, in some embodiments, the peak data rate of multiple first-type terminals is the same, wherein each first-type terminal supports a different number of MIMO layers for uplink and / or downlink channels.

[0103] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0104] In a fifth aspect, an embodiment of the present disclosure proposes a network device, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute the second aspect and the optional implementation method of the second aspect.

[0105] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0106] In a seventh aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0107] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0108] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0109] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0110] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0111] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect and its optional implementation, the second aspect and its optional implementation.

[0112] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0113] The present disclosure provides an information processing method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "information processing method" and "information processing method" and "communication method" are interchangeable; the terms "information processing apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0114] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0115] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0116] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0117] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0118] In the embodiments of the present disclosure, “plurality” refers to two or more.

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

[0120] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0121] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0122] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0123] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0124] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0125] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0126] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0127] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0128] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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", "bandwidth part (BWP)", etc.

[0129] In some embodiments, "terminal" or "terminal device" may be referred to as "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, client, etc.

[0130] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0132] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0133] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0134] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

[0135] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, a reduced capability (RedCap) terminal device, and an evolved reduced capability (eRedCap) terminal device, but is not limited to these.

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

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

[0138] In some embodiments, the network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0139] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0140] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0141] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0142] In the embodiment of the present disclosure, the peak data rate of the terminal is related to the capability of the terminal.

[0143] Optionally, the maximum transmission data rate of the NR terminal can be determined according to the following formula:

[0144] Where Mbps is the transmission rate unit, megabits per second, J is the number of component carriers (CCs) aggregated in a band or band combination; R max =948 / 1024;

[0145] For the jth component carrier,

[0146] The higher layer parameter maxNumberMIMO-LayersPDSCH (maximum number of multiple-input multiple-output (MIMO) layers of the Physical Downlink Shared Channel (PDSCH)) for the downlink, and maxNumberMIMO-LayersCB-PUSCH (maximum number of MIMO layers for the Physical Uplink Shared Channel (PUSCH) based on code blocks (CB)) and maxNumberMIMO-LayersNonCB-PUSCH (maximum number of MIMO layers for non-code block PUSCH) for the uplink, reported by the terminal based on UE capability signaling;

[0147] The supportedModulationOrderDL high-level parameter for the downlink (supported downlink modulation order) used for downlink maximum data rate calculation, and the supportedModulationOrderUL high-level parameter for the uplink (supported uplink modulation order) used for uplink maximum rate calculation, reported by the terminal based on UE capability signaling. The modulation order actually supported by the terminal can be greater than the reported parameter;

[0148] f (j) The scaling factor is given by the higher-layer parameter scalingFactor, which can take values ​​of 1, 0.8, 0.75, and 0.4. This parameter is also reported by the terminal based on UE capabilities.

[0149] μ is a system parameter (numerology), and its value is related to the sub-carrier spacing (SCS). The corresponding cyclic prefix is ​​controlled by the parameter cyclicPrefix.

[0150] is the average OFDM symbol duration in a subframe with system parameter μ, for example, It is assumed that the cyclic prefix corresponding to μ is a normal cyclic prefix;

[0151] is the bandwidth BW when the system parameter is μ (j) The maximum resource block (RB) allocation in (j) is the maximum bandwidth supported by the UE given the frequency band or frequency band combination;

[0152] OH (j) is the cost, and its value is as follows:

[0153] For the downlink frequency range FR1, the value is 0.14.

[0154] For the downlink frequency range FR2, the value is 0.18,

[0155] For the uplink frequency range FR1, the value is 0.08.

[0156] For the uplink frequency range FR2, the value is 0.10.

[0157] As described above, v, Q, and f are all parameters related to the capabilities of the terminal, and can be sent by the terminal to the network device through related signaling of the terminal capability report.

[0158] In some embodiments, the peak data rate of the terminal can be used to constrain the size of the transmission block (TB (Transmission Block) size, TBS) scheduled by the network device.

[0159] Specifically, it can be the ratio of the sum of all TBSs of a terminal scheduled by the network device in a time slot to the duration of the slot, which needs to be within the constraint range of the peak data rate.

[0160] In some embodiments, for an eRedCap terminal, the number of RBs supported by its data channel is further reduced based on the R17RedCap design, and the peak rate will be further reduced. Therefore, the peak rate determination method needs to be redefined.

[0161] The information processing method and device provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0162] FIG2A is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information processing method, which includes:

[0163] Step S2101 : Terminal 101 sends capability information to network device 102 .

[0164] In some embodiments, the capability information is used to indicate the capability of the terminal 101 .

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

[0166] The maximum number of multiple-input multiple-output (MIMO) layers supported by terminal 101 for uplink channels;

[0167] The maximum number of multiple-input multiple-output (MIMO) layers supported by terminal 101 for the downlink channel;

[0168] The uplink modulation order supported by terminal 101;

[0169] The downlink modulation order supported by terminal 101;

[0170] Scale factor.

[0171] Optionally, the maximum number of MIMO layers of the uplink channel supported by the terminal 101 may be indicated by at least one of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0172] Optionally, the maximum number of MIMO layers of the downlink channel supported by the terminal 101 may be indicated by a parameter maxNumberMIMO-LayersPDSCH.

[0173] Optionally, the uplink modulation order supported by the terminal 101 may be indicated by a parameter supportedModulationOrderUL.

[0174] Optionally, the downlink modulation order supported by the terminal 101 may be indicated by a parameter supportedModulationOrderDL.

[0175] Optionally, a scaling factor may be indicated by the parameter scalingFactor.

[0176] In some embodiments, the name of the capability information is not limited, and may be, for example, “capability information”, “terminal capability”, “terminal capability information”, “first type of terminal capability”, etc.

[0177] Optionally, the type of the terminal 101 is the first type or the second type.

[0178] Optionally, the first type of terminal 101 may be an eRedCap terminal.

[0179] Optionally, the second type of terminal 101 may be a non-eRedCap terminal.

[0180] Alternatively, the first type of terminal 101 may be a RedCap terminal.

[0181] Optionally, the second type of terminal 101 may be a normal terminal.

[0182] In some embodiments, the type of the terminal 101 is a first type, and at least one of the following in the capability information is not applicable to the terminal 101 of the first type:

[0183] Uplink modulation order supported by the terminal;

[0184] Downlink modulation order supported by the terminal;

[0185] Scale factor.

[0186] Optionally, not applicable to the first type of terminal 101 may mean that the capability information sent by the first type of terminal 101 to the network device 102 does not include at least one of the above information, or it may mean that the capability information sent by the first type of terminal 101 to the network device 102 includes at least one of the above information, but the at least one of the above information is not used by the network device 102 to determine the peak data rate of the terminal 101.

[0187] In some embodiments, the type of the terminal 101 is the second type, and the capability information is further used by the network device 102 to determine the peak data rate of the second type of terminal 101. That is, the network device 102 can calculate and determine the peak data rate of the second type of terminal 101 based on the capability information.

[0188] In some embodiments, the type of the terminal 101 is the first type, and the capability information is not used by the network device 102 to determine the peak data rate of the first type of terminal 101. That is, the network device 102 does not calculate and determine the peak data rate of the first type of terminal 101 based on the capability information.

[0189] Step S2102 , terminal 101 obtains the peak data rate of terminal 101 .

[0190] In some embodiments, the terminal 101 is of the first type, and the peak data rate is agreed upon by a protocol. The first type terminal 101 can obtain the peak data rate agreed upon by the protocol.

[0191] Optionally, the first type mentioned above may be, for example, an eRedCap terminal.

[0192] Optionally, the first type mentioned above may be, for example, a RedCap terminal.

[0193] Optionally, the peak rate may be one or more values ​​agreed upon by a protocol.

[0194] In some embodiments, the type of the terminal 101 is the second type, and the peak data rate is determined based on capability information of the second type of terminal 101 .

[0195] Furthermore, the terminal 101 can perform subsequent data transmission based on the acquired peak data rate, and the network device 102 can schedule resources of the terminal 101 based on the peak data rate.

[0196] In some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal agreed upon in the protocol may be different from the peak data rate corresponding to the downlink channel of the first type of terminal.

[0197] In some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal agreed upon in the protocol may be the same as the peak data rate corresponding to the downlink channel of the first type of terminal.

[0198] In some embodiments, the peak data rate of the first type of terminal supporting half-duplex (HD) frequency division duplex (FDD) agreed upon by the protocol may be the same as the peak data rate of the first type of terminal supporting full-duplex (FD) FDD.

[0199] In some embodiments, the peak data rate of the first type of terminal supporting HD-FDD agreed upon in the protocol may also be different from the peak data rate of the first type of terminal supporting FD-FDD.

[0200] In some embodiments, the protocol-agreed peak data rates of terminals of the first type supporting different uplink and / or downlink modulation orders may be the same. That is, the protocol may stipulate that the peak data rates of multiple terminals of the first type are the same, where each terminal of the first type supports a different uplink and / or downlink modulation order.

[0201] In some embodiments, the peak rates of the first type of terminals supporting different uplink and / or downlink modulation orders as agreed upon by the protocol may also be different.

[0202] Optionally, the first type of terminals supporting different uplink modulation orders may have the same peak data rate.

[0203] Optionally, the first type of terminals supporting different uplink modulation orders may have different peak data rates.

[0204] Optionally, the first type of terminals supporting different downlink modulation orders may have the same peak data rate.

[0205] Optionally, the first type of terminals supporting different downlink modulation orders may have different peak data rates.

[0206] Optionally, the first type of terminals supporting at least one downlink modulation order in the first set may have the same peak data rate, the first type of terminals supporting at least one downlink modulation order in the second set may have the same peak data rate, and the two peak data rates are different, etc., which is not specifically limited in the embodiments of the present disclosure.

[0207] In some embodiments, the protocol-agreed peak data rates for terminals of the first type supporting different numbers of MIMO layers for uplink and / or downlink channels may be the same. That is, the protocol may stipulate that the peak data rates for multiple terminals of the first type are the same, where each terminal of the first type supports a different number of MIMO layers for uplink and / or downlink channels.

[0208] In some embodiments, the peak rates of the first type of terminals supporting different numbers of MIMO layers for uplink and / or downlink channels as agreed upon in the protocol may also be different.

[0209] Optionally, the first type of terminals supporting different numbers of uplink MIMO layers may have the same peak data rate.

[0210] Optionally, the first type of terminals supporting different numbers of uplink MIMO layers may have different peak data rates.

[0211] Optionally, the first type of terminals supporting different numbers of downlink MIMO layers may have the same peak data rate.

[0212] Optionally, the first type of terminals supporting different numbers of downlink MIMO layers may have different peak data rates.

[0213] Optionally, the first type of terminals supporting at least one uplink MIMO layer in the first set may have the same peak data rate, the first type of terminals supporting at least one uplink MIMO layer in the second set may have the same peak data rate, and the two peak data rates are different, etc., which is not specifically limited in the embodiments of the present disclosure.

[0214] Step S2103 , the network device 102 obtains the peak data rate of the terminal 101 .

[0215] In some embodiments, the terminal 101 is of the first type, and the peak data rate is agreed upon by a protocol. The first type terminal 101 can obtain the peak data rate agreed upon by the protocol.

[0216] Optionally, the first type mentioned above may be, for example, an eRedCap terminal.

[0217] Optionally, the first type mentioned above may be, for example, a RedCap terminal.

[0218] Optionally, the peak rate may be one or more values ​​agreed upon by a protocol.

[0219] In some embodiments, the type of the terminal 101 is the second type, and the peak data rate is determined based on capability information of the second type of terminal 101 .

[0220] Furthermore, the terminal 101 can perform subsequent data transmission based on the acquired peak data rate, and the network device 102 can schedule resources of the terminal 101 based on the peak data rate.

[0221] In some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal agreed upon in the protocol may be different from the peak data rate corresponding to the downlink channel of the first type of terminal.

[0222] In some embodiments, the peak data rate corresponding to the uplink channel of the first type of terminal agreed upon in the protocol may be the same as the peak data rate corresponding to the downlink channel of the first type of terminal.

[0223] In some embodiments, the peak data rate of the first type of terminal supporting half-duplex (HD) frequency division duplex (FDD) agreed upon by the protocol may be the same as the peak data rate of the first type of terminal supporting full-duplex (FD) FDD.

[0224] In some embodiments, the peak data rate of the first type of terminal supporting HD-FDD agreed upon in the protocol may also be different from the peak data rate of the first type of terminal supporting FD-FDD.

[0225] In some embodiments, the protocol-agreed peak data rates of terminals of the first type supporting different uplink and / or downlink modulation orders may be the same. That is, the protocol may stipulate that the peak data rates of multiple terminals of the first type are the same, where each terminal of the first type supports a different uplink and / or downlink modulation order.

[0226] In some embodiments, the peak rates of the first type of terminals supporting different uplink and / or downlink modulation orders as agreed upon by the protocol may also be different.

[0227] Optionally, the first type of terminals supporting different uplink modulation orders may have the same peak data rate.

[0228] Optionally, the first type of terminals supporting different uplink modulation orders may have different peak data rates.

[0229] Optionally, the first type of terminals supporting different downlink modulation orders may have the same peak data rate.

[0230] Optionally, the first type of terminals supporting different downlink modulation orders may have different peak data rates.

[0231] Optionally, the first type of terminals supporting at least one downlink modulation order in the first set may have the same peak data rate, the first type of terminals supporting at least one downlink modulation order in the second set may have the same peak data rate, and the two peak data rates are different, etc., which is not specifically limited in the embodiments of the present disclosure.

[0232] In some embodiments, the protocol-agreed peak data rates for terminals of the first type supporting different numbers of MIMO layers for uplink and / or downlink channels may be the same. That is, the protocol may stipulate that the peak data rates for multiple terminals of the first type are the same, where each terminal of the first type supports a different number of MIMO layers for uplink and / or downlink channels.

[0233] In some embodiments, the peak rates of the first type of terminals supporting different numbers of MIMO layers for uplink and / or downlink channels as agreed upon in the protocol may also be different.

[0234] Optionally, the first type of terminals supporting different numbers of uplink MIMO layers may have the same peak data rate.

[0235] Optionally, the first type of terminals supporting different numbers of uplink MIMO layers may have different peak data rates.

[0236] Optionally, the first type of terminals supporting different numbers of downlink MIMO layers may have the same peak data rate.

[0237] Optionally, the first type of terminals supporting different numbers of downlink MIMO layers may have different peak data rates.

[0238] Optionally, the first type of terminals supporting at least one uplink MIMO layer in the first set may have the same peak data rate, the first type of terminals supporting at least one uplink MIMO layer in the second set may have the same peak data rate, and the two peak data rates are different, etc., which is not specifically limited in the embodiments of the present disclosure.

[0239] In some embodiments, the type of the terminal 101 is the second type, and the peak data rate is determined based on capability information of the second type of terminal 101 .

[0240] Optionally, the peak data rate of the second type of terminal 101 is

[0241] Where J is the number of component carriers (CCs) aggregated in a band or band combination; R max =948 / 1024;

[0242] For the jth component carrier,

[0243] The higher layer parameter maxNumberMIMO-LayersPDSCH (maximum number of MIMO layers for PDSCH) for the downlink, and the higher layer parameters maxNumberMIMO-LayersCB-PUSCH (maximum number of MIMO layers for code block-based PUSCH) and maxNumberMIMO-LayersNonCB-PUSCH (maximum number of MIMO layers for non-code block-based PUSCH) for the uplink reported by terminal 101 in the capability information;

[0244] The higher-layer parameter supportedModulationOrderDL (supported downlink modulation order) for the downlink and the higher-layer parameter supportedModulationOrderUL (supported uplink modulation order) for the uplink reported by the terminal 101 in the capability information. The modulation order actually supported by the terminal 101 may be greater than the reported parameter;

[0245] f (j) is the scaling factor given by the higher-layer parameter scalingFactor reported by the terminal 101 in the capability information, where the scaling factor can take values ​​of 1, 0.8, 0.75, and 0.4;

[0246] μ is a system parameter (numerology), and its value is related to the sub-carrier spacing. The corresponding cyclic prefix is ​​controlled by the parameter cyclicPrefix.

[0247] is the average OFDM symbol duration in a subframe with system parameter μ, for example, It is assumed that the cyclic prefix corresponding to μ is a normal cyclic prefix;

[0248] is the bandwidth BW when the system parameter is μ (j) The maximum resource block RB allocation in, where BW (j) is the maximum bandwidth supported by the UE given the frequency band or frequency band combination;

[0249] OH (j)is the cost, and its value is as follows:

[0250] For the downlink frequency range FR1, the value is 0.14.

[0251] For the downlink frequency range FR2, the value is 0.18,

[0252] For the uplink frequency range FR1, the value is 0.08.

[0253] For the uplink frequency range FR2, the value is 0.10.

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

[0255] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0256] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0257] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0258] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0259] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0260] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0261] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0262] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0263] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0264] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0265] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step 2101 can be implemented as an independent embodiment, step 2102 can be implemented as an independent embodiment, step 2103 can be implemented as an independent embodiment, steps 2101+2102 can be implemented as an independent embodiment, steps 2101+2103 can be implemented as an independent embodiment, steps 2102+2103 can be implemented as an independent embodiment, steps 2101+2102+2103 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0266] In some embodiments, steps 2101 and 2102 may be executed in an exchanged order or simultaneously, steps 2101 and 2103 may be executed in an exchanged order or simultaneously, and steps 2102 and 2103 may be executed in an exchanged order or simultaneously.

[0267] In some embodiments, step 2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0268] In some embodiments, step 2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0269] In some embodiments, step 2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0270] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0271] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by terminal 101 and includes:

[0272] Step S3101 , sending capability information to the network device 102 .

[0273] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0274] In some embodiments, the terminal 101 sends capability information to the network device 102, but is not limited thereto and the capability information may also be sent to other entities.

[0275] Optionally, the capability information is used by the network device 102 to determine the peak data rate of the second type of terminal 101. Optional implementations thereof may be found in the optional implementation of step S2103 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0276] Optionally, the capability information is not used to determine the peak data rate of the first type of terminal 101. The peak data rate of the first type of terminal 101 is determined by the protocol. For alternative implementations, see the alternative implementation of step S2103 in FIG. 2A and other related portions of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0277] Step S3102, obtaining the peak data rate.

[0278] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0279] In some embodiments, step S3102 is omitted, and the terminal 101 autonomously implements the function indicated by the peak data rate, or the above function is default or by default.

[0280] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3102. For example, step 3101 may be implemented as an independent embodiment, step 3102 may be implemented as an independent embodiment, steps 3101+3102 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0281] In some embodiments, steps 3101 and 3102 may be performed in an interchanged order or simultaneously.

[0282] In some embodiments, step 3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0283] In some embodiments, step 3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0284] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to an information processing method, which is executed by terminal 101 and includes:

[0285] Step S3201, obtain the peak data rate.

[0286] Optional implementations of step S3201 can be found in step S2102 of FIG. 2A , optional implementations of step S3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0287] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by the network device 102 and includes:

[0288] Step S4101 , receiving capability information sent by terminal 101 .

[0289] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0290] In some embodiments, the network device 102 receives the first information sent by the terminal 101, but is not limited thereto and may also receive capability information sent by other entities.

[0291] Optionally, the capability information is used to determine a peak data rate of the second type of terminal 101 .

[0292] Optionally, the capability information is not used to determine the peak data rate of the first type of terminal 101. The peak data rate of the first type of terminal 101 is determined by the protocol. For alternative implementations, see the alternative implementation of step S2102 in FIG. 2A and other related portions of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0293] Step S4102 , determining the peak data rate of terminal 101 .

[0294] The optional implementation of step S4102 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0295] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4102. For example, step 4101 may be implemented as an independent embodiment, step 4102 may be implemented as an independent embodiment, steps 4101+4102 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0296] In some embodiments, steps 4101 and 4102 may be performed in an interchanged order or simultaneously.

[0297] In some embodiments, step 4101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0298] In some embodiments, step 4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0299] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to an information processing method, which is executed by the network device 102 and includes:

[0300] Step S4201 , determining the peak data rate of terminal 101 .

[0301] The optional implementation of step S4201 can refer to the optional implementation of step S2103 in Figure 2A, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2A and 4A, which will not be repeated here.

[0302] Optionally, the type of the terminal 101 is the second type, and the peak data rate of the second type terminal 101 is determined based on the capability information sent by the terminal 101. For optional implementations, refer to the optional implementations of step S2101 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0303] FIG5 is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG5 , the method according to the embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0304] Step S5101: The terminal determines a peak data rate of the terminal, wherein the type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

[0305] Step S5102: The network device determines the peak data rate of the terminal, wherein the type of the terminal is the first type, and the peak data rate is agreed upon by the protocol.

[0306] The optional implementation methods of step S5101 and step S5102 can refer to the steps in any embodiment or any multiple embodiments in the above-mentioned Figures 2A-2B, 3A-3B, and 4A-4B, and other related parts in the embodiments involved in Figures 2A-2B, 3A-3B, and 4A-4B.

[0307] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0308] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5102. For example, step 5101 may be implemented as an independent embodiment, step 5102 may be implemented as an independent embodiment, steps 5101+5102 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0309] In some embodiments, steps 5101 and 5102 may be performed in an interchanged order or simultaneously.

[0310] In some embodiments, step 5101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0311] In some embodiments, step 5102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0312] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0313] The following is an exemplary introduction to the methods described in the above embodiments.

[0314] In the disclosed embodiment, the specific value of the peak data rate of the eRedCap terminal can be directly specified in the protocol.

[0315] In some embodiments, the uplink and downlink peak rates of the eRedCap terminal can be defined as different values.

[0316] In some embodiments, HD-FDD and FD-FDD eRedCap terminals may have the same peak rate value.

[0317] In some embodiments, eRedCap terminals supporting different modulation orders may have the same peak rate value.

[0318] In some embodiments, eRedCap terminals supporting different MIMO layers may have the same peak rate value.

[0319] In some embodiments, terminal capability-related parameters such as supportedModulationOrderUL, supportedModulationOrderDL, and scalingFactor are only used by first-type terminals to report terminal capabilities and are not applicable to second-type terminals. Second-type terminals are eRedCap terminals. First-type terminals are non-eRedCap terminals.

[0320] As an example, for the parameter supportedModulationOrderUL, the protocol may stipulate that the capability is not applicable to eRedCap terminals (for example, the protocol may stipulate that the above capability is not applicable to eRedCap UEs).

[0321] As an example, for the parameter supported ModulationOrderDL, the protocol may stipulate that the capability is not applicable to eRedCap terminals (for example, the protocol may stipulate that the above capability is not applicable to eRedCap UEs).

[0322] As an example, for the parameter scalingFactor, the protocol may stipulate that the capability is not applicable to eRedCap terminals (for example, the protocol may stipulate that the above capability is not applicable to eRedCap UEs).

[0323] In some embodiments, both the first type terminal and the second type terminal may report the maximum uplink or downlink MIMO layer supported by the terminal through parameters such as maxNumberMIMO-LayersPDSCH, maxNumberMIMO-LayersCB-PUSCH, and maxNumberMIMO-LayersNonCB-PUSCH.

[0324] Optionally, for the first type of terminal, this parameter may also be used to determine the peak rate;

[0325] Optionally, for the second terminal type, this parameter cannot be used to determine the peak rate.

[0326] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0327] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0328] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0329] Figure 6A is a structural diagram of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 6A, the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the processing module is used to determine the peak data rate of the terminal; wherein the type of the terminal is the first type, and the peak data rate is agreed upon by the protocol. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step 2101, but not limited to this) executed by the terminal 101 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps (such as step 2102, step 2103, but not limited to this) executed by the terminal 101 in any of the above methods, which will not be repeated here.

[0330] Figure 6B is a structural diagram of the network device proposed in an embodiment of the present disclosure. As shown in Figure 6B, the network device 6200 may include: at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the processing module is used to determine the peak data rate of the terminal; wherein the type of the terminal is the first type, and the peak data rate is agreed upon by the protocol. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step 2101, but not limited to this) performed by the network device 102 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps (for example, step 2102, step 2103, but not limited to this) performed by the network device 102 in any of the above methods, which will not be repeated here.

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

[0332] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0333] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0334] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0335] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2101, but not limited thereto), and the processor 7101 performs at least one of the other steps (for example, step 2102, step 2103, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0336] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Alternatively, all or part of the memories 7103 may be located outside the communication device 7100. In alternative embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memory 7102 and may be configured to receive data from the memory 7102 or other devices, or to send data to the memory 7102 or other devices. For example, the interface circuits 7104 may read data stored in the memory 7102 and send the data to the processor 7101.

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

[0338] 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0339] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0340] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Alternatively, all or part of memory 7203 may be located external to chip 7200. Optionally, interface circuit 7202 is connected to memory 7203 and may be used to receive data from memory 7203 or other devices, or may be used to send data to memory 7203 or other devices. For example, interface circuit 7202 may read data stored in memory 7203 and send the data to processor 7201.

[0341] In some embodiments, the interface circuit 7202 performs at least one of the communication steps (e.g., steps 2101, 2102, 2201, and 2202) of the aforementioned method. For example, the interface circuit 7202 performing the communication steps (e.g., steps 2101, 2102, 2201, and 2202) of the aforementioned method means that the interface circuit 7202 performs data exchange between the processor 7201, chip 7200, memory 7203, or a transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps.

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

[0343] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0344] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0345] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0346] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0347] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0348] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0349] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. An information processing method, characterized in that: The method is executed by a terminal, and includes: determining a peak data rate of the terminal; The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

2. The method according to claim 1, characterized in that The method further comprises: Sending capability information of the terminal to a network device; The capability information includes at least one of the following information: The maximum number of multiple-input multiple-output MIMO layers of the uplink channel supported by the terminal; The maximum number of multiple-input multiple-output MIMO layers of the downlink channel supported by the terminal; An uplink modulation order supported by the terminal; downlink modulation order supported by the terminal; Scale factor.

3. The method according to claim 2, characterized in that At least one of the following information in the capability information is not applicable to the first type of terminal: The uplink modulation order supported by the terminal; Downlink modulation order supported by the terminal; Scale factor.

4. The method according to claim 2, characterized in that: The capability information is also used to determine a peak data rate for terminals of the second type.

5. The method according to any one of claims 1 to 4, characterized in that: The peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

6. The method according to any one of claims 1 to 4, characterized in that: The peak data rate of the first type of terminals supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminals supporting full-duplex frequency division multiplexing FD-FDD.

7. The method according to any one of claims 1 to 4, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

8. The method according to any one of claims 1 to 4, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports a different number of MIMO layers of uplink and / or downlink channels.

9. An information processing method, characterized in that: The method is performed by a network device, and the method includes: determining a peak data rate of the terminal; The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

10. The method according to claim 9, characterized in that The method further comprises: receiving capability information of the terminal sent by the terminal; The capability information includes at least one of the following information: The maximum number of multiple-input multiple-output MIMO layers of the uplink channel supported by the terminal; The maximum number of multiple-input multiple-output MIMO layers of the downlink channel supported by the terminal; An uplink modulation order supported by the terminal; downlink modulation order supported by the terminal; Scale factor.

11. The method according to claim 9, characterized in that At least one of the following information in the capability information is not applicable to the first type of terminal: The uplink modulation order supported by the terminal; Downlink modulation order supported by the terminal; Scale factor.

12. The method according to claim 10, characterized in that The capability information is also used to determine a peak data rate for terminals of the second type.

13. The method according to any one of claims 9 to 12, characterized in that: The peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

14. The method according to any one of claims 9 to 12, characterized in that: The peak data rate of the first type of terminals supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminals supporting full-duplex frequency division multiplexing FD-FDD.

15. The method according to any one of claims 9 to 12, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

16. The method according to any one of claims 9 to 12, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports a different number of MIMO layers of uplink and / or downlink channels.

17. An information processing method, characterized in that: The method comprises: The terminal and the network device determine a peak data rate of the terminal; The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

18. The method according to claim 17, characterized in that The method further comprises: The terminal sends the capability information of the terminal to the network device; The capability information includes at least one of the following information: The maximum number of multiple-input multiple-output MIMO layers of the uplink channel supported by the terminal; The maximum number of multiple-input multiple-output MIMO layers of the downlink channel supported by the terminal; An uplink modulation order supported by the terminal; downlink modulation order supported by the terminal; Scale factor.

19. The method according to claim 18, characterized in that At least one of the following information in the capability information is not applicable to the first type of terminal: The uplink modulation order supported by the terminal; Downlink modulation order supported by the terminal; Scale factor.

20. The method according to claim 18, characterized in that The capability information is also used to determine a peak data rate for terminals of the second type.

21. The method according to any one of claims 17 to 20, characterized in that: The peak data rate corresponding to the uplink channel of the first type of terminal is the same as or different from the peak data rate corresponding to the downlink channel of the first type of terminal.

22. The method according to any one of claims 17 to 20, characterized in that: The peak data rate of the first type of terminals supporting half-duplex frequency division multiplexing HD-FDD is the same as the peak data rate of the first type of terminals supporting full-duplex frequency division multiplexing FD-FDD.

23. The method according to any one of claims 17 to 20, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports different uplink and / or downlink modulation orders.

24. The method according to any one of claims 17 to 20, characterized in that: The peak data rates of multiple terminals of the first type are the same, wherein each terminal of the first type supports a different number of MIMO layers of uplink and / or downlink channels.

25. A terminal, characterized in that: The terminal comprises: A processing module, configured to determine a peak data rate of the terminal; The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

26. A network device, characterized in that: The network equipment includes: A processing module, configured to determine a peak data rate of a terminal; The type of the terminal is the first type, and the peak data rate is agreed upon by a protocol.

27. A communication device, characterized in that: The terminal comprises: one or more processors; The terminal is used to execute the information processing method according to any one of claims 1 to 8.

28. A communication device, characterized in that: The network equipment includes: one or more processors; Wherein, the terminal is used to execute the information processing method described in any one of claims 9-16.

29. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the information processing method according to any one of claims 1 to 8, and the network device is configured to implement the information processing method according to any one of claims 9 to 16.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the information processing method according to any one of claims 1-8 or 9-16.

Images