Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
As shown in fig. 1, the method for transmitting beam history information according to the embodiment of the present invention is applied to a terminal side, and specifically includes the following steps:
step 11: and when the reporting condition is met, reporting the beam history information to the network equipment.
When the terminal meets a certain reporting condition, the terminal reports the currently stored beam history information to the network equipment. The beam history information is beam information of a history beam associated with the terminal, and is mainly used for representing beam information of the terminal history movement information. It should be noted that the triggering method for reporting the beam history information by the terminal includes two methods, namely, an active triggering method and a passive triggering method, and specifically, meeting the reporting condition includes: and meeting the preset triggering and reporting condition, or receiving a reporting request which is sent by the network equipment and requests to report the beam history information. The following embodiment will describe the reporting of the beam history information in detail by combining the two modes.
Mode one, active reporting mode
The step 11 is specifically as follows: and the terminal detects whether a preset triggering reporting condition is met, and reports the beam history information to the network equipment when the preset triggering reporting condition is met.
The preset trigger reporting condition is a predefined trigger reporting condition or a trigger reporting condition specified by a protocol, for example, when a serving beam of the terminal is detected to be switched, the serving beam before switching is recorded in beam history information and reported to the network device, or when a cell to which the terminal belongs is detected to be changed, a beam associated with the cell before switching is recorded in the beam history information and reported to the network device. Or after a certain preset time, reporting the current existing beam history information to the network equipment, specifically, the terminal may report the beam history information value once, or periodically report the beam history information recorded by itself to the network equipment according to a preset period.
Mode two, passive reporting mode
The step 11 is specifically as follows: when a reporting request for requesting to report the beam history information sent by the network equipment is received, reporting the beam history information to the network equipment.
Here, the terminal only detects whether a trigger condition of reporting configuration is met when the network device configures the beam history information reporting configuration for the terminal, and reports the beam history information if the trigger condition is met.
Further, it should be noted that in the two reporting manners, 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 partial information in all the beam information. When reporting partial beam information, the following method can be specifically referred to: and reporting the beam information of which the beam quality or the beam number exceeds a second preset threshold value in the beam history information to the network equipment. For example, assuming that the beam quality is classified into five levels, i.e., 1, 2, 3, 4, and 5, and the predefined second preset threshold is level 3, when reporting the beam history information to the network device, the terminal only reports to the network device the beam information with the beam quality higher than level 3 in the recorded beam information. Or, assuming that 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 3 or more historical beams.
Further, the beam history information includes at least one of the following information:
frequency point information of Cell Global Identifier (CGI) or Physical Cell Identifier (PCI) of the history Cell. The history cell is a cell where a history service beam of the terminal is located.
Identity information, beam identification and/or time-frequency resource information of the beam; the beam is corresponding to each reference signal of the history cell. I.e. the ID, identity and time-frequency resource of the beams of various reference signals in the cell to which the terminal previously belongs.
Beam measurement information of a history service beam of the terminal; that is, the measurement quantity information of the service beam where the terminal has been located in the past may be specifically measurement quantity information of layer one and layer three, such as: reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indication (RSSI), Signal to Interference plus Noise Ratio (SINR), Channel Quality Indication (CQI), and the like. The service beam is a beam for providing a service for the terminal in a connected state, or a carrier beam of a reference signal of the terminal in the connected state.
Antenna panel (panel) information of historical service beams; i.e. antenna panel information of the service beam the terminal has been in.
The terminal dwell time length and dwell start-stop time information on the historical service beam; i.e. the length of the terminal's stay on the past service beam and the start and end times of the stay. Or, the time length and the start/end time of the terminal leaving service (out of service) or leaving coverage (out of coverage) on the historical service beam.
Measuring time information and measuring position information corresponding to the beam measuring information of the historical service beam; that is, the terminal records the measurement amount information of a certain service beam at different time points and different positions in the past.
Pseudo Co-Location (QCL) information of historical service beams; that is, the terminal transmits the past service beam from which antenna port, and indicates which service beams are transmitted from the same antenna port.
Bitmap information of a Synchronization Signal Block (SSB) corresponding to a history service beam; namely, the bitmap information of the SSB sending position configured by the broadcast and/or Radio Resource Control (RRC) dedicated signaling in the system message. For example, if the bitmap information of the SSB is "00101100", the beams corresponding to numbers 3, 5, and 6 are transmitted, and 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 being used for determining historical position, speed, moving direction and angle of the terminal, specifically, the navigation information includes inertial navigation information directly indicating the historical position, speed, moving direction and angle of the terminal, and the like, and other information from which the historical position, speed, moving direction and angle of the terminal can be derived. The navigation information can be reported together with the beam measurement information of the historical service beam.
It is worth noting, among other things, that the beam history information is stored in a predefined variable, which may be configured by the network device or defined directly by the protocol.
Further, before step 11, the method further includes a step of the terminal recording beam history information, specifically: recording corresponding beam information when a preset recording condition is met; and generating beam history information of the terminal according to the recorded beam information.
Wherein the preset recording condition comprises at least one of the following items:
the cell to which the terminal belongs is changed; namely, the terminal changes the Cell, specifically including changing a Primary Cell (PCell), a Secondary Cell (SCell), and a Primary/Secondary Cell (PSCell).
The network system of the terminal is changed; that is, the terminal changes the network type, 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 method includes that the terminal is switched from an in-service (in-service) state or an in-coverage (in-coverage) state to an out-of-service (out of service) state or an out-of-coverage (out of coverage) state, and the terminal is switched from the out-of-service (out of service) state or the out-of-coverage (out of coverage) state to the in-service (in-service) state or the in-coverage (in coverage) state.
The antenna panel where the terminal is located is changed; i.e. the antenna panel in which the terminal changes, i.e. the antenna panel in which the different beam is located.
A service beam or an attachment beam in which the terminal is located is changed; wherein, the attached beam is a beam for the terminal to read the SSB in an idle state.
The type of the beam used by the terminal changes; that is, the terminal switches from one beam to another beam, such as the terminal switches from a beam using the SSB to a beam using a Channel state indication reference Signal (CSI-RS).
The beam use state of the reference signal corresponding to the terminal is changed; such as the terminal switching from a beam that uses/does not use a reference signal to a beam that does not use/uses a 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.
In order to improve the availability of the recorded beam information, the terminal may filter part of the beam information according to a preset condition, and only retain possibly useful beam information. Specifically, the method comprises the following steps: and recording the beam information of which the beam quality or the beam number exceeds a first preset threshold value. It should be noted that the first preset threshold is only used as an illustration 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 setting of the first preset threshold may be set according to the configuration of the network device, may also be defined by the terminal, or may be defined directly 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: and sequencing the recorded beam information according to a preset sequence to generate beam history information of the terminal.
Wherein the preset sequence comprises one of the following sequences:
the frequency sequence of terminal residence on different wave beams; i.e., how often the terminal camps on certain beams, may be ordered by frequency.
The time sequence of the service beams of the terminal; i.e. recording in chronological order of the beams that have served the terminal.
The quality order of the service beams of the terminal; i.e. the records are sorted according to the quality of the beam serving the terminal.
The time sequence of the beams measured by the terminal; namely, the terminal records according to the time sequence of measuring different beams.
And the quality sequence of the beams measured by the terminal, namely the terminal sorts and records according to the quality of the measured beams of different beams.
Further, because of the mobility of the terminal and the instability of the network state, the beam information related to the terminal is continuously updated, and in order to ensure the validity of the beam history information recorded by the terminal, the step of generating the beam history information of the terminal according to the recorded beam information includes: if the number of the recorded beam information is larger than N, selecting N pieces of information which are nearest to the current moment in the beam information to generate beam history information of the terminal; wherein, N is the maximum record number allowed by the beam history information, and N is an integer greater than 1. Where N may be terminal predefined or may be network device configured. It is worth pointing out that, after the beam history information is generated, if the terminal records new beam information, and the total number of the beam information is greater than N, the beam information recorded earliest in the original beam history information is deleted, and the beam information recorded latest is supplemented, so as to realize the continuous update of the beam history information.
The beam history information, the recording of the beam history information, and the generation process are introduced above, and the following description will describe a process in which the terminal reports the beam history information by taking passive reporting as an example.
Specifically, when receiving a request for reporting beam history information sent by a network device, reporting the beam history information to the network device includes: receiving an inquiry request for inquiring whether available beam history information exists, wherein the inquiry request is sent by network equipment; inquiring whether available beam history information exists according to the inquiry request; if yes, feeding back feedback information of available beam history information to the network equipment; receiving a request for reporting available beam history information sent by the network equipment according to the feedback information; and reporting the available beam history information to the network equipment according to the reporting request. Wherein, the flow here is: when the terminal is required to report the beam history information, the network equipment firstly sends an inquiry request for requesting whether available beam history information exists to the terminal, when the terminal receives the inquiry request, the terminal inquires whether the available beam history information exists, and if the available beam history information exists, the terminal feeds back feedback information of the available beam history information to the network equipment. After receiving the feedback information, the network device sends a reporting request for requesting to report the beam history information to the terminal, and the terminal reports the available beam history information to the network device according to the reporting request.
Or, in order to simplify the interactive flow and save signaling overhead, when receiving a request for reporting beam history information sent by the network device, reporting the beam history information to the network device according to the reporting request includes: receiving an inquiry request for inquiring whether available beam history information exists, wherein the inquiry request is sent by network equipment; inquiring whether available beam history information exists according to the inquiry request; and if so, reporting the available beam history information to the network equipment. Wherein, the flow here is: when the terminal is required to report the beam history information, the network equipment firstly sends a query request for requesting whether available beam history information exists to the terminal, when the terminal receives the query request, the terminal queries whether the available beam history information exists, and if the available beam history information exists, the queried available beam history information is directly reported to the network equipment.
It is worth pointing out that the available beam history information is available beam history information in the target system. The network device may further instruct the terminal to query or report available beam history information in a target network type, where the target network type may be: at least one of LTE system, NR system and other network systems. For example, the network device may request the terminal to query or report the beam history information available in the NR system in the LTE system, or request the terminal to query or report the beam history information available in the LTE system in the NR system.
Specifically, a query request for inquiring whether beam history information in an available target network format exists is received, wherein the query request is sent by the network equipment. Suppose that a network device sends an inquiry request for inquiring whether available beam history information exists in an LTE system to a terminal, the terminal inquires whether the available beam history information exists in the LTE system according to the inquiry request, and sends feedback information to the network device when the available beam history information exists in the LTE system. Or receiving a reporting request sent by the network equipment for requesting to report the beam history information under the available target network system. Suppose that the network device sends a report request for requesting to report the history information of the beams available in the LTE system to the terminal, and the terminal reports the inquired history information of the beams available in the LTE system to the network device according to the report request.
Specifically, the step of receiving a query request for inquiring whether available beam history information exists, which is sent by the network device, includes: in the process of establishing/recovering the radio resource control RRC connection, a query request sent by a network device through an RRC message for inquiring whether available beam history information exists is received. Specifically, the network device sends a query request inquiring whether available beam history information exists to the terminal through an RRC Connection setup (rrcconnectionsetup) message, an RRC Connection resume (RRC Connection resume) message, an RRC reconfiguration (rrcreconfigurability) message, or a handover command (HO command) message. Accordingly, the step of feeding back feedback information that there is beam history information available to the network device includes: in the process of completing/recovering the establishment of the radio resource control RRC connection, feedback information of available beam history information is fed back to the network equipment through an RRC message. Specifically, when inquiring that available beam history information exists, the terminal may feed back the feedback information of the available beam history information to the network device through an RRC Connection setup complete (RRC Connection setup complete) message, an RRC Connection recovery complete (RRC Connection resume complete) message, an RRC reconfiguration complete (RRC reconfiguration complete) message, or a handover complete (HO complete) message.
Alternatively, a query request sent by the network device through a predefined RRC message is received to inquire whether available beam history information exists. Accordingly, the step of feeding back feedback information that there is beam history information available to the network device includes: feedback information that there is beam history information available is fed back to the network device through a predefined RRC message.
Or, receiving an inquiry request for inquiring whether available beam history information exists, which is sent by the network device through a Control Element (CE) of a Media Access Control (MAC) layer or Control information of a layer one. Accordingly, the step of feeding back feedback information that there is beam history information available to the network device comprises: and feeding back feedback information of available beam history information to the network equipment through a Control Element (CE) of a Medium Access Control (MAC) layer or control information of a layer one.
Or, when the terminal is in the inactive state, receiving an inquiry request for inquiring whether available beam history information exists, wherein the inquiry request is sent by the network equipment through signaling or a data packet. Accordingly, the step of feeding back feedback information that there is beam history information available to the network device includes: when the network equipment is in the inactive state, the feedback information of the available beam history information is fed back to the network equipment through signaling or data packets.
Further, in order to simplify the interaction flow and save signaling overhead, when receiving a request for reporting beam history information sent by the network device, the step of reporting the beam history information to the network device according to the report request further includes: receiving a request for reporting available beam history information sent by network equipment; inquiring whether available beam history information exists according to the reporting request; and if so, reporting the available beam history information to the network equipment. Wherein, the flow here is: when the terminal is required to report the beam history information, the network equipment sends a reporting request for requesting to report the beam history information to the terminal, the terminal inquires whether available beam history information exists according to the reporting request, and if the available beam history information exists, the inquired available beam history information is directly reported to the network equipment.
Specifically, the network device may further instruct the terminal to query or report available beam history information in a target network type, where the target network type may be: at least one of LTE system, NR system and other network systems. And receiving a reporting request which is sent by the network equipment and requests to report the beam history information under the available target network system. Suppose that the network device sends a report request for requesting to report the history information of the beams available in the LTE system to the terminal, and the terminal reports the inquired history information of the beams available 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 following means:
reporting the beam history information to the network equipment through an RRC message in the process of completing establishment/recovery of the RRC connection; specifically, the terminal may report the beam history information to the network device through an RRC Connection setup complete (RRC Connection setup complete) message, an RRC Connection recovery complete (RRC Connection resume complete) message, an RRC reconfiguration complete (RRC reconfiguration complete) message, or a handover complete (HO complete) message.
And reporting the beam history information to the network equipment through an RRC message in the process of reporting the terminal information or the measurement information. Correspondingly, the step of receiving the request for reporting the beam history information sent by the network device includes: and in the process of terminal information request or measurement information configuration, receiving a reporting request which is sent by the network equipment through an RRC message and requests to report the beam history information. Specifically, the network device sends a report request for requesting reporting of available beam history information to the terminal through a terminal information request (UE information request) message or a Measurement configuration (Measurement configuration) message. Accordingly, the terminal reports the beam history information to the network device through a terminal information report (UE information response) message or a Measurement report (Measurement report) message.
Or reporting the beam history information to the network equipment through a predefined RRC message; correspondingly, the step of receiving the request for reporting the beam history information sent by the network device includes: and receiving a request for reporting the beam history information sent by the network equipment through a predefined RRC message.
Or reporting the beam history information to the network equipment through the control information of the MAC layer CE or the layer one; correspondingly, the step of receiving the request for reporting the beam history information sent by the network device includes: and receiving a reporting request for requesting to report the beam history information, which is sent by the network equipment through the control information of the MAC layer CE or the layer one.
Or when the terminal is in the inactive state, reporting the beam history information to the network equipment through a signaling or a data packet. Correspondingly, the step of receiving the request for reporting the beam history information sent by the network device includes: and when the network equipment is in the inactive state, receiving a reporting request which is sent by the network equipment through a signaling or a data packet and requests to report the history information of the wave beam.
In the beam history information transmission method of the embodiment of the invention, the terminal reports the beam history information to the network equipment when the reporting condition is met, the beam history information can embody the historical movement information of the terminal, and the network equipment can optimize the subsequent paging process of the terminal according to the beam history information after receiving the beam history information of the terminal and accurately manage the mobility of the terminal.
The foregoing embodiments respectively describe in detail the beam history information transmission methods in different scenarios, and the following embodiments further describe the corresponding terminals with reference to the accompanying drawings.
As shown in fig. 2, the terminal 200 according to the embodiment of the present invention can implement details of a method for reporting beam history information to a network device when a reporting condition is satisfied in the foregoing embodiment, and achieve the same effect, where the terminal 200 specifically includes the following functional modules:
the reporting module 210 is configured to report the beam history information to the network device when the reporting condition is met.
Wherein the beam history information comprises at least one of:
frequency point information of a cell global unified identifier (CGI) or a Physical Cell Identifier (PCI) of a historical cell; the history cell is a cell where a history service beam of the terminal is located;
identity information, beam identification and/or time-frequency resource information of the beam; the wave beam is a wave beam corresponding to each reference signal of the historical cell;
beam measurement information for historical service beams;
antenna panel information for historical service beams;
the terminal dwell time length and dwell start-stop time information on the historical service beam;
measuring time information and measuring position information corresponding to the beam measuring information of the historical service beam;
pseudo co-located QCL information for historical service beams;
bitmap information of a synchronization signal block corresponding to a historical service beam; and
navigation information associated with the historical service beams, the navigation information being used to determine historical position, velocity, direction of movement, and angle of the terminal.
Wherein, the terminal still includes:
the recording module is used for recording corresponding beam information when a preset recording condition is met;
the generating module is used for generating beam history information of the terminal according to the recorded beam information;
wherein the preset recording condition comprises at least one of the following items:
the cell to which the terminal belongs is changed;
the network system of the terminal is changed;
the service or coverage status of the terminal changes;
the antenna panel where the terminal is located is changed;
a service beam or an attachment beam in which the terminal is located is changed;
the type of the beam used by the terminal changes;
the beam use state of the reference signal corresponding to the terminal is changed;
the terminal recognizes that the intensity of the beam is changed.
Wherein, the generation module includes:
the first generation submodule is used for sequencing the recorded beam information according to a preset sequence and generating beam historical information of the terminal;
wherein the preset sequence comprises one of the following sequences:
the frequency sequence of terminal residence on different wave beams;
the time sequence of the service beams of the terminal;
the quality order of the service beams of the terminal;
the time sequence of the beams measured by the terminal; and
the quality of the beams measured by the terminal is in good or bad order.
Wherein, the generation module further comprises:
the second generation submodule is used for selecting N pieces of information which are nearest to the current moment in the beam information to generate beam historical information of the terminal if the number of the recorded beam information is larger than N; wherein, N is the maximum record number allowed by the beam history information, and N is an integer greater than 1.
Wherein, the record module includes:
the first recording submodule is used for recording the beam information of which the beam quality or the beam number exceeds a first preset threshold;
the reporting module comprises:
and the first reporting submodule is used for reporting the beam information of which the beam quality or the beam number exceeds a second preset threshold value in the beam historical information to the network equipment.
Wherein, the reporting module includes:
the second reporting submodule is used for reporting the beam history information to the network equipment when the condition that the preset triggering reporting condition is met is detected;
or,
and the third reporting submodule is used for reporting the beam history information to the network equipment when receiving a reporting request which is sent by the network equipment and requests to report the beam history information.
Wherein, the third reporting submodule comprises:
a first receiving unit, configured to receive an inquiry request for inquiring whether available beam history information exists, where the inquiry request is sent by a network device;
a first query unit, configured to query whether available beam history information exists according to a query request;
the first reporting unit is used for reporting the available beam history information to the network equipment if the available beam history information exists;
or if the beam history information exists, feeding back feedback information of available beam history information to the network equipment; receiving a request for reporting available beam history information sent by the network equipment according to the feedback information; and reporting the available beam history information to the network equipment according to the reporting request.
Wherein, the third reporting sub-module further comprises:
a second receiving unit, configured to receive a request for requesting reporting of available beam history information, where the request is sent by a network device;
the second query unit is used for querying whether available beam history information exists or not according to the reporting request;
and a second reporting unit, configured to report the available beam history information to the network device if the available beam history information exists.
The available beam history information is available beam history information in a target system.
Wherein, the reporting module further comprises:
the fourth reporting submodule is used for reporting the beam history information to the network equipment through an RRC message in the process of completing establishment/recovery of the RRC connection;
or,
a fifth reporting submodule, configured to report the beam history information to the network device through an RRC message in a process of reporting the terminal information or the measurement information;
or,
a sixth reporting submodule, configured to report the beam history information to the network device through a predefined RRC message;
or,
the seventh reporting submodule is used for reporting the beam history information to the network equipment through the control information of the MAC layer CE or the layer one;
or,
and the eighth reporting submodule is used for reporting the beam history information to the network equipment through a signaling or a data packet when the terminal is in the inactive state.
The available beam history information is available beam history information in a target system.
It is worth pointing out that, when the terminal of the embodiment of the present invention meets the reporting condition, the terminal reports the beam history information to the network device, where the beam history information can reflect the historical movement information of the terminal, and after receiving the beam history information of the terminal, the network device can optimize the subsequent paging procedure of the terminal according to the beam history information and perform accurate mobility management on the terminal.
To better achieve the above object, further, fig. 3 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present invention, where the terminal 30 includes, but is not limited to: radio frequency unit 31, network module 32, audio output unit 33, input unit 34, sensor 35, display unit 36, user input unit 37, interface unit 38, memory 39, processor 310, and power supply 311. Those skilled in the art will appreciate that the terminal structure shown in fig. 3 is not intended to be limiting and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.
Wherein, the processor 310 controls the rf unit 31 to execute: and when the reporting condition is met, reporting the beam history information to the network equipment.
The terminal of the embodiment of the invention reports the beam history information to the network equipment when the reporting condition is met, the beam history information can reflect the history mobile information of the terminal, and the network equipment can optimize the subsequent paging process of the terminal according to the beam history information after receiving the beam history information of the terminal and accurately manage the mobility of the terminal.
It should be understood that, in the embodiment of the present invention, the radio frequency unit 31 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 310; in addition, the uplink data is transmitted to the base station. Typically, the 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 frequency unit 31 can also communicate with a network and other devices through a wireless communication system.
The terminal provides wireless broadband internet access to the user via the network module 32, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media.
The audio output unit 33 may convert 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. Also, the audio output unit 33 may also provide audio output related to a specific function performed by the terminal 30 (e.g., a call signal reception sound, a message reception sound, etc.). 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, and the Graphics processor 341 processes image data of a 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 processed image frames may be displayed on the display unit 36. The image frames processed by the graphic processor 341 may be stored in the memory 39 (or other storage medium) or transmitted via the radio frequency unit 31 or the network module 32. The microphone 342 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 31 in case of the phone call mode.
The terminal 30 also includes at least one sensor 35, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 361 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 361 and/or the backlight when the terminal 30 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 35 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which are not described in detail herein.
The display unit 36 is used to display information input by the user or information provided to the user. The Display unit 36 may include a Display panel 361, and the Display panel 361 may 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 may be used to receive input numeric or character information and 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. Touch panel 371, also referred to as a touch screen, may collect touch operations by a user on or near touch panel 371 (e.g., operations by a user on or near touch panel 371 using a finger, a stylus, or any suitable object or attachment). The touch panel 371 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 310, and receives and executes commands sent by the processor 310. In addition, the touch panel 371 may be implemented in various types, such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 37 may include other input devices 372 in addition to the touch panel 371. In particular, the other input devices 372 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described herein again.
Further, the touch panel 371 may be overlaid on the display panel 361, and when the touch panel 371 detects a touch operation thereon or nearby, the touch panel 371 is transmitted to the processor 310 to determine the type of the touch event, and then the processor 310 provides a corresponding visual output on the display panel 361 according to the type of the touch event. Although the touch panel 371 and the display panel 361 are shown in fig. 3 as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 371 and the display panel 361 may be integrated to implement the input and output functions of the terminal, and is not limited herein.
The interface unit 38 is an interface for connecting an external device to the terminal 30. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 38 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 30 or may be used to transmit data between the terminal 30 and an external device.
The memory 39 may be used to store software programs as well as various data. The memory 39 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program 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 store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 39 may include high speed random access memory, and may also include non-volatile 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, connects various parts of the entire terminal using various interfaces and lines, performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 39 and calling data stored in the memory 39, thereby performing overall monitoring of the terminal. Processor 310 may include one or more processing units; preferably, the processor 310 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 310.
The terminal 30 may further include a power supply 311 (such as a battery) for supplying power to various components, and preferably, the power supply 311 may be logically connected to the processor 310 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.
In addition, the terminal 30 includes some functional modules that are not shown, and are not described in detail herein.
Preferably, an embodiment of the present invention further provides a terminal, which includes a processor 310, a memory 39, and a computer program stored in the memory 39 and capable of running on the processor 310, where the computer program is executed by the processor 310 to implement each process of the foregoing beam history information transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. A terminal may be a wireless terminal or a wired terminal, and a wireless terminal may be a device providing voice and/or other service data connectivity to a user, a handheld device having a wireless connection function, or other processing devices connected to a wireless modem. A wireless terminal, which may be a mobile terminal such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal, e.g., a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more core networks via a Radio Access Network (RAN), and may exchange language and/or data with the RAN. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs) are used. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an access Terminal (access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Equipment (User device User Equipment), which are not limited herein.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the foregoing beam history information transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
The foregoing embodiment describes the beam history information transmission method of the present invention from the terminal side, and the following embodiment further describes the beam history information transmission method of the network device side with reference to the drawings.
As shown in fig. 4, the method for transmitting beam history information according to the embodiment of the present invention is applied to a network device, and specifically includes the following steps:
step 41: and receiving the beam history information reported by the terminal when the reporting condition is met.
The beam history information is beam information of a history beam associated with the terminal, and is mainly used for representing beam information of the terminal history movement information. It should be noted that the triggering method for reporting the beam history information by the terminal includes two methods, namely, an active triggering method and a passive triggering method, which are described above in the first and second embodiments, and therefore, the description thereof is omitted here.
Step 42: and paging or mobility management is carried out on the terminal according to the beam history information.
After obtaining the beam history information of the terminal, the network device integrates corresponding data content to optimize a subsequent paging process for the terminal or a mobility management process for the terminal. Specifically, the network device may predict the current location of the terminal according to the beam history information, so as to perform directional paging on the terminal, thereby improving the success rate of paging. Or, the network device determines whether to switch a cell or a service beam for the terminal according to the beam history information, so as to implement accurate mobility management for the terminal. In addition, the network device can also perform optimization of other procedures according to the beam history information.
Wherein the beam history information comprises at least one of:
frequency point information of a cell global unified identifier (CGI) or a Physical Cell Identifier (PCI) of a historical cell; the history cell is a cell where a history service beam of the terminal is located;
identity information, beam identification and/or time-frequency resource information of the beam; the beam is corresponding to each reference signal of the history cell. I.e. the ID, identity and time-frequency resource of the beams of various reference signals in the cell to which the terminal previously belongs.
Beam measurement information for historical service beams; specifically, the measurement quantity information of layer one and layer three may be, for example: RSRP, RSRQ, RSSI, SINR, CQI, etc. The service beam is a beam for providing a service for the terminal in a connected state, or a carrier beam of a reference signal of the terminal in the connected state.
Antenna panel information for historical service beams;
the terminal dwell time length and dwell start-stop time information on the historical service beam; or, the time length and the start/end time of the terminal leaving service (out of service) or leaving coverage (out of coverage) on the historical service beam.
Measuring time information and measuring position information corresponding to the beam measuring information of the historical service beam;
pseudo co-located QCL information for historical service beams, wherein the QCL information is used to indicate which service beams are emitted from the same antenna port;
bitmap information of a synchronization signal block corresponding to a historical service beam; and
navigation information associated with the history service beam, the navigation information being used for determining the history position, speed, moving direction and angle of the terminal, the navigation information including inertial navigation information directly indicating the history position, speed, moving direction and angle of the terminal, etc., and other information from which the history position, speed, moving direction and angle of the terminal can be derived.
Wherein, step 41 further comprises: and sending a reporting request for requesting to report the available beam history information to the terminal.
Specifically, the step of sending a report request for requesting reporting of the available beam history information to the terminal includes: and sending a report request for requesting to report the beam history information under the available target network system to the terminal. That is, the network device may further instruct the terminal to query or report available beam history information in a target network type, where the target network type may be: at least one of LTE system, NR system and other network systems.
Further, the step of sending a report request for requesting reporting of the beam history information to the terminal includes: transmitting an inquiry request inquiring whether available beam history information exists to the terminal; the receiving terminal feeds back feedback information with available beam history information according to the query request; and sending a request for reporting the available beam history information to the terminal according to the feedback information.
Wherein the step of transmitting an inquiry request inquiring whether there is available beam history information to the terminal includes: and sending an inquiry request for inquiring whether beam history information under an available target network system exists to the terminal.
Further, the step of transmitting a query request inquiring whether there is available beam history information to the terminal may be implemented by:
in the radio resource control RRC connection establishment/recovery procedure, a query request inquiring whether there is available beam history information is transmitted to the terminal through an RRC message.
Alternatively, a query request inquiring whether there is available beam history information is transmitted to the terminal through a predefined RRC message
Alternatively, an inquiry request inquiring whether there is available beam history information is transmitted to the terminal through a Control Element (CE) of a Media Access Control (MAC) layer or Control information of a layer one.
Or, when the terminal is in the inactive state, sending an inquiry request for inquiring whether available beam history information exists to the terminal through signaling or a data packet.
Correspondingly, the step of the receiving terminal feeding back the feedback information with the available beam history information according to the query request comprises the following steps:
in the process of completing establishment/recovery of Radio Resource Control (RRC) connection, receiving feedback information of available beam history information fed back by a terminal through an RRC message;
or,
receiving feedback information of available beam history information fed back by the terminal through a predefined RRC message;
or,
receiving feedback information of available beam history information fed back by a Control Element (CE) of a Media Access Control (MAC) layer or control information of a layer one by a terminal;
or,
when the terminal is in an inactive state, receiving feedback information of available beam history information fed back by the terminal through signaling or data packets.
Further, the step of sending a report request for requesting reporting of the beam history information to the terminal may be implemented by:
in the process of establishing/recovering the Radio Resource Control (RRC) connection, a reporting request for requesting to report available beam history information is sent to a terminal through an RRC message; correspondingly, the step of receiving the beam history information reported by the terminal includes: and receiving the beam history information reported by the terminal through the RRC message in the process of completing establishment/recovery of the RRC connection.
Or, in the process of terminal information request or measurement information configuration, sending a report request for requesting to report available beam history information to the terminal through an RRC message; correspondingly, the step of receiving the available beam history information reported by the terminal is as follows: and receiving available beam history information reported by the terminal through an RRC message in the process of reporting the terminal information or the measurement information.
Or sending a reporting request for requesting to report the available beam history information to the terminal through a predefined RRC message; correspondingly, the step of receiving the available beam history information reported by the terminal is as follows: and receiving available beam history information reported by the terminal through a predefined RRC message.
Or, sending a report request for requesting to report available beam history information to the terminal through the control information of the MAC layer CE or the layer one; correspondingly, the step of receiving the available beam history information reported by the terminal is as follows: and receiving available beam history information reported by the terminal through the control information of the MAC layer CE or the layer one.
Or when the terminal is in the inactive state, sending a reporting request for requesting to report the available beam history information to the terminal through a signaling or a data packet; correspondingly, the step of receiving the available beam history information reported by the terminal is as follows: and receiving beam history information reported by the terminal in the inactive state through a signaling or a data packet.
In the beam history information transmission method of the embodiment of the invention, the network equipment receives the beam history information reported by the terminal when the reporting condition is met, the beam history information can embody the historical movement information of the terminal, and after the network equipment receives the beam history information of the terminal, the network equipment can optimize the subsequent paging process of the terminal according to the beam history information and accurately manage the mobility of the terminal.
The foregoing embodiments describe a method for transmitting beam history information in different scenarios, and a network device corresponding to the method will be further described with reference to the accompanying drawings.
As shown in fig. 5, the network device 500 according to the embodiment of the present invention can implement the beam history information reported by the receiving terminal when the reporting condition is satisfied in the above embodiment; according to the beam history information, the details of the method for paging or mobility management are performed on the terminal, and the same effect is achieved, the network device 500 specifically includes the following functional modules:
a receiving module 510, configured to receive beam history information reported by a terminal when a reporting condition is met;
and the processing module 520 is configured to perform paging or mobility management on the terminal according to the beam history information.
Wherein the beam history information comprises at least one of:
frequency point information of a cell global unified identifier (CGI) or a Physical Cell Identifier (PCI) of a historical cell; the history cell is a cell where a history service beam of the terminal is located;
identity information, beam identification and/or time-frequency resource information of the beam; the beam is corresponding to each reference signal of the history cell.
Beam measurement information for historical service beams;
antenna panel information for historical service beams;
the terminal dwell time length and dwell start-stop time information on the historical service beam;
measuring time information and measuring position information corresponding to the beam measuring information of the historical service beam;
pseudo co-located QCL information for historical service beams;
bitmap information of a synchronization signal block corresponding to a historical service beam; and
navigation information associated with the historical service beams, the navigation information being used to determine historical position, velocity, direction of movement, and angle of the terminal.
Wherein, the network equipment still includes:
the sending module is used for sending a reporting request for requesting to report the available beam history information to the terminal.
Wherein, the sending module includes:
a first sending submodule, configured to send an inquiry request to a terminal, the inquiry requesting whether available beam history information exists;
the receiving submodule is used for receiving feedback information of available beam history information fed back by the terminal according to the query request;
and the second sending submodule is used for sending a request for reporting the available beam history information to the terminal according to the feedback information.
The available beam history information is available beam history information in a target system.
Wherein, the receiving module includes:
the first receiving submodule is used for receiving beam history information reported by the terminal through an RRC message in the process of completing establishment/recovery of a radio resource control RRC connection;
or,
the second receiving submodule is used for receiving the beam history information sent by the terminal through the RRC message in the process of reporting the terminal information or the measurement information;
or,
a third receiving submodule, configured to receive, through a predefined RRC message, beam history information sent by a terminal;
or,
the fourth receiving submodule is used for receiving the beam history information sent by the terminal through the control information of the MAC layer CE or the layer one;
or,
and the fifth receiving submodule is used for receiving the beam history information sent by the terminal in the inactive state through signaling or data packets.
It is worth pointing out that, the network device according to the embodiment of the present invention receives the beam history information reported by the terminal when the reporting condition is satisfied, the beam history information can reflect the historical movement information of the terminal, and after receiving the beam history information of the terminal, the network device can optimize the subsequent paging procedure of the terminal according to the beam history information and perform accurate mobility management on the terminal.
It should be noted that the division of the modules of the network device and the terminal is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the determining module may be a processing element separately set up, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the function of the determining module is called and executed by a processing element of the apparatus. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together 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 invention further provides a network device, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor implements the steps in the beam history information transmission method as described above when executing the computer program. An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the beam history information transmission method as described above.
Specifically, the embodiment of the invention also provides a network device. As shown in fig. 6, the network device 600 includes: antenna 61, radio frequency device 62, baseband device 63. The antenna 61 is connected to a radio frequency device 62. In the uplink direction, the rf device 62 receives information via the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes information to be transmitted and transmits the information to the radio frequency device 62, and the radio frequency device 62 processes the received information and transmits the processed information through the antenna 61.
The above-mentioned band processing means may be located in the baseband means 63, and the method performed by the network device in the above embodiment may be implemented in the baseband means 63, where the baseband means 63 includes a processor 64 and a memory 65.
The baseband device 63 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 6, wherein one chip, for example, the processor 64, is connected to the memory 65 to call up the program in the memory 65 to perform the network device operation shown in the above method embodiment.
The baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62, such as a Common Public Radio Interface (CPRI).
The processor may be a single processor or a combination of multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the methods performed by the network devices, for example: one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, or the like. The storage element may be a memory or a combination of a plurality of storage elements.
The memory 65 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double data rate SDRAM (ddr DRAM), Enhanced SDRAM (ESDRAM), SLDRAM (SLDRAM), and Direct Rambus RAM (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 invention further includes: a computer program stored in the memory 65 and executable on the processor 64, the processor 64 calling the computer program in the memory 65 to execute the method performed by each module shown in fig. 5.
In particular, the computer program when invoked by the processor 64 is operable to perform: receiving beam history information reported by a terminal when a reporting condition is met;
and paging or mobility management is carried out on the terminal according to the beam history information.
Wherein the beam history information comprises at least one of:
frequency point information of a cell global unified identifier (CGI) or a Physical Cell Identifier (PCI) of a historical cell; the history cell is a cell where a history service beam of the terminal is located;
identity information, beam identification and/or time-frequency resource information of the beam; the wave beam is a wave beam corresponding to each reference signal of the historical cell;
beam measurement information for historical service beams;
antenna panel information for historical service beams;
the terminal dwell time length and dwell start-stop time information on the historical service beam;
measuring time information and measuring position information corresponding to the beam measuring information of the historical service beam;
pseudo co-located QCL information for historical service beams;
bitmap information of a synchronization signal block corresponding to a historical service beam; and
navigation information associated with the historical service beam, the navigation information being used to determine historical position, velocity, direction of movement, and angle of the terminal.
In particular, the computer program when invoked by the processor 64 is operable to perform: and sending a reporting request for requesting to report the available beam history information to the terminal.
In particular, the computer program when invoked by the processor 64 is operable to perform: transmitting an inquiry request inquiring whether available beam history information exists to the terminal;
the receiving terminal feeds back feedback information with available beam history information according to the query request;
and sending a request for reporting the available beam history information to the terminal according to the feedback information.
The available beam history information is available beam history information in a target system.
In particular, the computer program when invoked by the processor 64 is operable to perform: receiving beam history information reported by the terminal through an RRC message in the process of completing establishment/recovery of a radio resource control RRC connection;
or,
receiving beam history information sent by a terminal through an RRC message in the process of reporting terminal information or reporting measurement information;
or,
receiving beam history information sent by a terminal through a predefined RRC message;
or,
receiving beam history information sent by a terminal through control information of an MAC layer CE or a layer one;
or,
and receiving beam history information sent by the terminal in the inactive state through signaling or data packets.
The network device may be a Base Transceiver Station (BTS) in Global System for mobile communications (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB, eNodeB) in LTE, a relay Station, an Access point, a Base Station in a future 5G network, or the like, which is not limited herein.
The network equipment in the embodiment of the invention 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 after the network equipment receives the beam history information of the terminal, the network equipment can optimize the subsequent paging process of the terminal according to the beam history information and accurately manage the mobility of the terminal.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.
Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.