Communication method, device and system

Abstract

Provided are a communication method, device and system, the communication method being applicable to a 5G network and a future 6G network. The method comprises: a second device receiving first indication information, the first indication information indicating a first virtual carrier, the first virtual carrier comprising at least two sub-blocks, the at least two sub-blocks being in one-to-one correspondence with the at least two carriers, the first virtual carrier comprising a first BWP, the first BWP comprising frequency domain resources corresponding to the at least two sub-blocks in the first virtual carrier, the size of the RBG in the first BWP is related to at least two sub-blocks; and the second device communicates with the first device based on the first virtual carrier indicated by the first indication information. Compared with multi-carrier aggregation, the virtual carrier in the method can simplify the processing flow and save the signaling overhead. And by defining the size of the RBG of the virtual carrier and aligning the understanding of the network side and the terminal side, resource scheduling based on the RBG is enabled, the resource utilization rate is improved, and meanwhile, the resource indication overhead is minimized.

Description

Technical Field

[0001] This application relates to the field of communications. In particular, it relates to a communication method, apparatus, and system. Background Technology

[0002] To reduce network deployment costs, different operators consider collaborative network construction through sharing, such as infrastructure sharing, main equipment sharing, and network roaming. While main equipment sharing helps reduce network construction costs, it still has limitations, lacks flexibility, and can lead to high signaling overhead and underutilization of resources. Summary of the Invention

[0003] This application provides a communication method, apparatus, and system that can reduce signaling overhead and improve resource utilization.

[0004] In a first aspect, a communication method is provided, which can be executed by a second device, or by a module, such as a chip or circuit, used in the second device; this application does not limit this. For ease of description, the following explanation uses execution by a second device as an example.

[0005] The method may include: receiving first indication information, the first indication information indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth (BWP), the first BWP including frequency domain resources corresponding to at least two sub-blocks within the first virtual carrier, the size of resource block groups (RBGs) in the first BWP being related to the at least two sub-blocks; and communicating with a network-side device based on the first virtual carrier indicated by the first indication information.

[0006] This method defines virtual carriers, which simplifies the processing flow compared to multi-carrier aggregation. For example, it eliminates the need for frequent activation / deactivation, saving signaling overhead. Furthermore, by defining the RBG size under the virtual carrier, it aligns the understanding between the network side and the terminal side, enabling RBG-based resource scheduling, improving resource utilization, and minimizing resource indication overhead.

[0007] In some implementations, the relationship between the size of the resource block group (RBG) in the first BWP and the at least two sub-blocks includes: the size of the RBG in the first BWP is determined based on the size of the first BWP and a first value, wherein the size of the first BWP is the number of resource blocks (RBs) contained in the at least two sub-blocks included in the first BWP, and the first value is determined based on the size of a reference sub-block, wherein the reference sub-block belongs to the at least two sub-blocks and is configured or predefined; or, the first value is determined based on the size of the first BWP and a first correspondence, wherein the first correspondence is the correspondence between the BWP size and the nominal RBG size.

[0008] This approach defines a reference sub-block. In scenarios where BWP is mapped to multiple sub-blocks, the reference sub-block method aligns the understanding of RBG size between the network side and the terminal side, enabling RBG-based resource scheduling.

[0009] In some implementations, the size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value, and the sizes of the RBGs within the first BWP other than the last RBG are the first value.

[0010] In this method, only the size of the last RBG may differ from the other RBGs. The size of the RBG is only related to the size of the BWP, and there is no need to consider the starting position of the BWP. This simplifies the implementation and reduces the complexity of device processing.

[0011] In some implementations, the size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

[0012] In some implementations, the size E of the first RBG within the first BWP satisfies the following relationship:

[0013]

[0014] in, Let K be the starting position of the first BWP, and K be the first value.

[0015] The size F of the last RBG within the first BWP satisfies the following relationship:

[0016]

[0017] in, Let K be the size of the first BWP, and K be the first value.

[0018] In this method, the size of the first RBG within the BWP is related to the starting position of the BWP. From the network side perspective, it is easier to achieve RBG alignment for multiple users, and network processing is simple.

[0019] In some implementations, the at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks as follows: the size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer, and the reference sub-block is configured or predefined.

[0020] In this approach, adjacent carriers or carriers belonging to the same radio frequency unit are mapped to the same resource block group, and operations are performed at the granularity of the resource block group, which facilitates processing on both the network side and the terminal side.

[0021] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0022] The size of the first RBG in the first sub-block is P.

[0023] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

[0024] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

[0025] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0026] The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0027] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

[0028] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation of the size of the first sub-block and P; or, the size S of the last RBG in the first sub-block and the size of the first RBG in the first sub-block indicated by the first indication information are used. The size N of the first sub-block sub-block,i The following relationship is satisfied between P and P:

[0029]

[0030] in This is for floor function.

[0031] In some implementations, the first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0032] The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

[0033] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0034] The size of the non-edge RBG in the second sub-block is Q.

[0035] The size of the first RBG within the second sub-block is Q.

[0036] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0037] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0038] The size of the non-edge RBG in the second sub-block is Q.

[0039] The size of the first RBG within the second sub-block is determined based on the number of the starting RB of the second sub-block in the common resources of the carrier associated with the second sub-block, or the number of the starting RB of the second sub-block in the first virtual carrier.

[0040] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0041] In some implementations, the first BWP includes at least one sub-block group, each of the at least one sub-block group including at least one sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0042] The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

[0043] In some implementations, the at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

[0044] In some implementations, all RBGs in the third sub-block except the last RBG are of the same size, or all RBGs in the third sub-block except the first RBG and the last RBG are of the same size.

[0045] In some implementations, the at least one sub-block group includes a first sub-block group, and the RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG, including:

[0046] The size of the RBG in the first sub-block group is related to the nominal RBG size L in the reference sub-block group, where L is a positive integer, and the reference sub-block group is pre-configured or pre-defined.

[0047] In some implementations, the third sub-block belongs to the first sub-block group.

[0048] The size of the non-edge RBG in the third sub-block is L.

[0049] The size of the first RBG in the third sub-block is L.

[0050] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and the L.

[0051] In some implementations, the third sub-block belongs to the first sub-block group.

[0052] The size of the non-edge RBG in the third sub-block is L.

[0053] The size of the first RBG in the third sub-block is determined based on the number of the starting RB of the third sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0054] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the third sub-block indicated by the first indication information, the size of the third sub-block, and L.

[0055] In some implementations, the third sub-block belongs to the first sub-block group.

[0056] The size of the non-edge RBG in the third sub-block is L.

[0057] The size of the first RBG within the third sub-block is L.

[0058] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0059] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0060] The size of the non-edge RBG in the third sub-block is L.

[0061] The size of the first RBG within the third sub-block is determined based on the number of the starting RB of the third sub-block in the common resources of the carrier associated with the third sub-block, or the number of the starting RB of the third sub-block in the first virtual carrier.

[0062] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0063] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0064] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the value of L.

[0065] The size of the RBGs in the third sub-block, excluding the last RBG, is L.

[0066] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0067] The size of the first RBG within the third sub-block is determined based on the starting position of the third sub-block and L. The starting position of the third sub-block is either the common resource number of the starting RB of the third sub-block within the sub-block, or the common resource number of the starting RB of the third sub-block within the first virtual carrier.

[0068] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0069] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0070] The size of the first RBG and the size of the last RBG within the third sub-block are determined based on the size of the third sub-block and the position of the third sub-block.

[0071] Secondly, a communication method is provided, which can be executed by a first device, or by a module used in the first device, such as a chip or circuit; this application does not limit this. For ease of description, the following explanation uses execution by the first device as an example.

[0072] The method includes: sending first indication information, the first indication information indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth (BWP), the first BWP being mapped onto at least two carriers, the size of a resource block group (RBG) in any of the at least two sub-blocks being associated with the at least two carriers; and communicating with a terminal device based on the first virtual carrier indicated by the first indication information.

[0073] In some implementations, the relationship between the size of the resource block group (RBG) in the first BWP and the at least two sub-blocks includes: the size of the RBG in the first BWP is determined based on the size of the first BWP and a first value, wherein the size of the first BWP is the number of resource blocks (RBs) contained in the at least two sub-blocks included in the first BWP, and the first value is determined based on the size of a reference sub-block, wherein the reference sub-block belongs to the at least two sub-blocks and is configured or predefined; or, the first value is determined based on the size of the first BWP and a first correspondence, wherein the first correspondence is the correspondence between the BWP size and the nominal RBG size.

[0074] In some implementations, the size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value, and the sizes of the RBGs within the first BWP other than the last RBG are the first value.

[0075] In some implementations, the size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

[0076] In some implementations, the size E of the first RBG within the first BWP satisfies the following relationship:

[0077]

[0078] in, Let K be the starting position of the first BWP, and K be the first value.

[0079] The size F of the last RBG within the first BWP satisfies the following relationship:

[0080]

[0081] in, Let K be the size of the first BWP, and K be the first value.

[0082] In some implementations, the at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks as follows: the size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer, and the reference sub-block is configured or predefined.

[0083] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0084] The size of the first RBG in the first sub-block is P.

[0085] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

[0086] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

[0087] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0088] The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0089] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

[0090] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation of the size of the first sub-block and P; or, the size S of the last RBG in the first sub-block and the size of the first RBG in the first sub-block indicated by the first indication information are used. The size N of the first sub-block sub-block,i The following relationship is satisfied between P and P:

[0091]

[0092] in This is for floor function.

[0093] In some implementations, the first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0094] The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

[0095] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0096] The size of the non-edge RBG in the second sub-block is Q.

[0097] The size of the first RBG within the second sub-block is Q.

[0098] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0099] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0100] The size of the non-edge RBG in the second sub-block is Q.

[0101] The size of the first RBG within the second sub-block is determined based on the number of the starting RB of the second sub-block in the common resources of the carrier associated with the second sub-block, or the number of the starting RB of the second sub-block in the first virtual carrier.

[0102] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0103] In some implementations, the first BWP includes at least one sub-block group, each of the at least one sub-block group including at least one sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0104] The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

[0105] In some implementations, the at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

[0106] In some implementations, all RBGs in the third sub-block except the last RBG are of the same size, or all RBGs in the third sub-block except the first RBG and the last RBG are of the same size.

[0107] In some implementations, the at least one sub-block group includes a first sub-block group, and the RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG, including:

[0108] The size of the RBG in the first sub-block group is related to the nominal RBG size L in the reference sub-block group, where L is a positive integer, and the reference sub-block group is pre-configured or pre-defined.

[0109] In some implementations, the third sub-block belongs to the first sub-block group.

[0110] The size of the non-edge RBG in the third sub-block is L.

[0111] The size of the first RBG in the third sub-block is L.

[0112] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and the L.

[0113] In some implementations, the third sub-block belongs to the first sub-block group.

[0114] The size of the non-edge RBG in the third sub-block is L.

[0115] The size of the first RBG in the third sub-block is determined based on the number of the starting RB of the third sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0116] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the third sub-block indicated by the first indication information, the size of the third sub-block, and L.

[0117] In some implementations, the third sub-block belongs to the first sub-block group.

[0118] The size of the non-edge RBG in the third sub-block is L.

[0119] The size of the first RBG within the third sub-block is L.

[0120] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0121] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0122] The size of the non-edge RBG in the third sub-block is L.

[0123] The size of the first RBG within the third sub-block is determined based on the number of the starting RB of the third sub-block in the common resources of the carrier associated with the third sub-block, or the number of the starting RB of the third sub-block in the first virtual carrier.

[0124] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0125] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0126] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the value of L.

[0127] The size of the RBGs in the third sub-block, excluding the last RBG, is L.

[0128] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0129] The size of the first RBG within the third sub-block is determined based on the starting position of the third sub-block and L. The starting position of the third sub-block is either the common resource number of the starting RB of the third sub-block within the sub-block, or the common resource number of the starting RB of the third sub-block within the first virtual carrier.

[0130] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0131] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0132] The size of the first RBG and the size of the last RBG within the third sub-block are determined based on the size of the third sub-block and the position of the third sub-block.

[0133] It should be understood that the second aspect is the implementation method of the network-side device corresponding to the first aspect. The explanation, supplement and description of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0134] Thirdly, a communication device is provided, including a transceiver unit and a processing unit. The transceiver unit is used to receive first indication information, the first indication information indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth (BWP), the first BWP including frequency domain resources corresponding to at least two sub-blocks within the first virtual carrier, the size of a resource block group (RBG) in the first BWP being related to the at least two sub-blocks; the processing unit is used to communicate with a network-side device based on the first virtual carrier indicated by the first indication information.

[0135] In some implementations, the relationship between the size of the resource block group (RBG) in the first BWP and the at least two sub-blocks includes: the size of the RBG in the first BWP is determined based on the size of the first BWP and a first value, wherein the size of the first BWP is the number of resource blocks (RBs) contained in the at least two sub-blocks included in the first BWP, and the first value is determined based on the size of a reference sub-block, wherein the reference sub-block belongs to the at least two sub-blocks and is configured or predefined; or, the first value is determined based on the size of the first BWP and a first correspondence, wherein the first correspondence is the correspondence between the BWP size and the nominal RBG size.

[0136] In some implementations, the size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value, and the sizes of the RBGs within the first BWP other than the last RBG are the first value.

[0137] In some implementations, the size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

[0138] In some implementations, the size E of the first RBG within the first BWP satisfies the following relationship:

[0139]

[0140] in, Let K be the starting position of the first BWP, and K be the first value.

[0141] The size F of the last RBG within the first BWP satisfies the following relationship:

[0142]

[0143] in, Let K be the size of the first BWP, and K be the first value.

[0144] In some implementations, the at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks as follows: the size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer, and the reference sub-block is configured or predefined.

[0145] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0146] The size of the first RBG in the first sub-block is P.

[0147] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

[0148] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

[0149] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0150] The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0151] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

[0152] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation of the size of the first sub-block and P; or, the size S of the last RBG in the first sub-block and the size of the first RBG in the first sub-block indicated by the first indication information are used. The size N of the first sub-block sub-block,i The following relationship is satisfied between P and P:

[0153]

[0154] in This is for floor function.

[0155] In some implementations, the first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0156] The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

[0157] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0158] The size of the non-edge RBG in the second sub-block is Q.

[0159] The size of the first RBG within the second sub-block is Q.

[0160] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0161] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0162] The size of the non-edge RBG in the second sub-block is Q.

[0163] The size of the first RBG within the second sub-block is determined based on the number of the starting RB of the second sub-block in the common resources of the carrier associated with the second sub-block, or the number of the starting RB of the second sub-block in the first virtual carrier.

[0164] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0165] In some implementations, the first BWP includes at least one sub-block group, each of the at least one sub-block group including at least one sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0166] The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

[0167] In some implementations, the at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

[0168] In some implementations, all RBGs in the third sub-block except the last RBG are of the same size, or all RBGs in the third sub-block except the first RBG and the last RBG are of the same size.

[0169] In some implementations, the at least one sub-block group includes a first sub-block group, and the RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG, including:

[0170] The size of the RBG in the first sub-block group is related to the nominal RBG size L in the reference sub-block group, where L is a positive integer, and the reference sub-block group is pre-configured or pre-defined.

[0171] In some implementations, the third sub-block belongs to the first sub-block group.

[0172] The size of the non-edge RBG in the third sub-block is L.

[0173] The size of the first RBG in the third sub-block is L.

[0174] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and the L.

[0175] In some implementations, the third sub-block belongs to the first sub-block group.

[0176] The size of the non-edge RBG in the third sub-block is L.

[0177] The size of the first RBG in the third sub-block is determined based on the number of the starting RB of the third sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0178] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the third sub-block indicated by the first indication information, the size of the third sub-block, and L.

[0179] In some implementations, the third sub-block belongs to the first sub-block group.

[0180] The size of the non-edge RBG in the third sub-block is L.

[0181] The size of the first RBG within the third sub-block is L.

[0182] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0183] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0184] The size of the non-edge RBG in the third sub-block is L.

[0185] The size of the first RBG within the third sub-block is determined based on the number of the starting RB of the third sub-block in the common resources of the carrier associated with the third sub-block, or the number of the starting RB of the third sub-block in the first virtual carrier.

[0186] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0187] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0188] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the value of L.

[0189] The size of the RBGs in the third sub-block, excluding the last RBG, is L.

[0190] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0191] The size of the first RBG within the third sub-block is determined based on the starting position of the third sub-block and L. The starting position of the third sub-block is either the common resource number of the starting RB of the third sub-block within the sub-block, or the common resource number of the starting RB of the third sub-block within the first virtual carrier.

[0192] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0193] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0194] The size of the first RBG and the size of the last RBG within the third sub-block are determined based on the size of the third sub-block and the position of the third sub-block.

[0195] Fourthly, a communication device is provided, including a transceiver unit and a processing unit. The transceiver unit is configured to transmit first indication information, the first indication information indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth (BWP), the first BWP being mapped onto the at least two carriers, and the size of a resource block group (RBG) in any of the at least two sub-blocks being associated with the at least two carriers; the processing unit is configured to communicate with a terminal device based on the first virtual carrier indicated by the first indication information.

[0196] In some implementations, the relationship between the size of the resource block group (RBG) in the first BWP and the at least two sub-blocks includes: the size of the RBG in the first BWP is determined based on the size of the first BWP and a first value, wherein the size of the first BWP is the number of resource blocks (RBs) contained in the at least two sub-blocks included in the first BWP, and the first value is determined based on the size of a reference sub-block, wherein the reference sub-block belongs to the at least two sub-blocks and is configured or predefined; or, the first value is determined based on the size of the first BWP and a first correspondence, wherein the first correspondence is the correspondence between the BWP size and the nominal RBG size.

[0197] In some implementations, the size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value, and the sizes of the RBGs within the first BWP other than the last RBG are the first value.

[0198] In some implementations, the size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

[0199] In some implementations, the size E of the first RBG within the first BWP satisfies the following relationship:

[0200]

[0201] in, Let K be the starting position of the first BWP, and K be the first value.

[0202] The size F of the last RBG within the first BWP satisfies the following relationship:

[0203]

[0204] in, Let K be the size of the first BWP, and K be the first value.

[0205] In some implementations, the at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks as follows: the size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer, and the reference sub-block is configured or predefined.

[0206] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0207] The size of the first RBG in the first sub-block is P.

[0208] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

[0209] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

[0210] In some implementations, the size of the non-edge RBG in the first sub-block is P.

[0211] The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0212] The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

[0213] In some implementations, the size of the last RBG in the first sub-block is obtained by modulo operation of the size of the first sub-block and P; or, the size S of the last RBG in the first sub-block and the size of the first RBG in the first sub-block indicated by the first indication information are used. The size N of the first sub-block sub-block,i The following relationship is satisfied between P and P:

[0214]

[0215] in This is for floor function.

[0216] In some implementations, the first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0217] The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

[0218] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0219] The size of the non-edge RBG in the second sub-block is Q.

[0220] The size of the first RBG within the second sub-block is Q.

[0221] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0222] In some implementations, the nominal RBG size of the second sub-block is Q, and the second sub-block belongs to the M sub-blocks.

[0223] The size of the non-edge RBG in the second sub-block is Q.

[0224] The size of the first RBG within the second sub-block is determined based on the number of the starting RB of the second sub-block in the common resources of the carrier associated with the second sub-block, or the number of the starting RB of the second sub-block in the first virtual carrier.

[0225] The size of the last RBG within the second sub-block is determined based on the size of the second sub-block and the Q.

[0226] In some implementations, the first BWP includes at least one sub-block group, each of the at least one sub-block group including at least one sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including:

[0227] The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

[0228] In some implementations, the at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

[0229] In some implementations, all RBGs in the third sub-block except the last RBG are of the same size, or all RBGs in the third sub-block except the first RBG and the last RBG are of the same size.

[0230] In some implementations, the at least one sub-block group includes a first sub-block group, and the RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG, including:

[0231] The size of the RBG in the first sub-block group is related to the nominal RBG size L in the reference sub-block group, where L is a positive integer, and the reference sub-block group is pre-configured or pre-defined.

[0232] In some implementations, the third sub-block belongs to the first sub-block group.

[0233] The size of the non-edge RBG in the third sub-block is L.

[0234] The size of the first RBG in the third sub-block is L.

[0235] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and the L.

[0236] In some implementations, the third sub-block belongs to the first sub-block group.

[0237] The size of the non-edge RBG in the third sub-block is L.

[0238] The size of the first RBG in the third sub-block is determined based on the number of the starting RB of the third sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information.

[0239] The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the third sub-block indicated by the first indication information, the size of the third sub-block, and L.

[0240] In some implementations, the third sub-block belongs to the first sub-block group.

[0241] The size of the non-edge RBG in the third sub-block is L.

[0242] The size of the first RBG within the third sub-block is L.

[0243] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0244] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0245] The size of the non-edge RBG in the third sub-block is L.

[0246] The size of the first RBG within the third sub-block is determined based on the number of the starting RB of the third sub-block in the common resources of the carrier associated with the third sub-block, or the number of the starting RB of the third sub-block in the first virtual carrier.

[0247] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0248] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0249] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the value of L.

[0250] The size of the RBGs in the third sub-block, excluding the last RBG, is L.

[0251] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0252] The size of the first RBG within the third sub-block is determined based on the starting position of the third sub-block and L. The starting position of the third sub-block is either the common resource number of the starting RB of the third sub-block within the sub-block, or the common resource number of the starting RB of the third sub-block within the first virtual carrier.

[0253] The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and the L.

[0254] In some implementations, the third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L.

[0255] The size of the first RBG and the size of the last RBG within the third sub-block are determined based on the size of the third sub-block and the position of the third sub-block.

[0256] It should be understood that the third and fourth aspects are the device-side implementation methods corresponding to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0257] Fifthly, this application provides a communication device, including an interface circuit and a processor. The interface circuit is used to implement the functions of the transceiver unit in the third aspect, and the processor is used to implement the functions of the processing unit in the third aspect.

[0258] In a sixth aspect, this application provides a communication device, including an interface circuit and a processor. The interface circuit is used to implement the functions of the transceiver unit in the fourth aspect, and the processor is used to implement the functions of the processing unit in the fourth aspect.

[0259] In a seventh aspect, this application provides a computer-readable medium storing program code for execution by a terminal device, the program code including instructions for performing the first aspect, or any possible manner of the first aspect, or all possible manner of the first aspect.

[0260] Eighthly, embodiments of this application provide a computer-readable medium storing program code for execution by a network-side device, the program code including instructions for performing a method for the second aspect, or any possible manner of the second aspect, or all possible manner of the second aspect.

[0261] Ninth aspect, a computer program product storing computer-readable instructions is provided, which, when executed on a computer, causes the computer to perform the method described in the first aspect, or any possible manner of the first aspect, or all possible manner of the first aspect.

[0262] In a tenth aspect, a computer program product storing a computer-readable instruction is provided, which, when executed on a computer, causes the computer to perform the second aspect described above, or any possible manner of the second aspect, or all possible manner of the second aspect.

[0263] Eleventhly, a communication system is provided, the communication system including means having a method for implementing the first aspect, or any possible mode of the first aspect, or all possible modes of the first aspect, a second aspect, or any possible mode of the second aspect, or all possible modes of the second aspect, and various possible design functions.

[0264] In a twelfth aspect, a processor is provided for coupling with a memory for performing the methods described in the first aspect above, or any possible manner of the first aspect, or all possible manner of the first aspect.

[0265] In a thirteenth aspect, a processor is provided for coupling with memory for performing the second aspect, or any possible manner of the second aspect, or all possible manner of the second aspect.

[0266] In a fourteenth aspect, a chip system is provided, comprising a processor and further comprising a memory for executing computer programs or instructions stored in the memory, such that the chip system implements the methods of either the first or second aspect described above, and any possible implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0267] In a fifteenth aspect, a communication method is provided, the method comprising: a first device sending first indication information to a second device, the first indication information indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth (BWP), the first BWP including frequency domain resources corresponding to at least two sub-blocks within the first virtual carrier, the size of a resource block group (RBG) in the first BWP being related to the at least two sub-blocks; and the second device communicating with a network-side device based on the first virtual carrier indicated by the first indication information. Attached Figure Description

[0268] Figure 1 This is a schematic diagram of the architecture of the communication system 1000 used in the embodiments of this application.

[0269] Figure 2 This is a schematic diagram of carrier aggregation.

[0270] Figure 3 This is a schematic diagram of a communication method provided in an embodiment of this application.

[0271] Figure 4 This is a schematic diagram of a virtual carrier provided in an embodiment of this application.

[0272] Figure 5 (a) is a schematic diagram of another virtual carrier provided in the embodiments of this application.

[0273] Figure 5 (b) is a schematic diagram of another virtual carrier provided in the embodiments of this application.

[0274] Figure 6This is a schematic diagram of the size of an RBG within a virtual carrier provided in an embodiment of this application.

[0275] Figure 7 This is a schematic diagram of the size of RBG within another virtual carrier provided in the embodiments of this application.

[0276] Figure 8 This is a schematic diagram of the size of RBG within another virtual carrier provided in the embodiments of this application.

[0277] Figure 9 This is a schematic block diagram of a communication device.

[0278] Figure 10 This is a schematic block diagram of yet another type of communication device.

[0279] Figure 11 This is a schematic block diagram of yet another type of communication device. Detailed Implementation

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

[0281] Figure 1 This is a schematic diagram of the architecture of the communication system 1000 used in an embodiment of this application. Figure 1 As shown, the communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include an Internet 300. The wireless access network 100 may include at least one wireless access network device (such as...). Figure 1 110a and 110b in the above), may also include at least one terminal (such as Figure 1 (Referring to 120a-120j in the original text). Terminals connect wirelessly to the wireless access network (WLAN) equipment, which in turn connects to the core network via wireless or wired connections. The core network equipment and the WLAN equipment can be independent physical devices, or they can integrate the functions of the core network equipment and the logical functions of the WLAN equipment onto the same physical device. Alternatively, a single physical device can integrate some of the functions of both the core network equipment and the WLAN equipment. Terminals and WLAN equipment can be interconnected via wired or wireless connections. Figure 1 This is just an illustration; the communication system may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 1 It is not shown in the middle.

[0282] Radio access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). Here, the CU performs the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). Wireless access network equipment can be macro base stations (such as...) Figure 1 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1 110b) in the text can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technology or device form used in the wireless access network equipment. For ease of description, the following description uses a base station as an example of a wireless access network device.

[0283] Terminal equipment can be a device that provides voice / data to users, such as a handheld device or vehicle-mounted device with wireless connectivity. Terminal equipment may include user equipment, and is sometimes also called a terminal, access station, user equipment (UE), UE station, remote station, wireless communication equipment, or user device, etc.

[0284] For example, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a complete vehicle, a wireless communication module in a complete vehicle, a telematics box (T-Box), a roadside unit (RSU), a wireless terminal in autonomous driving, a wireless terminal device in the Internet of Things (IoT), a wireless terminal device in telemedicine, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc., and the embodiments of this application are not limited thereto.

[0285] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but can also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include devices that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for measuring vital signs.

[0286] Terminal devices can also be V2X devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles (EVs), hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), new energy vehicles, and roadside units (RSUs). Terminal devices can also be devices used in device-to-device (D2D) communication, such as electricity meters and water meters.

[0287] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0288] The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can all be considered in-vehicle terminal devices, also known as on-board units (OBUs). The terminal device of this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit.

[0289] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0290] The roles of base stations and terminals can be relative, for example, Figure 1The helicopter or drone 120i can be configured as a mobile base station. For terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0291] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0292] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0293] The technical solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication between communication devices can include: wireless communication between network devices and terminals, wireless communication between network devices, and wireless communication between terminal devices. In this application, the term "wireless communication" can also be abbreviated as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0294] It is understood that the names of the signaling signals in the embodiments of this application are merely examples and may have different names in different systems and scenarios. The embodiments of this application do not limit this.

[0295] To facilitate understanding of the embodiments of this application, the terms involved in the embodiments of this application will be briefly explained below.

[0296] 1. Carrier

[0297] A carrier wave, or carrier frequency, is a physical concept. It is a radio wave of a specific frequency, measured in Hertz (Hz). It is an electromagnetic wave that is modulated in terms of frequency, amplitude, or phase to transmit speech, audio, images, or other signals.

[0298] 2. Bandwidth Part (BWP)

[0299] A Common Resource Block (BWP) is a set of consecutive common resource blocks (CRBs) within a portion of the bandwidth of a carrier (e.g., a cell in 100MHz), at a specific subcarrier interval. Each BWP can have three different parameters: subcarrier interval, symbol duration, and cyclic prefix (CP) length. In an NR system, a UE can configure up to four BWPs for downlink and uplink, but at any given time, only one BWP is active for downlink and one BWP is active for uplink.

[0300] 3. Resource block group (RBG)

[0301] An RBG is a resource unit for allocating traffic channel resources, consisting of a set of resource blocks (RBs). A BWP includes one or more RBGs.

[0302] Considering the implementation capabilities of both the terminal and the network, in 5G, for frequencies below 6GHz, the maximum bandwidth supported by the terminal is 100MHz; for frequencies above 6GHz, the maximum bandwidth supported by the terminal is 400MHz. This means the maximum carrier bandwidth is either 100MHz or 400MHz. The maximum speed for a single user can be improved through carrier aggregation (CA). Carrier aggregation can be intra-band carrier aggregation, inter-band carrier aggregation, or continuous or non-continuous carrier aggregation.

[0303] 4. Joint construction and sharing

[0304] To reduce network deployment costs, different operators may consider jointly building networks through network sharing. Depending on the shared equipment, this can include the following scenarios:

[0305] Infrastructure sharing: In this approach, different operators share towers and equipment rooms, while the networks of different operators remain independent.

[0306] Master device sharing: In this method, master devices (including base stations, antennas, etc.) can be shared.

[0307] Network roaming: In this method, different operators have independent networks and each operates its own network, but network sharing is achieved between different operators through roaming protocols.

[0308] It can be seen that, compared with the independent operation of the network by operators in the network roaming mode, the infrastructure sharing mode only shares sites, while the main equipment sharing (also known as radio access network (RAN) sharing) can achieve deeper sharing, which helps to further reduce network construction costs.

[0309] In the RAN sharing scenario, depending on whether spectrum resources are shared, it can be further divided into shared carrier frequency sharing and shared carrier frequency sharing.

[0310] 3GPP defines a shared carrier frequency scenario in TS23.501. On the radio side, 3GPP TS23.501 specifies that each cell broadcasts multiple public land mobile network (PLMN) information through System Information Block Type 1 (SIB1); the UE selects a PLMN and reports the selected PLMN to the sharing base station; the sharing base station routes the UE to the corresponding core network according to the PLMN selected by the UE.

[0311] In shared carrier scenarios, operators can share spectrum resources, meaning that users of operator A can use the spectrum resources allocated to operator B. However, since the spectrum resources currently allocated to different operators correspond to different carriers, when users of operator A simultaneously use the spectrum resources allocated to both operator A and operator B, carrier aggregation is required.

[0312] like Figure 2 As shown, taking the co-construction and sharing of spectrum on the C-band by operator A (corresponding to carrier 1) and operator B (corresponding to carrier 2) as an example, the system messages of both carrier 1 and carrier 2 will broadcast the PLMNs of operator A and operator B. Terminals can use the spectrum resources corresponding to carrier 1 and / or carrier 2. As mentioned earlier, since there are two corresponding carriers, the terminal needs to use carrier aggregation to simultaneously use the spectrum resources corresponding to carrier 1 and carrier 2. Currently, while sharing through master equipment helps reduce network construction costs, it still has certain limitations and is not flexible enough.

[0313] In the carrier sharing method, the spectrum is not shared between operators, which cannot maximize spectrum utilization. In addition, in low network load scenarios, the carriers of different operators need to remain active. From the perspective of the base station, a wider radio frequency bandwidth is required, which will consume more network energy.

[0314] Carrier sharing: Carrier sharing helps improve spectrum utilization, but when using the resources of two carriers simultaneously, carrier aggregation is required. However, carrier aggregation has the following drawbacks:

[0315] The signaling overhead is high, requiring the network side to provide configuration information for each carrier;

[0316] Activation / deactivation delay: After configuring the secondary carrier on the network side, the activation / deactivation of the secondary carrier needs to be performed through the media access control element (MAC CE), which increases the activation / deactivation delay.

[0317] Resources are not fully utilized. Even in intra-band scenarios, each carrier has a guard band, and data transmission cannot be performed within the guard band, resulting in underutilization of resources.

[0318] The terminal must support CA capabilities.

[0319] In other words, for co-construction and sharing scenarios, carrier aggregation is used to aggregate carriers from different operators, especially consecutive carriers. However, carrier aggregation can lead to problems such as activation / deactivation latency, underutilization of resources, and high signaling overhead.

[0320] In view of this, this application proposes a communication method that can reduce processing latency and signaling overhead, and improve resource utilization.

[0321] This communication method can be applied between network devices and terminal devices, between network devices, or between terminal devices; this application does not make any specific limitations.

[0322] The following example uses a first device and a second device as the executing entities of this communication method to illustrate the method. The first device can be a network-side device, such as a network device, and the second device can be a terminal-side device, such as a terminal device. Figure 3 As shown, the method includes the following steps:

[0323] S310, the first device sends a first instruction message to the second device, and the second device receives the first instruction message accordingly.

[0324] The first indication information indicates a virtual carrier (e.g., a first virtual carrier). This first indication information may be system information (SI).

[0325] A virtual carrier comprises at least two sub-blocks, each of which corresponds to one carrier (also referred to as a physical carrier in this document). In other words, a virtual carrier includes at least two carriers. A virtual carrier includes a frequency-domain resource plan (BWP), the frequency domain resources of which are the frequency domain resources corresponding to the at least two sub-blocks included in the virtual carrier. Alternatively, a BWP can be mapped to two or more physical carriers.

[0326] It should be understood that the use of "virtual carrier" as a name in this application is not intended to limit the scope of the application. For example, the virtual carrier may also be referred to as a carrier group, carrier set, multi-carrier, etc.

[0327] Taking virtual carrier A (an example of a first virtual carrier) as an example, virtual carrier A includes carrier 1 and carrier 2, and virtual carrier A includes sub-block 1 and sub-block 2. Sub-block 1 corresponds to carrier 1, and sub-block 2 corresponds to carrier 2. The frequency domain resources included in the BWP of this virtual carrier A are the frequency domain resources corresponding to sub-block 1 and sub-block 2.

[0328] Virtual carriers are logically continuous; for example, the virtual RB (virtual RB) numbers (or indices) corresponding to the virtual carriers are consecutive, or the frequency domain resources included in the BWP of the virtual carrier are consecutive. Figure 4 As shown, a virtual carrier comprises a logically contiguous segment of frequency domain resources, which originate from two or more sub-blocks. Figure 4 The virtual carrier comprises 150 logically contiguous virtual resource blocks (VRBs). VRBs numbered 0-49 originate from sub-block 1, VRBs numbered 50-99 originate from sub-block 2, VRBs numbered 100-149 originate from sub-block 3, and so on. Each sub-block is associated with a physical carrier.

[0329] Virtual carriers can be physically continuous or discontinuous. For example, the physical carriers associated with a sub-block can be intra-band or inter-band carriers. Figure 5 As shown in (a), the frequency domain resources corresponding to sub-block 1 and sub-block 2 are not contiguous, and there is a guard band between the frequency domain resources corresponding to sub-block 2 and sub-block 3. For example... Figure 5 As shown in (b), the frequency domain resources corresponding to sub-block 1, sub-block 2 and sub-block 3 are continuous.

[0330] In some embodiments, a BWP includes multiple RBGs, the size of which is related to at least two sub-blocks. As previously mentioned, an RBG consists of a set of resource blocks (RBs), or an RBG consists of one or more RBs. The size of an RBG is the number of RBs it contains.

[0331] It should be understood that the RB in this application can be either a VRB or a Physical Resource Block (PRB), and there is no limitation on the latter.

[0332] One possible approach is that the size of the RBG in the BWP is determined based on the size of the BWP and a first value, where the size of the BWP is the number of resource blocks (RBs) contained in at least two sub-blocks included in the BWP.

[0333] The first value is determined based on the size of the reference sub-block, which belongs to at least two sub-blocks and is either configured or predefined. For example, the first value can be the number of RBs included in the reference sub-block. Alternatively, the first value can be the nominal RBG size determined by the number of RBs in the reference sub-block, which serves as the nominal RBG size within this BWP. For instance, if the BWP has 150 RBs, the reference sub-block has 60 RBs, and the nominal RBG obtained from the reference sub-block is 4, then the BWP contains a total of 38 RBGs.

[0334] Optionally, the reference subblock is configured, and this reference subblock can be configured on the network side when configuring virtual carriers or BWP.

[0335] Alternatively, the first value is determined based on the size of the BWP and a first correspondence, which is the correspondence between the BWP size and the nominal RBG size. The size of the BWP is the number of RBs included in the BWP.

[0336] Furthermore, this mapping relationship is related to the BWP configuration. For example, the first mapping relationship can be shown in Table 1.

[0337] Table 1. Correspondence between nominal RBG size and BWP size within the BWP

[0338]

[0339] Configuration 1 and Configuration 2 represent different configuration granularities, which can be configured on the network side. The number of RBs included in the RBG differs between Configuration 1 and Configuration 2, resulting in different sizes of the corresponding frequency domain resource allocation indicator domain. For example, the granularity of Configuration 1 is smaller than that of Configuration 2. The values ​​in the Configuration 1 and Configuration 2 columns of Table 1 represent the granularity size, i.e., the nominal RBG size. The values ​​in the BWP size column represent the number of RBs included in the BWP. For example, the value 2 in the Configuration 1 column indicates that under Configuration 1, the nominal RBG includes 2 RBs. Other values ​​in the Configuration 1 and Configuration 2 columns can be found in the explanation here.

[0340] For example, if the number of RBs in a BWP is 100, and the network side is configured as Configuration 1, then one RBG contains 8 RBs (i.e., the nominal size of the RBG is 8), and there are a total of 13 RBGs in the BWP; if the network side is configured as Configuration 2, then one RBG contains 16 RBs (i.e., the nominal size of the RBG is 16), and there are a total of 7 RBGs in the BWP.

[0341] In one possible implementation 1, only the size of the last RBG within the BWP can differ from the sizes of the other RBGs.

[0342] For example, the size of the last RBG within the BWP is determined based on the size of the BWP (also known as bandwidth) and the first value. The sizes of all RBGs within the BWP except the last RBG are the first value.

[0343] For example, the size of the last RBG within the BWP is obtained by taking the modulo of the BWP bandwidth and the first value T. Specifically, the size of the last RBG within the BWP... modT, where Let T be the size of the BWP, and T be the first possible value. T can be determined based on the size of the BWP and the correspondence between the BWP size and the nominal RBG size (e.g., Table 1). Alternatively, T can be determined based on the size of the reference sub-block. For example, as mentioned earlier, the size of the reference sub-block can be directly used as the nominal RBG size; for instance, if the reference sub-block includes 4 RBs, then the nominal RBG size is determined to be 4 RBs. The reference sub-block can be any of the sub-blocks included in the BWP. The size of all RBGs within the BWP except the last RBG is T. For example... Figure 6 As shown, the size of the first RBG in BWP is G1, the size of the last RBG is G2, and the size of the remaining RBGs is T. In this implementation, G1 = T, G2 < T.

[0344] In one possible implementation 2, only the size of the first RBG and the size of the last RBG within the BWP can be less than or equal to the size of the other RBGs.

[0345] For example, the size of the first RBG within a BWP is determined based on the starting position of the BWP and a first value. The starting position of the BWP is the common resource number of the starting RB within the sub-block or virtual carrier, or the common resource number of the starting RB within the virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and a first value.

[0346] When configuring resources (such as multiple Resource Blocks) for communication, network devices can assign numbers to these RBs, which can correspond to different sub-blocks. These RBs can be called common resources. The common resource number of the starting RB in a BWP within a sub-block or virtual carrier is the number assigned to that RB by the network device.

[0347] The common resource numbering within a virtual carrier can be understood as: uniformly numbering the resource blocks (RBs) of the virtual carrier based on its carrier bandwidth. Optionally, the starting position of the common resources can differ for different subcarrier intervals. For example, when configuring a virtual carrier, the network side indicates the starting position of the common resources of the virtual carrier and uniformly numbers the RBs starting from that starting position. As mentioned earlier, within the virtual carrier, the network side will configure a BWP for the terminal, and the starting position of the BWP is any RB within the virtual carrier.

[0348] For example, the size of the first RBG is obtained by taking the difference between the nominal RBG size K and the modulo of the starting position of the BWP and the nominal RBG size K. The size of the last RBG is obtained by taking the modulo of the BWP and the nominal RBG size K. For other RBGs, their size is equal to the nominal RBG size K. Here, K can be determined based on the size of the BWP and the correspondence between the size of the BWP and the nominal RBG size (e.g., Table 1). Alternatively, K can be determined based on the size of a reference sub-block, which can be any of the sub-blocks included in the BWP.

[0349] For example, the size of the first RBG and the size of the last RBG within a BWP are calculated as follows:

[0350] The size E of the first RBG within BWP satisfies the following relationship:

[0351]

[0352] in, Let K be the starting position of BWP, and K be the first value.

[0353] The size F of the last RBG in BWP satisfies the following relationship:

[0354]

[0355] in, Let BWP be the size, and K be the first possible value.

[0356] like Figure 6 As shown, the size of the first RBG in BWP is G1, the size of the last RBG is G2, and the size of the remaining RBGs is K (i.e., T takes the value K). In this implementation, G1≤K, G2≤K.

[0357] Another possible approach 2: Include multiple sub-blocks in the BWP, where the size of the RBG in each sub-block is related to the size of the sub-block.

[0358] In BWP, multiple sub-blocks can be distinguished into edge RBGs and non-edge RBGs. For example, edge RBGs are the first and last RBGs within a certain sub-block, while non-edge RBGs are all RBGs within that sub-block except for the edge RBGs.

[0359] One possible implementation 3: The size of the RBG in the first sub-block is related to the reference sub-block. Further, the size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer, and the reference sub-block is configured or predefined. The first sub-block is a sub-block among at least two sub-blocks. The nominal RBG size in the reference sub-block can be determined based on the size of the reference sub-block. The size of the reference sub-block is the number of RBs included in the reference sub-block. P can be determined based on the correspondence between the sub-block size and the nominal RBG size. The correspondence between the sub-block size and the nominal RBG size is shown in Table 2.

[0360] Table 2 shows the correspondence between the nominal RBG size and the sub-block size within the BWP.

[0361]

[0362] The BWP size, configuration 1, and configuration 2 items can be referred to in the previous explanation of Table 1, and will not be repeated here. The difference is that the configuration granularity in configuration 1 or configuration 2 here is at the sub-block level. The values ​​in the configuration 1 and configuration 2 columns represent the nominal RBG size within the sub-block. For example, the value 2 in the configuration 1 column means that under configuration 1, the nominal RBG within a sub-block includes 2 RBs. Other values ​​in the configuration 1 and configuration 2 columns can be referred to in the explanation here.

[0363] For example, the size of the non-edge RBG in the first sub-block is P, the size of the first RBG in the first sub-block is P, and the size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P.

[0364] Optionally, the size of the last RBG in the first sub-block is obtained by taking the modulo of the size of the first sub-block and P.

[0365] by Figure 7 For example, the diagram includes sub-block 1, sub-block 2, and sub-block 3. In sub-block 1, the size of the first RBG is X1, the size of the last RBG is Y1, and the size of the remaining RBGs is R1. In sub-block 2, the size of the first RBG is X2, the size of the last RBG is Y2, and the size of the remaining RBGs is R2. In sub-block 3, the size of the first RBG is X3, the size of the last RBG is Y3, and the size of the remaining RBGs is R3. Sub-block 2 is the reference sub-block, and the nominal RBG size corresponding to sub-block 2 is R2. R1 and R3 are both equal to R2. In this example, the sizes of X1, X2, and X3 are also equal to R2, and the values ​​of Y1, Y2, and Y3 can be different, but all are less than or equal to R2.

[0366] In another example, the size of the non-edge RBG in the first sub-block is P. The size of the first RBG in the first sub-block is determined based on the common resource number of the starting RB of the first sub-block in the virtual carrier, or the size of the first RBG in the first sub-block is indicated by the network device. The common resource number in this virtual carrier is explained above and will not be repeated here.

[0367] The size of the last RBG in the first sub-block is determined by the size of the first sub-block and P. For example, the size of the last RBG in the first sub-block is obtained by taking the modulo of the size of the first sub-block and P.

[0368] Alternatively, the size of the last RBG in the first sub-block is determined by the size of the first RBG in the first sub-block as indicated by the network device, the size of the first sub-block, and P.

[0369] For example, the size S of the last RBG in the first sub-block, and the size of the first RBG in the first sub-block as indicated by the network device. The size of the first sub-block is N sub-block,i P and P satisfy the following relationship:

[0370]

[0371] in This is for floor function.

[0372] Or with Figure 7For example, if sub-block 2 is the reference sub-block, and the nominal RBG size corresponding to sub-block 2 is R2 (with a value of P), then R1 and R3 in the diagram are both equal to R2. In this method, the values ​​of X1, X2, and X3 can be different, and are less than or equal to R2. The sizes of X1, X2, and X3 can be determined based on the starting position of the corresponding sub-block; the values ​​of Y1, Y2, and Y3 can be different, but are all less than or equal to R2.

[0373] One possible implementation 4: The first BWP consists of M sub-blocks, where M is an integer greater than or equal to 2. The size of the RBG in any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG. That is, in this implementation, the size of each RBG in each sub-block is determined based on the size of that sub-block.

[0374] For example, the nominal RBG size of the second sub-block is Q, the second sub-block belongs to M sub-blocks, the size of the non-edge RBGs in the second sub-block is Q, the size of the first RBG in the second sub-block is Q, and the size of the last RBG in the second sub-block is determined based on the size of the second sub-block and Q. The nominal RBG size can be determined based on the size of the second sub-block, for example, according to Table 2.

[0375] The second sub-block can be one or more of the M sub-blocks. When the second sub-block is one of the M sub-blocks, the size of the RBG in each sub-block can be determined by referring to the method for determining the size of the RBG in the second sub-block. That is, within each sub-block, the size of the first RBG is equal to the nominal RBG size determined for that sub-block; within each sub-block, the size of the last RBG is determined based on the size of that sub-block and the nominal RBG size determined for that sub-block, for example, by taking the modulo between the size of that sub-block and the nominal RBG size determined for that sub-block.

[0376] by Figure 7 For example, in this implementation, X1 = R1, X2 = R2, X3 = R3, Y1 is less than or equal to R1, Y2 is less than or equal to R2, and Y3 is less than or equal to R3.

[0377] In another example, the size of the non-edge RBG in the second sub-block is Q. The size of the first RBG in the second sub-block is determined based on the number of the starting RB of the second sub-block in the common resources of the carrier associated with the second sub-block, or the number of the starting RB of the second sub-block in the first virtual carrier. The size of the last RBG in the second sub-block is determined based on the size of the second sub-block and Q. For example, it can be obtained by taking the modulo between the sub-block size and the RBG size. The number of the common resources can be referred to the previous explanation, which will not be repeated here.

[0378] The second sub-block can be one or more of the M sub-blocks. When the second sub-block is one of the M sub-blocks, the size of the RBGs in each sub-block can be determined by referring to the method for determining the size of the RBGs in the second sub-block. That is, within each sub-block, the first and last RBGs can be less than or equal to the nominal RBG size determined by their respective sub-blocks; the size of other RBGs is equal to the nominal RBG size determined based on that sub-block.

[0379] One possible implementation 5: The BWP includes at least one sub-block group, and any sub-block group in the at least one sub-block group includes at least one sub-block. The size of the RBG of any sub-block group in the at least one sub-block group is determined according to the number of RBs included in the sub-block group corresponding to the RBG.

[0380] In other words, the BWP can be divided into different sub-block groups, or the size of the RBG can be determined at the granularity of sub-block groups. Specifically, the implementation determines the RBG size in the following ways:

[0381] Case 1: The at least one sub-block group includes a first sub-block group, the size of the RBG in the first sub-block group is related to the nominal RBG size L in the reference sub-block group, where L is a positive integer, and the reference sub-block group is pre-configured or pre-defined.

[0382] The nominal RBG size in the reference sub-block group can be determined based on the correspondence between the size of the reference sub-block group and the nominal RBG size, as shown in Table 3.

[0383] Table 3 shows the correspondence between the nominal RBG size within the BWP and the size of the reference sub-block group.

[0384]

[0385] The BWP size, configuration 1, and configuration 2 items can be found in the previous explanation of Table 1, and will not be repeated here. The difference lies in the granularity of the configuration in configuration 1 or configuration 2, which is the granularity within a reference sub-block group. The values ​​in columns 1 and 2 represent the nominal RBG size within a reference sub-block group. For example, the value 2 in column 1 indicates that under configuration 1, the nominal RBG within a reference sub-block group includes 2 RBs. Other values ​​in columns 1 and 2 can be found in the explanation here.

[0386] In one example, the third sub-block belongs to the first sub-block group. The size of the non-edge RBG in the third sub-block is L. The size of the first RBG in the third sub-block is L. The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L.

[0387] The third sub-block can be one or more of the first sub-blocks. When the third sub-block is one of the first sub-blocks, the size of the RBGs in each sub-block can be determined by referring to the method used to determine the size of the RBGs in the third sub-block. That is, only the size of the last RBG in the third sub-block may be less than or equal to L. For example, the size of the last RBG in the third sub-block can be obtained by taking the modulo of the size of the third sub-block and L.

[0388] In another example, the third sub-block belongs to the first sub-block group. The size of the non-edge RBG in the third sub-block is L. The size of the first RBG in the third sub-block is determined based on the numbering of the starting RB of the third sub-block in the first virtual carrier. Alternatively, the size of the first RBG in the first sub-block is indicated by the indication information. The size of the last RBG in the third sub-block is determined based on the size of the third sub-block and L. Or, the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the third sub-block indicated by the indication information, the size of the third sub-block, and L. That is, the size of the RBG in each sub-block group is determined separately.

[0389] Case 2: The size of the RBG is determined independently within each sub-block group.

[0390] In one example, the third sub-block belongs to the first sub-block group. The size of the non-edge RBGs in the third sub-block is L. The size of the first RBG within the third sub-block is L. The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and L. For example, the size of the last RBG within the third sub-block is determined by taking the modulo of the size of the third sub-block and L. This L is determined based on the size of the sub-block group. For details, please refer to the previous explanation; further elaboration is omitted here.

[0391] In another example, the size of the non-edge RBG in the third sub-block is L. The size of the first RBG in the third sub-block is determined by the number of the starting RB of the third sub-block in the common resources of the carrier associated with the third sub-block, or by the number of the starting RB of the third sub-block in the virtual carrier. The size of the last RBG in the third sub-block is determined by the size of the third sub-block and L. For example, the size of the last RBG in the third sub-block is determined by taking the modulo of the size of the third sub-block and L. This L is determined based on the size of the sub-block group. For details, please refer to the previous explanation, which will not be repeated here.

[0392] Specifically, these examples can be found in the descriptions of possible method 1 and method 2 above. The calculation methods are similar, but the difference is that in these examples, the calculation is performed at the sub-block group level.

[0393] Scenario 3: The third sub-block belongs to the first sub-block group, and the nominal RBG size of the third sub-block is L. The size of the first RBG within the third sub-block is determined based on the starting position of the third sub-block and L. The starting position of the third sub-block is either the common resource number of the starting RB within the sub-block, or the common resource number of the starting RB within the first virtual carrier. The size of the last RBG within the third sub-block is determined based on the size of the third sub-block and L. Here, L is determined based on the size of the sub-block group to which the third sub-block belongs. For example, it can be determined according to Table 3.

[0394] like Figure 8 As shown, the virtual carrier comprises two sub-block groups, namely sub-block group 1 and sub-block group 2. Sub-block group 1 includes sub-block 1 and sub-block 2, and sub-block group 2 includes sub-block 3. In sub-block 1, the size of the first RBG is X1, the size of the last RBG is Y1, and the size of the remaining RBGs is U1; in sub-block 2, the size of the first RBG is X2, the size of the last RBG is Y2, and the size of the remaining RBGs is U2; in sub-block 3, the size of the first RBG is X3, the size of the last RBG is Y3, and the size of the remaining RBGs is U3.

[0395] For example, in case 4, the third sub-block is sub-block 1, and L is determined based on the size of sub-block group 1 (i.e., the total number of RBs included in sub-block 1 and sub-block 2). Therefore, U1 and U2 have the same value, L. The values ​​of X1, X2, and X3 may differ, as may the values ​​of Y1, Y2, and Y3.

[0396] Case 4: The third sub-block belongs to the first sub-block group. The nominal RBG size of the third sub-block is L. The size of the first RBG and the size of the last RBG in the third sub-block are determined based on the size and position of the third sub-block.

[0397] That is, the size of each RBG is determined as a whole for the sub-block group, and the size of the first and last RBG within each sub-block can be less than or equal to the nominal RBG size determined by its respective sub-block. For example, it can be determined according to Table 3. Figure 8 For example, U1 = U2, X1 and Y1 are less than or equal to U1, and their size is determined by the size and position of sub-block 1; X2 and Y2 are less than or equal to U2, and their size is determined by the size and position of sub-block 1.

[0398] It should be understood that in one possible implementation 5, the two sub-blocks in sub-block group 1 are contiguous, and sub-block group 1 and sub-block group 2 are not contiguous, but this application is not limited to this. For example, the sub-blocks in a sub-block group can also be non-contiguous.

[0399] S320, the second device communicates with the first device based on the first virtual carrier indicated by the first instruction information.

[0400] For example, the second device determines the first virtual carrier based on the first instruction information, sends information to the first device on the first virtual carrier, and / or receives information from the first device.

[0401] Optionally, the first device can also determine the frequency domain resource allocation unit indication field based on the number of RBGs in the BWP. For example, the number of bits contained in the frequency domain resource allocation unit indication field can be determined based on the number of RBGs. This frequency domain resource allocation unit indication field can be in the DCI. That is, in this application, the network side first configures the BWP for the terminal side, then determines the number of RBGs in the BWP according to the above scheme, and further determines the frequency domain resource allocation unit indication field based on the number of RBGs.

[0402] This method simplifies the processing flow compared to multi-carrier aggregation by defining virtual carriers. For example, it eliminates the need for frequent activation or deactivation, saving signaling overhead. Furthermore, by defining the calculation method for the RBG size under the virtual carrier, it aligns the understanding between the network side and the terminal side, enabling RBG-based resource scheduling while minimizing resource indication overhead.

[0403] The solution proposed in this application can be applied to 5.5G, 6G and future wireless communication systems. Applicable scenarios include, but are not limited to, terrestrial cellular communication, non-terrestrial communication (NTN), satellite communication, high altitude platform station (HAPS) communication, vehicle-to-everything (V2X) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication.

[0404] The various implementation methods described in this article can be independent solutions or combinations based on their internal logic, and all of these solutions fall within the protection scope of this application.

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

[0406] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0407] Similar to the above concept, such as Figure 9 As shown, this application embodiment also provides an apparatus 900 for implementing the functions of the transmitting or receiving device in the above method. For example, the apparatus can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or may include chips and other discrete devices. The apparatus 900 may include a processing unit 910 and a communication unit 920.

[0408] In this embodiment of the application, the communication unit may also be called a transceiver unit, which may include a sending unit and / or a receiving unit, respectively used to perform the sending and receiving steps of the sending device or the receiving device in the above method embodiment.

[0409] The following, combined with Figures 9 to 11 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0410] A communication unit can also be called a transceiver, transceiver device, or transceiver unit. A processing unit can also be called a processor, processing board, processing module, or processing device. Optionally, the device in communication unit 920 used to implement the receiving function can be considered a receiving unit, and the device in communication unit 920 used to implement the transmitting function can be considered a transmitting unit; that is, communication unit 920 includes a receiving unit and a transmitting unit. A communication unit can sometimes also be called a transceiver, transceiver unit, or interface circuit. A receiving unit can sometimes be called a receiver, receiver circuit, or receiving unit. A transmitting unit can sometimes be called a transmitter, transmitter, or transmitting circuit.

[0411] The communication device 1000 performs the above embodiment. Figure 3 The function of the first device in the process shown is as follows:

[0412] The communication unit is used for sending and receiving information, such as sending the first instruction message.

[0413] The processing unit is used to determine the first indication information, determine the first virtual carrier, etc.

[0414] The communication device 1000 performs the above embodiment. Figure 3When the second device functions in any of the processes shown:

[0415] The processing unit is used to determine a first virtual carrier, etc., based on the first indication information.

[0416] A communication unit is used to send and receive information. For example, it is used to receive first instruction information or to send information to a second device on a first virtual carrier.

[0417] The above is just an example. The processing unit 910 and the communication unit 920 can also perform other functions. For a more detailed description, please refer to [link / reference needed]. Figure 3 The descriptions of the method embodiments shown or other method embodiments are not repeated here.

[0418] As another possible product form, the transmitting and receiving devices described in the embodiments of this application can be implemented using a general bus architecture. For ease of explanation, see [link to documentation]. Figure 10 , Figure 10 This is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of this application. The communication device 1000 includes a processor 1001 and a transceiver 1002. The communication device 1000 can be a first terminal device, or a chip or chip system therein; or, the communication device 1000 can be a second terminal device, or a chip or module therein; or, the communication device 1000 can be a third terminal device, or a chip or module therein; or, the communication device 1000 can be a fourth terminal device, or a chip or module therein; or, the communication device 1000 can be a fifth terminal device, or a chip or module therein; or, the communication device 1000 can be a sixth terminal device, or a chip or module therein. Figure 10 Only the main components of the communication device 1000 are shown. In addition to the processor 1001 and transceiver 1002, the communication device 1000 may further include a memory 1003 and input / output devices (not shown).

[0419] Optionally, the processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0420] Optionally, the processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

[0421] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0422] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0423] In some embodiments, those skilled in the art will recognize that the above-described communication device 100 can be implemented in hardware using... Figure 10 The communication device 1000 shown is in the form of this device.

[0424] As an example, Figure 9 The function / implementation process of the processing module 920 can be achieved through... Figure 10 The processor 1001 in the communication device 1000 shown calls computer execution instructions stored in the memory 1003 to implement the function. Figure 9 The function / implementation process of the transceiver module 910 in the middle can be obtained through Figure 10 This is achieved through the transceiver 1002 in the communication device 1000 shown.

[0425] As another possible product form, the first and second devices in this application can be adopted. Figure 11 The shown composition structure, or including Figure 11 The components shown. Figure 11 A schematic diagram of the composition of a communication device 1100 provided in this application.

[0426] like Figure 11 As shown, the communication device 1100 includes a processor 1101. Optionally, the communication device also includes a communication interface 1102. It should be understood that the communication device may include multiple processors.

[0427] When the relevant program instructions are executed in the at least one processor 1101, the device 1100 may implement the methods and any possible designs provided in any of the foregoing embodiments. Alternatively, the processor 1101 may implement the methods and any possible designs provided in any of the foregoing embodiments through logic circuits or executable code instructions.

[0428] The communication interface 1102 can be used to receive program instructions and transmit them to the processor, or the communication interface 1102 can be used for communication interaction between the communication device 1100 and other communication devices, such as exchanging control signaling and / or service data. For example, the communication interface 1102 can be used to receive signals from other devices besides the communication device 1100 and transmit them to the processor 1101, or to send signals from the processor 1101 to other communication devices besides the communication device 1100.

[0429] Optionally, the communication interface 1102 can be a code and / or data read / write interface circuit, or the communication interface 1102 can be a signal transmission interface circuit between a communication processor and a transceiver, or a chip pin.

[0430] Optionally, the communication device 1100 may further include a memory 1103, which can be used to store the required program instructions and / or data. It should be noted that the memory 1103 may exist independently of the processor 1101 or may be integrated with the processor 1101. The memory 1103 may be located within or outside the communication device 1100, without limitation. It should be understood that the communication device may include multiple memories.

[0431] Optionally, the communication device 1100 may further include a power supply circuit 1104, which can be used to power the processor 1101. The power supply circuit 1104 may be located in the same chip as the processor 1101, or in a separate chip outside the chip containing the processor 1101.

[0432] Optionally, the communication device 1100 may also include a bus 1109, through which the various parts of the communication device 1100 can be interconnected.

[0433] In some embodiments, the hardware implementation will be apparent to those skilled in the art as described above. Figure 10 The communication device 100 shown can be adopted Figure 11 The communication device 1100 shown is in the form of this device.

[0434] As an example, Figure 9 The function / implementation process of the processing module 920 can be achieved through... Figure 11 The processor 1101 in the communication device 1100 shown calls computer execution instructions stored in memory 1103 to implement the function. Figure 9 The function / implementation process of the transceiver module 910 in the middle can be obtained through Figure 11 This is achieved through the communication interface 1102 in the communication device 1100 shown.

[0435] It should be pointed out that, Figure 11 The structures shown do not constitute a specific limitation on the transmitting or receiving devices. For example, in other embodiments of this application, the first device and the second device may include more or fewer components than those shown, or combine or separate certain components, or have different component arrangements. The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0436] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as an RF module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

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

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

[0439] In embodiments of this application, the processor may be a random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), register, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device or terminal device. Alternatively, the processor and storage medium may exist as discrete components in the network device or terminal device.

[0440] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0441] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0442] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0443] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0444] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive first indication information, the first indication information indicates a first virtual carrier, the first virtual carrier includes at least two sub-blocks, the at least two sub-blocks correspond one-to-one with at least two carriers, the first virtual carrier includes a first portion bandwidth BWP, the first BWP includes frequency domain resources corresponding to at least two sub-blocks in the first virtual carrier, and the size of resource block group RBG in the first BWP is related to the at least two sub-blocks. The first virtual carrier communicates with the network-side device based on the first indication information.

2. The method according to claim 1, characterized in that, The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of RBG in the first BWP is determined based on the size of the first BWP and a first value. The size of the first BWP is the number of resource blocks (RBs) contained in at least two sub-blocks included in the first BWP. The first value is determined based on the size of the reference sub-block, which belongs to the at least two sub-blocks. The reference sub-block is configured or predefined, or... The first value is determined based on the size of the first BWP and the first correspondence, which is the correspondence between the size of the BWP and the nominal RBG size.

3. The method according to claim 2, characterized in that, The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value. The size of the RBGs in the first BWP, excluding the last RBG, is the first value.

4. The method according to claim 2, characterized in that, The size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

5. The method according to claim 4, characterized in that, The size E of the first RBG within the first BWP satisfies the following relationship: in, Let K be the starting position of the first BWP, and K be the first value. The size F of the last RBG within the first BWP satisfies the following relationship: in, Let K be the size of the first BWP, and K be the first value.

6. The method according to claim 1, characterized in that, The at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer and the reference sub-block is configured or predefined.

7. The method according to claim 6, characterized in that, The size of the non-edge RBG in the first sub-block is P. The size of the first RBG in the first sub-block is P. The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

8. The method according to claim 7, characterized in that, The size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

9. The method according to claim 6, characterized in that, The size of the non-edge RBG in the first sub-block is P. The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information. The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

10. The method according to claim 1, characterized in that, The first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2. The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

11. The method according to claim 1, characterized in that, The first BWP includes at least one sub-block group, and any sub-block group in the at least one sub-block group includes at least one sub-block. The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

12. The method according to claim 11, characterized in that, The at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

13. The method according to claim 11 or 12, characterized in that, The third sub-block belongs to the at least one sub-block group. In the third sub-block, all RBGs except the last one are the same size, or... In the third sub-block, all RBGs except the first and last RBGs are the same size.

14. A communication method, characterized in that, include: Send a first indication message, the first indication message indicating a first virtual carrier, the first virtual carrier including at least two sub-blocks, the at least two sub-blocks corresponding one-to-one with at least two carriers, the first virtual carrier including a first portion bandwidth BWP, the first BWP mapped on at least two carriers, the size of the resource block group RBG in any sub-block of the at least two sub-blocks being associated with the at least two carriers; The first virtual carrier communicates with the terminal device based on the first indication information.

15. The method according to claim 14, characterized in that, The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of RBG in the first BWP is determined based on the size of the first BWP and a first value. The size of the first BWP is the number of resource blocks (RBs) contained in at least two sub-blocks included in the first BWP. The first value is determined based on the size of the reference sub-block, which belongs to the at least two sub-blocks. The reference sub-block is configured or predefined, or... The first value is determined based on the size of the first BWP and the first correspondence, which is the correspondence between the size of the BWP and the nominal RBG size.

16. The method according to claim 15, characterized in that, The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value. The size of the RBGs in the first BWP, excluding the last RBG, is the first value.

17. The method according to claim 15, characterized in that, The size of the first RBG within the first BWP is determined based on the starting position of the first BWP and the first value. The starting position of the first BWP is either the common resource number of the starting RB of the first BWP within the sub-block, or the common resource number of the starting RB of the first BWP within the first virtual carrier. The size of the last RBG within the first BWP is determined based on the size of the first BWP and the first value.

18. The method according to claim 17, characterized in that, The size E of the first RBG within the first BWP satisfies the following relationship: in, Let K be the starting position of the first BWP, and K be the first value. The size F of the last RBG within the first BWP satisfies the following relationship: in, Let K be the size of the first BWP, and K be the first value.

19. The method according to claim 14, characterized in that, The at least two sub-blocks include a first sub-block, the first BWP includes the first sub-block, and the size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of the RBG in the first sub-block is related to the nominal RBG size P in the reference sub-block, where P is a positive integer and the reference sub-block is configured or predefined.

20. The method according to claim 19, characterized in that, The size of the non-edge RBG in the first sub-block is P. The size of the first RBG in the first sub-block is P. The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and the P.

21. The method according to claim 20, characterized in that, The size of the last RBG in the first sub-block is obtained by modulo operation between the size of the first sub-block and P.

22. The method according to claim 19, characterized in that, The size of the non-edge RBG in the first sub-block is P. The size of the first RBG in the first sub-block is determined based on the number of the starting RB of the first sub-block in the first virtual carrier, or the size of the first RBG in the first sub-block is indicated by the first indication information. The size of the last RBG in the first sub-block is determined based on the size of the first sub-block and P, or the size of the last RBG in the first sub-block is determined based on the size of the first RBG in the first sub-block indicated by the first indication information, the size of the first sub-block, and P.

23. The method according to claim 14, characterized in that, The first BWP comprises M sub-blocks, where M is an integer greater than or equal to 2. The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The size of the RBG of any of the M sub-blocks is related to the number of RBs in the sub-block corresponding to the RBG.

24. The method according to claim 14, characterized in that, The first BWP includes at least one sub-block group, and any sub-block group in the at least one sub-block group includes at least one sub-block. The size of the resource block group (RBG) in the first BWP is related to the at least two sub-blocks, including: The RBG size of any sub-block group in the at least one sub-block group is determined based on the number of RBs included in the sub-block group corresponding to the RBG.

25. The method according to claim 24, characterized in that, The at least one sub-block group includes a first sub-block group, which includes at least two consecutive sub-blocks.

26. The method according to claim 24 or 25, characterized in that, The third sub-block belongs to the at least one sub-block group. In the third sub-block, all RBGs except the last one are the same size, or... In the third sub-block, all RBGs except the first and last RBGs are the same size.

27. A communication device, characterized in that, It includes modules or units for performing the method of any one of claims 1 to 13, or for performing the method of any one of claims 14 to 26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 13, or the method as described in any one of claims 14 to 26.

29. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 13, or the method as described in any one of claims 14 to 26.

30. A chip, characterized in that, The chip includes a processor and a communication interface. The processor reads instructions stored in the memory through the communication interface and executes the method as described in any one of claims 1 to 13, or the method as described in any one of claims 14 to 26.

Images