Communication method and communication device

Abstract

To solve the resource waste problem in the prior art, a communication method and apparatus are provided. In this application, the method includes a step in which a UE receives pre-configuration information. When a pre-configuration condition is met, the UE stops requesting uplink resources, and the uplink resources are used to transmit first information. When the first information is an activation request, the first information is used to activate the pre-configuration information. When the first information is a deactivation request, the first information is used to deactivate the pre-configuration information.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202210948679.1, entitled "COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on August 9, 2022, which is incorporated herein by reference in its entirety.

[0002] The present application relates to the field of communications technology, and more particularly to communications methods and devices. [Background technology]

[0003] A next generation radio access network (NG-RAN) usually sends pre-configuration information to user equipment (UE). When the UE needs to use the pre-configuration information to perform the corresponding function, the UE needs to first send an activation request to the NG-RAN. After obtaining an activation instruction from the NG-RAN, the UE activates the pre-configuration information based on the activation instruction. The activation request is carried in a medium access control element (MAC CE).

[0004] In the process of a UE transmitting a MAC CE to the NG-RAN, the UE determines whether a physical uplink shared channel (PUSCH) resource currently exists for transmitting the MAC CE. If a PUSCH resource does not exist for transmitting the MAC CE, the UE triggers a scheduling request (SR) to request a PUSCH resource. Before obtaining the requested PUSCH resource, the UE cannot cancel the SR, i.e., the SR remains in a pending state. In this case, a problem of resource waste occurs. Summary of the Invention

[0005] The present application provides a communication method and apparatus for solving the problem of resource wastage. [Means for solving the problem]

[0006] According to a first aspect, the present application provides a communication method. The method can be performed by a communication device. The communication device can be a terminal device (i.e., UE) or a module, such as a chip, within the terminal device.

[0007] The method includes a step of a UE receiving pre-configuration information, wherein the UE stops requesting uplink resources when a pre-configuration condition is met, and the uplink resources are used to transmit first information, and when the first information is an activation request, the first information is used to activate the pre-configuration information; or when the first information is a deactivation request, the first information is used to deactivate the pre-configuration information.

[0008] In the above technical solution, when it determines that the preset condition is met, the UE may stop requesting uplink resources, that is, the UE does not need to continuously request uplink resources until the requested uplink resources are obtained. In this way, the resources occupied by the UE in the process of requesting uplink resources are reduced, which helps solve the problem of resource waste.

[0009] In one possible implementation, the pre-configuration information is configuration information of a measurement gap (MG) pre-configured for positioning. In this way, the UE may request activation of the configuration information of the MG pre-configured for positioning, so that the UE may perform positioning measurements based on the configuration information of the MG activated for positioning.

[0010] In one possible implementation, the UE triggers an SR when there are no PUSCH resources to be used for transmitting the first information, and the SR is used to request a PUSCH resource. In one possible implementation, the UE triggers a random access channel (RACH) when there are no physical uplink control channel (PUCCH) resources to be used for transmitting the SR, and the RACH is used to request an uplink resource (also called an uplink grant resource). In this way, the UE triggers an SR and a RACH in order to request a PUSCH resource to be used for transmitting the first information (i.e., an activation request or a deactivation request).

[0011] In one possible implementation, the UE stopping the request for uplink resources when the preset condition is met includes the UE canceling the first information and stopping the request for uplink resources when the preset condition is met; When the first information is an activation request, the pre-configuration conditions include one or more of the following: measurements should be stopped; new pre-configuration information is received; other pre-configuration information is activated and the other pre-configuration information meets the measurement requirements; second information is received and the second information is used to modify the pre-configuration information; and pre-configuration information is already activated and the measurements include at least one or more of positioning measurements and radio resource management (RRM) measurements; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; and the pre-configured information has already been deactivated.

[0012] In one possible implementation, the UE includes a radio resource control (RRC) layer and a medium access control (MAC) layer.

[0013] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the RRC layer indicates to the MAC layer to stop measurement; the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; the MAC layer activates other pre-configuration information; the RRC layer receives second information and the RRC layer sends a cancel indication to the MAC layer, the cancel indication is used to cancel the activation request; and the MAC layer has already activated the pre-configuration information; and / or When the first information is a deactivation request, the preconfigured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request, and the MAC layer has already deactivated the preconfigured information.

[0014] In the above technical solution, a preset condition is provided for the UE to cancel the first information (i.e., an activation request or a deactivation request). When the preset condition is met, the UE may cancel the first information. In this way, the UE does not need to transmit the first information, i.e., does not need to transmit the SR triggered by the first information, and no longer needs to transmit the RACH triggered by the SR. This helps reduce resource waste.

[0015] In one possible implementation, the UE stopping the request for uplink resources when the preset condition is met includes the UE canceling an SR triggered by the first information when the preset condition is met, the SR being used to request a PUSCH resource, and the PUSCH resource being used to transmit the first information.

[0016] and / or when the first information is an activation request, the pre-configuration conditions include one or more of the following: an activation request has already been sent; the activation request is canceled; measurements should be stopped, and the measurements include at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify pre-configuration information; pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: a deactivation request has already been sent; second information is received and the second information is used to modify the pre-configured information; the deactivation request is canceled; and the pre-configured information has already been deactivated.

[0017] In one possible implementation, the UE includes an RRC layer and a MAC layer.

[0018] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the MAC layer has already sent an activation request; the MAC layer cancels the activation request; the RRC layer indicates to the MAC layer to stop measuring; the RRC layer receives the second information, and the RRC layer sends a cancellation indication to the MAC layer, and the cancellation indication is used to cancel the activation request; the MAC layer has already activated pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: the MAC layer has already sent a deactivation request; the RRC layer receives the second information, the RRC layer sends a cancel instruction to the MAC layer, and the cancel instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; and the MAC layer has already deactivated the pre-configured information.

[0019] The above technical solution provides a preset condition for the UE to cancel the SR. When the preset condition is met, the UE may cancel the SR, which helps to reduce resource waste.

[0020] In one possible implementation, the UE has already sent an activation request includes the UE determining, after performing packet assembly of the activation request, that the UE has already sent an activation request, and / or the UE has already sent a deactivation request includes the UE determining, after performing packet assembly of the deactivation request, that the UE has already sent a deactivation request. In the above technical solution, a determination condition is provided for the UE to determine that the first information (i.e., the activation request or the deactivation request) has been successfully transmitted. When the determination condition is met, the UE determines that the first information has already been successfully transmitted, and further determines that the UE can cancel the SR.

[0021] In one possible implementation, the UE stopping the request for uplink resources when the pre-configured condition is met includes the UE canceling the RACH triggered by the SR when the pre-configured condition is met, and the RACH being used to request the uplink resources.

[0022] When the first information is an activation request, the pre-configured conditions include one or more of the following: the activation request is canceled; the SR triggered by the activation request is canceled; measurements should be stopped, the measurements including at least one or more of positioning measurements and RRM measurements; second information is received, the second information is used to modify the pre-configuration information; the pre-configuration information has already been activated; and new pre-configuration information is received; and / or when the first information is a deactivation request, the pre-configured conditions include one or more of the following: second information is received, the second information is used to modify the pre-configuration information; the deactivation request is canceled; the SR triggered by the deactivation request is canceled; and the pre-configuration information has already been deactivated.

[0023] In one possible implementation, the UE includes an RRC layer and a MAC layer.

[0024] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the MAC layer cancels the activation request; the MAC layer cancels the SR triggered by the activation request; the RRC layer indicates the MAC layer to stop measuring; the RRC layer receives the second information and sends a cancellation indication to the MAC layer, where the cancellation indication is used to cancel the activation request; the MAC layer has already activated the pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; the MAC layer cancels the SR triggered by the deactivation request; and the MAC layer has already deactivated the pre-configured information.

[0025] The above technical solution provides a preset condition for the UE to cancel the RACH. When the preset condition is met, the UE may cancel the RACH, which helps to reduce resource waste.

[0026] In one possible implementation, the first information is a MAC CE.

[0027] According to a second aspect, an embodiment of the present application provides a communication device, the device having a function of implementing a UE in the first aspect or any one of the possible implementation forms of the first aspect. The device may be a UE or a chip included in the UE.

[0028] The functions of the communication device described above may be implemented by hardware or by hardware executing corresponding software, where the hardware or software includes one or more modules, units, or means corresponding to the functions described above.

[0029] In one possible implementation, the structure of the device includes a processing module and a transceiver module. The processing module is configured to support the device in performing corresponding functions of the UE in any one of the first aspect or implementations of the first aspect. The transceiver module is configured to support communication between the device and another communication device. For example, when the device is a UE, the device may receive pre-configuration information. The communication device may further include a storage module. The storage module is coupled to the processing module and stores program instructions and data required for the device. In one example, the processing module may be a processor, the communication module may be a transceiver, and the storage module may be a memory. The memory may be integrated with the processor or located separately from the processor.

[0030] In another possible implementation, the structure of the device may include a processor and further include a memory. The processor may be coupled to the memory and configured to execute computer program instructions stored in the memory, such that the device performs the method of the first aspect or any one of the possible implementations of the first aspect. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface. When the device is a network device or a UE, the communication interface may be a transceiver or an input / output interface. When the device is a chip included in a network device or a UE, the communication interface may be an input / output interface of the chip. Optionally, the transceiver may be a transceiver circuit, and the input / output interface may be an input / output circuit.

[0031] According to a third aspect, an embodiment of the present application provides a chip system including a processor. The processor is coupled to a memory, and the memory is configured to store a program or instruction. When the program or instruction is executed by the processor, the chip system is enabled to perform the method of the first aspect or any one of the possible implementation forms of the first aspect.

[0032] Optionally, the chip system further includes an interface circuit, the interface circuit configured to exchange code instructions with the processor.

[0033] Optionally, the chip system may have one or more processors, which may be implemented using hardware or software. When the processor is implemented using hardware, the processor may be a logic circuit, an integrated circuit, or the like. When the processor is implemented using software, the processor may be a general-purpose processor and is implemented by reading software code stored in a memory.

[0034] Optionally, there may be one or more memories in the chip system. The memory may be integrated with the processor or may be located separately from the processor. For example, the memory may be a non-transitory processor, such as a read-only memory (ROM). The memory and the processor may be integrated on the same chip or may be located on different chips.

[0035] According to a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program or instructions, which, when executed, enables a computer to perform the method of the first aspect or any one of the possible implementations of the first aspect.

[0036] According to a fifth aspect, an embodiment of the present application provides a computer program product, which, when read and executed by a computer, enables the computer to perform the method of the first aspect or any one of the possible implementation forms of the first aspect.

[0037] For technical effects that can be achieved in any one of the second to fifth aspects, please refer to the description of the beneficial effects in the first aspect, and details will not be described again in this specification. [Brief explanation of the drawings]

[0038] [Figure 1] 1 is a diagram of the architecture of a communication system according to the present application; [Figure 2] 1 is a schematic flowchart of pre-configuration and activation of a positioning MG according to the present application; [Figure 3] 1 is a diagram of the format of a MAC CE according to the present application. [Figure 4] 1 is a schematic flow chart of a communication method according to the present application; [Figure 5] FIG. 1 is a diagram of MAC CE cancellation according to the present application. [Figure 6] FIG. 1 is a diagram of SR cancellation according to the present application. [Figure 7] FIG. 1 is a diagram of RACH cancellation according to the present application. [Figure 8] 1 is a diagram of the structure of a communication device according to the present application; [Figure 9] FIG. 2 is a diagram of the structure of another communication device according to the present application. DETAILED DESCRIPTION OF THE INVENTION

[0039] Before the present application is described, some terms or techniques in the embodiments of the present application will first be briefly explained and described in order to facilitate the understanding of those skilled in the art.

[0040] I. User Equipment (UE) A terminal may also be referred to as user equipment (UE), a mobile station, a mobile terminal, a terminal device, etc. Terminals may be widely used in various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals may be mobile phones, tablet computers, computers with wireless transceiver capabilities, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The specific technology and device configuration used by the terminal are not limited in the embodiments of the present application.

[0041] II. Core Network The core network includes network devices that process and forward signaling and user data, such as access management devices, session management devices, user plane gateways, and location management devices.

[0042] A user plane gateway may be a server with functions specific to user plane data, such as mobility management, routing, and forwarding. A user plane gateway, such as a serving gateway (SGW), packet data network gateway (PGW), or user plane function (UPF) entity, is generally located on the network side.

[0043] The access management device is primarily responsible for authorization, and the access management device is, for example, an access management function (AMF) device.

[0044] The session management device is primarily responsible for session management, and is, for example, a session management function (SMF).

[0045] The location management device has a positioning function and is mainly responsible for supporting various types of UE-related location services, including UE positioning, forwarding assistance data to the UE, etc. For example, the location management device may include a location management function (LMF) or a location management component (LMC), or may be a local location management function (LLMF) in a network device. For ease of description, the following embodiments are described using an example in which the location management device is an LMF.

[0046] III. Next Generation Radio Access Network (NG-RAN) The NG-RAN may include next generation evolutional Node B (ng-eNB) and next generation Node B (gNB).

[0047] Specifically, the ng-eNB is a device deployed in a radio access network, conforming to 4G standards, and providing wireless communication functions to UEs. For example, the eNB may include a macro base station, a micro base station (also called a small cell), a relay station, an access point, a wearable device, and an in-vehicle device in various forms. Alternatively, the eNB may be a transmission and reception point (TRP).

[0048] Specifically, a gNB is a device deployed in a radio access network, conforming to 5G standards, and providing wireless communication functions to UEs. For example, a gNB may include a macro base station, a micro base station (also called a small cell), a relay station, an access point, a wearable device, and an in-vehicle device in various forms. Alternatively, a gNB may be a transmission and reception point (TRP) or a transmission measurement function (TMF). A gNB may include a central unit (CU) and distributed units (DUs) integrated into the gNB.

[0049] IV. Scheduling Request In new radio (NR) technologies, when a UE determines that a medium access control (MAC) layer trigger condition is met, it may send an SR to the NG-RAN to request the NG-RAN to schedule resources.

[0050] The MAC layer trigger conditions may include one or more of the following (1) to (5):

[0051] (1) There is no PUSCH transmission opportunity for a triggered buffer status report (BSR) or pre-emptive BSR.

[0052] (2) Triggered Timing Advance Reporting (TA reporting) The MAC CE has no PUSCH transmission opportunity and timing advance SR is enabled.

[0053] (3) The triggered listen before talk failure recovery MAC CE (LBT failure recovery MAC CE) does not have a PUSCH transmission opportunity.

[0054] (4) The triggered pre-configured MG MAC CE does not have a PUSCH transmission opportunity. The pre-configured MG MAC CE may be a pre-configured MG activation MAC CE or a pre-configured MG deactivation MAC CE.

[0055] (5) There is no PUSCH transmission opportunity for triggered beam failure recovery (BFR) for secondary cell (SCell) MAC CE and enhanced BFR MAC CE.

[0056] In the present application, "there is no PUSCH transmission opportunity" means, for example, that there is no PUSCH resource for PUSCH transmission, or that no PUSCH resource exists for PUSCH transmission.

[0057] Furthermore, after the UE triggers an SR, the SR remains in a "pending" state until the UE cancels the SR. When an SR is in a pending state, the UE continuously transmits the SR in a pending state to the NG-RAN. If a PUCCH resource exists to transmit the SR, the UE transmits the SR on the PUCCH resource. If a PUCCH resource does not exist to transmit the SR, the UE applies an uplink resource through a random access process.

[0058] The UE may cancel the SR in any one of the following cases:

[0059] Case 1: For SRs triggered by a BSR, the UE cancels all SRs when the following conditions are met: the UE has already sent a BSR and the BSR contains the latest buffer status information; or the UE may send all data in the buffer based on the uplink resources.

[0060] Case 2: For an SR triggered by a pre-emptive BSR, after successfully transmitting the pre-emptive BSR, the UE cancels the SR triggered by the pre-emptive BSR.

[0061] Case 3: For a BFR MAC CE, after successfully transmitting the BFR MAC CE, the UE cancels the SR triggered by the BFR MAC CE.

[0062] Case 4: For an LBT failure recovery MAC CE, after sending the LBT failure recovery MAC CE or canceling all LBT failures, the UE cancels the SR triggered by the LBT failure recovery MAC CE.

[0063] Additionally, for SR, if the UE does not obtain a PUCCH resource used to transmit the SR, the UE may obtain an uplink resource by transmitting a random access channel (RACH), where it will be understood that the RACH is triggered by the SR.

[0064] The UE may cancel the RACH triggered by the SR in any one of the following cases:

[0065] Case a: For a RACH triggered by a BSR, the UE cancels the RACH when it determines that the following conditions are met: the UE acquires a BSR in a non-RACH manner, and the BSR may indicate all data that has arrived since the previous BSR was sent; or the uplink resources can accommodate all uplink data.

[0066] Case b: For a RACH triggered by an SL-BSR, the UE cancels the RACH when it determines that the following conditions are met: the UE obtains a BSR in a non-RACH manner, and the BSR may indicate all data that has arrived since the previous BSR was sent; or the direct link grant resource can accommodate all direct link data.

[0067] Case c: For a RACH triggered by BFR for SCell, the UE cancels the RACH when it determines that the following conditions are met: the UE is already transmitting the BFR for SCell MAC CE using another uplink resource; or the UE determines that the SCell indicated by the BFR for SCell MAC CE is already deactivated.

[0068] Case d: For a RACH triggered by LBT failure recovery, the UE cancels the RACH when it determines that the following conditions are met: the UE sends an LBT failure recovery MAC CE using another uplink resource; or all SCells triggered by the UE for LBT failure recovery have already been deactivated.

[0069] V. Other In the embodiments of the present application, the terms "system" and "network" may be used interchangeably.

[0070] The term "plurality" means two or more.

[0071] The term "and / or" describes a relational relationship for describing related objects and indicates that three relations may exist. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists.

[0072] Additionally, the character " / " generally represents an "or" relationship between related objects.

[0073] "At least one of the following" or similar expressions means any combination of these items, including any combination of one item or more items. For example, at least one of a, b, or c can represent a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be singular or plural.

[0074] Additionally, unless otherwise stated, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish between multiple objects, but are not intended to limit the order, chronology, priority, or importance of the multiple objects. For example, a first message and a second message are used only to distinguish between different messages, and are not used to represent different priorities, transmission orders, or importance of the two types of messages.

[0075] Figure 1 is a diagram of the architecture of a communication system. The network elements / modules related to the communication system mainly include three parts: NG-RAN, UE, and core network.

[0076] The core network includes LMF, AMF, service location protocol (SLP), evolved serving mobile location center (E-SMLC), etc.

[0077] The LMF is connected to the AMF via the NL interface. For example, the AMF may receive a location service request related to the UE from the 5th generation core network location services (5GC LCS), or the AMF may initiate some location services on behalf of a specific UE and forward the location service request to the LMF. After obtaining the location information returned by the UE, the LMF returns the related location information to the 5GC LCS.

[0078] The NG-RAN may include a gNB, an ng-eNB, etc. The gNB is connected to the ng-eNB via an Xn interface, and the AMF is connected to the ng-eNB via an NG-C interface, or the AMF is connected to the gNB via the NG-C interface.

[0079] To support positioning, one or more network devices (e.g., gNB or ng-eNB) on the NG-RAN side configure resources for the UE to be used to transmit reference signals, measure uplink signals such as reference signals from the UE, and feed back measurement results to the LMF. The reference signals may specifically be positioning reference signals (PRS). The positioning reference signals are, for example, sounding reference signals (SRS) or preambles.

[0080] It should be understood that Fig. 1 is merely an example of a communication system to which the embodiments of the present application can be applied for the purpose of explanation, and does not specifically limit the types, number, connection methods, etc. of network elements included in a communication system to which the present application can be applied. In addition, the network elements / modules shown with dashed lines in Fig. 1 are optional. For example, the E-SMLC or SLP is optional.

[0081] 2 is a schematic flowchart of pre-configuration and activation of measurement gaps (MG) for positioning according to the present application. The NG-RAN is specifically a gNB.

[0082] Step 201: The LMF obtains from the gNB the positioning capabilities supported by the gNB.

[0083] Step 202: The LMF sends a first NRPPa message to the gNB. In response, the gNB receives the first NRPPa message from the LMF. The gNB is specifically a serving gNB. The first NRPPa message is used by the LMF to request PRS configuration information of neighboring cell gNBs of the gNB from the gNB and to request the gNB to pre-configure a positioning MG for the UE. The first NRPPa message is, for example, an NRPPa measurement pre-configuration required message.

[0084] Step 203: The gNB uses an RRC configuration request message to send configuration information of the pre-configured MG for positioning to the UE. In response, the UE receives an RRC configuration request message from the gNB, where the RRC configuration request message includes the configuration information of the MG for positioning.

[0085] Step 204: After completing the pre-configuration based on the configuration information of the MG for positioning, the UE sends an RRC configuration complete message to the gNB. In response, the gNB receives an RRC configuration complete message from the UE.

[0086] Step 205: The gNB sends a second NRPPa message to the LMF. In response, the LMF receives a second NRPPa message from the gNB. The second NRPPa message indicates to the LMF that the MG configuration information for positioning has been pre-configured. The second NRPPa message is, for example, an NRPPa measurement reconfiguration confirm message.

[0087] Step 206: The gNB receives a message used to activate the configuration information of the MG for positioning.

[0088] Step 206 may specifically include step 206-a and step 206-b.

[0089] Step 206-a: The LMF sends a third NRPPa message to the gNB, and in response, the gNB receives a third NRPPa message from the LMF. The third NRPPa message is used by the LMF to request the gNB to activate the configuration information of the MG pre-configured for positioning in the UE. The third NRPPa message is, for example, an NRPPa measurement activation message.

[0090] Step 206-b: The UE sends a MAC CE activation request to the gNB, and in response, the gNB receives a MAC CE activation request from the UE. The MAC CE activation request is used to request activation of configuration information of an MG preconfigured for positioning in the UE. The MAC CE activation request is, for example, an uplink MAC CE positioning measurement MG activation request.

[0091] Step 207: The gNB sends a MAC CE activation indication to the UE, and in response, the UE receives a MAC CE activation indication from the gNB. The MAC CE activation indication instructs the UE to activate configuration information of a MG preconfigured for positioning in the UE. The MAC CE activation indication is, for example, a downlink MAC CE positioning measurement MG activation indication.

[0092] It should be understood that the aforementioned step 206 and step 207 may alternatively be a process of deactivating the configuration information of the MG for positioning activated in the UE.

[0093] In response to this, in step 206-a, the LMF sends a fourth NRPPa message to the gNB, which is used by the LMF to request the gNB to deactivate the configuration information of the MG pre-configured for positioning in the UE. The fourth NRPPa message is, for example, an NRPPa measurement inactivation message.

[0094] In step 206-b, the UE sends a MAC CE deactivation request to the gNB, where the MAC CE deactivation request is, for example, an uplink MAC CE positioning measurement gap inactivation request.

[0095] In step 207, the gNB sends a MAC CE deactivation instruction to the UE, where the MAC CE deactivation instruction instructs the UE to deactivate the configuration information of the MG pre-configured for positioning in the UE. The MAC CE deactivation instruction is, for example, a downlink MAC CE positioning measurement MG deactivation instruction (DL MAC CE positioning measurement gap inactivation).

[0096] For ease of explanation, in this embodiment of the present application, the MAC CE positioning request and the MAC CE deactivation request are collectively referred to as MAC CE. For the format of MAC CE, please refer to Figure 3. Specifically, MAC CE occupies one byte (oct), and the last four bits in the byte include a positioning MG identifier (i.e., positioning MG ID) that indicates which MG for positioning the MAC CE is used to activate / deactivate. The first three bits of the byte are reserved bits, and the fourth bit is A / D.

[0097] In the aforementioned step 206-b, the process of the UE transmitting the MAC CE to the gNB may specifically be that the MAC layer of the UE triggers the MAC CE after receiving an instruction from a higher layer (e.g., the RRC layer). Furthermore, when the UE determines that the MAC CE is in a triggered state, the UE determines whether a PUSCH resource currently exists for transmitting the MAC CE. If the UE determines that a PUSCH resource currently exists for transmitting the MAC CE, the UE triggers an SR to request a PUSCH resource. In this case, the UE cannot cancel the SR before obtaining the requested PUSCH resource using the SR, i.e., the SR remains in a pending state, and a resource occupancy problem exists.

[0098] Furthermore, the UE determines whether there are currently any PUCCH resources available for transmitting the SR. If it determines that there are no PUCCH resources available for transmitting the SR, the UE further triggers a RACH to request uplink resources (including PUSCH resources and / or PUCCH resources). In this case, before the UE can obtain the requested uplink resources using the RACH, the UE needs to continuously transmit the RACH until the number of transmissions reaches the maximum number of RACH transmissions, which also creates a resource occupancy problem.

[0099] To solve the aforementioned problems, the present application provides a communication method for stopping / canceling an SR in time and / or stopping / canceling an RACH in time to reduce unnecessary resource occupation.

[0100] Please refer to the description of the schematic flow chart of an example of a communication method shown in FIG.

[0101] Step 401: The UE receives pre-configuration information.

[0102] Optionally, the pre-configuration information is configuration information of a MG pre-configured for positioning. Optionally, the UE receives an RRC message, where the RRC message is specifically an RRC configuration request message, and the RRC configuration request message includes configuration information of a MG pre-configured for positioning. Correspondingly, the UE receives the RRC configuration request message and performs pre-configuration based on the configuration information of the MG pre-configured for positioning in the RRC configuration request message.

[0103] In addition, the pre-configuration information may alternatively be other configuration information than the configuration information of the MG pre-configured for positioning.

[0104] Specifically, the UE receives pre-configuration information from the NG-RAN.

[0105] In one possible manner, when the UE needs to activate the pre-configuration information (e.g., when positioning measurement needs to be performed), the UE sends an activation request to the NG-RAN. In response, after receiving the activation request, the NG-RAN sends an activation instruction to the UE. After receiving the activation instruction from the NG-RAN, the UE activates the pre-configuration information.

[0106] For example, the UE determines whether a PUSCH resource used to transmit the activation request exists. If it determines that a PUSCH resource used to transmit the activation request exists, the UE transmits the activation request using the PUSCH resource. If it determines that a PUSCH resource used to transmit the activation request does not exist, the UE triggers an SR, which is used by the UE to request a PUSCH resource. Furthermore, the UE determines whether a PUCCH resource used to transmit the SR exists. If it determines that a PUCCH resource used to transmit the SR exists, the UE transmits the SR using the PUCCH resource. If it determines that a PUCCH resource used to transmit the SR does not exist, the UE triggers a RACH, which is used by the UE to request uplink resources (PUCCH resources and / or PUSCH resources).

[0107] In another possible scheme, the UE has already activated the pre-configured information. When the UE needs to deactivate the activated pre-configured information, the UE sends a deactivation request to the NG-RAN. After receiving the deactivation request, the NG-RAN sends a deactivation instruction to the UE. After receiving the deactivation instruction from the NG-RAN, the UE deactivates the pre-configured information.

[0108] For example, the UE determines whether a PUSCH resource used to transmit the deactivation request exists. If it determines that a PUSCH resource used to transmit the deactivation request exists, the UE transmits the deactivation request using the PUSCH resource. If it determines that a PUSCH resource used to transmit the deactivation request does not exist, the UE triggers an SR, which is used by the UE to request a PUSCH resource. Furthermore, the UE determines whether a PUCCH resource used to transmit the SR exists. If it determines that a PUCCH resource used to transmit the SR exists, the UE transmits the SR using the PUCCH resource. If it determines that a PUCCH resource used to transmit the SR does not exist, the UE triggers a RACH, which is used by the UE to request uplink resources (PUCCH resources and / or PUSCH resources).

[0109] In the present application, an activation request and a deactivation request may be collectively referred to as first information. In other words, the first information may be an activation request or a deactivation request. Furthermore, an SR triggered when a UE is to transmit the first information (it may also be understood that an SR is triggered by the first information) may also be referred to as a resource request. Similarly, an RACH triggered when a UE is to transmit an SR (it may also be understood that an RACH is triggered by the SR) may also be referred to as a resource request. It will be understood that a resource request is used to request an uplink resource, and the uplink resource may be used to transmit the first information. When the first information is an activation request, the first information is used to activate the pre-configured information. When the first information is a deactivation request, the first information is used to deactivate the pre-configured information.

[0110] Step 402: The UE stops requesting uplink resources (or stops transmitting resource requests) when a preset condition is met.

[0111] There may be three specific implementations in which the UE stops requesting uplink resources.

[0112] Implementation form 1: The UE cancels the first information.

[0113] For example, after canceling the first information, the UE may no longer request a PUSCH resource, i.e., it does not need to transmit the SR triggered by the first information. Furthermore, when the SR further triggers the RACH, the UE does not need to request a PUCCH resource used to transmit the SR, so the UE does not need to transmit the RACH triggered by the SR.

[0114] Implementation 2: The UE cancels the SR triggered by the first information.

[0115] For example, when the UE cancels the SR triggered by the first information, the UE may no longer request the PUCCH resource used to transmit the SR, i.e., the UE does not need to transmit the RACH triggered by the SR.

[0116] Implementation 3: The UE cancels the RACH triggered by the SR.

[0117] In the following, implementation forms 1 to 3 will be described with reference to the conditions corresponding to implementation forms 1 to 3.

[0118] In implementation form 1, upon determining that condition 1 is met, the UE cancels the first information, i.e., stops requesting uplink resources.

[0119] Optionally, when the first information is an activation request, Condition 1 may include at least one or more of the following Condition 1-1 to Condition 1-6.

[0120] The UE determining that condition 1 is satisfied may specifically mean that the UE determines that any one of conditions 1-1 to 1-6 is satisfied.

[0121] Condition 1-1: The UE has already activated the pre-configuration information.

[0122] It will be appreciated that when the UE has already activated the pre-configuration information in another manner, the UE may no longer need to send an activation request, i.e., the UE cancels the activation request.

[0123] For example, in the process in which the UE requests activation of the pre-configuration information 1, an SR is triggered or a RACH is further triggered. Furthermore, if the UE determines that the pre-configuration information 1 has already been activated, the UE cancels the activation request used to activate the pre-configuration information 1.

[0124] In a specific implementation, after the pre-configuration information has already been activated, the MAC layer of the UE no longer needs to send an activation request, i.e., the MAC layer of the UE cancels the activation request. Further referring to the above example, after determining that the pre-configuration information 1 has already been activated, the MAC layer of the UE no longer needs to request activation of the pre-configuration information 1, i.e., the MAC layer of the UE cancels the activation request used to activate the pre-configuration information 1.

[0125] Condition 1-2: The UE receives new pre-configuration information.

[0126] It will be appreciated that when the UE receives the new pre-configuration information, it may be considered that the pre-configuration information has already been changed, i.e., the UE no longer needs to request activation of the pre-configuration information. Optionally, the UE may further request that the new pre-configuration information be activated.

[0127] For example, the UE requests activation of pre-configuration information 1. When the UE receives new pre-configuration information 2, the UE no longer needs to request activation of pre-configuration information 1. Optionally, the UE may further request activation of pre-configuration information 2.

[0128] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer receives an RRC message, where the RRC message includes new pre-configuration information, and then the RRC layer sends the new pre-configuration information to the MAC layer. For the MAC layer, the MAC layer determines that the pre-configuration information has already been changed and no longer needs to request activation of the original pre-configuration information.

[0129] Further referring to the above example, the RRC layer receives an RRC message, where the RRC message includes pre-configuration information 2. The RRC layer sends pre-configuration information 2 to the MAC layer. In response to this, for the MAC layer, the MAC layer determines that the pre-configuration information has already changed and no longer needs to request activation of pre-configuration information 1. Optionally, the MAC layer further requests activation of pre-configuration information 2.

[0130] Condition 1-3: The UE activates other pre-configured information.

[0131] It should be understood that the UE may receive multiple pieces of pre-configuration information. When the UE activates other pieces of pre-configuration information in the multiple pieces of pre-configuration information and the other pieces of pre-configuration information can meet the requirements of the UE, the UE no longer needs to activate the pre-configuration information that currently needs to be activated.

[0132] For example, the UE receives multiple pieces of pre-configuration information (e.g., pre-configuration information and pre-configuration information b) from the NG-RAN, and the UE triggers an SR when it requests activation of pre-configuration information a. Furthermore, if the UE determines that pre-configuration information b has already been activated and that pre-configuration information b can also meet the UE's requirements, the UE no longer needs to request activation of pre-configuration information a.

[0133] In a specific implementation, a UE includes an RRC layer and a MAC layer. The RRC layer acquires multiple pieces of pre-configuration information using one or more RRC messages. When the MAC layer requests activation of one of the multiple pieces of pre-configuration information, the MAC layer triggers an SR because there is no PUSCH used to transmit the activation request for the pre-configuration information. Furthermore, if the MAC layer determines that another piece of the multiple pieces of pre-configuration information has already been activated, the MAC layer may cancel the transmission of the activation request for the pre-configuration information.

[0134] Further referring to the above example, the RRC layer receives an RRC message, where the RRC message includes pre-configuration information a and pre-configuration information b. The RRC layer sends the pre-configuration information a and pre-configuration information b to the MAC layer. The MAC layer triggers an SR when it requests activation of pre-configuration information a. Furthermore, if the MAC layer determines that pre-configuration information b has already been activated and that pre-configuration information b can also meet the requirements of the UE, the MAC layer no longer needs to request activation of pre-configuration information a.

[0135] Optionally, the plurality of pieces of pre-configured information are a plurality of pieces of configuration information of a MG pre-configured for positioning. Furthermore, the requirement that the other pre-configured information meets may specifically be a measurement requirement. Correspondingly, the UE or the MAC layer of the UE may perform measurements based on the other pre-configured information that has already been activated. The measurements include at least one or more of positioning measurements and RRM measurements.

[0136] Condition 1-4: The UE receives the second information, and the second information is used to modify the pre-configuration information.

[0137] It will be appreciated that upon receiving the second information (sometimes referred to as reconfiguration information), the UE needs to modify the configuration parameters in the pre-configuration information based on the second information. In this way, the UE no longer needs to request activation of the pre-configuration information before modification. Optionally, the UE may further request activation of the modified pre-configuration information. Optionally, the second information includes modification parameters, which indicate to the UE to modify the pre-configuration information.

[0138] For example, the UE receives pre-configuration information 1 and then requests activation of pre-configuration information 1. Upon receiving second information, the UE modifies the configuration parameters in pre-configuration information 1 based on the second information. In this way, the UE no longer needs to request activation of pre-configuration information 1 before the modification. Optionally, the UE may further request activation of the modified pre-configuration information 1.

[0139] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message. The RRC layer sends the second information to the MAC layer to indicate to the MAC layer to modify the pre-configured configuration information based on the second information. In this manner, the MAC layer no longer needs to request activation of the pre-configured information before modification. In this specification, the RRC message may also be referred to as an RRC reconfiguration message.

[0140] In addition, in another specific implementation form, after obtaining the second information, the RRC layer may further send a cancel instruction to the MAC layer to instruct the MAC layer to cancel the activation request, that is, after receiving the cancel instruction, the MAC layer may no longer request to activate the pre-configured information before the modification.

[0141] Alternatively, the second information sent by the RRC layer to the MAC layer may be understood as a cancellation indication.

[0142] For example, the RRC layer receives an RRC message, which includes pre-configuration information 1. The RRC layer sends the pre-configuration information 1 to the MAC layer. The MAC layer triggers SR when it requests activation of the pre-configuration information 1. Furthermore, the RRC layer receives an RRC message, which includes second information. The RRC layer sends the second information (or a cancel instruction) to the MAC layer. The MAC layer cancels the activation request, i.e., the MAC layer no longer needs to request activation of the pre-configuration information 1 before the modification.

[0143] Condition 1-5: The UE stops measuring.

[0144] This method is applicable when the pre-configured information is the configuration information of the MG pre-configured for positioning. It will be understood that when the UE stops the measurement, the UE no longer needs to request activation of the pre-configured information. The measurement includes at least one or more of positioning measurement and RRM measurement.

[0145] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer indicates to the MAC layer to stop measurement. Optionally, the RRC layer sends a measurement stop instruction to the MAC layer, where the measurement stop instruction indicates to the MAC layer to stop measurement, i.e., to cancel the activation request. Optionally, the RRC layer may further receive an instruction from an upper layer of the RRC layer (e.g., a radio link control (RLC) layer or a packet data convergence protocol (PDCP) layer), and further send a measurement stop instruction to the MAC layer based on the instruction of the upper layer.

[0146] Condition 1-6: The UE triggers a deactivation request, and the deactivation request is used to deactivate the pre-configuration information.

[0147] It can be understood that in the process where the UE triggers an activation request and does not send the activation request successfully, the UE triggers a deactivation request, in which case the UE no longer needs to send the activation request.

[0148] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer triggers a deactivation request and sends the deactivation request to the MAC layer. Correspondingly, the MAC layer determines, based on the unsent deactivation request and activation request, that the activation request and the deactivation request indicate the same pre-configuration information. In this case, the MAC layer may no longer need to send the activation request, that is, the MAC layer cancels the activation request. Optionally, when an identifier (e.g., a positioning MG ID) of the pre-configuration information included in the activation request is the same as an identifier (e.g., a positioning MG ID) of the pre-configuration information included in the deactivation request, the UE may determine that the activation request and the deactivation request indicate the same pre-configuration information.

[0149] Optionally, when the first information is a deactivation request, condition 1 may include at least one or more of the following condition 1-a and condition 1-b: The UE determining that condition 1 is satisfied may specifically be the UE determining that condition 1-a or condition 1-b is satisfied.

[0150] Condition 1-a: The UE receives the second information, and the second information is used to modify the pre-configuration information.

[0151] It will be understood that, upon receiving the second information, the UE needs to modify the configuration parameters in the pre-configuration information based on the second information. In this way, the pre-configuration information that has already been activated before the modification is invalid, i.e., the UE no longer needs to request that the pre-configuration information that has already been activated before the modification be deactivated.

[0152] For example, the UE receives pre-configuration information 1 and then requests deactivation of pre-configuration information 1. Upon receiving second information, the UE modifies configuration parameters in pre-configuration information 1 based on the second information. In this way, the pre-configuration information 1 that has already been activated before the modification is invalid, and the UE no longer needs to request deactivation of the pre-configuration information 1 that has already been activated before the modification.

[0153] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message, and the RRC layer sends a cancellation instruction to the MAC layer based on the second information. In response, the MAC layer cancels the deactivation request based on the cancellation instruction. For specific implementation, see the description of conditions 1-4. For ease of understanding, the "activation request" may be replaced with the "deactivation request."

[0154] Condition 1-b: The UE has already deactivated the pre-configuration information.

[0155] It should be understood that when the UE has already deactivated the pre-configuration information in another manner, the UE may no longer need to send a deactivation request, i.e., the UE cancels the deactivation request. For example, in the process of the UE requesting deactivation of pre-configuration information 1, an SR is triggered or a RACH is further triggered. Furthermore, when the UE determines that pre-configuration information 1 has already been deactivated, the UE cancels the deactivation request used to deactivate pre-configuration information 1.

[0156] In a specific implementation, after the pre-configuration information has already been deactivated, the MAC layer of the UE no longer needs to send a deactivation request, i.e., the MAC layer of the UE cancels the deactivation request. Further referring to the above example, after determining that the pre-configuration information 1 has already been deactivated, the MAC layer of the UE no longer needs to request deactivation of the pre-configuration information 1, i.e., the MAC layer of the UE cancels the deactivation request used to deactivate the pre-configuration information 1.

[0157] Condition 1-c: The UE triggers an activation request, and the activation request is used to activate the pre-configuration information.

[0158] It should be understood that in a process in which the UE triggers a deactivation request and does not successfully transmit the deactivation request, the UE triggers an activation request. In this case, the UE no longer needs to transmit the deactivation request. In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer triggers an activation request and transmits the activation request to the MAC layer. Correspondingly, the MAC layer determines, based on the activation request and the untransmitted deactivation request, that the deactivation request and the activation request indicate the same pre-configuration information. In this case, the MAC layer may no longer need to transmit the deactivation request, i.e., the MAC layer cancels the deactivation request. For specific implementations, please refer to the description of conditions 1-6 above. For ease of understanding, the "activation request" may be replaced with the "deactivation request," and the "deactivation request" may be replaced with the "activation request."

[0159] In one example, the activation request or deactivation request may be carried within a MAC CE. In an implementation of the interaction between the RRC layer and the MAC layer in the UE, when the RRC layer determines that condition 1 is met, the RRC layer sends an instruction to cancel the MAC CE to the MAC layer to indicate to the MAC layer to cancel the MAC CE. See FIG. 5 for a diagram of the interaction between the RRC layer and the MAC layer. For example, when the RRC layer determines that conditions 1-2 are met, the instruction to cancel the MAC CE is specifically new pre-configuration information; when the RRC layer determines that conditions 1-4 are met, the instruction to cancel the MAC CE is specifically a cancellation instruction; or when the RRC layer determines that conditions 1-5 are met, the instruction to cancel the MAC CE is specifically a measurement stop instruction.

[0160] In the above-mentioned implementation form 1, a preset condition is provided for the UE to cancel the first information (i.e., an activation request or a deactivation request). When the preset condition is met, the UE may cancel the first information. In this way, the UE does not need to transmit the first information, i.e., does not need to transmit the SR triggered by the first information, and no longer needs to transmit the RACH triggered by the SR. This helps to reduce resource waste.

[0161] In implementation form 2, when determining that condition 2 is met, the UE cancels the SR triggered by the first information.

[0162] Optionally, when the first information is an activation request, Condition 2 may include at least one or more of the following Conditions 2-1 to 2-6.

[0163] The UE determining that condition 2 is satisfied may specifically mean that the UE determines that any one of conditions 2-1 to 2-6 is satisfied.

[0164] Condition 2-1: The UE has already sent an activation request.

[0165] It will be appreciated that the UE transmits the activation request upon determining that there is a PUSCH resource to be used for transmitting the activation request. In this manner, the UE no longer needs to transmit an SR to request a PUSCH resource to be used for transmitting the activation request.

[0166] For example, when the UE needs to send an activation request (e.g., at time 1), the UE determines that there is no PUSCH resource, and therefore triggers an SR (the SR is in a pending state). Further, in the process of the SR being in a pending state, the UE determines that there is already a PUSCH resource that can be used to send the activation request (e.g., at time 2). Therefore, after sending the activation request using the existing PUSCH resource, the UE cancels the SR, and time 2 is later than time 1.

[0167] In a specific implementation, after the activation request has already been sent, the MAC layer of the UE cancels the SR triggered by the activation request. In a specific implementation, when the MAC layer in the UE completes packet assembly of the activation request, the activation request may be considered to have already been sent.

[0168] In a specific implementation, the UE may trigger multiple activation requests, each triggering a respective SR. Correspondingly, after determining that all activation requests have already been sent, the UE may cancel all SRs corresponding to all activation requests, or cancel some of all SRs corresponding to all activation requests. Alternatively, after determining that one of the activation requests has already been sent, the UE cancels the SR triggered by the activation request.

[0169] For example, the UE triggers activation request 1 and activation request 2, which trigger SR1 and SR2, respectively. In one example, the UE cancels SR1 and SR2 after activation request 1 and activation request 2 have already been sent. In another example, the UE cancels SR1 or SR2 after activation request 1 and activation request 2 have already been sent. Alternatively, the UE cancels SR1 triggered by activation request 1 after activation request 1 has already been sent, and the UE cancels SR2 triggered by activation request 2 after activation request 2 has already been sent.

[0170] Condition 2-2: The UE cancels the activation request.

[0171] It will be appreciated that after canceling an activation request, the UE may no longer need to request the PUSCH resources used to transmit the activation request, i.e., the UE does not need to transmit the SR triggered by the activation request.

[0172] For conditions under which the UE cancels the activation request, please refer to the above implementation form 1.

[0173] In one specific implementation, the MAC layer of the UE cancels the activation request, and then the MAC layer cancels the SR triggered by the activation request.

[0174] In a specific implementation, the UE may trigger multiple activation requests, each triggering a respective SR. Correspondingly, after all activation requests have been canceled, the UE may cancel all SRs corresponding to all activation requests, or cancel some of all SRs corresponding to all activation requests. Alternatively, after determining that one of the activation requests has been canceled, the UE cancels the SR triggered by the activation request.

[0175] For example, the UE triggers activation request 1 and activation request 2, which trigger SR1 and SR2, respectively. In one example, the UE cancels SR1 and SR2 after activation request 1 and activation request 2 have been canceled. In another example, the UE cancels one or more of SR1 and SR2 after activation request 1 and activation request 2 have been canceled. Alternatively, after activation request 1 is canceled, the UE cancels SR1 triggered by activation request 1, and after activation request 2 is canceled, the UE cancels SR2 triggered by activation request 2.

[0176] Condition 2-3: The UE receives the second information, and the second information is used to modify the pre-configuration information.

[0177] It will be appreciated that upon receiving the second information (sometimes referred to as reconfiguration information), the UE does not need to send an activation request used to activate the pre-configuration information before modification. For a specific explanation, see the description of conditions 1-4 above. Furthermore, the UE does not need to send an SR used to request PUSCH resources (i.e., an SR triggered by an activation request).

[0178] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message (specifically, may be an RRC reconfiguration message). The RRC layer sends a cancel instruction to the MAC layer to indicate to the MAC layer to cancel the activation request. For specific descriptions, see the description of conditions 1-4 above. Correspondingly, the MAC layer may not only cancel the activation request, but also cancel the SR triggered by the activation request.

[0179] Condition 2-4: The UE has already activated the pre-configuration information.

[0180] It will be understood that when the UE has already activated the pre-configuration information in another manner, the UE may cancel the activation request, i.e., the UE does not need to send an SR triggered by the activation request. In a specific implementation, after the MAC layer of the UE has already activated the pre-configuration information, the MAC layer may cancel the activation request, i.e., the MAC layer does not need to send an SR triggered by the activation request.

[0181] For details, see the explanation of condition 1-1 above.

[0182] Condition 2-5: The UE receives new pre-configuration information.

[0183] It will be understood that when the UE receives new pre-configuration information, the pre-configuration information may be considered to have been changed. The UE no longer needs to request activation of the pre-configuration information, i.e., the UE cancels the activation request. Furthermore, the UE determines that the SR triggered by the activation request does not need to be transmitted, i.e., the UE cancels the SR.

[0184] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer receives an RRC message, which includes new pre-configuration information, and then transmits the new pre-configuration information to the MAC layer. Correspondingly, the MAC layer determines that the pre-configuration information has been changed and cancels the activation request. Furthermore, the MAC layer cancels the SR triggered by the activation request.

[0185] For details, see the explanation of condition 1-2 above.

[0186] Condition 2-6: The UE stops measuring.

[0187] This method is applicable when the pre-configured information is the configuration information of the MG pre-configured for positioning. It will be understood that when the UE stops the measurement, the UE cancels the activation request and further cancels the SR triggered by the activation request. The measurement includes at least one or more of positioning measurement and RRM measurement.

[0188] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer indicates to the MAC layer to stop measurement. Optionally, the RRC layer sends a measurement stop instruction to the MAC layer, and the measurement stop instruction indicates to the MAC layer to stop measurement, i.e., to cancel the activation request. After canceling the activation request, the MAC layer further cancels the SR triggered by the activation request. Optionally, the RRC layer may further receive an instruction from a layer above the RRC layer (e.g., an RLC layer or a PDCP layer) and send a measurement stop instruction to the MAC layer based on the instruction of the upper layer.

[0189] Note that the UE (or the MAC layer in the UE) may first cancel the activation request and then cancel the SR triggered by the activation request. Alternatively, in another possible scheme, the UE (or the MAC layer in the UE) directly cancels the SR triggered by the activation request.

[0190] Optionally, when the first information is a deactivation request, Condition 2 may include at least one or more of the following Conditions 2-a to 2-d:

[0191] The UE determining that condition 2 is satisfied may specifically mean that the UE determines that one or more of conditions 2-a to 2-d are satisfied.

[0192] Condition 2-a: The UE has already sent a deactivation request.

[0193] It will be appreciated that the UE transmits the deactivation request upon determining that there is a PUSCH resource available for transmitting the deactivation request, and thus the UE may no longer transmit the SR triggered by the deactivation request.

[0194] For example, when the UE needs to send a deactivation request (e.g., at time a), the UE determines that there is no PUSCH resource, and therefore triggers an SR (the SR is in a pending state). Further, in the process of the SR being in a pending state, the UE determines that there is already a PUSCH resource that can be used to send the deactivation request (e.g., at time b). Therefore, after sending the deactivation request using the PUSCH resource, the UE cancels the SR triggered by the deactivation request, and time b is later than time a.

[0195] In a specific implementation, the MAC layer of the UE cancels the SR triggered by the deactivation request after the deactivation request has already been sent. In a specific implementation, when the MAC layer in the UE completes packet assembly for the deactivation request, the deactivation request may be considered to have already been sent.

[0196] In a specific implementation, the UE may trigger multiple deactivation requests, each triggering a respective SR. Correspondingly, after determining that all deactivation requests have already been sent, the UE may cancel all SRs corresponding to all deactivation requests, or cancel some of all SRs corresponding to all deactivation requests. Alternatively, after determining that one of the deactivation requests has already been sent, the UE cancels the SR triggered by the deactivation request. For a specific example, see the description of condition 2-1. "Activation request" is replaced with "deactivation request" for ease of understanding.

[0197] Condition 2-b: The UE cancels the deactivation request.

[0198] It will be appreciated that after canceling a deactivation request, the UE may no longer need to request the PUSCH resources used to transmit the deactivation request, i.e., the UE does not need to transmit the SR triggered by the deactivation request.

[0199] For the conditions for the UE to cancel the deactivation request, please refer to the above implementation form 1.

[0200] In one specific implementation, the MAC layer of the UE cancels the deactivation request, and further, the MAC layer cancels the SR triggered by the deactivation request.

[0201] In a specific implementation, the UE may trigger multiple deactivation requests, each triggering a respective SR. Correspondingly, after all deactivation requests have been canceled, the UE may cancel all SRs corresponding to all deactivation requests, or cancel some of all SRs corresponding to all deactivation requests. Alternatively, after determining that one of the deactivation requests has been canceled, the UE cancels the SR triggered by the deactivation request. For a specific example, see the description of condition 2-2. "Activation request" is replaced with "deactivation request" for ease of understanding.

[0202] Condition 2-c: The UE receives second information, and the second information is used to modify the pre-configuration information.

[0203] It will be appreciated that upon receiving the second information (sometimes referred to as reconfiguration information), the UE does not need to send a deactivation request used to deactivate the pre-configured information before modification. For a specific explanation, see the description of Conditions 2-3 above. Furthermore, the UE does not need to send an SR used to request PUSCH resources (i.e., an SR triggered by a deactivation request).

[0204] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message (specifically, an RRC reconfiguration message). The RRC layer sends a cancel instruction to the MAC layer to indicate to the MAC layer to cancel the deactivation request. The MAC layer may not only cancel the deactivation request, but also cancel the SR triggered by the deactivation request. For a specific description, see the description of Condition 2-3 above. The term "activation request" is replaced with "deactivation request" for ease of understanding.

[0205] Condition 2-d: The UE has already deactivated the pre-configuration information.

[0206] It will be appreciated that when the UE has already deactivated the pre-configuration information in another manner, the UE may no longer request the PUSCH resources used to send the deactivation request, i.e., the UE does not need to send an SR triggered by the deactivation request.

[0207] In one specific implementation, the MAC layer of the UE has already deactivated the pre-configuration information, and the MAC layer may further cancel the SR triggered by the deactivation request.

[0208] In addition, it should be noted that the UE (or the MAC layer in the UE) may first cancel the deactivation request and then cancel the SR triggered by the deactivation request. Alternatively, in another possible scheme, the UE (or the MAC layer in the UE) directly cancels the SR triggered by the deactivation request.

[0209] In a specific implementation, the activation request or deactivation request may be carried within the MAC CE. After canceling the MAC CE, the MAC layer may cancel the SR triggered by the MAC CE. For an illustration of canceling the SR triggered by the MAC CE in the MAC layer, see scheme a in Figure 6. In addition, after receiving the second information, the RRC layer may further directly send a cancellation indication to the MAC layer to indicate to the MAC layer to cancel the SR triggered by the MAC CE. After receiving the instruction from the upper layer, the RRC sends a measurement stop indication to the MAC layer, which indicates to stop measurement, i.e., to cancel the SR triggered by the MAC CE. In this specification, the cancellation indication and the measurement stop indication may be collectively referred to as an instruction to cancel the SR. For an illustration of sending an instruction to cancel the SR by the RRC layer to the MAC layer, see scheme b in Figure 6.

[0210] In the above-mentioned implementation form 2, a preset condition is provided for the UE to cancel the SR. When the preset condition is met, the UE may cancel the SR. This helps to reduce resource waste.

[0211] In implementation 3, if the UE determines that condition 3 is met, it cancels the RACH.

[0212] Optionally, when the first information is an activation request, Condition 3 may include at least one or more of the following Conditions 3-1 to 3-6.

[0213] The UE determining that condition 3 is satisfied may specifically mean that the UE determines that any one of conditions 3-1 to 3-6 is satisfied.

[0214] Condition 3-1: The UE cancels the activation request.

[0215] It will be appreciated that after canceling an activation request, the UE may no longer need to request a PUSCH resource used to transmit the activation request, i.e., the UE does not need to transmit an SR triggered by the activation request. Furthermore, the UE may no longer need to request a PUCCH resource used to transmit an SR, i.e., the UE does not need to transmit an RACH triggered by the SR.

[0216] For conditions under which the UE cancels the activation request, please refer to the above implementation form 1.

[0217] In a specific implementation, after canceling the activation request, the MAC layer of the UE cancels the SR triggered by the activation request, and then cancels the RACH triggered by the SR.

[0218] Condition 3-2: The UE cancels the SR triggered by the activation request.

[0219] It will be appreciated that after canceling the SR, the UE may no longer need to request PUCCH resources used to transmit the SR, i.e., the UE does not need to transmit the RACH triggered by the SR.

[0220] For conditions for the UE to cancel an SR triggered by an activation request, please refer to Implementation 2 above.

[0221] In one specific implementation, after canceling the SR triggered by the activation request, the MAC layer of the UE cancels the RACH triggered by the SR.

[0222] Condition 3-3: The UE stops measuring.

[0223] This method is applicable when the pre-configured information is the configuration information of the MG pre-configured for positioning. It should be understood that when the UE stops the measurement, after canceling the activation request, the UE cancels the SR triggered by the activation request, and then cancels the RACH triggered by the SR. The measurements include at least one or more of positioning measurements and RRM measurements.

[0224] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer indicates to the MAC layer to stop measurement. Optionally, the RRC layer sends a measurement stop instruction to the MAC layer, which indicates to stop measurement, i.e., to cancel the activation request. After canceling the activation request, the MAC layer cancels the SR triggered by the activation request, and then cancels the RACH triggered by the SR. Optionally, the RRC layer may further receive an instruction from a layer above the RRC layer (e.g., an RLC layer or a PDCP layer) and send a measurement stop instruction to the MAC layer based on the instruction of the upper layer.

[0225] Condition 3-4: The UE receives the second information, and the second information is used to modify the pre-configuration information.

[0226] It will be understood that upon receiving the second information, the UE does not need to send an activation request used to activate the pre-configuration information before the modification. For specific explanations, see the description of conditions 1-4 above. Furthermore, the UE does not need to send an SR used to request PUSCH resources (i.e., an SR triggered by an activation request), and does not need to send a RACH used to request PUCCH resources (i.e., a RACH triggered by an SR).

[0227] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message. The RRC layer sends a cancellation instruction to the MAC layer to indicate that the activation request should be canceled. For specific descriptions, see the descriptions of conditions 1-4 above. Correspondingly, the MAC layer may not only cancel the activation request, but also cancel the SR triggered by the activation request and further cancel the RACH triggered by the SR.

[0228] Condition 3-5: The UE has already activated the pre-configuration information.

[0229] It will be appreciated that when the UE has already activated the pre-configuration information in another manner, the UE may cancel the activation request, i.e., the UE does not need to send an SR triggered by the activation request, and further, the UE does not need to send a RACH triggered by the SR.

[0230] In one specific implementation, after the MAC layer of the UE determines that the pre-configuration information has already been activated, the MAC layer cancels the activation request, further cancels the SR triggered by the activation request, and cancels the RACH triggered by the SR.

[0231] Condition 3-6: The UE receives new pre-configuration information.

[0232] It will be understood that when the UE receives new pre-configuration information, the pre-configuration information may be considered to have been changed. The UE no longer needs to request activation of the pre-configuration information, i.e., the UE cancels the activation request. Furthermore, the UE determines that the SR triggered by the activation request does not need to be transmitted, i.e., the UE cancels the SR. Then, the UE determines that the RACH triggered by the SR does not need to be transmitted, i.e., the UE cancels the RACH.

[0233] In one specific implementation, after receiving the new pre-configuration information, the MAC layer of the UE cancels the activation request, further cancels the SR, and then cancels the RACH.

[0234] Note that the UE may first cancel the activation request, then cancel the SR triggered by the activation request, and then cancel the RACH triggered by the SR. Alternatively, in another possible scheme, the UE directly cancels the RACH triggered by the SR.

[0235] Optionally, when the first information is a deactivation request, Condition 3 may include at least one or more of the following Conditions 3-a to 3-d:

[0236] The UE determining that condition 3 is satisfied may specifically mean that the UE determines that any one of conditions 3-a to 3-d is satisfied.

[0237] Condition 3-a: The UE cancels the deactivation request.

[0238] It will be understood that after canceling a deactivation request, the UE may no longer need to request a PUSCH resource used to transmit the deactivation request, i.e., the UE cancels the SR triggered by the deactivation request. For conditions for the UE to cancel a deactivation request, see Implementation 1 above. Furthermore, after canceling an SR, the UE may no longer need to request a PUCCH resource used to transmit the SR, i.e., the UE cancels the RACH triggered by the SR.

[0239] In one specific implementation, after canceling the deactivation request, the MAC layer in the UE cancels the SR and then cancels the RACH.

[0240] Condition 3-b: The UE cancels the SR triggered by the deactivation request.

[0241] It will be appreciated that after canceling the SR triggered by the deactivation request, the UE may no longer need to request PUCCH resources used to transmit the SR, i.e., it does not need to transmit the RACH triggered by the SR. For conditions for the UE to cancel the SR, please refer to Implementation 2 above.

[0242] In one specific implementation, the MAC layer of the UE cancels the SR and also cancels the RACH.

[0243] Condition 3-c: The UE receives the second information, and the second information is used to modify the pre-configuration information.

[0244] It will be understood that upon receiving the second information, the UE does not need to send a deactivation request used to deactivate the pre-configured information before the modification. For specific explanations, see the description of conditions 1-4 above. Furthermore, the UE does not need to send an SR used to request PUSCH resources (i.e., an SR triggered by a deactivation request). The UE does not need to send a RACH used to request PUCCH resources (i.e., a RACH triggered by an SR).

[0245] In a specific implementation, the UE includes an RRC layer and a MAC layer. The RRC layer obtains the second information using an RRC message. The RRC layer sends a cancel instruction to the MAC layer to indicate that the MAC layer should cancel the deactivation request. In response, the MAC layer may not only cancel the deactivation request, but also cancel the SR triggered by the deactivation request and the RACH triggered by the SR.

[0246] Condition 3-d: The UE has already deactivated the pre-configuration information.

[0247] It will be appreciated that when the UE has already deactivated the pre-configuration information in another manner, the UE may no longer request a PUSCH resource used to transmit the deactivation request, i.e., the UE does not need to transmit an SR triggered by the deactivation request. Furthermore, the UE no longer requests a PUCCH resource used to transmit an SR, i.e., the UE does not need to transmit an RACH triggered by the SR.

[0248] In one specific implementation, the MAC layer in the UE has already deactivated the pre-configuration information and further cancels the SR triggered by the deactivation request and the RACH triggered by the SR.

[0249] Additionally, it should be noted that the UE may first cancel the deactivation request, then cancel the SR triggered by the deactivation request, and then cancel the RACH triggered by the SR. Alternatively, in another possible scheme, the UE directly cancels the RACH triggered by the SR.

[0250] In one particular implementation, the activation or deactivation request may be carried within the MAC CE.

[0251] After canceling the MAC CE, the MAC layer of the UE further cancels the MAC CE-triggered SR and the SR-triggered RACH (see scheme b in FIG. 7). Alternatively, after canceling the MAC CE-triggered SR, the MAC layer further cancels the SR-triggered RACH (see scheme a in FIG. 7). In addition, after receiving the second information, the RRC may further directly send a cancellation indication to the MAC layer to indicate to the MAC layer to cancel the SR-triggered RACH. After receiving an indication from the upper layer, the RRC layer sends a measurement stop indication to the MAC layer, which indicates to stop measurement, i.e., to cancel the SR-triggered RACH. In this specification, the cancellation indication and the measurement stop indication may be collectively referred to as an indication to cancel the RACH. For an illustration of sending an indication to cancel the RACH by the RRC layer to the MAC layer, see scheme c in FIG. 6.

[0252] In the above-mentioned implementation form 3, a preset condition is provided for the UE to cancel the RACH. When the preset condition is met, the UE may cancel the RACH. In this way, the UE no longer transmits the RACH. This helps to reduce resource waste.

[0253] It should be added that in this application, the UE mainly interacts with the NG-RAN, for example, the UE receives pre-configuration information, second information, etc. from the NG-RAN, and the UE transmits first information, SR, RACH, etc. to the NG-RAN.

[0254] Based on the above content and the same concept, Figures 8 and 9 are diagrams of possible communication device structures according to the present application. These communication devices can be configured to implement the functions of the UE in the above method embodiments, and therefore can also implement the beneficial effects of the above method embodiments. In the present application, the communication device may be the UE shown in Figure 1, or a module (e.g., a chip) applicable to the UE.

[0255] 8, the communication device 800 includes a transceiver module 801 and a processing module 802. The communication device 800 is configured to perform the functions of the UE in the method embodiment shown in FIG.

[0256] The communication device 800 includes the following: a transceiver module 801 configured to receive pre-configuration information; a processing module 802 configured to stop requesting uplink resources when a preset condition is met, the uplink resources being used to transmit first information, and when the first information is an activation request, the first information being used to activate the pre-configured information; or when the first information is a deactivation request, the first information being used to deactivate the pre-configured information; and Includes:

[0257] In one possible implementation, the pre-configuration information is configuration information of a MG that is pre-configured for positioning.

[0258] In one possible implementation, when there is no PUSCH resource to be used for transmitting the first information, the processing module 802 is further configured to trigger a scheduling request SR, where the SR is used to request a PUSCH resource.

[0259] In one possible implementation, when there are no PUCCH resources to be used for transmitting the SR, the processing module 802 is further configured to trigger a RACH, which is used to request uplink resources.

[0260] In one possible implementation, the processing module 802 is specifically configured to: cancel the first information and stop requesting uplink resources when the communication device 800 satisfies a preset condition; When the first information is an activation request, the pre-configuration conditions include one or more of the following: measurements should be stopped; new pre-configuration information is received; other pre-configuration information is activated and the other pre-configuration information meets measurement requirements; second information is received and the second information is used to modify the pre-configuration information; and pre-configuration information is already activated and the measurements are at least one or more of positioning measurements and RRM measurements; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; and the pre-configured information has already been deactivated.

[0261] In one possible implementation, the UE includes an RRC layer and a MAC layer.

[0262] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the RRC layer indicates to the MAC layer to stop measurement; the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; the MAC layer activates other pre-configuration information; the RRC layer receives second information and the RRC layer sends a cancel indication to the MAC layer, the cancel indication is used to cancel the activation request; and the MAC layer has already activated the pre-configuration information; and / or When the first information is a deactivation request, the preconfigured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request, and the MAC layer has already deactivated the preconfigured information.

[0263] In one possible implementation, the processing module 802 is specifically configured to cancel an SR triggered by the first information when the communication device 800 satisfies a preset condition, the SR being used to request a PUSCH resource, and the PUSCH resource being used to transmit the first information.

[0264] and / or when the first information is an activation request, the pre-configuration conditions include one or more of the following: an activation request has already been sent; the activation request is canceled; measurements should be stopped, and the measurements include at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify pre-configuration information; pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: a deactivation request has already been sent; second information is received and the second information is used to modify the pre-configured information; the deactivation request is canceled; and the pre-configured information has already been deactivated.

[0265] In one possible implementation, the UE includes an RRC layer and a MAC layer.

[0266] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the MAC layer has already sent an activation request; the MAC layer cancels the activation request; the RRC layer indicates to the MAC layer to stop measuring; the RRC layer receives the second information, and the RRC layer sends a cancellation indication to the MAC layer, and the cancellation indication is used to cancel the activation request; the MAC layer has already activated pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: the MAC layer has already sent a deactivation request; the RRC layer receives the second information, the RRC layer sends a cancel instruction to the MAC layer, and the cancel instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; and the MAC layer has already deactivated the pre-configured information.

[0267] In one possible implementation, the activation request has already been transmitted includes determining that the activation request has already been transmitted after packet assembly of the activation request has been performed, and / or the deactivation request has already been transmitted includes determining that the UE has already transmitted the deactivation request after packet assembly of the deactivation request has been performed.

[0268] In one possible implementation, the processing module 802 is specifically configured to cancel the RACH triggered by the SR when the communication device 800 meets a preset condition, and the RACH is used to request uplink resources.

[0269] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the activation request is canceled; the SR triggered by the activation request is canceled; measurements should be stopped, and the measurements include at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify pre-configuration information; the pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is a deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; the deactivation request is canceled; the SR triggered by the deactivation request is canceled; and the pre-configured information has already been deactivated.

[0270] In one possible implementation, the UE includes an RRC layer and a MAC layer.

[0271] When the first information is an activation request, the pre-configuration conditions include one or more of the following: the MAC layer cancels the activation request; the MAC layer cancels the SR triggered by the activation request; the RRC layer indicates to the MAC layer to stop measurement; the RRC layer receives the second information and sends a cancellation indication to the MAC layer, where the cancellation indication is used to cancel the activation request; the MAC layer has already activated the pre-configuration information; the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or when the first information is a deactivation request, the pre-configuration conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation indication to the MAC layer, where the cancellation indication is used to cancel the deactivation request; the MAC layer cancels the deactivation request; the MAC layer cancels the SR triggered by the deactivation request; and the MAC layer has already deactivated the pre-configuration information.

[0272] In one possible implementation, the first information is a MAC CE.

[0273] Figure 9 shows an apparatus 900 according to one embodiment of the present application. The apparatus shown in Figure 9 may be an implementation of the hardware circuit of the apparatus shown in Figure 8. The apparatus may be applicable to performing the functions of the UE in the aforementioned method embodiments in the above flowcharts. For ease of explanation, Figure 9 shows only the main components of the apparatus.

[0274] 9 includes a communication interface 910, a processor 920, and a memory 930. The memory 930 is configured to store program instructions and / or data. The processor 920 may operate in cooperation with the memory 930. The processor 920 may execute program instructions stored in the memory 930. When the instructions or programs stored in the memory 930 are executed, the processor 920 is configured to perform the operations performed by the processing module 802 in the aforementioned embodiments, and the communication interface 910 is configured to perform the operations performed by the transceiver module 801 in the aforementioned embodiments.

[0275] The memories 930 are coupled to the processor 920. The coupling in this embodiment of the present application may be an electrical, mechanical, or other form of indirect coupling or communication connection between devices, units, or modules, used for exchanging information between the devices, units, or modules. At least one of the memories 930 may be included in the processor 920.

[0276] In this embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or another type of communication interface. In this embodiment of the present application, when the communication interface is a transceiver, the transceiver may include a separate receiver and a separate transmitter, or may be a transceiver or a communication interface integrated with transceiver functionality.

[0277] The device 900 may further include a communication line 940. The communication interface 910, the processor 920, and the memory 930 may be interconnected using the communication line 940. The communication line 940 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The communication line 940 may be categorized into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent a bus in FIG. 9, but this does not mean that there is only one bus or only one type of bus.

[0278] Based on the above and the same concept, one embodiment of the present application provides a computer-readable storage medium, which stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the communication device is enabled to perform the method of the above method embodiment.

[0279] Based on the foregoing and the same concept, one embodiment of the present application provides a computer program product, which, when read and executed by a communication device, enables the communication device to perform the method of the foregoing method embodiments.

[0280] It should be understood that various numbers in the embodiments of the present application are used only for distinction to facilitate description, and are not intended to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not imply an execution order, and the execution order of the processes should be determined based on the functions and internal logic of the processes.

[0281] It is obvious that those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Thus, this application is intended to cover these modifications and variations of this application as long as they fall within the scope of the claims of this application and their equivalent technologies. [Explanation of symbols]

[0282] 801 Transceiver Module 802 Processing Module 900 Communication Equipment 910 Communication Interface 920 processor 930 memory 940 communication lines

Claims

1. 1. A communication method comprising: receiving, by a terminal device UE, pre-configuration information; stopping, by the UE, the request for uplink resources when a pre-configured condition is met; Including, the uplink resource is used to transmit first information; When the first information is an activation request, the first information is used to activate the pre-configured information, or when the first information is a deactivation request, the first information is used to deactivate the pre-configured information. Communication method.

2. The method of claim 1 , wherein the pre-configuration information is configuration information of a pre-configured measurement gap management group for positioning.

3. triggering, by the UE, a scheduling request SR when there is no physical uplink shared channel (PUSCH) resource to be used for transmitting the first information, wherein the SR is used to request the PUSCH resource.

3. The method of claim 1 or 2, further comprising:

4. triggering, by the UE, a random access channel (RACH) when there is no physical uplink control channel (PUCCH) resource to be used for transmitting the SR, the RACH being used to request the uplink resource.

4. The method of claim 3, further comprising:

5. The step of stopping the request for uplink resources by the UE when a pre-configured condition is met includes: canceling, by the UE, the first information and stopping the request for uplink resources when the pre-configured condition is met; Including, and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: measurements should be stopped; new pre-configured information is received; other pre-configured information is activated and the other pre-configured information meets measurement requirements; second information is received and the second information is used to modify the pre-configured information; and the pre-configured information is already activated and the measurements include at least one or more of positioning measurements and radio resource management (RRM) measurements; When the first information is the deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; and the pre-configured information has already been deactivated.

5. The method according to any one of claims 1 to 4.

6. the UE includes a radio resource control (RRC) layer and a medium access control (MAC) layer; and / or when the first information is the activation request, the pre-configuration conditions include one or more of the following: the RRC layer indicates to the MAC layer to stop measurements; the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; the MAC layer activates other pre-configuration information; the RRC layer receives the second information and sends a cancel indication to the MAC layer, the cancel indication is used to cancel the activation request; and the MAC layer has already activated the pre-configuration information; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request; and the MAC layer has already deactivated the pre-configured information. The method of claim 5.

7. The step of stopping the request for uplink resources by the UE when a pre-configured condition is met includes: canceling, by the UE, the SR triggered by the first information when the preconfigured condition is met, the SR being used to request the PUSCH resource, and the PUSCH resource being used to transmit the first information; Including, and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: the activation request has already been sent; the activation request is canceled; measurements should be stopped, the measurements including at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify the pre-configuration information; the pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the deactivation request has already been sent; second information is received and the second information is used to modify the pre-configured information; the deactivation request is canceled; and the pre-configured information has already been deactivated.

5. The method according to any one of claims 1 to 4.

8. the UE includes an RRC layer and a MAC layer; and / or when the first information is the activation request, the pre-configuration conditions include one or more of the following: the MAC layer has already sent the activation request; the MAC layer cancels the activation request; the RRC layer indicates to the MAC layer to stop measurements; the RRC layer receives the second information, the RRC layer sends a cancellation indication to the MAC layer, and the cancellation indication is used to cancel the activation request; the MAC layer has already activated the pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the MAC layer has already sent the deactivation request; the RRC layer receives the second information, the RRC layer sends a cancel instruction to the MAC layer, and the cancel instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; and the MAC layer has already deactivated the pre-configured information. The method of claim 7.

9. The UE having already sent the activation request includes determining, by the UE after performing packet assembly of the activation request, that the UE has already sent the activation request; and / or The UE having already sent the deactivation request includes determining, by the UE after performing packet assembly of the deactivation request, that the UE has already sent the deactivation request.

9. The method of claim 7 or 8.

10. The step of stopping the request for uplink resources by the UE when a pre-configured condition is met includes: canceling, by the UE, the RACH triggered by the SR when the pre-configured condition is met, the RACH being used to request the uplink resources. Including, and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: the activation request is canceled; the SR triggered by the activation request is canceled; measurements should be stopped, the measurements including at least one or more of positioning measurements and RRM measurements; second information is received, the second information is used to modify the pre-configuration information, the pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; the deactivation request is canceled; the SR triggered by the deactivation request is canceled; and the pre-configured information has already been deactivated.

5. The method according to any one of claims 1 to 4.

11. the UE includes an RRC layer and a MAC layer; When the first information is the activation request, the pre-configuration conditions include one or more of the following: the MAC layer canceling the activation request; the MAC layer canceling the SR triggered by the activation request; the RRC layer indicating the MAC layer to stop measurements; the RRC layer receiving the second information and sending a cancellation instruction to the MAC layer, which is used to cancel the activation request; the MAC layer already activating the pre-configuration information; the RRC layer receiving new pre-configuration information and sending the new pre-configuration information to the MAC layer; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; the MAC layer cancels the SR triggered by the deactivation request; and the MAC layer has already deactivated the pre-configured information. The method of claim 10.

12. 12. The method according to claim 1, wherein the first information is a Media Access Control Control Element (MAC CE).

13. A communication device, a transceiver module configured to receive pre-configuration information; a processing module configured to stop requesting uplink resources when a preset condition is met; Equipped with the uplink resource is used to transmit first information, and when the first information is an activation request, the first information is used to activate the pre-configured information, or when the first information is a deactivation request, the first information is used to deactivate the pre-configured information. Communication equipment.

14. The apparatus of claim 13 , wherein the pre-configuration information is configuration information of a pre-configured measurement gap management group for positioning.

15. When there is no physical uplink shared channel (PUSCH) resource to be used for transmitting the information, the processing module: Trigger a scheduling request SR, which is used to request the PUSCH resource.

15. The apparatus of claim 13 or 14, further configured to:

16. When there is no physical uplink control channel (PUCCH) resource to be used for transmitting the SR, the processing module: Triggering a random access channel (RACH), which is used to request the uplink resources.

16. The apparatus of claim 15, further configured to:

17. When the device satisfies the preset condition, the processing module: When the device satisfies the preset condition, cancel the first information and stop requesting the uplink resource. Specifically, it is configured as follows: and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: measurements should be stopped; new pre-configured information is received; other pre-configured information is activated and the other pre-configured information meets measurement requirements; second information is received and the second information is used to modify the pre-configured information; and the pre-configured information is already activated and the measurements include at least one or more of positioning measurements and radio resource management (RRM) measurements; When the first information is the deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; and the pre-configured information has already been deactivated.

17. Apparatus according to any one of claims 13 to 16.

18. The UE includes a radio resource control (RRC) layer and a medium access control (MAC) layer; and / or when the first information is the activation request, the pre-configuration conditions include one or more of the following: the RRC layer indicates to the MAC layer to stop measurements; the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; the MAC layer activates other pre-configuration information; the RRC layer receives the second information and sends a cancel indication to the MAC layer, the cancel indication is used to cancel the activation request; and the MAC layer has already activated the pre-configuration information; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request; and the MAC layer has already deactivated the pre-configured information.

18. The apparatus of claim 17.

19. When the device satisfies the preset condition, the processing module: When the device satisfies the preset condition, cancel the SR triggered by the first information, the SR is used to request the PUSCH resource, and the PUSCH resource is used to transmit the first information. Specifically, it is configured as follows: and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: the activation request has already been sent; the activation request is canceled; measurements should be stopped, the measurements including at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify the pre-configuration information; the pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the deactivation request has already been sent; second information is received and the second information is used to modify the pre-configured information; the deactivation request is canceled; and the pre-configured information has already been deactivated.

17. Apparatus according to any one of claims 13 to 16.

20. the UE includes an RRC layer and a MAC layer; and / or when the first information is the activation request, the pre-configuration conditions include one or more of the following: the MAC layer has already sent the activation request; the MAC layer cancels the activation request; the RRC layer indicates to the MAC layer to stop measurements; the RRC layer receives the second information, the RRC layer sends a cancellation indication to the MAC layer, and the cancellation indication is used to cancel the activation request; the MAC layer has already activated the pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the MAC layer has already sent the deactivation request; the RRC layer receives the second information, the RRC layer sends a cancel instruction to the MAC layer, and the cancel instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; and the MAC layer has already deactivated the pre-configured information.

20. The apparatus of claim 19.

21. The activation request having already been transmitted includes determining that the activation request has already been transmitted after packet assembly of the activation request has been performed; and / or determining that the deactivation request has already been transmitted includes determining that the UE has already transmitted the deactivation request after packet assembly of the deactivation request is performed.

21. Apparatus according to claim 19 or 20.

22. When the device satisfies the preset condition, the processing module: When the device satisfies the preset condition, cancel the RACH triggered by the SR, and the RACH is used to request the uplink resources. Specifically, it is configured as follows: and / or when the first information is the activation request, the pre-configured conditions include one or more of the following: the activation request is canceled; the SR triggered by the activation request is canceled; measurements should be stopped, the measurements including at least one or more of positioning measurements and RRM measurements; second information is received, and the second information is used to modify the pre-configuration information; the pre-configuration information is already activated, and new pre-configuration information is received; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: second information is received, and the second information is used to modify the pre-configured information; the deactivation request is canceled; the SR triggered by the deactivation request is canceled; and the pre-configured information has already been deactivated.

17. Apparatus according to any one of claims 13 to 16.

23. the UE includes an RRC layer and a MAC layer; When the first information is the activation request, the pre-configuration conditions include one or more of the following: the MAC layer cancels the activation request; the MAC layer cancels the SR triggered by the activation request; the RRC layer indicates to the MAC layer to stop measurements; the RRC layer receives the second information and sends a cancellation instruction to the MAC layer, which is used to cancel the activation request; the MAC layer has already activated the pre-configuration information, and the RRC layer receives new pre-configuration information and sends the new pre-configuration information to the MAC layer; and / or When the first information is the deactivation request, the pre-configured conditions include one or more of the following: the RRC layer receives the second information, the RRC layer sends a cancellation instruction to the MAC layer, and the cancellation instruction is used to cancel the deactivation request; the MAC layer cancels the deactivation request; the MAC layer cancels the SR triggered by the deactivation request; and the MAC layer has already deactivated the pre-configured information.

23. The apparatus of claim 22.

24. 24. The apparatus according to claim 13, wherein the first information is a Media Access Control Control Element (MAC CE).

25. 13. A communications device comprising a processor, the processor connected to a memory, the memory configured to store a computer program, the processor configured to execute the computer program stored in the memory to enable the communications device to perform a method according to any one of claims 1 to 12.

26. 13. A computer-readable storage medium storing a computer program or instructions, the computer program or instructions causing a method according to any one of claims 1 to 12 to be performed when executed by a communication device.

27. 13. A computer program product, the computer program product comprising a computer program or instructions, the computer program or instructions, when executed by a communication device, causing the method of any one of claims 1 to 12 to be performed.

Images