Beam configuration processing method and device, communication device, communication system, and medium

Abstract

Embodiments of the present disclosure provide a beam configuration processing method and device, a communication device, a communication system, and a storage medium. The method comprises: sending first information, the first information indicating a beam configuration for an access connection, the first information comprising frequency information, and the frequency information indicating a frequency domain position of a beam for the access connection. By means of the beam configuration for the access connection, the frequency domain position of the beam for the access connection can be indicated, the beam is no longer sent on the full bandwidth, the beam is sent, according to configuration requirements, at the corresponding frequency domain position, the accuracy of beam configuration is improved, interference to a signal caused by sending the beam on the full bandwidth is reduced, signal quality is improved, and the flexibility of beam configuration is also improved.

Description

Beam configuration processing method and device, communication device, communication system and medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method and device for processing beam configuration, a communication device, a communication system, and a storage medium. Background Art

[0002] A beam is the shape formed in space by electromagnetic waves emitted by an antenna. When configuring a beam, resources can be configured for the beam. Improper configuration may cause signal interference, or the configuration may be inflexible or imprecise.

[0003] Summary of the Invention

[0004] With the development of communication technology, beam configuration is becoming more and more complex, and there is a need to improve the accuracy or flexibility of beam configuration.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for processing beam configuration is provided, wherein the method includes:

[0006] Send first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0007] According to a second aspect of an embodiment of the present disclosure, a method for processing beam configuration is provided, wherein the method includes:

[0008] Receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0009] According to a third aspect of an embodiment of the present disclosure, a method for processing beam configuration is provided, wherein the method includes:

[0010] The access network device sends first information, wherein the first information indicates a beam configuration for the access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection;

[0011] The first device receives the first information.

[0012] According to a fourth aspect of an embodiment of the present disclosure, a core network device is provided, comprising:

[0013] The transceiver module is configured to send first information, wherein the first information indicates the beam configuration for the access connection, wherein the first information includes: frequency information; the frequency information indicates the frequency domain position of the beam for the access connection.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a first device is provided, comprising:

[0015] The transceiver module is configured to receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0016] According to the sixth aspect of an embodiment of the present disclosure, a communication system is provided, wherein the communication system includes a core network device and a first device; the core network device is configured to implement the method described in any one of the first aspects of the claims, and the first device is configured to implement the method described in any one of the second aspects.

[0017] According to a seventh aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the processing methods provided in the first and second aspects.

[0018] The technical solution provided by the embodiments of the present disclosure can indicate the frequency domain position of the beam of the access connection through the beam configuration of the access connection. The beam configuration is no longer sent on the full bandwidth. The beam is sent at the corresponding frequency domain position according to the configuration requirements, thereby improving the accuracy of the beam configuration, reducing the signal interference caused by sending the beam on the full bandwidth, improving the signal quality, and enhancing the flexibility of the beam configuration.

[0019] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0021] FIG1A is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0022] FIG1B is a schematic diagram showing a communication method according to an exemplary embodiment;

[0023] FIG1C is a schematic diagram showing a configuration of a beam for an access connection according to an exemplary embodiment;

[0024] FIG1D is a schematic diagram showing a configuration of a beam for an access connection according to an exemplary embodiment;

[0025] FIG1E is a schematic diagram showing a configuration of a beam for an access connection according to an exemplary embodiment;

[0026] FIG1F is a schematic diagram showing a configuration of a beam for an access connection according to an exemplary embodiment;

[0027] FIG2A is an interactive schematic diagram illustrating a method for processing beam configuration according to an exemplary embodiment;

[0028] FIG2B is an interactive schematic diagram illustrating a method for processing beam configuration according to an exemplary embodiment;

[0029] FIG3A is a schematic flow chart showing a method for processing beam configuration according to an exemplary embodiment;

[0030] FIG3B is a schematic flow chart showing a method for processing beam configuration according to an exemplary embodiment;

[0031] FIG4A is a schematic flow chart showing a method for processing beam configuration according to an exemplary embodiment;

[0032] FIG4B is a schematic flow chart showing a method for processing beam configuration according to an exemplary embodiment;

[0033] FIG5 is a schematic structural diagram of an access network device according to an exemplary embodiment;

[0034] FIG6 is a schematic structural diagram of a first device according to an exemplary embodiment;

[0035] FIG7a is a schematic structural diagram of a communication device according to an exemplary embodiment;

[0036] Fig. 7b is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0037] Embodiments of the present disclosure provide a beam configuration processing method and device, a communication device, a communication system, and a storage medium.

[0038] In a first aspect, an embodiment of the present disclosure provides a method for processing beam configuration, wherein the method includes:

[0039] First information is sent, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0040] In the above embodiment, the frequency information included in the first information indicates the frequency domain position of the beam of the access connection. The first information supports the configuration of frequency domain resources for the beam configuration of the access connection, and can allocate accurate frequency domain resources to the beam of the access connection, thereby improving the accuracy of the beam configuration of the access connection, reducing interference in beam transmission, and improving the flexibility of beam configuration.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency information includes at least one of the following:

[0042] Reference frequency;

[0043] An offset, used to determine the frequency domain starting position of the beam;

[0044] length, used to determine the amount of frequency domain resources used by the beam.

[0045] In some embodiments, the frequency information may further indicate at least one of the reference frequency point, offset, and length.

[0046] In the above embodiment, the specific position in the frequency domain and the frequency domain resource information of the beam of the access connection are determined by referring to the frequency point, offset and length, thereby improving the accuracy of the indication.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the offset includes an offset of a resource block RB, and the length includes a length of the RB;

[0048] or,

[0049] The offset includes an offset of a resource block group (RBG), and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

[0050] In the above embodiment, RBs and RBGs are configured with two different resource granularities. The resource granularity of RBs is larger than that of RBGs, which can achieve more accurate frequency domain indication and improve the accuracy of indicating the frequency domain position of the access connection beam. RBGs can reduce the amount of information in the first information while improving the accuracy of indicating the frequency domain position of the access connection beam. The frequency information only needs to indicate the offset of the RBG.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency information includes an index value.

[0052] Herein, one index value refers to one piece of frequency information or a combination of multiple pieces of frequency information.

[0053] In some embodiments, the frequency information includes an index value, wherein one of the index values ​​corresponds to at least one of:

[0054] A reference frequency;

[0055] An offset, used to determine the frequency domain starting position of the beam;

[0056] A length used to determine the amount of frequency domain resources used by the beam.

[0057] In the above embodiment, the associated frequency information can be found according to the index value in the frequency information, thereby determining the corresponding frequency domain resources, reducing the amount of the first information and saving signaling overhead.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency information includes at least one of the following:

[0059] Component Carrier (CC) identification;

[0060] Bandwidth Part (BWP) identification;

[0061] The number of the frequency band.

[0062] In the above embodiment, the beam configuration of the access connection is indicated by multiplexing information such as the carrier component CC, the bandwidth part BWP and the frequency band, without the need to use other information for indication.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes:

[0064] Set information used to indicate a resource set, wherein the set information includes resource information, one piece of resource information indicates a transmission resource in the resource set, and the resource information includes: a beam identifier and time domain information; the time domain information indicates the time domain position corresponding to the transmission resource.

[0065] In the above embodiment, by sending the first information, multiple resource information included in the set information can also be sent to achieve the configuration of the beam identifier and time domain information.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the frequency information is included in the set information, and the frequency domain position indicated by the frequency information is used for each transmission resource in the resource set.

[0067] In the above embodiment, the set information also includes frequency information. By configuring the frequency information common to each resource information in the resource set in the set information, beam configuration of each resource information in the entire set information can be achieved.

[0068] In combination with some embodiments of the first aspect, in some embodiments, the frequency information is included in the resource information, and the frequency domain position indicated by the frequency information is used for the transmission resource indicated by the resource information containing the frequency information.

[0069] In the above embodiment, frequency domain information is configured in each resource information respectively. Different resource information has different frequency domain information, which reduces the impact of the frequency domain information used for each resource transmission.

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

[0071] receiving second information, wherein the second information is used to indicate frequency capabilities of a first device associated with the access connection;

[0072] The sending of the first information includes:

[0073] The first information is sent according to the second information.

[0074] In the above embodiment, the first information is sent according to the frequency capability of the first device, which improves the matching of the beam configuration with the capability of the first device and reduces the situation where the first device does not support the configured frequency domain information.

[0075] In combination with some embodiments of the first aspect, in some embodiments, the first device is a repeater NCR controlled by the network.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, receiving the second information includes:

[0077] receiving the second information sent by a second device, wherein the second device is a management device of the first device;

[0078] or,

[0079] Receive the second information reported by the first device.

[0080] In the above embodiment, the second information may be received in different ways to obtain the frequency capability of the first device.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, when the access connection and the control connection of the first device use the same frequency band, the frequency information includes at least one of the following:

[0082] Reference frequency;

[0083] An offset, used to determine the frequency domain starting position of the beam;

[0084] length, used to determine the amount of frequency domain resources used by the beam;

[0085] Component Carrier (CC) identification;

[0086] Bandwidth Part (BWP) identification;

[0087] The number of the frequency band.

[0088] In the above embodiment, when the access connection and control connection of the first device use the same frequency band, the frequency domain position of the beam of the access connection can be indicated by the reference frequency, offset and length, or the frequency domain position of the beam of the access connection can be indicated based on the carrier component CC, bandwidth part BW and frequency band, etc., thereby increasing the way to indicate the frequency domain position of the beam of the access connection and improving the flexibility of indicating the frequency domain position of the beam of the access connection.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the access connection and the control connection of the first device use different or partially identical frequency bands, and the frequency information includes at least one of the following:

[0090] Reference frequency;

[0091] An offset, used to determine the frequency domain starting position of the beam;

[0092] length, used to determine the amount of frequency domain resources used by the beam.

[0093] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first information includes:

[0094] Send a radio resource control RRC message carrying the first information.

[0095] In the above embodiment, the first information can be sent through an RRC message, making the way of sending the first information more flexible.

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

[0097] Sending downlink control information (DCI), wherein the DCI is used to schedule aperiodic beam configuration based on the first information. Scheduling the aperiodic beam configuration based on the first information through the DCI makes the aperiodic beam configuration more efficient.

[0098] In conjunction with some embodiments of the first aspect, in some embodiments,

[0099] When the DCI is used for a control connection, the DCI is scrambled by a first scrambling sequence;

[0100] When the DCI is used for an access connection, the DCI is scrambled by a second scrambling sequence;

[0101] The second scrambling sequence is different from the first scrambling sequence.

[0102] In the above embodiment, the DCI is scrambled by using different scrambling methods to improve the security of the DCI and the security of the beam configuration.

[0103] In conjunction with some embodiments of the first aspect, in some embodiments, the beam configuration includes at least one of the following:

[0104] Periodic beam configuration;

[0105] Semi-static beam configuration;

[0106] Aperiodic beam configuration.

[0107] In a second aspect, an embodiment of the present disclosure provides a method for processing beam configuration, the method comprising:

[0108] Receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0109] In the above embodiment,

[0110] In a third aspect, an embodiment of the present disclosure provides a method for processing beam configuration, which includes:

[0111] The access network device sends first information, wherein the first information indicates a beam configuration for the access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection;

[0112] The first device receives the first information.

[0113] In a fourth aspect, an embodiment of the present disclosure provides a core network device, comprising:

[0114] The transceiver module is configured to send first information, wherein the first information indicates the beam configuration for the access connection, wherein the first information includes: frequency information; the frequency information indicates the frequency domain position of the beam for the access connection.

[0115] In a fifth aspect, an embodiment of the present disclosure provides a first device, comprising:

[0116] The transceiver module is configured to receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0117] In the sixth aspect, an embodiment of the present disclosure provides a communication system, wherein the communication system includes a core network device and a first device, the core network device is configured to implement the processing method described in the optional implementation manner of the first aspect, and the first device is configured to implement the communication method described in the optional implementation manner of the second aspect.

[0118] In a seventh aspect, an embodiment of the present disclosure provides a communication device, the communication device comprising:

[0119] one or more processors;

[0120] The processor is used to call instructions to enable the communication device to execute the processing method described in the optional implementation manner of the first aspect, the second aspect or the third aspect.

[0121] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the processing method described in the optional implementation of the first aspect, the second aspect or the third aspect.

[0122] In a ninth aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the processing method described in the optional implementation manner of the first aspect, the second aspect, or the third aspect.

[0123] In a tenth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the processing method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0124] It is understandable that the core network device, first device, communication device, communication system, storage medium, program product, and computer program are all used to perform the method provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0125] The present disclosure provides a beam configuration processing method and device, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "beam configuration processing method" are interchangeable, the terms "information indicating device" and "information processing device" are interchangeable, and the terms "communication system" and "information processing system" are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

[0137] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

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

[0139] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

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

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

[0142] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0143] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

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

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

[0148] As shown in FIG1A , a communication system 100 includes a terminal 101 , an access network device 102 , a core network device 103 , a first device 104 , and a second device 105 .

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

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

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

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

[0153] In some embodiments, the core network device 103 may be a single device including the first network element 1031, or may be multiple devices or a group of devices, each including the first network element 1031. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0154] In some embodiments, the first network element 1031 is, for example, an access and mobility management function (AMF).

[0155] In some embodiments, the first network element 1031 is, for example, a Mobility Management Entity (MME).

[0156] In some embodiments, the first network element 1031 is used for access and mobility management, such as registration management, connection management, and mobility management, etc., but the name is not limited thereto.

[0157] In some embodiments, the first network element 1031 may be a network element independent of the core network device.

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

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

[0160] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0161] Figure 1B is a communication diagram. A network controlled repeater (NCR) can improve system coverage in a low-cost manner. As shown in Figure 1B, the NCR includes two parts: the NCR mobile terminal (NCR-MT) and the NCR forwarding (NCR-Fwd). The NCR-MT is used to receive control commands sent by network equipment (such as a base station). For example, it can exchange information with the base station through a control link. The control command is used to control the behavior of the NCR-Fwd, that is, the behavior on the backhaul link and the access link, such as beam indication direction, forwarding on and off, and other control information. The NCR can be called a network controlled repeater.

[0162] Figure 1C is a schematic diagram of beam configuration for an access connection. It illustrates a periodic forwarding resource set (PFRD), including the configuration of a periodic beam indication (RBI). PFRD can periodically configure multiple resource information, each with its own identifier, such as an ID. The ID can range from 0 to 31, with a maximum of 32 IDs.

[0163] Each resource information includes a beam identifier and time domain information. The beam identifier has a range, such as 0-63, with a maximum of 64. Periodic Fwd Resource #0 represents the resource information with a resource information ID of 0, Periodic Fwd Resource #1 represents the resource information with a resource information ID of 1, and so on. Figure 1B also shows other information in the periodic forwarding resource configuration, such as the subcarrier spacing (SCS), periodicity, and priority flag.

[0164] Figure 1D illustrates a configuration diagram for a beam on an access connection, and Figure 1C illustrates a semi-persistent forwarding resource set (Semipersistent Fwd Resource Set), including the configuration of a semi-persistent beam indication. Semi-persistent forwarding resource set configuration can semi-statically configure multiple resource information, each with its own identifier, such as an ID. The ID can range from 0 to 31, with a maximum of 32 IDs.

[0165] Each resource information includes a beam identifier and time domain information. The beam identifier has a range, such as 0-63, with a maximum of 64. SemiPersistent Fwd Resource #0 represents the resource information with resource information ID 0, SemiPersistent Fwd Resource #1 represents the resource information with resource information ID 1, and so on. Figure 1D also shows other information in the semi-static forwarding resource configuration, such as the subcarrier spacing (SCS), periodicity, and priority flag.

[0166] Figure 1E is a schematic diagram of beam configuration for an access connection. Figure 1E illustrates aperiodic forwarding resource configuration (Aperiodic Fwd Config), including the configuration of an aperiodic beam indication (Aperiodic beam indication). Aperiodic forwarding resource configuration can aperiodically configure multiple resource information, each with its own aperiodic time-domain resource identifier, such as an ID. The ID can have a range, such as 0-31, with a maximum of 32.

[0167] Aperiodic Fwd Time Resource #1 represents the time domain resource information with a time domain resource ID of 1, Aperiodic Fwd Time Resource #2 represents the time domain resource information with a time domain resource ID of 2, and so on. FIG1D also shows other information in the aperiodic forwarding resource configuration, such as the subcarrier spacing (SCS) and the bit width of each beam index field in the downlink control signal DCI, such as a maximum of 6 bits. The DCI may also include the number of N time domain resources and N beam indexes.

[0168] As shown in Figures 1C through 1E above, whether for periodic beam indication, aperiodic beam indication, or semi-static beam indication, only time-domain resources are configured. The frequency-domain resources corresponding to the beams are not configured. All indicated beams are transmitted over the full NCR-Fwd bandwidth. This current configuration may cause interference and is inflexible. For example, it cannot support the beam configuration shown in Figure 1F below. Therefore, beam indication signaling needs to be enhanced.

[0169] During enhancement, the frequency domain resource size is fixed for periodic beam indications, such as synchronization signals and PBCH blocks (SSBs). For aperiodic or semi-static beam indications, such as those for dynamically scheduled user data, the frequency domain size is not fixed. Due to the non-fixed frequency domain size, it is difficult to accurately allocate frequency resources for each beam indication. Therefore, it is necessary to determine a reasonable frequency domain resource indication method for different beam indications.

[0170] FIG2A is an interactive diagram illustrating a method for processing beam configuration according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a method for processing beam configuration, which is used in a communication system 100 and includes:

[0171] S2101: Send the second information.

[0172] In some embodiments, the first device sends the second information.

[0173] In some embodiments, the first device includes but is not limited to a network controlled repeater (NCR).

[0174] In some embodiments, the first device sends the second information to the access network device.

[0175] In some embodiments, the second information is used to indicate a frequency capability of the first device associated with the access connection.

[0176] In some embodiments, the frequency capability may include: a supported frequency range, such as a supported frequency band.

[0177] In some embodiments, the first device sends a radio resource control RRC message, and the radio resource control RRC message carries the second information.

[0178] In some embodiments, the access network device receives the second information.

[0179] In some embodiments, the access network device receives the second information from a management device, for example, Operation Administration and Maintenance (OAM).

[0180] In other embodiments, the access network device receives the second information from the first device.

[0181] In some embodiments, the access network device receives terminal capability (UE Capability) information sent by the first device, where the terminal capability information includes the second information. The terminal capability information carries information indicating the terminal capability.

[0182] S2102: Send the first message.

[0183] In some embodiments, the access network device sends the first information.

[0184] In some embodiments, the access network device sends the first information to the first device.

[0185] In some embodiments, the access network device sends the first information based on the second information.

[0186] In some embodiments, the access network device sends the first information to the first device based on the second information.

[0187] In some embodiments, the access network device sends a radio resource control RRC message carrying the first information.

[0188] In some embodiments, the access network device sends a radio resource control RRC message carrying the first information via the PDSCH.

[0189] In some embodiments, the first information indicates a beam configuration for the access connection.

[0190] In some embodiments, the first information includes: frequency information.

[0191] In some embodiments, the frequency information indicates a frequency domain location of a beam for the access connection.

[0192] The frequency information included in the first information indicates the frequency domain position of the beam of the access connection. The first information supports the configuration of frequency domain resources for the beam configuration of the access connection, and can allocate precise frequency domain resources to the beam of the access connection, thereby improving the accuracy of the beam configuration of the access connection, reducing interference in beam transmission, and improving the flexibility of beam configuration.

[0193] In some embodiments, the first device receives the first information.

[0194] In some embodiments, the first device receives first information sent by the access network device.

[0195] In some embodiments, the frequency information includes at least one of the following:

[0196] Reference frequency;

[0197] An offset, used to determine the frequency domain starting position of the beam;

[0198] length, used to determine the amount of frequency domain resources used by the beam.

[0199] In some embodiments, the frequency information may further indicate at least one of the following:

[0200] Reference frequency;

[0201] An offset, used to determine the frequency domain starting position of the beam;

[0202] length, used to determine the amount of frequency domain resources used by the beam.

[0203] In some embodiments, the reference frequency point may be any frequency domain position such as the center frequency point of the cell, the starting frequency point of the cell, or the ending frequency point of the cell.

[0204] In some embodiments, the reference frequency information in the frequency information may be configured by default.

[0205] In some embodiments, when the reference frequency is the center frequency of the cell, the reference frequency in the frequency information is defaulted.

[0206] In some embodiments, the length may include the bandwidth.

[0207] The frequency domain position of the beam to be connected is indicated by the reference frequency point, offset and length, thereby improving the accuracy of indicating the frequency domain position, reducing interference between beams and facilitating improvement of signal quality.

[0208] In some embodiments, the offset comprises an offset of a resource block (RB), and the length comprises a length of a RB.

[0209] In some embodiments, the offset includes an offset of the resource block RB relative to a reference frequency point.

[0210] In some embodiments, the frequency information indicates: a frequency domain starting position of the beam determined according to an offset of the resource block RB relative to a reference frequency point.

[0211] In some embodiments, the offset includes an offset of a resource block group (RBG), and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

[0212] In some embodiments, the offset includes an offset of the resource block group RBG relative to a reference frequency point.

[0213] In some embodiments, the frequency information indicates: a frequency domain starting position of the beam determined according to an offset of the resource block group RBG relative to a reference frequency point.

[0214] In some embodiments, the length may include the length occupied by the resource block (RB) starting from the starting position of the beam in the frequency domain.

[0215] In some embodiments, the length may include the length occupied by the resource block group RBG starting from the frequency domain starting position of the beam.

[0216] In some embodiments, a resource block group RBG includes an even number of RB resource blocks.

[0217] RBs and RBGs are configurations of two different resource granularities. The resource granularity of RBs is larger than that of RBGs, which can achieve more accurate frequency domain indication, thereby improving the accuracy of indicating the frequency domain position of the access connection beam. RBGs can reduce the amount of information in the first information while improving the accuracy of indicating the frequency domain position of the access connection beam. The frequency information only indicates the offset of the RBG.

[0218] For example, one RBG may include 2, 4, 6 or 8 RBs, etc.

[0219] In some embodiments, the frequency information includes an index value; one index value refers to one piece of frequency information.

[0220] The associated frequency information can be found according to the index value in the frequency information, thereby determining the corresponding frequency domain resources. The amount of information of the index value is much smaller than the amount of information of a frequency information, so the amount of information of the first information can be reduced, saving signaling overhead.

[0221] In some embodiments, one of the index values ​​corresponds to at least one of:

[0222] A reference frequency;

[0223] An offset, used to determine the frequency domain starting position of the beam;

[0224] A length used to determine the amount of frequency domain resources used by the beam.

[0225] In some embodiments, an index value refers to a combination of any two of a reference frequency point, an offset, and a length.

[0226] Exemplarily, the correspondence between the index value and the frequency information is pre-configured to the terminal through an RRC message; or the correspondence between the index value and the frequency information is known in advance according to a protocol agreement.

[0227] In this way, the frequency information in the first information is index information, which can save signaling overhead.

[0228] In some embodiments, the combination of multiple frequency information may include: a reference frequency point, an offset, and a length.

[0229] In some embodiments, the combination of multiple frequency information may include: a reference frequency point and a length.

[0230] In some embodiments, the combination of multiple frequency information may include: a reference frequency point and an offset.

[0231] In some embodiments, the combination of multiple frequency information may include: a length and an offset.

[0232] In some embodiments, different index values ​​refer to different combinations of frequency information.

[0233] For example, index value 1 refers to the combination of reference frequency point 1, offset 1 and length 1, and index value 2 refers to the combination of reference frequency point 2, offset 2 and length 2.

[0234] The combination of multiple index values ​​and the multiple frequency information indicated by each index value may be in the form of a table.

[0235] In some embodiments, the frequency information includes at least one of the following:

[0236] Component Carrier (CC) identification;

[0237] Bandwidth Part (BWP) identification;

[0238] The number of the frequency band.

[0239] The carrier component CC, bandwidth part BWP and frequency band are frequency domain resources that have been configured in wireless communication, and these resources are all configured with identifiers. Reusing the identifiers of CC, BWP or frequency band as the aforementioned frequency information does not require configuring dedicated identifiers, which has the characteristic of simple implementation.

[0240] In some embodiments, the first information includes:

[0241] Set information used to indicate a resource set, wherein the set information includes resource information, one piece of resource information indicates a transmission resource in the resource set, and the resource information includes: a beam identifier and time domain information; the time domain information indicates the time domain position corresponding to the transmission resource.

[0242] 1C to 1E , the set information may include a periodic forwarding resource set (Periodic Fwd Resource Set) shown in FIG. 1C , a semi-persistent forwarding resource set (Semipersistent Fwd Resource Set) shown in FIG. 1D , and an aperiodic forwarding resource configuration (Aperiodic Fwd Config) shown in FIG. 1E .

[0243] The periodic forwarding resource configuration (Periodic Fwd Resource Set) shown in Figure 1C represents set information, indicating a resource set. Periodic Fwd Resource#0 and Periodic Fwd Resource#1, etc., respectively represent resource information, contained in the set information represented by the periodic forwarding resource configuration (Periodic Fwd Resource Set). Periodic Fwd Resource#0 indicates periodic forwarding resource #0, and Periodic Fwd Resource#1 indicates periodic forwarding resource #1. Periodic Fwd Resource#0 and Periodic Fwd Resource#1 respectively include a beam identifier and time domain information. The time domain information indicates the time domain position of the corresponding transmission resource, such as the slot offset, symbol offset, and symbol length.

[0244] The semi-persistent forwarding resource configuration (Semipersistent Fwd Resource Set) shown in Figure 1D represents set information, indicating a resource set. SemiPersistent Fwd Resource#0 and SemiPersistent Fwd Resource#1, etc. respectively represent resource information, which is included in the set information represented by the semi-persistent forwarding resource configuration (Semipersistent Fwd Resource Set). SemiPersistent Fwd Resource#0 indicates semi-persistent forwarding resource #0, and SemiPersistent Fwd Resource#1 indicates semi-persistent forwarding resource #1. SemiPersistent Fwd Resource#0 and SemiPersistent Fwd Resource#1 respectively include beam identifiers and time domain information. Time domain information indicates the time domain position of the corresponding transmission resource, such as slot offset, symbol offset, and symbol length.

[0245] The aperiodic forwarding resource configuration (Aperiodic Fwd Config) shown in Figure 1E represents set information, indicating a resource set. Aperiodic Fwd Time Resource#1 and Aperiodic Fwd Time Resource#2, etc., respectively represent resource information, which is included in the set information represented by the aperiodic forwarding resource configuration (Aperiodic Fwd Config). Aperiodic Fwd Time Resource#1 indicates aperiodic forwarding resource Resource#1, and Aperiodic Fwd Time Resource#2 indicates aperiodic forwarding resource Resource#2. Each piece of resource information such as Aperiodic Fwd Time Resource#1 and Aperiodic Fwd Time Resource#2 includes time domain information. The time domain information indicates the time domain position of the corresponding transmission resource, such as the slot offset, symbol offset, and symbol length.

[0246] In some embodiments, the frequency information is included in the set information; the frequency domain position indicated by the frequency information is used for each transmission resource in the resource set.

[0247] Frequency domain information is added to the aggregate information shown in Figures 1C and 1D. Specifically, the aggregate information includes frequency domain information, which is shared by the transmission resources indicated by each piece of resource information in the aggregate information. This frequency domain information is valid for beam configuration of each piece of resource information within the aggregate information. A single piece of frequency domain information can be used to configure the frequency domain information of each resource within the aggregate information. This reduces the amount of information in the first information while enabling frequency domain resource configuration, thereby reducing signaling overhead.

[0248] In some embodiments, the frequency information is included in the resource information; the frequency domain position indicated by the frequency information is used for the transmission resource indicated by the resource information including the frequency information.

[0249] Frequency domain information is added to the resource information Periodic Fwd Resource #0, SemiPeriodic Fwd Resource #0, and Aperiodic Fwd Time Resource #1 shown in Figures 1C and 1D. Each resource information includes a frequency domain information. The frequency domain information included in each resource information is valid for the beam configuration of the resource information to which it belongs. This improves the accuracy of the frequency domain position of the beam for the access connection, reduces interference between the frequency domain positions of the beams corresponding to the different resource information, improves signal transmission quality, and increases the flexibility of beam configuration.

[0250] In some embodiments, when the access connection and the control connection of the first device use the same frequency band, the frequency information includes at least one of the following:

[0251] Reference frequency;

[0252] An offset, used to determine the frequency domain starting position of the beam;

[0253] length, used to determine the amount of frequency domain resources used by the beam;

[0254] Component Carrier (CC) identification;

[0255] Bandwidth Part (BWP) identification;

[0256] The number of the frequency band.

[0257] In some embodiments, when the access connection and the control connection of the first device use the same frequency band, the frequency information includes at least one of the following:

[0258] Reference frequency;

[0259] An offset, used to determine the frequency domain starting position of the beam;

[0260] length, used to determine the amount of frequency domain resources used by the beam;

[0261] and / or,

[0262] The frequency information indicates at least one of the following:

[0263] Component Carrier (CC) identification;

[0264] Bandwidth Part (BWP) identification;

[0265] The number of the frequency band.

[0266] The access connection and control connection of the first device use the same or different frequency bands. The access connection is the connection between the first device and the UE. The control connection is the connection between the access network device and the first device.

[0267] If the access connection between the first device and the UE uses frequency band 1, and the control connection between the first device and the access network device also uses frequency band 1, the first device supports in-band communication with the access network device. In this way, the reference frequency, offset, and length can be used to indicate the frequency domain information of the beam of the access connection, and the frequency domain resources used by the first device, such as the carrier component CC, bandwidth part BWP, and frequency band number, can be reused for in-band communication.

[0268] In some embodiments, when the frequency bands used by the access connection and the control connection of the first device are different or partially the same, the frequency information includes at least one of the following:

[0269] Reference frequency;

[0270] An offset, used to determine the frequency domain starting position of the beam;

[0271] length, used to determine the amount of frequency domain resources used by the beam.

[0272] The above steps S2101 and S2102 may be used for periodic or semi-static beam configuration.

[0273] In some embodiments, the term "send" can be interchanged with terms such as "transmit", "report", and "transmit".

[0274] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 can be implemented as an independent embodiment, where the first device sends the second information indicating the frequency capability of the first device. Step S2102 can also be implemented as an independent embodiment, where the first information can be sent to the first device.

[0275] In some embodiments, based on the processing method shown in Figure 2A, Figure 2B is an interactive schematic diagram of a beam configuration processing method according to an embodiment of the present disclosure. As shown in Figure 2B, the embodiment of the present disclosure relates to a beam configuration processing method for communication system 100. In addition to S2101 and S2102, the method further includes:

[0276] S2103: Send downlink control information DCI; wherein, the DCI is used to perform non-periodic beam configuration scheduling based on the first information.

[0277] That is, the method includes:

[0278] S2101: Send the second information.

[0279] S2102: Sending the first information. For the corresponding contents of S2101 and S2102, please refer to the contents described in FIG2A and will not be repeated here.

[0280] S2103: Send downlink control information DCI.

[0281] In some embodiments, the access network device sends downlink control information DCI.

[0282] In some embodiments, the access network device sends downlink control information DCI to the first device.

[0283] In some embodiments, when the DCI is for a control connection, the DCI is scrambled by a first scrambling sequence;

[0284] When the DCI is used for an access connection, the DCI is scrambled by a second scrambling sequence;

[0285] The second scrambling sequence is different from the first scrambling sequence.

[0286] In some embodiments, the DCI is used at least for scheduling of a control connection, and the first scrambling sequence may include but is not limited to a cell radio network temporary identifier (Cell-RNTI). Scheduling of the control connection by the DCI includes but is not limited to beam scheduling.

[0287] In some embodiments, the DCI is at least used for beam scheduling of the access connection, and the second scrambling sequence may include but is not limited to a Controlled Repeater Radio Network Temporary Identifier (CR-RNTI) of a repeater controlled by the network.

[0288] Scrambling DCI can improve the security of DCI transmission and thus the security of beam configuration. Scrambling DCI for different purposes with different scrambling sequences can reduce the possibility of DCI being misinterpreted and scrambled.

[0289] The scrambling sequences of DCI for different connections are different, which makes it convenient for the first device to determine the connection for which the currently received DCI is targeted according to the descrambling sequence, thereby reducing signaling overhead.

[0290] In some embodiments, DCI is also used for resource scheduling of any other connections.

[0291] In some embodiments, the control connection is a control connection between the access network device and the first device.

[0292] In some embodiments, the DCI includes a control command;

[0293] In some embodiments, the DCI includes a control command sent by the base station, where the control command is used to control the first device to perform non-periodic beam configuration scheduling based on the first information.

[0294] The above steps S2101 to S2103 may be used for non-periodic beam configuration.

[0295] In some embodiments, step S2101 may be implemented as an independent embodiment, and the first device may send the second information to indicate the frequency capability of the first device.

[0296] In some embodiments, step S2102 may be implemented as an independent embodiment, and it is sufficient to send the first information to the first device.

[0297] In some embodiments, step S2101 may be used as a default step, and step S2102 and step S2103 may be implemented as independent embodiments, as long as the first information and the DCI can be sent.

[0298] In some embodiments, the beam configuration includes at least one of the following:

[0299] Periodic beam configuration;

[0300] Semi-static beam configuration;

[0301] Aperiodic beam configuration.

[0302] Due to the periodic beam configuration and semi-static beam configuration, the frequency domain information is bound to the beam information once configured, and can be executed according to the configuration information without the need for DCI scheduling.

[0303] Aperiodic beam configuration is also called dynamic beam configuration. Dynamic beam configuration is used for temporary or sudden transmission needs and is therefore irregular. After frequency domain information is configured via RRC messages, DCI is used to schedule the configured frequency domain information and beams. The scheduled beams are then used for aperiodic transmissions.

[0304] Exemplarily, if the DCI carries the beam identifier of a beam in the first information, it means that the DCI schedules the beam.

[0305] As another example, the DCI includes a bit map, in which a bit may correspond to a beam or a beam combination. The beam corresponding to the bit with the first value in the bit map is scheduled, and the other beams are not scheduled, thereby realizing dynamic scheduling of one or more beams among the multiple beams configured with the first information through the DCI.

[0306] Using DCI for beam scheduling is characterized by good dynamics and high timeliness.

[0307] In some embodiments, the wireless resource control RRC message carries first information, the first information includes frequency information and resource information, the frequency information includes frequency domain information, the frequency domain information is included in the resource information, and the periodic beam configuration can be achieved through the wireless resource control RRC message. The RRC message indicates the frequency domain resources of the periodic beam.

[0308] Based on Figure 1C, frequency domain information is added to each resource information pair. The resource information includes frequency domain information, time domain information, and beam identifiers. Each resource information pair indicates the frequency domain position through the frequency domain information it contains. This improves the accuracy of the frequency domain position of the periodic beam for the access connection, reduces interference between the frequency domain positions of the beams corresponding to each resource information pair, improves signal transmission quality, and increases the flexibility of beam configuration.

[0309] In some embodiments, the wireless resource control RRC message carries first information, the first information includes frequency information, resource information and collection information, the frequency information includes frequency domain information, the resource information and frequency domain information are included in the collection information, the RRC message indicates the frequency domain resources of the periodic beam, and the frequency domain resource configuration of the periodic beam can be achieved through the wireless resource control RRC message.

[0310] This frequency domain information is shared by all transmission resources indicated by each resource information in the aggregate information. This single frequency domain information can be used to configure the frequency domain information for each resource within the aggregate information. This frequency domain information is valid for the periodic beams of each resource in the aggregate information. While configuring the frequency domain resources, it also reduces the amount of information contained in the first information, thereby reducing signaling overhead.

[0311] In some embodiments, the RRC message indicates the frequency domain resources of the semi-static beam.

[0312] Based on Figure 1D, frequency domain information is added to each resource information pair. The resource information includes frequency domain information, time domain information, and beam identifiers. Each resource information pair indicates the frequency domain position through the frequency domain information it contains. This improves the accuracy of the frequency domain position of the semi-static beam for the access connection, reduces interference between the frequency domain positions of the beams corresponding to each resource information pair, improves signal transmission quality, and increases the flexibility of semi-static beam configuration.

[0313] In some embodiments, the wireless resource control RRC message carries first information, the first information includes frequency information, resource information and collection information, the frequency information includes frequency domain information, the resource information and frequency domain information are included in the collection information, the RRC message indicates the frequency domain resources of the semi-static beam, and the frequency domain resource configuration of the semi-static beam can be achieved through the wireless resource control RRC message.

[0314] In some embodiments, the RRC message indicates the frequency domain resources of the non-periodic beam, and the non-periodic beam configuration scheduling is performed based on the first information through DCI.

[0315] When the DCI is used for a control connection, the DCI uses a first scrambling sequence; when the DCI is used for an access connection, the DCI uses a second scrambling sequence; the second scrambling sequence is different from the first scrambling sequence.

[0316] The terms "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", "data" and so on are interchangeable.

[0317] FIG3A is an interactive diagram illustrating a method for processing beam configuration according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a method for processing beam configuration, which is used in an access network device and includes:

[0318] S3101: Receive the second information.

[0319] In some embodiments, the access network device receives the second information.

[0320] In some embodiments, the access network device receives the second information sent by the first device.

[0321] In some embodiments, the first device includes but is not limited to a network controlled repeater (NCR).

[0322] In some embodiments, the access network device receives second information sent by a second device, where the second device is a management device of the first device.

[0323] In some embodiments, the second device includes but is not limited to an Operation Administration and Maintenance (OAM) device.

[0324] In some embodiments, the access network device receives terminal capability (UE Capability) information sent by the first device, where the terminal capability information includes the second information. The terminal capability information carries information indicating the terminal capability.

[0325] In some embodiments, the second information is used to indicate a frequency capability of the first device associated with the access connection.

[0326] In some embodiments, the frequency capability may include: a supported frequency range, such as a supported frequency band.

[0327] In some embodiments, the access network device receives a radio resource control RRC message, where the radio resource control RRC message carries the second information.

[0328] S3102: Send the first message.

[0329] In some embodiments, the access network device sends the first information.

[0330] In some embodiments, the access network device sends the first information to the first device.

[0331] In some embodiments, the access network device sends the first information based on the second information.

[0332] In some embodiments, the access network device sends the first information to the first device based on the second information.

[0333] In some embodiments, the access network device sends a radio resource control RRC message carrying the first information.

[0334] In some embodiments, the access network device sends a radio resource control RRC message carrying the first information via the PDSCH.

[0335] In some embodiments, the first information indicates a beam configuration for the access connection.

[0336] In some embodiments, the first information includes: frequency information.

[0337] In some embodiments, the frequency information indicates a frequency domain location of a beam for the access connection.

[0338] The frequency information included in the first information indicates the frequency domain position of the beam of the access connection. The first information supports the configuration of frequency domain resources for the beam configuration of the access connection, and can allocate precise frequency domain resources to the beam of the access connection, thereby improving the accuracy of the beam configuration of the access connection, reducing interference in beam transmission, and improving the flexibility of beam configuration.

[0339] In some embodiments, the frequency information includes at least one of the following:

[0340] Reference frequency;

[0341] An offset, used to determine the frequency domain starting position of the beam;

[0342] length, used to determine the amount of frequency domain resources used by the beam.

[0343] In some embodiments, the reference frequency point may be any frequency domain position such as the center frequency point of the cell, the starting frequency point of the cell, or the ending frequency point of the cell.

[0344] In some embodiments, the reference frequency information in the frequency information may be configured by default.

[0345] In some embodiments, when the reference frequency is the center frequency of the cell, the reference frequency in the frequency information is defaulted.

[0346] In some embodiments, the length may include the bandwidth.

[0347] The frequency domain position of the beam to be connected is indicated by the reference frequency point, offset and length, thereby improving the accuracy of indicating the frequency domain position, reducing interference between beams and facilitating improvement of signal quality.

[0348] In some embodiments, the offset comprises an offset of a resource block (RB), and the length comprises a length of a RB.

[0349] In some embodiments, the offset includes an offset of the resource block RB relative to a reference frequency point.

[0350] In some embodiments, the frequency information indicates: a frequency domain starting position of the beam determined according to an offset of the resource block RB relative to a reference frequency point.

[0351] In some embodiments, the offset includes an offset of a resource block group (RBG), and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

[0352] In some embodiments, the offset includes an offset of the resource block group RBG relative to a reference frequency point.

[0353] In some embodiments, the frequency information indicates: a frequency domain starting position of the beam determined according to an offset of the resource block group RBG relative to a reference frequency point.

[0354] In some embodiments, the length may include the length occupied by the resource block (RB) starting from the starting position of the beam in the frequency domain.

[0355] In some embodiments, the length may include the length occupied by the resource block group RBG starting from the frequency domain starting position of the beam.

[0356] In some embodiments, a resource block group RBG includes an even number of RB resource blocks.

[0357] RBs and RBGs are configurations of two different resource granularities. The resource granularity of RBs is larger than that of RBGs, which can achieve more accurate frequency domain indication, thereby improving the accuracy of indicating the frequency domain position of the access connection beam. RBGs can reduce the amount of information in the first information while improving the accuracy of indicating the frequency domain position of the access connection beam. The frequency information only indicates the offset of the RBG.

[0358] In some embodiments, the frequency information includes an index value; one index value refers to one piece of frequency information.

[0359] The associated frequency information can be found according to the index value in the frequency information, thereby determining the corresponding frequency domain resources. The amount of information of the index value is much smaller than the amount of information of a frequency information, so the amount of information of the first information can be reduced, saving signaling overhead.

[0360] In some embodiments, one of the index values ​​corresponds to at least one of:

[0361] A reference frequency;

[0362] An offset, used to determine the frequency domain starting position of the beam;

[0363] A length used to determine the amount of frequency domain resources used by the beam.

[0364] In some embodiments, an index value refers to a reference frequency point.

[0365] In some embodiments, an index value refers to an offset, or refers to the frequency domain starting position of a beam.

[0366] In some embodiments, an index value refers to a length, or refers to the amount of frequency domain resources used by the beam.

[0367] In some embodiments, one index value refers to a combination of multiple frequency information.

[0368] According to the index value in the frequency information, the combination of multiple associated frequency information can be found to determine the corresponding frequency domain resources. The amount of information of the index value is much smaller than the amount of information of the combination of multiple specific frequency information. This reduces the amount of information of the first information and saves signaling overhead.

[0369] In some embodiments, the combination of multiple frequency information may include: a reference frequency point, an offset, and a length.

[0370] In some embodiments, the combination of multiple frequency information may include: a reference frequency point and a length.

[0371] In some embodiments, the combination of multiple frequency information may include: a reference frequency point and an offset.

[0372] In some embodiments, the combination of multiple frequency information may include: a length and an offset.

[0373] In some embodiments, different index values ​​refer to different combinations of frequency information.

[0374] For example, index value 1 refers to the combination of reference frequency point 1, offset 1 and length 1, and index value 2 refers to the combination of reference frequency point 2, offset 2 and length 2.

[0375] The combination of multiple index values ​​and the multiple frequency information indicated by each index value may be in the form of a table.

[0376] In some embodiments, the frequency information includes at least one of the following:

[0377] The identification of the carrier component CC;

[0378] The identification of the bandwidth part BWP;

[0379] The number of the frequency band.

[0380] The carrier component CC, bandwidth part BWP and frequency band are the frequency domain resource information used by the first device, and the frequency domain resources used by the first device in the existing protocol are reused. There is no need to use other information to indicate the frequency domain position of the beam of the access connection, saving signaling overhead.

[0381] In some embodiments, the first information includes:

[0382] Set information used to indicate a resource set, wherein the set information includes resource information, one piece of resource information indicates a transmission resource in the resource set, and the resource information includes: a beam identifier and time domain information; the time domain information indicates the time domain position corresponding to the transmission resource.

[0383] The above steps S3101 and S3102 can be used for periodic or semi-static beam configuration. Due to the periodic beam configuration and semi-static beam configuration, the frequency domain information is bound to the beam information once configured, and can be executed according to the configuration information without the need for DCI scheduling.

[0384] FIG3B is an interactive diagram illustrating a method for processing beam configuration according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a method for processing beam configuration, which is used in an access network device and includes:

[0385] S3101: Receive the second information.

[0386] S3102: Send the first message.

[0387] S3103: Send DCI.

[0388] For the corresponding information of S3101 and S3102, please refer to the content in the embodiment shown in Figure 3A.

[0389] In some embodiments, the access network device sends downlink control information DCI.

[0390] In some embodiments, the access network device sends downlink control information DCI to the first device.

[0391] In some embodiments, the first device receives the DCI.

[0392] In some embodiments, the first device receives DCI sent by the access network device.

[0393] In some embodiments, the DCI is used at least for beam scheduling of a control connection, and the first scrambling sequence may include but is not limited to a cell radio network temporary identifier (Cell-RNTI). The scheduling of the control connection by the DCI includes but is not limited to beam scheduling.

[0394] In some embodiments, the DCI is at least used for beam scheduling of the access connection, and the second scrambling sequence may include but is not limited to a Network Controlled Repeater Radio Network Temporary Identifier (NCR-RNTI) of a network-controlled repeater.

[0395] The scrambling sequences of DCI for different connections are different, which makes it convenient for the first device to determine the connection for which the currently received DCI is targeted according to the descrambling sequence, thereby reducing signaling overhead.

[0396] In some embodiments, DCI is also used for resource scheduling of any other connections.

[0397] Scrambling DCI can improve the security of DCI transmission and thus the security of beam configuration. Scrambling DCI for different purposes with different scrambling sequences can reduce the possibility of DCI being misinterpreted and scrambled.

[0398] The above steps S3201 to S3203 may be used for non-periodic beam configuration.

[0399] In some embodiments, step S3201 can be used as a default step, and the access network device only needs to send the first information and DCI.

[0400] Aperiodic beam configuration is also called dynamic beam configuration. Dynamic beam configuration is used for temporary or sudden transmission needs and is therefore irregular. After frequency domain information is configured via RRC messages, DCI is used to schedule the configured frequency domain information and beams. The scheduled beams are then used for aperiodic transmissions.

[0401] Exemplarily, if the DCI carries the beam identifier of a beam in the first information, it means that the DCI schedules the beam.

[0402] As another example, the DCI includes a bit map, in which a bit may correspond to a beam or a beam combination. The beam corresponding to the bit with the first value in the bit map is scheduled, and the other beams are not scheduled, thereby realizing dynamic scheduling of one or more beams among the multiple beams configured with the first information through the DCI.

[0403] Using DCI for beam scheduling is characterized by good dynamics and high timeliness.

[0404] FIG4A is a flow chart of a method for processing beam configuration according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a communication method, which is executed by a first device and includes:

[0405] S4101: Send the second information.

[0406] In some embodiments, the first device sends the second information.

[0407] In some embodiments, the first device includes but is not limited to a network controlled repeater (NCR).

[0408] In some embodiments, the first device sends the second information to the access network device.

[0409] In some embodiments, the second information is used to indicate a frequency capability of the first device associated with the access connection.

[0410] In some embodiments, the frequency capability may include: a supported frequency range, such as a supported frequency band.

[0411] In some embodiments, the first device sends a radio resource control RRC message, and the radio resource control RRC message carries the second information.

[0412] S4102: Receive first information.

[0413] In some embodiments, the first device receives the first information.

[0414] In some embodiments, the first device receives first information sent by the access network device.

[0415] In some embodiments, the first network device receives a radio resource control RRC message carrying the first information.

[0416] In some embodiments, the first network device receives a radio resource control RRC message carrying the first information through the PDSCH.

[0417] In some embodiments, the first information indicates a beam configuration for the access connection.

[0418] In some embodiments, the first information includes: frequency information.

[0419] In some embodiments, the frequency information indicates a frequency domain location of a beam for the access connection.

[0420] The frequency information included in the first information indicates the frequency domain position of the beam of the access connection. The first information supports the configuration of frequency domain resources for the beam configuration of the access connection, and can allocate precise frequency domain resources to the beam of the access connection, thereby improving the accuracy of the beam configuration of the access connection, reducing interference in beam transmission, and improving the flexibility of beam configuration.

[0421] The above steps S4101 to S4102 can be used for periodic or semi-static beam configuration. Since the frequency domain information of periodic beam configuration and semi-static beam configuration is bound to the beam information once configured, it can be executed according to the configuration information without DCI scheduling.

[0422] FIG4B is a flow chart of a method for processing beam configuration according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a communication method, which is executed by a first device and includes:

[0423] S4101: Send the second information.

[0424] S4102: Receive first information.

[0425] S4103: Receive downlink control information DCI, DCI, used to perform non-periodic beam configuration scheduling based on the first information.

[0426] In some embodiments, the first device receives downlink control information DCI.

[0427] For the corresponding contents of S4101 and S4102, please refer to Figure 4A.

[0428] In some embodiments, the DCI is descrambled using a first scrambling sequence, wherein the DCI is used to control the connection;

[0429] descrambling the DCI using a second scrambling sequence, wherein the DCI is used for an access connection;

[0430] The second scrambling sequence is different from the first scrambling sequence.

[0431] In some embodiments, after receiving the DCI, the DCI is successfully descrambled using the first scrambling sequence, indicating that the DCI is used for the control connection, and beam scheduling of the control connection can be performed through the DCI.

[0432] In some embodiments, after receiving the DCI, the DCI is successfully descrambled using the second scrambling sequence, indicating that the DCI is used for the access connection, and beam scheduling of the access connection can be performed through the DCI.

[0433] In some embodiments, the first scrambling sequence may include but is not limited to a cell radio network temporary identifier (Cell-RNTI).

[0434] In some embodiments, the second scrambling sequence may include but is not limited to a Network Controlled Repeater Radio Network Temporary Identifier (NCR-RNTI) of a network controlled repeater.

[0435] In some embodiments, DCI scheduling for control connections includes but is not limited to beam scheduling. The scrambling sequences of DCI for different connections are different, which facilitates the first device to determine the connection for which the currently received DCI is targeted based on the descrambling sequence, thereby reducing signaling overhead.

[0436] In some embodiments, DCI is also used for resource scheduling of any other connections.

[0437] The above steps S4101 to S4102 may be used for non-periodic beam configuration.

[0438] Aperiodic beam configuration is also called dynamic beam configuration. Dynamic beam configuration is used for temporary or sudden transmission needs and is therefore irregular. After frequency domain information is configured via RRC messages, DCI is used to schedule the configured frequency domain information and beams. The scheduled beams are then used for aperiodic transmissions.

[0439] Exemplarily, if the DCI carries the beam identifier of a beam in the first information, it means that the DCI schedules the beam.

[0440] As another example, the DCI includes a bit map, in which a bit may correspond to a beam or a beam combination. The beam corresponding to the bit with the first value in the bit map is scheduled, and the other beams are not scheduled, thereby realizing dynamic scheduling of one or more beams among the multiple beams configured with the first information through the DCI.

[0441] Using DCI for beam scheduling is characterized by good dynamics and high timeliness.

[0442] In some embodiments, S4101 is optional, and S4102 and S4103 can be used as independent embodiments, and the scheduled beam configuration can be received after receiving the first information and receiving the DCI.

[0443] In some embodiments, S4103 is optional, or both S4101 and S4103 are optional, and S4102 is an independent embodiment that only needs to receive the first information.

[0444] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0445] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0446] In some embodiments, frequency domain resource indication is supported for the beam position of the access connection of the NCR.

[0447] In some embodiments, the indication of the frequency domain resource includes at least one of the following:

[0448] Option 1: Directly indicate frequency resource information, where the indication content includes at least one of the following:

[0449] {reference frequency, RB offset, RB length}.

[0450] In some embodiments, the test frequency point may be a default value, in which case the center frequency is a predefined value, such as the center frequency of the cell where the NCR-MT is located.

[0451] In some embodiments, the RB offset and RB length may also be understood as frequency location and bandwidth.

[0452] In some embodiments, the RB offset and RB length may be defined through an RRC table and directly indicated through an index value index in the table in the beam indication configuration.

[0453] In some embodiments, the reference frequency, RB offset and RB length can all be determined in the form of a table through a radio resource control RRC message (i.e., each index value index in the table corresponds to a combination of a reference frequency, RB offset and RB length), and directly indicated by the index value index in the table in the beam indication configuration.

[0454] In some embodiments, the resource block RB may also be replaced by other frequency domain resource units, such as a resource block group RBG.

[0455] In some embodiments, 1RBG=2RB.

[0456] In some embodiments, the base station configures multiple groups of frequency resources for non-periodic beam indication through RRC messages, such as through the parameter AperiodicFwdFreqResource (refer to Figure 1E), each group includes {reference frequency, RB offset, RB length} and corresponds to an ID. When the base station indicates the non-periodic beam through DCI, the ID is included in the DCI.

[0457] In some embodiments, the base station configures frequency resources for periodic / semi-static beam indication via RRC, and directly includes: reference frequency, RB offset, and RB length in the RRC parameters.

[0458] Option 2: Reuse the frequency domain resource definitions used by UE / NCR-MT in existing protocols, such as BWP and component carrier (CC).

[0459] For example, the base station configures four dedicated BWPs for NCR-MT. In this case, the side control information is carried by DCI format 2-8, which is transmitted on BWP#2. The frequency domain resource of the beam indicated in the DCI is BWP#1.

[0460] For example, the base station configures three serving cells for the NCR-MT, and indicates in the access link periodic forwarding resource set configuration that the frequency domain resource of the beam is CC#2.

[0461] In some embodiments, before performing frequency domain configuration, the base station needs to know the frequency domain capability of the NCR in advance. This information can be obtained in one of the following two ways:

[0462] Method 1: The network indicates the frequency capabilities of NCR-Fwd and / or NCR-MT to the NCR and base stations through the Operation Administration and Maintenance (OAM) equipment.

[0463] Method 2: The NCR reports its frequency capabilities to the base station through the UE capabilities.

[0464] Regarding the frequency domain resource indication content, the method of Option 2 is applicable to NCRs that support in-band communication with access network devices, but cannot be used for NCRs that support out-band communication. The method of Option 1 is applicable to NCRs that support both in-band and out-band communication with access network devices.

[0465] The above method can also be applied to devices such as RIS.

[0466] In some embodiments, beam configuration includes: for periodic beam indication

[0467] For example, a new RRC parameter is added to indicate the frequency domain resource of a periodic beam. This parameter is included in periodicFwdResourceSet → PeriodicFwdResource → Frequency resource. In this case, the frequency domain resource is valid for each beam index. See Figure 1C.

[0468] For another example, a new RRC parameter is added to indicate the frequency domain resources of a periodic beam. This parameter is included in periodicFwdResourceSet. In this case, the frequency domain resources are valid for each resource set, that is, multiple beam indices.

[0469] In some embodiments, beam configuration includes: for semi-static beam indication

[0470] For example, a new RRC parameter is added to indicate the frequency domain resource of a semi-persistent beam. This parameter is included in SemiPersistentFwdResourceSet → SemiPersistentFwdResource → Frequency resource. In this case, the frequency domain resource is valid for each beam index. See Figure 1D.

[0471] For example, a new RRC parameter is added to indicate the frequency domain resources of a periodic beam. This parameter is included in SemiPersistentFwdResourceSet. In this case, the frequency domain resources are valid for each resource set, that is, multiple beam indices. See Figure 1E.

[0472] In some embodiments, for non-periodic beam indication

[0473] A new RRC parameter is added to indicate the frequency domain resource for aperiodic beams. This parameter is included in AperiodicFwdResource → AperiodicFwdFreqResource, and the frequency domain resource ID is further indicated through downlink control information (DCI) scrambled by NCR-RNTI. The DCI contains N frequency domain resources, which correspond one-to-one with N time domain resources and N beam IDs.

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

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

[0476] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0477] FIG5 is a schematic structural diagram of an access network device provided by an embodiment of the present disclosure, wherein the access network device includes:

[0478] The transceiver module 501 is configured to send first information, wherein the first information indicates the beam configuration for the access connection, wherein the first information includes: frequency information; the frequency information indicates the frequency domain position of the beam for the access connection.

[0479] Optionally, the frequency information indicates at least one of the following:

[0480] Reference frequency;

[0481] An offset, used to determine the frequency domain starting position of the beam;

[0482] length, used to determine the amount of frequency domain resources used by the beam.

[0483] Optionally, the offset includes an offset of a resource block RB, and the length includes a length of the RB;

[0484] or,

[0485] The offset includes an offset of a resource block group (RBG), and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

[0486] Optionally, the frequency information includes an index value,

[0487] Herein, one index value refers to one piece of frequency information or a combination of multiple pieces of frequency information.

[0488] Optionally, the frequency information includes at least one of the following:

[0489] The identification of the carrier component CC;

[0490] The identification of the bandwidth part BWP;

[0491] The number of the frequency band.

[0492] Optionally, the first information includes:

[0493] Collection information, indicating resource collection;

[0494] Resource information is included in the set information, and one piece of resource information indicates a transmission resource, and the resource information includes: a beam identifier and time domain information; the time domain information indicates the time domain position corresponding to the transmission resource.

[0495] Optionally, the frequency domain information is included in the set information;

[0496] The frequency domain information indicates a frequency domain position, which is used for each resource in the resource set.

[0497] Optionally, the frequency domain information is included in the resource information;

[0498] Among them, one frequency domain position indicated by the frequency domain information is used for one transmission resource.

[0499] Optionally, the transceiver module 501 is configured to receive second information, wherein the second information is used to indicate the frequency capability of the first device associated with the access connection; and send the first information according to the second information.

[0500] Optionally, the first device is a repeater NCR controlled by the network.

[0501] Optionally, the transceiver module 501 is configured to receive the second information sent by a second device, where the second device is a management device of the first device; or receive the second information reported by the first device.

[0502] Optionally, the first device supports in-band communication with an access network device, and the frequency information indicates at least one of the following:

[0503] Reference frequency;

[0504] An offset, used to determine the frequency domain starting position of the beam;

[0505] length, used to determine the amount of frequency domain resources used by the beam;

[0506] The identification of the carrier component CC;

[0507] The identification of the bandwidth part BWP;

[0508] The number of the frequency band.

[0509] Optionally, the first device supports in-band communication and out-of-band communication with an access network device, and the frequency information indicates at least one of the following:

[0510] Reference frequency;

[0511] An offset, used to determine the frequency domain starting position of the beam;

[0512] length, used to determine the amount of frequency domain resources used by the beam.

[0513] Optionally, the transceiver module 501 is configured to send a radio resource control RRC message carrying the first information.

[0514] Optionally, the transceiver module 501 is configured to send downlink control information DCI; wherein the DCI is used to perform non-periodic beam configuration scheduling based on the first information.

[0515] Optionally, when the DCI is used for a control connection, the DCI uses a first scrambling sequence;

[0516] When the DCI is used for an access connection, the DCI uses a second scrambling sequence;

[0517] The second scrambling sequence is different from the first scrambling sequence.

[0518] Optionally, the beam configuration includes at least one of the following:

[0519] Periodic / semi-static beam configuration;

[0520] Aperiodic beam configuration.

[0521] FIG6 is a schematic structural diagram of a first device provided in an embodiment of the present disclosure, wherein the first device includes:

[0522] The transceiver module 601 is configured to receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

[0523] Optionally, the frequency information indicates at least one of the following:

[0524] Reference frequency;

[0525] An offset, used to determine the frequency domain starting position of the beam;

[0526] length, used to determine the amount of frequency domain resources used by the beam.

[0527] Optionally, the offset includes an offset of a resource block RB, and the length includes a length of the RB;

[0528] or,

[0529] The offset includes an offset of a resource block group (RBG), and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

[0530] Optionally, the frequency information includes an index value,

[0531] Herein, one index value refers to one piece of frequency information or a combination of multiple pieces of frequency information.

[0532] Optionally, the frequency information includes at least one of the following:

[0533] The identification of the carrier component CC;

[0534] The identification of the bandwidth part BWP;

[0535] The number of the frequency band.

[0536] Optionally, the first information includes:

[0537] Collection information, indicating resource collection;

[0538] Resource information is included in the resource set information, and one piece of resource information indicates a transmission resource, and the resource information includes: a beam identifier and time domain information; the time domain information indicates the time domain position corresponding to the transmission resource.

[0539] Optionally, the frequency domain information is included in the set information;

[0540] The frequency domain information indicates a frequency domain position, which is used for each resource in the resource set.

[0541] Optionally, the frequency domain information is included in the resource information;

[0542] Among them, one frequency domain position indicated by the frequency domain information is used for one transmission resource.

[0543] Optionally, the transceiver module 601 is configured to send second information, wherein the second information is used to indicate the frequency capability of the first device associated with the access connection; and receive the first information according to the second information.

[0544] Optionally, the first device is a repeater NCR controlled by the network.

[0545] Optionally, the transceiver module 601 is configured to receive a radio resource control RRC message carrying the first information.

[0546] Optionally, the transceiver module 601 is configured to receive downlink control information DCI; wherein the DCI is used to perform non-periodic beam configuration scheduling based on the first information.

[0547] Optionally,

[0548] descrambling the DCI using a first scrambling sequence, wherein the DCI is used to control the connection;

[0549] descrambling the DCI using a second scrambling sequence, wherein the DCI is used for an access connection;

[0550] The second scrambling sequence is different from the first scrambling sequence.

[0551] Optionally, the beam configuration includes at least one of the following:

[0552] Periodic / semi-static beam configuration;

[0553] Aperiodic beam configuration.

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

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

[0556] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0557] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0558] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0559] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0561] FIG7 b is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG7 b , but the present disclosure is not limited thereto.

[0562] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above communication methods.

[0563] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0564] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0565] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

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

[0567] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0568] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0569] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for processing beam configuration, wherein: The method comprises: Send first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

2. The method according to claim 1, wherein: The frequency information includes at least one of the following: Reference frequency; An offset, used to determine a frequency domain starting position of the beam; length, which is used to determine the amount of frequency domain resources used by the beam.

3. The method according to claim 2, wherein: The offset includes an offset of a resource block RB, and the length includes a length of the RB; or, The offset includes an offset of a resource block group RBG, and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

4. The method according to claim 1, wherein: The frequency information includes an index value, Wherein, one of the index values ​​corresponds to at least one of the following: A reference frequency point; An offset for determining a frequency domain starting position of the beam; A length that determines the amount of frequency domain resources used by the beam.

5. The method according to claim 1, wherein: The frequency information includes at least one of the following: The identification of the carrier component CC; The identification of the bandwidth part BWP; The number of the frequency band.

6. The method according to any one of claims 1 to 5, wherein: The first information includes: The set information is used to indicate a resource set, wherein the set information includes resource information, one piece of resource information indicates a transmission resource in the resource set, and the resource information includes: a beam identifier and time domain information; the time domain information indicates a time domain position corresponding to the transmission resource.

7. The method according to claim 6, wherein: The frequency information is included in the set information, and a frequency domain position indicated by the frequency information is used for each transmission resource in the resource set.

8. The method according to claim 6, wherein: The frequency information is included in the resource information, and the frequency domain position indicated by the frequency information is used for the transmission resource indicated by the resource information including the frequency information.

9. The method according to any one of claims 1 to 8, wherein: The method further comprises: receiving second information, wherein the second information is used to indicate a frequency capability of a first device associated with the access connection; The sending of the first information includes: The first information is sent according to the second information.

10. The method according to claim 9, wherein: The first device is a repeater NCR controlled by the network.

11. The method according to claim 9, wherein: The receiving of the second information comprises: receiving the second information sent by a second device, wherein the second device is a management device of the first device; or, Receive the second information reported by the first device.

12. The method according to any one of claims 9 to 11, wherein: When the access connection and the control connection of the first device use the same frequency band, the frequency information includes at least one of the following: Reference frequency; An offset, used to determine a frequency domain starting position of the beam; length, used to determine the amount of frequency domain resources used by the beam; The identification of the carrier component CC; The identification of the bandwidth part BWP; The number of the frequency band.

13. The method according to any one of claims 9 to 11, wherein: When the frequency bands used by the access connection and the control connection of the first device are different or partially the same, the frequency information includes at least one of the following: Reference frequency; An offset, used to determine a frequency domain starting position of the beam; length, which is used to determine the amount of frequency domain resources used by the beam.

14. The method according to any one of claims 1 to 13, wherein: The sending of the first information includes: Send a radio resource control RRC message carrying the first information.

15. The method according to any one of claims 1 to 14, wherein: The method further comprises: Send downlink control information DCI; wherein the DCI is used to perform non-periodic beam configuration scheduling based on the first information.

16. The method according to claim 15, wherein: When the DCI is used for controlling a connection, the DCI is scrambled by a first scrambling sequence; When the DCI is used for an access connection, the DCI is scrambled by a second scrambling sequence; The second scrambling sequence is different from the first scrambling sequence.

17. The method according to any one of claims 1 to 16, wherein: The beam configuration includes at least one of the following: Periodic beam configuration; Semi-static beam configuration; Aperiodic beam configuration.

18. A method for processing beam configuration, wherein: The method comprises: Receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

19. The method according to claim 18, wherein: The frequency information includes at least one of the following: Reference frequency; An offset, used to determine a frequency domain starting position of the beam; length, which is used to determine the amount of frequency domain resources used by the beam.

20. The method according to claim 19, wherein: The offset includes an offset of a resource block RB, and the length includes a length of the RB; or, The offset includes an offset of a resource block group RBG, and the length includes a length of the RBG; wherein one RBG includes a plurality of RBs.

21. The method according to claim 18, wherein: The frequency information includes an index value, Wherein, one of the index values ​​corresponds to at least one of the following: A reference frequency point; An offset for determining a frequency domain starting position of the beam; A length that determines the amount of frequency domain resources used by the beam.

22. The method according to claim 17, wherein: The frequency information includes at least one of the following: The identification of the carrier component CC; The identification of the bandwidth part BWP; The number of the frequency band.

23. The method according to any one of claims 18 to 22, wherein: The first information includes: The set information is used to indicate a resource set, wherein the set information includes resource information, one piece of resource information indicates a transmission resource in the resource set, and the resource information includes: a beam identifier and time domain information; the time domain information indicates a time domain position corresponding to the transmission resource.

24. The method according to claim 23, wherein: The frequency information is included in the set information, and a frequency domain position indicated by the frequency information is used for each transmission resource in the resource set.

25. The method according to claim 23, wherein: The frequency information is included in the resource information, and the frequency domain position indicated by the frequency information is used for the transmission resource indicated by the resource information including the frequency information.

26. The method according to any one of claims 18 to 25, wherein: The method further comprises: sending second information, wherein the second information is used to indicate a frequency capability of a first device associated with the access connection; The receiving of the first information includes: The first information is received according to the second information.

27. The method according to claim 26, wherein: The first device is a repeater NCR controlled by the network.

28. The method according to any one of claims 18 to 27, wherein: The receiving of the first information comprises: Receive a radio resource control RRC message carrying the first information.

29. The method according to any one of claims 18 to 28, wherein: The method further comprises: Receive downlink control information DCI; wherein the DCI is used to perform non-periodic beam configuration scheduling based on the first information.

30. The method of claim 29, wherein: descrambling the DCI using a first scrambling sequence, wherein the DCI is used to control a connection; descrambling the DCI using a second scrambling sequence, wherein the DCI is used for an access connection; The second scrambling sequence is different from the first scrambling sequence.

31. The method according to any one of claims 18 to 30, wherein: The beam configuration includes at least one of the following: Periodic beam configuration; Semi-static beam configuration; Aperiodic beam configuration.

32. A method for processing beam configuration, wherein: The method comprises: The access network device sends first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of a beam for the access connection; The first device receives the first information.

33. A core network device, wherein: The core network equipment includes: The transceiver module is configured to send first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

34. A first device, wherein: The first device comprises: The transceiver module is configured to receive first information, wherein the first information indicates a beam configuration for an access connection, wherein the first information includes: frequency information; the frequency information indicates a frequency domain position of the beam for the access connection.

35. A communication system, wherein: The communication system includes an access network device and a first device; the access network device is configured to implement the method described in any one of claims 1 to 17, and the first device is configured to implement the method described in any one of claims 18 to 31.

36. A communication device, wherein: The communication device comprises: one or more processors; The processor is used to call instructions so that the communication device executes the processing method described in any one of claims 1 to 17, claims 18 to 31 and claim 32.

37. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the processing method described in any one of claims 1 to 17, claims 18 to 31, and claim 32.

Images