Carrier indication method and system, and communication entity and storage medium
By acquiring carrier scheduling information and performing cross-carrier scheduling or multi-carrier scheduling, the problem of lack of scheduling solutions in NR V2X carrier aggregation scenario is solved, and efficient management and flexible scheduling of carrier resources are realized.
Patent Information
- Application Number
- PCT/CN2024/106442
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-18
- Filing Date
- 2024-07-19
- Publication Date
- 2025-03-27
AI Technical Summary
There is a lack of solutions to realize multi-carrier scheduling and cross-carrier scheduling in the existing NR V2X carrier aggregation scenarios, which makes it difficult to efficiently manage carrier resources in complex V2X communication scenarios.
By acquiring carrier scheduling information, cross-carrier scheduling and multi-carrier scheduling are realized. The specific steps include acquiring carrier scheduling information and performing cross-carrier scheduling or multi-carrier scheduling based on the information.
Multi-carrier scheduling and cross-carrier scheduling in V2X carrier aggregation scenario are realized, the efficiency and flexibility of carrier resource management are improved, and the needs of complex V2X communication scenarios are met.
Smart Images

Figure CN2024106442_27032025_PF_FP_ABST
Abstract
Description
Carrier indication method, system, communication entity and storage medium Technical Field
[0001] The present application relates to the field of communication technology, for example, to a carrier indication method, system, communication entity and storage medium. Background Art
[0002] With the continuous advancement of radio technology, a large number of radio services have emerged. In addition to cellular services between base stations and terminals, Long Term Evolution (LTE) and New Radio (NR) systems also include vehicle-to-everything (V2X) services, which are abbreviated as LTE V2X, LTE-V, or LTE sidelink in LTE and NR V2X, NR-V, or NR sidelink in NR. The link for V2X service communication is called a sidelink, sidelink, or sidelink (SL). The main channels include the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH). The PSCCH carries sidelink control information, and the PSSCH carries service data. When business data needs to be transmitted between devices, it is transmitted directly from the data source device to the target device without being forwarded by other network devices. This is direct communication between devices. The device is a user equipment (UE) with V2X functionality. SL can be divided into three main communication scenarios: the first is the in-coverage scenario, where both the data source and target devices are within the coverage of the base station; the second is the partial coverage scenario, where one of the data source and target devices is within the coverage of the base station, while the other is outside; and the third is the out-of-coverage scenario, where both the data source and target devices are outside the coverage of the base station. SL can be divided into two main communication modes: the first mode (abbreviated as mode 3 or mode 3 in LTE and mode 1 or mode 1 in NR), the resources for the device to send sidelink signals come from the scheduling of the base station; the second mode (abbreviated as mode 4 or mode 4 in LTE and mode 2 or mode 2 in NR), the device autonomously selects resources from the network-configured or pre-configured resource pool according to the resource selection strategy. The resource selection strategy mainly includes: sensing mechanism, partial sensing mechanism, and random selection mechanism.Taking NR as an example, when implementing Mode 1, the base station sends the Scheduling Control Field to UE1 via Downlink Control Information (DCI). This Scheduling Control Field specifies how UE1 schedules UE2. UE1 sends the Scheduling Control Field to UE2 via Sidelink Control Information (SCI). When implementing Mode 2, UE1 autonomously generates the Scheduling Control Field and sends it to UE2 via SCI.
[0003] In the latest NR systems involving V2X deployment scenarios, carrier aggregation (CA) needs to be considered. Currently, there is no solution to define how to implement multi-carrier scheduling or cross-carrier scheduling in NR V2X CA scenarios.
[0004] Summary of the Invention
[0005] This embodiment of the present application provides a carrier indication method, which is applied to a communication entity. The method includes:
[0006] Obtain carrier scheduling information;
[0007] Cross-carrier scheduling or multi-carrier scheduling is performed according to the carrier scheduling information.
[0008] An embodiment of the present application provides a carrier indication system, including: a first communication entity and a second communication entity;
[0009] The first communication entity is configured to execute the carrier indication method of any of the above embodiments;
[0010] The second communication entity is configured to execute the carrier indication method of any one of the above embodiments.
[0011] An embodiment of the present application provides a communication entity, including: a processor; the processor is configured to implement the carrier indication method of any of the above embodiments when executing a computer program.
[0012] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, which implements the carrier indication method of any of the above embodiments when the computer program is executed by a processor.
[0013] With respect to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG1 is a schematic diagram of a network of an edge link communication system provided by an embodiment;
[0015] FIG2 is a schematic flow chart of a carrier indication method provided by an embodiment;
[0016] FIG3 is a schematic flow chart of another carrier indication method provided by an embodiment;
[0017] FIG4 is a schematic diagram of a multi-carrier scheduling set and a multi-carrier scheduling set indication field provided by an embodiment;
[0018] FIG5 is a schematic diagram of a carrier and a first carrier indication field for carrier aggregation provided by an embodiment;
[0019] FIG6 is another schematic diagram of a carrier and a first carrier indication field for carrier aggregation provided by an embodiment;
[0020] FIG7 is a schematic flow chart of another carrier indication method provided by an embodiment;
[0021] FIG8 is a schematic diagram of a carrier and a second carrier indication field for carrier aggregation provided by an embodiment;
[0022] FIG9 is a schematic structural diagram of a carrier indication system provided by an embodiment;
[0023] FIG10 is a schematic diagram of a carrier indication device provided by an embodiment;
[0024] FIG11 is a schematic structural diagram of a terminal provided by an embodiment. DETAILED DESCRIPTION
[0025] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
[0026] FIG1 is a networking diagram of a sidelink communication system provided by an embodiment. As shown in FIG1 , in a Sidelink communication system, when there is a service that needs to be transmitted between communication entities, the service data between the communication entities can be transmitted directly from the source communication entity to the target communication entity through the sidelink without being forwarded on the network side, that is, without being forwarded through the cellular link between the communication entity and the access network device. For example, in FIG1 , communication entity 1 and communication entity 2 can communicate directly through Sidelink without being forwarded on the network side. When communication entity 1 needs to send service data to communication entity 2, communication entity 1 is referred to as the source communication entity or data source device, and communication entity 2 is referred to as the target communication entity or target device. This technology can reduce the burden on the cellular network, reduce the battery power consumption of the communication entity, and improve the robustness of the network infrastructure, so as to meet the requirements of high data rate services and proximity services. It also supports direct communication in scenarios without network coverage, and can meet special communication needs such as public safety.
[0027] In the current NR side link CA scenario, there is no solution to define how communication entity 1 and communication entity 2 implement multi-carrier scheduling or how to implement cross-carrier scheduling.
[0028] The carrier indication method provided in this application can be applied to various wireless communication systems, such as LTE systems, fourth-generation mobile communication technology (4G) systems, fifth-generation mobile communication technology (5G) systems, LTE and 5G hybrid architecture systems, 5G NR systems, and new communication systems emerging in future communication developments, such as sixth-generation mobile communication technology (6G) systems. It is particularly suitable for sidelink communication systems networked based on the above systems, such as the sidelink communication system shown in Figure 1.
[0029] The communication entity in this embodiment includes at least one of the following: a network node, a terminal node, a radio resource control layer (RRC layer), a radio link control layer (RLC layer), a medium access control layer (MAC layer), and a physical layer (PHY layer).
[0030] The communication entity can be a device with wireless transceiver capabilities, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted, etc.); it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). Examples of some communication entities include: UE, mobile phone, mobile station, tablet computer, laptop computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA) and other user equipment that can be connected to the Internet, or virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc., or Internet of Things node in the Internet of Things, or vehicle-mounted communication device in the Internet of Vehicles, or entertainment, gaming equipment or system, or global positioning system equipment, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the communication entity.
[0031] The access network device is an access device that a communication entity uses to access the wireless communication system through a wireless method. It can be a base station, an evolved NodeB (eNB or eNodeB) in Long Term Evolution Advanced (LTEA), a transmission reception point (TRP), a base station in a 5G mobile communication system or the next generation Node B (gNB), a base station in a future mobile communication system, or an access node in a Wireless Fidelity (WiFi) system. The base station may include various macro base stations, micro base stations, home base stations, wireless remote stations, routers, WIFI devices, or various network-side devices such as primary cells and secondary cells, and location management function (LMF) devices. It can also be a module or unit that completes part of the functions of a base station, for example, it can be a centralized unit (CU) or a distributed unit (DU). The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device. In addition, the access network device can be referred to as a base station. Core network equipment may include access and mobility management network elements and session management network elements.
[0032] In an embodiment of the present application, a carrier indication method, system, communication entity and storage medium that can be operated in the above-mentioned wireless communication system are provided. By obtaining carrier scheduling information, cross-carrier scheduling or multi-carrier scheduling is performed according to the carrier scheduling information, thereby realizing multi-carrier scheduling or cross-carrier scheduling in the V2X carrier aggregation scenario.
[0033] The following describes a carrier indication method, a carrier indication system, a communication entity, and their technical effects.
[0034] FIG2 is a flow chart of a carrier indication method provided by an embodiment. The carrier indication method provided by this embodiment is applicable to a communication entity. The method includes the following steps.
[0035] Step 201: Acquire carrier scheduling information.
[0036] In one embodiment, the carrier scheduling information is used to indicate whether cross-carrier scheduling is performed.
[0037] When the carrier scheduling information indicates cross-carrier scheduling, the carrier scheduling information is also used to indicate the scheduled carrier in the cross-carrier scheduling.
[0038] Cross-carrier scheduling in this embodiment refers to the situation where the scheduling grant and transmission data are sent on different carriers. In other words, the downlink control information and / or sidelink control information of one carrier schedules the PSSCH of another carrier. The scheduled carrier in this embodiment refers to the carrier on which the PSSCH is scheduled.
[0039] In one embodiment, the carrier scheduling information is used to indicate whether multi-carrier scheduling is performed.
[0040] When the carrier scheduling information indicates multi-carrier scheduling, the carrier scheduling information is also used to indicate one or more scheduled carriers in the multi-carrier scheduling.
[0041] The multi-carrier scheduling in this embodiment refers to the downlink control information and / or side link control information of one carrier scheduling the PSSCH of one or more carriers.
[0042] When the communication entity in this embodiment is a data source device in an edge link communication system (also referred to as a first communication entity), step 201 includes at least one of the following: receiving carrier scheduling information from an access network device; generating carrier scheduling information; and pre-configuring carrier scheduling information.
[0043] Optionally, the pre-configured carrier scheduling information in this embodiment means that the carrier scheduling information is pre-set in the first communication entity.
[0044] Optionally, the first communication entity may also send carrier scheduling information to another communication entity connected thereto, that is, a target device in the side-link communication system, which may also be referred to as a second communication entity.
[0045] When the communication entity in this embodiment is a target device (i.e., a second communication entity) in an edge-link communication system, step 201 includes at least one of the following: receiving carrier scheduling information from another communication entity connected to the communication entity; and pre-configuring carrier scheduling information.
[0046] It can be understood that when the communication entity in this embodiment is a target device in the edge-link communication system, the other communication entity connected to the communication entity refers to a data source device in the edge-link communication system.
[0047] Optionally, the pre-configured carrier scheduling information in this embodiment means that the carrier scheduling information is pre-set in the second communication entity.
[0048] Step 202: Perform cross-carrier scheduling or multi-carrier scheduling according to the carrier scheduling information.
[0049] After the communication entity obtains the carrier scheduling information, it can perform cross-carrier scheduling or multi-carrier scheduling according to the content indicated in the carrier scheduling information.
[0050] Cross-carrier scheduling is performed according to the carrier scheduling information, for example, the PSCCH of carrier 2 may be scheduled in carrier 1.
[0051] Multi-carrier scheduling is performed according to the carrier scheduling information. For example, the PSCCHs of carrier 2, carrier 3, and carrier 4 may be scheduled in carrier 1.
[0052] The carrier indication method provided in this embodiment obtains carrier scheduling information and performs cross-carrier scheduling or multi-carrier scheduling according to the carrier scheduling information, thereby realizing multi-carrier scheduling or cross-carrier scheduling in the V2X carrier aggregation scenario.
[0053] Figure 3 is a flowchart illustrating another carrier indication method provided by one embodiment. Based on the embodiment shown in Figure 2 and various optional implementations, this embodiment provides a detailed description of how carrier scheduling information is used to indicate whether multi-carrier scheduling is in progress. As shown in Figure 3, the carrier indication method provided by this embodiment includes the following steps.
[0054] Step 301: Acquire carrier scheduling information.
[0055] In one embodiment, the carrier scheduling information in this embodiment is used to indicate whether multi-carrier scheduling is performed.
[0056] In one embodiment, the carrier scheduling information is further used to indicate one or more scheduled carriers in multi-carrier scheduling.
[0057] In one implementation, the carrier scheduling information may directly indicate one or more scheduled carriers in multi-carrier scheduling.
[0058] In another implementation, the carrier scheduling information indicates that multi-carrier scheduling is to be performed, and indicates one or more scheduled carriers in the multi-carrier scheduling. Of course, in this implementation, if the carrier scheduling information indicates that multi-carrier scheduling is not to be performed, then the carrier scheduling information does not indicate the scheduled carriers.
[0059] The following three examples illustrate how the carrier scheduling information indicates one or more scheduled carriers in multi-carrier scheduling.
[0060] Example 3.1
[0061] In this example, the carrier scheduling information is also used to indicate M multi-carrier scheduling sets. The m-th multi-carrier scheduling set includes Y m carriers. Wherein, M is an integer greater than 0, and m is an integer greater than 0 and less than or equal to M. m is an integer greater than 0, that is, the number of carriers in the multi-carrier scheduling set can be 1 or more.
[0062] It can be understood that carriers in one multi-carrier scheduling set among the M multi-carrier scheduling sets can be used for multi-carrier scheduling.
[0063] In this example, the one or more scheduled carriers indicated in the carrier scheduling information are located in a scheduled multi-carrier scheduling set among the M multi-carrier scheduling sets. Based on this, the carrier scheduling information includes a multi-carrier scheduling set indication field, which is used to indicate the index of the scheduled multi-carrier scheduling set. It can be understood that since the one or more scheduled carriers are located in a scheduled multi-carrier scheduling set among the M multi-carrier scheduling sets, indicating the index of the scheduled multi-carrier scheduling set through the multi-carrier scheduling set indication field is equivalent to indicating the one or more scheduled carriers through the multi-carrier scheduling set indication field.
[0064] It should be noted that the index of the scheduled multi-carrier scheduling set in this embodiment may also be referred to as an identifier of the scheduled multi-carrier scheduling set, or other information that can uniquely characterize the scheduled multi-carrier scheduling set.
[0065] Optionally, the multi-carrier scheduling set indication field includes N bits, where N=ceil(log2M), and ceil(log2M) represents the smallest integer rounded up to log2M.
[0066] Figure 4 is a schematic diagram of a multi-carrier scheduling set and a multi-carrier scheduling set indication field provided by an embodiment. As shown in Figure 4, it is assumed that there are 5 multi-carrier scheduling sets, that is, M is equal to 5. As shown in Figure 4: multi-carrier scheduling set 0 includes: (carrier 01, carrier 02, carrier 03); multi-carrier scheduling set 1 includes: (carrier 11, carrier 12, carrier 13); multi-carrier scheduling set 2 includes: (carrier 21); multi-carrier scheduling set 3 includes: (carrier 31, carrier 32, carrier 33, carrier 34); multi-carrier scheduling set 4 includes: (carrier 41, carrier 42). Among them, the index of multi-carrier scheduling set 0 is 000, the index of multi-carrier scheduling set 1 is 001, the index of multi-carrier scheduling set 2 is 010, the index of multi-carrier scheduling set 3 is 011, and the index of multi-carrier scheduling set 4 is 100.
[0067] Based on the example in FIG4 , the number of bits included in the multi-carrier scheduling set indication field is calculated as follows: N=ceil(log2M)=ceil(log25)=3.
[0068] As shown in FIG4 , the multi-carrier scheduling set indication field includes 3 bits.
[0069] When the multi-carrier scheduling set indication field indicates 010, it indicates that the multi-carrier scheduling set indexed by 010 is scheduled, and the index of multi-carrier scheduling set 2 is 010, that is, it indicates that the scheduled multi-carrier scheduling set is multi-carrier scheduling set 2. This means that the carrier included in multi-carrier scheduling set 2, that is, carrier 21, is scheduled.
[0070] It can be seen that in this example, the carrier scheduling information is also used to indicate M multi-carrier scheduling sets, and the m-th multi-carrier scheduling set includes Y m carriers, and the number of bits included in the multi-carrier scheduling set indication field is determined by N=ceil(log2M), so that one or more scheduled carriers in multi-carrier scheduling can be indicated with the least number of bits, which can save signaling overhead and thus save communication resources.
[0071] Example 3.2
[0072] In this example, the carrier scheduling information is further used to indicate X carriers used for carrier aggregation, where X is an integer greater than 0.
[0073] It can be understood that one or more carriers among the X carriers can be used for multi-carrier scheduling.
[0074] Optionally, the carrier scheduling information includes a first carrier indication field. The first carrier indication field is used to indicate one or more scheduled carriers.
[0075] Optionally, the first carrier indication field includes X bits.
[0076] In this example, the number of carriers used for carrier aggregation indicated by the carrier scheduling information is X, and the first carrier indication field includes X bits, which means that each bit in the first carrier indication field corresponds to a carrier. The value of the bit indicates whether the carrier corresponding to the bit is scheduled. For example, it is pre-defined that when the bit value is 1, it indicates that the carrier is scheduled, and when the bit value is 0, it indicates that the carrier is not scheduled.
[0077] Figure 5 is a schematic diagram of carriers and a first carrier indication field for carrier aggregation provided by an embodiment. As shown in Figure 5, assuming that the number of carriers used for carrier aggregation indicated by the carrier scheduling information is 5: carrier 1, carrier 2, carrier 3, carrier 4, and carrier 5, then the first carrier indication field includes 5 bits. The correspondence between carriers and bits can be pre-agreed. As shown in Figure 5, if carrier 1 corresponds to the least significant bit (called the 1st bit), carrier 2 corresponds to the second least significant bit (called the 2nd bit), carrier 3 corresponds to the 3rd bit, carrier 4 corresponds to the 4th bit, and carrier 5 corresponds to the 5th bit. It is pre-agreed that when the bit value is 1, it indicates that the carrier is scheduled; when the bit value is 0, it indicates that the carrier is not scheduled. When the first carrier indication field is 10110, it indicates that carrier 5, carrier 3, and carrier 2 are scheduled.
[0078] The number of bits in the first carrier indication field in this example is greater than the number of bits in the multi-carrier scheduling set indication field in Example 3.1, thereby improving the reliability of indicating one or more scheduled carriers.
[0079] Example 3.3
[0080] In this example, the carrier scheduling information is further used to indicate X carriers used for carrier aggregation, where X is an integer greater than 0.
[0081] It can be understood that one or more carriers among the X carriers can be used for multi-carrier scheduling.
[0082] Optionally, the carrier scheduling information includes a first carrier indication field. The first carrier indication field is used to indicate one or more scheduled carriers.
[0083] Optionally, the first carrier indicator field includes X*Y bits, where Y=ceil(log2X).
[0084] Figure 6 is another schematic diagram of carriers used for carrier aggregation and the first carrier indication field provided by an embodiment. As shown in Figure 6, assume that the number of carriers used for carrier aggregation indicated by the carrier scheduling information is five: carrier 1, carrier 2, carrier 3, carrier 4, and carrier 5. Therefore, Y = ceil(log2X) = 3. The first carrier indication field includes 15 bits. Three bits represent the index of the scheduled carrier or other information that uniquely identifies the scheduled carrier, such as the cell index corresponding to the carrier. As shown in Figure 6, assume that carrier 1 corresponds to bits 1 to 3, carrier 2 corresponds to bits 4 to 6, carrier 3 corresponds to bits 7 to 9, carrier 4 corresponds to bits 10 to 12, and carrier 5 corresponds to bits 13 to 15. Assume that the index corresponding to carrier 5 is 100, and the index corresponding to carrier 2 is 001. When the first carrier indication field is 100000000001000, it indicates that carrier 5 and carrier 2 are scheduled.
[0085] The number of bits in the first carrier indication field in this example is greater than the number of bits in the multi-carrier scheduling set indication field in Example 3.1, thereby improving the reliability of indicating one or more scheduled carriers.
[0086] Step 302: Perform multi-carrier scheduling according to the carrier scheduling information.
[0087] In step 302, multi-carrier scheduling may be implemented according to one or more scheduled carriers indicated in the carrier scheduling information.
[0088] Optionally, based on Example 3.1, the multi-carrier scheduling set indication field is carried in at least one of the following information: PC5-RRC, MAC-Control Element (CE), DCI, and SCI.
[0089] Optionally, the multi-carrier scheduling set indication field reuses the DCI and / or SCI reserved bit field; or, the multi-carrier scheduling set indication field reuses the DCI and / or SCI existing bit field; or, the multi-carrier scheduling set indication field occupies the DCI and / or SCI filling bit field; or, the multi-carrier scheduling set indication field occupies the DCI and / or SCI independent bit field.
[0090] Optionally, based on Example 3.2 and Example 3.3, the first carrier indication field is carried in at least one of the following information: Proximity-based services Communication 5-Radio Resource Control (PC5-RRC), Medium Access Control-Control Element (MAC-CE), DCI and SCI.
[0091] Optionally, the first carrier indication field reuses the DCI and / or SCI reserved bit field; or, the first carrier indication field reuses the DCI and / or SCI existing bit field; or, the first carrier indication field occupies the DCI and / or SCI fill bit field; or, the first carrier indication field occupies the DCI and / or SCI independent bit field.
[0092] Optionally, the DCI and / or SCI reserved bit field in this embodiment includes at least one of the following: a reserved bit field in DCI format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C, for example, a "reserved" bit field.
[0093] Optionally, the existing bit fields of DCI and / or SCI in this embodiment include at least one of the following: existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, the "configuration index" bit field in DCI Format 3_0.
[0094] Optionally, the DCI and / or SCI padding bit field in this embodiment includes at least one of the following: a padding bit field added to align format sizes between different formats in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C, for example, a "padding" bit field.
[0095] Optionally, the DCI and / or SCI independent bit fields in this embodiment include at least one of the following: a bit field newly added relative to existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, a "multiple carrier set indicator" bit field and a "carrier indicator" bit field.
[0096] Optionally, the DCI and / or SCI independent bit fields in this embodiment include at least one of the following: a format newly added relative to existing formats in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, independent bit fields in DCI Format 3_2, SCI format 1-B, and SCI format 2-D, such as a "multiple carrier set indicator" bit field and a "carrier indicator" bit field.
[0097] The carrying manner of the multi-carrier scheduling set indication field and the first carrier indication field can be compatible with the communication system version in the related art.
[0098] The carrier indication method provided in this embodiment, on the one hand, the method for determining the number of bits of the carrier scheduling set indication field and the first carrier indication field can save signaling overhead; on the other hand, the carrying method of the multi-carrier scheduling set indication field and the first carrier indication field can be compatible with the communication system version in the related technology.
[0099] Figure 7 is a flowchart illustrating another carrier indication method provided by one embodiment. Based on the embodiment shown in Figure 2 and various optional implementations, this embodiment provides a detailed description of how carrier scheduling information is used to indicate cross-carrier scheduling. As shown in Figure 7, the carrier indication method provided by this embodiment includes the following steps.
[0100] Step 701: Acquire carrier scheduling information.
[0101] In one embodiment, the carrier scheduling information in this embodiment is used to indicate whether cross-carrier scheduling is performed.
[0102] In one embodiment, the carrier scheduling information is also used to indicate the scheduled carrier in cross-carrier scheduling.
[0103] In one implementation, the carrier scheduling information may directly indicate the scheduled carrier in the cross-carrier scheduling.
[0104] In another implementation, the carrier scheduling information indicates cross-carrier scheduling and indicates the scheduled carrier in the cross-carrier scheduling. Of course, in this implementation, if the carrier scheduling information indicates not to perform cross-carrier scheduling, then the carrier scheduling information does not indicate the scheduled carrier.
[0105] In this embodiment, the carrier scheduling information is also used to indicate the Z carriers used for carrier aggregation. Z is an integer greater than 0. It should be noted that Z in this embodiment can be the same as or different from the number of carriers X in the embodiment shown in Figure 3 and various optional implementations. This embodiment does not impose any restrictions on this.
[0106] It can be understood that carriers among the Z carriers can be used for cross-carrier scheduling.
[0107] Optionally, the carrier scheduling information includes a second carrier indicator field. The second carrier indicator field is used to indicate the index of the scheduled carrier. Of course, the index of the scheduled carrier in this embodiment can also be other information that can uniquely represent the scheduled carrier, such as the cell index corresponding to the carrier.
[0108] Optionally, the second carrier indication field includes R bits; wherein R=ceil(log2Z).
[0109] Figure 8 is a schematic diagram of carriers used for carrier aggregation and a second carrier indicator field, provided by an embodiment. As shown in Figure 8 , assume that the number of carriers used for carrier aggregation indicated by the carrier scheduling information is five: carrier 0, carrier 1, carrier 2, carrier 3, and carrier 4. Assume that the index of carrier 0 is 000, the index of carrier 1 is 001, the index of carrier 2 is 010, the index of carrier 3 is 011, and the index of carrier 4 is 100.
[0110] Based on the example in FIG8 , the number of bits included in the second carrier indication field is calculated as follows: R=ceil(log2Z)=ceil(log25)=3.
[0111] As shown in FIG8 , the second carrier indication field includes 3 bits.
[0112] When the second carrier indication field indicates 010, it means that the carrier with index 010 is scheduled, and the index of carrier 2 is 010, that is, it means that carrier 2 is scheduled.
[0113] Step 702: Perform cross-carrier scheduling according to carrier scheduling information.
[0114] In step 702, cross-carrier scheduling may be implemented according to the scheduled carrier indicated in the carrier scheduling information.
[0115] Optionally, the second carrier indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI, and SCI.
[0116] Optionally, the second carrier indication field reuses the DCI and / or SCI reserved bit field; or, the second carrier indication field reuses the DCI and / or SCI existing bit field; or, the second carrier indication field occupies the DCI and / or SCI fill bit field; or, the second carrier indication field occupies the DCI and / or SCI independent bit field.
[0117] Optionally, the DCI and / or SCI reserved bit field in this embodiment includes at least one of the following: reserved bit fields in DCI format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C, for example, a "reserved" bit field.
[0118] Optionally, the existing bit fields of DCI and / or SCI in this embodiment include at least one of the following: existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, the "configuration index" bit field in DCI Format 3_0.
[0119] Optionally, the DCI and / or SCI padding bit field in this embodiment includes at least one of the following: a padding bit field added to align format sizes between different formats in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C, for example, a "padding" bit field.
[0120] Optionally, the DCI and / or SCI independent bit fields in this embodiment include at least one of the following: a bit field newly added relative to existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, a "multiple carrier set indicator" bit field and a "carrier indicator" bit field.
[0121] Optionally, the DCI and / or SCI independent bit fields in this embodiment include at least one of the following: a format newly added relative to existing formats in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C. For example, independent bit fields in DCI Format 3_2, SCI format 1-B, and SCI format 2-D, such as a "multiple carrier set indicator" bit field and a "carrier indicator" bit field.
[0122] The carrier indication method provided in this embodiment, on the one hand, determines the number of bits of the second carrier indication field, which can save signaling overhead; on the other hand, the carrying method of the second carrier indication field can be compatible with the communication system version in the related technology.
[0123] It should be noted that the carrier index in the embodiments shown in FIG. 3 and FIG. 7 and various optional implementations may also be a bandwidth part (Bandwidth Part, BWP) index, thereby implementing scheduling of the BWP.
[0124] FIG9 is a schematic diagram of the structure of a carrier indication system provided by an embodiment. As shown in FIG9 , the carrier indication system provided by this embodiment includes: a first communication entity 91 and a second communication entity 92 .
[0125] The first communication entity 91 implements the carrier indication method of any of the above embodiments.
[0126] The second communication entity 92 implements the carrier indication method of any of the above embodiments.
[0127] The carrier indication system provided in this embodiment can implement the carrier indication method of the above embodiment. The implementation principle and technical effects are similar to those of the above embodiment and will not be described again here.
[0128] FIG10 is a schematic diagram of a carrier indication device provided by an embodiment. The carrier indication device may be provided in a communication entity. As shown in FIG10 , the carrier indication device provided by this embodiment includes the following modules: an acquisition module 101 and a scheduling module 102.
[0129] The acquisition module 101 is configured to acquire carrier scheduling information.
[0130] The scheduling module 102 is configured to perform cross-carrier scheduling or multi-carrier scheduling according to the carrier scheduling information.
[0131] In one embodiment, the carrier scheduling information is used to indicate whether cross-carrier scheduling is performed.
[0132] In one embodiment, the carrier scheduling information is used to indicate whether multi-carrier scheduling is performed.
[0133] In one embodiment, the carrier scheduling information is further used to indicate one or more scheduled carriers in multi-carrier scheduling.
[0134] In one embodiment, the carrier scheduling information is further used to indicate M multi-carrier scheduling sets, and the m-th multi-carrier scheduling set includes Y m carriers. Where M is an integer greater than 0, m is an integer greater than 0 and less than or equal to M, and Y m An integer greater than 0.
[0135] In one embodiment, the one or more scheduled carriers are located in a scheduled multi-carrier scheduling set among the M multi-carrier scheduling sets. The carrier scheduling information includes a multi-carrier scheduling set indication field, and the multi-carrier scheduling set indication field is used to indicate an index of the scheduled multi-carrier scheduling set.
[0136] In one embodiment, the multi-carrier scheduling set indication field includes N bits, where N=ceil(log2M), and ceil(log2M) represents the smallest integer rounded up to log2M.
[0137] In one embodiment, the carrier scheduling information is further used to indicate X carriers used for carrier aggregation, where X is an integer greater than 0.
[0138] In one embodiment, the carrier scheduling information includes a first carrier indication field, and the first carrier indication field is used to indicate the one or more scheduled carriers.
[0139] In one embodiment, the first carrier indicator field includes X bits.
[0140] In one embodiment, the first carrier indicator field includes X*Y bits; wherein Y=ceil(log2X).
[0141] In one embodiment, the carrier scheduling information is further used to indicate the scheduled carrier in cross-carrier scheduling.
[0142] In one embodiment, the carrier scheduling information is further used to indicate Z carriers used for carrier aggregation, where Z is an integer greater than 0.
[0143] In one embodiment, the carrier scheduling information includes a second carrier indication field, and the second carrier indication field is used to indicate the index of the scheduled carrier.
[0144] In one embodiment, the second carrier indicator field includes R bits, where R=ceil(log2Z).
[0145] In one embodiment, the multi-carrier scheduling set indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI, and SCI.
[0146] In one embodiment, the multi-carrier scheduling set indication field reuses the DCI and / or SCI reserved bit field; or, the multi-carrier scheduling set indication field reuses the DCI and / or SCI existing bit field; or, the multi-carrier scheduling set indication field occupies the DCI and / or SCI filling bit field; or, the multi-carrier scheduling set indication field occupies the DCI and / or SCI independent bit field.
[0147] In one embodiment, the first carrier indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI, and SCI.
[0148] In one embodiment, the first carrier indication field reuses the reserved bit field of DCI and / or SCI; or, the first carrier indication field reuses the existing bit field of DCI and / or SCI; or, the first carrier indication field occupies the padding bit field of DCI and / or SCI; or, the first carrier indication field occupies the independent bit field of DCI and / or SCI.
[0149] In one embodiment, the second carrier indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI, and SCI.
[0150] In one embodiment, the second carrier indication field reuses the DCI and / or SCI reserved bit field; or, the second carrier indication field reuses the DCI and / or SCI existing bit field; or, the second carrier indication field occupies the DCI and / or SCI fill bit field; or, the second carrier indication field occupies the DCI and / or SCI independent bit field.
[0151] In one embodiment, the DCI and / or SCI reserved bit fields include at least one of the following: reserved bit fields in DCI format 3_0 DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C.
[0152] In one embodiment, the existing bit fields of DCI and / or SCI include at least one of the following: existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C.
[0153] In one embodiment, the DCI and / or SCI padding bit field includes at least one of the following: a padding bit field added to DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C to align format sizes between different formats.
[0154] In one embodiment, the DCI and / or SCI independent bit fields include at least one of the following: a bit field newly added relative to the existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B and SCI format 2-C.
[0155] In one embodiment, the DCI and / or SCI independent bit fields include at least one of the following: a newly added format relative to the existing formats among DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C.
[0156] In one embodiment, the communication entity includes at least one of the following: a network node, a terminal node, a radio resource control layer, a radio link control layer, a medium access control layer, and a physical layer.
[0157] In one embodiment, the acquisition module 101 is configured to perform at least one of the following: receiving the carrier scheduling information from an access network device; generating the carrier scheduling information; and pre-configuring the carrier scheduling information.
[0158] Optionally, the device further includes: a sending module, configured to send the carrier scheduling information to another communication entity connected to the communication entity.
[0159] In one embodiment, the acquisition module 101 is configured to perform at least one of the following: receiving the carrier scheduling information from another communication entity connected to the communication entity; and pre-configuring the carrier scheduling information.
[0160] The carrier indication device provided in this embodiment can implement the carrier indication method of the above embodiment. The implementation principle and technical effects are similar to those of the above embodiment and will not be repeated here.
[0161] An embodiment of the present application further provides a communication entity, including: a processor configured to implement the method provided in any embodiment of the present application when executing a computer program. The communication entity includes: a processor configured to implement the carrier indication method provided in any embodiment of the present application when executing the computer program. Exemplarily, the communication entity may be a terminal, such as a UE.
[0162] Illustratively, the following embodiment provides a structural diagram in which a communication entity is a terminal.
[0163] FIG11 is a schematic diagram of the structure of a terminal provided by an embodiment. The terminal can be implemented in various forms. The terminal in this application may include, but is not limited to, mobile terminal devices such as mobile phones, smart phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), navigation devices, vehicle-mounted terminal devices, vehicle-mounted display terminals, vehicle-mounted electronic rearview mirrors, etc., as well as fixed terminal devices such as digital televisions (TVs) and desktop computers.
[0164] As shown in FIG11 , the terminal 50 may include a wireless communication unit 51, an audio / video (A / V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, a processor 58, and a power supply unit 59, among others. FIG11 shows a terminal including various components, but it should be understood that implementation of all illustrated components is not required. More or fewer components may be implemented instead.
[0165] In this embodiment, the wireless communication unit 51 allows radio communication between the terminal 50 and a base station or network. The A / V input unit 52 is configured to receive audio or video signals. The user input unit 53 generates key input data based on user input commands to control various operations of the terminal 50. The sensing unit 54 monitors the current state of the terminal 50, its location, the presence or absence of user touch input to the terminal 50, its orientation, the acceleration or deceleration movement and direction of the terminal 50, and generates commands or signals for controlling the operations of the terminal 50. The interface unit 57 serves as an interface through which at least one external device can connect to the terminal 50. The output unit 55 is configured to provide output signals in a visual, audio, and / or tactile manner. The memory 56 can store software programs, etc., for processing and control operations executed by the processor 58, or can temporarily store data that has been output or is to be output. The memory 56 may include at least one type of storage medium. Furthermore, the terminal 50 may cooperate with a network storage device that performs the storage function of the memory 56 via a network connection. The processor 58 generally controls the overall operation of the terminal 50. The power supply unit 59 receives external power or internal power and provides appropriate power required to operate various elements and components under the control of the processor 58 .
[0166] The processor 58 executes at least one functional application and data processing by running the program stored in the memory 56, such as implementing the method provided in the embodiment of the present application.
[0167] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method provided in any embodiment of the present application is implemented.
[0168] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. The computer-readable storage medium includes (a non-exhaustive list): an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0169] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, the data signal carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0170] The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
[0171] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination of multiple programming languages, including object-oriented programming languages (such as Java, Smalltalk, C++, Ruby, Go), and conventional procedural programming languages (such as "C" or similar programming languages). The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0172] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
[0173] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
[0174] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.
[0175] Any block diagram of a logical flow in the drawings of this application may represent program steps, or may represent interconnected logical circuits, modules and functions, or may represent a combination of program steps and logical circuits, modules and functions. A computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile discs DVD or CD), etc. Computer-readable media may include non-transitory storage media. A data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FPGA), and a processor based on a multi-core processor architecture.
Claims
1. A carrier indication method, applied to a communication entity, the method comprising: Obtain carrier scheduling information; Cross-carrier scheduling or multi-carrier scheduling is performed according to the carrier scheduling information.
2. The method according to claim 1, wherein: The carrier scheduling information is used to indicate whether to perform cross-carrier scheduling.
3. The method according to claim 1, wherein: The carrier scheduling information is used to indicate whether to perform multi-carrier scheduling.
4. The method according to claim 1 or 3, wherein: The carrier scheduling information is also used to indicate one or more scheduled carriers in the multi-carrier scheduling.
5. The method according to claim 4, wherein: The carrier scheduling information is also used to indicate M multi-carrier scheduling sets, the m-th multi-carrier scheduling set including Y m carriers; wherein M is an integer greater than 0, m is an integer greater than 0 and less than or equal to M, and Y m An integer greater than 0.
6. The method according to claim 5, wherein: The one or more scheduled carriers are located in a scheduled multi-carrier scheduling set in the M multi-carrier scheduling sets; The carrier scheduling information includes a multi-carrier scheduling set indication field, and the multi-carrier scheduling set indication field is used to indicate the index of the scheduled multi-carrier scheduling set.
7. The method according to claim 6, wherein: The multi-carrier scheduling set indication field includes N bits, wherein N=ceil(log2M), and ceil(log2M) represents the smallest integer rounded upwards for log2M.
8. The method according to claim 4, wherein: The carrier scheduling information is also used to indicate X carriers used for carrier aggregation, where X is an integer greater than 0.
9. The method according to claim 8, wherein: The carrier scheduling information includes a first carrier indication field, and the first carrier indication field is used to indicate the one or more scheduled carriers.
10. The method according to claim 9, wherein: The first carrier indication field includes X bits.
11. The method according to claim 9, wherein: The first carrier indication field includes X*Y bits, wherein Y=ceil(log2X).
12. The method according to claim 1 or 2, wherein: The carrier scheduling information is also used to indicate the scheduled carrier in the cross-carrier scheduling.
13. The method according to claim 12, wherein: The carrier scheduling information is also used to indicate Z carriers used for carrier aggregation, where Z is an integer greater than 0.
14. The method according to claim 13, wherein: The carrier scheduling information includes a second carrier indication field, where the second carrier indication field is used to indicate an index of the scheduled carrier.
15. The method according to claim 14, wherein: The second carrier indication field includes R bits, wherein R=ceil(log2Z).
16. The method according to claim 6, wherein: The multi-carrier scheduling set indication field is carried in at least one of the following information: proximity service communication 5-radio resource control PC5-RRC, media access control-control unit MAC-CE, downlink control information DCI and side link control information SCI.
17. The method according to claim 16, wherein: The multi-carrier scheduling set indication field reuses the DCI and / or SCI reserved bit field; or, The multi-carrier scheduling set indication field reuses the existing bit field of DCI and / or SCI; or, The multi-carrier scheduling set indication field occupies the DCI and / or SCI filling bit field; or, The multi-carrier scheduling set indication field occupies a DCI and / or SCI independent bit field.
18. The method according to claim 9, wherein: The first carrier indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI and SCI.
19. The method according to claim 18, wherein: The first carrier indication field reuses the DCI and / or SCI reserved bit field; or, The first carrier indication field reuses the existing bit field of DCI and / or SCI; or, The first carrier indication field occupies the DCI and / or SCI padding bit field; or, The first carrier indication field occupies a DCI and / or SCI independent bit field.
20. The method according to claim 14, wherein: The second carrier indication field is carried in at least one of the following information: PC5-RRC, MAC-CE, DCI and SCI.
21. The method according to claim 20, wherein: The second carrier indication field reuses the DCI and / or SCI reserved bit field; or, The second carrier indication field reuses the existing bit field of DCI and / or SCI; or, The second carrier indication field occupies the DCI and / or SCI padding bit field; or, The second carrier indication field occupies a DCI and / or SCI independent bit field.
22. The method according to any one of claims 17, 19 and 21, wherein: The DCI and / or SCI reserved bit field includes at least one of the following: a reserved bit field in DCI format 3_0DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C; The existing bit fields of DCI and / or SCI include at least one of the following: existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C; The DCI and / or SCI padding bit field includes at least one of the following: a padding bit field added in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B, and SCI format 2-C for aligning format sizes between different formats; The DCI and / or SCI independent bit fields include at least one of the following: a newly added bit field relative to the existing bit fields in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B and SCI format 2-C; or, the DCI and / or SCI independent bit fields include at least one of the following: a newly added format relative to the existing formats in DCI Format 3_0, DCI Format 3_1, SCI format 1-A, SCI format 2-A, SCI format 2-B and SCI format 2-C.
23. The method according to any one of claims 1 to 3, wherein: The communication entity includes at least one of the following: a network node, a terminal node, a radio resource control layer, a radio link control layer, a medium access control layer, and a physical layer.
24. The method according to any one of claims 1 to 3, wherein: The acquiring of carrier scheduling information includes at least one of the following: Receiving the carrier scheduling information from an access network device; generating the carrier scheduling information; The carrier scheduling information is preconfigured.
25. The method according to claim 24, further comprising: The carrier scheduling information is sent to another communication entity connected to the communication entity.
26. The method according to any one of claims 1 to 3, wherein: The acquiring of carrier scheduling information includes at least one of the following: receiving the carrier scheduling information from another communication entity connected to the communication entity; The carrier scheduling information is preconfigured.
27. A carrier indication system, comprising a first communication entity and a second communication entity; The first communication entity is configured to execute the carrier indication method according to any one of claims 1 to 25; The second communication entity is configured to execute the carrier indication method according to any one of claims 1 to 23 and 26.
28. A communication entity, comprising: processor; The processor is configured to implement the carrier indication method according to any one of claims 1 to 26 when executing a computer program.
29. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the carrier indication method according to any one of claims 1 to 26.
Citation Information
Patent Citations
Joint use of multi-carrier and single-carrier multiplexing schemes for wireless communication
CN101601246A
Communication method and device
CN114826537A
Carrier indication method and system, communication entity and storage medium
CN117939655A
Wireless communication method, terminal device, and network device
WO2022021136A1