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: in response to receiving a handover command, a terminal device sending first data to a first device, such that the first device sends the first data to a second device. The technical solution of the present application can refine an existing A-IoT processing mechanism, such that a terminal device supports, during the process of executing an A-IoT operation as a reader, ensuring the continuity of an A-IoT service and / or avoiding data loss.

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 UE 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, which may affect the continuity of A-IoT services.

[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] S2: In response to receiving a handover command, send first data to the first device so that the first device sends the first data to the second device.

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

[0011] The first data is the A-IOT response signaling;

[0012] The primary data source is A-IoT devices;

[0013] The switching command is sent by the first device;

[0014] The switching command is sent by the second device;

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

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

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

[0018] The first data is sent from the first device to the second device via XnAP signaling;

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

[0020] The second device is the original cell base station.

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

[0022] RRC signaling includes the original device identifier;

[0023] XnAP signaling includes the original device identifier;

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

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

[0026] Send an A-IoT data transmission completion indication to the first device;

[0027] Receive A-IOT data sent by the first device via RRC signaling;

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

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

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

[0031] The second device sends an A-IoT service release instruction to the core network device;

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

[0033] The first device sends the first data to the original cell via XnAP signaling;

[0034] The first device receives the path switching response message sent by the core network device;

[0035] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

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

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

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

[0039] Original equipment identification includes AS-ID and / or RRC-ID;

[0040] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0041] 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;

[0042] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0043] The reader configuration 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.

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

[0045] RRC-ID includes AS-ID;

[0046] RRC-ID is used to identify A-IoT devices on the UU interface;

[0047] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0048] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0050] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0051] Access network equipment includes a first device and / or a second device.

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

[0053] S1: In response to receiving a handover request, obtain first data from the terminal device and send it to the second device.

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

[0055] The first data is the A-IOT response signaling;

[0056] The primary data source is A-IoT devices;

[0057] The first data is sent by the terminal device based on the handover command;

[0058] The handover request was sent by the second device;

[0059] Send a switching command to the terminal device;

[0060] Receive the first data via RRC signaling;

[0061] The first data is sent to the second device via XnAP signaling;

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

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

[0064] The second device is the original cell base station.

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

[0066] The switching command is sent by the second device;

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

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

[0069] RRC signaling includes the original device identifier;

[0070] XnAP signaling includes the original device identifier;

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

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

[0073] Receive the A-IoT data transmission completion indication sent by the terminal device;

[0074] Send A-IOT data to the terminal device via RRC signaling;

[0075] The second device sends an A-IoT service release instruction to the core network device;

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

[0077] The first data is sent to the original cell via XnAP signaling;

[0078] Receive path switching response messages sent by core network devices;

[0079] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

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

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

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

[0083] Original equipment identification includes AS-ID and / or RRC-ID;

[0084] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0085] 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;

[0086] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0087] The reader configuration 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.

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

[0089] RRC-ID includes AS-ID;

[0090] RRC-ID is used to identify A-IoT devices on the UU interface;

[0091] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0092] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0094] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0095] Access network equipment includes a first device and / or a second device.

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

[0097] S0: Send a handover request so that the first device obtains the first data from the terminal device based on the handover request and sends it to the second device.

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

[0099] The first data is the A-IOT response signaling;

[0100] The primary data source is A-IoT devices;

[0101] The first data is sent from the terminal device to the first device based on the handover command;

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

[0103] The first data is sent from the first device to the second device via XnAP signaling;

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

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

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

[0107] RRC signaling includes the original device identifier;

[0108] XnAP signaling includes the original device identifier;

[0109] The switching command is sent by the first device;

[0110] Send a switching command to the terminal device;

[0111] Send the handover command via RRC reconfiguration message;

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

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

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

[0115] The terminal device sends an A-IoT data transmission completion indication to the first device;

[0116] The terminal device receives A-IoT data sent by the first device via RRC signaling;

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

[0118] Receive the handover request confirmation message sent by the first device;

[0119] Send an A-IoT service release instruction to the core network equipment;

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

[0121] The first device sends the first data to the original cell via XnAP signaling;

[0122] The first device receives the path switching response message sent by the core network device;

[0123] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

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

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

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

[0127] Original equipment identification includes AS-ID and / or RRC-ID;

[0128] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0129] 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;

[0130] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0131] The reader configuration 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.

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

[0133] RRC-ID includes AS-ID;

[0134] RRC-ID is used to identify A-IoT devices on the UU interface;

[0135] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0136] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0138] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0139] Access network equipment includes a first device and / or a second device.

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

[0141] The first communication module is used to send first data to the first device in response to receiving a handover command, so that the first device can send the first data to the second device.

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

[0143] The second sending module is used to receive a handover request, obtain first data from the terminal device, and send it to the second device.

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

[0145] The third sending module is used to send a handover request so that the first device can obtain the first data from the terminal device based on the handover request and send it to the second device.

[0146] 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.

[0147] The communication device 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), 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.

[0148] 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.

[0149] In this application's technical solution, the terminal device, upon receiving a switching command, sends first data to the first device, thereby enabling the first device to send the first data to the second device. This improves the existing A-IoT processing mechanism, ensuring the continuity of A-IoT services and / or preventing data loss during the process of the terminal device acting as a reader to perform A-IoT operations. Attached Figure Description

[0150] 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.

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

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

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

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

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

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

[0157] 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;

[0158] Figure 8 is a schematic diagram of a communication method according to the second embodiment of this application;

[0159] Figure 9 is a flowchart illustrating the communication method according to the third embodiment of this application;

[0160] Figure 10 is a flowchart illustrating the communication method according to the fourth embodiment of this application;

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

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

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

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

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

[0166] 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.

[0167] Implementation methods of this application

[0168] 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.

[0169] 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.

[0170] 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, may 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, may 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.

[0171] 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.

[0172] 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).”

[0173] 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.

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

[0175] 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.

[0176] The communication device 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), 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.

[0177] 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.

[0178] 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.

[0179] 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.

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

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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.

[0188] 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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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).

[0199] 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.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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.

[0206] 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.

[0207] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in 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.

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

[0209] Technical terms involved in this embodiment: A-IoT: Ambient IoT; CBRA: Contention-Based Random Access; CFA: Contention-Free Access; D2R: Device to Reader; IoT: Internet of Things; PDRCH: Physical D2R Channel; PRDCH: Physical R2D Channel; R2D: Reader to Device; TrCH: Transport Channel; DO-DTT: Device-Originated by Device-Terminated Trigger; DT: Device-Terminated; DO-A: Device-Originated Autonomous; LPWAN: Low Power Wide Area Network; MTC: Machine Type Communication; NB-IoT: Narrow Band Internet of Things, Narrowband Internet of Things; RedCap: Reduced Capability, Lightweight; SRB: Signaling Radio Bearer; 5GC: 5G Core network; ADRF: Analytics Data Repository Function; AF: Application Function; AMF: Access and Mobility Management Function; AUSF: Authentication Server Function; DN: Data Network; NEF: Network Exposure Function; NF: Network Function; NR: New Radio.NRF: Network Repository Function; NWDAF: Network Data Analytics Function; OTT: Over The Top; PCF: Policy Control Function; PDU: Protocol Data Unit; (R)AN: Radio Access Network; SMF: Session Management Function; UDM: Unified Data Management; UE: User Equipment; UPF: User Plane Function; NG-RAN: 5G Radio Access Network; SENF: Sensing Function; GMSENC: Gateway Mobile Sensing Centre; GAD: Universal Geographical Area Description; SUPI: Subscription Permanent Identifier; ISAC: Integrated Sensing and Communication.

[0210] First Embodiment

[0211] 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 S2:

[0212] Step S2: In response to receiving the handover command, the terminal device sends first data to the first device, so that the first device sends the first data to the second device.

[0213] This embodiment takes into account that: due to the mobility of terminal devices, cell handover may be triggered when the 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 and cause the terminal device to be unable to transmit data between network devices and IoT devices.

[0214] 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.

[0215] Therefore, this embodiment proposes a solution whereby, upon receiving a switching command, the terminal device sends first data to the first device, which in turn sends the first data to the second device. This improves the existing A-IoT processing mechanism, enabling the terminal device to perform A-IoT operations as a reader while ensuring the continuity of A-IoT services and / or preventing data loss.

[0216] Optionally, the first data comes from the A-IoT device.

[0217] Optionally, A-IoT devices are Internet of Things (IoT) devices (such as devices).

[0218] Optionally, the first data is A-IOT response signaling and / or D2R response command.

[0219] Optionally, during the interaction between the terminal device and the A-IoT device, the terminal device forwards A-IoT data sent by the network device to the A-IoT device, such as A-IoT paging commands and / or R2D commands, and / or the A-IoT device returns corresponding A-IoT data to the terminal device, such as A-IoT response signaling and / or D2R response commands.

[0220] Optionally, the first device and / or the second device are network devices.

[0221] Alternatively, network equipment may be base stations, etc.

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

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

[0224] Optionally, due to the mobility of terminal devices, cell handover may be triggered during A-IoT operations performed by the terminal device as a reader, for example, moving from the coverage area of ​​the original cell base station to the coverage area of ​​the target cell base station. 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, or the target cell may not be able to configure the radio resource configuration that the original cell configured for the terminal device. To ensure the continuity of A-IoT services, when the terminal device receives a handover command or after receiving a handover command, it sends first data from the IoT device to the target cell base station, which then sends the first data to the original cell base station, thereby ensuring the continuity of A-IoT services and / or preventing data loss.

[0225] Optionally, the switching command is sent to the terminal device by the first device or the second device.

[0226] Optionally, the handover command is triggered after the handover is initiated by the second device.

[0227] Optionally, during the handover preparation process initiated by the second device, the second device sends a handover request to the first device.

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

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

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

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

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

[0233] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the first and / or second device.

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

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

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

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

[0238] 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.

[0239] Optionally, the reader configuration includes radio resource configuration for the terminal device to perform A-IoT operations and / or XnAP connections allocated for A-IoT by the access network device.

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

[0241] Optionally, after receiving the handover request confirmation message sent by the first device, the second device initiates a handover operation and / or notifies the core network equipment to release the service.

[0242] Optionally, the second device sends a handover command to the terminal device.

[0243] Optionally, the switching command includes an A-IOT data reporting instruction.

[0244] Optionally, the switching command is sent by the second device to the terminal device via an RRC reconfiguration message. For example, the second device configures an indication in the RRC reconfiguration message, which can be a 1-bit indication to indicate whether the terminal device allows the reporting of A-IOT data.

[0245] Optionally, the second device initiates an A-IoT service release instruction to the core network device. For example, if the first device indicates service release in the handover request confirmation message sent to the second device, the second device, while sending the handover command to the terminal device, initiates an A-IoT service release instruction to the core network device to release the A-IoT service.

[0246] Optionally, the A-IoT service release indication includes the functional node identifier (AIOT-F ID) that initiated the A-IoT service and / or the A-IoT service identifier (Correlation ID).

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

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

[0249] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the first device.

[0250] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the target cell corresponding to the first device.

[0251] Optionally, after sending a handover completion message, the terminal device sends the first data to the first device.

[0252] Optionally, the first data is sent from the terminal device to the first device via RRC signaling.

[0253] Optionally, the first device sends the first data to the second device.

[0254] Optionally, the first data is sent from the first device to the second device via XnAP signaling.

[0255] Optionally, the RRC signaling includes the original device identifier.

[0256] Optionally, XnAP signaling includes the original device identifier.

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

[0258] Optionally, the terminal device sends an A-IOT response signaling to the target base station via RRC signaling. If a new SRB is established, the target base station uses the new SRB to send the RRC signaling; otherwise, it uses SRB1, SRB2, or SRB4 to carry the signaling. Optionally, the RRC signaling may include the original RRC-ID.

[0259] Optionally, the terminal device sends an A-IoT data transmission completion indication to the first device. That is, the terminal device can also instruct the network device whether the A-IoT data transmission is complete.

[0260] Optionally, the terminal device can receive A-IOT data sent by the first device via RRC signaling. Optionally, the A-IOT data can be an R2D command. Optionally, the RRC signaling can include the original RRC-ID.

[0261] Optionally, after the first device receives the A-IOT data transmission completion indication sent by the terminal device, the first device sends a path switch request message to the core network device.

[0262] Optionally, the path switching request message includes an A-IoT service release indication and / or ongoing A-IoT service information.

[0263] Optionally, if the first device does not receive the reader configuration of the terminal device, the path switching request message may carry an A-IOT service release indication.

[0264] Optionally, after receiving the path switching request message sent by the first device, the core network device sends a path switching response message to the first device.

[0265] Optionally, the first device receives a path switching response message sent by the core network device.

[0266] Optionally, after receiving the first data sent by the terminal device, the first device sends the first data to the original cell via XnAP signaling. Optionally, the XnAP signaling includes the original RRC-ID.

[0267] Optionally, after receiving the first data sent by the terminal device, the first device may also send the first data to the second device via XnAP signaling.

[0268] Optionally, if the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, the original cell releases the reader configuration of the terminal device.

[0269] Through the technical solution of this embodiment, the terminal device responds to receiving the switching command and sends first data to the first device, so that the first device sends the first data to the second device. This can improve the existing A-IoT processing mechanism, so that during the process of the terminal device performing A-IoT operation as a reader, it can support ensuring the continuity of A-IoT services and / or avoid data loss.

[0270] Second Embodiment

[0271] Based on the first embodiment of this application, a second embodiment of this application is proposed. This embodiment mainly describes a method for cross-base station A-IoT data forwarding in a scenario where the terminal device is used as a reader.

[0272] Optionally, in response to receiving a handover command, the terminal device sends first data to the first device, so that the first device sends the first data to the second device, thereby improving the existing A-IoT processing mechanism and enabling the terminal device to support ensuring the continuity of A-IoT services and / or preventing data loss during the process of performing A-IoT operations as a reader.

[0273] Optionally, the first data comes from the A-IoT device.

[0274] Optionally, A-IoT devices are Internet of Things (IoT) devices (such as devices).

[0275] Optionally, the first data is A-IOT response signaling and / or D2R response command.

[0276] Optionally, during the interaction between the terminal device and the A-IoT device, the terminal device forwards A-IoT data sent by the network device to the A-IoT device, such as A-IoT paging commands and / or R2D commands, and / or the A-IoT device returns corresponding A-IoT data to the terminal device, such as A-IoT response signaling and / or D2R response commands.

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

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

[0279] Optionally, due to the mobility of terminal devices, cell handover may be triggered during A-IoT operations performed by the terminal device as a reader, for example, moving from the coverage area of ​​the original cell base station to the coverage area of ​​the target cell base station. 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, or the target cell may not be able to configure the radio resource configuration that the original cell configured for the terminal device. To ensure the continuity of A-IoT services, when the terminal device receives a handover command or after receiving a handover command, it sends first data from the IoT device to the target cell base station, which then sends the first data to the original cell base station, thereby ensuring the continuity of A-IoT services and / or preventing data loss.

[0280] Optionally, the handover command is sent from the original cell base station to the terminal device.

[0281] Optionally, the handover command is triggered after the original cell base station initiates the handover.

[0282] As shown in Figure 8, the network system architecture involved in this embodiment includes: a terminal device (UE Reader) acting as a reader, the original cell base station (gNB1), the target cell base station (gNB2), and core network equipment (CN). The original cell base station (gNB1) and the target cell base station (gNB2) are connected via the Xn interface. The terminal device (UE Reader) also interacts with the device (A-IoT device) to perform A-IoT operations. In the scenario where the terminal device acts as a reader, the process of cross-base station A-IoT data forwarding specifically includes the following steps 0-7a and / or 7b:

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

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

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

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

[0287] Optionally, the HANDOVER REQUEST message includes at least one of the following: the UE reader configuration information of the original cell, the data forwarding instruction, the new SRB establishment instruction, the original RRC-ID, and the ongoing A-IOT service information.

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

[0289] 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).

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

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

[0292] 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.

[0293] Step 3. The original cell base station gNB1 initiates the handover and notifies the core network equipment (CN) to release services;

[0294] 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.

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

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

[0297] Optionally, the RRCReconfiguration message may be configured with an indication, such as a 1-bit indication, to indicate whether the terminal device is allowed to report A-IOT data and / or whether it can forward A-IOT data from the original cell.

[0298] Step 3b. The original cell base station gNB1 initiates an A-IoT service release instruction to the core network equipment;

[0299] For example, if the target cell base station indicates the release of services in step 2, the original cell base station initiates an A-IOT service release instruction to the core network equipment.

[0300] Optionally, the A-IoT service release indication may include service information, such as 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).

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

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

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

[0304] Step 6a: The terminal device sends an A-IOT response signaling to the target cell base station via RRC signaling;

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

[0306] Optionally, the RRC signaling includes the old RRC-ID.

[0307] Optionally, the terminal device can also instruct the network device side whether A-IoT data transmission has been completed.

[0308] Optionally, the terminal device can also receive A-IOT data from the target cell base station via RRC signaling. Optionally, the RRC signaling includes the old RRC-ID.

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

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

[0311] Optionally, the path switch request message may carry an A-IoT service release indication.

[0312] Optionally, if the target cell base station does not have a reader configured to receive terminal equipment, the path switch request message sent by the target cell base station to the core network equipment may carry an A-IOT service release indication.

[0313] Optionally, the path switch request message may also contain business information, such as at least one of the following: AIoT-F ID (identifier of the functional node initiating the A-IoT service) and Correlation ID (identifier of the A-IoT service).

[0314] Optionally, the execution order of steps 6a and 6b can be simultaneous, or step 6a can take precedence, or step 6b can be executed first; no limitation is made here.

[0315] Step 7a: The target cell base station forwards the received A-IoT data to the original cell base station;

[0316] Optionally, after receiving the A-IOT data, the target cell base station forwards the received A-IOT data to the original cell base station via XnAP signaling.

[0317] Optionally, the XnAP signaling includes the old RRC-ID.

[0318] Optionally, the target cell base station can also forward A-IOT data to the original cell base station via XnAP signaling, wherein the XnAP signaling includes the old RRC-ID.

[0319] Optionally, the target cell may also indicate to the original cell whether A-IoT data transmission has been completed. Optionally, if A-IoT data transmission is completed, the original cell may release the reader configuration of the terminal device. Optionally, the reader configuration of the terminal device includes the XnAP connection allocated for A-IoT by the access network equipment side.

[0320] Optionally, if the original cell receives a CONTEXT RELEASE message from the terminal device in the target cell, the original cell may release the reader configuration of the terminal device. Optionally, the reader configuration of the terminal device includes the XnAP connection allocated for A-IOT by the access network device side.

[0321] Step 7b: The target cell base station receives the path switching response message sent by the network equipment side.

[0322] Optionally, the target cell base station receives a path switching request response sent by the network device.

[0323] Optionally, the execution order of steps 7a and 7b can be simultaneous, or step 7a can take precedence, or step 7b can be executed first; no limitation is made here.

[0324] Through the technical solution of this embodiment, the terminal device, in response to receiving the handover command, sends the first data from the A-IoT device to the target cell base station, so that the target cell base station sends the first data to the original cell base station, thereby improving the existing A-IoT processing mechanism and enabling the terminal device, as a reader, to perform A-IoT operations while ensuring the continuity of A-IoT services and / or avoiding data loss.

[0325] Third Embodiment

[0326] Referring to Figure 9, which is a flowchart illustrating a communication method according to a third embodiment of this application, the communication method of this embodiment can be applied to a first device (such as a base station), and includes step S1:

[0327] Step S1: Upon receiving the handover request, the first device obtains the first data from the terminal device and sends it to the second device.

[0328] This embodiment provides a method for forwarding A-IoT data across network devices in an A-IoT service scenario. The proposed solution is that, in response to receiving a handover request, the first device obtains the first data from the terminal device and sends it to the second device. This can improve the existing A-IoT processing mechanism, enabling the terminal device to perform A-IoT operations as a reader, thus ensuring the continuity of A-IoT services and / or preventing data loss.

[0329] Optionally, the first device and / or the second device are network devices.

[0330] Alternatively, network equipment may be base stations, etc.

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

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

[0333] Optionally, the first data comes from the A-IoT device.

[0334] Optionally, A-IoT devices are Internet of Things (IoT) devices (such as devices).

[0335] Optionally, the first data is A-IOT response signaling and / or D2R response command.

[0336] Optionally, during the interaction between the terminal device and the A-IoT device, the terminal device forwards A-IoT data sent by the network device to the A-IoT device, such as A-IoT paging commands and / or R2D commands, and / or the A-IoT device returns corresponding A-IoT data to the terminal device, such as A-IoT response signaling and / or D2R response commands.

[0337] Optionally, the handover request is sent from the second device to the first device.

[0338] Optionally, in response to receiving a handover request, the first device obtains first data from the terminal device.

[0339] Optionally, the first data is sent by the terminal device to the first device based on the handover command.

[0340] Optionally, due to the mobility of terminal devices, cell handover may be triggered during A-IoT operations performed by the terminal device as a reader, for example, moving from the coverage area of ​​the original cell base station to the coverage area of ​​the target cell base station. 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, or the target cell may not be able to configure the radio resource configuration that the original cell configured for the terminal device. To ensure the continuity of A-IoT services, when the terminal device receives a handover command or after receiving a handover command, it sends first data from the IoT device to the target cell base station, which then sends the first data to the original cell base station, thereby ensuring the continuity of A-IoT services and / or preventing data loss.

[0341] Optionally, the switching command is sent to the terminal device by the first device or the second device.

[0342] Optionally, the handover command is triggered after the handover is initiated by the second device.

[0343] Optionally, during the handover preparation process initiated by the second device, the second device sends a handover request to the first device.

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

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

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

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

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

[0349] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the first and / or second device.

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

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

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

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

[0354] 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.

[0355] Optionally, the reader configuration includes radio resource configuration for the terminal device to perform A-IoT operations and / or XnAP connections allocated for A-IoT by the access network device.

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

[0357] Optionally, after receiving the handover request confirmation message sent by the first device, the second device initiates a handover operation and / or notifies the core network equipment to release the service.

[0358] Optionally, the second device sends a handover command to the terminal device.

[0359] Optionally, the switching command includes an A-IOT data reporting instruction.

[0360] Optionally, the switching command is sent by the second device to the terminal device via an RRC reconfiguration message. For example, the second device configures an indication in the RRC reconfiguration message, which can be a 1-bit indication to indicate whether the terminal device allows the reporting of A-IOT data.

[0361] Optionally, the second device initiates an A-IoT service release instruction to the core network device. For example, if the first device indicates service release in the handover request confirmation message sent to the second device, the second device, while sending the handover command to the terminal device, initiates an A-IoT service release instruction to the core network device to release the A-IoT service.

[0362] Optionally, the A-IoT service release indication includes the functional node identifier (AIOT-F ID) that initiated the A-IoT service and / or the A-IoT service identifier (Correlation ID).

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

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

[0365] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the first device.

[0366] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the target cell corresponding to the first device.

[0367] Optionally, after sending a handover completion message, the terminal device sends the first data to the first device.

[0368] Optionally, the first data is sent from the terminal device to the first device via RRC signaling.

[0369] Optionally, the first device sends the first data to the second device.

[0370] Optionally, the first data is sent from the first device to the second device via XnAP signaling.

[0371] Optionally, the RRC signaling includes the original device identifier.

[0372] Optionally, XnAP signaling includes the original device identifier.

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

[0374] Optionally, the terminal device sends an A-IOT response signaling to the target base station via RRC signaling. If a new SRB is established, the target base station uses the new SRB to send the RRC signaling; otherwise, it uses SRB1, SRB2, or SRB4 to carry the signaling. Optionally, the RRC signaling may include the original RRC-ID.

[0375] Optionally, the terminal device sends an A-IoT data transmission completion indication to the first device. That is, the terminal device can also instruct the network device whether the A-IoT data transmission is complete.

[0376] Optionally, the terminal device can receive A-IOT data sent by the first device via RRC signaling. Optionally, the A-IOT data can be an R2D command. Optionally, the RRC signaling can include the original RRC-ID.

[0377] Optionally, after the first device receives the A-IOT data transmission completion indication sent by the terminal device, the first device sends a path switch request message to the core network device.

[0378] Optionally, the path switching request message includes an A-IoT service release indication and / or ongoing A-IoT service information.

[0379] Optionally, if the first device does not receive the reader configuration of the terminal device, the path switching request message may carry an A-IOT service release indication.

[0380] Optionally, after receiving the path switching request message sent by the first device, the core network device sends a path switching response message to the first device.

[0381] Optionally, the first device receives a path switching response message sent by the core network device.

[0382] Optionally, after receiving the first data sent by the terminal device, the first device sends the first data to the original cell via XnAP signaling. Optionally, the XnAP signaling includes the original RRC-ID.

[0383] Optionally, after receiving the first data sent by the terminal device, the first device may also send the first data to the second device via XnAP signaling.

[0384] Optionally, if the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, the original cell releases the reader configuration of the terminal device.

[0385] Through the technical solution of this embodiment, the first device, in response to receiving a handover request, obtains the first data from the terminal device and sends it to the second device. This can improve 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.

[0386] Fourth embodiment

[0387] Referring to Figure 10, which is a flowchart illustrating the communication method of the fourth 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 S0:

[0388] Step S0: The second device sends a handover request so that the first device can obtain the first data from the terminal device based on the handover request and send it to the second device.

[0389] This embodiment provides a method for forwarding A-IoT data across network devices in an A-IoT service scenario. The proposed solution is that the second device sends a handover request so that the first device can obtain the first data from the terminal device based on the handover request and send it to the second device. This can improve 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.

[0390] Optionally, the first device and / or the second device are network devices.

[0391] Alternatively, network equipment may be base stations, etc.

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

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

[0394] Optionally, the first data comes from the A-IoT device.

[0395] Optionally, A-IoT devices are Internet of Things (IoT) devices (such as devices).

[0396] Optionally, the first data is A-IOT response signaling and / or D2R response command.

[0397] Optionally, during the interaction between the terminal device and the A-IoT device, the terminal device forwards A-IoT data sent by the network device to the A-IoT device, such as A-IoT paging commands and / or R2D commands, and / or the A-IoT device returns corresponding A-IoT data to the terminal device, such as A-IoT response signaling and / or D2R response commands.

[0398] Optionally, the second device sends a handover request.

[0399] Optionally, the first device receives the handover request.

[0400] Optionally, in response to receiving a handover request, the first device obtains first data from the terminal device.

[0401] Optionally, the first data is sent by the terminal device to the first device based on the handover command.

[0402] Optionally, due to the mobility of terminal devices, cell handover may be triggered during A-IoT operations performed by the terminal device as a reader, for example, moving from the coverage area of ​​the original cell base station to the coverage area of ​​the target cell base station. 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, or the target cell may not be able to configure the radio resource configuration that the original cell configured for the terminal device. To ensure the continuity of A-IoT services, when the terminal device receives a handover command or after receiving a handover command, it sends first data from the IoT device to the target cell base station, which then sends the first data to the original cell base station, thereby ensuring the continuity of A-IoT services and / or preventing data loss.

[0403] Optionally, the switching command is sent to the terminal device by the first device or the second device.

[0404] Optionally, the handover command is triggered after the handover is initiated by the second device.

[0405] Optionally, during the handover preparation process initiated by the second device, the second device sends a handover request to the first device.

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

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

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

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

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

[0411] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the first and / or second device.

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

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

[0414] Optionally, after receiving the handover request sent by the second device, the first device sends a handover request confirmation message to the second device.

[0415] 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.

[0416] Optionally, the reader configuration includes radio resource configuration for the terminal device to perform A-IoT operations and / or XnAP connections allocated for A-IoT by the access network device.

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

[0418] Optionally, after receiving the handover request confirmation message sent by the first device, the second device initiates a handover operation and / or notifies the core network equipment to release the service.

[0419] Optionally, the second device sends a handover command to the terminal device.

[0420] Optionally, the switching command includes an A-IOT data reporting instruction.

[0421] Optionally, the switching command is sent by the second device to the terminal device via an RRC reconfiguration message. For example, the second device configures an indication in the RRC reconfiguration message, which can be a 1-bit indication to indicate whether the terminal device allows the reporting of A-IOT data.

[0422] Optionally, the second device initiates an A-IoT service release instruction to the core network device. For example, if the first device indicates service release in the handover request confirmation message sent to the second device, the second device, while sending the handover command to the terminal device, initiates an A-IoT service release instruction to the core network device to release the A-IoT service.

[0423] Optionally, the A-IoT service release indication includes the functional node identifier (AIOT-F ID) that initiated the A-IoT service and / or the A-IoT service identifier (Correlation ID).

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

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

[0426] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the first device.

[0427] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the target cell corresponding to the first device.

[0428] Optionally, after sending a handover completion message, the terminal device sends the first data to the first device.

[0429] Optionally, the first data is sent from the terminal device to the first device via RRC signaling.

[0430] Optionally, the first device sends the first data to the second device.

[0431] Optionally, the first data is sent from the first device to the second device via XnAP signaling.

[0432] Optionally, the RRC signaling includes the original device identifier.

[0433] Optionally, XnAP signaling includes the original device identifier.

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

[0435] Optionally, the terminal device sends an A-IOT response signaling to the target base station via RRC signaling. If a new SRB is established, the target base station uses the new SRB to send the RRC signaling; otherwise, it uses SRB1, SRB2, or SRB4 to carry the signaling. Optionally, the RRC signaling may include the original RRC-ID.

[0436] Optionally, the terminal device sends an A-IoT data transmission completion indication to the first device. That is, the terminal device can also instruct the network device whether the A-IoT data transmission is complete.

[0437] Optionally, the terminal device can receive A-IOT data sent by the first device via RRC signaling. Optionally, the A-IOT data can be an R2D command. Optionally, the RRC signaling can include the original RRC-ID.

[0438] Optionally, after the first device receives the A-IOT data transmission completion indication sent by the terminal device, the first device sends a path switch request message to the core network device.

[0439] Optionally, the path switching request message includes an A-IoT service release indication and / or ongoing A-IoT service information.

[0440] Optionally, if the first device does not receive the reader configuration of the terminal device, the path switching request message may carry an A-IOT service release indication.

[0441] Optionally, after receiving the path switching request message sent by the first device, the core network device sends a path switching response message to the first device.

[0442] Optionally, the first device receives a path switching response message sent by the core network device.

[0443] Optionally, after receiving the first data sent by the terminal device, the first device sends the first data to the original cell via XnAP signaling. Optionally, the XnAP signaling includes the original RRC-ID.

[0444] Optionally, after receiving the first data sent by the terminal device, the first device may also send the first data to the second device via XnAP signaling.

[0445] Optionally, if the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, the original cell releases the reader configuration of the terminal device.

[0446] Through the technical solution of this embodiment, the second device sends a handover request so that the first device can obtain the first data from the terminal device based on the handover request and send it to the second device. This can improve 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.

[0447] Fifth embodiment

[0448] Referring to Figure 11, which is a schematic diagram of the interaction flow between a first device, a second device, and a terminal device according to the fifth embodiment of the communication method, the fifth embodiment of this application proposes a communication method including steps S0-S2:

[0449] Step S0: The second device sends a handover request so that the first device obtains the first data from the terminal device based on the handover request and sends it to the second device;

[0450] Step S1: Upon receiving the handover request, the first device obtains the first data from the terminal device and sends it to the second device;

[0451] Step S2: In response to receiving the handover command, the terminal device sends first data to the first device, so that the first device sends the first data to the second device.

[0452] This embodiment proposes a technical solution whereby the second device sends a handover request, the first device responds by receiving the handover request, obtains first data from the terminal device, and sends it to the second device, and the terminal device responds by receiving the handover command and sends the first data to the first device, thereby enabling the first device to send the first data to the second device. This improves the existing A-IoT processing mechanism, 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.

[0453] Optionally, the first data comes from the A-IoT device.

[0454] Optionally, A-IoT devices are Internet of Things (IoT) devices (such as devices).

[0455] Optionally, the first data is A-IOT response signaling and / or D2R response command.

[0456] Optionally, during the interaction between the terminal device and the A-IoT device, the terminal device forwards A-IoT data sent by the network device to the A-IoT device, such as A-IoT paging commands and / or R2D commands, and / or the A-IoT device returns corresponding A-IoT data to the terminal device, such as A-IoT response signaling and / or D2R response commands.

[0457] Optionally, the first device and / or the second device are network devices.

[0458] Alternatively, network equipment may be base stations, etc.

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

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

[0461] Optionally, due to the mobility of terminal devices, cell handover may be triggered during A-IoT operations performed by the terminal device as a reader, for example, moving from the coverage area of ​​the original cell base station to the coverage area of ​​the target cell base station. 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, or the target cell may not be able to configure the radio resource configuration that the original cell configured for the terminal device. To ensure the continuity of A-IoT services, when the terminal device receives a handover command or after receiving a handover command, it sends first data from the IoT device to the target cell base station, which then sends the first data to the original cell base station, thereby ensuring the continuity of A-IoT services and / or preventing data loss.

[0462] Optionally, the switching command is sent to the terminal device by the first device or the second device.

[0463] Optionally, the handover command is triggered after the handover is initiated by the second device.

[0464] Optionally, during the handover preparation process initiated by the second device, the second device sends a handover request to the first device.

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

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

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

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

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

[0470] Optionally, the AS-ID is used to identify the A-IoT device between the terminal device and the first and / or second device.

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

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

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

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

[0475] 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.

[0476] Optionally, the reader configuration includes radio resource configuration for the terminal device to perform A-IoT operations and / or XnAP connections allocated for A-IoT by the access network device.

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

[0478] Optionally, after receiving the handover request confirmation message sent by the first device, the second device initiates a handover operation and / or notifies the core network equipment to release the service.

[0479] Optionally, the second device sends a handover command to the terminal device.

[0480] Optionally, the switching command includes an A-IOT data reporting instruction.

[0481] Optionally, the switching command is sent by the second device to the terminal device via an RRC reconfiguration message. For example, the second device configures an indication in the RRC reconfiguration message, which can be a 1-bit indication to indicate whether the terminal device allows the reporting of A-IOT data.

[0482] Optionally, the second device initiates an A-IoT service release instruction to the core network device. For example, if the first device indicates service release in the handover request confirmation message sent to the second device, the second device, while sending the handover command to the terminal device, initiates an A-IoT service release instruction to the core network device to release the A-IoT service.

[0483] Optionally, the A-IoT service release indication includes the functional node identifier (AIOT-F ID) that initiated the A-IoT service and / or the A-IoT service identifier (Correlation ID).

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

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

[0486] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the first device.

[0487] Optionally, after the terminal device completes the RACH process to the target cell, it sends a handover completion message to the target cell corresponding to the first device.

[0488] Optionally, after sending a handover completion message, the terminal device sends the first data to the first device.

[0489] Optionally, the first data is sent from the terminal device to the first device via RRC signaling.

[0490] Optionally, the first device sends the first data to the second device.

[0491] Optionally, the first data is sent from the first device to the second device via XnAP signaling.

[0492] Optionally, the RRC signaling includes the original device identifier.

[0493] Optionally, XnAP signaling includes the original device identifier.

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

[0495] Optionally, the terminal device sends an A-IOT response signaling to the target base station via RRC signaling. If a new SRB is established, the target base station uses the new SRB to send the RRC signaling; otherwise, it uses SRB1, SRB2, or SRB4 to carry the signaling. Optionally, the RRC signaling may include the original RRC-ID.

[0496] Optionally, the terminal device sends an A-IoT data transmission completion indication to the first device. That is, the terminal device can also instruct the network device whether the A-IoT data transmission is complete.

[0497] Optionally, the terminal device can receive A-IOT data sent by the first device via RRC signaling. Optionally, the A-IOT data can be an R2D command. Optionally, the RRC signaling can include the original RRC-ID.

[0498] Optionally, after the first device receives the A-IOT data transmission completion indication sent by the terminal device, the first device sends a path switch request message to the core network device.

[0499] Optionally, the path switching request message includes an A-IoT service release indication and / or ongoing A-IoT service information.

[0500] Optionally, if the first device does not receive the reader configuration of the terminal device, the path switching request message may carry an A-IOT service release indication.

[0501] Optionally, after receiving the path switching request message sent by the first device, the core network device sends a path switching response message to the first device.

[0502] Optionally, the first device receives a path switching response message sent by the core network device.

[0503] Optionally, after receiving the first data sent by the terminal device, the first device sends the first data to the original cell via XnAP signaling. Optionally, the XnAP signaling includes the original RRC-ID.

[0504] Optionally, after receiving the first data sent by the terminal device, the first device may also send the first data to the second device via XnAP signaling.

[0505] Optionally, if the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, the original cell releases the reader configuration of the terminal device.

[0506] Through the technical solution of this embodiment, the second device sends a handover request, the first device responds to receiving the handover request by obtaining the first data from the terminal device and sending it to the second device, and the terminal device responds to receiving the handover command by sending the first data to the first device, so that the first device sends the first data to the second device. This can improve 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.

[0507] Sixth Embodiment

[0508] Please refer to Figure 12, 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 12 can be used to perform some or all of the functions in the method embodiments described above. As shown in Figure 12, the communication device 150 includes:

[0509] The first communication module 1501 is used to send first data to the first device in response to receiving a switching command, so that the first device sends the first data to the second device.

[0510] Optionally, the communication device further includes at least one of the following:

[0511] The first data is the A-IOT response signaling;

[0512] The primary data source is A-IoT devices;

[0513] The switching command is sent by the first device;

[0514] The switching command is sent by the second device;

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

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

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

[0518] The first data is sent from the first device to the second device via XnAP signaling;

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

[0520] The second device is the original cell base station.

[0521] Optionally, the communication device further includes at least one of the following:

[0522] RRC signaling includes the original device identifier;

[0523] XnAP signaling includes the original device identifier;

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

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

[0526] Send an A-IoT data transmission completion indication to the first device;

[0527] Receive A-IOT data sent by the first device via RRC signaling;

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

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

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

[0531] The second device sends an A-IoT service release instruction to the core network device;

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

[0533] The first device sends the first data to the original cell via XnAP signaling;

[0534] The first device receives the path switching response message sent by the core network device;

[0535] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

[0536] Optionally, the communication device further includes at least one of the following:

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

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

[0539] Original equipment identification includes AS-ID and / or RRC-ID;

[0540] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0541] 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;

[0542] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0543] The reader configuration 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.

[0544] Optionally, the communication device further includes at least one of the following:

[0545] RRC-ID includes AS-ID;

[0546] RRC-ID is used to identify A-IoT devices on the UU interface;

[0547] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0548] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0550] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0551] Access network equipment includes a first device and / or a second device.

[0552] 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.

[0553] Seventh Embodiment

[0554] Please refer to Figure 13, 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 13 can be used to perform some or all of the functions in the method embodiment described in the above embodiment. As shown in Figure 13, the communication device 160 includes:

[0555] The second communication module 1601 is used to receive a handover request, obtain first data from the terminal device, and send it to the second device.

[0556] Optionally, the communication device further includes at least one of the following:

[0557] The first data is the A-IOT response signaling;

[0558] The primary data source is A-IoT devices;

[0559] The first data is sent by the terminal device based on the handover command;

[0560] The handover request was sent by the second device;

[0561] Send a switching command to the terminal device;

[0562] Receive the first data via RRC signaling;

[0563] The first data is sent to the second device via XnAP signaling;

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

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

[0566] The second device is the original cell base station.

[0567] Optionally, the communication device further includes at least one of the following:

[0568] The switching command is sent by the second device;

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

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

[0571] RRC signaling includes the original device identifier;

[0572] XnAP signaling includes the original device identifier;

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

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

[0575] Receive the A-IoT data transmission completion indication sent by the terminal device;

[0576] Send A-IOT data to the terminal device via RRC signaling;

[0577] The second device sends an A-IoT service release instruction to the core network device;

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

[0579] The first data is sent to the original cell via XnAP signaling;

[0580] Receive path switching response messages sent by core network devices;

[0581] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

[0582] Optionally, the communication device further includes at least one of the following:

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

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

[0585] Original equipment identification includes AS-ID and / or RRC-ID;

[0586] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0587] 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;

[0588] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0589] The reader configuration 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.

[0590] Optionally, the communication device further includes at least one of the following:

[0591] RRC-ID includes AS-ID;

[0592] RRC-ID is used to identify A-IoT devices on the UU interface;

[0593] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0594] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0596] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0597] Access network equipment includes a first device and / or a second device.

[0598] 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.

[0599] Eighth embodiment

[0600] Please refer to Figure 14, 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 14 can be used to perform some or all of the functions described in the method embodiments above. As shown in Figure 14, the device 170 includes:

[0601] The third communication module 1701 is used to send a handover request so that the first device can obtain first data from the terminal device based on the handover request and send it to the second device.

[0602] Optionally, the communication device further includes at least one of the following:

[0603] The first data is the A-IOT response signaling;

[0604] The primary data source is A-IoT devices;

[0605] The first data is sent from the terminal device to the first device based on the handover command;

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

[0607] The first data is sent from the first device to the second device via XnAP signaling;

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

[0609] The second device is the original cell base station.

[0610] Optionally, the communication device further includes at least one of the following:

[0611] RRC signaling includes the original device identifier;

[0612] XnAP signaling includes the original device identifier;

[0613] The switching command is sent by the first device;

[0614] Send a switching command to the terminal device;

[0615] Send the handover command via RRC reconfiguration message;

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

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

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

[0619] The terminal device sends an A-IoT data transmission completion indication to the first device;

[0620] The terminal device receives A-IoT data sent by the first device via RRC signaling;

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

[0622] Receive the handover request confirmation message sent by the first device;

[0623] Send an A-IoT service release instruction to the core network equipment;

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

[0625] The first device sends the first data to the original cell via XnAP signaling;

[0626] The first device receives the path switching response message sent by the core network device;

[0627] If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

[0628] Optionally, the communication device further includes at least one of the following:

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

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

[0631] Original equipment identification includes AS-ID and / or RRC-ID;

[0632] The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information;

[0633] 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;

[0634] The path switching request message includes an A-IoT service release instruction and / or ongoing A-IoT service information;

[0635] The reader configuration 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.

[0636] Optionally, the communication device further includes at least one of the following:

[0637] RRC-ID includes AS-ID;

[0638] RRC-ID is used to identify A-IoT devices on the UU interface;

[0639] AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices;

[0640] AS-ID and / or RRC-ID are assigned by the terminal device;

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

[0642] The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier;

[0643] Access network equipment includes a first device and / or a second device.

[0644] 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.

[0645] Referring to Figure 15, 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 or a second device (or a component that can be used in a first device or a second 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 a terminal device, a first device, or a second device, as detailed in the descriptions in the above method embodiments.

[0646] 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.

[0647] 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, or the second device.

[0648] Optionally, the communication device 180 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[0649] 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.

[0650] Alternatively, the memory 1802 may also store data. The processor 1801 and the memory 1802 can be configured separately or integrated together.

[0651] 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, or second device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device 180.

[0652] 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 a switching command; and the processor 1801 may send first data to the first device in response to receiving the switching command, so that the first device may send the first data to the second device.

[0653] 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.

[0654] 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.

[0655] 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.

[0656] 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.

[0657] In this application, the communication device can be a terminal device (such as a mobile phone), or a first device or a second device (such as a base station), 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.

[0658] Although the communication device is described in the above embodiments using terminal devices, first devices, or second devices as examples, the scope of the communication device described in this application is not limited to the aforementioned terminal devices, first devices, or second devices, and the structure of the communication device is not limited to FIG15. The communication device can be a standalone device or can be part of a larger device.

[0659] This application also provides a communication system, including: a terminal device as described in any of the above embodiments; and a first device or a second device as described in any of the above embodiments.

[0660] 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.

[0661] The communication device in this application may be a terminal device (such as a mobile phone), a first device or a second device (such as a base station), 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.

[0662] 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.

[0663] 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.

[0664] 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.

[0665] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0666] 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.

[0667] 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.

[0668] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0669] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0670] 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.

[0671] 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.

[0672] 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.

[0673] 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.

[0674] 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)).

[0675] 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

1. A communication method, wherein, Applied to terminal devices, including the following steps: S2: In response to receiving a handover command, send first data to the first device so that the first device sends the first data to the second device.

2. The method according to claim 1, wherein, It also includes at least one of the following: The first data is the A-IOT response signaling; The primary data source is A-IoT devices; The switching command is sent by the first device; The switching command is sent by the second device; The handover command is sent by the second device via an RRC reconfiguration message; The switching commands include A-IOT data reporting instructions; The first data is sent to the first device via RRC signaling; The first data is sent from the first device to the second device via XnAP signaling; The first device is the target cell base station; The second device is the original cell base station.

3. The method according to claim 2, wherein, It also includes at least one of the following: RRC signaling includes the original device identifier; XnAP signaling includes the original device identifier; Perform the RACH procedure on the target cell; Send a handover completion message to the first device; Send an A-IoT data transmission completion indication to the first device; Receive A-IOT data sent by the first device via RRC signaling; 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 sends an A-IoT service release instruction to the core network device; The first device sends a path switching request message to the core network device; The first device sends the first data to the original cell via XnAP signaling; The first device receives the path switching response message sent by the core network device; If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

4. The method according to claim 3, wherein, It also includes at least one of the following: The RACH procedure can be either a CFRA procedure or a CBRA procedure. RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; Original equipment identification includes AS-ID and / or RRC-ID; The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information; 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 an A-IoT service release instruction and / or ongoing A-IoT service information; The reader configuration 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.

5. The method according to claim 4, wherein, It also includes at least one of the following: RRC-ID includes AS-ID; RRC-ID is used to identify A-IoT devices on the UU interface; AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices; AS-ID and / or RRC-ID are assigned by the terminal device; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier; Access network equipment includes a first device and / or a second device.

6. A communication method, wherein, Applied to the first device, including the following steps: S1: In response to receiving a handover request, obtain first data from the terminal device and send it to the second device.

7. The method according to claim 6, wherein, It also includes at least one of the following: The first data is the A-IOT response signaling; The primary data source is A-IoT devices; The first data is sent by the terminal device based on the handover command; The handover request was sent by the second device; Send a switching command to the terminal device; Receive the first data via RRC signaling; The first data is sent to the second device via XnAP signaling; Send a handover request confirmation message to the second device; The first device is the target cell base station; The second device is the original cell base station.

8. The method according to claim 7, wherein, It also includes at least one of the following: The switching command is sent by the second device; The handover command is sent by the second device via an RRC reconfiguration message; The switching commands include A-IOT data reporting instructions; RRC signaling includes the original device identifier; XnAP signaling includes the original device identifier; The terminal device executes the RACH procedure to the target cell; Receive the handover completion message sent by the terminal device; Receive the A-IoT data transmission completion indication sent by the terminal device; Send A-IOT data to the terminal device via RRC signaling; The second device sends an A-IoT service release instruction to the core network device; Send a path switching request message to the core network equipment; The first data is sent to the original cell via XnAP signaling; Receive path switching response messages sent by core network devices; If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

9. The method according to claim 8, wherein, It also includes at least one of the following: The RACH procedure can be either a CFRA procedure or a CBRA procedure. RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; Original equipment identification includes AS-ID and / or RRC-ID; The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information; 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 an A-IoT service release instruction and / or ongoing A-IoT service information; The reader configuration 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.

10. The method according to claim 9, wherein, It also includes at least one of the following: RRC-ID includes AS-ID; RRC-ID is used to identify A-IoT devices on the UU interface; AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices; AS-ID and / or RRC-ID are assigned by the terminal device; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier; Access network equipment includes a first device and / or a second device.

11. A communication method, wherein, Applied to a second device, including the following steps: S0: Send a handover request so that the first device obtains the first data from the terminal device based on the handover request and sends it to the second device.

12. The method according to claim 11, wherein, It also includes at least one of the following: The first data is the A-IOT response signaling; The primary data source is A-IoT devices; The first data is sent from the terminal device to the first device based on the handover command; The first data is sent from the terminal device to the first device via RRC signaling; The first data is sent from the first device to the second device via XnAP signaling; The first device is the target cell base station; The second device is the original cell base station.

13. The method according to claim 12, wherein, It also includes at least one of the following: RRC signaling includes the original device identifier; XnAP signaling includes the original device identifier; The switching command is sent by the first device; Send a switching command to the terminal device; Send the handover command via RRC reconfiguration message; The switching commands include A-IOT data reporting instructions; The terminal device executes the RACH procedure to the target cell; The terminal device sends a handover completion message to the first device; The terminal device sends an A-IoT data transmission completion indication to the first device; The terminal device receives A-IoT data sent by the first device via RRC signaling; The first device receives a handover request sent by the second device; Receive the handover request confirmation message sent by the first device; Send an A-IoT service release instruction to the core network equipment; The first device sends a path switching request message to the core network device; The first device sends the first data to the original cell via XnAP signaling; The first device receives the path switching response message sent by the core network device; If the original cell receives an A-IOT data transmission completion indication and / or a terminal device connection release message from the target cell, then the original cell releases the reader configuration of the terminal device.

14. The method according to claim 13, wherein, It also includes at least one of the following: The RACH procedure can be either a CFRA procedure or a CBRA procedure. RRC signaling is carried by at least one of SRB1, SRB2, SRB4 and the new SRB; Original equipment identification includes AS-ID and / or RRC-ID; The handover request includes at least one of the following: reader configuration information of the terminal equipment configured in the original cell, data forwarding indication, new SRB establishment indication, original equipment identifier, and ongoing A-IoT service information; 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 an A-IoT service release instruction and / or ongoing A-IoT service information; The reader configuration 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.

15. The method according to claim 14, wherein, It also includes at least one of the following: RRC-ID includes AS-ID; RRC-ID is used to identify A-IoT devices on the UU interface; AS-ID is used to identify A-IoT devices between terminal devices and first and / or second devices; AS-ID and / or RRC-ID are assigned by the terminal device; A-IoT service information includes the functional node identifier that initiates the A-IoT service and / or the A-IoT service identifier; The A-IoT service release instruction includes the functional node identifier that initiated the A-IoT service and / or the A-IoT service identifier; Access network equipment includes a first device and / or a second device.

16. 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, 6, or 11.

17. 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, 6, or 11.

Images