Method, apparatus and device for acquiring beam information, and storage medium

Abstract

Embodiments of the present application provide a method, device and computer readable storage medium for acquiring beam information, relating to the technical field of communication. The method comprises: a user equipment (UE) acquiring information of a second type of beam available to the UE on a first type of beam camped by the UE; and the UE triggering an access procedure on the second type of beam. The method provided by the embodiments of the present application can solve the problem that the UE acquires the second type of beam available through the first type of beam.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method, apparatus, device, and computer-readable storage medium for acquiring beam information. Background Technology

[0002] In satellite communication systems, two types of beams are distinguished: Type I beams and Type II beams. Type I beams are also known as unrestricted beams, while Type II beams are also known as service beams. Type I beams do not provide services to connected UEs, while Type II beams allow UEs to access the network and provide services to connected UEs. The satellite coverage area can be divided into multiple beam positions. Type I beams periodically scan each beam position, while Type II beams are scheduled to provide services to UEs as needed, providing services to connected UEs.

[0003] In existing NR communication systems, idle or inactive UEs obtain the cell's system information on the initial bandwidth part (BWP) and access the cell on the initial BWP. There is no situation where the discovered cell and the accessed cell are in different operating bandwidth ranges.

[0004] However, in existing satellite communication systems, the UE discovers the cell location (Type 1 beam) and accesses the cell location (Type 2 beam) in different operating frequency domains and bandwidths. How the UE can obtain relevant information about the Type 2 beam that can be accessed through the Type 1 beam remains to be solved. Summary of the Invention

[0005] This application provides a method, apparatus, device, and computer-readable storage medium for acquiring beam information, which can solve at least one technical problem in the prior art.

[0006] Firstly, a method for acquiring beam information is provided, the method comprising:

[0007] The user equipment (UE) obtains information about the second type of beam available to the UE on the first type of beam it is camped on;

[0008] The UE is in the second type of beam-triggered access process.

[0009] In one possible implementation, before the UE obtains information about a second type of beam available to the UE on the first type of beam it is camped on, the method further includes:

[0010] The UE initiates an access request to the network on the first type of beam it is camped on.

[0011] In another possible implementation, the UE initiates an access request to the network on the first type of beam it is camped on, including:

[0012] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0013] If it is determined, based on the relevant information of the second type of beam, that there is no second type of beam available to the UE in the current network, the UE initiates an access request to the network on the first type of beam.

[0014] In another possible implementation, the information of the second type of beam includes at least one of the following:

[0015] The identifier for the second type of beam;

[0016] Second type of beam frequency domain information;

[0017] Temporal configuration information for the second type of beam;

[0018] The identifier of the first type of associated beam;

[0019] Indication that a Type II beam is in service;

[0020] Indication information for upcoming Category 2 beam service.

[0021] In another possible implementation, the UE obtains information about the second type of beam available to the UE on the first type of beam it is camped on, including:

[0022] The UE receives first system information on the first type of beam it is camped on, the first system information carrying information about the second type of beam available to the UE; or...

[0023] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0024] The UE obtains information about the second type of beams available to the UE based on the relevant information of the second type of beams.

[0025] In another possible implementation, the relevant information of the second type of beam is carried through the second system information and / or the media access control layer control unit (MAC CE), and the relevant information of the second type of beam includes at least one of the following:

[0026] Is there any indication of Category II beam coverage?

[0027] Indication information regarding whether it carries information about type 2 beams;

[0028] The UE requests configuration information for relevant network resources.

[0029] Configuration information for at least one type II beam.

[0030] In another possible implementation, the configuration information for each of the second type of beams includes at least one of the following:

[0031] The identifier for the second type of beam;

[0032] Second type of beam frequency domain information;

[0033] Temporal configuration information for the second type of beam;

[0034] Indication that a Type II beam is in service;

[0035] Indication information for upcoming Category 2 beam service.

[0036] In another possible implementation, the time-domain configuration information of the second type of beam includes at least one of the following:

[0037] Type II beam arrival time offset;

[0038] Synchronization signal block (SSB) mode for Category 2 beams;

[0039] The time difference between Type II beams and Type I beams.

[0040] In another possible implementation, obtaining information about the second type of beam available to the UE includes:

[0041] After the UE initiates an access request to the network on the first type of beam it is camped on, or after learning from the relevant information of the second type of beam information that a second type of beam is currently covering the network, or after learning from the relevant information of the second type of beam information that it carries information about a second type of beam,

[0042] At the next downlink moment of the first type of beam during the current scanning period of the first type of beam, the UE receives third system information or MAC CE, wherein the third system information or MAC CE carries information about the second type of beam available to the UE.

[0043] In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0044] Secondly, a method for acquiring beam information is provided, the method comprising:

[0045] The system sends information about the second type of beam available to the UE that is camped on the first type of beam to the UE that is camped on the first type of beam, so that the UE can trigger the access procedure on the second type of beam.

[0046] In one possible implementation, before transmitting information about the second type of beam to the UE camped on the first type of beam via the first type of beam, the process includes:

[0047] Receive the access request sent by the UE on the first type of beam.

[0048] In another possible implementation, transmitting information about the second type of beam to the UE residing in the first type of beam via the first type of beam includes:

[0049] Upon receiving an access request initiated by the UE, during the downlink transmission time of the first type of beam where the UE is camped within the current scanning period of the first type of beam, the third system information or MACCE is transmitted, wherein the third system information or the MACCE carries information about the second type of beam available to the UE.

[0050] In another possible implementation, the information of the second type of beam includes at least one of the following:

[0051] The identifier for the second type of beam;

[0052] Second type of beam frequency domain information;

[0053] Temporal configuration information for the second type of beam;

[0054] The associated first type of beam identifier;

[0055] Indication that a Type II beam is in service;

[0056] Indication information for upcoming Category 2 beam service.

[0057] In another possible implementation, transmitting information about the second type of beam to the UE residing in the first type of beam via the first type of beam includes:

[0058] First system information is sent to a UE residing on the first type of beam via a first type of beam, the first system information carrying information about a second type of beam available to the UE; or...

[0059] The relevant information of the second type of beam is sent to the UE camped on the first type of beam through the first type of beam, so that the UE can obtain the information of the second type of beam based on the relevant information of the second type of beam.

[0060] In another possible implementation, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0061] Is there any indication of Category II beam coverage?

[0062] Indication information regarding whether it carries information about type 2 beams;

[0063] The UE requests configuration information for relevant network resources.

[0064] Configuration information for at least one type II beam.

[0065] In another possible implementation, the configuration information of the second type of beam includes at least one of the following:

[0066] The identifier for the second type of beam;

[0067] Second type of beam frequency domain information;

[0068] Temporal configuration information for the second type of beam;

[0069] Indication that a Type II beam is in service;

[0070] Indication information for upcoming Category 2 beam service.

[0071] In another possible implementation, the time-domain configuration information of the second beam includes at least one of the following:

[0072] Type II beam arrival time offset;

[0073] Synchronization signal block (SSB) mode for Category 2 beams;

[0074] The time difference between the second type of beam and the first type of beam.

[0075] In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0076] Thirdly, a device for acquiring beam information is provided, applied to user equipment, the device comprising:

[0077] The acquisition module is used to acquire information about the second type of beam available to the user equipment (UE) on the first type of beam it is camped on;

[0078] The processing module is used by the UE during the second type of beam-triggered access process.

[0079] In one possible implementation, it also includes: a transmission module, used by the UE to initiate an access request to the network on the first type of beam it resides in.

[0080] In another possible implementation, the sending module is specifically used for:

[0081] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0082] If it is determined, based on the relevant information of the second type of beam, that there is no second type of beam available to the UE in the current network, the UE initiates an access request to the network on the first type of beam.

[0083] In another possible implementation, the information of the second type of beam includes at least one of the following:

[0084] The identifier for the second type of beam;

[0085] Second type of beam frequency domain information;

[0086] Temporal configuration information for the second type of beam;

[0087] The identifier of the first type of associated beam;

[0088] Indication that a Type II beam is in service;

[0089] Indication information for upcoming Category 2 beam service.

[0090] In another possible implementation, the acquisition module is specifically used for:

[0091] The UE receives first system information on the first type of beam it is camped on, the first system information carrying information about the second type of beam available to the UE; or...

[0092] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0093] The UE obtains information about the second type of beams available to the UE based on the relevant information of the second type of beams.

[0094] In another possible implementation, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0095] Is there any indication of Category II beam coverage?

[0096] Indication information regarding whether it carries information about type 2 beams;

[0097] The UE requests configuration information for relevant network resources.

[0098] Configuration information for at least one type II beam.

[0099] In another possible implementation, the configuration information for each of the second type of beams includes at least one of the following:

[0100] The identifier for the second type of beam;

[0101] Second type of beam frequency domain information;

[0102] Temporal configuration information for the second type of beam;

[0103] Indication that a Type II beam is in service;

[0104] Indication information for upcoming Category 2 beam service.

[0105] In another possible implementation, the time-domain configuration information of the second type of beam includes at least one of the following:

[0106] Type II beam arrival time offset;

[0107] Synchronization signal block (SSB) mode for Category 2 beams;

[0108] The time difference between Type II beams and Type I beams.

[0109] In another possible implementation, the acquisition module is specifically used for:

[0110] After the UE initiates an access request to the network on the first type of beam it is camped on, or after learning from the relevant information of the second type of beam information that a second type of beam is currently covering the network, or after learning from the relevant information of the second type of beam information that it carries information about a second type of beam,

[0111] At the next downlink moment of the first type of beam during the current scanning period of the first type of beam, the UE receives third system information or MAC CE, wherein the third system information or MAC CE carries information about the second type of beam available to the UE.

[0112] In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0113] Fourthly, a device for acquiring beam information is provided, applied to network-side equipment, the device comprising:

[0114] The transmitting module is configured to transmit information about a second type of beam available to the UE residing in the first type of beam via a first type of beam, so that the UE can trigger an access procedure on the second type of beam.

[0115] In one possible implementation, it further includes: a receiving module for receiving an access request sent by the UE on the first type of beam.

[0116] In another possible implementation, the transmitting module is specifically used to: after receiving an access request initiated by the UE, during the downlink transmission time of the first type of beam where the UE is camped within the current scanning period of the first type of beam, transmit third system information or MACCE, wherein the third system information or the MACCE carries information about the second type of beam available to the UE.

[0117] In another possible implementation, the information of the second type of beam includes at least one of the following:

[0118] The identifier for the second type of beam;

[0119] Second type of beam frequency domain information;

[0120] Temporal configuration information for the second type of beam;

[0121] The associated first type of beam identifier;

[0122] Indication that a Type II beam is in service;

[0123] Indication information for upcoming Category 2 beam service.

[0124] In another possible implementation, the acquisition module is specifically configured to: send first system information to a UE residing in the first type of beam via a first type of beam, wherein the first system information carries information about a second type of beam available to the UE; or...

[0125] The relevant information of the second type of beam is sent to the UE camped on the first type of beam through the first type of beam, so that the UE can obtain the information of the second type of beam based on the relevant information of the second type of beam.

[0126] In another possible implementation, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0127] Is there any indication of Category II beam coverage?

[0128] Indication information regarding whether it carries information about type 2 beams;

[0129] The UE requests configuration information for relevant network resources.

[0130] Configuration information for at least one type II beam.

[0131] In another possible implementation, the configuration information of the second type of beam includes at least one of the following:

[0132] The identifier for the second type of beam;

[0133] Second type of beam frequency domain information;

[0134] Temporal configuration information for the second type of beam;

[0135] Indication that a Type II beam is in service;

[0136] Indication information for upcoming Category 2 beam service.

[0137] In another possible implementation, the time-domain configuration information of the second beam includes at least one of the following:

[0138] Type II beam arrival time offset;

[0139] Synchronization signal block (SSB) mode for Category 2 beams;

[0140] The time difference between the second type of beam and the first type of beam.

[0141] In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0142] Fifthly, a user equipment is provided, the equipment comprising:

[0143] Memory, used to store computer programs;

[0144] Transceiver, used to send and receive data under the control of the processor;

[0145] A processor is configured to read and execute a computer program from the memory to implement the method for acquiring beam information as described in the first aspect of this application.

[0146] Sixthly, a network-side device is provided, comprising:

[0147] Memory, used to store computer programs;

[0148] Transceiver, used to send and receive data under the control of the processor;

[0149] A processor is configured to read and execute a computer program from the memory to implement the method for acquiring beam information as described in the second aspect of this application.

[0150] In a seventh aspect, a processor-readable storage medium is provided, the processor-readable storage medium storing a computer program, the computer program being used to cause a processor to execute and implement the method for acquiring beam information as shown in the first aspect of this application.

[0151] Eighthly, a processor-readable storage medium is provided, the processor-readable storage medium storing a computer program for causing a processor to execute and implement the method for acquiring beam information as shown in the second aspect of this application.

[0152] The beneficial effects of the technical solution provided in this application are:

[0153] The UE obtains information about its available second-type beams through the first-type beam it camps on, and triggers the access process on the second-type beam, thereby solving the problem of the UE knowing the available second-type beams through the first-type beam. Attached Figure Description

[0154] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0155] Figure 1 A flowchart illustrating a method for acquiring beam information provided in an embodiment of this application;

[0156] Figure 2 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0157] Figure 3 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0158] Figure 4 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0159] Figure 5 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0160] Figure 6 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0161] Figure 7 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0162] Figure 8 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0163] Figure 9 A flowchart illustrating a method for acquiring beam information according to another embodiment of this application;

[0164] Figure 10 This is a schematic diagram of the structure of a user equipment provided in an embodiment of this application. Detailed Implementation

[0165] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting the invention.

[0166] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0167] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0168] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network-side equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G systems (5GS).

[0169] First, let's introduce and explain several terms used in this application:

[0170] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0171] The network-side equipment involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in the access network that communicates with wireless terminal devices through one or more sectors on the air interface, or other names. The network-side equipment can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network-side equipment can also coordinate the attribute management of the air interface.

[0172] For example, the network-side equipment involved in the embodiments of this application can be a base transceiver station (BTS) in Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a network-side device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), an evolved network-side device (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network-side equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may also be geographically separated.

[0173] Network-side equipment and terminal equipment can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0174] In satellite communication systems, two types of beams are distinguished: Type I beams and Type II beams. Type I beams are also called unrestricted beams, and Type II beams are called service beams. Type I beams do not provide services to connected UEs, while Type II beams allow UEs to access and provide services to connected UEs. The communication coverage area of ​​a satellite can be divided into multiple positions. Type I beams provide services to each position by periodically scanning each position. Within each period, Type I beams provide services for a fixed unit of time at each position, such as 5ms. UEs at each position can periodically receive services from Type I beams. Type I beams have a narrower operating bandwidth and do not provide services to connected UEs; however, Type I beams can broadcast system information to UEs. Each Type I beam can be identified by a corresponding beam identifier.

[0175] The satellite system provides services to connected UEs through Type II beams. A satellite can support multiple Type II beams, each with different operating frequency domains and bandwidths. The operating frequency domains and bandwidths of Type II beams also differ from those of Type I beams. Type II beams are scheduled on demand, meaning that they are allocated to serve a UE based on whether a UE needs to access the service on a particular beam position.

[0176] Since the beam types serving connected and disconnected UEs are different, how the UE can learn about the second type of beams that can be accessed through the first type of beam needs to be solved.

[0177] Therefore, in the method for obtaining beam information provided in this application embodiment, the UE obtains information about the second type of beam that can be accessed by broadcasting relevant information about the second type of beam at the current coverage position in the first type of beam system information, and / or, the UE sends an access request through the first type of beam, and the first type of beam carries relevant information about the second type of beam that provides services to the UE through the system information or the Media Access Control Element (MAC CE).

[0178] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0179] This application provides a method for obtaining beam information, such as... Figure 1 As shown, the method includes:

[0180] S101. The user equipment (UE) obtains information about the second type of beam available to the UE on the first type of beam it is camped on;

[0181] S102, The UE is in the second type of beam-triggered access process.

[0182] Specifically, in this embodiment, the UE can obtain information about its available second type of beam on the first type of beam it is camped on, search and synchronize to the second type of beam, and then trigger the access process on the second type of beam.

[0183] In one possible implementation, prior to S101, the method further includes:

[0184] S100, the UE initiates an access request to the network on the first type of beam it is camped on.

[0185] One possible implementation, S100 may specifically include:

[0186] Before acquiring second-type beam information available to the UE, the UE always initiates an access request to the network on the first-type beam it is camped on. One possible implementation of this access request is to send a random access preamble, or sequence, configured by the network.

[0187] In one possible implementation, S100 may specifically include:

[0188] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0189] If, based on the relevant information of the second type of beam, it is determined that there is no second type of beam available to the UE in the current network, the UE initiates an access request to the network on the first type of beam. One possible implementation of this access request is to send a random access preamble, or sequence, configured by the network.

[0190] In the above embodiments, the information of the second type of beam includes at least one of the following:

[0191] The identifier for the second type of beam;

[0192] Second type of beam frequency domain information;

[0193] Temporal configuration information for the second type of beam;

[0194] The identifier of the first type of associated beam;

[0195] Indication that a Type II beam is in service;

[0196] Indication information for upcoming Category 2 beam service.

[0197] The identifier of the associated first type beam indicates the identifier information of the first type beam corresponding to the second type beam when the network receives the access request. That is, the second type beam is the second type beam that responds to the access request sent through the first type beam. For example, the first type beam can also be called the random beam, and the second type beam can also be called the service beam. If the UE initiates an access request to the network while camped on random beam 2, and the network receives the access request and schedules service beam 4 for the UE, then the identifier of the random beam associated with service beam 4 is configured as 2.

[0198] In this application embodiment, the UE obtains information about its available second type beams on the first type beam it camps on, including the following methods:

[0199] The first method: The UE receives first system information on the first type of beam it is camped on, and the first system information carries information about the second type of beam available to the UE;

[0200] The second method is as follows: The UE obtains relevant information about the second type of beam on the first type of beam it is camped on; based on the relevant information about the second type of beam, it obtains information about the second type of beam available to the UE.

[0201] In the first approach described above, the specific process for obtaining information about the second type of beam available to the UE may include:

[0202] The UE broadcasts first system information on the first type of beam it is camped on, which carries information about the second type of beam available to the UE. One possible implementation is that the first system information carries an indication that the second type of beam is being served. For example, if the second type of beam 2 is currently serving the position that the first type of beam 1 is currently scanning, then the system information may carry the identifier 2 of the second type of beam, the frequency domain information of the second type of beam, the time domain configuration information of the second type of beam, the identifier of the associated first type of beam, and the indication that the second type of beam is being served.

[0203] In the second method described above, the specific process of obtaining information about the second type of beam available to the UE may include:

[0204] One possible implementation is to determine, based on relevant information of the second type of beam information, that a second type of beam is currently covering the area, or based on relevant information of the second type of beam information, that information carrying the second type of beam is being obtained.

[0205] One possible implementation is that, at the next downlink moment of the first type of beam where the UE is camped during the current scanning period of the first type of beam, third system information or MAC CE is received, wherein the third system information or the MAC CE carries information about the second type of beam available to the UE.

[0206] Another possible implementation is that the UE obtains relevant information about the second type of beam on the first type of beam it is camped on, and initiates an access request to the network on the first type of beam. After determining, based on the relevant information of the second type of beam, that there is no second type of beam currently covering the current beam position (i.e., the beam position currently being scanned by the first type of beam), or that there is no second type of beam about to cover the current beam position, the UE initiates an access request to the network on the first type of beam it is camped on. The network sends the second type of beam information to the UE based on the UE's request. The UE then obtains the information about the second type of beam available to the UE.

[0207] One possible implementation is that, at the next downlink moment of the first type of beam where the UE is camped during the current scanning period of the first type of beam, third system information or MAC CE is received, wherein the third system information or the MAC CE carries information about the second type of beam available to the UE.

[0208] Specifically, in this embodiment, the MAC CE can be scheduled by a PDCCH scrambled with a preset RNTI. In one possible implementation, the MAC CE is scheduled by a PDCCH scrambled with RA-RNTI. The next downlink time refers to the downlink time at which system information or the MAC CE can be scheduled.

[0209] In the above embodiments, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0210] Is there any indication of Category II beam coverage?

[0211] Indication information regarding whether it carries information about type 2 beams;

[0212] The UE requests configuration information for relevant network resources.

[0213] Configuration information for at least one type II beam.

[0214] The configuration information of the relevant resources requested by the UE to access the network may specifically include the resource configuration used by the UE when initiating the access request. One possible implementation is to include the time and frequency resources, sequence, preamble, etc., for initiating the access request.

[0215] The configuration information for each of the second type of beams includes at least one of the following:

[0216] The identifier for the second type of beam;

[0217] Second type of beam frequency domain information;

[0218] Temporal configuration information for the second type of beam;

[0219] Indication that a Type II beam is in service;

[0220] Indication information for upcoming Category 2 beam service.

[0221] The time-domain configuration information of the second type of beam includes at least one of the following:

[0222] Type II beam arrival time offset;

[0223] Synchronization signal block (SSB) mode for Category 2 beams;

[0224] The time difference between Type II beams and Type I beams.

[0225] The synchronization signal block (SSB) mode of the second type beam may include the SSB period length and / or the starting position of the SSB within that period. The time difference between the second type beam and the first type beam, the synchronization time difference, may include any one or more of the following: SFN offset, slot offset, OFDM symbol offset, but is not limited to these.

[0226] This application provides a method for obtaining beam information, such as... Figure 2 As shown, the method includes:

[0227] S201. Send information about a second type of beam available to the UE that is camped on the first type of beam through the first type of beam, so that the UE can trigger an access procedure on the second type of beam.

[0228] Specifically, in this embodiment, the information of the second type of beam includes at least one of the following:

[0229] The identifier for the second type of beam;

[0230] Second type of beam frequency domain information;

[0231] Temporal configuration information for the second type of beam;

[0232] The associated first type of beam identifier;

[0233] Indication that a Type II beam is in service;

[0234] Indication information for upcoming Category 2 beam service.

[0235] In one possible implementation, prior to S201, the method further includes:

[0236] S200: Receive the access request sent by the UE on the first type of beam.

[0237] Specifically, in this embodiment, after receiving an access request sent by the UE on the first type of beam, the network side can allocate an available second type of beam to the UE and send the information of the second type of beam to the UE through system information and / or MAC CE. One possible implementation of the access request is to send a random access preamble, or sequence, configured by the network.

[0238] In another possible implementation, S201 may specifically include: after receiving an access request initiated by the UE, during the downlink transmission time of the first type of beam in which the UE is camped within the current scanning period of the first type of beam, sending third system information or MACCE, wherein the third system information or the MACCE carries information about the second type of beam available to the UE.

[0239] Specifically, in this embodiment, the MAC CE is scheduled by a PDCCH scrambled with a preset RNTI. In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled with RA-RNTI.

[0240] In another possible implementation, S201 may specifically include:

[0241] First system information is sent to a UE residing on the first type of beam via a first type of beam, the first system information carrying information about a second type of beam available to the UE; or...

[0242] The relevant information of the second type of beam is sent to the UE camped on the first type of beam through the first type of beam, so that the UE can obtain the information of the second type of beam based on the relevant information of the second type of beam.

[0243] Specifically, in this embodiment, the relevant information of the second type of beam is carried through second system information and / or MACCE, and the relevant information of the second type of beam includes at least one of the following:

[0244] Is there any indication of Category II beam coverage?

[0245] Indication information regarding whether it carries information about type 2 beams;

[0246] The UE requests configuration information for relevant network resources.

[0247] Configuration information for at least one type II beam.

[0248] The configuration information of the relevant resources requested by the UE to access the network may specifically include the resource configuration used by the UE when initiating the access request. One possible implementation is to include the time and frequency resources, sequence, preamble, etc., for initiating the access request.

[0249] The configuration information for the second type of beam includes at least one of the following:

[0250] The identifier for the second type of beam;

[0251] Second type of beam frequency domain information;

[0252] Temporal configuration information for the second type of beam;

[0253] Indication that a Type II beam is in service;

[0254] Indication information for upcoming Category 2 beam service.

[0255] The time-domain configuration information of the second beam includes at least one of the following:

[0256] Type II beam arrival time offset;

[0257] Synchronization signal block (SSB) mode for Category 2 beams;

[0258] The time difference between the second type of beam and the first type of beam.

[0259] The synchronization signal block (SSB) mode of the second type beam may include the SSB period length and / or the starting position of the SSB within that period. The time difference between the second type beam and the first type beam, the synchronization time difference, may include any one or more of the following: SFN offset, slot offset, OFDM symbol offset, but is not limited to these.

[0260] In summary, the method for obtaining beam information provided in this application embodiment allows the UE to obtain information about the second type of beam that can be accessed by broadcasting relevant information about the second type of beam for the current coverage position in the first type of beam system information, and / or the UE sends an access request through the first type of beam, and the first type of beam carries relevant information about the second type of beam that provides services to the UE through the system information or MAC CE.

[0261] The following is in conjunction with the appendix Figures 3 to 9 The paper takes the example of "the satellite system is pre-divided into 500 positions, the dwell time of the first type of beam at each position is 5ms, the scanning period of the first type of beam is 2.5s, the beam index (identifier) ​​of the first type of beam is 0-499, and the identification of the second type of beam is 1-5" to describe in detail the specific implementation process of a method for obtaining beam information provided in the embodiments of this application.

[0262] Example 1: Obtaining second-type beam information by sending an access request.

[0263] Example 1-1: The method for the UE to obtain the second type of beam information via MAC CE is as follows Figure 3As shown, it includes:

[0264] Step 301: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and initiates an access request on the first type of beam.

[0265] Specifically, in this embodiment, before sending an access request, the UE obtains system information from the first type of beam 15. This system information includes basic information about five second type of beams or at least one second type of beam (i.e., the system information may contain basic information about all second type of beams, or basic information about the second type of beam that may be scheduled to that beam position). The basic information of each second type of beam includes at least one of the following:

[0266] The identifier for the second type of beam;

[0267] Frequency domain information of the second type of beam;

[0268] Temporal configuration information for the second type of beam;

[0269] Indication that a Type II beam is in service;

[0270] Indication information for upcoming Category 2 beam service.

[0271] Alternatively, before sending an access request, the UE obtains system information from the first type beam 15, wherein the system information does not include basic information of the second type beam.

[0272] Optionally, before initiating an access request, the UE also obtains configuration information of relevant network resources for which it requests access through the system information of the first type of beam. This includes, for example, the time-frequency resources, sequence, and preamble for initiating the access request. One possible implementation is to transmit the sequence on network-configured resources, such as transmitting a specified preamble on configured RACH resources.

[0273] Step 302: After receiving the UE's access request through the first type beam 15, the network allocates the second type beam to the UE.

[0274] Step 303: The network sends the information of the second type beam to the UE via MAC CE through the first type beam 15.

[0275] In this embodiment, the MAC CE is scheduled through a physical downlink control channel (PDCCH) scrambled with a preset Radio Network Temporary Identifier (RNTI). One possible implementation is to use random access radio network temporary identifier (RA-RNTI) scrambling.

[0276] Assuming the identifier of the assigned second type of beam is 2, the specific methods by which the MAC CE carries the second type of beam information may include the following:

[0277] Method 1-1: If the system information in step 301 has already broadcast part of the access information of the second type beam, then the MACCE can only carry the identifier of the second type beam. The UE can obtain the frequency domain information and / or time domain information related to the second type beam by combining the identifier of the second type beam with the system information.

[0278] Method 1-2: If the system information in step 301 has already broadcast some information of the access to the second type of beam, such as broadcasting frequency domain information, then the MAC CE can only carry the identifier and / or time domain information of the second type of beam. The UE can obtain the frequency domain information related to the second type of beam by combining the identifier of the second type of beam with the system information.

[0279] Methods 1-3: If the system information in step 301 has already broadcast some information of the access to the second type of beam, such as broadcasting time domain information, then the MAC CE can only carry the identifier and / or frequency domain information of the second type of beam. The UE can obtain the time domain information related to the second type of beam by combining the identifier of the second type of beam with the system information.

[0280] Methods 1-4: If the system information in step 301 does not carry part of the information of the second type of beam, then the MAC CE carries the identifier of the second type of beam and / or the frequency domain information and / or the time domain information corresponding to the second type of beam.

[0281] In addition to the above information, optionally, the basic information of the second type of beam may also include the identifier of the first type of beam, wherein the first type of beam corresponds to the first type of beam through which the UE sends the access request, and in this embodiment, it is the first type of beam 15. Optionally, the basic information of the second type of beam may also include indication information that the second type of beam is about to be served or indication information that the second type of beam is currently being served.

[0282] Step 304: The UE obtains the second type beam information from the first type beam 15.

[0283] Specifically, during the scanning of the first type of beam 15, the UE synchronizes with the first type of beam 15 and listens to its PDCCH scheduling. It descrambles the PDCCH using a preset RNTI to obtain scheduling information, and further obtains the corresponding MAC CE, thereby acquiring the second type of beam information carried in the MAC CE. This second type of beam information is the information of the second type of beam 2. The preset RNTI can be RA-RNTI or other RNTIs. One possible implementation is that the MAC CE is only used for the first type of beam, and the UE can parse the MAC PDU according to the MAC CE format only for the first type of beam. If the definition of the MAC CE does not distinguish between the first and second type of beams, the MAC CE is defined using a logical channel ID or other identifier.

[0284] It should be noted that, in this embodiment, after obtaining the information of the second type of beam 2, it is possible to search for and synchronize with the second type of beam 2, and trigger the access process on the second type of beam 2.

[0285] Examples 1-2: Methods for the UE to obtain second-type beam information through system information, as follows Figure 4 As shown, it includes:

[0286] Step 401: The UE camps on the first type of beam, presets the identifier corresponding to the first type of beam to be 15, and initiates an access request on the first type of beam.

[0287] Specifically, in this embodiment, before sending an access request, the UE obtains system information from the first type of beam 15. This system information includes basic information about five second type of beams or at least one second type of beam (i.e., the system information may contain basic information about all second type of beams, or basic information about the second type of beam that may be scheduled to that beam position). The basic information of each second type of beam includes at least one of the following:

[0288] The identifier for the second type of beam;

[0289] Frequency domain information of the second type of beam;

[0290] Temporal configuration information for the second type of beam;

[0291] Indication that a Type II beam is in service;

[0292] Indication information for upcoming Category 2 beam service.

[0293] Alternatively, before sending an access request, the UE obtains system information from the first type beam 15, wherein the system information does not include basic information of the second type beam.

[0294] Optionally, before initiating an access request, the UE also obtains configuration information of relevant network resources for which it requests access through the system information of the first type of beam. This includes, for example, the time-frequency resources, sequence, and preamble for initiating the access request. One possible implementation is to transmit the sequence on network-configured resources, such as transmitting a specified preamble on configured RACH resources.

[0295] Step 402: After receiving the UE's access request through the first type beam 15, the network allocates the second type beam to the UE.

[0296] Step 403: The network sends the information of the second type beam to the UE through system information via the first type beam 15.

[0297] In this embodiment, assuming the identifier of the second type of beam assigned is 2, the specific ways in which the system information carries the second type of beam information may include the following:

[0298] Method 2-1: If the system information in step 401 has already broadcast part of the access information of the second type beam, then the system information can only carry the identifier of the second type beam. The UE can obtain the frequency domain information and / or time domain information related to the second type beam by combining the second type beam identifier with the part of the access information of the second type beam broadcast by the system information.

[0299] Method 2-2: If the system information in step 401 has already broadcast some information about accessing the second type of beam, such as broadcasting frequency domain information, then the system information can carry only the second type of beam identifier and / or time domain information. The UE can obtain the frequency domain information related to the second type of beam by combining the identifier of the second type of beam with the partial information about accessing the second type of beam broadcast by the system information.

[0300] Method 2-3: If the system information in step 401 has already broadcast some information about accessing the second type of beam, such as time domain information, then the system information may only carry the identifier and / or frequency domain information of the second type of beam. The UE can obtain the time domain information related to the second type of beam by combining the identifier of the second type of beam with the partial information about accessing the second type of beam broadcast by the system information.

[0301] Method 2-4: If the system information in step 401 does not carry part of the information of the second type of beam, then the system information carries the identifier of the second type of beam and / or the frequency domain information and / or the time domain information corresponding to the second type of beam.

[0302] In addition to the above information, the optional basic information of the second type of beam may also include a first type of beam identifier, wherein the first type of beam corresponds to the first type of beam through which the UE sends the access request, and in this embodiment, it is the first type of beam 15. Optionally, the basic information of the second type of beam may also include indication information that the second type of beam is about to be served or indication information that the second type of beam is currently being served.

[0303] Step 404: The UE obtains the second type beam information from the first type beam 15.

[0304] Specifically, when the UE scans the first type of beam 15, it synchronizes with the first type of beam 15, listens to its system information, and thus obtains the second type of beam information, wherein the second type of beam information is the information of the second type of beam 2.

[0305] It should be noted that, in this embodiment, after obtaining the information of the second type of beam 2, it is possible to search for and synchronize with the second type of beam 2, and trigger the access process on the second type of beam 2.

[0306] Example 2: Optionally, the second type of beam information can be obtained by sending an access request.

[0307] Example 2-1: A method for the UE to obtain second-type beam information through system information, as follows: Figure 5 As shown, it includes:

[0308] Step 501: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and obtains system information in the first type of beam, wherein the system information includes at least one of the following:

[0309] Is there any indication information for second-type beam coverage? For example: There is currently an indication information for second-type beam coverage, indicating that there is second-type beam coverage.

[0310] Indication information indicating whether it carries Type II beam information; for example: indication information indicating whether it carries Type II beam information, indicating that Type II beam information can be directly obtained;

[0311] The UE requests configuration information for relevant network resources.

[0312] Configuration information for at least one type II beam.

[0313] The configuration information for each of the second type of beams includes at least one of the following:

[0314] The identifier for the second type of beam;

[0315] Second type of beam frequency domain information;

[0316] Temporal configuration information for the second type of beam;

[0317] Indication that a Type II beam is in service;

[0318] Indication information for upcoming Category 2 beam service.

[0319] The information of the second type of beam currently covered, taking the second type of beam 2 as an example, includes the basic information of the second type of beam identified as 2, such as frequency domain information.

[0320] Step 502: The UE searches for and synchronizes with the second type beam 2, and triggers the access procedure on the second type beam 2.

[0321] Example 2-2: The UE obtains the second type of beam information by combining system information and MAC CE method, such as Figure 6 As shown, it includes:

[0322] Step 601: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and obtains system information in the first type of beam, wherein the system information includes at least one of the following:

[0323] Is there any indication information for second-type beam coverage? For example: There is currently an indication information for second-type beam coverage, indicating that there is second-type beam coverage.

[0324] Indication information indicating whether it carries Type II beam information; for example: indication information indicating whether it carries Type II beam information, indicating that Type II beam information can be directly obtained;

[0325] The UE requests configuration information for relevant network resources.

[0326] Configuration information for at least one type II beam.

[0327] The configuration information for each of the second type of beams includes at least one of the following:

[0328] The identifier for the second type of beam;

[0329] Second type of beam frequency domain information;

[0330] Temporal configuration information for the second type of beam;

[0331] Indication that a Type II beam is in service;

[0332] Indication information for upcoming Category 2 beam service.

[0333] Step 602: The UE receives downlink data at the next downlink time and parses the MAC CE to obtain information about the currently covered Type II beam. The next downlink time refers to the downlink time at which system information or the MAC CE can be scheduled.

[0334] Specifically, in this embodiment, taking the second type of beam 2 as an example, this embodiment includes the basic information of the second type of beam identified as 2, such as frequency domain information.

[0335] Step 603: The UE searches for and synchronizes with the second type beam 2, and triggers the access procedure on the second type beam 2.

[0336] Examples 2-3: Methods for the UE to obtain second-type beam information via MAC CE are as follows Figure 7 As shown, it includes:

[0337] Step 701: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and obtains system information and downlink data scrambled by a preset RNTI (e.g., RA-RNTI, or other RNTI) in the first type of beam.

[0338] Step 702: Analyze the MAC CE to obtain information about the currently covered Type II beam.

[0339] Specifically, in this embodiment, taking the second type beam 2 as an example, this embodiment includes the basic information of the second type beam identified as 2, such as frequency domain information, and indication information of the current second type beam being served, or indication information of the second type beam being about to be served, etc.

[0340] Step 703: The UE then searches for and synchronizes with the second type beam 2, and triggers the access procedure on the second type beam 2.

[0341] Examples 2-4: Methods for a UE to obtain second-type beam information by sending an access request, such as... Figure 8 As shown, it includes:

[0342] Step 801: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and obtains system information in the first type of beam, wherein the system information includes at least one of the following:

[0343] There is currently no indication of Category 2 beam coverage; this indicates that there is no Category 2 beam coverage.

[0344] Indication information indicating whether or not it carries Type II beam information; indication information indicating whether or not it carries Type II beam information.

[0345] The UE requests configuration information for relevant network resources.

[0346] Step 802: If the UE learns from the system information that there is no Type II beam currently providing coverage and service on the network, it determines that it needs to send an access request to the network to request the network to schedule a Type II beam.

[0347] Step 803: The UE sends an access request in the first type beam 15.

[0348] Step 804: The UE obtains the second type beam information from the first type beam 15.

[0349] Specifically, in this embodiment, the process by which the UE obtains the information of the second type of beam after sending an access request from the first type of beam 15 can be implemented in the manner described in Embodiment 1. For the sake of brevity, it will not be repeated here.

[0350] It should be noted that, in this embodiment, after obtaining the information of the second type of beam 2, it is possible to search for and synchronize with the second type of beam 2, and trigger the access process on the second type of beam 2.

[0351] Example 3: A method for the UE to obtain second-type beam information through the same first-type beam within the same scanning period is as follows: Figure 9 As shown, it includes:

[0352] Step 901: The UE camps on the first type of beam, the identifier of the first type of beam is preset to 15, and initiates an access request on the first type of beam.

[0353] Specifically, in this embodiment, before sending the access request, the UE can obtain system information in the manner described in Embodiment 1, which will not be repeated here for the sake of brevity.

[0354] Step 902: After receiving the UE's access request through the first type beam 15, the network allocates the second type beam to the UE.

[0355] Step 903: Within the same scanning period, the information of the allocated second type beam is sent to the UE through the downlink transmission time of the first type beam 15.

[0356] Assuming the second type of beam assigned is identified as 2, in this embodiment, the information of the second type of beam can be sent to the UE in the manner described in Embodiment 1. For the sake of brevity, it will not be repeated here.

[0357] Step 904: The UE obtains the second type beam information from the first type beam 15.

[0358] Specifically, in this embodiment, the UE can listen to the scheduling information of the first type of beam 15 and obtain the second type of beam information through MAC CE or system information as in embodiment 1, wherein the second type of beam information is the information of the second type of beam 2.

[0359] It should be noted that, in this embodiment, after obtaining the information of the second type of beam 2, it is possible to search for and synchronize with the second type of beam 2, and trigger the access process on the second type of beam 2.

[0360] It should also be noted that, in the above embodiments, the time-domain configuration information of the second type of beam includes at least one of the following:

[0361] Type II beam arrival time offset;

[0362] Synchronization signal block (SSB) mode for Category 2 beams;

[0363] The time difference between Type II beams and Type I beams.

[0364] The second type of beam arrival time offset refers to the time after which the second type of beam serves the position after the first type of beam (i.e., the aforementioned first type of beam 15) or the second first type of beam receives information about an available second type of beam. For example, if the UE obtains information about the second type of beam from the first type of beam at time T, and the second type of beam arrives at time T+offset, the UE searches for the second type of beam.

[0365] Alternatively, the arrival time offset of the second type beam refers to the offset time after the start or end time of the service of the first type beam that provides information about the available second type beam to the UE, serving that position. For example: If the UE obtains information about the second type beam on the first type beam 15, and the first type beam 15 starts serving that position at time T with a service duration of t1, then the UE obtains information about the available second type beam through the first type beam 15 during the period from T to T+t1. The second type beam arrives at T+offset or T+t1+offset and begins serving that position.

[0366] The Synchronization Signal Block (SSB) pattern for Type II beams includes: the SSB period length and / or the starting position of the SSB within that period, used to determine the location of the Type II beam's SSB occurrence. The time difference between Type II and Type I beams, such as SFN offset, slot offset, OFDM symbol offset, but not limited to these, is used to determine the synchronization of the Type II beam.

[0367] It should also be noted that the above embodiments are for obtaining second-type beam information through the same first-type beam, but do not exclude the possibility of obtaining second-type beam information through different first-type beams.

[0368] Based on the same inventive concept, embodiments of this application provide an apparatus for acquiring beam information, applied to user equipment, including:

[0369] The acquisition module is used to acquire information about the second type of beam available to the user equipment (UE) on the first type of beam it is camped on;

[0370] The processing module is used by the UE during the second type of beam-triggered access process.

[0371] In some embodiments, it further includes: a transmitting module, used by the UE to initiate an access request to the network on the first type of beam where it resides.

[0372] In other embodiments, the sending module is specifically used for:

[0373] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0374] If it is determined, based on the relevant information of the second type of beam, that there is no second type of beam available to the UE in the current network, the UE initiates an access request to the network on the first type of beam.

[0375] In the above embodiments, the information of the second type of beam includes at least one of the following:

[0376] The identifier for the second type of beam;

[0377] Second type of beam frequency domain information;

[0378] Temporal configuration information for the second type of beam;

[0379] The identifier of the first type of associated beam;

[0380] Indication that a Type II beam is in service;

[0381] Indication information for upcoming Category 2 beam service.

[0382] In another possible implementation, the acquisition module is specifically used for:

[0383] The UE receives first system information on the first type of beam it is camped on, the first system information carrying information about the second type of beam available to the UE; or...

[0384] The UE obtains relevant information about the second type of beam on the first type of beam it is camped on;

[0385] The UE obtains information about the second type of beams available to the UE based on the relevant information of the second type of beams.

[0386] In another possible implementation, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0387] Is there any indication of Category II beam coverage?

[0388] Indication information regarding whether it carries information about type 2 beams;

[0389] The UE requests configuration information for relevant network resources.

[0390] Configuration information for at least one type II beam.

[0391] The configuration information for each of the second type of beams includes at least one of the following:

[0392] The identifier for the second type of beam;

[0393] Second type of beam frequency domain information;

[0394] Temporal configuration information for the second type of beam;

[0395] Indication that a Type II beam is in service;

[0396] Indication information for upcoming Category 2 beam service.

[0397] The time-domain configuration information of the second type of beam includes at least one of the following:

[0398] Type II beam arrival time offset;

[0399] Synchronization signal block (SSB) mode for Category 2 beams;

[0400] The time difference between Type II beams and Type I beams.

[0401] In another possible implementation, the acquisition module is specifically used for:

[0402] After the UE initiates an access request to the network on the first type of beam it is camped on, or after learning from the relevant information of the second type of beam information that a second type of beam is currently covering the network, or after learning from the relevant information of the second type of beam information that it carries information about a second type of beam,

[0403] At the next downlink moment of the first type of beam during the current scanning period of the first type of beam, the UE receives third system information or MAC CE, wherein the third system information or MAC CE carries information about the second type of beam available to the UE.

[0404] The MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0405] For details not described in the device provided in this application, please refer to [the relevant documentation]. Figure 1 , Figure 3-9 The methods provided in the illustrated embodiments and the beneficial effects that the user equipment provided in this application can achieve are the same as those described in the embodiments. Figure 1 , Figure 3-9 The methods provided in the illustrated embodiments are the same and will not be repeated here.

[0406] Based on the same inventive concept, embodiments of this application also provide a device for acquiring beam information, applied to a network-side device, comprising:

[0407] The transmitting module is configured to transmit information about a second type of beam available to the UE residing in the first type of beam via a first type of beam, so that the UE can trigger an access procedure on the second type of beam.

[0408] In one possible implementation, it further includes: a receiving module for receiving an access request sent by the UE on the first type of beam.

[0409] In another possible implementation, the transmitting module is specifically used to: after receiving an access request initiated by the UE, during the downlink transmission time of the first type of beam where the UE is camped within the current scanning period of the first type of beam, transmit third system information or MACCE, wherein the third system information or the MACCE carries information about the second type of beam available to the UE.

[0410] In another possible implementation, the information of the second type of beam includes at least one of the following:

[0411] The identifier for the second type of beam;

[0412] Second type of beam frequency domain information;

[0413] Temporal configuration information for the second type of beam;

[0414] The associated first type of beam identifier;

[0415] Indication that a Type II beam is in service;

[0416] Indication information for upcoming Category 2 beam service.

[0417] In another possible implementation, the acquisition module is specifically configured to: send first system information to a UE residing in the first type of beam via a first type of beam, wherein the first system information carries information about a second type of beam available to the UE; or...

[0418] The relevant information of the second type of beam is sent to the UE camped on the first type of beam through the first type of beam, so that the UE can obtain the information of the second type of beam based on the relevant information of the second type of beam.

[0419] In another possible implementation, the relevant information of the second type of beam is carried through second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following:

[0420] Is there any indication of Category II beam coverage?

[0421] Indication information regarding whether it carries information about type 2 beams;

[0422] The UE requests configuration information for relevant network resources.

[0423] Configuration information for at least one type II beam.

[0424] The configuration information for the second type of beam includes at least one of the following:

[0425] The identifier for the second type of beam;

[0426] Second type of beam frequency domain information;

[0427] Temporal configuration information for the second type of beam;

[0428] Indication that a Type II beam is in service;

[0429] Indication information for upcoming Category 2 beam service.

[0430] The time-domain configuration information of the second beam includes at least one of the following:

[0431] Type II beam arrival time offset;

[0432] Synchronization signal block (SSB) mode for Category 2 beams;

[0433] The time difference between the second type of beam and the first type of beam.

[0434] In another possible implementation, the MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

[0435] For details not described in the device provided in this application, please refer to [the relevant documentation]. Figure 2-9 The methods provided in the illustrated embodiments and the beneficial effects that the user equipment provided in this application can achieve are the same as those described in the embodiments. Figure 2-9 The methods provided in the illustrated embodiments are the same and will not be repeated here.

[0436] Based on the same principle as the method provided in the embodiments of this application, this application provides an electronic device, which includes: a memory and a processor; at least one program stored in the memory, which, when executed by the processor, compared with the prior art, allows the UE to obtain information about its available second type of beams through the first type of beam it resides in and trigger an access process through the second type of beam. Specifically, the UE obtains information about the second type of beams that can be accessed through the relevant information of the second type of beams currently covered by the system information of the first type of beam, and / or the UE sends an access request through the first type of beam. The first type of beam carries information about the second type of beams that provide services to the UE through the system information or MAC CE, thereby solving the problem that the UE can learn about the available second type of beams through the first type of beam.

[0437] An electronic device provided in this application embodiment can be a user device or a network-side device as described in the above embodiments.

[0438] In one alternative embodiment, a user equipment is provided, such as Figure 10 As shown, Figure 10 The user equipment 100 shown includes a processor 1003 and a memory 1001. The processor 1003 and the memory 1001 are connected, for example, via a bus interface. Optionally, the user equipment 100 may further include a transceiver 1002, which can be used for data interaction between the user equipment and other devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 1002 is not limited to one type, and the structure of the user equipment 100 does not constitute a limitation on the embodiments of this application.

[0439] It should be understood that in the above embodiments, Figure 10 The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1003 and memory represented by memory 1001 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1002 can be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0440] The processor 1003 is responsible for managing the bus architecture and general processing, while the memory 1002 can store the data used by the processor 1003 when performing operations.

[0441] Optionally, the processor 1003 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0442] The processor executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling a computer program stored in memory. The processor and memory may also be physically separated.

[0443] This application provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments. Compared with the prior art, the UE obtains information about its available second-type beams through the first-type beam it is camped on and triggers an access process through the second-type beam. Specifically, the UE obtains information about the accessible second-type beams through the relevant information of the second-type beams currently covered in the system information of the first-type beam, and / or, the UE sends an access request through the first-type beam. The first-type beam carries information about the second-type beams providing services to the UE through the system information or MAC CE, thereby solving the problem of the UE knowing the accessible second-type beams through the first-type beam.

[0444] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0445] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

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

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

[0449] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0450] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0451] The above description is only a partial embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for acquiring beam information, characterized in that, The method includes: The user equipment (UE) obtains information about the second type of beam available to the UE on the first type of beam it is camped on; The UE is in the second type of beam-triggered access process; Before the UE obtains information about the second type of beam available to the UE on the first type of beam it is camped on, the method further includes: The UE initiates an access request to the network on the first type of beam it is camped on; The step of obtaining information about the second type of beam available to the UE includes: After the UE initiates an access request to the network on the first type of beam it is camped on, or after learning, based on relevant information of the second type of beam information, that a second type of beam is currently covering the network, or after learning, based on relevant information of the second type of beam information, that it carries information about a second type of beam, At the next downlink moment of the first type of beam during the current scanning period of the first type of beam, the UE receives third system information or MAC CE, wherein the third system information or MAC CE carries information about the second type of beam available to the UE.

2. The method according to claim 1, characterized in that, The UE initiates an access request to the network on the first type of beam it is camped on, including: The UE obtains relevant information about the second type of beam on the first type of beam it is camped on; If it is determined, based on the relevant information of the second type of beam, that there is no second type of beam available to the UE in the current network, the UE initiates an access request to the network on the first type of beam.

3. The method according to claim 1, characterized in that, The information for the second type of beam includes at least one of the following: The identifier for the second type of beam; Second type of beam frequency domain information; Temporal configuration information for the second type of beam; The identifier of the first type of associated beam; Indication that a Type II beam is in service; Indication information for upcoming Category 2 beam service.

4. The method according to claim 1, characterized in that, The UE obtains information about the second type of beam available to the UE on the first type of beam it is camped on, including: The UE receives first system information on the first type of beam it is camped on, the first system information carrying information about the second type of beam available to the UE; or... The UE obtains relevant information about the second type of beam on the first type of beam it is camped on; The UE obtains information about the second type of beams available to the UE based on the relevant information of the second type of beams.

5. The method according to claim 2 or 4, characterized in that, The relevant information of the second type of beam is carried through the second system information and / or the media access control layer control unit MAC CE, and the relevant information of the second type of beam includes at least one of the following: Is there any indication of Category II beam coverage? Indication information regarding whether it carries information about type 2 beams; The UE requests configuration information for relevant network resources. Configuration information for at least one type II beam.

6. The method according to claim 5, characterized in that, The configuration information for each type II beam includes at least one of the following: The identifier for the second type of beam; Second type of beam frequency domain information; Temporal configuration information for the second type of beam; Indication that a Type II beam is in service; Indication information for upcoming Category 2 beam service.

7. The method according to claim 3 or 6, characterized in that, The time-domain configuration information for the second type of beam includes at least one of the following: Type II beam arrival time offset; Synchronization signal block (SSB) mode for Category 2 beams; The time difference between Type II beams and Type I beams.

8. The method according to claim 1 or 5, characterized in that, The MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

9. A method for acquiring beam information, characterized in that, The method includes: The system sends information about the second type of beam available to the UE that is camped on the first type of beam to the UE that is camped on the first type of beam, so that the UE can trigger the access procedure on the second type of beam. Before transmitting information about the second type of beam to the UE camped on the first type of beam via the first type of beam, the process includes: Receive the access request sent by the UE on the first type of beam; The step of sending information about the second type of beam to the UE residing in the first type of beam via the first type of beam includes: Upon receiving an access request initiated by the UE, during the downlink transmission time of the first type of beam where the UE is camped within the current scanning period of the first type of beam, the third system information or MACCE is transmitted, wherein the third system information or the MACCE carries information about the second type of beam available to the UE.

10. The method according to claim 9, characterized in that, The information for the second type of beam includes at least one of the following: The identifier for the second type of beam; Second type of beam frequency domain information; Temporal configuration information for the second type of beam; The associated first type of beam identifier; Indication that a Type II beam is in service; Indication information for upcoming Category 2 beam service.

11. The method according to claim 9, characterized in that, The step of sending information about the second type of beam to the UE residing in the first type of beam via the first type of beam includes: First system information is sent to a UE residing on the first type of beam via a first type of beam, the first system information carrying information about a second type of beam available to the UE; or... The relevant information of the second type of beam is sent to the UE camped on the first type of beam through the first type of beam, so that the UE can obtain the information of the second type of beam based on the relevant information of the second type of beam.

12. The method according to claim 11, characterized in that, The relevant information of the second type of beam is carried through the second system information and / or MAC CE, and the relevant information of the second type of beam includes at least one of the following: Is there any indication of Category II beam coverage? Indication information regarding whether it carries information about type 2 beams; The UE requests configuration information for relevant network resources. Configuration information for at least one type II beam.

13. The method according to claim 12, characterized in that, The configuration information for the second type of beam includes at least one of the following: The identifier for the second type of beam; Second type of beam frequency domain information; Temporal configuration information for the second type of beam; Indication that a Type II beam is in service; Indication information for upcoming Category 2 beam service.

14. The method according to claim 10 or 13, characterized in that, The time-domain configuration information for the second type of beam includes at least one of the following: Type II beam arrival time offset; Synchronization signal block (SSB) mode for Category 2 beams; The time difference between the second type of beam and the first type of beam.

15. The method according to claim 9 or 12, characterized in that, The MAC CE is scheduled by a PDCCH scrambled by a preset RNTI.

16. A device for acquiring beam information, characterized in that, Applied to user equipment, including: The acquisition module is used to acquire information about the second type of beam available to the user equipment (UE) on the first type of beam it is camped on; The processing module is used by the UE during the second type of beam-triggered access process; The device further includes a transmitting module, which is used by the UE to initiate an access request to the network on the first type of beam on which it resides; The acquisition module is specifically used after the UE initiates an access request to the network on the first type of beam it is camped on, or after learning, based on the relevant information of the second type of beam information, that a second type of beam is currently covering the network, or after learning, based on the relevant information of the second type of beam information, that it carries information about a second type of beam. At the next downlink moment of the first type of beam during the current scanning period of the first type of beam, the UE receives third system information or MAC CE, wherein the third system information or MAC CE carries information about the second type of beam available to the UE.

17. A device for acquiring beam information, characterized in that, Applied to network-side devices, including: The transmitting module is used to transmit information about a second type of beam available to the UE camped on the first type of beam through a first type of beam, so that the UE can trigger an access procedure on the second type of beam; The device further includes a receiving module, which is used to receive an access request sent by the UE on the first type of beam; The transmitting module is specifically used to transmit third system information or MACCE at the downlink transmission time of the first type of beam where the UE is camped during the current scanning period of the first type of beam after receiving the access request initiated by the UE. The third system information or the MACCE carries information about the second type of beam available to the UE.

18. A user equipment, characterized in that, include: Memory, used to store computer programs; A transceiver is used to send and receive data under the control of a processor. Processor, configured to read the computer program in the memory and execute claim 1 The method described in any one of the 8.

19. A network-side device, characterized in that, include: Memory, used to store computer programs; A transceiver is used to send and receive data under the control of a processor. Processor, configured to read the computer program in the memory and execute claim 9 The method as described in any one of the 15.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for causing a processor to execute claim 1. The method described in any one of the 8.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for causing a processor to execute claim 9. The method as described in any one of the 15.

Images