Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus, which can be applied to an NTN scenario. An access network device (i.e., a first network device) of a serving cell of a UE determines one or more target cells for the UE, acquires respective PUR configuration information of the one or more target cells, and provides the PUR configuration information corresponding to the one or more target cells to the UE. After the UE leaves the serving cell, the UE may send uplink data on the basis of the PUR configuration information of a new cell, the new cell being one of the one or more target cells. Thus, after the serving cell of the UE changes, uplink data transmission can be carried out on a valid PUR of the new cell, thereby increasing uplink capacity.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 29, 2024, with application number 202410383657.4 and invention name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technology, and more specifically, to a communication method and a communication device. Background Art

[0003] The uplink (UL) system capacity of current narrowband internet of things (NB-IoT) non-terrestrial networks (NTN) is actually limited by the corresponding system downlink (DL) capacity due to the larger signaling overhead in the downlink and the tight coupling between UL and DL signaling. This affects UL traffic, such as mobile originated (MO) transmissions. Whenever a user equipment (UE) needs to transmit UL data, it requires an approximately equal number of DL control messages from the network, which severely limits the UL capacity.

[0004] In order to improve the uplink capacity of the network, early data transmission (EDT) without physical random access channel (PRACH) is proposed. EDT is the transmission of small packets in the idle state of radio resource control (RRC), and PUR (preconfigured uplink resource, PUR) is also the transmission of small packets in the idle state of RRC. The difference between EDT and PUR is that the UE can initiate RA for data transmission in any cell that supports EDT. Although PUR can initiate data transmission without RA, it can only initiate data transmission in cells configured with preconfigured uplink resources. However, in the NTN scenario, the serving cell changes frequently. After the serving cell changes, the UE cannot initiate data transmission based on PUR in the new cell. Summary of the Invention

[0005] The present application provides a communication method and a communication device, which can support a UE to continue to transmit a PUR after switching a serving cell, thereby improving uplink capacity.

[0006] In a first aspect, a communication method is provided, which may be performed by a communication device or a module (e.g., a chip or circuit) applied to the communication device. The communication device may be a first network device in a method embodiment. The method may include: determining one or more target cells, one of the target cells being not a serving cell of a UE; and sending a first message to a user equipment (UE), the first message including configuration information of preconfigured uplink resources (PURs) corresponding to the one or more target cells.

[0007] In this technical solution, the access network device (i.e., the first network device) of the UE's serving cell determines one or more target cells for the UE, obtains PUR configuration information corresponding to the one or more target cells, and provides the PUR configuration information corresponding to the one or more target cells to the UE. After the UE leaves the serving cell, the UE can send uplink data based on the PUR configuration information of the new cell, which is one of the one or more target cells. Therefore, after the UE's serving cell changes, uplink data transmission can be performed on the valid PUR of the new cell, achieving RA-free uplink data transmission and improving uplink capacity.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a second message to a second network device, the second message including identification information of at least one target cell; and receiving a third message from the second network device, the third message including PUR configuration information corresponding to the at least one target cell.

[0009] In this implementation, the first network device provides the identification information of the target cell to the second network device, so that the second network device allocates PUR resources of the target cell to the UE, facilitating the UE to subsequently initiate PUR transmission in the target cell.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the determining of one or more target cells includes: obtaining identification information of the one or more target cells from the UE, the one or more target cells being determined based on one or more of the following information: service stop time information in system message block 3, system message block 31, and system message block 32; determining the one or more target cells according to the identification information of the one or more target cells.

[0011] In this implementation, the terminal device determines the target cell based on system messages, etc., and provides the identification information of the target cell to the first network device, so that the first network device obtains the PUR configuration information of the target cell from the second network device and provides it to the UE, so that the UE can subsequently initiate PUR transmission in the target cell.

[0012] In combination with the first aspect, in certain implementations of the first aspect, determining one or more target cells includes: obtaining PUR demand information from the UE, the PUR demand information including PUR time domain information requested by the UE, the PUR time domain information including at least one of a period, an offset, and a number of times; and determining the one or more target cells based on the PUR demand information.

[0013] In this implementation, the first network device obtains a PUR requirement from the terminal device, and determines a target cell based on the PUR requirement of the terminal device.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the second message further includes one or more items of the following information: UE location information, and PUR time domain information.

[0015] In this implementation, the first network device provides the identifier of the target cell to the second network device through a second message. In addition, the first network device also provides the location of the terminal device, PUR time domain information, etc. to the second network device to facilitate the second network device to determine whether to allocate PUR resources of the target cell.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the second message and / or the third message also includes uplink authorization information, and the uplink authorization information includes one of the following: first uplink authorization information, the first uplink authorization information is the common uplink authorization information of the one or more target cells; or, second uplink authorization information, the second uplink authorization information is the common uplink authorization information of the at least one target cell corresponding to the second network device; or, at least one third uplink authorization information, the third uplink authorization information is the uplink authorization information corresponding to one or more target cells.

[0017] In combination with the first aspect, in some implementations of the first aspect, when the PUR corresponding to the PUR configuration information performs data transmission based on the user plane, the second message further includes one or more of the following information: access layer AS security information corresponding to the first target cell, the AS security information is used to determine the AS security key between the first target cell and the UE, and the AS security information includes an access layer key and the next hop chain to calculate the NCC; the security algorithm of the source cell; the security capability information of the UE, the security capability information of the UE indicating the security algorithms supported by the UE; wherein the security algorithm includes an encryption algorithm and / or an integrity protection algorithm, and the first target cell is one of the one or more target cells.

[0018] In this implementation, when the terminal device uses PUR data transmission based on the user plane, the first network device also provides security-related information of the target cell to the second network device for security protection of user-plane-based data transmission between the second network device and the terminal device.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the PUR configuration information includes one or more of the following information: identification information of the first target cell, uplink authorization information of the first target cell, timing advance TA corresponding to the first target cell, and TA validity condition corresponding to the first target cell, wherein the first target cell is one of the one or more target cells.

[0020] In this implementation, the PUR configuration information configured by the second network device may further include identification information of the target cell, uplink authorization information, TA information, and TA validity conditions, etc.

[0021] In combination with the first aspect, in certain implementations of the first aspect, when the PUR corresponding to the PUR configuration information performs data transmission based on the user plane, the PUR configuration information further includes one or more of the following information: a recovery identifier corresponding to the first target cell, the recovery identifier being used to identify the UE context saved by the network device to which the first target cell belongs for the UE; RRC configuration information of the first target cell; AS security configuration of the first target cell, the AS security configuration including the access layer key The next hop chain calculates one or more of the NCC and the security algorithm.

[0022] In this implementation, when the terminal device uses PUR data transmission based on the user plane, the PUR configuration information determined by the second network device also includes a recovery identifier of the target cell and security-related information. The recovery identifier is used by the network device corresponding to the target cell to obtain the UE context, and the security-related information is used to ensure security protection of user-plane-based data transmission between the terminal device and the target cell.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the recovery identifier includes a first part and a second part, the first part is used to identify the network device to which the first target cell belongs, and the second part is used to identify the UE context saved by the network device to which the first target cell belongs for the UE.

[0024] In combination with the first aspect, in certain implementations of the first aspect, the PUR configuration information corresponding to the one or more target cells includes: first uplink authorization information, which is the common uplink authorization information of the one or more target cells; or, at least one second uplink authorization information, which is the common uplink authorization information of at least one target cell managed by a network device; or, at least one third uplink authorization information, which is the uplink authorization information corresponding to one or more target cells.

[0025] In this implementation, the second network device can configure uplink authorization information of different granularities. Under different granularities, the air interface message overhead, storage overhead, etc. of the terminal device will be different.

[0026] In a second aspect, a communication method is provided, which can be performed by a communication device or a module (e.g., a chip or circuit, etc.) applied to the communication device. The communication device can be a terminal device in a method embodiment. The method can include: receiving a first message from a first network device, the first message including pre-configured uplink resource (PUR) configuration information corresponding to one or more target cells, where the one target cell is not a serving cell of a user equipment (UE); and sending uplink data on a valid PUR of a second target cell based on the PUR configuration information, where the second target cell is one of the one or more target cells.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the PUR corresponding to the PUR configuration information performs data transmission based on the user plane; and the first message further includes one or more of the following: a recovery identifier corresponding to the first target cell, the recovery identifier being used to identify the UE context saved by the network device to which the first target cell belongs for the UE; RRC configuration information of the first target cell; AS security configuration of the first target cell, the AS security configuration including the access layer key The next hop chain calculates one or more of the NCC and the security algorithm; the first target cell is one of the one or more target cells.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: sending a first verification token on the valid PUR of the second target cell, the first verification token being generated based on one or more of the following information of the second target cell: PUR RNTI, physical cell identifier, cell identifier.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the second target cell is one of the following cells: a cell reselected by the UE; a cell measured by the UE; or a cell where the UE resides.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the PUR configuration information corresponding to the one or more target cells includes: first uplink authorization information, the first uplink authorization information is the common uplink authorization information of the one or more target cells; or, at least one second uplink authorization information, the second uplink authorization information is the common uplink authorization information of at least one target cell managed by a network device; or, at least one third uplink authorization information, the third uplink authorization information is the uplink authorization information corresponding to one or more target cells.

[0031] In a third aspect, a communication method is provided, which can be performed by a communication device or a module (e.g., a chip or circuit) applied to the communication device. The communication device can be a second network device in a method embodiment. The method can include: receiving a second message, the second message including identification information of at least one target cell, the at least one target cell not being a serving cell of the UE; determining PUR configuration information corresponding to the at least one target cell; and sending a third message, the third message carrying the PUR configuration information corresponding to the at least one target cell.

[0032] In combination with the third aspect, in certain implementations of the third aspect, the second message also includes one or more of the following information: UE location information, PUR time domain information, and uplink authorization information, and the PUR time domain information includes at least one of period, offset, and number of times.

[0033] In combination with the third aspect, in some implementations of the third aspect, the PUR corresponding to the PUR configuration information performs data transmission based on the user plane; the second message also includes one or more of the following information: AS security information corresponding to the first target cell, the AS security information is used to determine the AS security key between the first target cell and the UE, and the AS security information includes an access layer key and the next hop chain to calculate the NCC; the security algorithm of the source cell; the security capability information of the UE, the security capability information of the UE indicating the security algorithms supported by the UE; the security algorithm includes an encryption algorithm and / or an integrity protection algorithm, and the first target cell is one of the one or more target cells.

[0034] In combination with the third aspect, in certain implementations of the third aspect, the PUR configuration information includes one or more of the following information: identification information of the first target cell, uplink authorization information of the first target cell, the TA corresponding to the first target cell, and the TA validity condition corresponding to the first target cell, where the first target cell is one of the at least one target cell.

[0035] In combination with the third aspect, in some implementations of the third aspect, the PUR corresponding to the PUR configuration information performs data transmission based on the user plane; the PUR configuration information also includes one or more of the following information: a recovery identifier corresponding to the first target cell, the recovery identifier being used to identify the UE context saved by the network device to which the first target cell belongs for the UE; RRC configuration information of the first target cell; AS security configuration of the first target cell, the AS security configuration including the access layer key The next hop chain calculates one or more of the NCC and the security algorithm.

[0036] In combination with the third aspect, in certain implementations of the third aspect, the recovery identifier includes a first part and a second part, the first part is used to identify the network device to which the first target cell belongs, and the second part is used to identify the UE context stored by the network device to which the first target cell belongs.

[0037] In combination with the third aspect, in certain implementations of the third aspect, the uplink authorization information includes one of the following: first uplink authorization information, the first uplink authorization information is uplink authorization information common to one or more target cells; or, second uplink authorization information, the second uplink authorization information is uplink authorization information common to the at least one target cell managed by the second network device; or, at least one third uplink authorization information, the third uplink authorization information is uplink authorization information corresponding to one or more target cells.

[0038] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving a first verification token from the UE; generating a second verification token based on one or more of the following information of the first target cell: PUR RNTI, physical cell identifier, cell identifier; and performing security verification on the UE based on the first verification token and the second verification token.

[0039] In a fourth aspect, a communication device is provided, wherein the communication device has the function of implementing the method of any one of aspects 1 to 3, or any possible implementation of any one of aspects 1 to 3. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-mentioned functions.

[0040] In a fifth aspect, a communication device is provided, comprising at least one processor, wherein the at least one processor is configured to cause the communication device to execute the method in the first aspect or any possible implementation thereof; or execute the method in the second aspect or any possible implementation thereof; or execute the method in the third aspect or any possible implementation thereof. Optionally, the at least one processor is coupled to at least one memory, the at least one memory being used to store a computer program or instruction, and the at least one processor being used to call and execute the computer program or instruction from the at least one memory, so that the communication device executes the method in the first aspect or any possible implementation thereof; or executes the method in the second aspect or any possible implementation thereof; or executes the method in the third aspect or any possible implementation thereof. The at least one processor may be included in the communication device or may be configured outside the communication device.

[0041] In a sixth aspect, a communication device is provided, comprising a communication interface and circuitry, wherein the communication interface is configured to receive information and / or data to be processed and transmit the information and / or data to the circuitry; the circuitry is configured to process the information and / or data to execute the method of any possible implementation of any one of aspects 1 to 3. Optionally, the communication interface is further configured to output the processed information and / or data.

[0042] In the seventh aspect, a computer-readable storage medium is provided, in which computer program code or instructions are stored. When the computer instructions are executed on a computer, the method in the first aspect or any possible implementation thereof is implemented; or, the method in the second aspect or any possible implementation thereof is implemented; or, the method in the third aspect or any possible implementation thereof is implemented.

[0043] In an eighth aspect, a computer program product is provided, comprising computer program code or instructions, which, when executed on a computer, enables the method of the first aspect or any possible implementation thereof to be implemented; or, the method of the second aspect or any possible implementation thereof to be implemented; or, the method of the third aspect or any possible implementation thereof to be implemented.

[0044] In a ninth aspect, a wireless communication system is provided, comprising a communication device according to any one of the first to third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 is a schematic flow chart of MO-EDT for control plane CIoT 5GS optimization.

[0046] Figure 2 is a schematic flow chart of MO-EDT for control plane CIoT 5GS optimization.

[0047] FIG3 is a schematic diagram of a PUR configuration request and a PUR configuration process.

[0048] FIG4 is a schematic diagram of transmission of control plane optimization performed by PUR.

[0049] FIG5 is a schematic diagram of PUR transmission for user plane optimization.

[0050] FIG6 is an architecture diagram of a communication system applicable to an embodiment of the present application.

[0051] FIG7 is a schematic flow chart of the communication method provided in this application.

[0052] FIG8 is an example of control plane PUR transmission provided in this application.

[0053] FIG9 is an example of user plane PUR transmission provided by the present application.

[0054] FIG10 is a schematic structural diagram of a communication device provided in this application.

[0055] FIG11 is a schematic structural diagram of another communication device provided in this application.

[0056] FIG12 is a schematic structural diagram of another communication device provided in this application. DETAILED DESCRIPTION

[0057] The technical solution in this application will be described below with reference to the accompanying drawings.

[0058] 1. EDT

[0059] Early data transmission (EDT) can be divided into mobile originated early data transmission (MO-EDT) and mobile terminated early data transmission (MT-EDT). The embodiments of the present application relate to MO-EDT. MO-EDT is triggered when the following conditions are met: 1) the upper layer or upper layer has requested to establish or resume an RRC connection for mobile originated data transmission; 2) the uplink data size is less than or equal to the TB size indicated in the system message.

[0060] (1) Control surface MO-EDT

[0061] The characteristics of control plane PEDT transmission are as follows: uplink user data is sent via NAS messages connected to RRC Early Data Request (RRC EDR) messages on the common control channel (CCCH); downlink user data can be transmitted via NAS messages connected to RRC Early Data Complete (RRC EDC) messages on the CCCH; and there is no need to switch to the RRC connected state for EDT transmission.

[0062] Figure 1 is a schematic flow chart of MO-EDT for control plane CIoT 5GS optimization.

[0063] 0. When the UE requests a mobile originated data connection, it initiates the MO-EDT procedure and selects the random access preamble configured for EDT. Mobile originated data comes from upper or higher layers.

[0064] 1. The UE sends an RRCEarlyDataRequest message and user data. In addition, the UE can instruct the access stratum (AS) to release auxiliary information.

[0065] 2. The ng-eNB initiates the Next Generation Access Protocol (NG-AP) Initial UE Message procedure to forward the NAS message. The (ng-)eNB can indicate in this procedure that this connection is triggered for EDT.

[0066] 3. The access and mobility management function (AMF) determines the PDU session contained in the NAS message.

[0067] 4.AMF sends the PDU session ID and uplink data to the session management function (SMF), and SMF forwards the uplink data to UPF.

[0068] 5. If there is downlink data, UPF forwards the downlink data to SMF, and SFM forwards the downlink data to AMF.

[0069] 6. If downlink data is received from the serving gateway (S-GW) or SMF, the AMF forwards the data to the ng-eNB via the DL NAS transfer procedure and may also indicate whether more data is expected. Otherwise, the AMF may trigger the connection establishment indication procedure and indicate whether further data is expected.

[0070] 7. If no further data is expected, the (ng-)eNB may send an RRC Early Data Complete message on CCCH to keep the UE in RRC_IDLE state. If downlink data is received in step 6, the downlink data is included in the RRC Early Data Complete message.

[0071] 8. Start the AN release process.

[0072] (2) User plane MO-EDT

[0073] User plane MO-EDT, which can be called user plane-based MO-EDT or MO-EDT using the user plane, has the following characteristics: the UE is in RRC_IDLE and there are valid PUR resources; the next hop chaining count (NCC) is provided to the UE in the RRCConnectionRelease message carrying the suspension indication; uplink user data is sent on the dedicated traffic channel (DTCH) multiplexed with the RRCConnectionResumeRequest message on the CCCH; downlink user data can be transmitted on the DTCH multiplexed with the RRCConnectionRelease message on the dedicated control channel (DCCH); the integrity key from the previous connection is used to calculate the short MAC-I as the authentication token of the RRCConnectionResumeRequest message; and uplink and downlink user data are encrypted. The key is derived based on the NCC provided in the RRCConnectionRelease message of the previous RRC connection; the RRCConnectionRelease message is integrity protected and encrypted using the newly derived key; there is no need to switch to the RRC connected state for PUR transmission.

[0074] Figure 2 is a schematic flowchart of MO-EDT for optimizing the control plane of the 5G system (5GS) for the consumer Internet of Things (CIoT).

[0075] 0. When the UE requests to resume mobile originated data, the UE initiates the MO-EDT procedure and selects the random access preamble configured for EDT.

[0076] 1. The UE sends an RRC Connection Resume Request (RRCConnectionResumeRequest) to the ng-eNB, including the UE's inactive radio network temporary identifier (I-RNTI), the reason for resumption, and the authentication token. The UE resumes all signaling radio bearers (SRBs) and data radio bearers (DRBs), derives new security keys using the NCC provided in the RRCConnectionRelease message of the previous connection, and re-establishes AS security. User data is encrypted and transmitted on the DTCH channel and multiplexed with the RRCConnectionResumeRequest message on the CCCH channel. The UE can instruct the AS to release auxiliary information.

[0077] 2. Uplink data is sent to UPF.

[0078] 3. The ng-eNB sends an NG-AP Context Resume Request message to the AMF to resume the connection. If the UE includes AS Release Assistance Information indicating no further UL / DL higher layer PDUs in step 1, the ng-eNB may request an immediate transition to RRC IDLE and suspend.

[0079] 4. If the AMF does not receive a request to immediately migrate to the suspended RRC IDLE in step 3, or the AMF knows that downlink data or signaling is suspended, the AMF requests the SMF to resume the PDU session.

[0080] 5.AMF sends an NG-AP Context Resume Response to the ng-eNB. If the AMF receives a request for immediate migration to RRC IDLE with Suspend in step 3 and there is no downlink data or signaling pending, the AMF includes a Suspend indication and keeps the UE in CM-IDLE with Suspend.

[0081] 6. If the AMF includes a Suspend indication in step 5, the ng-eNB proceeds to step 8. If the AMF does not include a Suspend indication in step 1, and the UE includes AS release assistance information indicating a single downlink data transmission only after an uplink transmission, the ng-eNB may wait for the DL data to arrive and proceed to step 7.

[0082] 7. The ng-eNB initiates the NG-AP UE Context Suspend procedure and notifies the AMF to suspend the RRC connection. The AMF requests the SMF to suspend the PDU session, and the SMF requests the UPF to release the tunnel information for the UE.

[0083] 8. The eNB sends an RRCConnectionRelease message to maintain the UE in the RRC_IDLE state. This message includes the releaseCause (rrc-Suspend), I-RNTI, NCC, and DRB-Continue ROHC, which the UE saved. If downlink data is received in step 6, it is encrypted and transmitted on the DTCH, which is multiplexed with the RRCConnectionRelease message on the DCCH. The process ends after receiving HARQ feedback (ARQ) confirming successful DL transmission.

[0084] 2. PUR

[0085] Preconfigured uplink resource (PUR): When in RRC_CONNECTED mode, the UE can request to configure a PUR or release a PUR configuration. The (ng-)eNB decides to configure a PUR based on the UE's request, the UE's subscription information, and / or local policy. A PUR is only valid in the cell in which the PUR configuration was received.

[0086] In the RRC_IDLE state, the PUR configuration is maintained. A PUR transmission is used when upper layers request the establishment or resumption of an RRC connection, the UE has a valid PUR, and the specified timing advance (TA) verification criteria are met. Transmission using a PUR allows a single uplink transmission from the RRC idle state (RRC_IDLE) using preconfigured uplink resources without performing a random access procedure. A transmission using a PUR is triggered when upper layers request the establishment or resumption of an RRC connection, the UE has a valid PUR for transmission, and the TA verification criteria are met.

[0087] FIG3 is a schematic diagram of a PUR configuration request and a PUR configuration process.

[0088] Step 0: The UE is in the RRC connected state and the cell enables PUR.

[0089] Step 1: The UE may indicate the PUR requirement to the (ng-)eNB by sending a PURConfigurationRequest message indicating the requested resource information (e.g., number of occurrences, period, time offset, TBS, RRC confirmation or Layer 1 ACK (L1ACK) preference, etc.). Alternatively, the UE may indicate to the (ng-)eNB in ​​the PURConfigurationRequest message to release the PUR configuration.

[0090] Step 2: When the (ng-)eNB moves the UE to RRC_IDLE, based on the previous UE PUR configuration request, subscription information and / or local policy, the (ng-)eNB may decide to provide PUR resources to the UE or release existing PUR resources. The (ng-)eNB includes the details of the PUR configuration or the PUR release indication in the RRCConnectionRelease message.

[0091] For UEs using control plane PUR transmission, the (ng-)eNB may provide the PUR configuration including the PUR configuration ID. When the UE establishes an RRC connection without using PUR resources, the PUR configuration ID(s) shall be included in the RRCConnectionSetupComplete message.

[0092] When the UE accesses another cell and the cell does not support PUR, or when the PUR resources are not used for a configured number of consecutive times, the UE and the (ng-)eNB may implicitly release the PUR configuration.

[0093] (1) Control surface PUR

[0094] The characteristics of control plane PUR transmission are as follows:

[0095] -Use PUR resources to send uplink user data on CCCH via NAS messages connected to RRC EarlyDataRequest messages;

[0096] - If there is no downlink data, the (ng-)eNB may terminate the procedure by sending a Layer 1 acknowledgment, a MAC Timing Advance Command, and an RRCEarlyDataComplete message without user data;

[0097] - Downlink user data can be transmitted on CCCH using the NAS message attached to the RRC EarlyDataComplete message;

[0098] - No need to switch to RRC connected state for PUR transmission.

[0099] FIG4 is a schematic diagram of transmission of control plane optimization performed by PUR.

[0100] Step 0: The UE determines whether the PUR resources are valid, for example, whether the PUR is used in the cell, and whether the timing advance is valid.

[0101] Step 1: The UE sends an RRC EarlyDataRequest on the PUR resources instead of the resources allocated in the random access response. If the uplink data is too large to be included in the RRC EarlyDataRequest, the UE can send an RRCConnectionRequest using the PUR resources. This process will fall back to the traditional RRC connection establishment process and a new C-RNTI can be allocated.

[0102] After step 1, the (ng-)eNB may request the UE to suspend transmission using the PUR by sending a Layer 1 Fallback Indication. UE actions after receiving the Layer 1 Fallback Indication are performed by the UE.

[0103] Steps 2 to 6: The MO-EDT optimized for the control plane CIoT 5GS in Figure 1 is not described in detail here.

[0104] Step 7a: If the (ng-)eNB realizes that there is no pending downlink data or signaling, the (ng-)eNB may send an L1ACK to the UE, optionally including a timing advance adjustment, to update the TA and terminate the procedure.

[0105] Step 7b: If the (ng-)eNB realizes that there is no further data or signaling, the (ng-)eNB may send a timing advance command to update the TA and terminate the procedure.

[0106] Step 7c: Same as step 7 of the control plane CIoT 5GS optimization in MO-EDT in Figure 1, but may also include a timing advance command.

[0107] (2) User plane PUR

[0108] The user plane PUR, which can be called a user plane-based PUR or a user plane-using PUR, has the following characteristics:

[0109] -The UE is in RRC_IDLE and there are valid PUR resources;

[0110] -Provide the Next Hop Chaining Count (NCC) to the UE in the RRCConnectionRelease message carrying the suspend indication;

[0111] -Uplink user data is sent on the DTCH multiplexed with the RRCConnectionResumeRequest message on the CCCH;

[0112] - Downlink user data can be transmitted on the DTCH multiplexed with the RRCConnectionRelease message on the DCCH;

[0113] - Encrypt uplink and downlink user data. The key is derived based on the NCC provided in the RRCConnectionRelease message of the previous RRC connection;

[0114] -Integrity protection and encryption of the RRCConnectionRelease message using the newly derived keys;

[0115] - No need to switch to RRC connected state for PUR transmission.

[0116] FIG5 is a schematic diagram of PUR transmission for user plane optimization.

[0117] Step 1: The UE confirms that the PUR resources are valid, for example, PUR is enabled in the cell, time alignment is valid, etc.

[0118] Step 1: Send the RRCConnectionResumeRequest message on the PUR resources, not on the resources allocated in the random access response.

[0119] If the user data is too large to be completely contained in the transmission using PUR, the UE can use PUR to transmit RRCConnectionResumeRequest and a piece of user data. This process will fall back to the traditional RRC connection resumption process; a new C-RNTI can be allocated.

[0120] After step 1, the (ng-)eNB may request the UE to suspend transmission using the PUR by sending a layer 1 fallback indication. The actions of the UE after receiving the layer 1 fallback indication are performed by the UE.

[0121] Steps 2 to 7 are the same as the user plane CIoT 5GS optimization in MO-EDT in Figure 2 and are not repeated here.

[0122] Step 8: Same as step 8 in MO-EDT optimized for user plane 5GS in Figure 2, except that a timing advance command may also be included.

[0123] In the NTN scenario, due to the rapid change of serving cells and discontinuous coverage, PUR resources are unavailable after the cell change and cannot support UE to perform PUR transmission.

[0124] To address this issue, the present application provides a communication method that can ensure that after a UE's serving cell is changed, the new serving cell is configured with an available PUR to support the UE in transmitting the PUR.

[0125] The technical solution provided by this application is introduced below.

[0126] Figure 6 is an architectural diagram of a communication system applicable to an embodiment of the present application. As shown, the communication system includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (such as 110a and 110b in Figure 4, collectively referred to as 110) and at least one terminal device (such as 120a-120j in Figure 1, collectively referred to as 120). The RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 4). The terminal device 120 is connected to the RAN node 110 wirelessly. The RAN node 110 is connected to the core network 200 wirelessly or by wire. The core network devices in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or they can be the same physical device that integrates the core network logical functions and the radio access network logical functions.

[0127] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, a non-terrestrial network (NTN) system, or a future-oriented evolutionary system. The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems.

[0128] In addition, when the RAN 100 in the embodiment of the present application is an NTN system, the RAN 100 can be in transparent transmission mode or regeneration mode, an earth fixed cell (quasi-earth fixed) or an earth moving cell.

[0129] FIG7 is a schematic flow chart of the communication method provided in this application.

[0130] 210. The first network device determines one or more target cells.

[0131] If the first network device determines a target cell, the target cell is not the serving cell of the UE. If the first network device determines multiple target cells, the multiple target cells may include but not include the serving cell of the UE. The first network device refers to the access network device of the source cell of the UE, which may also be called the source base station.

[0132] 220. The first network device sends a first message to the UE.

[0133] The UE receives a first message from a first network device.

[0134] The first message includes the PUR configuration information corresponding to the one or more target cells. If there are multiple target cells, the first message may include the PUR configuration information of each of the one or more target cells. Alternatively, the first message may also include one or more PUR configuration information, each PUR configuration information corresponding to one or more target cells, that is, the PUR configuration information is universal (the same) for one or more target cells, and the one or more target cells corresponding to the PUR configuration information can be indicated by the cell identification information. In other words, the PUR configuration information of the one or more target cells can be sent through one or more messages, and the first message here can be one or more messages.

[0135] Optionally, method 200 may further include step 230 .

[0136] 230. Send uplink data on a valid PUR of a second target cell based on the PUR configuration information corresponding to the one or more target cells. The second target cell is one of the one or more target cells. It should be understood that in the embodiment, both the first target cell and the second target cell are one of the one or more target cells. Furthermore, the second target cell generally refers to a cell from which the UE initiates PUR transmission.

[0137] After receiving the first message, the UE can obtain the PUR configuration information of each of the one or more target cells, or the PUR configuration information shared by the one or more target cells. Subsequently, the UE can send uplink data on the PUR of any one of the one or more target cells as needed. The PUR of the second target cell is determined based on the PUR configuration information corresponding to the second target cell.

[0138] During soft satellite handover and hard satellite handover, multiple satellites (cells supported by satellites) in the earth fixed cell (quasi-Earth fixed) scenario have the same (synchronization signal and PBCH block, SSB) frequency and the same gNB, supporting the resynchronization process during satellite handover. Specifically, multiple satellites maintain the same PCI in the geographical area covered by the earth fixed cell beam. The resynchronization process during satellite handover avoids the UE's L3 mobility, such as the UE's L3 mobility requires a dedicated RRC message to indicate the UE handover. For soft satellite handover, the UE can start synchronizing with the target satellite before the source satellite stops serving the cell. When the UE switches to the target satellite, it is not required to be connected to the source satellite. For a UE in a non-RRC connected state (such as an RRC idle state or an RRC inactive state), since the PCIs of multiple cells have not changed, the first message may include PUR configuration information and the corresponding one or more target cells. The UE may obtain downlink synchronization of the new satellite (cell) between the service start time of the target satellite service and the service stop time of the current cell, or may obtain downlink synchronization of the new satellite (cell) at or before the service stop time indicated by the serving cell. The UE still uses the PUR configuration information of the cell, that is, the UE believes that the PUR resource is still valid in the new cell.

[0139] In an embodiment of the present application, the UE obtains the PUR configuration information of one or more target cells from the access network device (i.e., the first network device) of the serving cell. After the UE leaves the serving cell, the UE can send uplink data according to the PUR configuration information of the new cell (i.e., the second target cell), specifically, the uplink data is sent on the valid PUR indicated by the PUR configuration information of the new cell. The new cell is one of the one or more target cells, which can be a cell measured by the UE, or a cell reselected by the UE, or a cell where the UE resides. Therefore, in the NTN scenario, even if the serving cell of the UE changes frequently, after the serving cell of the UE changes, when the PUR configuration of the source cell is unavailable, since the UE has obtained the PUR configuration information of the new cell in advance, uplink data transmission can be performed on the valid PUR resources indicated by the PUR configuration information of the new cell.

[0140] Optionally, before step 220 , method 200 may further include steps 240 to 250 .

[0141] 240. The first network device sends a second message to the second network device, where the second message includes identification information of at least one target cell.

[0142] Correspondingly, the second network device receives the second message from the first network device.

[0143] 250. The second network device sends a third message to the first network device, where the third message includes PUR configuration information corresponding to the at least one target cell.

[0144] In the embodiments of the present application, the second network device refers to the access network device of the target cell, which may also be referred to as the target base station. Furthermore, in method 200, a single second network device is used as an example for description. When multiple second network devices are involved, the interaction between each second network device and the first network device is similar, and reference may be made to the description of the single second network device described in method 200.

[0145] In addition, as described in step 210, the first network device may determine one or more target cells. In combination with step 240 and step 250, the following possible situations are involved:

[0146] 1) The first network device determines a target cell (e.g., target cell a), which corresponds to network device A. In step 240, the first network device sends a second message to network device A, where the second message includes identification information of target cell a. In step 250, network device A sends a third message to the first network device, where the third message includes PUR configuration information corresponding to target cell a.

[0147] 2) The first network device determines multiple target cells, which correspond to network device A. In step 240, the first network device sends a second message to network device A, where the second message includes identification information of each of the multiple target cells. In step 250, network device A sends a third message to the first network device, where the third message includes PUR configuration information corresponding to the multiple target cells.

[0148] 3) The first network device determines multiple target cells (e.g., target cells a, b, and c), assuming that target cell a corresponds to network device A, and target cells b and c correspond to network device B. In step 240, the first network device sends a second message to network device A, the second message including identification information of target cell a; in addition, the first network device sends a second message to network device B, the second message including identification information of target cell b and identification information of target cell c. In step 250, network device A sends a third message to the first network device, the third message including PUR configuration information of target cell a; in addition, network device B sends a third message to the first network device, the third message including PUR configuration information corresponding to target cell b and target cell c. This can be PUR configuration information for each cell, or one PUR configuration information corresponding to multiple target cells.

[0149] In the above examples, network device A or network device B is an example of a second network device. Therefore, in method 200, the second network device refers to a specific second network device. In each embodiment of the present application, a second network device is used as an example to illustrate the interaction between the second network device and the first network device / UE.

[0150] In addition, as can be seen from the above example, for a specific second network device (e.g., network device A or network device B in the above example), upon receiving the second message from the first network device, the second message includes the identifier of at least one target cell among the one or more target cells determined by the first network device. In other words, the at least one target cell is managed by the specific second network device.

[0151] In an embodiment of the present application, the UE obtains the PUR configuration information of one or more target cells from the access network device of the serving cell. After the UE leaves the serving cell, the UE can send uplink data according to the PUR configuration information of the new cell, specifically, the uplink data is sent on the valid PUR indicated by the PUR configuration information of the new cell. The new cell is one of the one or more target cells, which can be a cell measured by the UE, or a cell reselected by the UE, or a cell where the UE resides. It can be seen that in the NTN scenario, the UE's serving cell changes frequently. In the scenario where the PUR configuration of the source cell is unavailable, since the UE obtains the PUR configuration information of the new cell in advance, uplink data transmission can be performed based on the PUR configuration of the new cell.

[0152] The technical solutions provided in this application can be applied to scenarios where PUR is used for control plane transmission and PUR is used for user plane transmission, which are described in detail below.

[0153] Example 1

[0154] PUR for control surface transmission

[0155] FIG8 is an example of control plane PUR transmission provided in this application.

[0156] 601. A first network device determines one or more target cells.

[0157] As an example, step 601 may include the following two implementations.

[0158] Implementation 1

[0159] The first network device obtains PUR requirement information from the UE, where the PUR requirement information includes PUR time domain information requested by the UE, and the PUR time domain information includes at least one of a number, a period, and a transport block size (TBS) information. The first network device determines, based on the PUR requirement information and the cells to be covered, the one or more target cells for configuring the PUR for the UE.

[0160] Implementation 2

[0161] The first network device obtains identification information of the one or more target cells from the UE, and determines the one or more target cells according to the identification information of the one or more target cells.

[0162] For example, the UE determines one or more target cells for configuring a PUR for the UE based on the service stop time (t-service) information of system information block type 31 (SystemInformationBlockType31, SIB31), system information block type 32 (SystemInformationBlockType32, SIB32), and system information block type 3 (SystemInformationBlockType3, SIB3), and indicates the identification information of the one or more target cells to the first network device.

[0163] Among them, system information block type 31 contains satellite assistance information corresponding to the service cell, and system information block type 32 contains satellite assistance information for discontinuous coverage prediction. Satellite assistance information may include one or more of satellite footprint information, satellite service information, satellite identification, satellite frequency information, etc. Satellite footprint information is used to indicate the coverage range provided by the satellite cell, such as indicating the elevation angle range and / or radius of the earth moving cell, indicating the reference point and radius of the quasi-earth fixed cell, and the radius is the distance between the coverage edge and the reference point. Satellite service information indicates the time information when the satellite provides coverage, such as indicating the ephemeris parameters of the earth moving cell to estimate the time from entering coverage to leaving coverage, indicating one or more of the service start time of the quasi-earth fixed satellite cell; the t-service information of system information block type 3 indicates the time information when the NTN quasi-earth fixed cell will stop serving the current coverage area.

[0164] 602. The first network device sends a second message to the second network device, where the second message includes identification information of at least one target cell.

[0165] In addition, optionally, the second message further includes one or more of the following information:

[0166] Uplink authorization information, UE location information, PUR time domain information.

[0167] Optionally, if the one or more target cells correspond to multiple second network devices, in step 602, the uplink authorization information sent by the first network device to the multiple second network devices may include the following possible implementations:

[0168] The first network device indicates the same uplink grant information (e.g., first uplink grant information) to the multiple second network devices as a common uplink grant between the multiple stations. That is, the first grant information corresponds to the one or more target cells determined by the first network device, and the first grant information is common (the same) to the multiple second network devices; or

[0169] The first network device indicates a piece of uplink authorization information to each second network device, where the piece of uplink authorization information (for example, second uplink authorization information) corresponds to at least one target cell managed by each second network device, that is, the second uplink authorization information is for at least one target cell managed by each second network device; or

[0170] The first network device sends uplink authorization information corresponding to the one or more target cells (for example, called third uplink authorization information), that is, the one or more target cells determined by the first network device respectively correspond to one piece of third uplink authorization information.

[0171] Therefore, each target cell may correspond to one uplink authorization information, or the first network device may send one or more uplink authorization information, and each authorization information may correspond to multiple target cells.

[0172] Alternatively, the second message does not include the uplink authorization information, or in other words, the first network device does not indicate the uplink authorization information to the second network device, and the second network device determines the uplink authorization information for the UE.

[0173] The uplink authorization information indicates the uplink authorization parameters used by the UE for PUR transmission, such as the authorized channel element mode (CE mode), the DCI field of the number of physical uplink shared channel (PUSCH) resource units, the downlink control information (DCI) field of the PUSCH physical resource block (PRB) allocation, the DCI field of the PUSCH modulation and coding mode, and the DCI field of the number of PUSCH repetitions.

[0174] The location information of the UE may be coarse-grained or fine-grained location information.

[0175] The identification information of the target cell may include one or more of the following: the cell global identifier (CGI), physical cell identifier (PCI) and frequency, physical cell identifier (PCI), cell identifier (cell ID), non-public network identifier (NPN ID), non-terrestrial network identifier (NTN ID), or other cell identifiers. The CGI may include a public land mobile network identifier (PLMN ID), a Cell ID, and a tracking area (TA).

[0176] Optionally, if there is an X2 interface, the first network device directly sends the second message to the second network device; if there is no X2 interface, the first network device may send the second message to the second network device through the core network.

[0177] 603. The second network device sends a third message to the first network device, where the third message includes PUR configuration information corresponding to at least one target cell. The third message may include PUR configuration information for one or more target cells; alternatively, the third message may include one or more PUR configuration information, each PUR configuration information corresponding to one or more target cells. That is, the PUR configuration information is common (the same) to the one or more target cells, and the one or more target cells corresponding to the PUR configuration information may be indicated by cell identification information.

[0178] The PUR configuration information may include one or more of the following:

[0179] Uplink authorization information, TA, and TA validity conditions. Taking the first target cell as an example, the PUR configuration information may include one or more of the uplink authorization information of the first target cell, the TA of the first target cell, and the TA validity conditions of the first target cell. For a second network device, the first target cell here is one of the at least one target cell corresponding to the second network device.

[0180] It should be understood that when the multiple target cells determined by the first network device correspond to multiple second network devices, each second network device sends the PUR configuration information of at least one corresponding target cell to the first network device, so that the first network device obtains the PUR configuration information of each of the multiple target cells. When the first network device determines a target cell, the first target cell is the target cell. The target cell is not the source cell of the UE.

[0181] Therefore, each second network device sends the PUR configuration information corresponding to the at least one target cell corresponding to the second network device to the first network device.

[0182] Optionally, if the first network device does not indicate the uplink authorization information to the second network device in step 602, the third message further includes uplink authorization information configured by the second network device for the UE.

[0183] Similar to the uplink authorization information carried by the second message in step 602, the uplink authorization information carried by the third message may include the following implementations:

[0184] (1) first uplink authorization information, where the first uplink authorization information is common uplink authorization information for the one or more target cells, that is, the one or more target cells determined by the first network device are configured with the same first uplink authorization information, or,

[0185] (2) at least one second uplink authorization information, where the second uplink authorization information is common uplink authorization information of the at least one target cell corresponding to a second network device, that is, the at least one target cell corresponding to each second network device corresponds to the same second uplink authorization information; or

[0186] (3) at least one third uplink authorization information, where the third uplink authorization information is uplink authorization information corresponding to one or more target cells, that is, among the one or more target cells determined by the second network device, each target cell may correspond to one third authorization information, or one third authorization information may correspond to multiple target cells.

[0187] The third message may further indicate the correspondence between the uplink authorization information and the target cell, for example, the correspondence may be indicated by indicating an identifier of the target cell, a PUR configuration information ID or a PUR-RNTI.

[0188] In implementation (1), the uplink authorization information is a common uplink authorization between multiple second network devices, and the PUR configuration information corresponding to the one or more target cells indicates a common uplink authorization. For the case where the first network device determines multiple target cells, the "common" means that it is applicable to the multiple target cells; in implementation (2), for the case where the first network device determines multiple target cells (assuming it is called a set A of target cells), one or more target cells under the second network device (a subset of set A, for example, called subset a, which can include multiple target cells) can share an uplink authorization, for example, the multiple target cells included in subset a can correspond to a certain second network device (for example, multiple target cells managed by a second network device), or can correspond to at least two second network devices (that is, a set of target cells managed by the at least two second network devices), the multiple target cells included in set A can be configured with an uplink authorization information set, and one uplink authorization information in the uplink authorization information set corresponds to the multiple target cells included in subset a. In implementation (3), for the one or more target cells determined by the first network device, each target cell corresponds to an uplink authorization information.

[0189] In addition, the TA and TA validity conditions of the first target cell may be determined by the second network device based on the UE's location information and indicated to the UE, or may not be determined or indicated by the second network device, that is, the UE determines the TA by itself to ensure that the TA is valid. In this implementation, the PUR configuration information does not include the TA and TA validity conditions of the first target cell. Among them, the TA validity conditions may include one or more of the time alignment timer (TAT) configuration, the reference signal receiving power (RSRP) change threshold, the RSRP threshold, and the data volume threshold.

[0190] In addition, the PUR configuration information of the first target cell may further include one or more of an identifier of the first target cell, a PUR configuration identifier (identifier, ID), a PUR-radio network temporary identifier (RNTI), the number of PUR opportunities, the offset of the PUR opportunity, the period of the PUR opportunity, the number of consecutive PUR opportunities that can be skipped before implicitly releasing the PUR, and the PUR search space configuration. The second network device may determine the PUR time domain information of the first target cell based on the time when the first target cell serves the UE, such as one or more of the offset of the PUR opportunity, the period of the PUR opportunity, and the number of PUR opportunities.

[0191] Based on steps 601 to 603 above, the first network device obtains the PUR configuration information of the one or more target cells from the second network device.

[0192] Optionally, after indicating the PUR configuration information of the target cell to the first network device, the second network device may further send a message to the first network device to cancel or modify the prepared PUR configuration information of the target cell.

[0193] 604. The first network device indicates the PUR configuration information corresponding to the one or more target cells to the UE.

[0194] The implementation form of the first network device indicating the PUR configuration information corresponding to the one or more target cells to the UE may be that the first network device indicates the PUR configuration information of each of the one or more target cells; or, the first network device sends one or more PUR configuration information, each PUR configuration information corresponds to one or more target cells, that is, the PUR configuration information is common (the same) for one or more target cells, and the cell identification information can be used to indicate the one or more target cells corresponding to the PUR configuration information.

[0195] Optionally, the PUR configuration information corresponding to the one or more target cells also includes uplink authorization information of the one or more target cells. As an example, the PUR configuration information corresponding to the one or more target cells indicates the correspondence between the uplink authorization information and the one or more target cells. For example, the uplink authorization information and the target cell can be associated by indicating an identifier of the target cell, a PUR configuration information ID, or a PUR-RNTI. Each uplink authorization information is configured for the corresponding target cell.

[0196] The uplink authorization information sent by the first network device to the UE can be implemented in the three specific ways as described in the above step 603. For example, the uplink authorization information can be the first uplink authorization information, at least one second uplink authorization information or at least one third uplink authorization information. Please refer to the description in step 603 for details and will not be repeated here.

[0197] It should be understood that the first network device can indicate the PUR configuration information corresponding to the one or more target cells by sending an RRC Connection Release (RRCConnectionRelease) message to the UE, and the one or more target cells in step 604 refer to the one or more target cells determined by the first network device in step 601.

[0198] Correspondingly, the UE enters the RRC idle state and saves the PUR configuration information corresponding to the one or more target cells, that is, the PUR configuration information of each of the one or more target cells.

[0199] Subsequently, if the UE has an uplink data transmission requirement and determines that the new cell is configured with a valid PUR, the UE may send uplink data on the valid PUR of the new cell, as in step 605 .

[0200] 605. Optionally, when the UE determines that the new cell is configured with a valid PUR, the UE transmits the PUR on the valid PUR of the new cell.

[0201] The new cell can be a cell measured by the UE, a reselected cell, or a cell the UE is residing in. The new cell is one of the one or more target cells. If a PUR is configured for the new cell and the TA of the new cell is valid, the UE sends an RRC EDR message using control plane transmission on the valid PUR of the new cell. The RRC EDR message carries uplink data.

[0202] 606. Optionally, the UE receives an L1ACK, a time advance command, or an RRC early data complete (EDC) message that does not carry downlink data from the first network device.

[0203] The UE receives an L1ACK, a timing advance command, or an RRC EDC message that does not carry downlink data, which instructs the UE to end PUR transmission.

[0204] In Example 1, in the NTN scenario, the serving cell changes frequently. When the UE leaves the serving cell configured with a PUR, it obtains the PUR configuration information of the new cell in advance, and thus can initiate control plane transmission on the PUR configured in the new cell. This allows the UE to perform data transmission in the new cell without random access, achieving PRACH-free EDT, reducing air interface signaling transmission, and improving the network's uplink capacity.

[0205] Example 2

[0206] PUR is used for user plane transmission

[0207] FIG9 is an example of user plane PUR transmission provided by the present application.

[0208] 701. A first network device determines one or more target cells.

[0209] Similar to step 601, the first network device can determine the one or more target cells in two implementation methods: 1) the first network device obtains PUR demand information from the UE, and determines the one or more target cells for configuring PUR for the UE based on the PUR demand information and the cells to be covered; 2) the UE determines the one or more target cells based on the PUR demand information, and sends the identification information of the one or more target cells to the first network device; the first network device determines the one or more target cells based on the identification information of the one or more target cells.

[0210] 702. The first network device sends a second message to the second network device, where the second message includes identification information of at least one target cell.

[0211] Similar to Example 1, Example 2 also uses a second network device as an example for description. When multiple target cells are involved, and the multiple target cells correspond to multiple second network devices, the interaction between each second network device and the first network device can refer to the description of this second network device.

[0212] In addition, optionally, the second message further includes one or more of the following information: uplink authorization information, UE location information, and PUR time domain information. For this information, please refer to the description in step 602 and will not be repeated here.

[0213] Different from the case where the PUR uses the control plane mode for data transmission, if the PUR uses the user plane mode for data transmission, the second message also includes one or more of the following information:

[0214] The AS security information corresponding to the first target cell, the security algorithm of the source cell, and the security capability of the UE.

[0215] The first target cell is one of the at least one target cell corresponding to the second network device, or in other words, the first target cell is a representative of the target cells, and the one or more target cells are described as an example.

[0216] The AS security information of the first target cell is used to determine the AS security key between the first target cell and the UE; the AS security information includes the access layer key and one or more of the next hop chain counter (NCC). The UE's security capability information is used to indicate the security algorithms supported by the UE, where the security algorithms include encryption algorithms and / or integrity protection algorithms.

[0217] PUR requirement indicates the identification information, security information and uplink authorization information of the target cell.

[0218] The security information may include one or more of the AS security information corresponding to the target cell, the security algorithm of the source cell, and the security capability information of the UE. (Access Stratum Key) and Next Hop Chaining Count (NCC) are used to generate the key for AS security between the target cell and the UE, where the NCC calculates the access stratum key of the first target cell for the first network device The NCC used, the first network device derives the access layer key of the first target cell based on the PCI, downlink frequency, and NCC of the first target cell The first network device determines the vertical or horizontal key derivation method based on whether there is an unused NCC. The first target cell (the second network device corresponding to the first target cell) uses One or more of the following are derived: a new RRC signaling integrity protection key (KRRCint), an RRC signaling encryption key (KRRCenc), a user plane integrity protection key (KUPint), and a user plane encryption key (KUPenc). The second network device may be the first network device or another device other than the first network device.

[0219] Optionally, the first network device sends the second message to the second network device through an X2 interface; or, the first network device may send the second message to the second network device through a core network.

[0220] 703. The second network device sends a third message to the first network device, where the third message includes PUR configuration information corresponding to at least one target cell. The third message may include PUR configuration information for each of the one or more target cells, or the third message may include one or more PUR configuration information, where each PUR configuration information corresponds to one or more target cells, i.e., the PUR configuration information is common (the same) to the one or more target cells, and the one or more target cells corresponding to the PUR configuration information may be indicated by cell identification information.

[0221] The PUR configuration information may include one or more of the following information:

[0222] Uplink authorization information, TA, and TA validity conditions.

[0223] Taking the first target cell as an example, the PUR configuration information may include one or more of the uplink authorization information of the first target cell, the TA of the first target cell, and the TA validity condition of the first target cell. For a second network device, the first target cell here is one of the at least one target cell corresponding to the second network device. For this information, please refer to the description in step 603 and will not be repeated here.

[0224] In addition, unlike the PUR data transmission based on the control plane, if the PUR data transmission is based on the user plane, the PUR configuration information also includes one or more of the following information:

[0225] The resume identifier (resume ID) corresponding to the first target cell, the identifier of the first target cell, the RRC configuration information of the first target cell, and the AS security configuration of the first target cell.

[0226] The resume ID of the first target cell is used to identify the UE context stored for the UE by the second network device corresponding to the first target cell. The AS security context is included in the UE context. The resume ID can consist of two parts, or it can include only the first part or the second part. As an example, the resume ID includes a first part and a second part, wherein the first part is used to identify the second network device corresponding to the first target cell, and the second part is used to identify the UE context established or stored for the UE by the second network device corresponding to the first target cell. For example, the resume ID is a 40-bit field, 20 bits of which are used to identify the ID of the second network device (assuming it is network device A) in the first target cell, and the other 20 bits are used to identify the UE context of the UE stored by network device AB. For another example, the resume ID is a 24-bit field, 12 bits of which are used to identify / index to the ID of network device A, and the other 12 bits are used to identify the UE context stored for the UE by network device A. Optionally, the first part and the second part can be two fields, or two parts of a field, respectively, without limitation. As another example, the resume ID consists of a single field, which is used to identify the ID of network device A. Combined with other information, the UE context stored by network device A for the UE can be determined.

[0227] The RRC configuration information may include parameters such as signaling radio bearer (SRB) or data radio bearer (DRB) configuration. In addition, the RRC configuration may not include a mobility control information (MobilityControlInfo) information element or a synchronization reconfiguration (ReconfigurationWithSync) information element, because the mobility control information element or the synchronization reconfiguration information element is used to instruct the UE to perform uplink synchronization. The UE may perform uplink synchronization in the following possible ways: one way is for the UE to calculate the timing advance (TA) value on its own; the other way is for the UE to initiate random access to obtain the TA value. Since the TA value of the first target cell may be included in the PUR configuration, the UE can use the TA value in the PUR configuration corresponding to the first target cell.

[0228] The AS security configuration of the first target cell may include One or more of the NCC and security algorithms. The AS security configuration of the first target cell includes at least and / or NCC. When the AS security configuration of the first target cell does not include When the UE saves the AS security context of the source cell, including the source cell's One or more of the NCC and security algorithms, based on the source cell The target cell PCI, target cell frequency, and the first target cell NCC are used to derive the first target cell The UE compares the saved NCC with the NCC of the first target cell to determine whether it is different to determine the horizontal or vertical key derivation method. If the AS security configuration of the first target cell does not include NCC, the UE directly uses the NCC corresponding to the first target cell.

[0229] In addition, optionally, the PUR configuration information may further include one or more of the following:

[0230] Cell ID, PUR configuration ID, PUR-RNTI, number of PUR opportunities, PUR opportunity offset, PUR opportunity period, number of consecutive PUR opportunities that can be skipped before implicitly releasing the PUR, and PUR search space configuration.

[0231] In addition, the second network device may send a message to the first network device to cancel or modify the prepared PUR configuration information of the target cell.

[0232] 704. The first network device indicates the PUR configuration information corresponding to the one or more target cells to the UE. Accordingly, the UE enters the RRC idle state and retains the PUR configuration information corresponding to the one or more target cells.

[0233] In step 704, the first network device indicates the PUR configuration information corresponding to the one or more target cells to the UE, which may be as described in step 603. In addition, in the user plane-based transmission, the PUR configuration information of the target cell also includes security-related information.

[0234] Taking the first target cell as an example of the one or more target cells, the PUR configuration information of the first target cell may also include one or more items of the resume identifier (resume ID), RRC configuration information, and AS security configuration of the first target cell.

[0235] The UE receives the PUR configuration information corresponding to the one or more target cells. Taking the first target cell as one of the one or more target cells as an example, the UE applies the RRC configuration of the first target cell and the AS security configuration of the first target cell to obtain the PUR configuration information of the first target cell. The order in which the UE applies the RRC configuration and the AS security configuration of the first target cell is not restricted. The UE generates a verification token based on one or more of the PUR RNTI, physical cell identifier, and cell identifier in the information of the first target cell. It is hereinafter referred to as the first verification token. The first verification token is used by the second network device corresponding to the first target cell to perform security verification on the identity of the UE. Alternatively, the UE saves the UE context of the source cell and generates a verification token based on one or more of the C-RNTI, source cell PCI, and cell identifier of the first target cell used in the source cell, wherein the source cell is the serving cell of the UE before entering the RRC idle state, that is, the cell that sends the RRC connection release message. Correspondingly, when the first network device sends the second message to the second network device, the second message includes the C-RNTI and PCI of the source cell.

[0236] As an example, the first network device may send an RRC release message to the UE to indicate the PUR configuration information corresponding to the one or more target cells.

[0237] 705. Optionally, when the UE determines that the new cell is configured with a valid PUR, the UE transmits the PUR in the new cell.

[0238] The UE sends the uplink data and the first verification token in a user plane transmission manner on the valid PUR of the new cell. For example, the UE sends an RRCConnectionResume message, and the RRCConnectionResume message carries the uplink data and the first verification token.

[0239] Accordingly, the second network device determines the UE context of the UE according to the resume ID, and then obtains the AS security context contained in the UE context. The AS security context may include the AS security context corresponding to the first target cell. NCC, one or more security algorithms. The second network device generates a second verification token based on one or more of the PUR RNTI, physical cell identifier, and cell identifier corresponding to the first target cell, and compares it with the received first verification token. If the two are the same, the security verification of the UE passes, otherwise it fails. Alternatively, the UE context includes the C-RNTI and PCI of the source cell. The second network device generates a second verification token based on the C-RNTI and PCI of the source cell and the cell identifier of the first target cell, and compares it with the received first verification token.

[0240] 706. The UE receives an RRC connection release message from the first network device.

[0241] In Example 2, in the NTN scenario, the serving cell changes frequently. When the UE leaves the cell configured with the PUR, it obtains the PUR configuration information of the new cell in advance, and can initiate user-plane-based transmission on the PUR configured in the new cell. This allows the UE to perform data transmission in the new cell without random access, achieving PRACH-free EDT, reducing air interface signaling transmission and improving the network's uplink capacity.

[0242] The communication method provided by this application has been described in detail above. The communication device provided by this application is introduced below.

[0243] See FIG10 , which is a schematic structural diagram of a communication device provided in this application.

[0244] As shown in Figure 10, a communication device 1000 includes a processing module 1001 and a communication module 1002. The communication device 1000 can be a communication device, or a device applied to a communication device and capable of implementing the corresponding functions of the communication device, such as a chip, a chip system, or a circuit. For example, the communication device can be a network device (such as an access network device) or a terminal device.

[0245] The communication module may also be a transceiver module, a transceiver, a transceiver, or a transceiver device. The processing module may also be a processor, a processing board, a processing unit, or a processing device. Optionally, the communication module is used to perform the sending and receiving operations of the network device (e.g., the first network device or the second network device) or the terminal device in any method embodiment. The device used to implement the receiving function in the communication module can be regarded as a receiving unit, and the device used to implement the sending function in the communication module can be regarded as a sending unit, that is, the communication module includes a receiving unit and a sending unit. For example, in Figure 7, if the communication device corresponds to the first network device, the communication module can be used to perform the sending operation in step 240, the receiving operation in step 250, and the sending operation in step 220; if the communication device corresponds to the second network device, the communication module can be used to perform the receiving operation in step 240 and the sending operation in step 250; if the communication device corresponds to the UE, the communication module can be used to perform the receiving operation in step 220. The processing module is used to perform operations / processing related to the internal implementation of the network device or terminal device in any method embodiment. For example, in Figure 7 , if the communication device corresponds to a first network device, the processing module may be configured to execute step 210; if the communication device corresponds to a UE, the processing module may be configured to execute step 230. If the communication device corresponds to a second network device, the processing module may be configured to configure PUR configuration information for the at least one target cell based on the PUR requirement information from the first network device and the identification information of the at least one target cell (not shown in Figure 7 ). It should be understood that the specific operations of each module can be referred to the description in the method embodiment and will not be repeated here.

[0246] Furthermore, it should be noted that the aforementioned communication module and / or processing module may be implemented as a virtual module. For example, the processing module may be implemented as a software functional unit or a virtual device, and the communication module may be implemented as a software function or a virtual device. Alternatively, the processing module or the communication module may be implemented as a physical device. For example, if the device is implemented as a chip / hardware circuit, the communication module may be an input / output circuit and / or a communication interface that performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module may be an integrated circuit or a logic circuit, etc.

[0247] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single module, physically exist separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware, software functional modules, or a combination of hardware and software functional modules, without limitation.

[0248] Referring to FIG11 , the present application also provides a schematic structural diagram of another communication device.

[0249] The communication device 1100 can be used to implement the functions of any communication device (for example, a first network device, a second network device, or a terminal device) described in the aforementioned method embodiments. The communication device 1100 may include at least one processor 1110. Optionally, the processor 1110 (or processing device) is coupled to a memory, and the memory may be located within the communication device, or the memory may be integrated with the processor, or the memory may be located outside the communication device. For example, the communication device 1100 may also include at least one memory 1120. The memory 1120 stores the necessary computer programs, instructions, and / or data for implementing any of the above embodiments; the processor 1110 may execute the computer programs, instructions, and / or data stored in the memory 1120 to complete the corresponding functions of the network device or terminal device in any of the above embodiments.

[0250] The communication device 1100 may further include a communication interface 1130, through which the communication device 1100 may exchange information with other devices. Exemplarily, the communication interface 1130 may be a transceiver, a circuit, a bus, a module, a pin, or another type of communication interface. When the communication device 1100 is a chip-type device or circuit, the communication interface 1130 in the device 1100 may also be an input / output circuit that may input information (or receive information) and / or output information (or send information). The processor may be an integrated circuit or a logic circuit, etc., and the processor may determine output information based on the input information.

[0251] Coupling in this application refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. Processor 1110 may operate in conjunction with memory 1120 and communication interface 1130. This application does not limit the connection medium between the processor 1110, memory 1120, and communication interface 1130.

[0252] Referring to Figure 12, the present application also provides a chip, wherein chip 30 includes circuit 31 and communication interface 32. Input / output interface 32. Circuit 31 can be a logic circuit, an integrated circuit, etc., and communication interface 32 can also be an input / output circuit, an input / output interface, an interface circuit, etc., which can input information (or receive information) or output information (or send information). Chip 30 can execute the methods performed by the network device (e.g., the first network device or the second network device) or the terminal device in each embodiment of the present application.

[0253] In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the operations and / or processing performed by the network device or terminal device in each method embodiment of the present application are executed.

[0254] The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processing performed by the network device or terminal device in the various method embodiments of the present application are executed.

[0255] The present application provides a communication system, including the network device and terminal device in the above method embodiment. For example, the communication system includes a first network device and a terminal device. Further, it may also include a second network device.

[0256] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.

[0257] In the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0258] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0260] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0261] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0262] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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

Claims

1. A communication method, characterized in that: include: Determining one or more target cells, wherein one target cell is not a serving cell of the UE; A first message is sent to a user equipment UE, where the first message includes configuration information of pre-configured uplink resources (PUR) corresponding to the one or more target cells.

2. The method according to claim 1, characterized in that The method further comprises: Sending a second message to the second network device, where the second message includes identification information of at least one target cell; A third message is received from the second network device, where the third message includes PUR configuration information corresponding to the at least one target cell.

3. The method according to claim 1 or 2, characterized in that The determining of one or more target cells includes: obtaining identification information of the one or more target cells from the UE, the one or more target cells being determined based on one or more of the following information: service stop time information in system message block 3, system message block 31, and system message block 32; The one or more target cells are determined according to identification information of the one or more target cells.

4. The method according to claim 1 or 2, characterized in that The determining of one or more target cells includes: Acquire PUR requirement information from the UE, where the PUR requirement information includes PUR time domain information requested by the UE, where the PUR time domain information includes at least one of a period, an offset, and a number of times; The one or more target cells are determined according to the PUR demand information.

5. The method according to any one of claims 2 to 4, characterized in that The second message further includes one or more items of the following information: UE location information and PUR time domain information.

6. The method according to any one of claims 2 to 5, characterized in that The second message and / or the third message further includes uplink authorization information, where the uplink authorization information includes one of the following: first uplink authorization information, where the first uplink authorization information is common uplink authorization information of the one or more target cells; or, second uplink authorization information, where the second uplink authorization information is common uplink authorization information of the at least one target cell managed by the second network device; or, At least one third uplink authorization information, where the third uplink authorization information is uplink authorization information corresponding to one or more target cells.

7. The method according to claim 5 or 6, characterized in that When the PUR corresponding to the PUR configuration information uses a user plane for data transmission, the second message further includes one or more of the following information: Access layer AS security information corresponding to the first target cell, the AS security information is used to determine the AS security key between the first target cell and the UE, the AS security information includes an access layer key Calculate NCC with the next hop chain; Security algorithm of the source cell; UE security capability information, where the UE security capability information indicates security algorithms supported by the UE; Wherein, the security algorithm includes an encryption algorithm and / or an integrity protection algorithm; The first target cell is one of the one or more target cells.

8. The method according to any one of claims 1 to 7, characterized in that The PUR configuration information includes one or more of the following information: Identification information of the first target cell, uplink authorization information of the first target cell, timing advance TA corresponding to the first target cell, and TA validity condition corresponding to the first target cell, wherein the first target cell is one of the one or more target cells.

9. The method according to claim 8, characterized in that When the PUR corresponding to the PUR configuration information performs data transmission based on the user plane, the PUR configuration information further includes one or more of the following information: a recovery identifier corresponding to the first target cell, the recovery identifier being used to identify a UE context saved for the UE by a network device to which the first target cell belongs; RRC configuration information of the first target cell; The AS security configuration of the first target cell, wherein the AS security configuration includes an access layer key The next hop chain calculates one or more of the NCC and the security algorithm.

10. The method according to claim 9, characterized in that The recovery identifier includes a first part and a second part, the first part is used to identify the network device to which the first target cell belongs, and the second part is used to identify the UE context saved by the network device to which the first target cell belongs for the UE.

11. The method according to any one of claims 1 to 10, characterized in that The PUR configuration information corresponding to the one or more target cells includes: first uplink authorization information, where the first uplink authorization information is uplink authorization information common to the one or more target cells; or at least one second uplink authorization information, where the second uplink authorization information is uplink authorization information common to at least one target cell managed by a network device; or At least one third uplink authorization information, where the third uplink authorization information is uplink authorization information corresponding to one or more target cells.

12. A communication method, characterized in that: include: receiving a first message from a first network device, where the first message includes configuration information of pre-configured uplink resources (PUR) corresponding to one or more target cells, where the one target cell is not a serving cell of a user equipment (UE); Based on the PUR configuration information, uplink data is sent on a valid PUR of a second target cell, where the second target cell is one of the one or more target cells.

13. The method according to claim 12, characterized in that The PUR corresponding to the PUR configuration information performs data transmission based on a user plane; and the first message further includes one or more of the following: a recovery identifier corresponding to the first target cell, where the recovery identifier is used to identify a UE context saved for the UE by a network device to which the first target cell belongs; RRC configuration information of the first target cell; AS security configuration of the first target cell, wherein the AS security configuration includes an access layer key The next hop chain calculates one or more of the NCC and the security algorithm; The first target cell is one of the one or more target cells.

14. The method according to claim 12 or 13, characterized in that The method further comprises: A first verification token is sent on a valid PUR of the second target cell, where the first verification token is generated according to one or more of the following information of the second target cell: PUR RNTI, physical cell identifier, and cell identifier.

15. The method according to any one of claims 12 to 14, characterized in that The second target cell is one of the following cells: The cell reselected by the UE; The cell measured by the UE; The cell where the UE resides.

16. The method according to any one of claims 12 to 15, characterized in that The PUR configuration information corresponding to the one or more target cells includes: first uplink authorization information, where the first uplink authorization information is uplink authorization information common to the one or more target cells; or at least one second uplink authorization information, where the second uplink authorization information is uplink authorization information common to at least one target cell managed by a network device; or At least one third uplink authorization information, where the third uplink authorization information is uplink authorization information corresponding to one or more target cells.

17. A communication method, characterized in that: include: receiving a second message, where the second message includes identification information of at least one target cell, where the at least one target cell is not a serving cell of the UE; Determining PUR configuration information corresponding to the at least one target cell; A third message is sent, where the third message carries the PUR configuration information corresponding to the at least one target cell.

18. The method according to claim 17, characterized in that The second message further includes one or more of the following information: UE location information, PUR time domain information, and uplink authorization information, where the PUR time domain information includes at least one of a period, an offset, and a number of times.

19. The method according to claim 18, characterized in that The PUR corresponding to the PUR configuration information performs data transmission based on the user plane; the second message further includes one or more of the following information: AS security information corresponding to the first target cell, the AS security information is used to determine the AS security key between the first target cell and the UE, the AS security information includes an access layer key Calculate NCC with the next hop chain; Security algorithm of the source cell; UE security capability information, where the UE security capability information indicates security algorithms supported by the UE; Wherein, the security algorithm includes an encryption algorithm and / or an integrity protection algorithm; The first target cell is one of the one or more target cells.

20. The method according to any one of claims 17 to 19, characterized in that The PUR configuration information includes one or more of the following information: The identification information of the first target cell, the uplink authorization information of the first target cell, the TA corresponding to the first target cell, and the TA validity condition corresponding to the first target cell, the first target cell being one of the at least one target cell.

21. The method according to claim 20, characterized in that The PUR corresponding to the PUR configuration information performs data transmission based on the user plane; the PUR configuration information further includes one or more of the following information: A recovery identifier corresponding to the first target cell, where the recovery identifier is used to identify a UE context saved for the UE by a network device to which the first target cell belongs; RRC configuration information of the first target cell; The AS security configuration of the first target cell, wherein the AS security configuration includes an access layer key The next hop chain calculates one or more of the NCC and the security algorithm.

22. The method according to claim 21, characterized in that The recovery identifier includes a first part and a second part, the first part is used to identify the network device to which the first target cell belongs, and the second part is used to identify the UE context saved by the network device to which the first target cell belongs.

23. The method according to any one of claims 18 to 22, characterized in that The uplink authorization information includes one of the following: first uplink authorization information, where the first uplink authorization information is uplink authorization information common to one or more target cells; or, second uplink authorization information, where the second uplink authorization information is common uplink authorization information of the at least one target cell managed by the second network device; or, At least one third uplink authorization information, where the third uplink authorization information is uplink authorization information corresponding to one or more target cells.

24. The method according to any one of claims 17 to 23, characterized in that The method further comprises: receiving a first verification token from the UE; generating a second verification token according to one or more of the following information of the first target cell: PUR RNTI, physical cell identifier, cell identifier; Perform security verification on the UE according to the first verification token and the second verification token.

25. A communication device, characterized in that: The method comprises a module or unit for executing the method according to any one of claims 1 to 11; or comprises a module or unit for executing the method according to any one of claims 12 to 16; or comprises a module or unit for executing the method according to any one of claims 17 to 24.

26. A communication device, characterized in that: The method comprises a processor coupled to a memory, wherein the processor is configured to execute a computer program or instruction stored in the memory so as to cause the communication device to perform the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 16, or the method according to any one of claims 17 to 24.

27. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 16, or the method according to any one of claims 17 to 24 is implemented.

28. A computer program product, characterized in that The computer program product comprises instructions, which, when executed, enable the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 16, or the method according to any one of claims 17 to 24 to be implemented.

Images