Communication method, communication device, and storage medium

Abstract

Disclosed in the present application are a communication method, a communication device, and a storage medium. The method comprises: communicating with a third device on the basis of first data or first signaling. The technical solution of the present application can refine an existing A-IoT processing mechanism, thereby ensuring the continuity of an A-IoT service and / or avoiding data loss during the process of a terminal device executing an A-IoT operation as a reader.

Description

Communication methods, communication equipment and storage media Technical Field

[0001] This application relates to the field of communication technology, specifically to a communication method, communication device, and storage medium. Background Technology

[0002] In existing protocols, a terminal device can be configured by a network device as a reader to perform A-IoT (Ambient Internet of Things) operations and transmit data between the network device (such as a base station) and the IoT device (such as a device). The reader configuration provided by the network device for the terminal device includes at least the radio resource configuration for performing A-IoT operations.

[0003] In the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] Due to the mobility of terminal devices, cell handover may be triggered when a terminal device performs A-IoT operations as a reader. However, different cells may have different reader configurations for terminal devices. For example, the target cell may not support A-IoT operations and may not be able to configure a reader for the terminal device. Alternatively, the target cell may not be able to configure the radio resources that the original cell configured for the terminal device. This will affect the continuity of A-IoT services, especially the continuity of A-IoT services for a single IoT device, which may prevent the terminal device from transmitting data between network devices and IoT devices.

[0005] Therefore, it is necessary to improve the existing A-IoT processing mechanism so that when the terminal device performs A-IoT operations as a reader, it can support ensuring the continuity of A-IoT services and / or avoid data loss.

[0006] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical solutions

[0007] The main objective of this application is to provide a communication method, communication device, and storage medium, which aims to improve the existing A-IoT processing mechanism so that when the terminal device performs A-IoT operations as a reader, it can support and ensure the continuity of A-IoT services and / or avoid data loss.

[0008] This application provides a communication method applicable to terminal devices (such as mobile phones), comprising the following steps:

[0009] S3: Communicate with a third device based on the first data or the first signaling.

[0010] Optionally, the first data is sent from the second device to the first device.

[0011] Optionally, before step S3, the following steps are also included:

[0012] Receive the first data sent by the first device;

[0013] Communicating with a third device based on first data includes at least one of the following:

[0014] Send the first data to the third device;

[0015] Receive the second data sent by the third device.

[0016] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0017] After receiving or sending the first signaling to the first device, send an R2D command to the third device or receive a D2R response command sent by the third device.

[0018] Optionally, the communication method further includes at least one of the following:

[0019] The first data is sent to the first device when the second device performs the handover;

[0020] The first data is sent by the first device based on a cell handover message.

[0021] The first data is A-IOT data;

[0022] The second data is the A-IOT response signaling;

[0023] The first data is sent from the core network equipment to the second equipment;

[0024] The first data is an R2D command;

[0025] The second data is the D2R response command;

[0026] R2D commands are A-IOT paging commands or access trigger commands;

[0027] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[0028] The first device is the target cell base station;

[0029] The second device is the original cell base station;

[0030] The third device is an A-IOT device.

[0031] Optionally, the communication method further includes at least one of the following:

[0032] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[0033] The second device sends a handover request to the first device;

[0034] The first device receives a handover request sent by the second device;

[0035] The first device sends a handover request confirmation message to the second device;

[0036] The second device performs the handover and / or data forwarding;

[0037] Receive the switching command sent by the second device;

[0038] The second device sends the first data to the first device;

[0039] The first device receives the first data sent by the second device;

[0040] Perform the RACH procedure on the target cell;

[0041] Send a cell handover completion message to the first device;

[0042] The first device sends a path switching request message to the core network device;

[0043] Receive the first data sent by the first device;

[0044] Send the second data to the first device;

[0045] The first device sends the second data to the second device;

[0046] The first device sends the second data to the core network device;

[0047] If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed.

[0048] Optionally, the communication method further includes at least one of the following:

[0049] The handover command is sent by the second device via an RRC reconfiguration message;

[0050] The switching commands include A-IOT data reporting instructions;

[0051] The first data is carried in the XnAP signaling;

[0052] The second data is sent to the first device via RRC signaling;

[0053] The second data is forwarded from the first device to the second device via XnAP signaling;

[0054] The second data is forwarded by the first device to the core network device via NGAP signaling;

[0055] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0056] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[0057] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[0058] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[0059] Optionally, the communication method further includes at least one of the following:

[0060] Assign AS-ID and / or RRC-ID to the third device;

[0061] Receive the first data forwarding completion indication sent by the first device;

[0062] The first device retains the new device identifier and / or discards the original device identifier;

[0063] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[0064] The first device sends a message to the second device requesting the original device's NGAP ID;

[0065] The first device receives the original device NGAP ID message sent by the second device;

[0066] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[0067] Restart the A-IOT service after the switch is complete.

[0068] Optionally, the communication method further includes at least one of the following:

[0069] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[0070] RRC signaling includes the original device identifier and / or the new device identifier;

[0071] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[0072] XnAP signaling is either new signaling or RRC transmission signaling;

[0073] The original equipment identification includes the original AS-ID and / or RRC-ID;

[0074] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[0075] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[0076] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[0077] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[0078] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[0079] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[0080] RRC-ID is used to identify a third device on the UU interface;

[0081] RRC-ID includes AS-ID;

[0082] The device NGAP ID is used to identify a third device on the NG port;

[0083] The original device's NGAP ID is assigned by the second device;

[0084] The new device's NGAP ID is assigned by the first device.

[0085] This application also provides a communication method applicable to a first device (such as a base station), comprising the following steps:

[0086] S2: Send first data or first signaling to enable the terminal device to communicate with the third device based on the first data or first signaling.

[0087] Optionally, the communication method further includes at least one of the following:

[0088] Receive the first data sent by the second device;

[0089] The terminal device communicates with the third device based on the first signaling, including:

[0090] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0091] The terminal device communicates with the third device based on the first data, including at least one of the following:

[0092] The terminal device sends the first data to the third device;

[0093] The terminal device receives the second data sent by the third device.

[0094] Optionally, the communication method further includes at least one of the following:

[0095] The first data is sent to the first device when the second device performs the handover;

[0096] The first data is sent by the first device based on a cell handover message.

[0097] The first data is A-IOT data;

[0098] The second data is the A-IOT response signaling;

[0099] The first data is sent from the core network equipment to the second equipment;

[0100] The first data is an R2D command;

[0101] The second data is the D2R response command;

[0102] R2D commands are A-IOT paging commands or access trigger commands;

[0103] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[0104] The first device is the target cell base station;

[0105] The second device is the original cell base station;

[0106] The third device is an A-IOT device.

[0107] Optionally, the communication method further includes at least one of the following:

[0108] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[0109] Receive a handover request sent by the second device;

[0110] Send a handover request confirmation message to the second device;

[0111] The second device performs the handover and / or data forwarding;

[0112] The second device sends a handover command to the terminal device;

[0113] The terminal device receives a handover command sent by the second device;

[0114] Receive the first data sent by the second device;

[0115] The terminal device executes the RACH procedure to the target cell;

[0116] Receive the cell handover completion message sent by the terminal device;

[0117] Send a path switching request message to the core network equipment;

[0118] Receive the second data sent by the terminal device;

[0119] Send the second data to the second device;

[0120] Send the second data to the core network equipment;

[0121] If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed.

[0122] Optionally, the communication method further includes at least one of the following:

[0123] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[0124] The switching commands include A-IOT data reporting instructions;

[0125] The first data is carried in the XnAP signaling;

[0126] Receive the second data via RRC signaling;

[0127] The second data is forwarded to the second device via XnAP signaling;

[0128] The second data is forwarded to the core network equipment via XnAP signaling;

[0129] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0130] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[0131] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[0132] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[0133] Optionally, the communication method further includes at least one of the following:

[0134] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[0135] Send the first data forwarding completion indication to the terminal device;

[0136] Save the new device identifier and / or discard the original device identifier;

[0137] Save the original device NGAP ID and / or the new device NGAP ID;

[0138] Send a message to the second device requesting the original device's NGAP ID;

[0139] Receive the original device NGAP ID message sent by the second device;

[0140] Obtain the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[0141] The terminal device restarts the A-IoT service after the switchover is complete.

[0142] Optionally, the communication method further includes at least one of the following:

[0143] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[0144] RRC signaling includes the original device identifier and / or the new device identifier;

[0145] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[0146] XnAP signaling is either new signaling or RRC transmission signaling;

[0147] The original equipment identification includes the original AS-ID and / or RRC-ID;

[0148] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[0149] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[0150] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[0151] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[0152] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[0153] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[0154] RRC-ID is used to identify a third device on the UU interface;

[0155] RRC-ID includes AS-ID;

[0156] The device NGAP ID is used to identify a third device on the NG port;

[0157] The original device's NGAP ID is assigned by the second device;

[0158] The new device's NGAP ID is assigned by the first device.

[0159] This application also provides a communication method applicable to a second device (such as a base station), comprising the following steps:

[0160] S1: Send first data or first signaling to enable the first device to send the first data or first signaling to the terminal device, and the terminal device to communicate with the third device based on the first data or first signaling.

[0161] Optionally, the communication method further includes at least one of the following:

[0162] Receive the first data or first signaling sent by the core network equipment;

[0163] The terminal device communicates with the third device based on the first signaling, including:

[0164] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0165] The terminal device communicates with the third device based on the first data, including at least one of the following:

[0166] The terminal device sends the first data to the third device;

[0167] The terminal device receives the second data sent by the third device.

[0168] Optionally, the communication method further includes at least one of the following:

[0169] The first data is sent to the first device when the second device performs the handover;

[0170] The first data is sent by the first device to the terminal device based on the cell handover completion message;

[0171] The first data is A-IOT data;

[0172] The second data is the A-IOT response signaling;

[0173] The first data is an R2D command;

[0174] The second data is the D2R response command;

[0175] R2D commands are A-IOT paging commands or access trigger commands;

[0176] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[0177] The first device is the target cell base station;

[0178] The second device is the original cell base station;

[0179] The third device is an A-IOT device.

[0180] Optionally, the communication method further includes at least one of the following:

[0181] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[0182] Send a handover request to the first device;

[0183] The first device sends a handover request confirmation message to the second device;

[0184] Perform handover and / or data forwarding;

[0185] Send a switching command to the first device;

[0186] The first device performs the RACH procedure to the target cell;

[0187] The terminal device sends a cell handover completion message to the first device;

[0188] The first device sends a path switching request message to the core network device;

[0189] The terminal device sends second data to the first device;

[0190] Receive the second data sent by the first device;

[0191] The first device sends the second data to the core network device;

[0192] If the first data cannot be sent to the terminal device, an NGAP signaling message is sent to the AMF to indicate that the AMF has failed to send A-IOT data.

[0193] Optionally, the communication method further includes at least one of the following:

[0194] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[0195] The switching commands include A-IOT data reporting instructions;

[0196] The first data is carried in the XnAP signaling;

[0197] The second data is sent from the terminal device to the first device via RRC signaling;

[0198] The second data is forwarded from the first device to the second device via XnAP signaling;

[0199] The second data is forwarded by the first device to the core network device via NGAP signaling;

[0200] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0201] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[0202] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[0203] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[0204] Optionally, the communication method further includes at least one of the following:

[0205] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[0206] The first device retains the new device identifier and / or discards the original device identifier;

[0207] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[0208] Receive the original device NGAP ID request message sent by the first device;

[0209] Send the original device NGAP ID message to the first device;

[0210] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[0211] The terminal device restarts the A-IoT service after the switchover is complete.

[0212] Optionally, the communication method further includes at least one of the following:

[0213] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[0214] RRC signaling includes the original device identifier and / or the new device identifier;

[0215] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[0216] XnAP signaling is either new signaling or RRC transmission signaling;

[0217] The original equipment identification includes the original AS-ID and / or RRC-ID;

[0218] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[0219] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[0220] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[0221] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[0222] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[0223] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[0224] RRC-ID is used to identify a third device on the UU interface;

[0225] RRC-ID includes AS-ID;

[0226] The device NGAP ID is used to identify a third device on the NG port;

[0227] The original device's NGAP ID is assigned by the second device;

[0228] The new device's NGAP ID is assigned by the first device.

[0229] This application also provides a communication method applicable to core network equipment (such as a CN), comprising the following steps:

[0230] S0: Send first data or first signaling to enable the second device to send the first data or first signaling to the terminal device via the first device, and the terminal device to communicate with the third device based on the first data or first signaling.

[0231] Optionally, the communication method further includes at least one of the following:

[0232] The terminal device communicates with the third device based on the first signaling, including:

[0233] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0234] The terminal device communicates with the third device based on the first data, including at least one of the following:

[0235] The terminal device sends the first data to the third device;

[0236] The terminal device receives the second data sent by the third device.

[0237] Optionally, the communication method further includes at least one of the following:

[0238] The first data is sent to the first device when the second device performs the handover;

[0239] The first data is sent by the first device to the terminal device based on the cell handover completion message;

[0240] The first data is A-IOT data;

[0241] The second data is the A-IOT response signaling;

[0242] The first data is an R2D command;

[0243] The second data is the D2R response command;

[0244] R2D commands are A-IOT paging commands or access trigger commands;

[0245] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[0246] The first device is the target cell base station;

[0247] The second device is the original cell base station;

[0248] The third device is an A-IOT device.

[0249] Optionally, the communication method further includes at least one of the following:

[0250] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[0251] The second device sends a handover request to the first device;

[0252] The first device sends a handover request confirmation message to the second device;

[0253] The second device performs the handover and / or data forwarding;

[0254] The terminal device receives a handover command sent by the second device;

[0255] The terminal device executes the RACH procedure to the target cell;

[0256] The terminal device sends a cell handover completion message to the first device;

[0257] Receive the path switching request message sent by the first device;

[0258] The terminal device sends second data to the first device;

[0259] The first device sends the second data to the second device;

[0260] Receive the second data sent by the first device;

[0261] If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed.

[0262] Optionally, the communication method further includes at least one of the following:

[0263] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[0264] The switching commands include A-IOT data reporting instructions;

[0265] The first data is carried in the XnAP signaling;

[0266] The second data is sent to the first device via RRC signaling;

[0267] The second data is forwarded from the first device to the second device via XnAP signaling;

[0268] The second data is forwarded by the first device to the core network device via NGAP signaling;

[0269] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0270] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[0271] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[0272] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[0273] Optionally, the communication method further includes at least one of the following:

[0274] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[0275] The first device retains the new device identifier and / or discards the original device identifier;

[0276] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[0277] The first device sends a message to the second device requesting the original device's NGAP ID;

[0278] The first device receives the original device NGAP ID message sent by the second device;

[0279] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[0280] The terminal device restarts the A-IoT service after the switchover is complete.

[0281] Optionally, the communication method further includes at least one of the following:

[0282] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[0283] RRC signaling includes the original device identifier and / or the new device identifier;

[0284] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[0285] XnAP signaling is either new signaling or RRC transmission signaling;

[0286] The original equipment identification includes the original AS-ID and / or RRC-ID;

[0287] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[0288] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[0289] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[0290] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[0291] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[0292] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[0293] RRC-ID is used to identify a third device on the UU interface;

[0294] RRC-ID includes AS-ID;

[0295] The device NGAP ID is used to identify a third device on the NG port;

[0296] The original device's NGAP ID is assigned by the second device;

[0297] The new device's NGAP ID is assigned by the first device.

[0298] This application also provides a communication device, the communication device comprising:

[0299] The first communication module is used to communicate with a third device based on first data or first signaling.

[0300] This application also provides a communication device, the communication device comprising:

[0301] The second sending module is used to send first data or first signaling so that the terminal device can communicate with the third device based on the first data or first signaling.

[0302] This application also provides a communication device, the communication device comprising:

[0303] The third sending module is used to send first data or first signaling so that the first device sends the first data or first signaling to the terminal device, and the terminal device communicates with the third device based on the first data or first signaling.

[0304] This application also provides a communication device, the communication device comprising:

[0305] The fourth sending module is used to send first data or first signaling so that the second device sends the first data or first signaling to the terminal device via the first device, and the terminal device communicates with the third device based on the first data or first signaling.

[0306] This application also provides a communication device, including: a memory, a processor, and a communication program stored in the memory and executable on the processor, wherein the communication program, when executed by the processor, implements the steps of any of the communication methods described above.

[0307] The communication equipment in this application may be a terminal device (such as a mobile phone), a first device and / or a second device (such as a base station), a core network device (such as a CN), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific meaning needs to be clarified in the context.

[0308] This application also provides a computer-readable storage medium storing a communication program, which, when executed by a processor, implements the steps of any of the communication methods described above.

[0309] The technical solution of this application allows the terminal device to communicate with the third device based on the first data or the first signaling, which can improve the existing A-IoT processing mechanism and support ensuring the continuity of A-IoT services and / or preventing data loss during the process of the terminal device performing A-IoT operations as a reader. Attached Figure Description

[0310] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0311] Figure 1 is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application;

[0312] Figure 2 is a communication network system architecture diagram provided in an embodiment of this application;

[0313] Figure 3 is a diagram of another communication network system architecture provided in an embodiment of this application;

[0314] Figure 4 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0315] Figure 5 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0316] Figure 6 is a flowchart illustrating the communication method according to the first embodiment of this application;

[0317] Figure 7 is a schematic diagram of a scenario where the terminal device moves in the communication method shown in the first embodiment of this application;

[0318] Figure 8 is a schematic diagram of the interaction scenario between the terminal device and the A-IoT device in the communication method shown in the first embodiment of this application;

[0319] Figure 9 is a schematic diagram of a scenario illustrating the communication method according to the second embodiment of this application;

[0320] Figures 10-12 are schematic diagrams illustrating a communication method according to a third embodiment of this application.

[0321] Figure 13 is a flowchart illustrating the communication method according to the fifth embodiment of this application;

[0322] Figure 14 is a flowchart illustrating the communication method according to the sixth embodiment of this application;

[0323] Figure 15 is a flowchart illustrating the communication method according to the seventh embodiment of this application;

[0324] Figure 16 is a schematic diagram of the interaction process between the network device and the terminal device in the communication method shown in the eighth embodiment of this application;

[0325] Figure 17 is a schematic diagram of the communication device provided in an embodiment of this application;

[0326] Figure 18 is a second structural schematic diagram of the communication device provided in an embodiment of this application;

[0327] Figure 19 is a schematic diagram of the structure of the communication device provided in the embodiment of this application;

[0328] Figure 20 is a schematic diagram of the structure of the communication device provided in the embodiment of this application;

[0329] Figure 21 is a schematic diagram of the structure of the communication device provided in the embodiment of this application.

[0330] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments.

[0331] Implementation methods of this application

[0332] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0333] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element, and / or, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0334] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, can be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, can be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0335] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0336] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0337] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0338] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0339] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0340] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a first device and / or a second device (such as a base station), a core network device (such as a CN), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific meaning needs to be clarified according to the context.

[0341] Terminal devices can be implemented in various forms. For example, the terminal devices described in this application may include smart terminal devices such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0342] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminal devices.

[0343] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: a radio frequency unit 101, a WiFi module 102, an audio output unit 103, an A / V (audio / video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0344] The following section, with reference to Figure 1, provides a detailed description of each component of the mobile terminal:

[0345] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. And / or, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.

[0346] WiFi is a short-range wireless transmission technology. Mobile terminals using WiFi module 102 can help users send and receive emails, browse web pages, and access streaming media, providing wireless broadband internet access. Although Figure 1 shows WiFi module 102, it is understood that it is not an essential component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0347] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, or other modes. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0348] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0349] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0350] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0351] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands from processor 110. And / or, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0352] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 according to the type of touch event. Although in FIG. 1, the touch panel 1071 and the display panel 1061 are implemented as two independent components to realize the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0353] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more components within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0354] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). And / or, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0355] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0356] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0357] Although not shown in Figure 1, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0358] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0359] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of this application. The communication network system is an NR (New Radio) system based on general mobile communication technology, and is at least applied to 5G systems. The communication network system architecture includes 5GC (5G core network) and NG-RAN (5G radio access network). 5GC includes: AMF (Access and Mobility Management Function) and UPF (User Plane Function Entity); NG-RAN includes gNB, ng-gNB, etc.

[0360] The AMF (Automatic Facilitation Module) is used to perform registration, connection, reachability, and mobility management. It provides a session management message transmission channel for the UE and SMF, and offers authentication and authorization functions for user access. It is the access point for the UE (User Equipment) and the core network control plane of the radio. The UPF (User PF) is used for packet routing and forwarding, policy enforcement, traffic reporting, QoS processing, etc. The gNB (Gateway Base Station) is a key unit in the 5G (NR) wireless communication system. As a base station in the 5G Radio Access Network (RAN), it is responsible for establishing wireless connections with the UE and for data transmission between the UE and the core network.

[0361] Optionally, the communication network system architecture may also include the following service-based interfaces: Xn interface and NG interface, where Xn is the interface between gNBs (ng-gNBs); and NG is the interface between gNBs (ng-gNBs) and AMF and / or UPF.

[0362] Please refer to Figure 3, which is another communication network system architecture diagram provided in the embodiments of this application. The communication network system is a NR (New Radio) system of general mobile communication technology, which is at least applied to 5G systems. The network functions (NF) of the communication network system architecture may include: AUSF (Authentication Service Function), AMF (Access and Mobility Management Function), DN (Data Network) (e.g., operator services, Internet access or third-party services), NEF (Network Exposure Function), NRF (Network Repository Function), NSACF (Network Slice Admission Control Function), NSSAAF (Network Slice-Specific and SNPN Authentication and Authorization Function), NSSF (Network Slice Selection Function), PCF (Policy Control Function), SMF (Session Management Function), UDM (Unified Data Management), UPF (User Plane Function), AF (Application Function), UE (User Equipment), (R)AN ((Radio) Access Network), and EASDF (Edge Application Server Discovery Function).

[0363] Optionally, the communication network system architecture may also include the following network entities: SCP (Serving Communication Agent) and multiple interfaces. Specifically, interface N1 is the interface between the UE and AMF, N2 is the interface between the RAN and AMF, N3 is the interface between the RAN and UPF, N4 is the interface between the UPF and SMF, N6 is the interface between the UPF and DN, and N9 is the interface between UPFs.

[0364] Optionally, the communication network system architecture may further include the following service-based interfaces: Namf, Nsmf, Nnef, Npcf, Nudm, Naf, Nnrf, Nnsacf, Nnssf, Nnssaaf, Nausf, Neasdf, and Nupf, wherein Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nnef is the service-based interface presented by NEF, Npcf is the service-based interface presented by PCF, Nudm is the service-based interface presented by UDM, Naf is the service-based interface presented by AF, Nnrf is the service-based interface presented by NRF, Nnsacf is the service-based interface presented by NSACF, Nnssf is the service-based interface presented by NSSF, Nnssaaf is the service-based interface presented by NSSAAF, Nausf is the service-based interface presented by AUSF, Neasdf is the service-based interface presented by EASDF, and Nupf is the service-based interface presented by UPF.

[0365] Although the above description uses LTE and NR systems as examples, those skilled in the art should know that this application is not only applicable to LTE and NR systems, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5GA, and future new network systems (such as 6G), etc., without limitation here.

[0366] Figure 4 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0367] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0368] Figure 5 is a schematic diagram of the hardware structure of a network node 150 provided in this application. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the above-described method embodiment. The implementation principle and beneficial effects are similar, and will not be described again here.

[0369] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0370] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0371] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.

[0372] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0373] Technical terms used in this embodiment:

[0374] A-IoT: Ambient IoT;

[0375] CBRA: Contention-Based Random Access;

[0376] CFA: Contention-Free Access, based on non-contention-based random access;

[0377] D2R: Device to Reader;

[0378] IoT: Internet of Things;

[0379] PDRCH: Physical D2R Channel;

[0380] PRDCH: Physical R2D CHannel;

[0381] R2D: Reader to Device;

[0382] TrCH: Transport Channel;

[0383] DO-DTT: Device-Originated by Device-Terminated Trigger;

[0384] DT: Device-Terminated;

[0385] DO-A: Device-Originated Autonomous;

[0386] LPWAN: Low Power Wide Area Network;

[0387] MTC: Machine Type Communication;

[0388] NB-IoT: Narrow Band Internet of Things;

[0389] RedCap: Reduced Capability, lightweight;

[0390] SRB: Signaling Radio Bearer;

[0391] 5GC: 5G Core network;

[0392] ADRF: Analytics Data Repository Function, an entity that provides functionality for the analytics data repository.

[0393] AF: Application Function, application function entity;

[0394] AMF; Access and Mobility Management Function.

[0395] AUSF: Authentication Server Function;

[0396] DN: Data Network;

[0397] NEF: Network Exposure Function.

[0398] NF: Network Function, a network function entity;

[0399] NR: New Radio;

[0400] NRF: Network Repository Function.

[0401] NWDAF: Network Data Analytics Function;

[0402] OTT: Over The Top;

[0403] PCF: Policy Control Function;

[0404] PDU: Protocol Data Unit;

[0405] (R)AN: (Radio)Access Network;

[0406] SMF: Session Management Function;

[0407] UDM: Unified Data Management;

[0408] UE: User Equipment, terminal equipment;

[0409] UPF: User Plane Function;

[0410] NG-RAN: 5G Radio Access Network;

[0411] SENF: Sensing Function;

[0412] GMSENC: Gateway Mobile Sensing Centre;

[0413] GAD: Universal Geographical Area Description;

[0414] SUPI: SUbscription Permanent Identifier;

[0415] ISAC: Integrated Sensing and Communication.

[0416] First Embodiment

[0417] Referring to Figure 6, which is a flowchart illustrating the communication method of the first embodiment of this application, the communication method of this embodiment can be applied to terminal devices (such as mobile phones), including step S3:

[0418] S3: The terminal device communicates with the third device based on the first data or the first signaling.

[0419] This embodiment takes into account that: due to the mobility of terminal devices, cell handover may be triggered when a terminal device performs A-IoT operations as a reader. However, different cells may have different reader configurations for terminal devices. For example, the target cell may not support A-IoT operations and may not be able to configure a reader for the terminal device. Alternatively, the target cell may not be able to configure the radio resources that the original cell configured for the terminal device. This will affect the continuity of A-IoT services, especially the continuity of A-IoT services for a single IoT device (A-IoT device) cannot be guaranteed, resulting in the terminal device being unable to transmit data between network devices and IoT devices.

[0420] As shown in Figure 7, the terminal device (UE Reader) interacts with the A-IoT device (such as device 1, device 2 or device 3) to perform A-IoT operations. Due to the mobility of the terminal device, the terminal device will trigger cell handover during the A-IoT operation. For example, the terminal device moves from the cell covered by base station 1 to the cell covered by base station 2. Different cells may have different reader configurations for the terminal device, which will affect the continuity of A-IoT services.

[0421] Therefore, this embodiment proposes a technical solution in which the terminal device communicates with the third device based on the first data or the first signaling, thereby improving the existing A-IoT processing mechanism so that the terminal device, as a reader, can perform A-IoT operations while ensuring the continuity of A-IoT services and / or preventing data loss.

[0422] As shown in Figure 8, during the process of the terminal device performing A-IoT operations as a reader, the interaction messages between the terminal device and the A-IoT device (such as a device) include at least one of MSG1 (message 1), MSG2 (message 2), MSG3 (message 3), MSG4 (message 4), and MSG5 (message 5).

[0423] Optionally, MSG1, MSG3, and MSG5 are sent to the terminal device by the A-IoT device.

[0424] Optionally, MSG2 and MSG4 are sent from the terminal device to the A-IoT device.

[0425] Optionally, MSG1 is a random access ID request message sent by the A-IoT device to the terminal device.

[0426] Optionally, MSG2 is a random access ID response message sent by the terminal device to the A-IOT device.

[0427] Optionally, MSG3 is a D2R upper-layer data transmission response command sent by the A-IoT device to the terminal device.

[0428] Optionally, MSG4 is an R2D command sent by the terminal device to the A-IOT device, which is forwarded from the original cell base station to the target cell base station.

[0429] Optionally, MSG5 is a D2R upper-layer data transmission response command sent by the A-IOT device to the terminal device. This D2R upper-layer data transmission response command is forwarded from the target cell base station or the original cell base station to the AMF.

[0430] Based on the scenarios shown in Figures 7 and 8, the technical solution of this embodiment will be described in detail below.

[0431] Optionally, the terminal device communicates with the third device based on the first data or the first signaling.

[0432] Optionally, the first data is sent from the first device to the terminal device.

[0433] Optionally, before step S3, the communication method further includes: the terminal device receiving first data sent by the first device.

[0434] Optionally, the first data is sent from the second device to the first device.

[0435] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0436] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0437] Optionally, the first data is sent to the first device when the second device performs the handover.

[0438] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0439] Optionally, the first signaling is sent from the first device to the terminal device.

[0440] Optionally, the first signaling is sent from the terminal device to the first device.

[0441] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0442] Optionally, the first device is the target cell base station.

[0443] Optionally, the second device is the original cell base station.

[0444] Optionally, the third device is an A-IoT device.

[0445] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[0446] The terminal device sends the first data to the third device;

[0447] The terminal device receives the second data sent by the third device.

[0448] Optionally, the first data is A-IOT data.

[0449] Optionally, the second data is A-IOT response signaling.

[0450] Optionally, the first data is an R2D command.

[0451] Optionally, the second data is a D2R response command.

[0452] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0453] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0454] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[0455] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[0456] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[0457] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[0458] Optionally, in response to receiving the handover command, the terminal device communicates with the third device based on the first data or the first signaling. That is, before the terminal device communicates with the third device based on the first data or the first signaling, the second device performs the handover and / or data forwarding and sends the handover command to the terminal device.

[0459] Optionally, the second device initiates a handover preparation process to the first device, and the second device sends a handover request to the first device.

[0460] Optionally, the handover request includes at least one of the following: reader configuration information of the terminal device configured in the original cell, data forwarding indication, new SRB establishment indication, original device identifier, ongoing A-IoT service information, and the original device identifier list received by the second device.

[0461] Optionally, the original device identifier includes the original AS-ID and / or RRC-ID.

[0462] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0463] Optionally, the AS-ID is used to identify a third device between the terminal device and the first and / or second device.

[0464] Optionally, AS-ID is used to identify A-IoT devices between the terminal device and the original cell base station.

[0465] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the target cell base station.

[0466] Optionally, RRC-ID is used to identify a third device on the uu interface.

[0467] Optionally, RRC-ID is used to identify A-IoT devices on the uu interface.

[0468] Optionally, RRC-ID includes AS-ID.

[0469] Optionally, the RRC-ID includes the AS-ID plus the reader ID of the terminal device.

[0470] Optionally, the AS-ID and / or RRC-ID are assigned by the terminal device.

[0471] Optionally, the terminal device assigns an AS-ID and / or RRC-ID to the third device.

[0472] Optionally, the device NGAP ID is used to identify a third device on the NG port.

[0473] Optionally, the reader configuration information of the terminal device includes the radio resource configuration for the terminal device to perform A-IOT operations and / or the XnAP connection allocated for A-IOT by the access network device.

[0474] Optionally, the A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier.

[0475] Optionally, the access network equipment includes a first device and / or a second device.

[0476] Optionally, the first device receives a handover request sent by the second device.

[0477] Optionally, the first device sends a handover request confirmation message to the second device.

[0478] Optionally, the handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released.

[0479] Optionally, the second device performs the handover and / or data forwarding.

[0480] Optionally, the second device sends a switching command to the terminal device and / or sends first data to the first device.

[0481] Optionally, the handover command is an RRC reconfiguration message, meaning the handover command is sent from the second device to the terminal device via an RRC reconfiguration message.

[0482] Optionally, the first data is A-IOT data forwarded by the second device, which is the R2D command received by the second device from the core network device, such as the Command Request command.

[0483] Optionally, the first data is carried in XnAP signaling; that is, the forwarded A-IOT data is carried in XnAP signaling.

[0484] Optionally, the XnAP signaling includes at least one of the following: the source device identifier, the container of the NGAP signaling, and the command request.

[0485] Optionally, the XnAP signaling includes at least one of the following: the original RRC-ID, the original Device NGAP ID (i.e., the original device NGAP ID), a container for NGAP signaling, and an R2D command.

[0486] Alternatively, NGAP signaling can be a command request.

[0487] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[0488] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[0489] Optionally, the NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of the NGAP signaling, the original Device NGAP ID, the new Device NGAPID, the command response, and the inventory report.

[0490] Optionally, the original Device NGAP ID is assigned by a second device.

[0491] Optionally, the original Device NGAP ID is assigned by the original cell base station. Alternatively, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface.

[0492] Optionally, the new Device NGAP ID is assigned by the first device.

[0493] Optionally, the new Device NGAP ID is assigned by the target cell base station. Alternatively, the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[0494] Optionally, if the second device finds that it cannot send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to send A-IOT data.

[0495] Optionally, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[0496] Optionally, the terminal device receives a handover command sent by the second device.

[0497] Optionally, the terminal device performs a RACH procedure to the target cell.

[0498] Optionally, the RACH procedure can be a CFRA procedure or a CBRA procedure.

[0499] Optionally, after completing the RACH process, the terminal device sends a cell handover completion message to the first device.

[0500] Optionally, the cell handover completion message is an RRC connection reconfiguration completion message (RRCReconfigurationComplete message).

[0501] Optionally, after receiving the first data (i.e., the R2D command from the core network device) sent by the second device from the core network device, the first device sends a path switch request message to the core network device.

[0502] Optionally, the path switching request message includes the original Device NGAP ID and / or the new Device NGAP ID.

[0503] Optionally, the core network device sends a path switching request response message to the first device.

[0504] Optionally, the terminal device and the first device transmit data via RRC signaling.

[0505] Optionally, the RRC signaling includes the original device identifier and / or the new device identifier.

[0506] Optionally, RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and a new SRB.

[0507] Optionally, the first device sends the first data to the terminal device via RRC signaling.

[0508] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID.

[0509] Optionally, the first device may also instruct the terminal device whether it has completed forwarding the A-IoT data transmission from the second device.

[0510] Optionally, the terminal device receives a first data forwarding completion indication sent by the first device.

[0511] Optionally, the terminal device sends the first data to the third device.

[0512] Optionally, the terminal device receives second data sent by the third device.

[0513] Optionally, the second data is sent to the first device via RRC signaling.

[0514] Optionally, the terminal device sends second data to the first device via RRC signaling.

[0515] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[0516] Optionally, the first device sends the second data to the core network device.

[0517] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling. Optionally, the NGAP signaling also includes a new Device NGAP ID.

[0518] Optionally, the first device may save the new device identifier and / or discard the original device identifier.

[0519] Optionally, the first device saves the new RRC-ID and / or discards the original RRC-ID.

[0520] Optionally, after receiving the second data, the first device sends the second data to the second device.

[0521] Optionally, the second data is carried in XnAP signaling, that is, the second data is forwarded from the first device to the second device by the first device through XnAP signaling.

[0522] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0523] Optionally, XnAP signaling can be a Command Response / inventory report.

[0524] Optionally, after receiving the second data, the first device sends an NGAP ID request message to the second device.

[0525] Optionally, the original device NGAP ID request message carries the original AS-ID and / or the reader ID of the terminal device.

[0526] Optionally, the original device NGAP ID request message carries the RRC-ID.

[0527] Optionally, the first device receives the original Device NGAP ID message sent by the second device;

[0528] Optionally, the original Device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device.

[0529] Optionally, the original Device NGAP ID message carries the original RRC-ID.

[0530] Optionally, the first device sends the second data to the core network device.

[0531] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0532] Optionally, XnAP signaling can be a Command Response / inventory report.

[0533] Optionally, the second data is carried in XnAP signaling.

[0534] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling.

[0535] Optionally, the NGAP signaling also includes the original Device NGAP ID and the new Device NGAP ID.

[0536] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0537] Optionally, after receiving the second data, the first device obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[0538] Optionally, the first device obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device and the original RRC-ID list and original device NGAP-ID list obtained from the second device in the handover request message, and then carries the second data (i.e. the forwarded A-IOT data) in the NGAP signaling.

[0539] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[0540] Optionally, the new Device NGAP-ID is assigned to the device by the first device and is used to uniquely identify a device on the NGAP interface.

[0541] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0542] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[0543] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[0544] Optionally, in this scheme, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered access failures and are prepared to receive re-access trigger commands, such as A-IOT paging messages.

[0545] Through the technical solution of this embodiment, the terminal device communicates with the third device based on the first data or the first signaling, which can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[0546] Second Embodiment

[0547] Based on the first embodiment of this application, a second embodiment of this application is proposed. This embodiment mainly describes the method of establishing and forwarding A-IoT data across base stations in the scenario where the terminal device is used as a reader.

[0548] Optionally, the terminal device communicates with the third device based on the first data, thereby improving the existing A-IoT processing mechanism, so that during the process of the terminal device performing A-IoT operations as a reader, it can support ensuring the continuity of A-IoT services and / or avoid data loss.

[0549] Optionally, the terminal device receives the first data sent by the first device.

[0550] Optionally, the first data is sent from the second device to the first device.

[0551] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0552] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0553] Optionally, the first data is sent to the first device when the second device performs the handover.

[0554] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0555] Optionally, the terminal device communicates with the third device based on the first data, including:

[0556] The terminal device sends the first data to the third device;

[0557] The terminal device receives the second data sent by the third device.

[0558] Optionally, the first data is A-IOT data.

[0559] Optionally, the second data is A-IOT response signaling.

[0560] Optionally, the first data is an R2D command.

[0561] Optionally, the second data is a D2R response command.

[0562] As shown in Figure 9, the network system architecture involved in this embodiment includes: a terminal device (UE Reader) as a reader, the original cell base station (gNB1), the target cell base station (gNB2), and the core network device (CN). The terminal device (UE Reader) also interacts with the device (A-IOT device) to perform A-IOT operations.

[0563] Optionally, the original cell base station (gNB1) and the target cell base station (gNB2) are connected via the Xn interface.

[0564] Optionally, MSG1, MSG2, and MSG3 have been successfully transmitted before the cell handover is performed.

[0565] Optionally, in scenarios where the terminal device acts as a reader, the process of establishing a bearer and forwarding A-IoT data across base stations includes the following steps 0-10:

[0566] Step 0. The core network equipment sends a command request to the original cell base station;

[0567] Step 1. The original cell base station sends a handover request message to the target cell base station;

[0568] Optionally, the original cell gNB1 initiates a handover preparation process to the target cell gNB1.

[0569] Optionally, the original cell gNB1 sends a HANDOVER REQUEST message to the target cell gNB2.

[0570] Optionally, the HANDOVER REQUEST message includes at least one of the following: UEreader configuration information configured in the original cell, data forwarding indication, new SRB establishment indication, original RRC-ID (old RRC-ID), ongoing A-IOT service information, and the original device identifier list received by the original cell base station.

[0571] Optionally, the original RRC-ID is used to uniquely identify a device on the original cell's UU port, etc.

[0572] Optionally, the A-IoT service information includes at least one of the following: AIOT-F ID (the identifier of the functional node initiating the A-IoT service) and Correlation ID (the identifier of the A-IoT service).

[0573] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0574] Step 2. The target cell base station sends a handover request confirmation message to the original cell base station;

[0575] Optionally, the target cell gNB2 sends a HANDOVER REQUEST ACKNOWLEDGE message to the original cell gNB1.

[0576] Optionally, the HANDOVER REQUEST ACKNOWLEDGE message may carry at least one of the following: reader configuration information of the terminal device, an indication that the reader configuration information of the terminal device configured in the original cell remains valid, and an indication that the reader configuration information of the terminal device configured in the original cell is released.

[0577] Step 3. The original cell base station executes the handover command and data forwarding;

[0578] Specifically, it includes steps 3a and 3b. The execution order of steps 3a and 3b can be simultaneous, or steps 3a can be prioritized, or steps 3b can be executed first. No restrictions are imposed here.

[0579] Step 3a. The original cell base station sends a handover command to the terminal device;

[0580] Optionally, the original cell base station sends an RRCReconfiguration message to the terminal device, and sends a handover command through the RRCReconfiguration message.

[0581] Step 3b. The original cell base station gNB1 sends forwarded A-IOT data (i.e., the first data) to the target cell base station gNB2;

[0582] Optionally, the forwarded A-IOT data is also the R2D command received by the original cell base station from the core network equipment, such as the Command Request command.

[0583] Optionally, the forwarded A-IOT data is carried in XnAP signaling.

[0584] Optionally, the XnAP signaling also includes a container for the original RRC-ID, the original Device NGAP ID, and the NGAP signaling.

[0585] Optionally, NGAP signaling can be a Command.

[0586] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[0587] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[0588] Optionally, if the original cell base station finds that it cannot send A-IOT data to the terminal device, it can send NGAP signaling to the AMF.

[0589] Optionally, the signaling indicates to the AMF that A-IOT data transmission failed. Optionally, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[0590] Step 4. The terminal device performs the RACH procedure to the target cell;

[0591] Optionally, the RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0592] Step 5. The terminal device sends a handover completion message to the target cell;

[0593] Optionally, the switchover completion message is an RRC connection reconfiguration complete message (RRCReconfigurationComplete message).

[0594] Step 6. The target cell base station sends a path handover request message to the core network equipment;

[0595] Optionally, the target cell base station sends a path switch request message to the core network equipment.

[0596] Optionally, the path switch request message may include the original Device NGAP ID and / or the new Device NGAP ID.

[0597] Optionally, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface, and the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[0598] Step 7. The core network equipment sends a path handover response message to the target cell base station;

[0599] Optionally, the core network equipment sends a path switching request response to the target cell base station.

[0600] Step 8. The target cell base station sends A-IoT data to the terminal device via RRC signaling;

[0601] Optionally, A-IOT data is an R2D command.

[0602] Optionally, if a new SRB is established, the target cell base station uses the new SRB to send the RRC signaling; or, if a new SRB is not established, the target cell base station uses SRB1, SRB2, or SRB4 to send the RRC signaling.

[0603] Optionally, the RRC signaling includes the original RRC-ID.

[0604] Optionally, the target cell base station can also instruct the terminal device whether it has completed forwarding the A-IOT data from the original cell.

[0605] Optionally, the terminal device forwards the received A-IoT data to the device.

[0606] Optionally, the terminal device receives A-IOT response signaling from the device.

[0607] Step 9. The terminal device sends an A-IOT response signaling to the target cell base station via RRC signaling;

[0608] Optionally, if a new SRB is established, the target cell base station uses the new SRB to send the RRC signaling.

[0609] Optionally, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to carry the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[0610] Optionally, the A-IOT response signaling is a D2R response command.

[0611] Optionally, the target cell base station receives A-IOT response signaling.

[0612] Optionally, the target cell base station saves the new RRC-ID and discards the original RRC-ID.

[0613] Step 10. The target cell base station sends a response command to the core network equipment.

[0614] Optionally, the target cell base station sends a command response to the core network equipment.

[0615] Optionally, the target cell base station will send the response command to the core network equipment via NGAP signaling.

[0616] Optionally, the NGAP signaling also includes a new Device NGAP ID.

[0617] Through the technical solution of this embodiment, the terminal device communicates with the third device based on the first data, which can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[0618] Third Embodiment

[0619] Based on any of the above embodiments of this application, a third embodiment of this application is proposed. This embodiment mainly describes the method of establishing and forwarding A-IoT data across base stations in the scenario where the terminal device is used as a reader.

[0620] Optionally, the terminal device communicates with the third device based on the first data, thereby improving the existing A-IoT processing mechanism, so that during the process of the terminal device performing A-IoT operations as a reader, it can support ensuring the continuity of A-IoT services and / or avoid data loss.

[0621] Optionally, the terminal device receives the first data sent by the first device.

[0622] Optionally, the first data is sent from the second device to the first device.

[0623] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0624] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0625] Optionally, the first data is sent to the first device when the second device performs the handover.

[0626] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0627] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[0628] The terminal device sends the first data to the third device;

[0629] The terminal device receives the second data sent by the third device.

[0630] Optionally, the first data is A-IOT data.

[0631] Optionally, the second data is A-IOT response signaling.

[0632] Optionally, the first data is an R2D command.

[0633] Optionally, the second data is a D2R response command.

[0634] As shown in Figures 10-12, the network system architecture involved in this embodiment includes: a terminal device (UE), a source cell base station (gNB1), a target cell base station (gNB2), and a core network device (CN). The terminal device (UE Reader) also interacts with the device (A-IOT device) to perform A-IOT operations.

[0635] Optionally, the original cell base station (gNB1) and the target cell base station (gNB2) are connected via the Xn interface.

[0636] Optionally, MSG1 and MSG2 have been successfully transmitted before the cell handover is performed, or MSG1, MSG2, MSG3 and MSG4 have been successfully transmitted.

[0637] Optionally, in scenarios where the terminal device acts as a reader, the process of implementing cross-base station A-IoT data forwarding specifically includes the following steps 0-10:

[0638] Step 0. The core network equipment sends a command request to the original cell base station;

[0639] Step 1. The original cell base station sends a handover request message to the target cell base station;

[0640] Optionally, the original cell gNB1 initiates a handover preparation process to the target cell gNB1.

[0641] Optionally, the original cell gNB1 sends a HANDOVER REQUEST message to the target cell gNB2.

[0642] Optionally, the HANDOVER REQUEST message includes at least one of the following: UEreader configuration information configured in the original cell, data forwarding indication, new SRB establishment indication, original RRC-ID (old RRC-ID), ongoing A-IOT service information, and the original device identifier list received by the original cell base station.

[0643] Optionally, the original RRC-ID is used to uniquely identify a device on the original cell's UU port, etc.

[0644] Optionally, the A-IoT service information includes at least one of the following: AIOT-F ID (the identifier of the functional node initiating the A-IoT service) and Correlation ID (the identifier of the A-IoT service).

[0645] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0646] Step 2. The target cell base station sends a handover request confirmation message to the original cell base station;

[0647] Optionally, the target cell gNB2 sends a HANDOVER REQUEST ACKNOWLEDGE message to the original cell gNB1.

[0648] Optionally, the HANDOVER REQUEST ACKNOWLEDGE message may carry at least one of the following: reader configuration information of the terminal device, an indication that the reader configuration information of the terminal device configured in the original cell remains valid, and an indication that the reader configuration information of the terminal device configured in the original cell is released.

[0649] Step 3. The original cell base station sends a handover command to the terminal device;

[0650] Optionally, the original cell base station sends an RRCReconfiguration message to the terminal device, and sends a handover command through the RRCReconfiguration message.

[0651] Step 4. The terminal device performs the RACH procedure to the target cell;

[0652] Optionally, the RACH procedure can be either a CFRA procedure or a CBRA procedure.

[0653] Step 5. The terminal device sends a handover completion message to the target cell;

[0654] Step 6. The target cell base station sends a path handover request message to the core network equipment;

[0655] Optionally, the target cell base station sends a path switch request message to the core network equipment.

[0656] Optionally, the path switch request message may include the original Device NGAP ID and / or the new Device NGAP ID.

[0657] Optionally, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface, and the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[0658] Step 7. The core network equipment sends a path handover response message to the target cell base station;

[0659] Optionally, the core network equipment sends a path switching request response to the target cell base station.

[0660] Step 8. The terminal device sends an A-IOT response signaling to the target cell base station via RRC signaling;

[0661] Optionally, if a new SRB is established, the target cell base station uses the new SRB to send the RRC signaling.

[0662] Optionally, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to carry the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[0663] Optionally, the A-IOT response signaling is a D2R response command.

[0664] Optionally, there are three ways to implement the target cell base station, as shown in Figures 10, 11 and 12 respectively.

[0665] Optionally, in the first implementation, as shown in Figure 10, steps 9 and 10 are included after step 8:

[0666] Step 9. The target cell base station gNB2 sends the forwarded A-IOT data to the original cell base station gNB1;

[0667] Optionally, the forwarded A-IOT data is the D2R command (also known as the D2R response command) received by the target cell base station from the terminal device, such as the Command Response / Inventory Report command.

[0668] Optionally, the forwarded A-IOT data is carried in XnAP signaling.

[0669] Optionally, the XnAP signaling also includes a container for the original RRC-ID, the original Device NGAP ID, and the NGAP signaling.

[0670] Optionally, NGAP signaling can be a Command Response / inventory report.

[0671] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[0672] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[0673] Step 10. The original cell base station gNB1 sends forwarded A-IOT data to the core network equipment.

[0674] Optionally, forwarded A-IOT data, such as Command Response / inventory report commands, may carry the Device NGAP-ID.

[0675] Alternatively, as shown in Figure 11, the second implementation further includes steps 9-11 after step 8:

[0676] Step 9. The target cell base station sends the forwarded A-IOT data to the original cell base station;

[0677] Optionally, the forwarded A-IOT data may include a message requesting the original device NGAP-ID.

[0678] Optionally, request the original device NGAP-ID message carrying the original RRC-ID.

[0679] Step 10. The original cell base station returns A-IoT data to the target cell base station;

[0680] Optionally, the returned A-IOT data includes the original Device NGAP-ID message.

[0681] Optionally, the target cell base station receives the original Device NGAP-ID message from the original cell base station.

[0682] Optionally, the original Device NGAP-ID message also includes the original RRC-ID.

[0683] Step 11. The target cell base station sends a command response to the core network equipment.

[0684] Optionally, the target cell base station sends the D2R command received by the target cell base station from the terminal device to the core network equipment, such as the Command Response / inventory report command.

[0685] Optionally, the D2R command is forwarded A-IOT data, which is carried in NGAP signaling.

[0686] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[0687] Optionally, the new Device NGAP-ID is assigned to the device by the target cell base station and is used to uniquely identify a device on the NGAP interface.

[0688] Optionally, the target cell base station will save the new Device NGAP-ID and the new RRC-ID together.

[0689] Alternatively, as shown in Figure 12, the third implementation further includes steps 9-10 after step 8:

[0690] Step 9. Obtain the original Device NGAP-ID from the target cell base station;

[0691] Optionally, the target cell base station obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[0692] Optionally, the target cell base station obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device, as well as the original RRC-ID list and original device NGAP-ID list obtained from the original cell base station in the handover request message.

[0693] Step 10. The target cell base station sends a command response to the core network equipment.

[0694] Optionally, the target cell base station sends the D2R command received by the target cell base station from the terminal device to the core network equipment, such as the Command Response / inventory report command.

[0695] Optionally, the D2R command is forwarded A-IOT data, which is carried in NGAP signaling.

[0696] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[0697] Optionally, the new Device NGAP-ID is assigned to the device by the target cell base station and is used to uniquely identify a device on the NGAP interface.

[0698] Optionally, the target cell base station will save the new Device NGAP-ID and the new RRC-ID together.

[0699] Through the technical solution of this embodiment, the terminal device communicates with the third device based on the first data, which can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[0700] Fourth embodiment

[0701] Based on any of the above embodiments of this application, a fourth embodiment of this application is proposed. This embodiment mainly describes the method of establishing and forwarding A-IoT data across base stations in the scenario where the terminal device is used as a reader.

[0702] Optionally, the terminal device communicates with the third device based on the first signaling, thereby improving the existing A-IoT processing mechanism so that during the process of the terminal device performing A-IoT operations as a reader, it can support ensuring the continuity of A-IoT services and / or avoid data loss.

[0703] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0704] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0705] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0706] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[0707] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[0708] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[0709] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[0710] Optionally, the network system architecture involved in this embodiment includes: a terminal device (UE Reader) as a reader, a source cell base station (gNB1), a target cell base station (gNB2), and a core network device (CN). The terminal device (UE Reader) also interacts with the device (A-IoT device) to perform A-IoT operations.

[0711] Optionally, the original cell base station (gNB1) and the target cell base station (gNB2) are connected via the Xn interface.

[0712] Optionally, MSG1, MSG2, and MSG3 have been successfully transmitted before the cell handover is performed.

[0713] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[0714] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[0715] Optionally, access trigger messages or A-IOT paging messages are sent via R2D commands.

[0716] Optionally, in this scheme, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered access failures and are prepared to receive re-access trigger commands, such as A-IOT paging messages.

[0717] Through the technical solution of this embodiment, the terminal device communicates with the third device based on the first signaling, which can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[0718] Fifth Embodiment

[0719] Referring to Figure 13, which is a flowchart illustrating the communication method of the fifth embodiment of this application, the communication method of this embodiment can be applied to a first device (such as a base station), including step S2:

[0720] Step S2: The first device sends first data or first signaling to enable the terminal device to communicate with the third device based on the first data or first signaling.

[0721] Optionally, the first data is sent from the first device to the terminal device.

[0722] Optionally, the terminal device receives the first data sent by the first device.

[0723] Optionally, the first data is sent from the second device to the first device.

[0724] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0725] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0726] Optionally, the first data is sent to the first device when the second device performs the handover.

[0727] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0728] Optionally, the first device receives the first data sent by the second device and sends the first data to the terminal device, so that the terminal device can communicate with the third device based on the first data or the first signaling.

[0729] Optionally, the first signaling is sent from the first device to the terminal device.

[0730] Optionally, the first signaling is sent from the terminal device to the first device.

[0731] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0732] Optionally, the first device is the target cell base station.

[0733] Optionally, the second device is the original cell base station.

[0734] Optionally, the third device is an A-IoT device.

[0735] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[0736] The terminal device sends the first data to the third device;

[0737] The terminal device receives the second data sent by the third device.

[0738] Optionally, the first data is A-IOT data.

[0739] Optionally, the second data is A-IOT response signaling.

[0740] Optionally, the first data is an R2D command.

[0741] Optionally, the second data is a D2R response command.

[0742] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0743] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0744] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[0745] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[0746] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[0747] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[0748] Optionally, the terminal device communicates with the third device based on the first data or the first signaling in response to receiving the handover command. That is, before the terminal device communicates with the third device based on the first data or the first signaling, the second device performs the handover and / or data forwarding and sends the handover command to the terminal device.

[0749] Optionally, the second device initiates a handover preparation process to the first device, and the second device sends a handover request to the first device.

[0750] Optionally, the handover request includes at least one of the following: reader configuration information of the terminal device configured in the original cell, data forwarding indication, new SRB establishment indication, original device identifier, ongoing A-IoT service information, and the original device identifier list received by the second device.

[0751] Optionally, the original device identifier includes the original AS-ID and / or RRC-ID.

[0752] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0753] Optionally, the AS-ID is used to identify a third device between the terminal device and the first and / or second device.

[0754] Optionally, AS-ID is used to identify A-IoT devices between the terminal device and the original cell base station.

[0755] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the target cell base station.

[0756] Optionally, RRC-ID is used to identify a third device on the uu interface.

[0757] Optionally, RRC-ID is used to identify A-IoT devices on the uu interface.

[0758] Optionally, RRC-ID includes AS-ID.

[0759] Optionally, the RRC-ID includes the AS-ID plus the reader ID of the terminal device.

[0760] Optionally, the AS-ID and / or RRC-ID are assigned by the terminal device.

[0761] Optionally, the terminal device assigns an AS-ID and / or RRC-ID to the third device.

[0762] Optionally, the device NGAP ID is used to identify a third device on the NG port.

[0763] Optionally, the reader configuration information of the terminal device includes the radio resource configuration for the terminal device to perform A-IOT operations and / or the XnAP connection allocated for A-IOT by the access network device.

[0764] Optionally, the A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier.

[0765] Optionally, the access network equipment includes a first device and / or a second device.

[0766] Optionally, the first device receives a handover request sent by the second device.

[0767] Optionally, the first device sends a handover request confirmation message to the second device.

[0768] Optionally, the handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released.

[0769] Optionally, the second device performs the handover and / or data forwarding.

[0770] Optionally, the second device sends a switching command to the terminal device and / or sends first data to the first device.

[0771] Optionally, the handover command is an RRC reconfiguration message, meaning the handover command is sent from the second device to the terminal device via an RRC reconfiguration message.

[0772] Optionally, the first data is A-IOT data forwarded by the second device, which is the R2D command received by the second device from the core network device, such as the Command Request command.

[0773] Optionally, the first data is carried in XnAP signaling; that is, the forwarded A-IOT data is carried in XnAP signaling.

[0774] Optionally, the XnAP signaling includes at least one of the following: the source device identifier, the container of the NGAP signaling, and the command request.

[0775] Optionally, the XnAP signaling includes at least one of the following: the original RRC-ID, the original Device NGAP ID (i.e., the original device NGAP ID), a container for NGAP signaling, and an R2D command.

[0776] Alternatively, NGAP signaling can be a command request.

[0777] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[0778] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[0779] Optionally, the NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of the NGAP signaling, the original Device NGAP ID, the new Device NGAPID, the command response, and the inventory report.

[0780] Optionally, the original Device NGAP ID is assigned by a second device.

[0781] Optionally, the original Device NGAP ID is assigned by the original cell base station. Alternatively, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface.

[0782] Optionally, the new Device NGAP ID is assigned by the first device.

[0783] Optionally, the new Device NGAP ID is assigned by the target cell base station. Alternatively, the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[0784] Optionally, if the second device finds that it cannot send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to send A-IOT data.

[0785] Alternatively, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[0786] Optionally, the terminal device receives a handover command sent by the second device.

[0787] Optionally, the terminal device performs a RACH procedure to the target cell.

[0788] Optionally, the RACH procedure can be a CFRA procedure or a CBRA procedure.

[0789] Optionally, after completing the RACH process, the terminal device sends a cell handover completion message to the first device.

[0790] Optionally, the cell handover completion message is an RRC connection reconfiguration completion message (RRCReconfigurationComplete message).

[0791] Optionally, after receiving the first data (i.e., the R2D command from the core network device) sent by the second device from the core network device, the first device sends a path switch request message to the core network device.

[0792] Optionally, the path switching request message includes the original Device NGAP ID and / or the new Device NGAP ID.

[0793] Optionally, the core network device sends a path switching request response message to the first device.

[0794] Optionally, the terminal device and the first device transmit data via RRC signaling.

[0795] Optionally, the RRC signaling includes the original device identifier and / or the new device identifier.

[0796] Optionally, RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and a new SRB.

[0797] Optionally, the first device sends the first data to the terminal device via RRC signaling.

[0798] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID.

[0799] Optionally, the first device may also instruct the terminal device whether it has completed forwarding the A-IoT data transmission from the second device.

[0800] Optionally, the terminal device receives a first data forwarding completion indication sent by the first device.

[0801] Optionally, the terminal device sends the first data to the third device.

[0802] Optionally, the terminal device receives second data sent by the third device.

[0803] Optionally, the second data is sent to the first device via RRC signaling.

[0804] Optionally, the terminal device sends second data to the first device via RRC signaling.

[0805] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[0806] Optionally, the first device sends the second data to the core network device.

[0807] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling. Optionally, the NGAP signaling also includes a new Device NGAP ID.

[0808] Optionally, the first device may save the new device identifier and / or discard the original device identifier.

[0809] Optionally, the first device saves the new RRC-ID and / or discards the original RRC-ID.

[0810] Optionally, after receiving the second data, the first device sends the second data to the second device.

[0811] Optionally, the second data is carried in XnAP signaling, that is, the second data is forwarded from the first device to the second device by the first device through XnAP signaling.

[0812] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0813] Optionally, XnAP signaling can be a Command Response / inventory report.

[0814] Optionally, after receiving the second data, the first device sends an NGAP ID request message to the second device.

[0815] Optionally, the original device NGAP ID request message carries the original AS-ID and / or the reader ID of the terminal device.

[0816] Optionally, the original device NGAP ID request message carries the RRC-ID.

[0817] Optionally, the first device receives the original Device NGAP ID message sent by the second device;

[0818] Optionally, the original Device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device.

[0819] Optionally, the original Device NGAP ID message carries the original RRC-ID.

[0820] Optionally, the first device sends the second data to the core network device.

[0821] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0822] Optionally, XnAP signaling can be a Command Response / inventory report.

[0823] Optionally, the second data is carried in XnAP signaling.

[0824] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling.

[0825] Optionally, the NGAP signaling also includes the original Device NGAP ID and the new Device NGAP ID.

[0826] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0827] Optionally, after receiving the second data, the first device obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[0828] Optionally, the first device obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device and the original RRC-ID list and original device NGAP-ID list obtained from the second device in the handover request message, and then carries the second data (i.e. the forwarded A-IOT data) in the NGAP signaling.

[0829] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[0830] Optionally, the new Device NGAP-ID is assigned to the device by the first device and is used to uniquely identify a device on the NGAP interface.

[0831] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0832] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[0833] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[0834] Optionally, in this embodiment, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered to have failed to access and are prepared to receive a re-access trigger command, such as an A-IOT paging message.

[0835] Through the technical solution of this embodiment, the first device sends first data or first signaling so that the terminal device can communicate with the third device based on the first data or first signaling. This can improve the existing A-IoT processing mechanism and support ensuring the continuity of A-IoT services and / or preventing data loss during the process of the terminal device performing A-IoT operations as a reader.

[0836] Sixth Embodiment

[0837] Referring to Figure 14, which is a flowchart illustrating the communication method of the sixth embodiment of this application, the communication method of this embodiment can be applied to a second device (such as a base station), and includes step S1:

[0838] Step S1: The second device sends first data or first signaling to enable the first device to send first data or first signaling to the terminal device, and the terminal device communicates with the third device based on the first data or first signaling.

[0839] Optionally, the terminal device receives the first data sent by the first device.

[0840] Optionally, the first data is sent from the second device to the first device.

[0841] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0842] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0843] Optionally, the first data is sent to the first device when the second device performs the handover.

[0844] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0845] Optionally, the first device receives the first data sent by the second device and sends the first data to the terminal device, so that the terminal device can communicate with the third device based on the first data or the first signaling.

[0846] Optionally, the first signaling is sent from the first device to the terminal device.

[0847] Optionally, the first signaling is sent from the terminal device to the first device.

[0848] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0849] Optionally, the first device is the target cell base station.

[0850] Optionally, the second device is the original cell base station.

[0851] Optionally, the third device is an A-IoT device.

[0852] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[0853] The terminal device sends the first data to the third device;

[0854] The terminal device receives the second data sent by the third device.

[0855] Optionally, the first data is A-IOT data.

[0856] Optionally, the second data is A-IOT response signaling.

[0857] Optionally, the first data is an R2D command.

[0858] Optionally, the second data is a D2R response command.

[0859] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0860] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0861] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0862] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[0863] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[0864] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[0865] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[0866] Optionally, the terminal device communicates with the third device based on the first data or the first signaling in response to receiving the handover command. That is, before the terminal device communicates with the third device based on the first data or the first signaling, the second device performs the handover and / or data forwarding and sends the handover command to the terminal device.

[0867] Optionally, the second device initiates a handover preparation process to the first device, and the second device sends a handover request to the first device.

[0868] Optionally, the handover request includes at least one of the following: reader configuration information of the terminal device configured in the original cell, data forwarding indication, new SRB establishment indication, original device identifier, ongoing A-IoT service information, and the original device identifier list received by the second device.

[0869] Optionally, the original device identifier includes the original AS-ID and / or RRC-ID.

[0870] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0871] Optionally, the AS-ID is used to identify a third device between the terminal device and the first and / or second device.

[0872] Optionally, AS-ID is used to identify A-IoT devices between the terminal device and the original cell base station.

[0873] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the target cell base station.

[0874] Optionally, RRC-ID is used to identify a third device on the uu interface.

[0875] Optionally, RRC-ID is used to identify A-IoT devices on the uu interface.

[0876] Optionally, RRC-ID includes AS-ID.

[0877] Optionally, the RRC-ID includes the AS-ID plus the reader ID of the terminal device.

[0878] Optionally, the AS-ID and / or RRC-ID are assigned by the terminal device.

[0879] Optionally, the terminal device assigns an AS-ID and / or RRC-ID to the third device.

[0880] Optionally, the device NGAP ID is used to identify a third device on the NG port.

[0881] Optionally, the reader configuration information of the terminal device includes the radio resource configuration for the terminal device to perform A-IOT operations and / or the XnAP connection allocated for A-IOT by the access network device.

[0882] Optionally, the A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier.

[0883] Optionally, the access network equipment includes a first device and / or a second device.

[0884] Optionally, the first device receives a handover request sent by the second device.

[0885] Optionally, the first device sends a handover request confirmation message to the second device.

[0886] Optionally, the handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released.

[0887] Optionally, the second device performs the handover and / or data forwarding.

[0888] Optionally, the second device sends a switching command to the terminal device and / or sends first data to the first device.

[0889] Optionally, the handover command is an RRC reconfiguration message, meaning the handover command is sent from the second device to the terminal device via an RRC reconfiguration message.

[0890] Optionally, the first data is A-IOT data forwarded by the second device, which is the R2D command received by the second device from the core network device, such as the Command Request command.

[0891] Optionally, the first data is carried in XnAP signaling; that is, the forwarded A-IOT data is carried in XnAP signaling.

[0892] Optionally, the XnAP signaling includes at least one of the following: the source device identifier, the container of the NGAP signaling, and the command request.

[0893] Optionally, the XnAP signaling includes at least one of the following: the original RRC-ID, the original Device NGAP ID (i.e., the original device NGAP ID), a container for NGAP signaling, and an R2D command.

[0894] Alternatively, NGAP signaling can be a command request.

[0895] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[0896] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[0897] Optionally, the NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of the NGAP signaling, the original Device NGAP ID, the new Device NGAPID, the command response, and the inventory report.

[0898] Optionally, the original Device NGAP ID is assigned by a second device.

[0899] Optionally, the original Device NGAP ID is assigned by the original cell base station. Alternatively, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface.

[0900] Optionally, the new Device NGAP ID is assigned by the first device.

[0901] Optionally, the new Device NGAP ID is assigned by the target cell base station. Alternatively, the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[0902] Optionally, if the second device finds that it cannot send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to send A-IOT data.

[0903] Alternatively, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[0904] Optionally, the terminal device receives a handover command sent by the second device.

[0905] Optionally, the terminal device performs a RACH procedure to the target cell.

[0906] Optionally, the RACH procedure can be a CFRA procedure or a CBRA procedure.

[0907] Optionally, after completing the RACH process, the terminal device sends a cell handover completion message to the first device.

[0908] Optionally, the cell handover completion message is an RRC connection reconfiguration completion message (RRCReconfigurationComplete message).

[0909] Optionally, after receiving the first data (i.e., the R2D command from the core network device) sent by the second device from the core network device, the first device sends a path switch request message to the core network device.

[0910] Optionally, the path switching request message includes the original Device NGAP ID and / or the new Device NGAP ID.

[0911] Optionally, the core network device sends a path switching request response message to the first device.

[0912] Optionally, the terminal device and the first device transmit data via RRC signaling.

[0913] Optionally, the RRC signaling includes the original device identifier and / or the new device identifier.

[0914] Optionally, RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and a new SRB.

[0915] Optionally, the first device sends the first data to the terminal device via RRC signaling.

[0916] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID.

[0917] Optionally, the first device may also instruct the terminal device whether it has completed forwarding the A-IoT data transmission from the second device.

[0918] Optionally, the terminal device receives a first data forwarding completion indication sent by the first device.

[0919] Optionally, the terminal device sends the first data to the third device.

[0920] Optionally, the terminal device receives second data sent by the third device.

[0921] Optionally, the second data is sent to the first device via RRC signaling.

[0922] Optionally, the terminal device sends second data to the first device via RRC signaling.

[0923] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[0924] Optionally, the first device sends the second data to the core network device.

[0925] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling. Optionally, the NGAP signaling also includes a new Device NGAP ID.

[0926] Optionally, the first device may save the new device identifier and / or discard the original device identifier.

[0927] Optionally, the first device saves the new RRC-ID and / or discards the original RRC-ID.

[0928] Optionally, after receiving the second data, the first device sends the second data to the second device.

[0929] Optionally, the second data is carried in XnAP signaling, that is, the second data is forwarded from the first device to the second device by the first device through XnAP signaling.

[0930] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0931] Optionally, XnAP signaling can be a Command Response / inventory report.

[0932] Optionally, after receiving the second data, the first device sends an NGAP ID request message to the second device.

[0933] Optionally, the original device NGAP ID request message carries the original AS-ID and / or the reader ID of the terminal device.

[0934] Optionally, the original device NGAP ID request message carries the RRC-ID.

[0935] Optionally, the first device receives the original Device NGAP ID message sent by the second device;

[0936] Optionally, the original Device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device.

[0937] Optionally, the original Device NGAP ID message carries the original RRC-ID.

[0938] Optionally, the first device sends the second data to the core network device.

[0939] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[0940] Optionally, XnAP signaling can be a Command Response / inventory report.

[0941] Optionally, the second data is carried in XnAP signaling.

[0942] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling.

[0943] Optionally, the NGAP signaling also includes the original Device NGAP ID and the new Device NGAP ID.

[0944] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0945] Optionally, after receiving the second data, the first device obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[0946] Optionally, the first device obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device and the original RRC-ID list and original device NGAP-ID list obtained from the second device in the handover request message, and then carries the second data (i.e. the forwarded A-IOT data) in the NGAP signaling.

[0947] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[0948] Optionally, the new Device NGAP-ID is assigned to the device by the first device and is used to uniquely identify a device on the NGAP interface.

[0949] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[0950] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[0951] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[0952] Optionally, in this embodiment, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered to have failed to access and are prepared to receive a re-access trigger command, such as an A-IOT paging message.

[0953] Through the technical solution of this embodiment, the second device sends first data or first signaling, so that the first device sends first data or first signaling to the terminal device. The terminal device communicates with the third device based on the first data or first signaling. This can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[0954] Seventh Embodiment

[0955] Referring to Figure 15, which is a flowchart illustrating the communication method of the seventh embodiment of this application, the communication method of this embodiment can be applied to core network equipment (such as CN), including step S0:

[0956] Step S0: The core network device sends first data or first signaling to enable the second device to send the first data or first signaling to the terminal device via the first device, and the terminal device communicates with the third device based on the first data or first signaling.

[0957] Optionally, the first data is sent from the second device to the first device.

[0958] Optionally, the first data is sent from the first device to the terminal device.

[0959] Optionally, the terminal device receives the first data sent by the first device.

[0960] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[0961] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[0962] Optionally, the first data is sent to the first device when the second device performs the handover.

[0963] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[0964] Optionally, the first device receives the first data sent by the second device and sends the first data to the terminal device, so that the terminal device can communicate with the third device based on the first data or the first signaling.

[0965] Optionally, the first signaling is sent from the first device to the terminal device.

[0966] Optionally, the first signaling is sent from the terminal device to the first device.

[0967] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0968] Optionally, the first device is the target cell base station.

[0969] Optionally, the second device is the original cell base station.

[0970] Optionally, the third device is an A-IoT device.

[0971] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[0972] The terminal device sends the first data to the third device;

[0973] The terminal device receives the second data sent by the third device.

[0974] Optionally, the first data is A-IOT data.

[0975] Optionally, the second data is A-IOT response signaling.

[0976] Optionally, the first data is an R2D command.

[0977] Optionally, the second data is a D2R response command.

[0978] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[0979] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[0980] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[0981] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[0982] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[0983] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[0984] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[0985] Optionally, the terminal device communicates with the third device based on the first data or the first signaling in response to receiving the handover command. That is, before the terminal device communicates with the third device based on the first data or the first signaling, the second device performs the handover and / or data forwarding and sends the handover command to the terminal device.

[0986] Optionally, the second device initiates a handover preparation process to the first device, and the second device sends a handover request to the first device.

[0987] Optionally, the handover request includes at least one of the following: reader configuration information of the terminal device configured in the original cell, data forwarding indication, new SRB establishment indication, original device identifier, ongoing A-IoT service information, and the original device identifier list received by the second device.

[0988] Optionally, the original device identifier includes the original AS-ID and / or RRC-ID.

[0989] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[0990] Optionally, the AS-ID is used to identify a third device between the terminal device and the first and / or second device.

[0991] Optionally, AS-ID is used to identify A-IoT devices between the terminal device and the original cell base station.

[0992] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the target cell base station.

[0993] Optionally, RRC-ID is used to identify a third device on the uu interface.

[0994] Optionally, RRC-ID is used to identify A-IoT devices on the uu interface.

[0995] Optionally, RRC-ID includes AS-ID.

[0996] Optionally, the RRC-ID includes the AS-ID plus the reader ID of the terminal device.

[0997] Optionally, the AS-ID and / or RRC-ID are assigned by the terminal device.

[0998] Optionally, the terminal device assigns an AS-ID and / or RRC-ID to the third device.

[0999] Optionally, the device NGAP ID is used to identify a third device on the NG port.

[1000] Optionally, the reader configuration information of the terminal device includes the radio resource configuration for the terminal device to perform A-IOT operations and / or the XnAP connection allocated for A-IOT by the access network device.

[1001] Optionally, the A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier.

[1002] Optionally, the access network equipment includes a first device and / or a second device.

[1003] Optionally, the first device receives a handover request sent by the second device.

[1004] Optionally, the first device sends a handover request confirmation message to the second device.

[1005] Optionally, the handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released.

[1006] Optionally, the second device performs the handover and / or data forwarding.

[1007] Optionally, the second device sends a switching command to the terminal device and / or sends first data to the first device.

[1008] Optionally, the handover command is an RRC reconfiguration message, meaning the handover command is sent from the second device to the terminal device via an RRC reconfiguration message.

[1009] Optionally, the first data is A-IOT data forwarded by the second device, which is the R2D command received by the second device from the core network device, such as the Command Request command.

[1010] Optionally, the first data is carried in XnAP signaling; that is, the forwarded A-IOT data is carried in XnAP signaling.

[1011] Optionally, the XnAP signaling includes at least one of the following: the source device identifier, the container of the NGAP signaling, and the command request.

[1012] Optionally, the XnAP signaling includes at least one of the following: the original RRC-ID, the original Device NGAP ID (i.e., the original device NGAP ID), a container for NGAP signaling, and an R2D command.

[1013] Alternatively, NGAP signaling can be a command request.

[1014] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[1015] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[1016] Optionally, the NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of the NGAP signaling, the original Device NGAP ID, the new Device NGAPID, the command response, and the inventory report.

[1017] Optionally, the original Device NGAP ID is assigned by a second device.

[1018] Optionally, the original Device NGAP ID is assigned by the original cell base station. Alternatively, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface.

[1019] Optionally, the new Device NGAP ID is assigned by the first device.

[1020] Optionally, the new Device NGAP ID is assigned by the target cell base station. Alternatively, the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[1021] Optionally, if the second device finds that it cannot send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to send A-IOT data.

[1022] Alternatively, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[1023] Optionally, the terminal device receives a handover command sent by the second device.

[1024] Optionally, the terminal device performs a RACH procedure to the target cell.

[1025] Optionally, the RACH procedure can be a CFRA procedure or a CBRA procedure.

[1026] Optionally, after completing the RACH process, the terminal device sends a cell handover completion message to the first device.

[1027] Optionally, the cell handover completion message is an RRC connection reconfiguration completion message (RRCReconfigurationComplete message).

[1028] Optionally, after receiving the first data (i.e., the R2D command from the core network device) sent by the second device from the core network device, the first device sends a path switch request message to the core network device.

[1029] Optionally, the path switching request message includes the original Device NGAP ID and / or the new Device NGAP ID.

[1030] Optionally, the core network device sends a path switching request response message to the first device.

[1031] Optionally, the terminal device and the first device transmit data via RRC signaling.

[1032] Optionally, the RRC signaling includes the original device identifier and / or the new device identifier.

[1033] Optionally, RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and a new SRB.

[1034] Optionally, the first device sends the first data to the terminal device via RRC signaling.

[1035] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID.

[1036] Optionally, the first device may also instruct the terminal device whether it has completed forwarding the A-IoT data transmission from the second device.

[1037] Optionally, the terminal device receives a first data forwarding completion indication sent by the first device.

[1038] Optionally, the terminal device sends the first data to the third device.

[1039] Optionally, the terminal device receives second data sent by the third device.

[1040] Optionally, the second data is sent to the first device via RRC signaling.

[1041] Optionally, the terminal device sends second data to the first device via RRC signaling.

[1042] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[1043] Optionally, the first device sends the second data to the core network device.

[1044] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling. Optionally, the NGAP signaling also includes a new Device NGAP ID.

[1045] Optionally, the first device may save the new device identifier and / or discard the original device identifier.

[1046] Optionally, the first device saves the new RRC-ID and / or discards the original RRC-ID.

[1047] Optionally, after receiving the second data, the first device sends the second data to the second device.

[1048] Optionally, the second data is carried in XnAP signaling, that is, the second data is forwarded from the first device to the second device by the first device through XnAP signaling.

[1049] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[1050] Optionally, XnAP signaling can be a Command Response / inventory report.

[1051] Optionally, after receiving the second data, the first device sends an NGAP ID request message to the second device.

[1052] Optionally, the original device NGAP ID request message carries the original AS-ID and / or the reader ID of the terminal device.

[1053] Optionally, the original device NGAP ID request message carries the RRC-ID.

[1054] Optionally, the first device receives the original Device NGAP ID message sent by the second device;

[1055] Optionally, the original Device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device.

[1056] Optionally, the original Device NGAP ID message carries the original RRC-ID.

[1057] Optionally, the first device sends the second data to the core network device.

[1058] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[1059] Optionally, XnAP signaling can be a Command Response / inventory report.

[1060] Optionally, the second data is carried in XnAP signaling.

[1061] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling.

[1062] Optionally, the NGAP signaling also includes the original Device NGAP ID and the new Device NGAP ID.

[1063] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[1064] Optionally, after receiving the second data, the first device obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[1065] Optionally, the first device obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device and the original RRC-ID list and original device NGAP-ID list obtained from the second device in the handover request message, and then carries the second data (i.e. the forwarded A-IOT data) in the NGAP signaling.

[1066] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[1067] Optionally, the new Device NGAP-ID is assigned to the device by the first device and is used to uniquely identify a device on the NGAP interface.

[1068] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[1069] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[1070] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[1071] Optionally, in this embodiment, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered to have failed to access and are prepared to receive a re-access trigger command, such as an A-IOT paging message.

[1072] Through the technical solution of this embodiment, the core network device sends first data or first signaling, so that the second device sends first data or first signaling to the terminal device via the first device. The terminal device communicates with the third device based on the first data or first signaling. This can improve the existing A-IoT processing mechanism, so as to support and ensure the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operation as a reader.

[1073] Eighth embodiment

[1074] Referring to Figure 16, which is a schematic diagram of the interaction flow of the first device, the second device, the core network device, and the terminal device according to the eighth embodiment of the communication method, the eighth embodiment of this application proposes a communication method including steps S0-S3:

[1075] Step S0: The core network device sends first data or first signaling to enable the second device to send the first data or first signaling to the terminal device via the first device, and the terminal device communicates with the third device based on the first data or first signaling;

[1076] Step S1: The second device sends first data or first signaling to enable the first device to send first data or first signaling to the terminal device, and the terminal device communicates with the third device based on the first data or first signaling;

[1077] Step S2: The first device sends first data or first signaling to enable the terminal device to communicate with the third device based on the first data or first signaling;

[1078] Step S3: The terminal device communicates with the third device based on the first data or the first signaling.

[1079] Optionally, the terminal device receives the first data sent by the first device.

[1080] Optionally, the terminal device communicates with the third device based on the first data or the first signaling.

[1081] Optionally, the first data is sent from the second device to the first device.

[1082] Optionally, the first data is forwarded from the core network equipment to the first equipment by the second equipment.

[1083] Optionally, the first data is sent from the core network device to the second device, and then the second device sends the first data back to the first device.

[1084] Optionally, the first data is sent to the first device when the second device performs the handover.

[1085] Optionally, the first data is sent by the first device to the terminal device based on the cell handover completion message.

[1086] Optionally, the first signaling is sent from the first device to the terminal device.

[1087] Optionally, the first signaling is sent from the terminal device to the first device.

[1088] Optionally, the first signaling is at least one of the MSG1, MSG2, and RRC connection reconfiguration completion messages during the random access process.

[1089] Optionally, the first device is the target cell base station.

[1090] Optionally, the second device is the original cell base station.

[1091] Optionally, the third device is an A-IoT device.

[1092] Optionally, the terminal device communicates with the third device based on the first data, including at least one of the following:

[1093] The terminal device sends the first data to the third device;

[1094] The terminal device receives the second data sent by the third device.

[1095] Optionally, the first data is A-IOT data.

[1096] Optionally, the second data is A-IOT response signaling.

[1097] Optionally, the first data is an R2D command.

[1098] Optionally, the second data is a D2R response command.

[1099] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[1100] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[1101] Optionally, after receiving the first signaling from the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is MSG2 in the random access process.

[1102] Optionally, the R2D command is an A-IOT paging command or an access trigger command.

[1103] Optionally, the A-IOT paging command is a retransmission of the most recent A-IOT paging command.

[1104] Optionally, after the terminal device sends the first signaling to the first device, it sends an R2D command to the third device or receives a D2R response command sent by the third device. Optionally, the first signaling is at least one of the MSG1 and RRC connection reconfiguration completion messages in the random access process.

[1105] Optionally, the terminal device communicates with the third device based on the first data or the first signaling in response to receiving the handover command. That is, before the terminal device communicates with the third device based on the first data or the first signaling, the second device performs the handover and / or data forwarding and sends the handover command to the terminal device.

[1106] Optionally, the second device initiates a handover preparation process to the first device, and the second device sends a handover request to the first device.

[1107] Optionally, the handover request includes at least one of the following: reader configuration information of the terminal device configured in the original cell, data forwarding indication, new SRB establishment indication, original device identifier, ongoing A-IoT service information, and the original device identifier list received by the second device.

[1108] Optionally, the original device identifier includes the original AS-ID and / or RRC-ID.

[1109] Optionally, the original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original Device NGAP ID list.

[1110] Optionally, the AS-ID is used to identify a third device between the terminal device and the first and / or second device.

[1111] Optionally, AS-ID is used to identify A-IoT devices between the terminal device and the original cell base station.

[1112] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the target cell base station.

[1113] Optionally, RRC-ID is used to identify a third device on the uu interface.

[1114] Optionally, RRC-ID is used to identify A-IoT devices on the uu interface.

[1115] Optionally, RRC-ID includes AS-ID.

[1116] Optionally, the RRC-ID includes the AS-ID plus the reader ID of the terminal device.

[1117] Optionally, the AS-ID and / or RRC-ID are assigned by the terminal device.

[1118] Optionally, the terminal device assigns an AS-ID and / or RRC-ID to the third device.

[1119] Optionally, the device NGAP ID is used to identify a third device on the NG port.

[1120] Optionally, the reader configuration information of the terminal device includes the radio resource configuration for the terminal device to perform A-IOT operations and / or the XnAP connection allocated for A-IOT by the access network device.

[1121] Optionally, the A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier.

[1122] Optionally, the access network equipment includes a first device and / or a second device.

[1123] Optionally, the first device receives a handover request sent by the second device.

[1124] Optionally, the first device sends a handover request confirmation message to the second device.

[1125] Optionally, the handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released.

[1126] Optionally, the second device performs the handover and / or data forwarding.

[1127] Optionally, the second device sends a switching command to the terminal device and / or sends first data to the first device.

[1128] Optionally, the handover command is an RRC reconfiguration message, meaning the handover command is sent from the second device to the terminal device via an RRC reconfiguration message.

[1129] Optionally, the first data is A-IOT data forwarded by the second device, which is the R2D command received by the second device from the core network device, such as the Command Request command.

[1130] Optionally, the first data is carried in XnAP signaling; that is, the forwarded A-IOT data is carried in XnAP signaling.

[1131] Optionally, the XnAP signaling includes at least one of the following: the source device identifier, the container of the NGAP signaling, and the command request.

[1132] Optionally, the XnAP signaling includes at least one of the following: the original RRC-ID, the original Device NGAP ID (i.e., the original device NGAP ID), a container for NGAP signaling, and an R2D command.

[1133] Alternatively, NGAP signaling can be a command request.

[1134] Optionally, XnAP signaling can be newly defined signaling or RRC transmission signaling.

[1135] Optionally, XnAP signaling is XnAP signaling oriented towards terminal devices.

[1136] Optionally, the NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of the NGAP signaling, the original Device NGAP ID, the new Device NGAPID, the command response, and the inventory report.

[1137] Optionally, the original Device NGAP ID is assigned by a second device.

[1138] Optionally, the original Device NGAP ID is assigned by the original cell base station. Alternatively, the original Device NGAP ID is assigned by the original cell base station to identify a device on the NGAP interface.

[1139] Optionally, the new Device NGAP ID is assigned by the first device.

[1140] Optionally, the new Device NGAP ID is assigned by the target cell base station. Alternatively, the new Device NGAP ID is assigned by the target cell base station to identify a device on the NGAP interface.

[1141] Optionally, if the second device finds that it cannot send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to send A-IOT data.

[1142] Alternatively, the NGAP signaling can be NAS NON DELIVERY INDICATION, or a new signaling, such as A-IOT NON DELIVERY INDICATION.

[1143] Optionally, the terminal device receives a handover command sent by the second device.

[1144] Optionally, the terminal device performs a RACH procedure to the target cell.

[1145] Optionally, the RACH procedure can be a CFRA procedure or a CBRA procedure.

[1146] Optionally, after completing the RACH process, the terminal device sends a cell handover completion message to the first device.

[1147] Optionally, the cell handover completion message is an RRC connection reconfiguration completion message (RRCReconfigurationComplete message).

[1148] Optionally, after receiving the first data (i.e., the R2D command from the core network device) sent by the second device from the core network device, the first device sends a path switch request message to the core network device.

[1149] Optionally, the path switching request message includes the original Device NGAP ID and / or the new Device NGAP ID.

[1150] Optionally, the core network device sends a path switching request response message to the first device.

[1151] Optionally, the terminal device and the first device transmit data via RRC signaling.

[1152] Optionally, the RRC signaling includes the original device identifier and / or the new device identifier.

[1153] Optionally, RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and a new SRB.

[1154] Optionally, the first device sends the first data to the terminal device via RRC signaling.

[1155] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID.

[1156] Optionally, the first device may also instruct the terminal device whether it has completed forwarding the A-IoT data transmission from the second device.

[1157] Optionally, the terminal device receives a first data forwarding completion indication sent by the first device.

[1158] Optionally, the terminal device sends the first data to the third device.

[1159] Optionally, the terminal device receives second data sent by the third device.

[1160] Optionally, the second data is sent to the first device via RRC signaling.

[1161] Optionally, the terminal device sends second data to the first device via RRC signaling.

[1162] Optionally, if a new SRB is established, the target cell base station uses the new SRB to transmit the RRC signaling; otherwise, if no new SRB is established, the target cell base station uses SRB1, SRB2, or SRB4 to transmit the RRC signaling. Optionally, the RRC signaling includes the original RRC-ID and / or the new RRC-ID.

[1163] Optionally, the first device sends the second data to the core network device.

[1164] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling. Optionally, the NGAP signaling also includes a new Device NGAP ID.

[1165] Optionally, the first device may save the new device identifier and / or discard the original device identifier.

[1166] Optionally, the first device saves the new RRC-ID and / or discards the original RRC-ID.

[1167] Optionally, after receiving the second data, the first device sends the second data to the second device.

[1168] Optionally, the second data is carried in XnAP signaling, that is, the second data is forwarded from the first device to the second device by the first device through XnAP signaling.

[1169] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[1170] Optionally, XnAP signaling can be a Command Response / inventory report.

[1171] Optionally, after receiving the second data, the first device sends an NGAP ID request message to the second device.

[1172] Optionally, the original device NGAP ID request message carries the original AS-ID and / or the reader ID of the terminal device.

[1173] Optionally, the original device NGAP ID request message carries the RRC-ID.

[1174] Optionally, the first device receives the original Device NGAP ID message sent by the second device;

[1175] Optionally, the original Device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device.

[1176] Optionally, the original Device NGAP ID message carries the original RRC-ID.

[1177] Optionally, the first device sends the second data to the core network device.

[1178] Optionally, the second data is a D2R command from the terminal device, such as a Command Response / Inventory Report command.

[1179] Optionally, XnAP signaling can be a Command Response / inventory report.

[1180] Optionally, the second data is carried in XnAP signaling.

[1181] Optionally, the second data is forwarded by the first device to the core network device via NGAP signaling.

[1182] Optionally, the NGAP signaling also includes the original Device NGAP ID and the new Device NGAP ID.

[1183] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[1184] Optionally, after receiving the second data, the first device obtains the original Device NGAP ID based on the original device identifier and / or the original device identifier list.

[1185] Optionally, the first device obtains the original Device NGAP-ID based on the original RRC-ID carried by the terminal device and the original RRC-ID list and original device NGAP-ID list obtained from the second device in the handover request message, and then carries the second data (i.e. the forwarded A-IOT data) in the NGAP signaling.

[1186] Optionally, the NGAP signaling also includes the original Device NGAP-ID and the new Device NGAP-ID.

[1187] Optionally, the new Device NGAP-ID is assigned to the device by the first device and is used to uniquely identify a device on the NGAP interface.

[1188] Optionally, the first device saves the new Device NGAP-ID and the new RRC-ID together.

[1189] Optionally, the terminal device can restart the A-IoT service after the handover is complete.

[1190] Optionally, after the terminal device completes the handover process, such as sending an RRCReconfigurationComplete message to the target cell, it restarts the A-IOT service and begins transmitting access trigger messages or A-IOT paging messages to the device.

[1191] Optionally, in this embodiment, among all devices that were accessed by the previous access trigger message, those that did not complete their tasks are considered to have failed to access and are prepared to receive a re-access trigger command, such as an A-IOT paging message.

[1192] Through the technical solution of this embodiment, the core network device sends first data or first signaling, so that the second device sends first data or first signaling to the terminal device via the first device. The terminal device communicates with the third device based on the first data or first signaling. This can improve the existing A-IoT processing mechanism, so as to support ensuring the continuity of A-IoT services and / or avoid data loss during the process of the terminal device performing A-IoT operations as a reader.

[1193] Ninth Embodiment

[1194] Please refer to Figure 17, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This device can be mounted on or is the terminal device in the above method embodiments. The communication device shown in Figure 17 can be used to perform some or all of the functions in the method embodiments described above. As shown in Figure 17, the communication device 140 includes:

[1195] The first communication module 1401 is used to communicate with a third device based on first data or first signaling.

[1196] Optionally, the communication device further includes at least one of the following:

[1197] Optionally, the first data is sent from the second device to the first device.

[1198] Optionally, before communicating with the third device based on the first data or the first signaling, the method further includes:

[1199] Receive the first data sent by the first device.

[1200] Optionally, communication with a third device based on the first data includes at least one of the following:

[1201] Send the first data to the third device;

[1202] Receive the second data sent by the third device.

[1203] Optionally, the terminal device communicates with the third device based on the first signaling, including:

[1204] After receiving or sending the first signaling to the first device, the communication device sends an R2D command to the third device or receives a D2R response command from the third device. Optionally, the communication device further includes at least one of the following:

[1205] The first data is sent to the first device when the second device performs the handover;

[1206] The first data is sent by the first device based on a cell handover message.

[1207] The first data is A-IOT data;

[1208] The second data is the A-IOT response signaling;

[1209] The first data is sent from the core network equipment to the second equipment;

[1210] The first data is an R2D command;

[1211] The second data is the D2R response command;

[1212] R2D commands are A-IOT paging commands or access trigger commands;

[1213] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[1214] The first device is the target cell base station;

[1215] The second device is the original cell base station;

[1216] The third device is an A-IOT device.

[1217] Optionally, the communication device further includes at least one of the following:

[1218] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[1219] The second device sends a handover request to the first device;

[1220] The first device receives a handover request sent by the second device;

[1221] The first device sends a handover request confirmation message to the second device;

[1222] The second device performs the handover and / or data forwarding;

[1223] Receive the switching command sent by the second device;

[1224] The second device sends the first data to the first device;

[1225] The first device receives the first data sent by the second device;

[1226] Perform the RACH procedure on the target cell;

[1227] Send a cell handover completion message to the first device;

[1228] The first device sends a path switching request message to the core network device;

[1229] Receive the first data sent by the first device;

[1230] Send the second data to the first device;

[1231] The first device sends the second data to the second device;

[1232] The first device sends the second data to the core network device;

[1233] If the second device fails to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the AMF has failed to transmit A-IoT data. Optionally, the communication device further includes at least one of the following:

[1234] The handover command is sent by the second device via an RRC reconfiguration message;

[1235] The switching commands include A-IOT data reporting instructions;

[1236] The first data is carried in the XnAP signaling;

[1237] The second data is sent to the first device via RRC signaling;

[1238] The second data is forwarded from the first device to the second device via XnAP signaling;

[1239] The second data is forwarded by the first device to the core network device via NGAP signaling;

[1240] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[1241] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[1242] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[1243] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[1244] Optionally, the communication device further includes at least one of the following:

[1245] Assign AS-ID and / or RRC-ID to the third device;

[1246] Receive the first data forwarding completion indication sent by the first device;

[1247] The first device retains the new device identifier and / or discards the original device identifier;

[1248] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[1249] The first device sends a message to the second device requesting the original device's NGAP ID;

[1250] The first device receives the original device NGAP ID message sent by the second device;

[1251] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[1252] Restart the A-IOT service after the switch is complete.

[1253] Optionally, the communication device further includes at least one of the following:

[1254] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[1255] RRC signaling includes the original device identifier and / or the new device identifier;

[1256] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[1257] XnAP signaling is either new signaling or RRC transmission signaling;

[1258] The original equipment identification includes the original AS-ID and / or RRC-ID;

[1259] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[1260] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[1261] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[1262] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[1263] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[1264] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[1265] RRC-ID is used to identify a third device on the UU interface;

[1266] RRC-ID includes AS-ID;

[1267] The device NGAP ID is used to identify a third device on the NG port;

[1268] The original device's NGAP ID is assigned by the second device;

[1269] The new device's NGAP ID is assigned by the first device.

[1270] The communication device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[1271] Tenth Embodiment

[1272] Please refer to Figure 18, which is a second structural schematic diagram of the communication device provided in the embodiment of this application. This device can be mounted on or is the first device (such as a base station) in the above method embodiment. The communication device shown in Figure 18 can be used to perform some or all of the functions in the method embodiment described in the above embodiment. As shown in Figure 18, the communication device 150 includes:

[1273] The second communication module 1501 is used to send first data or first signaling so that the terminal device can communicate with the third device based on the first data or first signaling.

[1274] Optionally, the communication device further includes at least one of the following:

[1275] Receive the first data sent by the second device;

[1276] The terminal device communicates with the third device based on the first signaling, including:

[1277] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[1278] The terminal device communicates with the third device based on the first data, including at least one of the following:

[1279] The terminal device sends the first data to the third device;

[1280] The terminal device receives the second data sent by the third device.

[1281] Optionally, the communication device further includes at least one of the following:

[1282] The first data is sent to the first device when the second device performs the handover;

[1283] The first data is sent by the first device based on a cell handover message.

[1284] The first data is A-IOT data;

[1285] The second data is the A-IOT response signaling;

[1286] The first data is sent from the core network equipment to the second equipment;

[1287] The first data is an R2D command;

[1288] The second data is the D2R response command;

[1289] R2D commands are A-IOT paging commands or access trigger commands;

[1290] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[1291] The first device is the target cell base station;

[1292] The second device is the original cell base station;

[1293] The third device is an A-IOT device.

[1294] Optionally, the communication device further includes at least one of the following:

[1295] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[1296] Receive a handover request sent by the second device;

[1297] Send a handover request confirmation message to the second device;

[1298] The second device performs the handover and / or data forwarding;

[1299] The second device sends a handover command to the terminal device;

[1300] The terminal device receives a handover command sent by the second device;

[1301] Receive the first data sent by the second device;

[1302] The terminal device executes the RACH procedure to the target cell;

[1303] Receive the cell handover completion message sent by the terminal device;

[1304] Send a path switching request message to the core network equipment;

[1305] Receive the second data sent by the terminal device;

[1306] Send the second data to the second device;

[1307] Send the second data to the core network equipment;

[1308] If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed.

[1309] Optionally, the communication device further includes at least one of the following:

[1310] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[1311] The switching commands include A-IOT data reporting instructions;

[1312] The first data is carried in the XnAP signaling;

[1313] Receive the second data via RRC signaling;

[1314] The second data is forwarded to the second device via XnAP signaling;

[1315] The second data is forwarded to the core network equipment via XnAP signaling;

[1316] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[1317] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[1318] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[1319] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[1320] Optionally, the communication device further includes at least one of the following:

[1321] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[1322] Send the first data forwarding completion indication to the terminal device;

[1323] Save the new device identifier and / or discard the original device identifier;

[1324] Save the original device NGAP ID and / or the new device NGAP ID;

[1325] Send a message to the second device requesting the original device's NGAP ID;

[1326] Receive the original device NGAP ID message sent by the second device;

[1327] Obtain the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[1328] The terminal device restarts the A-IoT service after the switchover is complete.

[1329] Optionally, the communication device further includes at least one of the following:

[1330] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[1331] RRC signaling includes the original device identifier and / or the new device identifier;

[1332] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[1333] XnAP signaling is either new signaling or RRC transmission signaling;

[1334] The original equipment identification includes the original AS-ID and / or RRC-ID;

[1335] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[1336] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[1337] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[1338] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[1339] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[1340] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[1341] RRC-ID is used to identify a third device on the UU interface;

[1342] RRC-ID includes AS-ID;

[1343] The device NGAP ID is used to identify a third device on the NG port;

[1344] The original device's NGAP ID is assigned by the second device;

[1345] The new device's NGAP ID is assigned by the first device.

[1346] The communication device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[1347] Eleventh Embodiment

[1348] Please refer to Figure 19, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This device can be mounted on or is the second device (such as a base station) in the above method embodiments. The communication device shown in Figure 19 can be used to perform some or all of the functions described in the method embodiments above. As shown in Figure 19, the communication device 160 includes:

[1349] The third communication module 1601 is used to send first data or first signaling to enable the first device to send the first data or first signaling to the terminal device, and the terminal device to communicate with the third device based on the first data or first signaling.

[1350] Optionally, the communication device further includes at least one of the following:

[1351] Receive the first data or first signaling sent by the core network equipment;

[1352] The terminal device communicates with the third device based on the first signaling, including:

[1353] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[1354] The terminal device communicates with the third device based on the first data, including at least one of the following:

[1355] The terminal device sends the first data to the third device;

[1356] The terminal device receives the second data sent by the third device.

[1357] Optionally, the communication device further includes at least one of the following:

[1358] The first data is sent to the first device when the second device performs the handover;

[1359] The first data is sent by the first device to the terminal device based on the cell handover completion message;

[1360] The first data is A-IOT data;

[1361] The second data is the A-IOT response signaling;

[1362] The first data is an R2D command;

[1363] The second data is the D2R response command;

[1364] R2D commands are A-IOT paging commands or access trigger commands;

[1365] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[1366] The first device is the target cell base station;

[1367] The second device is the original cell base station;

[1368] The third device is an A-IOT device.

[1369] Optionally, the communication device further includes at least one of the following:

[1370] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[1371] Send a handover request to the first device;

[1372] The first device sends a handover request confirmation message to the second device;

[1373] Perform handover and / or data forwarding;

[1374] Send a switching command to the first device;

[1375] The first device performs the RACH procedure to the target cell;

[1376] The terminal device sends a cell handover completion message to the first device;

[1377] The first device sends a path switching request message to the core network device;

[1378] The terminal device sends second data to the first device;

[1379] Receive the second data sent by the first device;

[1380] The first device sends the second data to the core network device;

[1381] If the first data cannot be sent to the terminal device, an NGAP signaling message is sent to the AMF to indicate that the AMF has failed to send A-IOT data.

[1382] Optionally, the communication device further includes at least one of the following:

[1383] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[1384] The switching commands include A-IOT data reporting instructions;

[1385] The first data is carried in the XnAP signaling;

[1386] The second data is sent from the terminal device to the first device via RRC signaling;

[1387] The second data is forwarded from the first device to the second device via XnAP signaling;

[1388] The second data is forwarded by the first device to the core network device via NGAP signaling;

[1389] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[1390] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[1391] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[1392] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[1393] Optionally, the communication device further includes at least one of the following:

[1394] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[1395] The first device retains the new device identifier and / or discards the original device identifier;

[1396] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[1397] Receive the original device NGAP ID request message sent by the first device;

[1398] Send the original device NGAP ID message to the first device;

[1399] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[1400] The terminal device restarts the A-IoT service after the switchover is complete.

[1401] Optionally, the communication device further includes at least one of the following:

[1402] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[1403] RRC signaling includes the original device identifier and / or the new device identifier;

[1404] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[1405] XnAP signaling is either new signaling or RRC transmission signaling;

[1406] The original equipment identification includes the original AS-ID and / or RRC-ID;

[1407] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[1408] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[1409] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[1410] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[1411] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[1412] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[1413] RRC-ID is used to identify a third device on the UU interface;

[1414] RRC-ID includes AS-ID;

[1415] The device NGAP ID is used to identify a third device on the NG port;

[1416] The original device's NGAP ID is assigned by the second device;

[1417] The new device's NGAP ID is assigned by the first device.

[1418] The communication device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[1419] Twelfth Embodiment

[1420] Please refer to Figure 20, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This device can be mounted on or is the core network device in the above method embodiments. The communication device shown in Figure 20 can be used to perform some or all of the functions described in the method embodiments above. As shown in Figure 20, the device 170 includes:

[1421] The fourth communication module 1701 is used to send first data or first signaling so that the second device sends the first data or first signaling to the terminal device via the first device, and the terminal device communicates with the third device based on the first data or first signaling.

[1422] Optionally, the communication device further includes at least one of the following:

[1423] The terminal device communicates with the third device based on the first signaling, including:

[1424] After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device.

[1425] The terminal device communicates with the third device based on the first data, including at least one of the following:

[1426] The terminal device sends the first data to the third device;

[1427] The terminal device receives the second data sent by the third device.

[1428] Optionally, the communication device further includes at least one of the following:

[1429] The first data is sent to the first device when the second device performs the handover;

[1430] The first data is sent by the first device to the terminal device based on the cell handover completion message;

[1431] The first data is A-IOT data;

[1432] The second data is the A-IOT response signaling;

[1433] The first data is an R2D command;

[1434] The second data is the D2R response command;

[1435] R2D commands are A-IOT paging commands or access trigger commands;

[1436] The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure;

[1437] The first device is the target cell base station;

[1438] The second device is the original cell base station;

[1439] The third device is an A-IOT device.

[1440] Optionally, the communication device further includes at least one of the following:

[1441] An A-IOT paging command is a retransmission of the most recent A-IOT paging command;

[1442] The second device sends a handover request to the first device;

[1443] The first device sends a handover request confirmation message to the second device;

[1444] The second device performs the handover and / or data forwarding;

[1445] The terminal device receives a handover command sent by the second device;

[1446] The terminal device executes the RACH procedure to the target cell;

[1447] The terminal device sends a cell handover completion message to the first device;

[1448] Receive the path switching request message sent by the first device;

[1449] The terminal device sends second data to the first device;

[1450] The first device sends the second data to the second device;

[1451] Receive the second data sent by the first device;

[1452] If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed.

[1453] Optionally, the communication device further includes at least one of the following:

[1454] The handover command is sent from the second device to the terminal device via an RRC reconfiguration message;

[1455] The switching commands include A-IOT data reporting instructions;

[1456] The first data is carried in the XnAP signaling;

[1457] The second data is sent to the first device via RRC signaling;

[1458] The second data is forwarded from the first device to the second device via XnAP signaling;

[1459] The second data is forwarded by the first device to the core network device via NGAP signaling;

[1460] The RACH procedure can be either a CFRA procedure or a CBRA procedure.

[1461] The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device;

[1462] The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released;

[1463] The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID.

[1464] Optionally, the communication device further includes at least one of the following:

[1465] The terminal device assigns an AS-ID and / or RRC-ID to the third device;

[1466] The first device retains the new device identifier and / or discards the original device identifier;

[1467] The first device stores the original device's NGAP ID and / or the new device's NGAP ID;

[1468] The first device sends a message to the second device requesting the original device's NGAP ID;

[1469] The first device receives the original device NGAP ID message sent by the second device;

[1470] The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list;

[1471] The terminal device restarts the A-IoT service after the switchover is complete.

[1472] Optionally, the communication device further includes at least one of the following:

[1473] RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB;

[1474] RRC signaling includes the original device identifier and / or the new device identifier;

[1475] XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request;

[1476] XnAP signaling is either new signaling or RRC transmission signaling;

[1477] The original equipment identification includes the original AS-ID and / or RRC-ID;

[1478] The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list;

[1479] NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report;

[1480] A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier;

[1481] The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID;

[1482] The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device;

[1483] AS-ID is used to identify a third device between the terminal device and the first and / or second device;

[1484] RRC-ID is used to identify a third device on the UU interface;

[1485] RRC-ID includes AS-ID;

[1486] The device NGAP ID is used to identify a third device on the NG port;

[1487] The original device's NGAP ID is assigned by the second device;

[1488] The new device's NGAP ID is assigned by the first device.

[1489] The communication device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[1490] Referring to Figure 21, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application, the communication device 180 described in this embodiment may be a terminal device (or a component that can be used in a terminal device) or a first device, a second device, or a core network device (or a component that can be used in a first device, a second device, or a core network device) mentioned in the foregoing method embodiments. The communication device 180 can be used to implement the methods described in the above method embodiments corresponding to the terminal device, the first device, the second device, or the core network device, as detailed in the descriptions in the above method embodiments.

[1491] The communication device 180 may include one or more processors 1801, which may also be referred to as processing units, and can perform certain control or processing functions. The processor 1801 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[1492] Optionally, the processor 1801 may also store instructions 1803 or data (e.g., intermediate data). Optionally, instructions 1803 may be executed by the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments corresponding to the terminal device, the first device, the second device, or the core network device.

[1493] Optionally, the communication device 180 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[1494] Optionally, the communication device 180 may include one or more memories 1802, which may store instructions 1804 that can be executed on the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments.

[1495] Alternatively, the memory 1802 may also store data. The processor 1801 and the memory 1802 can be configured separately or integrated together.

[1496] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801, which may be referred to as a processing unit, controls the communication device 180 (terminal device, first device, second device, or core network device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transceiver functions of the communication device 180.

[1497] Optionally, if the communication device 180 is used to implement the operation corresponding to the terminal device in the above embodiments, for example, the transceiver 1805 may receive the first data or the first signaling; and / or the processor 1801 may communicate with the third device based on the first data or the first signaling.

[1498] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[1499] Optionally, if the communication device 180 is used to implement the operation corresponding to the first device in the above embodiments, for example, the transceiver 1805 can send the first data or the first signaling.

[1500] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[1501] The processor 1801 and transceiver 1805 described in this application can be implemented on ICs (Integrated Circuits), analog integrated circuits, RFICs (Radio Frequency Integrated Circuits), mixed-signal integrated circuits, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N-Metal-Oxide-Semiconductor), PMOS (Positive channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[1502] In this application, the communication equipment can be a terminal device (such as a mobile phone), a first device (such as a base station), a second device (such as a base station), or a core network device (such as a CN), depending on the context. Furthermore, the terminal device can be implemented in various forms. For example, the terminal devices described in this application can include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[1503] Although the communication device is described in the above embodiments as a terminal device, a first device, a second device, or a core network device, the scope of the communication device described in this application is not limited to the aforementioned terminal device, first device, second device, or core network device, and the structure of the communication device is not limited to FIG21. The communication device can be a standalone device or can be part of a larger device.

[1504] This application also provides a communication system, including: a terminal device as described in any of the above embodiments; and / or, a first device, a second device, or a core network device as described in any of the above embodiments.

[1505] This application also provides a communication device, including a memory and a processor. The memory stores a communication program, and when the communication program is executed by the processor, it implements the steps of the communication method in any of the above embodiments.

[1506] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a first device (such as a base station), a core network device, or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

[1507] This application also provides a computer-readable storage medium storing a communication program, which, when executed by a processor, implements the steps of the communication method in any of the above embodiments.

[1508] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described communication method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.

[1509] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[1510] This application also provides a chip, including a memory and a processor. The memory is used to store a communication program, and the processor is used to call and run the communication program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[1511] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[1512] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[1513] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[1514] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[1515] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[1516] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[1517] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[1518] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the methods of each embodiment of this application.

[1519] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[1520] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

A communication method, wherein, Applied to terminal devices, including the following steps: S3: Communicate with a third device based on the first data or the first signaling. According to the method of claim 1, wherein, The first data is sent from the second device to the first device; and / or, Before step S3, the following are also included: Receive the first data sent by the first device; Communicating with a third device based on first data includes at least one of the following: Send the first data to the third device; Receive the second data sent by the third device. According to the method of claim 1, wherein, Communication with a third device based on the first signaling includes: After receiving the first signaling or sending the first signaling to the first device, send an R2D command to the third device or receive a D2R response command sent by the third device. The method according to claim 2 or 3, wherein, It also includes at least one of the following: The first data is sent to the first device when the second device performs the handover; The first data is sent by the first device based on a cell handover message. The first data is A-IOT data; The second data is the A-IOT response signaling; The first data is sent from the core network equipment to the second equipment; The first data is an R2D command; The second data is the D2R response command; R2D commands are A-IOT paging commands or access trigger commands; The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure; The first device is the target cell base station; The second device is the original cell base station; The third device is an A-IOT device. The method according to claim 4, wherein, It also includes at least one of the following: An A-IOT paging command is a retransmission of the most recent A-IOT paging command; The second device sends a handover request to the first device; The first device receives a handover request sent by the second device; The first device sends a handover request confirmation message to the second device; The second device performs the handover and / or data forwarding; Receive the switching command sent by the second device; The second device sends the first data to the first device; The first device receives the first data sent by the second device; Perform the RACH procedure on the target cell; Send a cell handover completion message to the first device; The first device sends a path switching request message to the core network device; Receive the first data sent by the first device; Send the second data to the first device; The first device sends the second data to the second device; The first device sends the second data to the core network device; If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed. The method according to claim 5, wherein, It also includes at least one of the following: The handover command is sent by the second device via an RRC reconfiguration message; The first data is carried in the XnAP signaling; The second data is sent to the first device via RRC signaling; The second data is forwarded from the first device to the second device via XnAP signaling; The second data is forwarded by the first device to the core network device via NGAP signaling; The RACH procedure can be either a CFRA procedure or a CBRA procedure. The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device; The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released; The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID. The method according to claim 6, wherein, It also includes at least one of the following: Assign AS-ID and / or RRC-ID to the third device; Receive the first data forwarding completion indication sent by the first device; The first device retains the new device identifier and / or discards the original device identifier; The first device stores the original device's NGAP ID and / or the new device's NGAP ID; The first device sends a message to the second device requesting the original device's NGAP ID; The first device receives the original device NGAP ID message sent by the second device; The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list; Restart the A-IOT service after the switch is complete. The method according to claim 7, wherein, It also includes at least one of the following: RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; RRC signaling includes the original device identifier and / or the new device identifier; XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request; XnAP signaling is either new signaling or RRC transmission signaling; The original equipment identification includes the original AS-ID and / or RRC-ID; The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list; NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID; The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device; AS-ID is used to identify a third device between the terminal device and the first and / or second device; RRC-ID is used to identify a third device on the UU interface; RRC-ID includes AS-ID; The device NGAP ID is used to identify a third device on the NG port; The original device's NGAP ID is assigned by the second device; The new device's NGAP ID is assigned by the first device. A communication method, wherein, Applied to the first device, including the following steps: S2: Send first data or first signaling to enable the terminal device to communicate with the third device based on the first data or first signaling. The method according to claim 9, wherein, It also includes at least one of the following: Receive the first data sent by the second device; The terminal device communicates with the third device based on the first signaling, including: After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. The terminal device communicates with the third device based on the first data, including at least one of the following: The terminal device sends the first data to the third device; The terminal device receives the second data sent by the third device. The method according to claim 10, wherein, It also includes at least one of the following: The first data is sent to the first device when the second device performs the handover; The first data is sent by the first device based on a cell handover message. The first data is A-IOT data; The second data is the A-IOT response signaling; The first data is sent from the core network equipment to the second equipment; The first data is an R2D command; The second data is the D2R response command; R2D commands are A-IOT paging commands or access trigger commands; The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure; The first device is the target cell base station; The second device is the original cell base station; The third device is an A-IOT device. The method according to claim 11, wherein, It also includes at least one of the following: An A-IOT paging command is a retransmission of the most recent A-IOT paging command; Receive a handover request sent by the second device; Send a handover request confirmation message to the second device; The second device performs the handover and / or data forwarding; The second device sends a handover command to the terminal device; The terminal device receives a handover command sent by the second device; Receive the first data sent by the second device; The terminal device executes the RACH procedure to the target cell; Receive the cell handover completion message sent by the terminal device; Send a path switching request message to the core network equipment; Receive the second data sent by the terminal device; Send the second data to the second device; Send the second data to the core network equipment; If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed. The method according to claim 12, wherein, It also includes at least one of the following: The handover command is sent from the second device to the terminal device via an RRC reconfiguration message; The first data is carried in the XnAP signaling; Receive the second data via RRC signaling; The second data is forwarded to the second device via XnAP signaling; The second data is forwarded to the core network equipment via XnAP signaling; The RACH procedure can be either a CFRA procedure or a CBRA procedure. The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device; The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released; The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID. The method according to claim 13, wherein, It also includes at least one of the following: The terminal device assigns an AS-ID and / or RRC-ID to the third device; Send the first data forwarding completion indication to the terminal device; Save the new device identifier and / or discard the original device identifier; Save the original device NGAP ID and / or the new device NGAP ID; Send a message to the second device requesting the original device's NGAP ID; Receive the original device NGAP ID message sent by the second device; Obtain the original device NGAP ID based on the original device identifier and / or the original device identifier list; The terminal device restarts the A-IoT service after the switchover is complete. The method according to claim 14, wherein, It also includes at least one of the following: RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; RRC signaling includes the original device identifier and / or the new device identifier; XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request; XnAP signaling is either new signaling or RRC transmission signaling; The original equipment identification includes the original AS-ID and / or RRC-ID; The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list; NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID; The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device; AS-ID is used to identify a third device between the terminal device and the first and / or second device; RRC-ID is used to identify a third device on the UU interface; RRC-ID includes AS-ID; The device NGAP ID is used to identify a third device on the NG port; The original device's NGAP ID is assigned by the second device; The new device's NGAP ID is assigned by the first device. A communication method, wherein, Applied to a second device, including the following steps: S1: Send first data or first signaling to enable the first device to send the first data or first signaling to the terminal device, and the terminal device to communicate with the third device based on the first data or first signaling. The method according to claim 16, wherein, It also includes at least one of the following: Receive the first data or first signaling sent by the core network equipment; The terminal device communicates with the third device based on the first signaling, including: After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. The terminal device communicates with the third device based on the first data, including at least one of the following: The terminal device sends the first data to the third device; The terminal device receives the second data sent by the third device. The method according to claim 17, wherein, It also includes at least one of the following: The first data is sent to the first device when the second device performs the handover; The first data is sent by the first device to the terminal device based on the cell handover completion message; The first data is A-IOT data; The second data is the A-IOT response signaling; The first data is an R2D command; The second data is the D2R response command; R2D commands are A-IOT paging commands or access trigger commands; The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure; The first device is the target cell base station; The second device is the original cell base station; The third device is an A-IOT device. The method according to claim 18, wherein, It also includes at least one of the following: An A-IOT paging command is a retransmission of the most recent A-IOT paging command; Send a handover request to the first device; The first device sends a handover request confirmation message to the second device; Perform handover and / or data forwarding; Send a switching command to the first device; The first device performs the RACH procedure to the target cell; The terminal device sends a cell handover completion message to the first device; The first device sends a path switching request message to the core network device; The terminal device sends second data to the first device; Receive the second data sent by the first device; The first device sends the second data to the core network device; If the first data cannot be sent to the terminal device, an NGAP signaling message is sent to the AMF to indicate that the AMF has failed to send A-IOT data. The method according to claim 19, wherein, It also includes at least one of the following: The handover command is sent from the second device to the terminal device via an RRC reconfiguration message; The first data is carried in the XnAP signaling; The second data is sent from the terminal device to the first device via RRC signaling; The second data is forwarded from the first device to the second device via XnAP signaling; The second data is forwarded by the first device to the core network device via NGAP signaling; The RACH procedure can be either a CFRA procedure or a CBRA procedure. The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device; The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released; The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID. The method according to claim 20, wherein, It also includes at least one of the following: The terminal device assigns an AS-ID and / or RRC-ID to the third device; The first device retains the new device identifier and / or discards the original device identifier; The first device stores the original device's NGAP ID and / or the new device's NGAP ID; Receive the original device NGAP ID request message sent by the first device; Send the original device NGAP ID message to the first device; The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list; The terminal device restarts the A-IoT service after the switchover is complete. The method according to claim 21, wherein, It also includes at least one of the following: RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; RRC signaling includes the original device identifier and / or the new device identifier; XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request; XnAP signaling is either new signaling or RRC transmission signaling; The original equipment identification includes the original AS-ID and / or RRC-ID; The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list; NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID; The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device; AS-ID is used to identify a third device between the terminal device and the first and / or second device; RRC-ID is used to identify a third device on the UU interface; RRC-ID includes AS-ID; The device NGAP ID is used to identify a third device on the NG port; The original device's NGAP ID is assigned by the second device; The new device's NGAP ID is assigned by the first device. A communication method, wherein, Applied to core network equipment, including the following steps: S0: Send first data or first signaling to enable the second device to send the first data or first signaling to the terminal device via the first device, and the terminal device to communicate with the third device based on the first data or first signaling. The method according to claim 23, wherein, It also includes at least one of the following: The terminal device communicates with the third device based on the first signaling, including: After receiving the first signaling or sending the first signaling to the first device, the terminal device sends an R2D command to the third device or receives a D2R response command sent by the third device. The terminal device communicates with the third device based on the first data, including at least one of the following: The terminal device sends the first data to the third device; The terminal device receives the second data sent by the third device. The method according to claim 24, wherein, It also includes at least one of the following: The first data is sent to the first device when the second device performs the handover; The first data is sent by the first device to the terminal device based on the cell handover completion message; The first data is A-IOT data; The second data is the A-IOT response signaling; The first data is an R2D command; The second data is the D2R response command; R2D commands are A-IOT paging commands or access trigger commands; The first signaling message is at least one of the MSG1, MSG2 and RRC connection reconfiguration completion messages in the random access procedure; The first device is the target cell base station; The second device is the original cell base station; The third device is an A-IOT device. The method according to claim 25, wherein, It also includes at least one of the following: An A-IOT paging command is a retransmission of the most recent A-IOT paging command; The second device sends a handover request to the first device; The first device sends a handover request confirmation message to the second device; The second device performs the handover and / or data forwarding; The terminal device receives a handover command sent by the second device; The terminal device executes the RACH procedure to the target cell; The terminal device sends a cell handover completion message to the first device; Receive the path switching request message sent by the first device; The terminal device sends second data to the first device; The first device sends the second data to the second device; Receive the second data sent by the first device; If the second device is unable to send the first data to the terminal device, it sends an NGAP signaling message to the AMF to indicate that the A-IOT data transmission has failed. The method according to claim 26, wherein, It also includes at least one of the following: The handover command is sent from the second device to the terminal device via an RRC reconfiguration message; The first data is carried in the XnAP signaling; The second data is sent to the first device via RRC signaling; The second data is forwarded from the first device to the second device via XnAP signaling; The second data is forwarded by the first device to the core network device via NGAP signaling; The RACH procedure can be either a CFRA procedure or a CBRA procedure. The handover request includes at least one of the following: the reader configuration information of the terminal device configured in the original cell, the data forwarding instruction, the new SRB establishment instruction, the original device identifier, the ongoing A-IoT service information, and the original device identifier list received by the second device; The handover request confirmation message includes at least one of the following: reader configuration information of the terminal device, indication that the reader configuration information of the terminal device configured in the original cell remains valid, and indication that the reader configuration information of the terminal device configured in the original cell is released; The path switching request message includes the original device's NGAP ID and / or the new device's NGAP ID. The method according to claim 27, wherein, It also includes at least one of the following: The terminal device assigns an AS-ID and / or RRC-ID to the third device; The first device retains the new device identifier and / or discards the original device identifier; The first device stores the original device's NGAP ID and / or the new device's NGAP ID; The first device sends a message to the second device requesting the original device's NGAP ID; The first device receives the original device NGAP ID message sent by the second device; The first device obtains the original device NGAP ID based on the original device identifier and / or the original device identifier list; The terminal device restarts the A-IoT service after the switchover is complete. The method according to claim 28, wherein, It also includes at least one of the following: RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; RRC signaling includes the original device identifier and / or the new device identifier; XnAP signaling includes at least one of the following: native device identifier, container for NGAP signaling, and command request; XnAP signaling is either new signaling or RRC transmission signaling; The original equipment identification includes the original AS-ID and / or RRC-ID; The original device identifier list includes at least one of the original AS-ID list, RRC-ID list, and original device NGAP ID list; NGAP signaling includes at least one of the following: the original AS-ID, the reader ID of the terminal device, the container of NGAP signaling, the original device NGAP ID, the new device NGAP ID, the command response, and the inventory report; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The original device's NGAP ID request message carries the original AS-ID and / or the terminal device's reader ID; The original device NGAP ID message carries the original AS-ID and / or the reader ID of the terminal device; AS-ID is used to identify a third device between the terminal device and the first and / or second device; RRC-ID is used to identify a third device on the UU interface; RRC-ID includes AS-ID; The device NGAP ID is used to identify a third device on the NG port; The original device's NGAP ID is assigned by the second device; The new device's NGAP ID is assigned by the first device. A communication device, wherein, include: A memory and a processor, wherein the memory stores a communication program, and the communication program, when executed by the processor, implements the communication method as described in claim 1, 9, 16 or 23. A computer-readable storage medium, wherein, The computer-readable storage medium stores a communication program, which, when executed by a processor, implements the communication method as described in claim 1, 9, 16, or 23.

Images