Communication method and device

Abstract

The invention relates to a communication method, equipment, a computer readable storage medium, a computer program product and a computer program. The method comprises the following steps: a terminal device receives configuration information, wherein the configuration information is used for configuring the terminal device to report related information of a global navigation satellite system (GNSS).

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, device, computer-readable storage medium, computer program product, and computer program. Background Art

[0002] In related technologies, discussions have focused on enhancing the capabilities of Internet of Things (IoT) terminals, including enabling them to perform Global Navigation Satellite System (GNSS) positioning operations. However, the challenge remains determining when these terminals should report GNSS-related information to the network, allowing the network to configure appropriate measurement intervals for the terminals.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method, device, computer-readable storage medium, computer program product, and computer program.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The terminal device receives configuration information, where the configuration information is used to configure the terminal device to report global navigation satellite system (GNSS) related information.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The first network device sends configuration information, where the configuration information is used to configure the terminal device to report Global Navigation Satellite System (GNSS) related information.

[0009] An embodiment of the present application provides a terminal device, including:

[0010] The first communication unit is configured to receive configuration information, where the configuration information is used to configure the terminal device to report Global Navigation Satellite System (GNSS) related information.

[0011] An embodiment of the present application provides a first network device, including:

[0012] The second communication unit is used to send configuration information, where the configuration information is used to configure the terminal device to report global navigation satellite system GNSS related information.

[0013] An embodiment of the present application provides a terminal device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.

[0014] An embodiment of the present application provides a first network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first network device executes the above method.

[0015] The embodiment of the present application provides a chip for implementing the above method.

[0016] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0017] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0018] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0019] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0020] In the embodiment of the present application, by adopting the above solution, the terminal device can receive configuration information for configuring it to report GNSS-related information. In this way, the terminal device can configure the network side to report GNSS-related information at an appropriate time, thereby ensuring that the network side configures an appropriate measurement interval for the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a schematic diagram of a communication scenario.

[0022] FIG2 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0023] FIG3 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0024] FIG4 is an exemplary flow chart of a communication method according to the present application.

[0025] FIG5 is an exemplary flowchart of a terminal device re-reporting GNSS-related information according to an embodiment of the present application.

[0026] FIG6 is an exemplary flowchart of reporting GNSS related information when a terminal device switches from a second network device to a first network device according to an embodiment of the present application.

[0027] 7 and 8 are two exemplary flow charts of exchanging GNSS-related information between network devices when a terminal device switches from a first network device to a third network device according to an embodiment of the present application.

[0028] FIG9 is an exemplary flowchart of a terminal device reporting GNSS-related information when the terminal device switches from a first network device to a third network device according to an embodiment of the present application.

[0029] FIG10 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0030] FIG11 is a schematic block diagram of a terminal device according to another embodiment of the present application.

[0031] FIG12 is a schematic block diagram of a first network device according to an embodiment of the present application.

[0032] FIG13 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0033] FIG14 is a schematic block diagram of a chip according to an embodiment of the present application.

[0034] FIG15 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0036] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0037] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0038] In one possible implementation, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0039] In one possible implementation, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0040] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0041] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0042] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0043] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0044] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0045] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0046] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0047] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0048] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0049] In one possible implementation, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0050] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0051] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0052] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0053] Non-Terrestrial Network (NTN):

[0054] NTN generally uses satellite communications to provide communications services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts where communications equipment cannot be deployed or where there is a sparse population. However, satellite communications, because a single satellite can cover a large area and orbits the Earth, theoretically every corner of the globe can be covered. Second, satellite communications have significant social value. Satellite communications can provide low-cost coverage in remote mountainous areas and poor, underdeveloped countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting their development. Third, satellite communications offer long range, and the cost of communications does not increase significantly with increasing distance. Finally, satellite communications are highly stable and unaffected by natural disasters.

[0055] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers. Communication satellites are divided into LEO (Low-Earth Orbit) satellites, MEO (Medium-Earth Orbit) satellites, GEO (Geostationary Earth Orbit) satellites, HEO (High Elliptical Orbit) satellites, etc. according to the different orbital altitudes. The following mainly describes LEO and GEO:

[0056] LEO: Low-orbit satellites have an altitude range of 500 km to 1500 km, with an orbital period of approximately 1.5 to 2 hours. Signal propagation delay for single-hop communication between users is typically less than 20 ms. The maximum satellite visibility time is 20 minutes. Signal propagation distances are short, link loss is minimal, and the transmit power requirements for user terminals are low.

[0057] GEO: Geosynchronous Earth Orbit (GEO): Satellites orbit at an altitude of 35,786 km and orbit the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 milliseconds.

[0058] Related research has focused on two NTN architectures: transparent forwarding and regenerative forwarding. NTNs consist of the following network elements: one or more gateways, connecting satellites to the terrestrial public network; feeder links, used for communication between gateways and satellites; service links, used for communication between terminals and satellites; intersatellite links, which exist within the regenerative forwarding network architecture; and satellites, which can be categorized as either transparent forwarding or regenerative forwarding based on their functionality. Transparent forwarding only provides radio frequency filtering, frequency conversion, and amplification, transparently forwarding signals without altering the waveform of the forwarded signal. Regenerative forwarding, in addition to providing radio frequency filtering, frequency conversion, and amplification, can also provide demodulation / decoding, routing / conversion, and encoding / modulation, emulating some or all of the functions of a base station.

[0059] LTE / NR terrestrial network uplink timing advance:

[0060] A key feature of uplink transmission is orthogonal multiple access (MAL) across different UEs in time and frequency. This means that uplink transmissions from different UEs in the same cell do not interfere with each other. To ensure orthogonality in uplink transmissions and avoid intra-cell interference, the eNB / gNB requires that signals from different UEs at the same time but on different frequency resources arrive at the eNB / gNB at essentially aligned times. To ensure time synchronization on the eNB / gNB side, LTE / NR supports an uplink timing advance mechanism.

[0061] The uplink and downlink clocks on the eNB / gNB are identical, but there is an offset between the uplink and downlink clocks on the UE side, and different UEs have different uplink timing advances. By appropriately controlling the offset for each UE, the eNB / gNB can control the time it takes for uplink signals from different UEs to arrive at the eNB / gNB. UEs farther from the eNB / gNB experience greater transmission latency and therefore need to send uplink data earlier than UEs closer to the eNB / gNB.

[0062] The eNB / gNB determines the TA (Timing Advance) value for each UE based on measurements of the UE's uplink transmission. The eNB / gNB sends TA commands to the UE in two ways.

[0063] Acquisition of initial TA: During the random access process, the eNB / gNB determines the TA value by measuring the received preamble and sends it to the UE through the Timing Advance Command field of the RAR.

[0064] Adjustment of the TA in the RRC (Radio Resource Control) Connected State: Although the UE and the eNB / gNB achieve uplink synchronization during random access, the timing of the uplink signal reaching the eNB / gNB may change over time. Therefore, the UE needs to continuously update its uplink timing advance to maintain uplink synchronization. If a UE's TA needs to be corrected, the eNB / gNB sends a Timing Advance Command to the UE, requesting it to adjust its uplink timing. This Timing Advance Command is sent to the UE via the Timing Advance Command MAC (Medium Access Control) CE (Control Element).

[0065] TA maintenance in NTN

[0066] In traditional TN (Terrestrial Network) networks, UEs perform TA maintenance based on TA commands issued by the network. For Rel-17 NTN, assuming that UEs have GNSS (Global Navigation Satellite System) positioning capabilities and TA pre-compensation capabilities, UEs can estimate the service link TA based on the UE location and the location of the serving satellite. Therefore, a TA determination method combining open-loop and closed-loop is introduced in NTN. For NTN UEs in RRC_IDLE / INACTIVE and RRC_CONNECTED states, their timing advance (TA) is calculated by the following formula:

[0067] T TA =(N TA +N TA,UE-specific +N TA,common +N TA,offset )×T c

[0068] Among them, N TA For the PRACH (Physical Random Access Channel) transmission scenario, it is defined as 0 and can be updated later through the TA command in Msg2 / MsgB and the TA command MAC CE. TA,UE-specificIt is the TA of the service link estimated by the UE and used for TA pre-compensation. Specifically, the UE obtains the satellite position based on its own GNSS position information combined with the satellite ephemeris information broadcast by the serving cell, thereby calculating the propagation delay of the service link from the UE to the satellite. TA,common It is a common TA controlled by the network and contains any timing deviation that the network deems necessary. TA,offset is a fixed offset for calculating TA.

[0069] From the above formula, it can be seen that the UE in the RRC connected state needs to obtain the service link TA (i.e. N TA,UE-specific ), on the one hand, it needs to know its own GNSS position information, and on the other hand, it needs to obtain the position of the serving satellite through the serving cell satellite ephemeris information. In addition, in order to calculate the TA of the UE, the UE also needs to obtain the public TA (i.e. N TA,common ).

[0070] R17 Internet of Things (IoT) NTN GNSS Operations

[0071] In R17 IoT NTN (i.e., scenarios where NB-IoT and eMTC are connected to NTN), the GNSS measurement module and communication module of the IoT terminal cannot operate simultaneously (Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed). In R17 NTN, IoT terminals can only perform GNSS measurements to obtain location information in RRC IDLE or RRC INACTIVE states. The GNSS module cannot be activated in RRC connected state. Therefore, before entering the RRC connected state, the UE must first obtain its own GNSS position (i.e., GNSS measurement results) using the GNSS module. The UE can determine the validity period of the GNSS position based on its own circumstances (such as the UE's mobility status) and report the remaining validity period of the GNSS position to the network during RRC connection establishment / RRC re-establishment / RRC connection recovery. For a UE in the RRC connected state, when its GNSS position expires, the UE cannot perform GNSS operations in the RRC connected state and cannot calculate the time to return to the RRC IDLE state.

[0072] GNSS enhancements for R18 IoT NTN

[0073] The main research objectives of IoT NTN in Rel-18 include: IoT-NTN Performance Enhancements in Rel-18 to address remaining issues from Rel-17.

[0074] This work considers Rel-17 IoT-NTN as baseline as well as Rel-17 NR-NTN outcome and the further IoT-NTN performance enhancements objectives are listed below: Disabling of HARQ feedback to mitigate impact of HARQ stalling on UE data rates; Study and specify, if needed, improved GNSS operations for a new position fix for UE pre-compensation during long connection times and for reduced power consumption.

[0075] Based on the above research objectives, in Release 18, IoT terminals connected to NTN will be able to perform GNSS operations in the RRC connected state. In related discussions, GNSS enhancements for IoT terminals connected to NTN were discussed, and the following conclusions were reached:

[0076] 1. An IoT NTN UE may need to reacquire a valid GNSS position fix during a long RRC connection. How can a UE update or reduce the need to update the GNSS position fix during an RRC connection?

[0077] 2. For connected GNSS measurements, at least the following candidate solutions can be considered: Method 1: The UE reacquires the GNSS position fix based on timer control; Method 2: A new gap is introduced, and the UE reacquires the GNSS position fix during the gap.

[0078] 3. For the triggering of connected GNSS measurement, you can consider: UE-triggered GNSS measurement; network-triggered GNSS measurement.

[0079] As previously mentioned, IoT terminal capabilities have been enhanced during relevant discussions, enabling UEs to perform GNSS positioning operations in the RRC connected state. Accordingly, the network may need to know the UE's GNSS-related information so that it can determine how to configure appropriate measurement gaps for the UE to perform GNSS measurements. Therefore, determining when the UE reports GNSS-related information to the network so that the network can configure appropriate measurement gaps for the UE becomes a critical issue.

[0080] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0081] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0082] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0083] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0084] Figure 2 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.

[0085] S210: The terminal device receives configuration information, where the configuration information is used to configure the terminal device to report Global Navigation Satellite System (GNSS) related information.

[0086] Figure 3 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.

[0087] S310. The first network device sends configuration information, where the configuration information is used to configure the terminal device to report GNSS-related information.

[0088] Here, the terminal device may be an Internet of Things (IoT) terminal device.

[0089] The first network device may be a first access network device. The access network device may be any one of a base station, a gNB, an eNB, a satellite, and the like.

[0090] In some possible implementations, the first network device may be an access network device of a cell where the terminal device is currently located.

[0091] The first network device sending the configuration information may specifically include: the first network device sending the configuration information to the terminal device. Correspondingly, the terminal device receiving the configuration information may specifically include: the terminal device receiving the configuration information sent by the first network device.

[0092] It should be noted that, before the first network device sends the configuration information to the terminal device, the process may further include: the first network device determining whether to send the configuration information to the terminal device.

[0093] The first network device determines whether to send the configuration information to the terminal device, which may specifically include: the first network device sending the configuration information to the terminal device when the first network device supports the terminal device performing GNSS measurements in a connected state; and / or the first network device not sending the configuration information to the terminal device when the first network device does not support the terminal device performing GNSS measurements in a connected state. Whether the first network device supports the terminal device performing GNSS measurements in a connected state may be determined by the first network device based on its own capabilities, and the capabilities of the first network device itself are not exhaustively listed here.

[0094] The configuration information is carried by one of the following: system information broadcast; a first radio resource control (RRC) message; a first media access control (MAC) control element (CE); or a first physical downlink control channel (PDCCH) instruction.

[0095] Optionally, the configuration information may be included in a system information broadcast. In this case, the configuration information may be sent by the first network device to all devices served by it via a system information broadcast. The terminal device may be any one of all devices served by the first network device. The any one device served by the first network device may be a device within the coverage area of ​​the first network device.

[0096] Specifically, the configuration information may be carried by at least one of system information blocks (SIB) 1, SIB2, SIB31, etc. in the system information.

[0097] Optionally, the aforementioned configuration information may be carried in a dedicated signaling corresponding to the terminal device. Specifically, the configuration information may be carried by any one of the first RRC message, the first MAC CE, and the first PDCCH instruction.

[0098] In this case, the first network device sending the configuration information to the terminal device may specifically include: when the first network device supports the terminal device performing GNSS measurements in a connected state and the terminal device supports performing GNSS measurements in a connected state, sending the configuration information to the terminal device. Here, whether the terminal device supports performing GNSS measurements in a connected state can be reported to the network side in advance as a capability information of the terminal device; accordingly, the first network device on the network side can obtain the capability information of the terminal device in advance, and then determine whether the terminal device supports performing GNSS measurements in a connected state.

[0099] In one embodiment, the aforementioned first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reestablishment message, a first RRC connection recovery message, and a first RRC connection reconfiguration message.

[0100] The first network device sends configuration information to the terminal device, which may be at least one of the following: the first network device may carry the configuration information through a first RRC connection establishment message and send it to the terminal device during the process of establishing an RRC connection with the terminal device; the first network device may carry the configuration information through a first RRC connection reconstruction message and send it to the terminal device during the process of reestablishing the RRC connection with the terminal device; the first network device may carry the configuration information through a first RRC connection recovery message and send it to the terminal device during the process of recovering the RRC connection with the terminal device; the first network device may carry the configuration information through a first RRC connection reconfiguration message and send it to the terminal device during the process of reconfiguring the terminal device.

[0101] It should be noted that, in this embodiment, the aforementioned first RRC connection reconfiguration message is used to carry other information besides the indication information indicating the handover, that is, the first RRC connection reconfiguration message in this embodiment is not used in the handover scenario.

[0102] In one embodiment, the aforementioned first PDCCH instruction may refer to the first DCI (Downlink Control Information) transmitted on the PDCCH, that is, the configuration information may be carried by the first DCI.

[0103] The DCI format used by the first DCI can be set according to actual conditions, for example, any one of the multiple DCI formats specified in the relevant protocol can be used, which is not limited in this embodiment.

[0104] After receiving the configuration information sent by the first network device, the terminal device may further perform the following processing: the terminal device sends GNSS related information to the first network device. Accordingly, the processing performed by the first network device may include: the first network device receives the GNSS related information reported by the terminal device.

[0105] The GNSS related information includes at least one of the following: the validity period of the GNSS measurement result and the measurement period of the GNSS.

[0106] The validity period of the GNSS measurement result may refer to the remaining time during which the GNSS measurement result is valid, or the remaining validity period of the GNSS measurement result. The GNSS measurement result may refer to a GNSS position, or a GNSS positioning.

[0107] The GNSS measurement duration can be called GNSS position fix time duration for measurement

[0108] (GNSS positioning measurement duration) specifically refers to the time required for the terminal device to perform GNSS positioning (or position) measurement.

[0109] The aforementioned GNSS related information may be carried by one of the following: a third RRC message, a third MAC CE.

[0110] The third RRC message may be an uplink RRC message, and the third MAC CE may be an uplink MAC CE.

[0111] The third RRC message may include one of the following: a first RRC connection establishment complete message, a first RRC connection reestablishment complete message, a first RRC connection recovery complete message, a first RRC connection reconfiguration complete message, and a first UE assistance information (Assistance Information) message.

[0112] Exemplarily, if the configuration information is carried by the first RRC connection establishment message or the system message block when the aforementioned first network device sends the configuration information, the terminal device may use the first RRC connection establishment completion message to carry the GNSS related information. If the configuration information is carried by the first RRC connection reconstruction message or the system message block when the aforementioned first network device sends the configuration information, the terminal device may use the first RRC connection reconstruction completion message to carry the GNSS related information. If the configuration information is carried by the first RRC connection recovery message or the system message block when the aforementioned first network device sends the configuration information, the terminal device may use the first RRC connection recovery completion message to carry the GNSS related information. If the configuration information is carried by the first RRC connection reconfiguration message when the aforementioned first network device sends the configuration information, the terminal device may use the first RRC connection reconfiguration completion message to carry the GNSS related information. If the configuration information is carried by the first RRC connection reconfiguration message when the aforementioned first network device sends the configuration information, and the first RRC connection reconfiguration message contains a configuration requiring the terminal device to report auxiliary information, the terminal device may use the first UE auxiliary information message to carry the GNSS related information.

[0113] The solution provided in the above embodiment is exemplarily described with reference to FIG4 , including:

[0114] S401. A first network device sends configuration information to a terminal device.

[0115] S402. The terminal device reports GNSS-related information to the first network device.

[0116] In some possible implementations, the first network device is an access network device of a cell where the terminal device is currently located; and the first network device configures the terminal device to report GNSS-related information.

[0117] After the first network device receives the GNSS related information reported by the terminal device, the method further includes: the first network device sending a second RRC message to the terminal device; and the first network device receiving the GNSS related information sent by the terminal device.

[0118] Correspondingly, after the terminal device sends GNSS related information to the first network device, the method also includes: when the terminal device receives the second RRC message sent by the first network device, the terminal device determines whether to send GNSS related information to the first network device.

[0119] The difference from the previous embodiment is that the solution provided by this embodiment is that after the terminal device has reported GNSS related information to the first network device it is currently located, when it receives a second RRC message sent by the first network device again, the terminal device needs to decide whether to send GNSS related information to the first network device again.

[0120] The aforementioned second RRC message may not carry configuration information. The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection recovery message, or a third RRC connection reconfiguration message. It should be noted that the aforementioned third RRC connection reconfiguration message is used to carry information other than the indication information indicating the handover, that is, the third RRC connection reconfiguration message is not used in handover scenarios.

[0121] Exemplarily, the first network device sends a second RRC message to the terminal device, which may be at least one of the following: the first network device may send a second RRC connection reconstruction message to the terminal device during the process of re-establishing an RRC connection with the terminal device; the first network device may send a second RRC connection recovery message to the terminal device during the process of performing RRC connection recovery with the terminal device; the first network device may send a third RRC connection reconfiguration message to the terminal device during the process of performing RRC reconfiguration on the terminal device. This embodiment does not limit the specific content that may be carried by the aforementioned second RRC connection reconstruction message, second RRC connection recovery message, and third RRC connection reconfiguration message.

[0122] The terminal device determines whether to send GNSS-related information to the first network device, including:

[0123] If the terminal device sends the GNSS related information within the second preset time period before receiving the second RRC message, the terminal device determines to send the GNSS related information to the first network device; or, if the terminal device does not send the GNSS related information within the second preset time period before receiving the second RRC message, the terminal device determines not to send the GNSS related information to the first network device.

[0124] Specifically, the terminal device determines whether to send the GNSS related information to the first network device, which may include:

[0125] When the terminal device receives the second RRC message, it determines whether GNSS related information has been sent to the first network device again within a second preset time period before the moment of receiving the second RRC message; if it has been sent, it determines to send the GNSS related information to the first network device again; otherwise, it determines not to send the GNSS related information to the first network device again.

[0126] Furthermore, when the aforementioned terminal device determines to send GNSS related information to the first network device, the terminal device sends GNSS related information to the first network device.

[0127] The specific value of the aforementioned second preset time length can be set according to actual conditions, for example, it can be 0.5 seconds, 1 second, 2 seconds, or longer or shorter, and they are not exhaustively listed here.

[0128] The GNSS related information can also be carried by any one of the third RRC message and the third MAC CE, which will not be described in detail.

[0129] The content contained in the GNSS-related information sent by the terminal device to the first network device at different times or at different times may be of the same type as the content contained in the GNSS-related information in the aforementioned embodiment, but the specific values ​​may be the same or different. For example, the GNSS-related information sent by the terminal device to the first network device for the first time may include at least one of the first valid duration of the GNSS measurement result and the first measurement duration of the GNSS; the GNSS-related information sent by the terminal device to the first network device for the second time may include at least one of the second valid duration of the GNSS measurement result and the second measurement duration of the GNSS; and the first valid duration and the second valid duration may be the same or different, and the first measurement duration and the second measurement duration may be the same or different.

[0130] The solution provided in the above embodiment is exemplarily described with reference to FIG5 , including:

[0131] S501. A first network device sends configuration information to a terminal device.

[0132] S502. The terminal device reports GNSS-related information to the first network device.

[0133] S503. The first network device sends a second RRC message to the terminal device;

[0134] S504: The terminal device determines whether to send GNSS related information to the first network device again. If so, execute S505; otherwise, end the process.

[0135] S505: The terminal device reports GNSS related information to the first network device again.

[0136] The above embodiments all illustrate the processing of the terminal device within the coverage of the first network device. In actual scenarios, the terminal device will also switch between different network devices. The following describes the processing of the terminal device reporting GNSS-related information during the switching process:

[0137] In some possible implementations, the terminal device is switched from the second network device to the aforementioned first network device; and the aforementioned second network device has not configured the terminal device to report GNSS-related information.

[0138] The second network device may be a source access network device of the terminal device; the first network device may be a target access network device of the terminal device.

[0139] In this embodiment, the configuration information is carried by the first RRC connection reconfiguration message, and the first RRC connection reconfiguration message includes first indication information; wherein, the first indication information is used to instruct the terminal device to switch from the second network device to the first network device. If the first network device requires the terminal device to report GNSS-related information, the following processing can be performed: the first network device sends the configuration information to the terminal device through the second network device. Accordingly, the aforementioned terminal device receives the configuration information, which can be specifically: the terminal device receives the configuration information sent by the first network device through the second network device.

[0140] Among them, the first indication information is the synchronous reconfiguration (reconfigurationWithSync) information in the first RRC connection reconfiguration message; it should be understood that in some possible examples, the synchronous reconfiguration information can also be called a synchronous reconfiguration field.

[0141] It should be noted that when the first RRC connection reconfiguration message carries the first indication information, the aforementioned configuration information and the first indication information may occupy different fields in the first RRC connection reconfiguration message; or, the aforementioned configuration information may be the content of the first indication information.

[0142] In this embodiment, after receiving the configuration information sent by the first network device, the terminal device may further perform the following processing: the terminal device sends GNSS related information to the first network device. Accordingly, the processing performed by the first network device may include: the first network device receives the GNSS related information reported by the terminal device.

[0143] Here, the GNSS related information is carried by the third RRC message, specifically, the GNSS related information can be carried by the first RRC connection reconfiguration complete message. The GNSS related information includes the same content as in the above embodiment and is not described in detail.

[0144] The solution provided in this embodiment is exemplarily described with reference to FIG6 :

[0145] S601. The terminal device reports a measurement report to the second network device.

[0146] The measurement report may include at least one of the following: an identifier of the candidate network device and a signal strength of the candidate network device. The signal strength of the candidate network device may include an RSRP (Reference Signal Receiving Power) measurement result and / or an RSRQ (Reference Signal Receiving Quality) measurement result.

[0147] S602: The second network device determines the first network device as the target network device of the terminal device based on the measurement report; the second network device sends a handover request message to the first network device.

[0148] The second network device determining the first network device as the target network device for the terminal device based on the measurement report may mean that the second network device selects the first network device with the highest signal strength from the measurement report as the target network device for the current handover. It should be understood that this is merely an example and does not limit the implementation method for selecting the target network device during the handover process.

[0149] S603: The first network device receives a switching request message sent by the second network device, and the first network device sends a response message to the second network device, where the response message carries configuration information.

[0150] Specifically, when the first network device receives the switching request message sent by the second network device, it determines whether the terminal device needs to report GNSS-related information; if necessary, the first network device sends a response message to the second network device, and the response message carries configuration information, and the response message is also used to confirm that the terminal device is allowed to access.

[0151] The aforementioned first network device determining whether the terminal device needs to report GNSS-related information may include: the first network device determining that the terminal device needs to report GNSS-related information when the first network device supports the terminal device performing GNSS measurements in a connected state and the terminal device supports performing GNSS measurements in a connected state. The specific processing method for the first network device's determination is the same as that in the aforementioned embodiment and is not further described.

[0152] It should also be noted that the aforementioned first network device receiving the handover request message from the second network device may be: the first network device receiving the handover request message via an Xn interface between the first network device and the second network device. The aforementioned first network device sending response information to the second network device may be: the first network device sending response information via an Xn interface between the first network device and the second network device, and the response information may be a handover request confirmation message.

[0153] Alternatively, the first network device receiving the handover request message sent by the second network device may be: the first network device receiving the handover request message sent by the second network device via the S1 interface between the first network device and the core network device. The aforementioned first network device sending response information to the second network device may be: the first network device sending response information to the core network device via the S1 interface between the first network device and the core network device; and the core network device sending response information to the second network device via the S1 interface between the first network device and the core network device.

[0154] The sending of the response information by the first network device to the core network device via the S1 interface between the first network device and the core network device may be: the first network device sends a handover request confirmation message to the core network device via the S1 interface between the first network device and the core network device. The sending of the response information by the core network device to the second network device via the S1 interface between the first network device and the core network device may be: the core network device sends a handover command to the second network device via the S1 interface between the first network device and the core network device.

[0155] S604. The second network device sends a first RRC connection reconfiguration message to the terminal device, where the first RRC connection reconfiguration message carries the configuration information.

[0156] Specifically, when the second network device receives the response information, it can add the configuration information carried in the response information to the first RRC connection reconfiguration message, and add the first indication information to the first RRC connection reconfiguration message; then the second network device sends the first RRC connection reconfiguration message to the terminal device.

[0157] S605. The terminal device reports GNSS-related information to the first network device.

[0158] In some possible implementations, the terminal device is currently in a switching process from a first network device to a third network device. In addition, the first network device has configured the terminal device to report GNSS-related information.

[0159] After the first network device receives the GNSS related information reported by the terminal device, the method further includes:

[0160] The first network device sends a handover request message of the terminal device to the third network device; the handover request message carries the GNSS related information;

[0161] Upon receiving the response information sent by the third network device, the first network device sends second indication information to the terminal device; wherein the second indication information is used to instruct the terminal device to switch from the first network device to the third network device. The second indication information is carried by a second RRC connection reconfiguration message. The second indication information is synchronization reconfiguration information in the second RRC connection reconfiguration message.

[0162] That is to say, when the first network device has locally obtained the GNSS related information reported by the terminal device, during the switching process of the terminal device from the first network device to the third network device, the first network device, as the source network device, will send the GNSS related information reported by the terminal device to the third network device through a switching request message, so that the target network device, i.e., the third network device, can efficiently obtain the GNSS related information of the terminal device. Furthermore, the third network device can also control the GNSS measurement of the terminal device based on the GNSS related information of the terminal device. For example, the third network device can allocate a corresponding measurement gap (interval) to the terminal device based on the GNSS measurement duration contained in the GNSS related information of the terminal device, so that the terminal device performs GNSS measurement based on the measurement gap, etc. It should be understood that this is only an exemplary explanation, and the specific processing of the GNSS measurement of the terminal device by the third network device based on the GNSS related information of the terminal device can be the same as the content specified in the relevant protocol, and is not exhaustive here.

[0163] In one possible example, the aforementioned first network device sending a handover request message for the terminal device to the third network device may refer to: the first network device sending the handover request message for the terminal device to the third network device via an Xn interface. Correspondingly, the first network device receiving response information sent by the third network device may specifically refer to: the first network device receiving response information sent by the third network device via the Xn interface. The response information may be used to confirm that the terminal device is allowed to access; the response message may specifically be a handover request confirmation message.

[0164] Taking FIG. 7 as an example for exemplary description, the first network device sending the handover request message of the terminal device to the third network device may include:

[0165] S701: A first network device receives a measurement report reported by a terminal device;

[0166] After the first network device receives the measurement report reported by the terminal device, it can also select a third network device as the target network device for this switching based on the measurement report.

[0167] Among them, the selection of the third network device as the target network device for this switching based on the measurement report may refer to selecting the third network device with the largest signal strength from the measurement report as the target network device for this switching. The measurement report may include at least one of the following: the identifier of the candidate network device, the signal strength of the candidate network device. The signal strength of the candidate network device may include: RSRP (Reference Signal Receiving Power) measurement results and / or RSRQ (Reference Signal Receiving Quality) measurement results. It should be understood that this is only an exemplary description and is not intended to limit the implementation method of selecting the target network device during the switching process.

[0168] S702: The first network device sends a handover request message to the third network device, where the handover request message carries the GNSS-related information.

[0169] When the first network device receives the response information sent by the third network device, the specific process of the first network device sending the second indication information to the terminal device is still described with reference to FIG. 7 , including:

[0170] S703. The first network device receives a handover request confirmation message sent by the third network device.

[0171] S704. The first network device sends a second RRC connection reconfiguration message to the terminal device, where the second RRC connection reconfiguration message carries second indication information, and the second indication information is used to instruct the terminal device to switch from the first network device to the third network device.

[0172] In another possible example, the aforementioned first network device sending a handover request message for the terminal device to the third network device may refer to: the S1 interface between the first network device and the core network device sending a handover request; the core network device sending a handover request message via the S1 interface between the first network device and the third network device. Accordingly, the first network device receiving response information sent by the third network device may specifically refer to: the third network device sending a response information via the S1 interface between the third network device and the core network device; the core network device sending a response information via the S1 interface between the core network device and the first network device; wherein the response information may be used to confirm that the terminal device is allowed to access.

[0173] The third network device sending the response information via the S1 interface between the third network device and the core network device may refer to: the third network device sending the handover request confirmation message via the S1 interface between the third network device and the core network device. The core network device sending the response information via the S1 interface between the core network device and the first network device may refer to: the core network device sending the handover command via the S1 interface between the core network device and the first network device.

[0174] Taking FIG. 8 as an example for illustrative description, the first network device sending the handover request message of the terminal device to the third network device may include:

[0175] S801: A first network device receives a measurement report reported by a terminal device;

[0176] S802. The first network device sends a handover request message to the core network device; the handover request message carries the GNSS related information;

[0177] S803. The core network device sends a handover request message to the third network device; the handover request message carries the GNSS related information;

[0178] When the first network device receives the response information sent by the third network device, the specific process of the first network device sending the second indication information to the terminal device is still described with reference to FIG. 7 , including:

[0179] S804. The third network device sends a handover request confirmation message to the core network device;

[0180] S805. The core network device sends a handover command to the first network device.

[0181] S806: The first network device sends a second RRC connection reconfiguration message to the terminal device, wherein the second RRC connection reconfiguration message carries second indication information, and the second indication information is used to instruct the terminal device to switch from the first network device to the third network device.

[0182] Furthermore, although not illustrated in Figures 7 and 8, after receiving the aforementioned second RRC connection reconfiguration message, the terminal device can send a second RRC connection reconfiguration completion message to the third network device. The second RRC connection reconfiguration completion message can be used to indicate that the terminal device has connected to the third network device, which means that the terminal device has switched successfully.

[0183] In some possible implementations, a terminal device is currently in the process of switching from a first network device to a third network device. Specifically, the first network device is the source access network device of the terminal device, and the third network device is the target access network device of the terminal device. Furthermore, the first network device requires the terminal device to have reported GNSS-related information. Furthermore, the terminal device can determine whether to send GNSS-related information to the third network device.

[0184] After the terminal device sends GNSS related information to the first network device, the method also includes: when the terminal device receives second indication information sent by a third network device through the first network device, the terminal device determines whether to send GNSS related information to the third network device; wherein the second indication information is used to instruct the terminal device to switch from the first network device to the third network device.

[0185] The second indication information is carried by a second RRC connection reconfiguration message; the second RRC connection reconfiguration message is used to determine whether the third network device configures the terminal device to report GNSS related information. The second indication information is synchronization reconfiguration information in the second RRC connection reconfiguration message.

[0186] The aforementioned second RRC connection reconfiguration message may carry second indication information and configuration information. The second indication information and configuration information may be carried by different fields in the second RRC connection reconfiguration message, or the second indication information may include configuration information, all of which are within the protection scope of this embodiment.

[0187] The way in which the third network device decides whether to configure the terminal device to report GNSS related information can be: when the third network device itself supports the terminal device to perform GNSS measurements in the connected state and the terminal device supports performing GNSS measurements in the connected state, the third network device determines to configure the terminal device to report GNSS related information; when the third network device itself does not support the terminal device to perform GNSS measurements in the connected state and / or the terminal device does not support performing GNSS measurements in the connected state, the third network device determines not to configure the terminal device to report GNSS related information.

[0188] The terminal device determines whether to send the GNSS related information to the third network device, which may specifically include: the terminal device determines that the third network device configures the terminal device to report GNSS related information based on the second RRC connection reconfiguration message, and sends the GNSS related information within a first preset time length before receiving the second RRC connection reconfiguration message, and determines to send the GNSS related information to the third network device.

[0189] Alternatively, the method may further include one of the following: the terminal device determines, based on the second RRC connection reconfiguration message, that the third network device configures the terminal device to report GNSS related information, and when the GNSS related information is not sent within a first preset time length before receiving the second RRC connection reconfiguration message, determining not to send the GNSS related information to the third network device;

[0190] When the terminal device determines, based on the second RRC connection reconfiguration message, that the third network device has not configured the terminal device to report GNSS related information, the terminal device determines not to send the GNSS related information to the third network device.

[0191] That is, during the handover process of the terminal device from the first network device to the third network device and within the first preset time period before receiving the second indication information, if the terminal device sends GNSS-related information to the first network device, it is very likely that the third network device will not obtain the GNSS-related information sent by the first network device. By adopting this embodiment, it is ensured that when the third network device configures the terminal device to report GNSS-related information, the third network device can obtain the latest GNSS-related information of the terminal device, thereby ensuring that the third network device controls the GNSS measurement of the terminal device based on the latest GNSS-related information.

[0192] Among them, sending the GNSS related information within the first preset time period before receiving the second RRC connection reconfiguration message may mean that the terminal device connection reconfiguration message sends GNSS related information to the first network device within the first preset time period before the moment of receiving the second indication information.

[0193] The aforementioned first preset duration can be expressed as T. The specific value of the first preset duration can be set according to actual conditions, for example, it can be 1 second, 2 seconds, or longer or shorter, which is not exhaustively listed here.

[0194] The manner in which the aforementioned terminal device determines whether the third network device has configured the terminal device to report GNSS-related information based on the second RRC connection reconfiguration message may include: when the second RRC connection reconfiguration message carries second indication information, the terminal device determines whether the second RRC connection reconfiguration message carries configuration information, and if so, determines that the third network device has configured the terminal device to report GNSS-related information; if not, determines whether the second RRC connection reconfiguration message is an incremental configuration, and if so, determines that the third network device has configured the terminal device to report GNSS-related information. In addition, it also includes: when the second RRC connection reconfiguration message does not carry configuration information and the second RRC connection reconfiguration message is not an incremental configuration, determining that the third network device has not configured the terminal device to report GNSS-related information.

[0195] Among them, if it is an incremental configuration, determining that the third network device configures the terminal device to report GNSS related information may include: if it is an incremental configuration, judging whether the first network device configures the terminal device to report GNSS related information; if so, determining that the third network device configures the terminal device to report GNSS related information.

[0196] Whether the second RRC connection reconfiguration message is an incremental configuration may be determined based on whether the second RRC connection reconfiguration message indicates a full configuration. Exemplarily, the full configuration indication may be included in second indication information in the second RRC connection reconfiguration message. For example, if the second indication information indicates "full configuration," it indicates that the current configuration is full; if the second indication information does not indicate "full configuration," it indicates that the current configuration is incremental.

[0197] There is another possible example, in which the terminal device determines whether to send GNSS related information to the third network device, including: when the terminal device determines based on the second RRC connection reconfiguration message that the third network device configures the terminal device to report GNSS related information, the terminal device determines to send the GNSS related information to the third network device; or, when the terminal device determines based on the second RRC connection reconfiguration message that the third network device does not configure the terminal device to report GNSS related information, the terminal device determines not to send the GNSS related information to the third network device. That is, when the terminal device receives the switching command (i.e., the second indication information carried by the second RRC connection reconfiguration message), if the terminal device determines that the third network device configures it to report GNSS related information, it sends GNSS related information to the third network device. In this example, the way in which the terminal device determines whether the third network device configures it to report GNSS related information is the same as that in the aforementioned embodiment, and will not be repeated.

[0198] In the above embodiment, the content included in the GNSS related information sent by the terminal device to the third network device is the same as the content type included in the GNSS related information sent by the terminal device to the first network device in the aforementioned embodiment, but the specific values ​​may be the same or different.

[0199] The GNSS-related information sent by the aforementioned terminal device to the third network device may be carried by a second RRC connection reconfiguration completion message, and the second RRC connection reconfiguration completion message is also used to confirm that the handover is completed.

[0200] It should be noted that the aforementioned first network device and the third network device can be switched through the Xn interface or the S1 interface. The relevant description of the switching process of the Xn interface and the S1 interface is the same as that of the aforementioned embodiment, so it will not be repeated.

[0201] 9 , an exemplary description is given by taking the switching of the Xn interface performed by the first network device and the third network device as an example, specifically including:

[0202] S901: A first network device receives a measurement report reported by a terminal device;

[0203] S902: The first network device sends a handover request message to the third network device, where the handover request message carries the GNSS-related information.

[0204] S903. The first network device receives a handover request confirmation message sent by the third network device.

[0205] S904. The first network device sends a second RRC connection reconfiguration message to the terminal device, where the second RRC connection reconfiguration message carries second indication information, and the second indication information is used to instruct the terminal device to switch from the first network device to the third network device.

[0206] S905. The terminal device determines whether to send GNSS-related information to the third network device. If so, execute S906; otherwise, the terminal device sends a second RRC connection reconfiguration completion message to the third network device and accesses the third network device to perform subsequent processing. This part is not shown in Figure 9 for simplicity.

[0207] Here, the manner in which the terminal device determines whether to send GNSS-related information to the third network device is the same as that in the aforementioned embodiment and will not be repeated.

[0208] S906. The terminal device sends a second RRC connection reconfiguration completion message to the third network device, where the second RRC connection reconfiguration completion message carries GNSS-related information.

[0209] It can be seen that by adopting the above solution, the terminal device can receive the configuration information for configuring it to report GNSS related information. In this way, the terminal device can configure the network side to report GNSS related information at the appropriate time, thereby ensuring that the network side configures the appropriate measurement interval for the terminal device.

[0210] FIG10 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, including:

[0211] The first communication unit 1001 is configured to receive configuration information, where the configuration information is used to configure the terminal device to report Global Navigation Satellite System (GNSS) related information.

[0212] The first communication unit is configured to receive the configuration information sent by the first network device.

[0213] The configuration information is carried by one of the following: system information broadcast; a first radio resource control RRC message; a first medium access control MAC control element CE; a first physical downlink control channel PDCCH instruction.

[0214] The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reconstruction message, a first RRC connection recovery message, and a first RRC connection reconfiguration message.

[0215] The configuration information is carried by the first RRC connection reconfiguration message, and the first RRC connection reconfiguration message includes first indication information; wherein the first indication information is used to instruct the terminal device to switch from the second network device to the first network device;

[0216] The first communication unit is configured to receive the configuration information sent by the first network device through the second network device.

[0217] The first indication information is synchronization reconfiguration information in the first RRC connection reconfiguration message.

[0218] The first communication unit is configured to send GNSS related information to the first network device.

[0219] Based on FIG10 , as shown in FIG11 , the terminal device further includes:

[0220] A first processing unit 1002 is configured to determine whether to send GNSS-related information to the third network device when the first communication unit receives second indication information sent by the third network device through the first network device; wherein the second indication information is used to instruct the terminal device to switch from the first network device to the third network device;

[0221] The first communication unit 1001 is configured to receive, through the first network device, second indication information sent by a third network device.

[0222] The second indication information is carried by a second RRC connection reconfiguration message.

[0223] The first processing unit is used to determine that the third network device configures the terminal device to report GNSS related information based on the second RRC connection reconfiguration message, and sends the GNSS related information within a first preset time period before receiving the second RRC connection reconfiguration message, and determine to send the GNSS related information to the third network device.

[0224] The first processing unit is configured to determine whether to send GNSS-related information to the first network device when a second RRC message sent by the first network device is received through the second communication unit; the second communication unit is configured to receive the second RRC message sent by the first network device.

[0225] The first processing unit is configured to determine, when the GNSS related information is sent within a second preset time period before receiving the second RRC message, to send the GNSS related information to the first network device; or, when the GNSS related information is not sent within a second preset time period before receiving the second RRC message, to determine not to send the GNSS related information to the first network device.

[0226] The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection recovery message, and a third RRC connection reconfiguration message.

[0227] The GNSS related information is carried by one of the following: a third RRC message, a third MAC CE.

[0228] The GNSS related information includes at least one of the following: the validity period of the GNSS measurement result and the measurement period of the GNSS.

[0229] The terminal device is an Internet of Things (IoT) terminal device.

[0230] The terminal device of the embodiment of the present application is capable of implementing the corresponding functions of the access network device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the access network device can be found in the corresponding descriptions in the aforementioned method embodiments, and will not be repeated here. The functions described in the various modules (sub-modules, units or components, etc.) in the access network device of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).

[0231] FIG12 is a schematic diagram of the composition structure of a first network device according to an embodiment of the present application, including:

[0232] The second communication unit 1201 is configured to send configuration information, where the configuration information is used to configure the terminal device to report Global Navigation Satellite System (GNSS) related information.

[0233] The second communication unit is used to send the configuration information to the terminal device.

[0234] The configuration information is carried by at least one of the following: a system broadcast message; a first radio resource control RRC message; a first medium access control MAC control element CE; a first physical downlink control channel PDCCH instruction.

[0235] The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reconstruction message, a first RRC connection recovery message, and a first RRC connection reconfiguration message.

[0236] The configuration information is carried by the first indication information in the first RRC connection reconfiguration message; wherein, the first indication information is used to instruct the terminal device to switch from the second network device to the first network device.

[0237] The first indication information is synchronization reconfiguration information in the first RRC connection reconfiguration message.

[0238] The second communication unit is used to receive GNSS related information reported by the terminal device.

[0239] The GNSS related information is carried by one of the following: a third RRC message, a third MAC CE.

[0240] The second communication unit is used to send a switching request message of the terminal device to the third network device; the switching request message carries the GNSS related information; and when a response message sent by the third network device is received, a second indication message is sent to the terminal device; wherein the second indication message is used to instruct the terminal device to switch from the first network device to the third network device.

[0241] The second indication information is carried by a second RRC connection reconfiguration message; the second RRC connection reconfiguration message is used to determine whether the third network device configures the terminal device to report GNSS-related information connection reconfiguration message connection reconfiguration message connection reconfiguration message.

[0242] The second communication unit is used to send a second RRC message to the terminal device; and receive GNSS related information sent by the terminal device.

[0243] The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection recovery message, and a third RRC connection reconfiguration message.

[0244] The GNSS related information includes at least one of the following: the validity period of the GNSS measurement result and the measurement period of the GNSS.

[0245] The terminal device is an Internet of Things (IoT) terminal device.

[0246] The first network device of the embodiment of the present application can implement the corresponding functions of the first network device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first network device can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the first network device may also include a second processing unit, which may perform decision-making and other processing, but is not shown in Figure 12. The functions described with respect to the various modules (sub-modules, units or components, etc.) in the first network device of the application embodiment may be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).

[0247] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 includes a processor 1310, which can call and run a computer program from a memory to enable the communication device 1900 to implement the method in the embodiment of the present application.

[0248] In a possible implementation, the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0249] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0250] In one possible implementation, the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, the transceiver 1330 may send information or data to other devices, or receive information or data sent by other devices.

[0251] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0252] In one possible implementation, the communication device 1300 may be a terminal device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0253] In one possible implementation, the communication device 1300 may be the first network device of the embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the first network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0254] 14 is a schematic structural diagram of a chip 1400 according to an embodiment of the present application. The chip 1400 includes a processor 1410, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0255] In one possible implementation, the chip 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to implement the method executed by the terminal device or the first network device in the embodiment of the present application.

[0256] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0257] In a possible implementation, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0258] In a possible implementation, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0259] In one possible implementation, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0260] In one possible implementation, the chip can be applied to the first network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0261] The chips used in the terminal device and the first network device may be the same chip or different chips.

[0262] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0263] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0264] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0265] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0266] FIG15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. The communication system 1500 includes a terminal device 1510 and a first network device 1520 .

[0267] The terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the first network device 1520 can be used to implement the corresponding functions implemented by the first network device in the above method. For the sake of brevity, they will not be described in detail here.

[0268] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0269] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0270] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0271] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: A terminal device receives configuration information for configuring the terminal device to report Global Navigation Satellite System (GNSS) related information.

2. The method according to claim 1, wherein The configuration information is carried by one of the following: System information broadcast; A first Radio Resource Control (RRC) message; A first Medium Access Control (MAC) control element (CE); A first Physical Downlink Control Channel (PDCCH) command.

3. The method according to claim 2, wherein The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reestablishment message, a first RRC connection resume message, a first RRC connection reconfiguration message.

4. The method according to claim 2 or 3, wherein The terminal device receiving the configuration information includes: The terminal device receives the configuration information sent by a first network device.

5. The method according to claim 3, wherein The configuration information is carried by the first RRC connection reconfiguration message, and the first RRC connection reconfiguration message includes first indication information; wherein, the first indication information is used to indicate that the terminal device switches from a second network device to the first network device. The terminal device receiving the configuration information includes: the terminal device receives the configuration information sent by the first network device through the second network device.

6. The method according to claim 5, wherein The first indication information is synchronization reconfiguration information in the first RRC connection reconfiguration message.

7. The method according to any one of claims 4-6, wherein The method further includes: The terminal device sends GNSS related information to the first network device.

8. The method according to claim 7, wherein After the terminal device sends GNSS related information to the first network device, the method further includes: When the terminal device receives second indication information sent by a third network device through the first network device, the terminal device determines whether to send GNSS related information to the third network device; wherein, the second indication information is used to indicate that the terminal device switches from the first network device to the third network device.

9. The method according to claim 8, wherein The second indication information is carried by a second RRC connection reconfiguration message.

10. The method according to claim 9, wherein, The terminal device determining whether to send GNSS related information to the third network device includes: When the terminal device determines based on the second RRC connection reconfiguration message that the third network device configures the terminal device to report GNSS related information, and the GNSS related information is sent within a first preset duration before receiving the second RRC connection reconfiguration message, the terminal device determines to send the GNSS related information to the third network device.

11. The method according to claim 7, wherein, After the terminal device sends GNSS related information to the first network device, the method further includes: When the terminal device receives a second RRC message sent by the first network device, the terminal device determines whether to send GNSS related information to the first network device.

12. The method according to claim 11, wherein, The terminal device determining whether to send GNSS related information to the first network device includes: When the GNSS related information is sent within a second preset duration before the terminal device receives the second RRC message, the terminal device determines to send the GNSS related information to the first network device. Alternatively, in the case that the terminal device does not send the GNSS-related information within a second preset duration before receiving the second RRC message, it is determined not to send the GNSS-related information to the first network device.

13. The method according to claim 11 or 12, wherein, The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection resume message, and a third RRC connection reconfiguration message.

14. The method according to any one of claims 7-13, wherein, The GNSS-related information is carried by one of the following: a third RRC message, a third MAC CE.

15. The method according to any one of claims 1 - 14, wherein, The GNSS-related information includes at least one of the following: the valid duration of GNSS measurement results, the measurement duration of GNSS.

16. The method according to any one of claims 1-15, wherein, The terminal device is an Internet of Things (IoT) terminal device.

17. A communication method, comprising: A first network device sends configuration information for configuring a terminal device to report global navigation satellite system (GNSS)-related information.

18. The method according to claim 17, wherein, The configuration information is carried by at least one of the following: A system broadcast message; A first radio resource control (RRC) message; A first medium access control (MAC) control element (CE); A first physical downlink control channel (PDCCH) command.

19. The method according to claim 18, wherein, The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reestablishment message, a first RRC connection resume message, and a first RRC connection reconfiguration message.

20. The method according to claim 18 or 19, wherein The first network device sending the configuration information includes: The first network device sends the configuration information to the terminal device.

21. The method according to claim 19, wherein, The configuration information is carried by first indication information in the first RRC connection reconfiguration message; wherein the first indication information is used to indicate that the terminal device switches from a second network device to the first network device.

22. The method according to claim 21, wherein, The first indication information is synchronization reconfiguration information in the first RRC connection reconfiguration message.

23. The method according to any one of claims 20-22, wherein, The method further includes: The first network device receives the GNSS-related information reported by the terminal device.

24. The method according to claim 23, wherein, The GNSS-related information is carried by one of the following: a third RRC message, a third MAC CE.

25. The method according to claim 23 or 24, wherein After the first network device receives the GNSS-related information reported by the terminal device, the method further includes: The first network device sends a handover request message of the terminal device to a third network device; the handover request message carries the GNSS-related information; In the case that the first network device receives response information sent by the third network device, the first network device sends second indication information to the terminal device; wherein the second indication information is used to indicate that the terminal device switches from the first network device to the third network device.

26. The method according to claim 25, wherein, The second indication information is carried by a second RRC connection reconfiguration message; the second RRC connection reconfiguration message is used to determine whether the third network device configures the terminal device to report GNSS-related information.

27. The method according to claim 23 or 24, wherein After the first network device receives the GNSS-related information reported by the terminal device, the method further includes: The first network device sends a second RRC message to the terminal device; The first network device receives the GNSS-related information sent by the terminal device.

28. The method according to claim 27, wherein, The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection resume message, and a third RRC connection reconfiguration message.

29. The method according to any one of claims 17-28, wherein, The GNSS-related information includes at least one of the following: the effective duration of GNSS measurement results and the measurement duration of GNSS.

30. The method according to any one of claims 17-29, wherein, The terminal device is an Internet of Things (IoT) terminal device.

31. A terminal device, comprising: A first communication unit, configured to receive configuration information for configuring the terminal device to report global navigation satellite system (GNSS)-related information.

32. The terminal device according to claim 31, wherein, The configuration information is carried by one of the following: System information broadcast; A first radio resource control (RRC) message; A first medium access control (MAC) control element (CE); A first physical downlink control channel (PDCCH) command.

33. The terminal device according to claim 32, wherein, The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reestablishment message, a first RRC connection resume message, and a first RRC connection reconfiguration message.

34. The terminal device according to claim 32 or 33, wherein, The first communication unit is configured to receive the configuration information sent by a first network device.

35. The terminal device according to claim 33, wherein, The configuration information is carried by the first RRC connection reconfiguration message, and the first RRC connection reconfiguration message includes first indication information; wherein the first indication information is used to indicate that the terminal device switches from a second network device to the first network device. The first communication unit is configured to receive the configuration information sent by the first network device through the second network device.

36. The terminal device according to claim 35, wherein, The first indication information is synchronization reconfiguration information in the first RRC connection reconfiguration message.

37. The terminal device according to any one of claims 34 to 36, wherein, The first communication unit is configured to send GNSS-related information to the first network device.

38. The terminal device according to claim 37, wherein, The terminal device further includes: A first processing unit, configured to determine whether to send GNSS-related information to a third network device when the first communication unit receives second indication information sent by the third network device through the first network device; wherein the second indication information is used to indicate that the terminal device switches from the first network device to the third network device. The first communication unit is configured to receive the second indication information sent by the third network device through the first network device.

39. The terminal device according to claim 38, wherein, The second indication information is carried by a second RRC connection reconfiguration message.

40. The terminal device according to claim 39, wherein, The first processing unit, in the connection reconfiguration message, is configured to determine to send the GNSS-related information to the third network device when it is determined, based on the second RRC connection reconfiguration message, that the third network device configures the terminal device to report GNSS-related information and the GNSS-related information is sent within a first preset duration before the second RRC connection reconfiguration message is received.

41. The terminal device according to claim 37, wherein, The terminal device further includes: A first processing unit, configured to determine whether to send GNSS-related information to the first network device when a second RRC message sent by the first network device is received through a second communication unit. The second communication unit is configured to receive the second RRC message sent by the first network device.

42. The terminal device according to claim 41, wherein, The first processing unit is configured to determine to send the GNSS-related information to the first network device when the GNSS-related information is sent within a second preset duration before receiving the second RRC message; or, determine not to send the GNSS-related information to the first network device when the GNSS-related information is not sent within a second preset duration before receiving the second RRC message.

43. The terminal device according to claim 41 or 42, wherein, The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection resume message, and a third RRC connection reconfiguration message.

44. The terminal device according to any one of claims 37-43, wherein, The GNSS-related information is carried by one of the following: a third RRC message, a third MAC CE.

45. The terminal device according to any one of claims 31-44, wherein, The GNSS-related information includes at least one of the following: the valid duration of GNSS measurement results, the measurement duration of GNSS.

46. The terminal device according to any one of claims 31-45, wherein, The terminal device is an Internet of Things (IoT) terminal device.

47. A first network device, comprising: A second communication unit, configured to send configuration information for configuring a terminal device to report global navigation satellite system (GNSS)-related information.

48. The first network device according to claim 47, wherein, The configuration information is carried by at least one of the following: a system broadcast message; a first radio resource control (RRC) message; a first medium access control (MAC) control element (CE); a first physical downlink control channel (PDCCH) command.

49. The first network device according to claim 48, wherein, The first RRC message includes one of the following: a first RRC connection establishment message, a first RRC connection reestablishment message, a first RRC connection resume message, a first RRC connection reconfiguration message.

50. The first network device according to claim 48 or 49, wherein, The second communication unit is configured to send the configuration information to the terminal device.

51. The first network device according to claim 49, wherein, The configuration information is carried by a first indication information in the first RRC connection reconfiguration message; wherein, the first indication information is used to indicate that the terminal device switches from a second network device to the first network device.

52. The first network device according to claim 51, wherein, The first indication information is synchronous reconfiguration information in the first RRC connection reconfiguration message.

53. The first network device according to any one of claims 50 - 52, wherein, The second communication unit is configured to receive the GNSS-related information reported by the terminal device.

54. The first network device according to claim 53, wherein, The GNSS-related information is carried by one of the following: a third RRC message, a third MAC CE.

55. The first network device according to claim 53 or 54, wherein, The second communication unit is configured to send a handover request message of the terminal device to a third network device; the handover request message carries the GNSS-related information; when receiving response information sent by the third network device, send second indication information to the terminal device; wherein, the second indication information is used to indicate that the terminal device switches from the first network device to the third network device.

56. The first network device according to claim 55, wherein, The second indication information is carried by a second RRC connection reconfiguration message; the second RRC connection reconfiguration message is used to determine whether the third network device configures the terminal device to report GNSS-related information.

57. The first network device according to claim 53 or 54, wherein, The second communication unit is configured to send a second RRC message to the terminal device; receive the GNSS-related information sent by the terminal device.

58. The first network device according to claim 57, wherein, The second RRC message is one of the following: a second RRC connection reestablishment message, a second RRC connection resume message, and a third RRC connection reconfiguration message.

59. The first network device according to any one of claims 47 - 58, wherein, The GNSS-related information includes at least one of the following: the effective duration of GNSS measurement results and the measurement duration of GNSS.

60. The first network device according to any one of claims 47-59, wherein, The terminal device is an Internet of Things (IoT) terminal device.

61. A terminal device, comprising: A processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the method according to any one of claims 1 to 16.

62. A first network device, comprising: A processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first network device executes the method according to any one of claims 17 to 30.

63. A chip, comprising: A processor, which is used to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 1 to 16.

64. A chip, comprising: A processor, which is used to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 17 to 30.

65. A computer-readable storage medium for storing a computer program, which when run by a device causes the device to execute the method according to any one of claims 1 to 16 or claims 17 to 30.

66. A computer program product including computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 16 or claims 17 to 30.

67. A computer program, which causes a computer to execute the method according to any one of claims 1 to 16 or claims 17 to 30.

Images