WO2019091273A1

WO2019091273A1 - Method and terminal for transmitting historical information of beam and network device

Info

Publication number: WO2019091273A1
Application number: PCT/CN2018/110745
Authority: WO
Inventors: 马玥
Original assignee: 维沃移动通信有限公司
Priority date: 2017-11-08
Filing date: 2018-10-18
Publication date: 2019-05-16
Also published as: CN109756924A

Abstract

Disclosed by the present disclosure are a method and terminal for transmitting historical information of a beam, as well as a network device, the method comprising: a terminal reporting historical information of a beam to a network device when a reporting condition is met. Accordingly, the network device receives the historical information of the beam which is reported by the terminal when the reporting condition is met and pages the terminal or performs mobility management on the terminal according to the historical information of the beam.

Description

Beam history information transmission method, terminal and network device

Cross-reference to related applications

The present application claims priority to Chinese Patent Application No. 201711092945.0, filed on Jan.

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to a beam history information transmission method, a terminal, and a network device.

Background technique

In the fifth generation (5Generation, 5G) mobile communication system, or the research called New Radio (NR) system, the operating frequency band supported by the system is raised to above 6 GHz, up to about 100 GHz. The high frequency band has a relatively rich idle frequency resource, which can provide greater throughput for data transmission. High-band coverage is limited, and multi-antenna multiple-input multiple-output (MIMO) technology is needed to improve coverage and capacity. Under high-frequency MIMO conditions, beamforming technology can be used to improve beam concentrated emission energy.

The analog beamforming is transmitted at full bandwidth, and each polarization direction array element on the panel of each high frequency antenna array can only transmit analog beams in a time division multiplexed manner. The shaping weight of the analog beam is achieved by adjusting the parameters of the device such as the RF front-end phase shifter. Generally, the training of the beamforming vector is performed by means of polling, that is, the array elements of each polarization direction of each antenna panel sequentially transmit the training signals, that is, the candidate shaping vectors, in a time-division multiplexing manner at an agreed time. After the terminal passes the measurement, the feedback beam report is used by the network device to implement the analog beam transmission when the next transmission service is used. Further, the network device configures a beam reporting setting information for the terminal by using high layer signaling, including content information of the beam report and time domain related information of the beam report (eg, period, aperiodic, half) Continuous, etc.), frequency granularity information of the beam report, and the like.

In a Long Time Evolution (LTE) system, if the terminal has the capability of storing historical measurement information, when the network device sends the historical measurement information through the message requesting terminal, the terminal reports the stored historical measurement information by signaling. The content of the report mainly includes the cell ID (cell ID), the dwell time, and the out of service time of the cell in which the cell is located. The main purpose of the report is to assist the network device to track the historical location information of the terminal. In the 5G system, the concept of the beam is introduced. The terminal uses the traditional historical measurement information report to report the beam-related historical measurement information to the network device, which is not conducive to the determination of the historical location of the terminal, and cannot achieve accurate mobility management.

Summary of the invention

In a first aspect, an embodiment of the present disclosure provides a beam history information transmission method, which is applied to a terminal side, and includes:

When the reporting condition is met, the beam history information is reported to the network device.

In a second aspect, an embodiment of the present disclosure further provides a terminal, including:

The reporting module is configured to report the beam history information to the network device when the reporting condition is met.

In a third aspect, an embodiment of the present disclosure provides a terminal, where the terminal includes a processor, a memory, and a computer program stored on the memory and operable on the processor, where the computer program is executed by the processor to implement the beam history information transmission. The steps of the method.

In a fourth aspect, an embodiment of the present disclosure provides a beam history information transmission method, which is applied to a network device side, and includes:

The beam history information reported by the receiving terminal when the reporting condition is met;

The terminal is paged or mobility managed according to the beam history information.

In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

a receiving module, configured to receive beam history information reported by the terminal when the reporting condition is met;

The processing module is configured to perform paging or mobility management on the terminal according to the beam history information.

In a sixth aspect, an embodiment of the present disclosure further provides a network device, where the network device includes a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program is implemented by the processor to implement the beam. The steps of the historical information transmission method.

In a seventh aspect, an embodiment of the present disclosure provides a computer readable storage medium. The computer readable storage medium stores a computer program. When the computer program is executed by the processor, the step of implementing the beam history information transmission method is implemented.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings to be used in the description of the embodiments of the present disclosure will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present disclosure. Other drawings may also be obtained from those of ordinary skill in the art based on these drawings without the inventive labor.

FIG. 1 is a schematic flowchart diagram of a method for transmitting beam history information on a terminal side according to an embodiment of the present disclosure;

2 is a schematic diagram of a module on a terminal side in an embodiment of the present disclosure;

Figure 3 shows a block diagram of a terminal of an embodiment of the present disclosure;

4 is a schematic flowchart diagram of a method for transmitting beam history information on a network device side according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a module on a network device side in an embodiment of the present disclosure;

Figure 6 shows a block diagram of a network device in accordance with an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a particular order or order. It is to be understood that the data so used may be interchanged where appropriate, such that the embodiments of the present application described herein can be implemented, for example, in a sequence other than those illustrated or described herein. In addition, the terms "comprises" and "comprises" and "the" and "the" are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.

As shown in FIG. 1 , the beam history information transmission method of the embodiment of the present disclosure is applied to the terminal side, and specifically includes the following steps:

Step 11: Report the beam history information to the network device when the reporting condition is met.

Here, the terminal reports the current stored beam history information to the network device when the terminal meets certain reporting conditions. The beam history information is beam information of a historical beam associated with the terminal, and is mainly used to represent beam information of the terminal historical movement information. It is to be noted that the triggering manner of the report of the beam history information of the terminal includes the active triggering and the passive triggering. Specifically, the conditions for the reporting are met: the preset triggering reporting condition is met, or the request sent by the network device is received. Report request for beam history information. In the following embodiment, the reporting of beam history information will be described in detail in combination with the two methods.

Method 1: Active reporting method

The step 11 is specifically: the terminal detects whether the preset trigger reporting condition is met, and reports the beam history information to the network device when the preset triggering reporting condition is met.

The preset triggering reporting condition is a pre-defined trigger reporting condition or a trigger reporting condition specified by the protocol. For example, when detecting the service beam handover of the terminal, the service beam before the handover is recorded in the beam history information. And reporting to the network device, or when detecting that the cell to which the terminal terminal belongs changes, the beam associated with the cell before the handover is recorded in the beam history information and reported to the network device. Or, after reaching a certain preset time, the current existing beam history information is reported to the network device, and the terminal may report the beam history information value at a time, or periodically report to the network device according to a preset period. Self-recorded beam history information.

Method 2, passive reporting

The step 11 is specifically: when the request for reporting the beam history information is reported by the network device, the beam history information is reported to the network device.

Here, it is said that the terminal only detects whether the triggering condition of the report configuration is met when the network device configures the configuration of the beam history information for the network device, and reports the trigger condition if the report is satisfied.

Further, it is worth noting that in the above two reporting modes, the beam history information reported by the terminal to the network device may be all the beam information recorded by the terminal, or may be part of the total beam information. When the partial beam information is reported, the beam information of the beam history information or the number of beams exceeding the second preset threshold is reported to the network device. For example, if the beam quality is divided into five levels of 1, 2, 3, 4, and 5, and the predefined second preset threshold is level 3, the terminal only records the beam information when reporting the beam history information to the network device. The beam information with a medium beam quality higher than level 3 is reported to the network device. Alternatively, if the second preset threshold of the number of beams is set to 3, the terminal reports the recorded beam history information to the network device when recording the 3 or more historical beams.

Further, the beam history information includes at least one of the following information:

The frequency information of the Cell Global Identifier (CGI) or the Physical Cell Identifier (PCI) of the historical cell. The historical cell is the cell where the historical service beam of the terminal is located.

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell. That is, the ID, the identifier, and the time-frequency resource of the beam of various reference signals in the cell to which the terminal belongs.

The beam measurement information of the historical service beam of the terminal; that is, the measurement information of the service beam that the terminal used to be, specifically, the measurement information of layer 1 and layer 3, such as: Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Received Signal Strength Indication (RSSI), Signal to Interference plus Noise Ratio (SINR), and Channel Quality Indicator (CQI) Wait. The service beam is a beam serving the terminal in the connected state, or a bearer beam of the reference signal of the terminal in the connected state.

The antenna panel information of the historical service beam; that is, the antenna panel information of the service beam that the terminal used to be.

The length of the dwell time and the dwell time of the terminal on the historical service beam; that is, the length of time the terminal stays on the previous service beam and the start time of the dwell time. Or, the length of time and the start termination time of the out-service or out of coverage of the terminal on the historical service beam.

The measurement time information and the measurement position information corresponding to the beam measurement information of the historical service beam; that is, the terminal records the measurement information of a certain service beam at different time points and different positions.

Quasi Co-Location (QCL) information of the historical service beam; that is, from which antenna port the terminal's previous service beam is sent, indicating which service beams are sent from the same antenna port.

Bitmap information of the Synchronous Signal Block (SSB) corresponding to the historical service beam; that is, the SSB transmission location of the broadcast and/or Radio Resource Control (RRC) dedicated signaling configuration in the system message Bitmap information. For example, the bitmap information of the SSB is "00101100", and the beams corresponding to numbers 3, 5, and 6 are transmitted. If the bitmap information of the SSB is changed to "01001100", the beams corresponding to numbers 2, 5, and 6 are transmitted.

And navigation information associated with the historical service beam, the navigation information is used to determine a historical position, a speed, a moving direction, and an angle of the terminal. Specifically, the navigation information includes directly indicating a historical position, a speed, a moving direction, an angle, and the like of the terminal. The INS information can also be other information that can derive the historical position, speed, direction and angle of movement of the terminal. The navigation information may be reported in association with the beam measurement information of the historical service beam.

Among them, it is worth noting that the beam history information is stored in a predefined variable, which can be configured by the network device or directly defined by the protocol.

Further, before the step 11, the step of recording the beam history information by the terminal is further included. Specifically, when the preset recording condition is met, the corresponding beam information is recorded; and the beam history information of the terminal is generated according to the recorded beam information.

The preset recording condition includes at least one of the following:

The cell to which the terminal belongs changes; that is, the terminal changes the cell, and specifically includes changing the primary cell (PCell), the secondary cell (SCell), and the primary/secondary cell (PSCell).

The network format of the terminal changes; that is, the terminal changes its network standard, such as switching from the NR system to the LTE system, or switching from the LTE system to the NR system.

The service or coverage status of the terminal changes; specifically, the terminal switches from the in service or the in coverage state to the out of service or the out of coverage state, and the terminal is disconnected. An out of service or out of coverage state is switched to an in service or an in coverage state.

The antenna panel where the terminal is located changes; that is, the terminal changes the antenna panel where it is located, that is, the antenna panel where the different beams are located.

The service beam or the attached beam where the terminal is located changes; wherein the attached beam is a beam in which the terminal reads the SSB in an idle state.

The type of beam used by the terminal changes; that is, the terminal switches from one beam to another, for example, the terminal is switched from a beam using the SSB to a beam using a channel status indicator reference signal (CSI-RS).

The beam use state of the reference signal corresponding to the terminal changes; for example, the terminal switches from a beam with/without using the reference signal to a beam that does not use/use the reference signal.

The terminal recognizes that the intensity of the beam changes, the terminal recognizes the change of the strong/weak beam, and records the last strong/weak beam.

The above describes the circumstances under which the terminal records beam information is triggered. In order to improve the availability of the recorded beam information, the terminal may filter part of the beam information according to preset conditions, and only retain the beam information that may be useful. Specifically, the beam information of the beam quality or the number of beams exceeding the first preset threshold is recorded. It should be noted that the first preset threshold is only used as a description of the threshold, and those skilled in the art should understand that the threshold corresponding to the beam quality is different from the threshold corresponding to the number of beams, and the specific first preset threshold may be set according to the network device. The configuration settings can also be customized by the terminal or directly defined by the protocol.

Further, the step of generating the beam history information of the terminal according to the recorded beam information may be specifically implemented by: sorting the recorded beam information according to a preset order, and generating beam history information of the terminal.

The preset order includes one of the following sequences:

The frequency order in which the terminals reside on different beams; that is, the frequency at which the terminals reside on certain beams, which can be ordered by frequency.

The chronological order of the service beams of the terminal; that is, the chronological order of the beams served by the terminal is recorded.

The quality of the service beam of the terminal is in good order; that is, the order is recorded according to the quality of the beam serving the terminal.

The chronological order of the beams measured by the terminal; that is, the terminal records in accordance with the chronological order of the measured different beams.

And the order of the quality of the beams measured by the terminal, that is, the terminal records the records according to the measured beam quality of different beams.

Further, the beam information related to the terminal is continuously updated due to the mobility of the terminal and the instability of the network state. To ensure the validity of the beam history information recorded by the terminal, the beam history of the terminal is generated according to the recorded beam information. The step of information includes: if the number of recorded beam information is greater than N, selecting beam history information of the N pieces of information from the current time in the beam information; wherein N is the maximum number of records allowed by the beam history information, N is an integer greater than one. N may be predefined by the terminal or configured by the network device. It is worth noting that after the beam history information is generated, if the terminal records new beam information, the total number of beam information is greater than N, and the earliest recorded beam information in the original beam history information is deleted, and the latest record is recorded. The beam information is supplemented to achieve continuous updating of the beam history information.

The following describes the process of the beam history information, the beam history information record, and the generation process. The following example uses the passive report as an example to describe the process of reporting the beam history information.

Specifically, the step of reporting the beam history information to the network device when receiving the request for reporting the beam history information by the network device includes: receiving a query request sent by the network device to query whether there is available beam history information; Requesting, querying whether there is available beam history information; if yes, feeding back feedback information of the available beam history information to the network device; and receiving the request for reporting the available beam history information by the receiving network device according to the feedback information; The reported beam history information is reported to the network device. The process here is: when the network device needs to report the beam history information, the network device first sends a query request to the terminal to query whether there is available beam history information, and the terminal queries whether there is an available beam when receiving the query request. The historical information, if present, feeds back to the network device feedback information about the available beam history information. After receiving the feedback information, the network device sends a report request for reporting the beam history information to the terminal, and the terminal reports the available beam history information to the network device according to the report request.

Or, in order to simplify the interaction process and save the signaling overhead, the step of reporting the beam history information to the network device according to the reporting request when receiving the request for reporting the beam history information by the network device includes: receiving the query sent by the network device Whether there is a query request for the available beam history information; whether the available beam history information exists according to the query request; if yes, the available beam history information is reported to the network device. The process here is: when the network device needs to report the beam history information, the network device first sends a query request to the terminal to query whether there is available beam history information, and the terminal queries whether there is an available beam when receiving the query request. The historical information, if any, reports the available beam history information to the network device.

Among them, it is worth noting that the available beam history information is the beam history information available in the target system. The network device may further instruct the terminal to query or report the available beam history information in the target network system, where the target network standard may be at least one of the LTE system, the NR system, and other network standards. For example, the network device may request the terminal to query or report the beam history information available in the NR system under the LTE system, or request the terminal to query or report the beam history information available in the LTE system under the NR system.

Specifically, the query sent by the network device asks whether there is a query request for the beam history information in the target network system. It is assumed that the network device sends a query request to the terminal to query whether there is beam history information available in the LTE system, and the terminal queries whether the beam history information available in the LTE system exists in the query request, and when there is beam history information available in the LTE system, The network device sends feedback information. Or, receiving a request sent by the network device to report a report request of the beam history information in the target network system that is available. It is assumed that the network device sends a report request to the terminal to report the beam history information available in the LTE system, and the terminal reports the available beam history information in the LTE system to the network device according to the report request.

Specifically, the step of receiving a query request sent by the network device to query whether there is available beam history information includes: in the RRC connection establishment/recovery process, receiving, by the RRC message, whether the network device has an available beam history. Query request for information. Specifically, the network device sends an inquiry to the terminal whether an RRC Connection setup message, an RRC connection resume message, an RRC reconfiguration message, or a HO command message is sent. Query request for beam history information. Correspondingly, the step of feeding back the feedback information of the available beam history information to the network device comprises: feeding back, by the RRC message, the feedback information of the available beam history information to the network device during the RRC connection setup completion/recovery completion process. . Specifically, when the terminal queries for the available beam history information, the terminal may complete the RRC Connection setup complete message, the RRC connection resume complete message, and the RRC reconfiguration complete. The message or the HO complete message feeds back to the network device feedback information about the available beam history information.

Alternatively, the receiving network device sends a query request for whether there is available beam history information by using a predefined RRC message. Correspondingly, the step of feeding back the feedback information of the available beam history information to the network device comprises: feeding back, by the predefined RRC message, feedback information of the available beam history information to the network device.

Alternatively, the receiving network device sends a query request for whether there is available beam history information by using a control element (Control Element, CE) of the Media Access Control (MAC) layer or layer 1 control information. Correspondingly, the step of feeding back the feedback information of the available beam history information to the network device includes: feeding back, by the medium access control, the control element CE of the MAC layer or the control information of the layer 1 to the network device, that the available beam history information exists. Feedback.

Or, when the terminal is in the inactive inactive state, the receiving network device sends a query request by using signaling or a data packet to query whether there is available beam history information. Correspondingly, the step of feeding back the feedback information of the available beam history information to the network device comprises: feeding back feedback information of the available beam history information to the network device through signaling or data packet when in the inactive inactive state.

Further, in order to simplify the interaction process and save the signaling overhead, the step of reporting the beam history information to the network device according to the reporting request when receiving the request for reporting the beam history information by the network device further includes: receiving the sending by the network device Requesting to report the available beam history information reporting request; querying whether there is available beam history information according to the reporting request; if yes, reporting the available beam history information to the network device. The process here is: when the network device needs the terminal to report the beam history information, the network device sends a report request requesting the report beam history information to the terminal, and the terminal queries whether the available beam history information exists according to the report request, and if yes, directly queries The available beam history information is reported to the network device.

Specifically, the network device may further instruct the terminal to query or report the available beam history information in the target network standard, where the target network standard may be at least one of the LTE system, the NR system, and other network standards. Receiving a request sent by the network device to report a report request of the beam history information in the target network system that is available. It is assumed that the network device sends a report request to the terminal to report the beam history information available in the LTE system, and the terminal reports the available beam history information in the LTE system to the network device according to the report request.

Further, the step of reporting the beam history information to the network device may be specifically implemented by:

The RRC connection setup complete message (RRC Connection setup complete) message and the RRC connection recovery completion (RRC) are reported to the network device by the RRC message during the completion of the RRC connection establishment/recovery process. The connection resume complete message, the RRC reconfiguration complete message or the HO complete message, reports the beam history information to the network device.

The beam history information is reported to the network device through the RRC message during the terminal information reporting or the measurement information reporting process. Correspondingly, the step of receiving the request report beam history information report request sent by the network device comprises: receiving, during the terminal information request or the measurement information configuration process, the report request of the report report beam history information sent by the network device by using the RRC message. Specifically, the network device sends a report request for reporting the available beam history information to the terminal by using a UE information request message or a measurement configuration message. Correspondingly, the terminal reports the beam history information to the network device by using a UE information response message or a measurement report message.

Or, the beam history information is reported to the network device by using the predefined RRC message; correspondingly, the step of receiving the request report beam history information report request sent by the network device includes: receiving the request report sent by the network device by using a predefined RRC message The beam history information is reported.

Or, the beam history information is reported to the network device by using the MAC layer CE or the control information of the layer 1; correspondingly, the step of receiving the request report beam history information report request sent by the network device includes: receiving the network device by using the MAC layer CE or layer A request for control information transmission reports a report request for reporting beam history information.

Or, when the terminal is in the inactive inactive state, the beam history information is reported to the network device by using signaling or a data packet. Correspondingly, the step of receiving the report beam history information report request sent by the network device includes: when the inactive inactive state is received, the receiving network device sends a report request for reporting the beam history information by using a signaling or a data packet.

In the beam history information transmission method of the embodiment of the present disclosure, the terminal reports the beam history information to the network device when the reporting condition is met, and the beam history information can reflect the historical movement information of the terminal, and the network device receives the beam history information of the terminal after receiving the beam history information of the terminal. The subsequent paging process of the terminal can be optimized according to the beam history information, and the terminal is accurately mobility managed.

The above embodiments respectively describe the beam history information transmission methods in different scenarios. The following embodiments of the present invention will be further described in conjunction with the accompanying drawings.

As shown in FIG. 2, the terminal 200 of the embodiment of the present disclosure can implement the details of the method for reporting the beam history information to the network device when the reporting condition is met in the foregoing embodiment, and achieve the same effect. The terminal 200 specifically includes the following. functional module:

The reporting module 210 is configured to report the beam history information to the network device when the reporting condition is met.

The beam history information includes at least one of the following information:

The cell of the historical cell globally identifies the frequency information of the CGI or the physical cell identifier PCI; the historical cell is the cell where the historical service beam of the terminal is located;

Beam identity information, beam identification, and/or time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

The length of the dwell time and the dwell time of the terminal on the historical service beam;

Measurement time information and measurement position information corresponding to beam measurement information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Bitmap information of the sync signal block corresponding to the historical service beam;

Navigation information associated with the historical service beam, the navigation information is used to determine the historical location, speed, direction and angle of the terminal.

The terminal further includes:

a recording module, configured to record corresponding beam information when a preset recording condition is met;

a generating module, configured to generate beam history information of the terminal according to the recorded beam information;

The preset recording condition includes at least one of the following:

The cell to which the terminal belongs changes;

The network standard of the terminal changes;

The service or coverage status of the terminal changes;

The antenna panel where the terminal is located changes;

The service beam or attached beam where the terminal is located changes;

The type of beam used by the terminal changes;

The beam usage state of the reference signal corresponding to the terminal changes;

The terminal recognizes that the intensity of the beam changes.

The generating module includes:

a first generation sub-module, configured to sort the recorded beam information according to a preset order, and generate beam history information of the terminal;

The preset order includes one of the following sequences:

The frequency order in which the terminals reside on different beams;

The chronological order of the service beams of the terminal;

The quality of the service beam of the terminal;

The chronological order of the beams measured by the terminal;

The quality of the beam measured by the terminal.

The generating module further includes:

a second generation submodule, configured to: if the number of the recorded beam information is greater than N, select beam history information of the N pieces of information in the beam information that is closest to the current time; wherein N is the maximum allowed by the beam history information The number of records, N is an integer greater than one.

The recording module includes:

a first recording submodule, configured to record beam information whose beam quality or number of beams exceeds a first preset threshold;

The reporting module includes:

The first reporting sub-module is configured to report beam information of the beam history information or the number of beams exceeding the second preset threshold to the network device.

The reporting module includes:

The second reporting sub-module is configured to report the beam history information to the network device when detecting that the preset trigger reporting condition is met;

or,

The third reporting sub-module is configured to report the beam history information to the network device when receiving the request for reporting the beam history information by the network device.

The third reporting submodule includes:

a first receiving unit, configured to receive a query request sent by the network device to query whether there is available beam history information;

a first query unit, configured to query whether there is available beam history information according to the query request;

The first reporting unit is configured to report the available beam history information to the network device if yes;

Or, if yes, the feedback information of the available beam history information is sent back to the network device; the receiving network device reports the available beam history information reporting request according to the request sent by the feedback information; and reports the available beam history information according to the reporting request. To network devices.

The third reporting sub-module further includes:

a second receiving unit, configured to receive, by the network device, a beam current history report request that is available for reporting the request;

a second query unit, configured to query whether there is available beam history information according to the report request;

The second reporting unit is configured to report the available beam history information to the network device if yes.

The available beam history information is the beam history information available in the target system.

The reporting module further includes:

The fourth reporting sub-module is configured to report the beam history information to the network device by using an RRC message during the completion of the RRC connection establishment/recovery of the RRC connection;

or,

The fifth reporting sub-module is configured to report the beam history information to the network device by using an RRC message during the terminal information reporting or measurement information reporting process;

or,

a sixth reporting sub-module, configured to report beam history information to the network device by using a predefined RRC message;

or,

The seventh reporting sub-module is configured to report the beam history information to the network device by using the control information of the MAC layer CE or the layer 1;

or,

The eighth reporting sub-module is configured to report the beam history information to the network device by using signaling or a data packet when the terminal is in the inactive inactive state.

It is to be noted that the terminal of the embodiment of the present disclosure reports the beam history information to the network device when the reporting condition is met, and the beam history information can reflect the historical mobile information of the terminal. After receiving the beam history information of the terminal, the network device can The subsequent paging process of the terminal is optimized according to the beam history information, and the terminal is accurately mobility managed.

In order to achieve the above objectives, FIG. 3 is a schematic diagram of a hardware structure of a terminal that implements various embodiments of the present disclosure. The terminal 30 includes, but is not limited to, a radio frequency unit 31, a network module 32, and an audio output unit 33. The input unit 34, the sensor 35, the display unit 36, the user input unit 37, the interface unit 38, the memory 39, the processor 310, and the power source 311 and the like. It will be understood by those skilled in the art that the terminal structure shown in FIG. 3 does not constitute a limitation to the terminal, and the terminal may include more or less components than those illustrated, or some components may be combined, or different component arrangements. In the embodiments of the present disclosure, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.

The processor 310 controls the radio frequency unit 31 to: report the beam history information to the network device when the reporting condition is met.

The terminal of the embodiment of the present disclosure reports the beam history information to the network device when the reporting condition is met, and the beam history information can reflect the historical movement information of the terminal. After receiving the beam history information of the terminal, the network device can obtain the beam history information according to the beam history information. Optimize the subsequent paging process of the terminal and perform precise mobility management on the terminal.

It should be understood that, in the embodiment of the present disclosure, the radio frequency unit 31 can be used for receiving and transmitting signals during the transmission and reception of information or during a call, and specifically, after receiving downlink data from the base station, processing the data to the processor 310; The uplink data is sent to the base station. Typically, radio frequency unit 31 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio unit 31 can also communicate with the network and other devices through a wireless communication system.

The terminal provides the user with wireless broadband Internet access through the network module 32, such as helping the user to send and receive emails, browse web pages, and access streaming media.

The audio output unit 33 can convert the audio data received by the radio frequency unit 31 or the network module 32 or stored in the memory 39 into an audio signal and output as sound. Moreover, the audio output unit 33 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) associated with a particular function performed by the terminal 30. The audio output unit 33 includes a speaker, a buzzer, a receiver, and the like.

The input unit 34 is for receiving an audio or video signal. The input unit 34 may include a graphics processing unit (GPU) 341 and a microphone 342 that images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The data is processed. The processed image frame can be displayed on the display unit 36. The image frames processed by the graphics processor 341 may be stored in the memory 39 (or other storage medium) or transmitted via the radio unit 31 or the network module 32. The microphone 342 can receive sound and can process such sound as audio data. The processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 31 in the case of a telephone call mode.

Terminal 30 also includes at least one type of sensor 35, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 361 according to the brightness of the ambient light, and the proximity sensor can close the display panel 361 and/or when the terminal 30 moves to the ear. Or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the terminal attitude (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; sensor 35 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.

The display unit 36 is for displaying information input by the user or information provided to the user. The display unit 36 can include a display panel 361. The display panel 361 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

The user input unit 37 can be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 37 includes a touch panel 371 and other input devices 372. The touch panel 371, also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 371 or near the touch panel 371. operating). The touch panel 371 can include two parts of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. To the processor 310, a command sent by the processor 310 is received and executed. In addition, the touch panel 371 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 371, the user input unit 37 may also include other input devices 372. Specifically, the other input devices 372 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which are not described herein.

Further, the touch panel 371 can be overlaid on the display panel 361. When the touch panel 371 detects a touch operation on or near the touch panel 371, it is transmitted to the processor 310 to determine the type of the touch event, and then the processor 310 according to the touch. The type of event provides a corresponding visual output on display panel 361. Although in FIG. 3, the touch panel 371 and the display panel 361 are used as two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 371 may be integrated with the display panel 361. The input and output functions of the terminal are implemented, and are not limited herein.

The interface unit 38 is an interface in which an external device is connected to the terminal 30. For example, the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more. The interface unit 38 can be configured to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within the terminal 30 or can be used at the terminal 30 and external devices Transfer data between.

Memory 39 can be used to store software programs as well as various data. The memory 39 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.). Further, the memory 39 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 310 is a control center of the terminal, which connects various parts of the entire terminal by various interfaces and lines, and executes by executing or executing software programs and/or modules stored in the memory 39, and calling data stored in the memory 39. The terminal's various functions and processing data, so as to monitor the terminal as a whole. The processor 310 may include one or more processing units; optionally, the processor 310 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, etc., and a modulation solution The processor mainly handles wireless communication. It can be understood that the above modem processor may not be integrated into the processor 310.

The terminal 30 may further include a power source 311 (such as a battery) for supplying power to the various components. Alternatively, the power source 311 may be logically connected to the processor 310 through the power management system to manage charging, discharging, and power management through the power management system. And other functions.

In addition, the terminal 30 includes some functional modules not shown, and details are not described herein again.

Optionally, an embodiment of the present disclosure further provides a terminal, including a processor 310, a memory 39, a computer program stored on the memory 39 and executable on the processor 310, when the computer program is executed by the processor 310. The processes of the foregoing embodiment of the beam history information transmission method are implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein again. The terminal may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with a wireless connection function, or other processing device connected to the wireless modem. . The wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal. For example, it may be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with a wireless access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (Personal Digital Assistant, PDA) and other equipment. The wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal. The access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.

The embodiment of the present disclosure further provides a computer readable storage medium. The computer readable storage medium stores a computer program, where the computer program is executed by the processor to implement various processes of the beam history information transmission method embodiment, and can achieve the same The technical effect, in order to avoid duplication, will not be repeated here. The computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

The above embodiment describes the beam history information transmission method of the present disclosure from the terminal side. The following embodiment will further introduce the beam history information transmission method on the network device side with reference to the accompanying drawings.

As shown in FIG. 4, the beam history information transmission method of the embodiment of the present disclosure is applied to a network device, and specifically includes the following steps:

Step 41: Receive beam history information reported by the terminal when the reporting condition is met.

The beam history information is beam information of a historical beam associated with the terminal, and is mainly used to represent beam information of the terminal historical movement information. It is to be noted that the triggering manner of the terminal to report the beam history information includes the active triggering and the passive triggering, as in the first mode and the second mode, and therefore no further details are provided herein.

Step 42: Perform paging or mobility management on the terminal according to the beam history information.

After obtaining the beam history information of the terminal, the network device integrates the corresponding data content to optimize the subsequent paging process of the terminal or the mobility management process of the terminal. Specifically, the network device may predict the current location of the terminal according to the beam history information, thereby performing directional paging on the terminal to improve the success rate of the paging. Alternatively, the network device determines, according to the beam history information, whether to switch the cell or the service beam for the terminal, so as to implement accurate mobility management for the terminal. In addition, network devices can optimize other processes based on beam history information.

The beam measurement information of the historical service beam; specifically, the measurement information of layer 1 and layer 3, such as: RSRP, RSRQ, RSSI, SINR, and CQI. The service beam is a beam serving the terminal in the connected state, or a bearer beam of the reference signal of the terminal in the connected state.

Antenna panel information of the historical service beam;

The length of the dwell time and the dwell time information of the terminal on the historical service beam; or the length of time and the start end time of the out of service or out of coverage of the terminal on the historical service beam.

Pseudo-co-located QCL information of the historical service beam, wherein the QCL information is used to indicate which service beams are sent from the same antenna port;

Navigation information associated with the historical service beam, the navigation information is used to determine the historical position, speed, moving direction, and angle of the terminal, and the navigation information includes inertial information directly indicating the historical position, speed, and moving direction and angle of the terminal. Other information that can derive the historical position, speed, direction and angle of movement of the terminal, and the like.

The step 41 further includes: sending, to the terminal, a report request for reporting the available beam history information.

Specifically, the available beam history information is the beam history information available in the target system, and the step of sending a report request for reporting the available beam history information to the terminal includes: sending a request to the terminal to report the available beam history information in the target network standard. Reporting request. That is, the network device may further instruct the terminal to query or report the available beam history information in the target network system, where the target network standard may be at least one of the LTE system, the NR system, and other network technologies.

Further, the step of sending a report request for reporting the available beam history information to the terminal includes: sending a query request to the terminal for querying whether there is available beam history information; and receiving, by the receiving terminal, the available beam history information according to the query request The feedback information is sent to the terminal according to the feedback information, and the request for reporting the available beam history information is reported to the terminal.

The step of sending a query request to the terminal to query whether there is available beam history information includes: sending a query request to the terminal to query whether there is available beam history information in the target network system.

Further, the step of transmitting a query request to the terminal to inquire whether there is available beam history information can be implemented in the following manner:

In the RRC connection establishment/recovery process, the RRC message is sent to the terminal to query whether there is a query request for available beam history information.

Or sending, by using a predefined RRC message, a query request to the terminal to query whether there is available beam history information.

Alternatively, the control information of the Medium Access Control (MAC) layer (Control Element, CE) or Layer 1 control information is sent to the terminal to query whether there is a query request for available beam history information.

Alternatively, when the terminal is in the inactive inactive state, a query request for asking whether there is available beam history information is sent to the terminal through signaling or a data packet.

Correspondingly, the step of the receiving terminal feeding back the feedback information of the available beam history information according to the query request includes:

In the process of completing the radio resource control RRC connection establishment/recovery, the receiving terminal feeds back the feedback information of the available beam history information through the RRC message;

or,

Receiving, by the terminal, feedback information of available beam history information that is fed back through a predefined RRC message;

or,

Receiving, by the medium access control, feedback information of the available beam history information of the control element CE of the MAC layer or the control information feedback of the layer 1;

or,

When the terminal is in the inactive inactive state, the receiving terminal feeds back feedback information of the available beam history information through signaling or data packet feedback.

Further, the step of sending a report request for reporting the available beam history information to the terminal may be implemented by:

In the RRC connection establishment/recovery process, the RRC message is sent to the terminal to report the report request for reporting the available beam history information. Correspondingly, the step of receiving the beam history information reported by the terminal includes: establishing the RRC connection in the radio resource control. During the completion/recovery process, the receiving terminal passes the beam history information reported by the RRC message.

Or, in the terminal information request or the measurement information configuration process, the RRC message is sent to the terminal to report the report request for reporting the available beam history information; correspondingly, the step of receiving the available beam history information reported by the terminal is: reporting the terminal information Or the available beam history information reported by the terminal through the RRC message during the measurement information reporting process.

Or sending a request for reporting the available beam history information to the terminal by using the predefined RRC message; correspondingly, the step of receiving the available beam history information reported by the terminal is: the receiving terminal is available through the pre-defined RRC message. Beam history information.

Or, by using the control information of the MAC layer CE or the layer 1 to send a report request to report the available beam history information to the terminal; correspondingly, the step of receiving the available beam history information reported by the terminal is: the receiving terminal passes the MAC layer CE or The available beam history information reported by the layer 1 control information.

Or, when the terminal is in the inactive inactive state, sending, by using signaling or a data packet, a reporting request for reporting the available beam history information to the terminal; correspondingly, the step of receiving the available beam history information reported by the terminal is: receiving the non-received The beam history information reported by the terminal in the inactive state through signaling or data packets.

In the beam history information transmission method of the embodiment of the present disclosure, the network device receives the beam history information reported by the terminal when the reporting condition is met, the beam history information can reflect the historical movement information of the terminal, and the network device receives the beam history information of the terminal. After that, the subsequent paging process of the terminal can be optimized according to the beam history information, and the terminal is accurately mobility managed.

The above embodiment describes the beam history information transmission method in different scenarios. The network device corresponding thereto will be further introduced in the following with reference to the accompanying drawings.

As shown in FIG. 5, the network device 500 of the embodiment of the present disclosure can implement the beam history information reported by the receiving terminal when the reporting condition is met, and the method for paging or mobility management of the terminal according to the beam history information. In detail, and achieving the same effect, the network device 500 specifically includes the following functional modules:

The receiving module 510 is configured to receive beam history information reported by the terminal when the reporting condition is met;

The processing module 520 is configured to perform paging or mobility management on the terminal according to the beam history information.

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell.

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

The network device further includes:

The sending module is configured to send a report request to the terminal to report the available beam history information.

The sending module includes:

a first sending submodule, configured to send, to the terminal, a query request for asking whether there is available beam history information;

a receiving submodule, configured to receive, by the terminal, feedback information of the available beam history information that is fed back according to the query request;

The second sending sub-module is configured to send, according to the feedback information, a request for reporting, by the terminal, the available beam history information reporting request.

The receiving module includes:

a first receiving submodule, configured to receive beam history information reported by the terminal through an RRC message during a radio resource control RRC connection setup completion/recovery process;

or,

a second receiving submodule, configured to receive beam history information sent by the terminal through an RRC message during a terminal information reporting or measurement information reporting process;

or,

a third receiving submodule, configured to receive beam history information sent by the terminal by using a predefined RRC message;

or,

a fourth receiving submodule, configured to receive, by using MAC layer CE or layer 1 control information, beam history information sent by the terminal;

or,

The fifth receiving submodule is configured to receive beam history information that is sent by the terminal or the data packet in the inactive inactive state.

It is to be noted that the network device of the embodiment of the present disclosure receives the beam history information reported by the terminal when the reporting condition is met, and the beam history information can reflect the historical movement information of the terminal. After receiving the beam history information of the terminal, the network device receives the beam history information of the terminal. The subsequent paging process of the terminal can be optimized according to the beam history information, and the terminal is accurately mobility managed.

It should be noted that the division of each module of the above network device and terminal is only a division of logical functions. In actual implementation, it may be integrated into one physical entity in whole or in part, or may be physically separated. And these modules can all be implemented by software in the form of processing component calls; or all of them can be implemented in hardware form; some modules can be realized by processing component calling software, and some modules are realized by hardware. For example, the determining module may be a separately set processing element, or may be integrated in one of the above-mentioned devices, or may be stored in the memory of the above device in the form of program code, by a processing element of the above device. Call and execute the functions of the above determination module. The implementation of other modules is similar. In addition, all or part of these modules can be integrated or implemented independently. The processing elements described herein can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above method, such as one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors, one Or a plurality of digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). As another example, when one of the above modules is implemented in the form of a processing component scheduler code, the processing component can be a general purpose processor, such as a central processing unit (CPU) or other processor that can invoke program code. As another example, these modules can be integrated and implemented in the form of a system-on-a-chip (SOC).

In order to better achieve the above object, an embodiment of the present disclosure further provides a network device, including a processor, a memory, and a computer program stored on the memory and operable on the processor, the processor executing the computer program The steps in the beam history information transmission method as described above are implemented. The disclosed embodiments also provide a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the beam history information transmission method as described above.

Specifically, embodiments of the present disclosure also provide a network device. As shown in FIG. 6, the network device 600 includes an antenna 61, a radio frequency device 62, and a baseband device 63. The antenna 61 is connected to the radio frequency device 62. In the upstream direction, the radio frequency device 62 receives information via the antenna 61 and transmits the received information to the baseband device 63 for processing. In the downstream direction, the baseband device 63 processes the information to be transmitted and transmits it to the radio frequency device 62. The radio frequency device 62 processes the received information and transmits it via the antenna 61.

The above-described band processing device may be located in the baseband device 63, and the method performed by the network device in the above embodiment may be implemented in the baseband device 63, which includes the processor 64 and the memory 65.

The baseband device 63 may include, for example, at least one baseband board on which a plurality of chips are disposed, as shown in FIG. 6, one of which is, for example, a processor 64, connected to the memory 65 to call a program in the memory 65 to execute The network device operation shown in the above method embodiment.

The baseband device 63 can also include a network interface 66 for interacting with the radio frequency device 62, such as a common public radio interface (CPRI).

The processor here may be a processor or a collective name of multiple processing elements. For example, the processor may be a CPU, an ASIC, or one or more configured to implement the method performed by the above network device. Integrated circuits, such as one or more microprocessors, one or more DSPs, or one or more field programmable gate array FPGAs. The storage element can be a memory or a collective name for a plurality of storage elements.

Memory 65 can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory. The volatile memory can be a Random Access Memory (RAM) that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Link DRAM (SLDRAM) ) and direct memory bus random access memory (DRRAM). The memory 65 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Specifically, the network device of the embodiment of the present disclosure further includes: a computer program stored on the memory 65 and operable on the processor 64, and the processor 64 calls a computer program in the memory 65 to execute the method executed by each module shown in FIG. .

Specifically, when the computer program is invoked by the processor 64, the method can be used to: perform beam history information reported by the terminal when the reporting condition is met;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Navigation information associated with the historical service beam, the navigation information being used to determine the historical location, speed, direction of movement, and angle of the terminal.

Specifically, when the computer program is called by the processor 64, it can be used to execute: sending a report request to the terminal to report the available beam history information.

Specifically, when the computer program is called by the processor 64, the method can be used to: send a query request to the terminal to query whether there is available beam history information;

Receiving, by the receiving terminal, feedback information of the available beam history information according to the query request;

According to the feedback information, the terminal sends a request to report the available beam history information reporting request.

Specifically, when the computer program is invoked by the processor 64, the method may be performed to: receive the beam history information reported by the terminal through the RRC message during the RRC connection establishment completion/recovery completion process;

or,

Receiving beam history information sent by the terminal through an RRC message during the terminal information reporting or measurement information reporting process;

or,

Receiving beam history information sent by the terminal by using a predefined RRC message;

or,

Receiving beam history information sent by the terminal by using control information of the MAC layer CE or layer 1;

or,

Receiving beam history information transmitted by a terminal or a data packet in an inactive inactive state.

The network device may be a Global System of Mobile communication (GSM) or a Base Transceiver Station (BTS) in Code Division Multiple Access (CDMA), or may be a wideband code division multiple access. A base station (NodeB, NB) in the (Wideband Code Division Multiple Access, WCDMA) may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or in a future 5G network. The base station or the like is not limited herein.

The network device in the embodiment of the present disclosure receives the beam history information reported by the terminal when the reporting condition is met, and the beam history information can reflect the historical mobile information of the terminal. After receiving the beam history information of the terminal, the network device can The beam history information optimizes the subsequent paging process of the terminal and performs precise mobility management on the terminal.

Those skilled in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present disclosure.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, a portion of the technical solution of the present disclosure that contributes in essence or to the related art or a part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present disclosure. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Moreover, it should be noted that in the apparatus and method of the present disclosure, it is apparent that the various components or steps may be decomposed and/or recombined. These decompositions and/or recombinations should be considered as equivalents to the present disclosure. Also, the steps of performing the above-described series of processes may naturally be performed in chronological order in the order illustrated, but need not necessarily be performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those skilled in the art that all or any of the steps or components of the methods and apparatus of the present disclosure may be in a network of any computing device (including a processor, storage medium, etc.) or computing device, in hardware, firmware The software, or a combination thereof, is implemented by those of ordinary skill in the art using their basic programming skills while reading the description of the present disclosure.

Thus, the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device. The computing device can be a well-known general purpose device. Accordingly, the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure. It will be apparent that the storage medium may be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present disclosure, it is apparent that various components or steps may be decomposed and/or recombined. These decompositions and/or recombinations should be considered as equivalents to the present disclosure. Also, the steps of performing the series of processes described above may naturally be performed in chronological order in the order illustrated, but need not necessarily be performed in chronological order. Certain steps may be performed in parallel or independently of one another.

The above is an alternative embodiment of the present disclosure, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present disclosure. Within the scope of protection of the present disclosure.

Claims

A beam history information transmission method is applied to a terminal side, including:

When the reporting condition is met, the beam history information is reported to the network device.
The beam history information transmission method according to claim 1, wherein the beam history information comprises at least one of the following information:

The cell of the historical cell globally identifies the frequency information of the CGI or the physical cell identifier PCI; the historical cell is the cell where the historical service beam of the terminal is located;

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

a length of dwell time and a dwell start time information of the terminal on the historical service beam;

Measurement time information and measurement position information corresponding to beam measurement information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Bitmap information of the synchronization signal block corresponding to the historical service beam;

Navigation information associated with the historical service beam, the navigation information being used to determine a historical location, speed, direction of movement, and angle of the terminal.
The beam history information transmission method according to claim 1, further comprising: before the step of reporting the beam history information to the network device when the reporting condition is met,

When the preset recording condition is met, the corresponding beam information is recorded;

Generating beam history information of the terminal according to the recorded beam information;

The preset recording condition includes at least one of the following:

The cell to which the terminal belongs changes;

The network format of the terminal changes;

The service or coverage status of the terminal changes;

The antenna panel where the terminal is located changes;

The service beam or the attached beam where the terminal is located changes;

The type of beam used by the terminal changes;

The beam usage status of the reference signal corresponding to the terminal changes;

The terminal recognizes that the intensity of the beam changes.
The beam history information transmission method according to claim 3, wherein the step of generating beam history information of the terminal according to the recorded beam information comprises:

Sorting the recorded beam information according to a preset order to generate beam history information of the terminal;

The preset sequence includes one of the following sequences:

The frequency order in which the terminals reside on different beams;

The chronological order of the service beams of the terminal;

The quality of the service beam of the terminal;

The chronological order of the beams measured by the terminal;

The quality of the beam measured by the terminal.
The beam history information transmission method according to claim 3, wherein the step of generating beam history information of the terminal according to the recorded beam information comprises:

If the number of the recorded beam information is greater than N, the N pieces of information in the beam information that are closest to the current time are used to generate beam history information of the terminal; where N is the maximum number of records allowed by the beam history information. , N is an integer greater than one.
The beam history information transmission method according to claim 3, wherein the step of recording the corresponding beam information comprises:

Recording beam information of the beam quality or the number of beams exceeding a first preset threshold;

The step of reporting the beam history information to the network device includes:

The beam information of the beam history information or the number of beams exceeding the second preset threshold is reported to the network device.
The beam history information transmission method according to claim 1, wherein the step of reporting the beam history information to the network device when the reporting condition is satisfied includes:

When the condition of the preset trigger report is met, the beam history information is reported to the network device;

or,

When receiving the request for reporting the beam history information, the beam history information is reported to the network device.
The beam history information transmission method according to claim 7, wherein the step of reporting the beam history information to the network device when receiving the report request for reporting the beam history information sent by the network device comprises:

Receiving a query request sent by the network device to query whether there is available beam history information;

Querying whether there is available beam history information according to the query request;

If yes, report the available beam history information to the network device;

Or, if yes, feeding back to the network device feedback information of the available beam history information; the receiving network device reporting the available beam history information reporting request according to the request sent by the feedback information; and according to the reporting request, the available information is available. The beam history information is reported to the network device.
The beam history information transmission method according to claim 7, wherein the step of reporting the beam history information to the network device when receiving the report request for reporting the beam history information sent by the network device comprises:

Receiving a request sent by the network device to report an available beam history information reporting request;

Determining whether there is available beam history information according to the reporting request;

If yes, the available beam history information is reported to the network device.
The beam history information transmission method according to claim 8 or 9, wherein the available beam history information is beam history information available under the target system.
The beam history information transmission method according to claim 1, wherein the step of reporting the beam history information to the network device comprises:

After the RRC connection establishment/recovery is completed, the beam history information is reported to the network device by using an RRC message;

or,

The beam history information is reported to the network device through the RRC message during the terminal information reporting or the measurement information reporting process;

or,

Reporting beam history information to the network device by using a predefined RRC message;

or,

The beam history information is reported to the network device by using the control information of the MAC layer CE or layer 1;

or,

When the terminal is in the inactive inactive state, the beam history information is reported to the network device by using signaling or a data packet.
A terminal comprising:

The reporting module is configured to report the beam history information to the network device when the reporting condition is met.
The terminal of claim 12, wherein the beam history information comprises at least one of the following information:

The cell of the historical cell globally identifies the frequency information of the CGI or the physical cell identifier PCI; the historical cell is the cell where the historical service beam of the terminal is located;

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

a length of dwell time and a dwell start time information of the terminal on the historical service beam;

Measurement time information and measurement position information corresponding to beam measurement information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Bitmap information of the synchronization signal block corresponding to the historical service beam;

Navigation information associated with the historical service beam, the navigation information being used to determine a historical location, speed, direction of movement, and angle of the terminal.
The terminal of claim 12, further comprising:

a recording module, configured to record corresponding beam information when a preset recording condition is met;

a generating module, configured to generate beam history information of the terminal according to the recorded beam information;

The preset recording condition includes at least one of the following:

The cell to which the terminal belongs changes;

The network format of the terminal changes;

The service or coverage status of the terminal changes;

The antenna panel where the terminal is located changes;

The service beam or the attached beam where the terminal is located changes;

The type of beam used by the terminal changes;

The beam usage status of the reference signal corresponding to the terminal changes;

The terminal recognizes that the intensity of the beam changes.
The terminal of claim 14, wherein the generating module comprises:

a first generation sub-module, configured to sort the recorded beam information according to a preset order, to generate beam history information of the terminal;

The preset sequence includes one of the following sequences:

The frequency order in which the terminals reside on different beams;

The chronological order of the service beams of the terminal;

The quality of the service beam of the terminal;

The chronological order of the beams measured by the terminal;

The quality of the beam measured by the terminal.
The terminal of claim 14, wherein the generating module further comprises:

a second generation submodule, configured to: if the number of the recorded beam information is greater than N, select the N pieces of information in the beam information that are closest to the current time to generate beam history information of the terminal; where N is the beam The maximum number of records allowed by history information, N is an integer greater than one.
The terminal of claim 14, wherein the recording module comprises:

a first recording submodule, configured to record beam information whose beam quality or number of beams exceeds a first preset threshold;

The reporting module includes:

The first reporting sub-module is configured to report beam information of the beam history information or the number of beams exceeding the second preset threshold to the network device.
The terminal according to claim 12, wherein the reporting module comprises:

The second reporting sub-module is configured to report the beam history information to the network device when detecting that the preset trigger reporting condition is met;

or,

The third reporting sub-module is configured to report the beam history information to the network device when receiving the request for reporting the beam history information by the network device.
The terminal according to claim 18, wherein the third reporting sub-module comprises:

a first receiving unit, configured to receive a query request sent by the network device to query whether there is available beam history information;

a first querying unit, configured to query, according to the query request, whether there is available beam history information;

The first reporting unit is configured to report the available beam history information to the network device if yes;

Or, if yes, feeding back to the network device feedback information of the available beam history information; the receiving network device reporting the available beam history information reporting request according to the request sent by the feedback information; and according to the reporting request, the available information is available. The beam history information is reported to the network device.
The terminal according to claim 18, wherein the third reporting sub-module further comprises:

a second receiving unit, configured to receive, by the network device, a beam current history report request that is available for reporting the request;

a second querying unit, configured to query, according to the reporting request, whether there is available beam history information;

The second reporting unit is configured to report the available beam history information to the network device if yes.
The terminal according to claim 19 or 20, wherein the available beam history information is beam history information available under the target system.
The terminal according to claim 12, wherein the reporting module further comprises:

The fourth reporting sub-module is configured to report the beam history information to the network device by using an RRC message during the completion of the RRC connection establishment/recovery of the RRC connection;

or,

The fifth reporting sub-module is configured to report the beam history information to the network device by using an RRC message during the terminal information reporting or measurement information reporting process;

or,

a sixth reporting sub-module, configured to report beam history information to the network device by using a predefined RRC message;

or,

The seventh reporting sub-module is configured to report the beam history information to the network device by using the control information of the MAC layer CE or the layer 1;

or,

The eighth reporting sub-module is configured to report the beam history information to the network device by using signaling or a data packet when the terminal is in the inactive inactive state.
A terminal comprising a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program being executed by the processor to implement any one of claims 1 to 11 The steps of the beam history information transmission method described in the item.
A beam history information transmission method is applied to a network device side, and includes:

The beam history information reported by the receiving terminal when the reporting condition is met;

Performing paging or mobility management on the terminal according to the beam history information.
The beam history information transmission method according to claim 24, wherein the beam history information comprises at least one of the following information:

The cell of the historical cell globally identifies the frequency information of the CGI or the physical cell identifier PCI; the historical cell is the cell where the historical service beam of the terminal is located;

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

a length of dwell time and a dwell start time information of the terminal on the historical service beam;

Measurement time information and measurement position information corresponding to beam measurement information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Bitmap information of the synchronization signal block corresponding to the historical service beam;

Navigation information associated with the historical service beam, the navigation information being used to determine a historical location, speed, direction of movement, and angle of the terminal.
The beam history information transmission method according to claim 24, further comprising, before the step of the beam terminal information reported by the receiving terminal when the reporting condition is met,

Sending a request to the terminal to report the available beam history information.
The beam history information transmission method according to claim 26, wherein the step of transmitting a report request for reporting the available beam history information to the terminal includes:

Sending a query request to the terminal to inquire whether there is available beam history information;

Receiving, by the terminal, feedback information of the available beam history information that is fed back according to the query request;

And sending, according to the feedback information, a beam beam history information reporting request that is available for reporting to the terminal.
The beam history information transmission method according to claim 26 or 27, wherein the available beam history information is beam history information available in the target system.
The beam history information transmission method according to claim 24, wherein the step of the beam history information reported by the receiving terminal when the reporting condition is met includes:

Receiving beam history information reported by the terminal through the RRC message during the completion of the RRC connection establishment/recovery process;

or,

Receiving beam history information sent by the terminal through an RRC message during the terminal information reporting or measurement information reporting process;

or,

Receiving beam history information sent by the terminal by using a predefined RRC message;

or,

Receiving beam history information sent by the terminal by using control information of the MAC layer CE or layer 1;

or,

Receiving beam history information transmitted by a terminal or a data packet in an inactive inactive state.
A network device, including:

a receiving module, configured to receive beam history information reported by the terminal when the reporting condition is met;

And a processing module, configured to perform paging or mobility management on the terminal according to the beam history information.
The network device of claim 30, wherein the beam history information comprises at least one of the following information:

The cell of the historical cell globally identifies the frequency information of the CGI or the physical cell identifier PCI; the historical cell is the cell where the historical service beam of the terminal is located;

The identity information of the beam, the beam identifier, and/or the time-frequency resource information; the beam is a beam corresponding to each reference signal of the historical cell;

Beam measurement information of the historical service beam;

Antenna panel information of the historical service beam;

a length of dwell time and a dwell start time information of the terminal on the historical service beam;

Measurement time information and measurement position information corresponding to beam measurement information of the historical service beam;

Pseudo-co-location QCL information of the historical service beam;

Bitmap information of the synchronization signal block corresponding to the historical service beam;

Navigation information associated with the historical service beam, the navigation information being used to determine a historical location, speed, direction of movement, and angle of the terminal.
The network device of claim 30, further comprising:

And a sending module, configured to send, to the terminal, a report request for reporting the available beam history information.
The network device of claim 32, wherein the sending module comprises:

a first sending submodule, configured to send, to the terminal, a query request for asking whether there is available beam history information;

a receiving submodule, configured to receive, by the terminal, feedback information of the available beam history information that is fed back according to the query request;

And a second sending submodule, configured to send, according to the feedback information, a report request to report the available beam history information to the terminal.
The network device according to claim 32 or 33, wherein the available beam history information is beam history information available under the target system.
The network device of claim 30, wherein the receiving module comprises:

a first receiving submodule, configured to receive beam history information reported by the terminal through an RRC message during a radio resource control RRC connection setup completion/recovery process;

or,

a second receiving submodule, configured to receive beam history information sent by the terminal through an RRC message during a terminal information reporting or measurement information reporting process;

or,

a third receiving submodule, configured to receive beam history information sent by the terminal by using a predefined RRC message;

or,

a fourth receiving submodule, configured to receive, by using MAC layer CE or layer 1 control information, beam history information sent by the terminal;

or,

The fifth receiving submodule is configured to receive beam history information that is sent by the terminal or the data packet in the inactive inactive state.
A network device comprising a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program being executed by the processor to implement any of claims 24 to 29 A step of the beam history information transmission method described.
A computer readable storage medium storing a computer program, the computer program being executed by a processor to implement the steps of the beam history information transmission method according to any one of claims 1 to 11 or 24 to 29.