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

Abstract

Embodiments of the present application provide a method, device and equipment for obtaining beam information, and a storage medium, relating to the technical field of communication. The method comprises: a user equipment (UE) obtaining information of at least one second first type beam on a first first type beam in which the UE is camping, the second first type beam being a first type beam on which the UE can obtain second type beam information; and obtaining information of a second type beam available to the UE on the first first type beam and / or one of the at least one second first type beam. In the method of the embodiments of the present application, the UE obtains information of at least one second first type beam on which the UE can obtain second type beam information through the first first type beam in which the UE is camping, and obtains information of a second type beam available to the UE on the first first type beam and / or one of the at least one second first type beam, thereby ensuring that the UE can obtain relevant information of a second type beam that can be accessed through the first type 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 cell system information on the initial bandwidth part (BWP) of the cell and access the cell on the initial BWP. There is no situation where the discovered cell and the accessed cell are in different working 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. The coverage of the Type 1 beam moves with the movement of the satellite. How to ensure that the UE can obtain relevant information about the Type 2 beam that can be accessed through the Type 1 beam is a problem that needs 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) acquires information of at least one second first type beam on the first first type beam it camps on, wherein the second first type beam is a first type beam on which the UE can obtain second type beam information;

[0008] On one of the first type of beam and / or at least one of the second type of beams, information about the second type of beam available to the UE is obtained.

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

[0010] The identification of the second type of beam;

[0011] Temporal information of the second type-one beam;

[0012] The identifier of the satellite containing the second type of beam;

[0013] The frequency domain information of the second type of beam.

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

[0015] The time offset between the second type-one beam and the first type-one beam;

[0016] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0017] Second type 1 beam synchronization signal block SSB mode;

[0018] The first type of beam scanning period offset N when the second type of beam appears;

[0019] The SSB mode of the satellite containing the second type of first beam;

[0020] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0021] In another possible implementation, the UE acquires information about at least one second first-type beam on the first first-type beam it is camped on, including:

[0022] The UE receives first system information on the first type of beam it is camped on, and the first system information carries information about at least one second type of beam.

[0023] In another possible implementation, the first system information also carries at least one of the following:

[0024] Duration of Type I beams;

[0025] The total number of Category I beams;

[0026] The order of appearance of the first type of beam;

[0027] The scanning period of the first type of beam;

[0028] Effective spacing of type II beams;

[0029] The first type of beam appears with the first type of beam scanning period offset N.

[0030] In another possible implementation, obtaining information about the second type of beam available to the UE on one of the first type of beam and / or at least one of the second type of beams includes:

[0031] The arrival time of at least one second type beam and / or the arrival time of the first type beam are determined based on the time-domain information of at least one second type beam and / or the information carried in the first system information.

[0032] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is acquired sequentially on the corresponding first type-1 beam in chronological order until information of a usable second type-1 beam is acquired.

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

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

[0035] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0036] The identifier of the satellite containing the second type of beam;

[0037] Frequency domain information of the associated first-type beam;

[0038] The identifier of the satellite to which the first type of beam is associated.

[0039] In another possible implementation, before obtaining information about the second type of beam available to the UE on the first type of beam and / or at least one of the second type of beams, the following steps are included:

[0040] The UE initiates an access request to the network on the first type of beam.

[0041] In another possible implementation, the method further includes at least one of the following operations:

[0042] A timer is started at a first preset time, and the duration of the timer is the effective interval of the second type of beam.

[0043] The timer is stopped at a second preset time.

[0044] The timer expires, indicating that the UE access has failed.

[0045] Wherein, the first preset time is at least one of the following:

[0046] When the UE sends an access request;

[0047] When the UE begins searching for Type II beams;

[0048] When the UE obtains available Type II beam information;

[0049] When the UE begins to acquire second type beam information for each second type first beam or the first type first beam;

[0050] When the UE arrives at each of the second type 1 beams or the first type 1 beam;

[0051] The second preset time is at least one of the following:

[0052] The UE successfully synchronized to the second type of beam;

[0053] The UE successfully obtained information about the available Type 2 beams;

[0054] The UE successfully connected to the second type of beam.

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

[0056] Send information about at least one second type of beam to the UE camped on the first type of beam;

[0057] Information about the second type of beam is transmitted to the UE through the first type of beam and / or at least one of the second type of beams.

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

[0059] The identification of the second type of beam;

[0060] Temporal information of the second type-one beam;

[0061] The identifier of the satellite containing the second type of beam;

[0062] The frequency domain information of the second type of beam.

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

[0064] The time offset between the second type-one beam and the first type-one beam;

[0065] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0066] Second type 1 beam synchronization signal block SSB mode;

[0067] The first type of beam scanning period offset N when the second type of beam appears;

[0068] The SSB mode of the satellite containing the second type of first beam;

[0069] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0070] In another possible implementation, transmitting information about at least one second first-type beam to the UE residing in the first first-type beam includes:

[0071] First system information is transmitted to a UE camped on a first type of beam, the first system information carrying information of at least one second type of beam.

[0072] In another possible implementation, the first system information also carries at least one of the following:

[0073] Duration of Type I beams;

[0074] The total number of Category I beams;

[0075] The order of appearance of the first type of beam;

[0076] The scanning period of the first type of beam;

[0077] Effective spacing of type II beams;

[0078] The first type of beam appears with the first type of beam scanning period offset N.

[0079] In another possible implementation, information about a second type of beam is transmitted to the UE via the first first type of beam and / or at least one second first type of beam, including:

[0080] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is transmitted sequentially on the corresponding first type-1 beam in chronological order.

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

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

[0083] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0084] The identifier of the satellite containing the second type of beam;

[0085] Frequency domain information of the associated first-type beam;

[0086] The identifier of the satellite to which the first type of beam is associated.

[0087] In another possible implementation, before transmitting information about the second type of beam available to the UE on the first first type beam and / or at least one second first type beam, the following is included:

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

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

[0090] The first acquisition module is used to acquire information of at least one second first type beam on the first first type beam on which the user equipment (UE) is camped, wherein the second first type beam is a first type beam on which the UE can acquire second type beam information;

[0091] The second acquisition module is used to acquire information about the second type of beam available to the UE on one of the first type of beam and / or at least one of the second type of beams.

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

[0093] The identification of the second type of beam;

[0094] Temporal information of the second type-one beam;

[0095] The identifier of the satellite containing the second type of beam;

[0096] The frequency domain information of the second type of beam.

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

[0098] The time offset between the second type-one beam and the first type-one beam;

[0099] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0100] Second type 1 beam synchronization signal block SSB mode;

[0101] The first type of beam scanning period offset N when the second type of beam appears;

[0102] The SSB mode of the satellite containing the second type of first beam;

[0103] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0104] In another possible implementation, the first acquisition module is specifically used for the UE to receive first system information on the first type of beam it is camped on, wherein the first system information carries information of at least one second type of beam.

[0105] In another possible implementation, the first system information also carries at least one of the following:

[0106] Duration of Type I beams;

[0107] The total number of Category I beams;

[0108] The order of appearance of the first type of beam;

[0109] The scanning period of the first type of beam;

[0110] Effective spacing of type II beams;

[0111] The first type of beam appears with the first type of beam scanning period offset N.

[0112] In another possible implementation, the second acquisition module is specifically used to determine the arrival time of at least one second first type beam and / or the arrival time of the first first type beam based on the time domain information of at least one second first type beam and / or the information carried in the first system information.

[0113] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is acquired sequentially on the corresponding first type-1 beam in chronological order until information of a usable second type-1 beam is acquired.

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

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

[0116] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0117] The identifier of the satellite containing the second type of beam;

[0118] Frequency domain information of the associated first-type beam;

[0119] The identifier of the satellite to which the first type of beam is associated.

[0120] In another 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.

[0121] In another possible implementation, a processing module is also included to perform at least one of the following operations:

[0122] A timer is started at a first preset time, and the duration of the timer is the effective interval of the second type of beam.

[0123] The timer is stopped at a second preset time.

[0124] The timer expires, indicating that the UE access has failed.

[0125] Wherein, the first preset time is at least one of the following:

[0126] When the UE sends an access request;

[0127] When the UE begins searching for Type II beams;

[0128] When the UE obtains available Type II beam information;

[0129] When the UE begins to acquire second type beam information for each second type first beam or the first type first beam;

[0130] When the UE arrives at each of the second type 1 beams or the first type 1 beam;

[0131] The second preset time is at least one of the following:

[0132] The UE successfully synchronized to the second type of beam;

[0133] The UE successfully obtained information about the available Type 2 beams;

[0134] The UE successfully connected to the second type of beam.

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

[0136] The first transmitting module is used to transmit information of at least one second first type beam to the UE camped on the first first type beam;

[0137] The second transmitting module is configured to transmit information of the second type of beam to the UE through the first type of beam and / or at least one of the second type of beams.

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

[0139] The identification of the second type of beam;

[0140] Temporal information of the second type-one beam;

[0141] The identifier of the satellite containing the second type of beam;

[0142] The frequency domain information of the second type of beam.

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

[0144] The time offset between the second type-one beam and the first type-one beam;

[0145] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0146] Second type 1 beam synchronization signal block SSB mode;

[0147] The first type of beam scanning period offset N when the second type of beam appears;

[0148] The SSB mode of the satellite containing the second type of first beam;

[0149] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0150] In another possible implementation, the first transmitting module is specifically used to transmit first system information to a UE camped on a first type of beam, the first system information carrying information of at least one second type of beam.

[0151] In another possible implementation, the first system information also carries at least one of the following:

[0152] Duration of Type I beams;

[0153] The total number of Category I beams;

[0154] The order of appearance of the first type of beam;

[0155] The scanning period of the first type of beam;

[0156] Effective spacing of type II beams;

[0157] The first type of beam appears with the first type of beam scanning period offset N.

[0158] In another possible implementation, the second transmitting module is specifically used to transmit information of the second type beam sequentially on the corresponding first type beam in chronological order at the arrival time of at least one of the second first type beams and / or the arrival time of the first first type beam.

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

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

[0161] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0162] The identifier of the satellite containing the second type of beam;

[0163] Frequency domain information of the associated first-type beam;

[0164] The identifier of the satellite to which the first type of beam is associated.

[0165] In another possible implementation, a receiving module is also included, for receiving access requests sent by the UE on the first type of beam.

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

[0167] Memory, used to store computer programs;

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

[0169] 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.

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

[0171] Memory, used to store computer programs;

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

[0173] 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.

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

[0175] 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.

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

[0177] The UE obtains information about at least one second first-class beam through the first first-class beam where it can obtain information about the second-class beam, and obtains information about the available second-class beam on one of the first first-class beams and / or at least one second first-class beam, thereby ensuring that the UE can obtain relevant information about the second-class beams that can be accessed through the first-class beam. Attached Figure Description

[0178] 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.

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

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

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

[0182] Figure 4 This application provides a schematic diagram of the structure of a user equipment according to an embodiment of the present application.

[0183] Figure 5 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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).

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

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] 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, while 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, for example, 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.

[0194] 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.

[0195] The satellite moves periodically along a fixed trajectory. One method of coverage using the first type of beam is to illuminate the ground at a fixed angle; in this case, the first type of beam, identified by beam identifier 'n', moves across the ground at a fixed speed to provide coverage. Another method is for the satellite to adjust its illumination angle to always illuminate a fixed location on the ground until the satellite moves out of its coverage area. In other words, the first type of beam, identified by beam identifier 'n', always covers a fixed location on the ground during the satellite's coverage period.

[0196] Because the beam types serving connected and disconnected UEs differ, a disconnected UE, when needing to access the satellite system, must send a request message via the first type beam to request network access and obtain information about accessible second type beams through the first type beam. Considering that after the UE sends the access request via the first type beam n, it may need to wait until the next beam scan cycle, after the first type beam n returns to coverage, to obtain the network-sent second type beam information. Since the coverage area of ​​the first type beam may shift with satellite movement, the UE might be located at the edge of the first type beam n when sending the access request, and when the first type beam n arrives again in the next beam scan cycle, the UE may no longer be within its coverage area. Ensuring that the UE can obtain accessible second type beam information through the first type beam remains to be solved.

[0197] Therefore, in the method for obtaining beam information in this application embodiment, the UE obtains information of at least one second first-class beam through the first first-class beam where it is camped, and obtains information of the available second-class beam on one of the first first-class beams and / or at least one second first-class beam, thereby ensuring that the UE knows the relevant information of the second-class beams that can be accessed through the first-class beam.

[0198] Specifically, the satellite can determine, through its motion trajectory, one or more second-type first-order beams that will cover the first position in the next beam scanning cycle. The first position is the position covered by the first-type first-order beam to which the UE is currently camped. The satellite then notifies the UE of the information of the second-type first-order beam. After the UE sends an access request through the first-type first-order beam, the satellite carries the frequency domain information and / or time domain information of the second-type beam serving the UE through system information or the Media Access Control Element (MAC CE) in the first-type first-order beam or the second-type first-order beam notified by the network.

[0199] 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.

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

[0201] S101. The user equipment (UE) obtains information of at least one second first type beam on the first first type beam it camps on, wherein the second first type beam is a first type beam on which the UE can obtain second type beam information.

[0202] S102. On one of the first type of beams and / or at least one of the second type of beams, obtain information about the second type of beams available to the UE.

[0203] In other words, in this embodiment, the network can obtain information about at least one first-type beam on a first-type beam where the UE is camped, and then the UE can attempt to obtain information about the second-type beam available to the UE on the camped first-type beam, or the UE can attempt to obtain information about the second-type beam available to the UE on at least one first-type beam obtained by the UE, or the UE can attempt to obtain information about the second-type beam available to the UE on both the camped first-type beam and the obtained at least one first-type beam.

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

[0205] The identification of the second type of beam;

[0206] Temporal information of the second type-one beam;

[0207] The identifier of the satellite containing the second type of beam;

[0208] The frequency domain information of the second type of beam.

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

[0210] The time offset between the second type-one beam and the first type-one beam;

[0211] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0212] Second type 1 beam synchronization signal block SSB mode;

[0213] The first type of beam scanning period offset N when the second type of beam appears;

[0214] The SSB mode of the satellite containing the second type of first beam;

[0215] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0216] The SSB pattern may include the SSB cycle length and / or the starting position of the SSB within that cycle.

[0217] In one possible implementation, S101 may specifically include:

[0218] The UE receives first system information on the first type of beam it is camped on, and the first system information carries information about at least one second type of beam.

[0219] In other words, in this embodiment, information of at least one second first type beam carried in the system information is obtained by receiving system information on a first type beam where the UE resides.

[0220] In some embodiments, the first system information further includes at least one of the following:

[0221] The duration of the first type of beam; the duration can be the dwell time at each position, for example: the dwell time of the first type of beam at each position is 5ms.

[0222] The total number of Type I beams; for example: there are 500 Type I beams.

[0223] The order in which the first type of beams appear; for example: there are 500 first type beams, labeled 0-499 respectively. The order in which the first type of beams appear can be in ascending order of labels or in a specified order.

[0224] The scanning period of the first type of beam; for example: the scanning period of the first type of beam is 2.5s.

[0225] Effective spacing of type II beams;

[0226] The offset N of the first type of beam scan period when the second type of beam appears. That is, the UE sends a request message to the first type of beam in the first scan period n, and the UE obtains the information of the second type of beam in the second type of beam after an interval of N or N-1 scan periods, that is, in the n+N+1 or n+N scan period.

[0227] In another possible implementation, prior to S101, the method further includes:

[0228] S100, the UE initiates an access request to the network on the first type of beam.

[0229] In other words, in this embodiment, the UE can initiate an access request to the network on a first type beam it is camped on. After receiving the access request, the network can allocate a second type beam available to the UE and transmit the information of the second type beam through system information or MAC CE.

[0230] It should be noted that, in this embodiment, before the UE initiates an access request to the network on its camped first-type beam, it can receive system information broadcast by the network on the camped first-type beam. This system information carries information about at least one first-type beam on which the UE can obtain second-type beam information. The UE can attempt to receive system information or MAC CE on its camped first-type beam and / or on at least one acquired first-type beam, and obtain information about a second-type beam available to the UE on one of the first-type beams.

[0231] In another possible implementation, S102 may specifically include:

[0232] The arrival time of at least one second type beam and / or the arrival time of the first type beam are determined based on the time-domain information of at least one second type beam and / or the information carried in the first system information.

[0233] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is acquired sequentially on the corresponding first type-1 beam in chronological order until information of a usable second type-1 beam is acquired.

[0234] In other words, in this embodiment, the UE may attempt to acquire information of the second type beam sequentially on the first type beam at the arrival time of at least one second type beam and / or the arrival time of the first type beam, until it successfully acquires information of the available second type beam or until it attempts to acquire information of the second type beam on the last first type beam. Whichever of the above processes occurs first, the UE will stop acquiring information of the second type beam.

[0235] For example, the arrival times of the first type 1 beam 15 and at least one second type 1 beam 14, 16 are in the following order: first type 1 beam 14, 15, 16. If the UE fails to synchronize with the first type 1 beam 14 or fails to obtain the relevant information of the second type 2 beam, the UE continues to synchronize with the first type 1 beam 15. If the UE successfully synchronizes with the first type 1 beam 15 and obtains the relevant information of the second type 2 beam, the synchronization with the first type 1 beam 16 is stopped.

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

[0237] 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 responded to the access request sent through the first-type beam. For example, if the UE initiates an access request through the first-type beam 2, and the network receives the access request and schedules the second-type beam 4 for the UE, then the identifier of the associated first-type beam of the second-type beam 4 is configured as 2.

[0238] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0239] The identifier of the satellite containing the second type of beam;

[0240] Frequency domain information of the associated first-type beam;

[0241] The identifier of the satellite to which the first type of beam is associated.

[0242] In some alternative embodiments, the method may further include at least one of the following operations:

[0243] A timer is started at a first preset time, and the duration of the timer is the effective interval of the second type of beam.

[0244] The timer is stopped at a second preset time.

[0245] If the timer times out, it is determined that the UE access has failed.

[0246] Wherein, the first preset time is at least one of the following:

[0247] When the UE sends an access request;

[0248] When the UE begins searching for Type II beams;

[0249] When the UE obtains available Type II beam information;

[0250] When the UE begins to acquire second type beam information for each second type first beam or the first type first beam;

[0251] When the UE arrives at each of the second type 1 beams or the first type 1 beams.

[0252] The second preset time is at least one of the following:

[0253] The UE successfully synchronized to the second type of beam;

[0254] The UE successfully obtained information about the available Type 2 beams;

[0255] The UE successfully connected to the second type of beam.

[0256] In other words, a timer can be set to determine whether a UE has successfully accessed the network.

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

[0258] S201. Send information about at least one second type of beam to the UE camped on the first type of beam;

[0259] S202. Send information about the second type of beam to the UE through the first type of beam and / or at least one type of second beam.

[0260] In some optional embodiments, prior to S201, the method may include:

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

[0262] In other words, in this embodiment, after receiving an access request sent by the UE on the first type of beam, the network side can allocate a second type of beam available to the UE and transmit the information of the second type of beam through system information or MAC CE.

[0263] It should be noted that, in this embodiment, before receiving an access request initiated by the UE on a first-type beam where it is camped, system information can be broadcast on that first-type beam. This system information carries information about at least one first-type beam on which the UE can obtain second-type beam information. When the network transmits the second-type beam information via system information or MAC CE, it can send system information or MAC CE carrying the second-type beam information on one of the first-type beams where the UE is camped, and / or at least one first-type beam, so that the UE can obtain the second-type beam information available to the UE on one of the first-type beams.

[0264] In one possible implementation, the information of the second type-1 beam includes at least one of the following:

[0265] The identification of the second type of beam;

[0266] Temporal information of the second type-one beam;

[0267] The identifier of the satellite containing the second type of beam;

[0268] The frequency domain information of the second type of beam.

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

[0270] The time offset between the second type-one beam and the first type-one beam;

[0271] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0272] Second type 1 beam synchronization signal block SSB mode;

[0273] The first type of beam scanning period offset N when the second type of beam appears;

[0274] The SSB mode of the satellite containing the second type of first beam;

[0275] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0276] The SSB pattern may include the SSB cycle length and / or the starting position of the SSB within that cycle.

[0277] In some alternative embodiments, S201 may specifically include: transmitting first system information to a UE camped on a first type of beam, the first system information carrying information of at least one second type of beam.

[0278] In some embodiments, the first system information further includes at least one of the following:

[0279] The duration of the first type of beam; the duration can be the dwell time at each position, for example: the dwell time of the first type of beam at each position is 5ms.

[0280] The total number of Category I beams;

[0281] The order of appearance of the first type of beam;

[0282] The scanning period of the first type of beam;

[0283] Effective spacing of type II beams;

[0284] The first type of beam appears with the first type of beam scanning period offset N.

[0285] In some alternative embodiments, S202 may specifically include:

[0286] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is transmitted sequentially on the corresponding first type-1 beam in chronological order.

[0287] Specifically, in this embodiment, the arrival time of at least one second first-type beam and / or the arrival time of the first first-type beam can be determined by the time-domain information of at least one second first-type beam and / or the information carried in the first system information.

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

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

[0290] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0291] The identifier of the satellite containing the second type of beam;

[0292] Frequency domain information of the associated first-type beam;

[0293] The identifier of the satellite to which the first type of beam is associated.

[0294] In summary, the method for obtaining beam information provided in this application embodiment allows the UE to obtain information about at least one second first-type beam through the first first-type beam it camps on, and to obtain information about the available second-type beam on one of the first first-type beams and / or at least one second first-type beam, thereby ensuring that the UE can obtain relevant information about the second-type beams that can be accessed through the first-type beam.

[0295] The following example illustrates the specific implementation process of a method for obtaining beam information provided in this application embodiment: “The satellite system is pre-defined to be 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.”

[0296] Example 1: The UE obtains the second type of beam information through the designated first type of beam.

[0297] like Figure 3 The methods shown include:

[0298] Step 300: 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 on the first type of beam 15.

[0299] The system information may include information about at least one second first-type beam that the UE can obtain second-type beam information, wherein the information about each second first-type beam includes at least one of the following:

[0300] The identification of the second type of beam;

[0301] Temporal information of the second type-one beam;

[0302] The identifier of the satellite where the second type of beam is located. For example, if the UE may move out of the coverage area of ​​the satellite where the first type of beam is located, this identifier is the identifier of the satellite where the second type of beam is located, which allows the UE to obtain information about the second type of beam.

[0303] The frequency domain information of the second type of beam, for example, the UE may move out of the coverage area of ​​the satellite where the first type of beam is located. The frequency domain information of the first type of beam is the frequency point of the second type of beam that the UE can obtain the second type of beam information.

[0304] Assuming that this embodiment uses two second type-1 beams as an example, for instance, the second type-1 beams are identified as 14 and 16.

[0305] 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 in the first type of beam.

[0306] 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.

[0307] Step 303: The network can obtain the second type beam information of the second type beam 14, 16 through the first type beam 15 and one or more UEs broadcasting the system information in step 301, and send the information of the second type beam to the UE.

[0308] Assuming the identifier for the assigned second type of beam is 2, the information for the second type of beam may further include:

[0309] The identifier of the first type of beam indicates the identifier information of the first type of beam that the network corresponding to the second type of beam receives the access request for. The second type of beam is the second type of beam that responds to the access request sent through the first type of beam. In this embodiment, the identifier of the first type of beam is 15.

[0310] If the second type beam is an indication information of the second type beam that responds to the access request sent through the current first type beam, it can be implicitly carried or explicitly carried. The implicit method can be implemented by not carrying the first type beam identifier, while the explicit method carries the indication information. For example, when the second type beam information is sent through the first type beam 15, one implementation is to not carry the first type beam identifier, and another implementation is to carry the indication information. The indication information indicates that the second type beam is the second type beam that responds to the access request sent through the current first type beam, or it can be notified by carrying the identifier of the first type beam as 15.

[0311] In this embodiment, the satellite identifier corresponds to the identifier of the satellite that the UE sends the access request to, that is, the identifier of the satellite where the first type of beam is located. If the network calculates that the UE has moved outside the coverage area of ​​the satellite, the satellite identifier can be the identifier of the next satellite covering this beam (i.e., the beam that the first type of beam is currently scanning).

[0312] The frequency domain information of the first type of beam, in this embodiment, corresponds to the frequency point of the first type of beam when the UE sends the access request. If the network calculates that the UE has moved to the coverage area of ​​the satellite, the frequency domain information of the first type of beam can be the frequency domain information of the first type of beam of the next satellite covering this frequency position.

[0313] Step 304: The UE obtains information about the second type of beam available to the UE on one of the first type of beam and / or at least one second type of beam.

[0314] Specifically, in this embodiment, the UE learns from step 301 that it can obtain information about the relevant second type beams 14, 16 and / or the first type beam 15, and based on the time-domain information of the second type beams and / or other information in the system information from step 301, the UE learns the arrival times of the second type beams 14, 16. The UE obtains the relevant information about the second type beams through the second type beams 14, 16 and / or the first type beams at the arrival times of the second type beams 14, 16.

[0315] In other words, the UE always needs to try to obtain the second type beam information from the first type beam that sends the access request and the second type beam that broadcasts the system information, or simply obtain the second type beam information from the second type beam that broadcasts the system information.

[0316] When the UE scans the first type of beams 14, 15, and 16, it synchronizes with the corresponding first type of beam and listens to its PDCCH scheduling to obtain the second type of beam information, wherein the second type of beam information is the information of the second type of beam 2.

[0317] It should be noted that once the UE obtains the second type of beam information, it will stop trying to obtain the second type of beam information on other first type beams. For example, if the arrival times of the three first type beams are 14, 15, and 16 respectively, and the UE fails to synchronize to the first type beam 14 or fails to obtain the second type of beam information, then the UE will continue to synchronize to the first type beam 15. If the UE successfully synchronizes to the first type beam 15 and obtains the second type of beam information, it will stop synchronizing to the first type beam 16.

[0318] It should be understood that, in this embodiment, before sending an access request, the UE obtains system information in the first type of beam 15. The system information may also include basic information of five second type beams or basic information of at least one second type beam (i.e., the system information may include basic information of all second type beams, or basic information of second type beams that may be scheduled to this beam position). The basic information of each second type beam includes at least one of the following:

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

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

[0321] Temporal configuration information for the second type of beam.

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

[0323] Alternatively, before initiating an access request, the UE may also obtain configuration information of relevant network resources requested for network access through the system information of the first type-one beam. One possible implementation is to transmit sequences on network-configured resources, for example, transmitting a specified preamble on a configured Random Access Channel (RACH) resource.

[0324] As an optional embodiment, in step 303, the network can obtain the second first type beam 14, 16 of the second type beam information through the first type beam 15 and one or more UEs broadcasting the system information in step 301, and send the information of the second type beam 2 to the UE through MAC CE.

[0325] 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.

[0326] The specific methods by which the MAC CE carries the second type of beam information may include the following:

[0327] 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 second type beam identifier with the system information.

[0328] 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.

[0329] 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.

[0330] 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.

[0331] As another optional embodiment, in step 303, the network can obtain the second first type beam 14, 16 of the second type beam information through the first type beam 15 and one or more UEs broadcasting the system information in step 301, and send the information of the second type beam 2 to the UE through the system information.

[0332] The specific methods by which the system information carries the second type of beam information may include the following:

[0333] Method 2-1: If the system information in step 301 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 identifier of the second type beam with the part of the access information of the second type beam broadcast by the system information.

[0334] Method 2-2: If the system information in step 301 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 identifier of the second type of beam 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.

[0335] Method 2-3: If the system information in step 301 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.

[0336] Method 2-4: If the system information in step 301 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.

[0337] In addition to the above information, optionally, the basic information of the second type beam may also include indication information that the second type beam is about to be served or indication information that the second type beam is currently being served.

[0338] As another optional embodiment, the time-domain information of the second first-type beam may include at least one of the following:

[0339] The time offset between the second type I beam and the first type I beam, that is, if the arrival time of the first type I beam is T, then the second type I beam will arrive at time T+offset.

[0340] The time offset between the second type 1 beam and the first type 1 beam within the same scanning period, that is, within the same scanning period, the first type 1 beam arrives at time T, and the second type 1 beam arrives at time T+offset after the arrival time of the first type 1 beam;

[0341] The synchronization signal block (SSB) mode for the second type of beam can include the SSB period length and / or the starting position of the SSB within that period, thereby determining the position of the second type of beam within the scanning period of the first type of beam. The scanning period offset N for the second type of beam is determined by the UE sending a request message to the first type of beam in scanning period n. After an interval of N or N-1 scanning periods, i.e., in the (n+N+1)th or (n+N)th scanning period, the UE obtains information about the second type of beam. For example, in this embodiment, N = 1. The second type of beam appears in the (N+1)th scanning period of the first type of beam, i.e., in the next scanning period.

[0342] The second is the SSB pattern of the satellite containing the first type beam. The SSB pattern may include: the scanning period of the first type beam of the satellite, and the starting position of each first type beam within the period.

[0343] The synchronization deviation between the satellite containing the second type 1 beam and the satellite containing the first type 1 beam (slot boundary alignment deviation or SFN boundary alignment deviation, sign alignment deviation may include any one or more of the following: SFN deviation, slot deviation, OFDM sign deviation, but not limited to the above)

[0344] Optionally, the system information may also include at least one of the following:

[0345] The duration of the first type of beam, for example, 5ms in this embodiment;

[0346] The total number of the first type of beams, for example: 500 in this embodiment;

[0347] The order in which the first type of beams appears, for example, in this embodiment, 500 first type beams appear in the order of their indexes, that is, 0, 1, 2, ..., 499.

[0348] The scan period offset N for the second type of beam is defined as follows: the UE sends a request message to the first type of beam in scan period n, and the UE obtains information about the second type of beam after an interval of N or N-1 scan periods, i.e., in the (n+N+1)th or (n+N)th scan period. For example, in this embodiment, N=1. The second type of beam appears in the (N+1)th scan period of the first type of beam, i.e., in the next scan period.

[0349] In step 304, the arrival times of the second first-type beams 14 and 16 can be determined based on the time-domain information and / or other information in the system information of the second first-type beam in step 301, including the following methods:

[0350] Method 1: Obtain the arrival time of the first type beams 14 and 16 by using the time domain offset of the second type beams 14 and 16. Then, determine the time offset between the second type beam and the first type beam. If the arrival time of the first type beam is T, then the second type beam will arrive after T+offset time.

[0351] Method 2: The time offset between the second type 1 beam and the first type 1 beam within the same scanning period, that is, within the same scanning period, the first type 1 beam arrives at time T, and the second type 1 beam arrives at time T+offset after the arrival time of the first type 1 beam, thus obtaining the arrival times of type 1 beams 14 and 16.

[0352] Method 3: Based on the SSB pattern of the second type beam 14, 16 in the time domain information of the second type beam 14, 16, the arrival time of the first type beam 14, 16 is obtained.

[0353] Method 4: Based on the number of first-type beams or the period of the first-type beams, the order of appearance of the first-type beams, and the duration of the first-type beams broadcast by the system, the arrival times of the first-type beams 14 and 16 can be determined.

[0354] Method 5: Based on the number of first-type beams or the period of the first-type beams broadcast by the system information and the location of the SSB pattern of the second first-type beams 14 and 16 in the time domain information, the arrival time of the first-type beams 14 and 16 can be determined.

[0355] Method 6: The appearance time of the second type-1 beam on its satellite is determined by the SSB pattern (including period and / or specific SSB occurrence position) of the satellite where the second type-1 beam is located, and / or the synchronization deviation (slot boundary alignment deviation or SFN boundary alignment deviation or sign alignment deviation) between the satellite where the second type-1 beam is located and the satellite where the first type-1 beam is located.

[0356] It should be noted that, using the above method 1, the UE can obtain the relevant information of the second type of beam through the corresponding first type of beam at the corresponding time.

[0357] For any of the methods 2-5 above, the UE always obtains the information related to the second type of beam through the first type of beams 14, 16, and / or 15 in the next beam scanning cycle. Alternatively, if step 301 also includes a scanning cycle offset N for the occurrence of the second first type of beam, for example, N is 2, then the UE determines to obtain the information related to the second type of beam through the first type of beams 14, 16, and / or 15 in the second scanning cycle after the current scanning cycle.

[0358] It should also be noted that one implementation is that the UE always needs to try to obtain the second type beam information from the first type beam that sends the access request and the second type beam that broadcasts the system information. That is, even if the second type beam broadcasts the system information does not contain the identifier of the first type beam, the UE still needs to try to obtain the second type beam information from the first type beam. Another implementation is that the UE only obtains the second type beam information from the second type beam broadcasts the system information. If the network wants the UE to obtain the second type beam information from the first type beam, then the second type beam needs to contain the identifier of the first type beam, that is, the second type beam is equal to the identifier of the first type beam.

[0359] Example 2: UE access success or abnormal scenario

[0360] Successful scenario: After obtaining the second type of beam information according to Embodiment 1 above, the UE determines the frequency domain information and / or the time domain information of the second type of beam. The UE searches for the corresponding second type of beam frequency at the corresponding time, synchronizes to that frequency, obtains the corresponding system information, and accesses the second type of beam. The frequency domain information can be the frequency domain location of the SSB.

[0361] Abnormal scenario: Before or while obtaining the second type of beam information, the UE may also obtain the effective interval information T', i.e., the effective time of the second type of beam, through the system information of the first type of beam or MAC CE. When the effective time expires, if the UE fails to search for the second type of beam or fails to access the second type of beam, the UE considers the access to have failed. The specific implementation method is as follows:

[0362] The UE starts a timer when it receives the second type of beam information; or,

[0363] The UE starts a timer when it initiates an access request; or,

[0364] A timer is started when the UE begins searching for the second type of beam; for example, if the information for the second type of beam carries an arrival time offset, the search for that second type of beam begins at the moment of its arrival, thus starting the timer. Alternatively,

[0365] The UE starts a timer when it begins acquiring information about the second type of beam for each second type of beam or the first type of beam; or,

[0366] The UE starts a timer when each second type I beam or first type I beam arrives.

[0367] The timer duration is the effective interval of the second type of beam. For example, if the timer duration is T', the timer T' will be turned off when the UE successfully synchronizes with the second type of beam 2, or successfully accesses the second type of beam 2, or successfully obtains the information of the second type of beam. Otherwise, the access is considered to have failed if the timer times out.

[0368] The method described in this application embodiment is also applicable to scenarios where the satellite coverage area moves relative to the ground, or where the satellite coverage moves with the ground.

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

[0370] The first acquisition module is used to acquire information of at least one second first type beam on the first first type beam on which the user equipment (UE) is camped, wherein the second first type beam is a first type beam on which the UE can acquire second type beam information;

[0371] The second acquisition module is used to acquire information about the second type of beam available to the UE on one of the first type of beam and / or at least one of the second type of beams.

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

[0373] The identification of the second type of beam;

[0374] Temporal information of the second type-one beam;

[0375] The identifier of the satellite containing the second type of beam;

[0376] The frequency domain information of the second type of beam.

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

[0378] The time offset between the second type-one beam and the first type-one beam;

[0379] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0380] Second type 1 beam synchronization signal block SSB mode;

[0381] The first type of beam scanning period offset N when the second type of beam appears;

[0382] The SSB mode of the satellite containing the second type of first beam;

[0383] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0384] In another possible implementation, the first acquisition module is specifically used for the UE to receive first system information on the first type of beam it is camped on, wherein the first system information carries information of at least one second type of beam.

[0385] In another possible implementation, the first system information also carries at least one of the following:

[0386] Duration of Type I beams;

[0387] The total number of Category I beams;

[0388] The order of appearance of the first type of beam;

[0389] The scanning period of the first type of beam;

[0390] Effective spacing of type II beams;

[0391] The first type of beam appears with the first type of beam scanning period offset N.

[0392] In another possible implementation, the second acquisition module is specifically used to determine the arrival time of at least one second first type beam and / or the arrival time of the first first type beam based on the time domain information of at least one second first type beam and / or the information carried in the first system information.

[0393] At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is acquired sequentially on the corresponding first type-1 beam in chronological order until information of a usable second type-1 beam is acquired.

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

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

[0396] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0397] The identifier of the satellite containing the second type of beam;

[0398] Frequency domain information of the associated first-type beam;

[0399] The identifier of the satellite to which the first type of beam is associated.

[0400] In another 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.

[0401] In another possible implementation, a processing module is also included to perform at least one of the following operations:

[0402] A timer is started at a first preset time, and the duration of the timer is the effective interval of the second type of beam.

[0403] The timer is stopped at a second preset time.

[0404] The timer expires, indicating that the UE access has failed.

[0405] Wherein, the first preset time is at least one of the following:

[0406] When the UE sends an access request;

[0407] When the UE begins searching for Type II beams;

[0408] When the UE obtains available Type II beam information;

[0409] When the UE begins to acquire second type beam information for each second type first beam or the first type first beam;

[0410] When the UE arrives at each of the second type 1 beams or the first type 1 beam;

[0411] The second preset time is at least one of the following:

[0412] The UE successfully synchronized to the second type of beam;

[0413] The UE successfully obtained information about the available Type 2 beams;

[0414] The UE successfully connected to the second type of beam.

[0415] For details not described in the device provided in this application, please refer to [the relevant documentation]. Figure 1 and Figure 3 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 and Figure 3 The methods provided in the illustrated embodiments are the same and will not be repeated here.

[0416] 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:

[0417] The first transmitting module is used to transmit information of at least one second first type beam to the UE camped on the first first type beam;

[0418] The second transmitting module is configured to transmit information of the second type of beam to the UE through the first type of beam and / or at least one of the second type of beams.

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

[0420] The identification of the second type of beam;

[0421] Temporal information of the second type-one beam;

[0422] The identifier of the satellite containing the second type of beam;

[0423] The frequency domain information of the second type of beam.

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

[0425] The time offset between the second type-one beam and the first type-one beam;

[0426] The time offset between the second type I beam and the first type I beam within the same type I beam scanning period;

[0427] Second type 1 beam synchronization signal block SSB mode;

[0428] The first type of beam scanning period offset N when the second type of beam appears;

[0429] The SSB mode of the satellite containing the second type of first beam;

[0430] The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

[0431] In another possible implementation, the first transmitting module is specifically used to transmit first system information to a UE camped on a first type of beam, the first system information carrying information of at least one second type of beam.

[0432] In another possible implementation, the first system information also carries at least one of the following:

[0433] Duration of Type I beams;

[0434] The total number of Category I beams;

[0435] The order of appearance of the first type of beam;

[0436] The scanning period of the first type of beam;

[0437] Effective spacing of type II beams;

[0438] The first type of beam appears with the first type of beam scanning period offset N.

[0439] In another possible implementation, the second transmitting module is specifically used to transmit information of the second type beam sequentially on the corresponding first type beam in chronological order at the arrival time of at least one of the second first type beams and / or the arrival time of the first first type beam.

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

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

[0442] The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam;

[0443] The identifier of the satellite containing the second type of beam;

[0444] Frequency domain information of the associated first-type beam;

[0445] The identifier of the satellite to which the first type of beam is associated.

[0446] In another possible implementation, a receiving module is also included, for receiving access requests sent by the UE on the first type of beam.

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

[0448] Based on the same principle as the method provided in the embodiments of this application, an electronic device is provided in the embodiments of this application. The electronic device 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 of at least one second first-type beam through the first first-type beam on which it resides, and to obtain information of the available second-type beam on one of the first first-type beams and / or at least one second first-type beam, thereby ensuring that the UE can obtain relevant information of the second-type beams that can be accessed through the first-type beam.

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

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

[0451] It should be understood that in the above embodiments, Figure 4The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 403 and memory represented by memory 401 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. Transceiver 402 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, and other transmission media.

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

[0453] In another alternative embodiment, a network-side device is provided, such as Figure 5 As shown, Figure 5 The network-side device 50 shown includes a processor 503 and a memory 501. The processor 503 and the memory 501 are connected, for example, via a bus interface. Optionally, the network-side device 50 may further include a transceiver 502, which can be used for data interaction between the network-side device and other network-side devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 502 is not limited to one, and the structure of this network-side device 50 does not constitute a limitation on the embodiments of this application.

[0454] It should be understood that in the above embodiments, Figure 5 The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 503 and memory represented by memory 501 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. Transceiver 502 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, and other transmission media.

[0455] Processor 503 is responsible for managing the bus architecture and general processing, while memory 502 can store the data used by processor 503 when performing operations.

[0456] Optionally, processor 403, and / or processor 503 may 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 may also adopt a multi-core architecture.

[0457] 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.

[0458] 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 at least one second first-type beam on which it can obtain second-type beam information through the first first-type beam it camps, and obtains information about the available second-type beam on one of the first first-type beams and / or at least one second first-type beam, thereby ensuring that the UE obtains relevant information about the second-type beams that can be accessed through the first-type beam.

[0459] 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.

[0460] 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.

[0461] 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.

[0462] 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.

[0463] 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.

[0464] 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.

[0465] 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.

[0466] 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) acquires information of at least one second first type beam on the first first type beam it camps on, wherein the second first type beam is a first type beam on which the UE can obtain second type beam information; On at least one of the first type beams of the second type beam, information about the second type beams available to the UE is obtained; The information of the second type of beam includes at least one of the following: The identification of the second type of beam; Temporal information of the second type-one beam; The identifier of the satellite containing the second type of beam; The frequency domain information of the second type of beam.

2. The method according to claim 1, characterized in that, The time-domain information of the second type-1 beam includes at least one of the following: The time offset between the second type-one beam and the first type-one beam; The time offset between the second type I beam and the first type I beam within the same type I beam scanning period; Second type 1 beam synchronization signal block SSB mode; The first type of beam scanning period offset N when the second type of beam appears; The SSB mode of the satellite containing the second type of first beam; The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

3. The method according to any one of claims 1-2, characterized in that, The UE acquires information about at least one second first-type beam on the first first-type beam it is camped on, including: The UE receives first system information on the first type of beam it is camped on, and the first system information carries information about at least one second type of beam.

4. The method according to claim 3, characterized in that, The first system information also carries at least one of the following: Duration of Type I beams; The total number of Category I beams; The order of appearance of the first type of beam; The scanning period of the first type of beam; Effective spacing of type II beams; The first type of beam appears with the first type of beam scanning period offset N.

5. The method according to claim 4, characterized in that, The step of obtaining information about the second type of beam available to the UE on one of the first type of beam and / or at least one of the second type of beam includes: The arrival time of at least one second type beam and / or the arrival time of the first type beam are determined based on the time-domain information of at least one second type beam and / or the information carried in the first system information. At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is acquired sequentially on the corresponding first type-1 beam in chronological order until information of a usable second type-1 beam is acquired.

6. The method according to any one of claims 1-2, 4 and 5, wherein the information of the second type of beam includes at least one of the following: The identifier of the first type of associated beam; The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam; The identifier of the satellite containing the second type of beam; Frequency domain information of the associated first-type beam; The identifier of the satellite to which the first type of beam is associated.

7. The method according to claim 1, characterized in that, Before obtaining information about the second type of beam available to the UE on one of the first type of beam and / or at least one of the second type of beams, the process includes: The UE initiates an access request to the network on the first type of beam.

8. The method according to claim 4 or 5, characterized in that, The method further includes at least one of the following operations: A timer is started at a first preset time, and the duration of the timer is the effective interval of the second type of beam. The timer is stopped at a second preset time. The timer expires, indicating that the UE access has failed. Wherein, the first preset time is at least one of the following: When the UE sends an access request; When the UE begins searching for Type II beams; When the UE obtains available Type II beam information; When the UE begins to acquire second type beam information for each second type first beam or the first type first beam; When the UE arrives at each of the second type 1 beams or the first type 1 beam; The second preset time is at least one of the following: The UE successfully synchronized to the second type of beam; The UE successfully obtained information about the available Type 2 beams; The UE successfully connected to the second type of beam.

9. A method for acquiring beam information, characterized in that, The method includes: Send information about at least one second type of beam to the UE camped on the first type of beam; Information about the second type of beam is transmitted to the UE through at least one second type of beam; The information of the second type of beam includes at least one of the following: The identification of the second type of beam; Temporal information of the second type-one beam; The identifier of the satellite containing the second type of beam; The frequency domain information of the second type of beam.

10. The method according to claim 9, characterized in that, The time-domain information of the second type-1 beam includes at least one of the following: The time offset between the second type-one beam and the first type-one beam; The time offset between the second type I beam and the first type I beam within the same type I beam scanning period; Second type 1 beam synchronization signal block SSB mode; The first type of beam scanning period offset N when the second type of beam appears; The SSB mode of the satellite containing the second type of first beam; The synchronization deviation between the satellite containing the second type of beam and the satellite containing the first type of beam.

11. The method according to any one of claims 9-10, characterized in that, The step of transmitting information for at least one second first-type beam to a UE camped on a first first-type beam includes: First system information is transmitted to a UE camped on a first type of beam, the first system information carrying information of at least one second type of beam.

12. The method according to claim 11, characterized in that, The first system information also carries at least one of the following: Duration of Type I beams; The total number of Category I beams; The order of appearance of the first type of beam; The scanning period of the first type of beam; Effective spacing of type II beams; The first type of beam appears with the first type of beam scanning period offset N.

13. The method according to claim 12, characterized in that, Sending information about a second type of beam to the UE via the first first type of beam and / or at least one second first type of beam, including: At the arrival time of at least one second type-1 beam and / or the arrival time of the first type-1 beam, information of the second type-1 beam is transmitted sequentially on the corresponding first type-1 beam in chronological order.

14. The method according to any one of claims 9-10, 12, and 13, wherein the information of the second type of beam includes at least one of the following: The identifier of the first type of associated beam; The second type of beam is an indication information of the second type of beam in response to the access request sent through the current first type of beam; The identifier of the satellite containing the second type of beam; Frequency domain information of the associated first-type beam; The identifier of the satellite to which the first type of beam is associated.

15. The method according to claim 9, characterized in that, Before transmitting information about the second type of beam available to the UE on the first first type beam and / or at least one second first type beam, the process includes: Receive the access request sent by the UE on the first type of beam.

16. A device for acquiring beam information, characterized in that, include: The first acquisition module is used to acquire information of at least one second first type beam on the first first type beam on which the user equipment (UE) is camped, wherein the second first type beam is a first type beam on which the UE can acquire second type beam information; The second acquisition module is used to acquire information about the second type of beam available to the UE on at least one of the first type of beams in the second first type of beam; The information of the second type of beam includes at least one of the following: The identification of the second type of beam; Temporal information of the second type-one beam; The identifier of the satellite containing the second type of beam; The frequency domain information of the second type of beam.

17. A device for acquiring beam information, characterized in that, include: The first transmitting module is used to transmit information of at least one second first type beam to the UE camped on the first first type beam; The second transmitting module is used to transmit information of the second type beam to the UE through at least one second first type beam; The information of the second type of beam includes at least one of the following: The identification of the second type of beam; Temporal information of the second type-one beam; The identifier of the satellite containing the second type of beam; The frequency domain information of the second type of beam.

18. A user equipment, characterized in that, include: Memory, used to store computer programs; A processor for reading a computer program from the memory and executing the method of any one of claims 1-8; A transceiver, used to send and receive data under the control of the processor.

19. A network-side device, characterized in that, include: Memory, used to store computer programs; A processor for reading a computer program from the memory and executing the method according to any one of claims 9-15; A transceiver, used to send and receive data under the control of the processor.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that causes a processor to perform the method of any one of claims 1-8.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that causes a processor to perform the method of any one of claims 9-15.

Images