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: a terminal device sending a second identifier, such that an access network device determines or generates a third identifier. By means of the technical solution of the present application, the establishment of an end-to-end bearer is supported, so as to improve an A-IoT data communication mechanism.

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] The existing protocol supports TP2, which means that the terminal device can act as a reader to communicate with IoT devices (such as devices) and transmit data between IoT devices and network devices (such as base stations) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The network device can forward A-IoT data from the core network device (such as CN) to the IoT device, and / or forward the A-IoT data received from the IoT device to the core network device.

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

[0004] The A-IoT data communication mechanism is still imperfect. For example, how to support the establishment of end-to-end bearers is not yet clear in the existing network architecture.

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

[0006] The main purpose of this application is to provide a processing method, communication device and storage medium, which are designed to support the establishment of end-to-end bearers to improve the A-IoT data communication mechanism.

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

[0008] S1: Send the second identifier so that the access network device can determine or generate the third identifier.

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

[0010] The second identifier is determined or generated by the terminal device;

[0011] The second identifier is determined or generated by the terminal device after receiving the device ID;

[0012] The terminal device is configured as a reader;

[0013] Assign a first identifier to the target device;

[0014] Upon receiving an inventory request, an inventory response is sent to the access network equipment;

[0015] Send an A-IoT paging command to the target device;

[0016] Assign a second identifier to the target device;

[0017] Send inventory reports to access network equipment;

[0018] The access network equipment sends inventory reports to the core network equipment.

[0019] Receive command requests from core network devices forwarded by access network devices;

[0020] Send the A-IoT upper-layer data content in the command request to the target device;

[0021] Receive command responses sent by the target device;

[0022] Send the A-IOT upper-layer data content in the command response to the access network device.

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

[0024] The device ID is sent by the target device;

[0025] Maintain the correspondence between the first identifier and the second identifier;

[0026] Access network equipment maintains the correspondence between the second and third identifiers;

[0027] The first identifier is used to identify the target device between the terminal device and the target device;

[0028] The second identifier is used to identify the target device on the UU interface;

[0029] The third identifier is used to identify the target device on the NGAP interface;

[0030] The second identifier may be the same as or different from the first identifier;

[0031] The second identifier includes the first identifier;

[0032] The first identifier includes AS-ID;

[0033] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[0034] The third identifier includes the device NGAP ID;

[0035] Data is transmitted between the device and the access network via RRC signaling;

[0036] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[0037] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[0039] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[0040] Inventory requests and / or command requests are sent by the access network equipment via the first RRC signaling;

[0041] Inventory responses and / or inventory reports are sent via a second RRC signaling;

[0042] The inventory report sent to the access network equipment includes at least one of the following: device ID, security parameter X, and N2;

[0043] The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[0044] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0045] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[0047] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[0048] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[0049] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[0050] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[0051] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[0052] The random response message includes a first identifier assigned by the terminal device to the target device.

[0053] This application also provides a communication method applicable to access network equipment (such as a base station), comprising the following steps:

[0054] S2: In response to receiving the second identifier, determine or generate the third identifier.

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

[0056] The second identifier is determined or generated by the terminal device;

[0057] The second identifier is determined or generated by the terminal device after receiving the device ID;

[0058] The terminal device is configured as a reader;

[0059] The terminal device assigns a first identifier to the target device;

[0060] Send an inventory request to the terminal device;

[0061] Receive inventory response sent by terminal device;

[0062] The terminal device sends an A-IoT paging command to the target device;

[0063] The terminal device assigns a second identifier to the target device;

[0064] Receive inventory reports sent by terminal devices;

[0065] Send inventory reports to core network equipment;

[0066] Send command requests from core network devices to terminal devices;

[0067] The terminal device sends the A-IoT upper-layer data content in the command request to the target device;

[0068] Receive the A-IoT upper-layer data content from the command response forwarded by the terminal device from the target device;

[0069] Send the A-IOT upper-layer data content from the command response of the target device to the core network device.

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

[0071] The device ID is sent from the target device to the terminal device;

[0072] The terminal device maintains the correspondence between the first identifier and the second identifier;

[0073] Maintain the correspondence between the second and third identifiers;

[0074] The first identifier is used to identify the target device between the terminal device and the target device;

[0075] The second identifier is used to identify the target device on the UU interface;

[0076] The third identifier is used to identify the target device on the NGAP interface;

[0077] The second identifier may be the same as or different from the first identifier;

[0078] The second identifier includes the first identifier;

[0079] The first identifier includes AS-ID;

[0080] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[0081] The third identifier includes the device NGAP ID;

[0082] Data is transmitted between the terminal device and the terminal device via RRC signaling;

[0083] The signaling sent to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier;

[0084] Signaling sent to core network devices and / or signaling sent by core network devices to access network devices contains a third identifier.

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

[0086] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[0087] Inventory requests and / or command requests are sent via the first RRC signaling;

[0088] Inventory responses and / or inventory reports are sent by the terminal device via a second RRC signaling;

[0089] The inventory report received from the terminal device includes at least one of the following: device ID, security parameter X, and N2;

[0090] The inventory report sent to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[0091] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0092] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[0094] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[0095] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[0096] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[0097] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[0098] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[0099] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[0101] S3: Receive the third identifier, which is determined or generated by the access network device in response to receiving the second identifier.

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

[0103] The second identifier is determined or generated by the terminal device;

[0104] The second identifier is determined or generated by the terminal device after receiving the device ID;

[0105] The terminal device is configured as a reader;

[0106] The terminal device assigns a first identifier to the target device;

[0107] Send inventory requests to terminal devices via access network equipment;

[0108] The receiving terminal device receives the inventory response forwarded by the access network equipment;

[0109] The terminal device sends an A-IoT paging command to the target device;

[0110] The terminal device assigns a second identifier to the target device;

[0111] Receive inventory reports from terminal devices forwarded by access network devices;

[0112] Send command requests to terminal devices through access network devices;

[0113] The terminal device sends the A-IoT upper-layer data content in the command request to the target device;

[0114] The terminal device receives the command response sent by the target device;

[0115] Receive A-IOT upper-layer data content from the command response forwarded by the access network device from the terminal device.

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

[0117] The device ID is sent by the target device;

[0118] The terminal device maintains the correspondence between the first identifier and the second identifier;

[0119] Access network equipment maintains the correspondence between the second and third identifiers;

[0120] The first identifier is used to identify the target device between the terminal device and the target device;

[0121] The second identifier is used to identify the target device on the UU interface;

[0122] The third identifier is used to identify the target device on the NGAP interface;

[0123] The second identifier may be the same as or different from the first identifier;

[0124] The second identifier includes the first identifier;

[0125] The first identifier includes AS-ID;

[0126] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[0127] The third identifier includes the device NGAP ID;

[0128] Terminal equipment and access network equipment transmit data via RRC signaling;

[0129] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[0130] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[0132] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[0133] Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling;

[0134] The inventory response and / or inventory report are sent by the terminal device to the access network device via a second RRC signaling; the inventory report sent by the terminal device to the access network device includes at least one of the device ID, security parameter X, and N2.

[0135] Inventory reports received from access network devices include at least one of the following: device ID, security parameter X, N2, and third identifier;

[0136] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0137] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[0139] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[0140] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[0141] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[0142] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[0143] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[0144] The random response message includes a first identifier assigned by the terminal device to the target device.

[0145] This application also provides a communication method applicable to a target device (such as a device), comprising the following steps:

[0146] S0: Send the device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device can determine or generate a third identifier in response to receiving the second identifier.

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

[0148] The terminal device is configured as a reader;

[0149] The terminal device assigns a first identifier to the target device;

[0150] Upon receiving an inventory request, the terminal device sends an inventory response to the access network device;

[0151] Receive A-IoT paging commands sent by the target device;

[0152] Send the device ID to the terminal device based on the A-IoT paging command;

[0153] The terminal device assigns a second identifier to the target device;

[0154] Terminal devices send inventory reports to core network devices through access network devices;

[0155] Receive command requests from core network devices forwarded by terminal devices;

[0156] The A-IOT upper-layer data content is sent from the terminal equipment and access network equipment to the core network equipment in the command response.

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

[0158] The terminal device maintains the correspondence between the first identifier and the second identifier;

[0159] Access network equipment maintains the correspondence between the second and third identifiers;

[0160] The first identifier is used to identify the target device between the terminal device and the target device;

[0161] The second identifier is used to identify the target device on the UU interface;

[0162] The third identifier is used to identify the target device on the NGAP interface;

[0163] The second identifier may be the same as or different from the first identifier;

[0164] The second identifier includes the first identifier;

[0165] The first identifier includes AS-ID;

[0166] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[0167] The third identifier includes the device NGAP ID;

[0168] Terminal equipment and access network equipment transmit data via RRC signaling;

[0169] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[0170] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[0172] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[0173] Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling;

[0174] The inventory response and / or inventory report are sent by the terminal device to the access network device via a second RRC signaling; the inventory report sent by the terminal device to the access network device includes at least one of the device ID, security parameter X, and N2.

[0175] The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[0176] If the AIoT paging command triggers CBRA, a random access procedure is initiated, and a random response message is received to obtain radio resource information from the random response message.

[0177] If the AIoT paging command triggers CFRA, then the radio resource information is obtained from the AIoT paging command.

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

[0179] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[0180] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[0181] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[0182] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[0183] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[0184] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[0186] The first sending module is used to send the second identifier so that the access network device can determine or generate the third identifier.

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

[0188] The processing module is used to determine or generate a third identifier in response to receiving a second identifier.

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

[0190] The receiving module is used to receive a third identifier, which is determined or generated by the access network device in response to receiving the second identifier.

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

[0192] The second sending module is used to send the device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device can determine or generate a third identifier in response to receiving the second identifier.

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

[0194] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), an access network device (such as a base station), a core network device (such as a CN) or a target device (such as a device), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified in the context.

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

[0196] In this technical solution, the terminal device sends a second identifier so that the access network device can determine or generate a third identifier, thereby supporting the establishment of an end-to-end bearer and improving the A-IoT data communication mechanism. Attached Figure Description

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

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

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

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

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

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

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

[0204] Figure 7 is a schematic diagram of a transmission between a terminal device and an access network device in a processing method shown in an embodiment of this application;

[0205] Figure 8 is another transmission diagram between the terminal device and the access network device in the processing method shown in the embodiment of this application;

[0206] Figure 9 is a schematic diagram of an example scenario interaction of the communication method shown in the second embodiment of this application;

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

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

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

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

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

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

[0213] Figure 16 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

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

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

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

[0217] Implementation methods of this application

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

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

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

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

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

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

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

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

[0226] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), an access network device (such as a base station), a core network device (such as a CN), a target device (such as an A-IoT device), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0259] 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-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; RedCap: Reduced Capability; 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; EPC: Electronic Product Code.

[0260] First Embodiment

[0261] 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 S1:

[0262] Step S1: The terminal device sends a second identifier so that the access network device can determine or generate a third identifier.

[0263] This embodiment takes into account that the existing A-IoT data communication mechanism is not yet perfect. For example, how to establish an end-to-end bearer is not yet clear in the existing network architecture.

[0264] Therefore, this embodiment proposes a technical solution whereby the terminal device sends a second identifier to enable the access network device to determine or generate a third identifier, thereby supporting the establishment of end-to-end bearers and improving the A-IoT data communication mechanism.

[0265] Optionally, the second identifier is determined or generated by the terminal device.

[0266] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0267] Optionally, the device ID is sent by the target device.

[0268] Optionally, the target device is an Internet of Things (IoT) device, such as an A-IoT device.

[0269] Optionally, the device ID is used to uniquely identify an A-IoT device, such as a Device.

[0270] Alternatively, the device ID can be an EPC (Electronic Product Code) or other ID used to identify the target device, such as a temporary ID assigned to a core network device.

[0271] Optionally, EPC is the device ID, i.e., the device ID.

[0272] Optionally, the terminal device is configured as a reader.

[0273] Optionally, the terminal device can perform A-IoT operations as a reader.

[0274] Optionally, the network device configures the terminal device as a reader.

[0275] Alternatively, the network device can be an access network device.

[0276] Alternatively, the access network equipment can be a base station, etc.

[0277] Optionally, when configuring a terminal device as a reader, the network device can configure a new SRB for that terminal device.

[0278] Optionally, the new SRB is specifically designed for sending signaling related to A-IOT operations.

[0279] Optionally, if no new SRB is configured, the terminal device uses SRB1, SRB2, or SRB4 to send signaling related to A-IOT operations.

[0280] Optionally, the terminal device can communicate with IoT devices (such as devices) as a reader and transmit data between the target device (IoT device) and the access network device (such as a base station) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The access network device can forward A-IoT data from the core network device (such as the CN) to the target device, and / or forward the received A-IoT data from the IoT device to the core network device.

[0281] Optionally, as shown in Figures 7 and 8, the terminal device and the access network device transmit data via RRC signaling; alternatively, the access network device and the core network device transmit data via NGAP signaling.

[0282] Optionally, the RRC signaling can be at least one of the following: R2D command, downlink information transmission signaling, D2R response command, uplink information transmission signaling, inventory request, inventory response, command request, and command response.

[0283] Optionally, the RRC signaling may include at least one of the following: the RRC signaling container, RRC-ID, AS-ID, and inventory report.

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

[0285] Optionally, NGAP signaling may include at least one of the following: AS-ID, reader ID of the terminal device, container of NGAP signaling, Device NGAP ID, command response, and inventory report.

[0286] Optionally, the target device and / or terminal device and / or access network device and / or core network device establish an end-to-end bearer through a first identifier and / or a second identifier and / or a third identifier to realize A-IoT data communication.

[0287] Optionally, the signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier.

[0288] Optionally, the signaling sent by the access network device to the core network device and / or the signaling sent by the core network device to the access network device includes a third identifier.

[0289] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0290] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0291] Optionally, the first identifier is assigned to the target device by the terminal device.

[0292] Optionally, the second identifier is assigned by the terminal device to the target device.

[0293] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0294] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0295] Optionally, the second identifier is used to identify the target device on the UU interface.

[0296] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0297] Optionally, the second identifier may be the same as or different from the first identifier.

[0298] Optionally, the second identifier includes the first identifier.

[0299] Optionally, the first identifier includes the AS-ID.

[0300] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0301] Optionally, the third identifier includes the device NGAP ID.

[0302] Optionally, the terminal device assigns a first identifier to the target device.

[0303] Optionally, the terminal device assigns a second identifier to the target device.

[0304] Optionally, the second identifier and the first identifier are different. For example, as shown in Figure 7, an access network device (such as a base station) covers an area with at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.). The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to each target device is RRC-ID. RRC-ID is used to identify the target device between the terminal device and the target device on the uu interface. Data is transmitted on the uu interface through RRC signaling, and the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0305] Optionally, the second identifier is the same as the first identifier. For example, as shown in Figure 8, an access network device (such as a base station) has at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.) in its coverage area. The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to the target device is also AS-ID. That is, the terminal device does not assign RRC-ID. When transmitting data of the target device through RRC signaling on the uu interface, if the data is related to a target device, it needs to carry AS-ID. The access network device maintains the correspondence between AS-ID and device NGAP ID.

[0306] Optionally, as one scenario, the target device sends a device ID to the terminal device.

[0307] Optionally, after receiving the device ID, the terminal device determines or generates an RRC-ID and assigns it to the target device. The RRC-ID is used to identify the target device on the uu interface.

[0308] Optionally, the terminal device establishes and / or maintains the correspondence between AS-ID and RRC-ID.

[0309] Optionally, the terminal device sends an RRC-ID to the access network device.

[0310] Optionally, after receiving the RRC-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0311] Optionally, the access network equipment establishes and / or maintains the mapping between RRC-ID and device NGAP ID.

[0312] Optionally, the access network device sends the device NGAP ID to the core network device.

[0313] By establishing the correspondence between AS-ID and RRC-ID, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0314] Optionally, RRC-ID can be replaced with AS-ID, or AS-ID and the reader ID of the terminal device.

[0315] Optionally, taking the replacement of RRC-ID with AS-ID as an example, as another scenario, the target device sends the device ID to the terminal device.

[0316] Optionally, after receiving the device ID, the terminal device assigns an AS-ID to the target device to identify the target device on the uu interface.

[0317] Optionally, the terminal device sends the AS-ID to the access network device.

[0318] Optionally, after receiving the AS-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0319] Optionally, the access network device establishes and / or maintains the mapping between AS-ID and device NGAP ID.

[0320] Optionally, the access network device sends the device NGAP ID to the core network device.

[0321] By leveraging the AS-ID and the mapping between AS-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is enabled, thereby improving the A-IoT data communication mechanism.

[0322] Optionally, the target device sends its device ID to the terminal device via radio resource information.

[0323] Optionally, radio resource information is obtained based on A-IoT services triggered by core network equipment.

[0324] Optionally, after the core network equipment triggers a service, the core network equipment sends an inventory request to the access network equipment (such as a base station).

[0325] Optionally, the inventory request carries configuration information related to triggering paging, such as device identification information paging ID, AIOT-F node identification, business identification Correlation ID, key parameter N1, etc.

[0326] Optionally, the inventory request is sent by the access network device to the terminal device via the first RRC signaling.

[0327] Optionally, the inventory request is carried in a container within the first RRC signaling.

[0328] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0329] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0330] Optionally, upon receiving an inventory request, the terminal device sends an inventory response to the access network device.

[0331] Optionally, the inventory response is sent by the terminal device to the access network device via a second RRC signaling.

[0332] Optionally, the inventory response is carried in a container within a second RRC signaling.

[0333] Optionally, the second RRC signaling is a D2R response command and / or uplink information transmission signaling.

[0334] Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, and / or ULInformationTransfer.

[0335] Optionally, the access network device sends an inventory response to the core network device.

[0336] Optionally, the terminal device sends an A-IoT paging command to the target device.

[0337] Optionally, the A-IoT paging command includes at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters.

[0338] Optionally, the target device receives an A-IoT paging command sent by the terminal device.

[0339] Optionally, if the target device determines that it needs to respond to the A-IoT paging command, it performs at least one of the following operations:

[0340] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0341] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

[0342] Optionally, the random response message includes a first identifier assigned by the terminal device to the target device.

[0343] Optionally, the random response message includes an AS-ID assigned by the terminal device to the target device. Optionally, the AS-ID uniquely identifies a target device between the terminal device and the target device.

[0344] Optionally, the target device sends MSG3 (message 3) on the acquired radio resources. Optionally, MSG3 carries the device ID.

[0345] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier, that is, maintains the correspondence between the device ID and the first identifier.

[0346] Optionally, after receiving the device ID, the terminal device assigns a second identifier to the target device, for example, assigning an RRC-ID to the target device. Optionally, the RRC-ID is used to uniquely identify a target device on the uu interface.

[0347] Optionally, the terminal device maintains a mapping relationship between the first identifier and the second identifier, that is, the terminal device maintains a correspondence relationship between the first identifier and the second identifier. For example, the terminal device maintains a correspondence relationship between AS-ID and RRC-ID.

[0348] Optionally, the terminal device sends an inventory report to the access network device.

[0349] Optionally, the inventory report is sent via a second RRC signaling.

[0350] Optionally, the inventory report is carried in a container within the first RRC signaling. Optionally, the first RRC signaling includes a second identifier, such as RRC-ID.

[0351] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0352] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0353] Optionally, the inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2.

[0354] Optionally, after receiving the first signaling, the access network device obtains the inventory report from the first signaling and obtains the second identifier, such as RRC-ID.

[0355] Optionally, the access network device assigns a third identifier to the target device. Optionally, the third identifier is the device NGAP ID.

[0356] Optionally, the access network equipment maintains the correspondence between the second identifier and the third identifier.

[0357] Optionally, the access network equipment maintains the mapping between RRC-ID and device NGAP ID.

[0358] Optionally, the access network device sends the device NGAP ID to the core network device.

[0359] Optionally, the access network equipment sends an inventory report to the core network equipment.

[0360] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and third identifier.

[0361] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and device NGAP ID.

[0362] Optionally, core network devices may store a third identifier, such as the device NGAP ID.

[0363] Optionally, the core network equipment sends a command request to the access network equipment.

[0364] Optionally, the command request may carry a third identifier, such as the device NGAP ID.

[0365] Optionally, the access network device forwards the command request to the terminal device.

[0366] Optionally, the command request forwarded by the access network device carries a second identifier, such as RRC-ID.

[0367] Optionally, the command request is sent by the access network device to the terminal device via the first RRC signaling.

[0368] Optionally, the command request is carried in a container within the first RRC signaling.

[0369] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0370] Optionally, the terminal device receives a command request from the core network device forwarded by the access network device.

[0371] Optionally, the command request received by the terminal device includes a second identifier, such as RRC-ID.

[0372] Optionally, the terminal device sends the A-IoT upper-layer data content in the command request to the target device.

[0373] Optionally, the terminal device receives a command response sent by the target device.

[0374] Optionally, the terminal device sends the A-IOT upper-layer data content in the command response to the access network device.

[0375] Optionally, the command response is carried in a container in the form of a second RRC signaling. Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer and / or ULInformationTransfer.

[0376] Optionally, the command response or second RRC signaling sent by the terminal device carries a second identifier, such as RRC-ID.

[0377] Optionally, the first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4.

[0378] Optionally, the access network device sends a command response to the core network device.

[0379] Optionally, the command response may carry a third identifier, such as the device NGAP ID.

[0380] By establishing the correspondence between the first and second identifiers, as well as between the second and third identifiers, end-to-end bearers can be established to enable A-IoT data communication between the target device and the core network device, thereby improving the A-IoT data communication mechanism.

[0381] Through the technical solution of this embodiment, the terminal device sends a second identifier so that the access network device can determine or generate a third identifier, supporting the establishment of end-to-end bearers, thereby improving the A-IoT data communication mechanism.

[0382] Second Embodiment

[0383] Based on the first embodiment of this application, a second embodiment of this application is proposed, which further discloses a communication method for establishing end-to-end bearer in a scenario where a terminal device is used as a reader.

[0384] Optionally, the terminal device sends a second identifier to enable the access network device to determine or generate a third identifier, supporting the establishment of an end-to-end bearer to improve the A-IoT data communication mechanism.

[0385] Optionally, the second identifier is determined or generated by the terminal device.

[0386] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0387] Optionally, the device ID is sent by the target device.

[0388] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0389] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0390] Optionally, the first identifier is assigned to the target device by the terminal device.

[0391] Optionally, the second identifier is assigned by the terminal device to the target device.

[0392] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0393] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0394] Optionally, the second identifier is used to identify the target device on the UU interface.

[0395] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0396] Optionally, the second identifier may be the same as or different from the first identifier.

[0397] Optionally, the second identifier includes the first identifier.

[0398] Optionally, the first identifier includes the AS-ID.

[0399] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0400] Optionally, the third identifier includes the device NGAP ID.

[0401] As shown in Figure 9, the system architecture involved in this embodiment includes: target device (e.g., Device), terminal device (UE Reader), access network device (e.g., base station, gNB), and core network device (e.g., CN). The terminal device is configured as a reader. This system architecture enables the end-to-end bearer communication process established in the scenario where the terminal device acts as a reader, including the following steps 1-17:

[0402] Step 1. The core network equipment sends an inventory request;

[0403] Optionally, if the core network device triggers a service, such as an inventory+command service, the core network device sends an Inventory Request message to the base station gNB.

[0404] Optionally, the Inventory Request message carries configuration information related to triggering paging. This includes device identification information (paging ID), the AIOT-F node identifier, the service identifier (Correlation ID), and key parameter N1.

[0405] Step 2. The access network device sends an inventory request to the terminal device;

[0406] Optionally, after receiving the Inventory Request message, the base station sends the Inventory Request message to the terminal device via RRC signaling.

[0407] Optionally, the RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, or DLInformationTransfer.

[0408] Optionally, the Inventory Request is included in the RRC signaling as a container.

[0409] Step 3. The terminal device sends an inventory response to the access network device;

[0410] Optionally, after receiving the Inventory Request message, the terminal device replies to the base station with an Inventory Response via RRC signaling.

[0411] Optionally, the RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, or ULInformationTransfer.

[0412] Optionally, the Inventory Response can be included in the RRC signaling in the form of a container.

[0413] Step 4. The access network device sends the inventory response to the core network device;

[0414] Optionally, the base station sends the Inventory Response to the core network equipment.

[0415] Step 5. The terminal device sends an A-IOT command to the target device;

[0416] Optionally, the terminal device sends an A-IOT paging message, i.e., an A-IOT command, to the device.

[0417] Optionally, the information carried by the A-IOT paging message includes at least one of the following: device identification information paging ID, key parameter N1, random access resource configuration parameters, etc.

[0418] Step 6. The target device receives the A-IOT command sent by the terminal device and determines whether it needs to respond to the paging.

[0419] Optionally, the device receives an A-IOT paging command from the network device side sent by the terminal device. If the device determines that it needs to respond to the paging message, it performs at least one of the following operations:

[0420] If the A-IOT paging command triggers CBRA, the device initiates a random access procedure, receives a random response message, and obtains radio resource information for sending MSG3 (specifically, the device ID) from it. Optionally, the random access response message contains an AS-ID assigned by the terminal device. Optionally, the AS-ID is used to uniquely identify a device between the terminal device and the device.

[0421] Optionally, the random access process includes at least one of the following: the terminal device sending an access trigger command to the device, receiving MSG1 (message 1) sent by the device, and sending MSG2 (message 2) to the device.

[0422] Optionally, MSG1 is a random access request, and MSG1 carries a random access ID. Optionally, MSG2 is a random access response, and MSG2 carries at least one of the following: random access ID, RN16, AS-ID, and radio resource information for sending MSG3.

[0423] If the A-IOT paging command triggers CFRA, the device obtains the radio resource information for sending MSG3 (specifically, the device ID) from the A-IOT paging message.

[0424] Step 7. The target device sends its device ID via MSG3;

[0425] Optionally, the Device sends the device ID, i.e., MSG3 (message 3), on the acquired radio resources.

[0426] Optionally, MSG3 is a D2R upper-layer data transmission command that can carry at least one of EPC (i.e., Device ID), security parameter X, and N2.

[0427] Step 8. After receiving the device ID, the terminal device assigns a second identifier to the target device and maintains the mapping between the first identifier and the second identifier;

[0428] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier.

[0429] Optionally, after receiving the device ID, the terminal device assigns an RRC-ID to the device.

[0430] Optionally, after receiving the device ID, the terminal device maintains the mapping between EPC and RRC-ID and assigns an RRC-ID to the device. Optionally, the RRC-ID is used to uniquely identify a device on the uu interface.

[0431] Optionally, the terminal device maintains a mapping, i.e., a correspondence, between the first identifier and the second identifier.

[0432] Optionally, the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0433] Step 9. The terminal device sends an inventory report to the access network device;

[0434] Optionally, the terminal device sends an Inventory Report to the base station via RRC signaling.

[0435] Optionally, the RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, or ULInformationTransfer.

[0436] Optionally, the Inventory Report is included in the RRC signaling as a container.

[0437] Optionally, the Inventory Report includes at least one of the following: Device ID, security parameter X, and N2.

[0438] Optionally, the RRC signaling includes an RRC-ID.

[0439] Step 10. The access network device assigns a third identifier to the target device and maintains the mapping between the second identifier and the second identifier;

[0440] Optionally, after receiving the aforementioned RRC signaling, the access network device obtains the inventory report and the second identifier, assigns a third identifier to the target device, and maintains the mapping between the second identifier and the second identifier, i.e., the correspondence.

[0441] Optionally, upon receiving the aforementioned RRC signaling, the base station obtains the Inventory Report and the RRC-ID, assigns a device NGAP ID to the device, and the gNB maintains the correspondence between the RRC-ID and the device NGAP ID.

[0442] Step 11. The access network equipment sends an inventory report to the core network equipment;

[0443] Optionally, the base station sends an Inventory Report message to the core network equipment.

[0444] Optionally, the Inventory Report includes at least one of the following: Device ID, security parameter X, N2, NGAP-ID.

[0445] Optionally, the core network equipment calculates security parameters, i.e., generate X = Fun1(key1, N1), Key2 = func2(key1, N1, N2).

[0446] Step 12. The core network device sends a command request to the access network device;

[0447] Optionally, the command request may carry information about the upper-layer data being protected by key2 and the device NGAP ID.

[0448] Step 13. The access network device sends a command request to the terminal device;

[0449] Optionally, after receiving the Command Request message from the core network equipment, the base station sends the Command Request message to the terminal equipment via RRC signaling.

[0450] Optionally, the RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, or DLInformationTransfer.

[0451] Optionally, the Inventory Request is included in the RRC signaling as a container, and optionally, the RRC signaling also includes the RRC-ID.

[0452] Step 14. The terminal device sends a command request to the target device;

[0453] Optionally, the terminal device sends the content in the Command Request to the device via an R2D upper-layer data transmission command. Optionally, the R2D upper-layer data transmission command carries the AS-ID.

[0454] Step 15. The target device sends a D2R response command to the terminal device;

[0455] Optionally, the Device sends the content in the Command Response to the terminal device via D2R upper-layer data transmission commands.

[0456] Step 16. The terminal device sends a command response to the access network device;

[0457] Optionally, the terminal device sends the contents of the Command Response to the gNB via RRC signaling.

[0458] Optionally, the RC signaling can be a new RRC signaling, such as D2RInformationTransfer, or ULInformationTransfer.

[0459] Optionally, the content of the Command Response is included in the RRC signaling in the form of a container. Optionally, the RRC signaling also includes the RRC-ID.

[0460] Step 17. The access network device sends a command response to the core network device.

[0461] Optionally, the base station sends a Command Response to the core network equipment; optionally, the command response includes the device NGAP ID.

[0462] By establishing the correspondence between the AS-ID and RRC-ID second identifiers, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0463] It should be noted that the RRC signaling transmitted on the uu interface can carry the following signaling: the content of at least one of the fields in the Inventory Request, Inventory Response, Inventory Report, Command Request, and Command Response messages, or these messages as a whole can be carried in the RRC signaling in the form of a container r.

[0464] Optionally, RRC signaling can also carry field content from NGAP signaling.

[0465] Optionally, the upper-layer content of A-IoT services can be carried in RRC signaling or NGAP signaling in a containerized manner.

[0466] In this embodiment, the terminal device sends a second identifier to enable the access network device to determine or generate a third identifier. The terminal device maintains the correspondence between the first and second identifiers, and the access network device maintains the correspondence between the second and third identifiers. Through the correspondence between the first and second identifiers and the correspondence between the second and third identifiers, end-to-end bearers can be established to realize A-IoT data communication from the target device to the core network device, thereby improving the A-IoT data communication mechanism.

[0467] Third Embodiment

[0468] Referring to Figure 10, 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 access network equipment (such as a base station), and includes step S2:

[0469] S2: Upon receiving the second identifier, the access network device determines or generates a third identifier.

[0470] This embodiment proposes a technical solution in which the access network device, upon receiving the second identifier, determines or generates a third identifier, supporting the establishment of end-to-end bearers to improve the A-IoT data communication mechanism.

[0471] Optionally, the second identifier is determined or generated by the terminal device.

[0472] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0473] Optionally, the device ID is sent by the target device.

[0474] Optionally, the target device is an Internet of Things (IoT) device, such as an A-IoT device.

[0475] Optionally, the device ID is used to uniquely identify an A-IoT device, such as a Device.

[0476] Alternatively, the device ID can be an EPC (Electronic Product Code) or other ID used to identify the target device, such as a temporary ID assigned by the core network.

[0477] Optionally, EPC is the device ID, i.e., the device ID.

[0478] Optionally, the terminal device is configured as a reader.

[0479] Optionally, the terminal device can perform A-IoT operations as a reader.

[0480] Optionally, the network device configures the terminal device as a reader.

[0481] Alternatively, the network device can be an access network device.

[0482] Alternatively, the access network equipment can be a base station, etc.

[0483] Optionally, when configuring a terminal device as a reader, the network device can configure a new SRB for that terminal device.

[0484] Optionally, the new SRB is specifically designed for sending signaling related to A-IOT operations.

[0485] Optionally, if no new SRB is configured, the terminal device uses SRB1, SRB2, or SRB4 to send signaling related to A-IOT operations.

[0486] Optionally, the terminal device can communicate with IoT devices (such as devices) as a reader and transmit data between the target device (IoT device) and the access network device (such as a base station) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The access network device can forward A-IoT data from the core network device (such as the CN) to the target device, and / or forward the received A-IoT data from the IoT device to the core network device.

[0487] Optionally, as shown in Figures 7 and 8, the terminal device and the access network device transmit data via RRC signaling; alternatively, the access network device and the core network device transmit data via NGAP signaling.

[0488] Optionally, the RRC signaling can be at least one of the following: R2D command, downlink information transmission signaling, D2R response command, uplink information transmission signaling, inventory request, inventory response, command request, and command response.

[0489] Optionally, the RRC signaling may include at least one of the following: the RRC signaling container, RRC-ID, AS-ID, and inventory report.

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

[0491] Optionally, NGAP signaling may include at least one of the following: AS-ID, reader ID of the terminal device, container of NGAP signaling, Device NGAP ID, command response, and inventory report.

[0492] Optionally, the target device and / or terminal device and / or access network device and / or core network device establish an end-to-end bearer through a first identifier and / or a second identifier and / or a third identifier to realize A-IoT data communication.

[0493] Optionally, the signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier.

[0494] Optionally, the signaling sent by the access network device to the core network device and / or the signaling sent by the core network device to the access network device includes a third identifier.

[0495] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0496] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0497] Optionally, the first identifier is assigned to the target device by the terminal device.

[0498] Optionally, the second identifier is assigned by the terminal device to the target device.

[0499] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0500] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0501] Optionally, the second identifier is used to identify the target device on the UU interface.

[0502] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0503] Optionally, the second identifier may be the same as or different from the first identifier.

[0504] Optionally, the second identifier includes the first identifier.

[0505] Optionally, the first identifier includes the AS-ID.

[0506] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0507] Optionally, the third identifier includes the device NGAP ID.

[0508] Optionally, the terminal device assigns a first identifier to the target device.

[0509] Optionally, the terminal device assigns a second identifier to the target device.

[0510] Optionally, the second identifier and the first identifier are different. For example, as shown in Figure 7, an access network device (such as a base station) covers an area with at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.). The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to each target device is RRC-ID. RRC-ID is used to identify the target device between the terminal device and the target device on the uu interface. Data is transmitted on the uu interface through RRC signaling, and the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0511] Optionally, the second identifier is the same as the first identifier. For example, as shown in Figure 8, an access network device (such as a base station) has at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.) in its coverage area. The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to the target device is also AS-ID. That is, the terminal device does not assign RRC-ID. When transmitting data of the target device through RRC signaling on the uu interface, if the data is related to a target device, it needs to carry AS-ID. The access network device maintains the correspondence between AS-ID and device NGAP ID.

[0512] Optionally, as one scenario, the target device sends a device ID to the terminal device.

[0513] Optionally, after receiving the device ID, the terminal device determines or generates an RRC-ID and assigns it to the target device. The RRC-ID is used to identify the target device on the uu interface.

[0514] Optionally, the terminal device establishes and / or maintains the correspondence between AS-ID and RRC-ID.

[0515] Optionally, the terminal device sends an RRC-ID to the access network device.

[0516] Optionally, after receiving the RRC-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0517] Optionally, the access network equipment establishes and / or maintains the mapping between RRC-ID and device NGAP ID.

[0518] Optionally, the access network device sends the device NGAP ID to the core network device.

[0519] By establishing the correspondence between AS-ID and RRC-ID, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0520] Optionally, RRC-ID can be replaced with AS-ID, or AS-ID and the reader ID of the terminal device.

[0521] Optionally, taking the replacement of RRC-ID with AS-ID as an example, as another scenario, the target device sends the device ID to the terminal device.

[0522] Optionally, after receiving the device ID, the terminal device assigns an AS-ID to the target device to identify the target device on the uu interface.

[0523] Optionally, the terminal device sends the AS-ID to the access network device.

[0524] Optionally, after receiving the AS-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0525] Optionally, the access network device establishes and / or maintains the mapping between AS-ID and device NGAP ID.

[0526] Optionally, the access network device sends the device NGAP ID to the core network device.

[0527] By leveraging the AS-ID and the mapping between AS-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is enabled, thereby improving the A-IoT data communication mechanism.

[0528] Optionally, the target device sends its device ID to the terminal device via radio resource information.

[0529] Optionally, radio resource information is obtained based on A-IoT services triggered by core network equipment.

[0530] Optionally, after the core network equipment triggers a service, the core network equipment sends an inventory request to the access network equipment (such as a base station).

[0531] Optionally, the inventory request carries configuration information related to triggering paging, such as device identification information paging ID, AIOT-F node identification, business identification Correlation ID, key parameter N1, etc.

[0532] Optionally, the inventory request is sent by the access network device to the terminal device via the first RRC signaling.

[0533] Optionally, the inventory request is carried in a container within the first RRC signaling.

[0534] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0535] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0536] Optionally, upon receiving an inventory request, the terminal device sends an inventory response to the access network device.

[0537] Optionally, the inventory response is sent by the terminal device to the access network device via a second RRC signaling.

[0538] Optionally, the inventory response is carried in a container within a second RRC signaling.

[0539] Optionally, the second RRC signaling is a D2R response command and / or uplink information transmission signaling.

[0540] Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, and / or ULInformationTransfer.

[0541] Optionally, the access network device sends an inventory response to the core network device.

[0542] Optionally, the terminal device sends an A-IoT paging command to the target device.

[0543] Optionally, the A-IoT paging command includes at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters.

[0544] Optionally, the target device receives an A-IoT paging command sent by the terminal device.

[0545] Optionally, if the target device determines that it needs to respond to the A-IoT paging command, it performs at least one of the following operations:

[0546] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0547] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

[0548] Optionally, the random response message includes a first identifier assigned by the terminal device to the target device.

[0549] Optionally, the random response message includes an AS-ID assigned by the terminal device to the target device. Optionally, the AS-ID uniquely identifies a target device between the terminal device and the target device.

[0550] Optionally, the target device sends MSG3 (message 3) on the acquired radio resources. Optionally, MSG3 carries the device ID.

[0551] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier, that is, maintains the correspondence between the device ID and the first identifier.

[0552] Optionally, after receiving the device ID, the terminal device assigns a second identifier to the target device, for example, assigning an RRC-ID to the target device. Optionally, the RRC-ID is used to uniquely identify a target device on the uu interface.

[0553] Optionally, the terminal device maintains a mapping relationship between the first identifier and the second identifier, that is, the terminal device maintains a correspondence relationship between the first identifier and the second identifier. For example, the terminal device maintains a correspondence relationship between AS-ID and RRC-ID.

[0554] Optionally, the terminal device sends an inventory report to the access network device.

[0555] Optionally, the inventory report is sent via a second RRC signaling.

[0556] Optionally, the inventory report is carried in a container within the first RRC signaling. Optionally, the first RRC signaling includes a second identifier, such as RRC-ID.

[0557] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0558] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0559] Optionally, the inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2.

[0560] Optionally, after receiving the first signaling, the access network device obtains the inventory report from the first signaling and obtains the second identifier, such as RRC-ID.

[0561] Optionally, the access network device assigns a third identifier to the target device. Optionally, the third identifier is the device NGAP ID.

[0562] Optionally, the access network equipment maintains the correspondence between the second identifier and the third identifier.

[0563] Optionally, the access network equipment maintains the mapping between RRC-ID and device NGAP ID.

[0564] Optionally, the access network device sends the device NGAP ID to the core network device.

[0565] Optionally, the access network equipment sends an inventory report to the core network equipment.

[0566] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and third identifier.

[0567] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and device NGAP ID.

[0568] Optionally, core network devices may store a third identifier, such as the device NGAP ID.

[0569] Optionally, the core network equipment sends a command request to the access network equipment.

[0570] Optionally, the command request may carry a third identifier, such as the device NGAP ID.

[0571] Optionally, the access network device forwards the command request to the terminal device.

[0572] Optionally, the command request forwarded by the access network device carries a second identifier, such as RRC-ID.

[0573] Optionally, the command request is sent by the access network device to the terminal device via the first RRC signaling.

[0574] Optionally, the command request is carried in a container within the first RRC signaling.

[0575] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0576] Optionally, the terminal device receives a command request from the core network device forwarded by the access network device.

[0577] Optionally, the command request received by the terminal device includes a second identifier, such as RRC-ID.

[0578] Optionally, the terminal device sends the A-IoT upper-layer data content in the command request to the target device.

[0579] Optionally, the terminal device receives a command response sent by the target device.

[0580] Optionally, the terminal device sends the A-IOT upper-layer data content in the command response to the access network device.

[0581] Optionally, the command response is carried in a container in the form of a second RRC signaling. Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer and / or ULInformationTransfer.

[0582] Optionally, the command response or second RRC signaling sent by the terminal device carries a second identifier, such as RRC-ID.

[0583] Optionally, the first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4.

[0584] Optionally, the access network device sends a command response to the core network device.

[0585] Optionally, the command response may carry a third identifier, such as the device NGAP ID.

[0586] By establishing the correspondence between the first and second identifiers, as well as between the second and third identifiers, end-to-end bearers can be established to enable A-IoT data communication between the target device and the core network device, thereby improving the A-IoT data communication mechanism.

[0587] Through the technical solution of this embodiment, the access network device responds to the receipt of the second identifier, determines or generates the third identifier, supports the establishment of end-to-end bearers, and thus improves the A-IoT data communication mechanism.

[0588] Fourth embodiment

[0589] Referring to Figure 11, 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 core network equipment (such as CN), including step S3:

[0590] S3: The core network equipment receives the third identifier, which is determined or generated by the access network equipment in response to receiving the second identifier.

[0591] This embodiment proposes a technical solution whereby the terminal device sends a second identifier to enable the access network device to determine or generate a third identifier, thereby supporting the establishment of an end-to-end bearer and improving the A-IoT data communication mechanism.

[0592] Optionally, the second identifier is determined or generated by the terminal device.

[0593] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0594] Optionally, the device ID is sent by the target device.

[0595] Optionally, the target device is an Internet of Things (IoT) device, such as an A-IoT device.

[0596] Optionally, the device ID is used to uniquely identify an A-IoT device, such as a Device.

[0597] Alternatively, the device ID can be an EPC (Electronic Product Code) or other ID used to identify the target device, such as a temporary ID assigned by the core network.

[0598] Optionally, EPC is the device ID, i.e., the device ID.

[0599] Optionally, the terminal device is configured as a reader.

[0600] Optionally, the terminal device can perform A-IoT operations as a reader.

[0601] Optionally, the network device configures the terminal device as a reader.

[0602] Alternatively, the network device can be an access network device.

[0603] Alternatively, the access network equipment can be a base station, etc.

[0604] Optionally, when configuring a terminal device as a reader, the network device can configure a new SRB for that terminal device.

[0605] Optionally, the new SRB is specifically designed for sending signaling related to A-IOT operations.

[0606] Optionally, if no new SRB is configured, the terminal device uses SRB1, SRB2, or SRB4 to send signaling related to A-IOT operations.

[0607] Optionally, the terminal device can communicate with IoT devices (such as devices) as a reader and transmit data between the target device (IoT device) and the access network device (such as a base station) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The access network device can forward A-IoT data from the core network device (such as the CN) to the target device, and / or forward the received A-IoT data from the IoT device to the core network device.

[0608] Optionally, as shown in Figures 7 and 8, the terminal device and the access network device transmit data via RRC signaling; alternatively, the access network device and the core network device transmit data via NGAP signaling.

[0609] Optionally, the RRC signaling can be at least one of the following: R2D command, downlink information transmission signaling, D2R response command, uplink information transmission signaling, inventory request, inventory response, command request, and command response.

[0610] Optionally, the RRC signaling may include at least one of the following: the RRC signaling container, RRC-ID, AS-ID, and inventory report.

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

[0612] Optionally, NGAP signaling may include at least one of the following: AS-ID, reader ID of the terminal device, container of NGAP signaling, Device NGAP ID, command response, and inventory report.

[0613] Optionally, the target device and / or terminal device and / or access network device and / or core network device establish an end-to-end bearer through a first identifier and / or a second identifier and / or a third identifier to realize A-IoT data communication.

[0614] Optionally, the signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier.

[0615] Optionally, the signaling sent by the access network device to the core network device and / or the signaling sent by the core network device to the access network device includes a third identifier.

[0616] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0617] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0618] Optionally, the first identifier is assigned to the target device by the terminal device.

[0619] Optionally, the second identifier is assigned by the terminal device to the target device.

[0620] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0621] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0622] Optionally, the second identifier is used to identify the target device on the UU interface.

[0623] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0624] Optionally, the second identifier may be the same as or different from the first identifier.

[0625] Optionally, the second identifier includes the first identifier.

[0626] Optionally, the first identifier includes the AS-ID.

[0627] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0628] Optionally, the third identifier includes the device NGAP ID.

[0629] Optionally, the terminal device assigns a first identifier to the target device.

[0630] Optionally, the terminal device assigns a second identifier to the target device.

[0631] Optionally, the second identifier and the first identifier are different. For example, as shown in Figure 7, an access network device (such as a base station) covers an area with at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.). The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to each target device is RRC-ID. RRC-ID is used to identify the target device between the terminal device and the target device on the uu interface. Data is transmitted on the uu interface through RRC signaling, and the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0632] Optionally, the second identifier is the same as the first identifier. For example, as shown in Figure 8, an access network device (such as a base station) has at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.) in its coverage area. The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to the target device is also AS-ID. That is, the terminal device does not assign RRC-ID. When transmitting data of the target device through RRC signaling on the uu interface, if the data is related to a target device, it needs to carry AS-ID. The access network device maintains the correspondence between AS-ID and device NGAP ID.

[0633] Optionally, as one scenario, the target device sends a device ID to the terminal device.

[0634] Optionally, after receiving the device ID, the terminal device determines or generates an RRC-ID and assigns it to the target device. The RRC-ID is used to identify the target device on the uu interface.

[0635] Optionally, the terminal device establishes and / or maintains the correspondence between AS-ID and RRC-ID.

[0636] Optionally, the terminal device sends an RRC-ID to the access network device.

[0637] Optionally, after receiving the RRC-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0638] Optionally, the access network equipment establishes and / or maintains the mapping between RRC-ID and device NGAP ID.

[0639] Optionally, the access network device sends the device NGAP ID to the core network device.

[0640] By establishing the correspondence between AS-ID and RRC-ID, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0641] Optionally, RRC-ID can be replaced with AS-ID, or AS-ID and the reader ID of the terminal device.

[0642] Optionally, taking the replacement of RRC-ID with AS-ID as an example, as another scenario, the target device sends the device ID to the terminal device.

[0643] Optionally, after receiving the device ID, the terminal device assigns an AS-ID to the target device to identify the target device on the uu interface.

[0644] Optionally, the terminal device sends the AS-ID to the access network device.

[0645] Optionally, after receiving the AS-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0646] Optionally, the access network device establishes and / or maintains the mapping between AS-ID and device NGAP ID.

[0647] Optionally, the access network device sends the device NGAP ID to the core network device.

[0648] By leveraging the AS-ID and the mapping between AS-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is enabled, thereby improving the A-IoT data communication mechanism.

[0649] Optionally, the target device sends its device ID to the terminal device via radio resource information.

[0650] Optionally, radio resource information is obtained based on A-IoT services triggered by core network equipment.

[0651] Optionally, after the core network equipment triggers a service, the core network equipment sends an inventory request to the access network equipment (such as a base station).

[0652] Optionally, the inventory request carries configuration information related to triggering paging, such as device identification information paging ID, AIOT-F node identification, business identification Correlation ID, key parameter N1, etc.

[0653] Optionally, the inventory request is sent by the access network device to the terminal device via the first RRC signaling.

[0654] Optionally, the inventory request is carried in a container within the first RRC signaling.

[0655] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0656] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0657] Optionally, upon receiving an inventory request, the terminal device sends an inventory response to the access network device.

[0658] Optionally, the inventory response is sent by the terminal device to the access network device via a second RRC signaling.

[0659] Optionally, the inventory response is carried in a container within a second RRC signaling.

[0660] Optionally, the second RRC signaling is a D2R response command and / or uplink information transmission signaling.

[0661] Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, and / or ULInformationTransfer.

[0662] Optionally, the access network device sends an inventory response to the core network device.

[0663] Optionally, the terminal device sends an A-IoT paging command to the target device.

[0664] Optionally, the A-IoT paging command includes at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters.

[0665] Optionally, the target device receives an A-IoT paging command sent by the terminal device.

[0666] Optionally, if the target device determines that it needs to respond to the A-IoT paging command, it performs at least one of the following operations:

[0667] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0668] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

[0669] Optionally, the random response message includes a first identifier assigned by the terminal device to the target device.

[0670] Optionally, the random response message includes an AS-ID assigned by the terminal device to the target device. Optionally, the AS-ID uniquely identifies a target device between the terminal device and the target device.

[0671] Optionally, the target device sends MSG3 (message 3) on the acquired radio resources. Optionally, MSG3 carries the device ID.

[0672] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier, that is, maintains the correspondence between the device ID and the first identifier.

[0673] Optionally, after receiving the device ID, the terminal device assigns a second identifier to the target device, for example, assigning an RRC-ID to the target device. Optionally, the RRC-ID is used to uniquely identify a target device on the uu interface.

[0674] Optionally, the terminal device maintains a mapping relationship between the first identifier and the second identifier, that is, the terminal device maintains a correspondence relationship between the first identifier and the second identifier. For example, the terminal device maintains a correspondence relationship between AS-ID and RRC-ID.

[0675] Optionally, the terminal device sends an inventory report to the access network device.

[0676] Optionally, the inventory report is sent via a second RRC signaling.

[0677] Optionally, the inventory report is carried in a container within the first RRC signaling. Optionally, the first RRC signaling includes a second identifier, such as RRC-ID.

[0678] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0679] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0680] Optionally, the inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2.

[0681] Optionally, after receiving the first signaling, the access network device obtains the inventory report from the first signaling and obtains the second identifier, such as RRC-ID.

[0682] Optionally, the access network device assigns a third identifier to the target device. Optionally, the third identifier is the device NGAP ID.

[0683] Optionally, the access network equipment maintains the correspondence between the second identifier and the third identifier.

[0684] Optionally, the access network equipment maintains the mapping between RRC-ID and device NGAP ID.

[0685] Optionally, the access network device sends the device NGAP ID to the core network device.

[0686] Optionally, the access network equipment sends an inventory report to the core network equipment.

[0687] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and third identifier.

[0688] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and device NGAP ID.

[0689] Optionally, core network devices may store a third identifier, such as the device NGAP ID.

[0690] Optionally, the core network equipment sends a command request to the access network equipment.

[0691] Optionally, the command request may carry a third identifier, such as the device NGAP ID.

[0692] Optionally, the access network device forwards the command request to the terminal device.

[0693] Optionally, the command request forwarded by the access network device carries a second identifier, such as RRC-ID.

[0694] Optionally, the command request is sent by the access network device to the terminal device via the first RRC signaling.

[0695] Optionally, the command request is carried in a container within the first RRC signaling.

[0696] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0697] Optionally, the terminal device receives a command request from the core network device forwarded by the access network device.

[0698] Optionally, the command request received by the terminal device includes a second identifier, such as RRC-ID.

[0699] Optionally, the terminal device sends the A-IoT upper-layer data content in the command request to the target device.

[0700] Optionally, the terminal device receives a command response sent by the target device.

[0701] Optionally, the terminal device sends the A-IOT upper-layer data content in the command response to the access network device.

[0702] Optionally, the command response is carried in a container in the form of a second RRC signaling. Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer and / or ULInformationTransfer.

[0703] Optionally, the command response or second RRC signaling sent by the terminal device carries a second identifier, such as RRC-ID.

[0704] Optionally, the first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4.

[0705] Optionally, the access network device sends a command response to the core network device.

[0706] Optionally, the command response may carry a third identifier, such as the device NGAP ID.

[0707] By establishing the correspondence between the first and second identifiers, as well as between the second and third identifiers, end-to-end bearers can be established to enable A-IoT data communication between the target device and the core network device, thereby improving the A-IoT data communication mechanism.

[0708] Through the technical solution of this embodiment, the core network device receives a third identifier, which is determined or generated by the access network device in response to receiving the second identifier, supporting the establishment of end-to-end bearers, thereby improving the A-IoT data communication mechanism.

[0709] Fifth Embodiment

[0710] Referring to Figure 12, which is a flowchart illustrating the communication method of the fifth embodiment of this application, the communication method of this embodiment can be applied to a target device (such as a device), and includes step S0:

[0711] S0: The target device sends a device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device, in response to receiving the second identifier, determines or generates a third identifier.

[0712] This embodiment proposes a technical solution whereby the target device sends a device ID, enabling the terminal device to determine or generate a second identifier and send the second identifier, and the access network device, upon receiving the second identifier, determines or generates a third identifier, supporting the establishment of end-to-end bearers to improve the A-IoT data communication mechanism.

[0713] Optionally, the second identifier is determined or generated by the terminal device.

[0714] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0715] Optionally, the target device is an Internet of Things (IoT) device, such as an A-IoT device.

[0716] Optionally, the device ID is used to uniquely identify an A-IoT device, such as a Device.

[0717] Alternatively, the device ID can be an EPC (Electronic Product Code) or other ID used to identify the target device, such as a temporary ID assigned by the core network.

[0718] Optionally, EPC is the device ID, i.e., the device ID.

[0719] Optionally, the terminal device is configured as a reader.

[0720] Optionally, the terminal device can perform A-IoT operations as a reader.

[0721] Optionally, the network device configures the terminal device as a reader.

[0722] Alternatively, the network device can be an access network device.

[0723] Alternatively, the access network equipment can be a base station, etc.

[0724] Optionally, when configuring a terminal device as a reader, the network device can configure a new SRB for that terminal device.

[0725] Optionally, the new SRB is specifically designed for sending signaling related to A-IOT operations.

[0726] Optionally, if no new SRB is configured, the terminal device uses SRB1, SRB2, or SRB4 to send signaling related to A-IOT operations.

[0727] Optionally, the terminal device can communicate with IoT devices (such as devices) as a reader and transmit data between the target device (IoT device) and the access network device (such as a base station) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The access network device can forward A-IoT data from the core network device (such as the CN) to the target device, and / or forward the received A-IoT data from the IoT device to the core network device.

[0728] Optionally, as shown in Figures 7 and 8, the terminal device and the access network device transmit data via RRC signaling; alternatively, the access network device and the core network device transmit data via NGAP signaling.

[0729] Optionally, the RRC signaling can be at least one of the following: R2D command, downlink information transmission signaling, D2R response command, uplink information transmission signaling, inventory request, inventory response, command request, and command response.

[0730] Optionally, the RRC signaling may include at least one of the following: the RRC signaling container, RRC-ID, AS-ID, and inventory report.

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

[0732] Optionally, NGAP signaling may include at least one of the following: AS-ID, reader ID of the terminal device, container of NGAP signaling, Device NGAP ID, command response, and inventory report.

[0733] Optionally, the target device and / or terminal device and / or access network device and / or core network device establish an end-to-end bearer through a first identifier and / or a second identifier and / or a third identifier to realize A-IoT data communication.

[0734] Optionally, the signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier.

[0735] Optionally, the signaling sent by the access network device to the core network device and / or the signaling sent by the core network device to the access network device includes a third identifier.

[0736] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0737] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0738] Optionally, the first identifier is assigned to the target device by the terminal device.

[0739] Optionally, the second identifier is assigned by the terminal device to the target device.

[0740] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0741] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0742] Optionally, the second identifier is used to identify the target device on the UU interface.

[0743] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0744] Optionally, the second identifier may be the same as or different from the first identifier.

[0745] Optionally, the second identifier includes the first identifier.

[0746] Optionally, the first identifier includes the AS-ID.

[0747] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0748] Optionally, the third identifier includes the device NGAP ID.

[0749] Optionally, the terminal device assigns a first identifier to the target device.

[0750] Optionally, the terminal device assigns a second identifier to the target device.

[0751] Optionally, the second identifier and the first identifier are different. For example, as shown in Figure 7, an access network device (such as a base station) covers an area with at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.). The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to each target device is RRC-ID. RRC-ID is used to identify the target device between the terminal device and the target device on the uu interface. Data is transmitted on the uu interface through RRC signaling, and the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0752] Optionally, the second identifier is the same as the first identifier. For example, as shown in Figure 8, an access network device (such as a base station) has at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.) in its coverage area. The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to the target device is also AS-ID. That is, the terminal device does not assign RRC-ID. When transmitting data of the target device through RRC signaling on the uu interface, if the data is related to a target device, it needs to carry AS-ID. The access network device maintains the correspondence between AS-ID and device NGAP ID.

[0753] Optionally, as one scenario, the target device sends a device ID to the terminal device.

[0754] Optionally, after receiving the device ID, the terminal device determines or generates an RRC-ID and assigns it to the target device. The RRC-ID is used to identify the target device on the uu interface.

[0755] Optionally, the terminal device establishes and / or maintains the correspondence between AS-ID and RRC-ID.

[0756] Optionally, the terminal device sends an RRC-ID to the access network device.

[0757] Optionally, after receiving the RRC-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0758] Optionally, the access network equipment establishes and / or maintains the mapping between RRC-ID and device NGAP ID.

[0759] Optionally, the access network device sends the device NGAP ID to the core network device.

[0760] By establishing the correspondence between AS-ID and RRC-ID, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0761] Optionally, RRC-ID can be replaced with AS-ID, or AS-ID and the reader ID of the terminal device.

[0762] Optionally, taking the replacement of RRC-ID with AS-ID as an example, as another scenario, the target device sends the device ID to the terminal device.

[0763] Optionally, after receiving the device ID, the terminal device assigns an AS-ID to the target device to identify the target device on the uu interface.

[0764] Optionally, the terminal device sends the AS-ID to the access network device.

[0765] Optionally, after receiving the AS-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0766] Optionally, the access network device establishes and / or maintains the mapping between AS-ID and device NGAP ID.

[0767] Optionally, the access network device sends the device NGAP ID to the core network device.

[0768] By leveraging the AS-ID and the mapping between AS-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is enabled, thereby improving the A-IoT data communication mechanism.

[0769] Optionally, the target device sends its device ID to the terminal device via radio resource information.

[0770] Optionally, radio resource information is obtained based on A-IoT services triggered by core network equipment.

[0771] Optionally, after the core network equipment triggers a service, the core network equipment sends an inventory request to the access network equipment (such as a base station).

[0772] Optionally, the inventory request carries configuration information related to triggering paging, such as device identification information paging ID, AIOT-F node identification, business identification Correlation ID, key parameter N1, etc.

[0773] Optionally, the inventory request is sent by the access network device to the terminal device via the first RRC signaling.

[0774] Optionally, the inventory request is carried in a container within the first RRC signaling.

[0775] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0776] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0777] Optionally, upon receiving an inventory request, the terminal device sends an inventory response to the access network device.

[0778] Optionally, the inventory response is sent by the terminal device to the access network device via a second RRC signaling.

[0779] Optionally, the inventory response is carried in a container within a second RRC signaling.

[0780] Optionally, the second RRC signaling is a D2R response command and / or uplink information transmission signaling.

[0781] Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, and / or ULInformationTransfer.

[0782] Optionally, the access network device sends an inventory response to the core network device.

[0783] Optionally, the terminal device sends an A-IoT paging command to the target device.

[0784] Optionally, the A-IoT paging command includes at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters.

[0785] Optionally, the target device receives an A-IoT paging command sent by the terminal device.

[0786] Optionally, if the target device determines that it needs to respond to the A-IoT paging command, it performs at least one of the following operations:

[0787] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0788] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

[0789] Optionally, the random response message includes a first identifier assigned by the terminal device to the target device.

[0790] Optionally, the random response message includes an AS-ID assigned by the terminal device to the target device. Optionally, the AS-ID uniquely identifies a target device between the terminal device and the target device.

[0791] Optionally, the target device sends MSG3 (message 3) on the acquired radio resources. Optionally, MSG3 carries the device ID.

[0792] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier, that is, maintains the correspondence between the device ID and the first identifier.

[0793] Optionally, after receiving the device ID, the terminal device assigns a second identifier to the target device, for example, assigning an RRC-ID to the target device. Optionally, the RRC-ID is used to uniquely identify a target device on the uu interface.

[0794] Optionally, the terminal device maintains a mapping relationship between the first identifier and the second identifier, that is, the terminal device maintains a correspondence relationship between the first identifier and the second identifier. For example, the terminal device maintains a correspondence relationship between AS-ID and RRC-ID.

[0795] Optionally, the terminal device sends an inventory report to the access network device.

[0796] Optionally, the inventory report is sent via a second RRC signaling.

[0797] Optionally, the inventory report is carried in a container within the first RRC signaling. Optionally, the first RRC signaling includes a second identifier, such as RRC-ID.

[0798] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0799] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0800] Optionally, the inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2.

[0801] Optionally, after receiving the first signaling, the access network device obtains the inventory report from the first signaling and obtains the second identifier, such as RRC-ID.

[0802] Optionally, the access network device assigns a third identifier to the target device. Optionally, the third identifier is the device NGAP ID.

[0803] Optionally, the access network equipment maintains the correspondence between the second identifier and the third identifier.

[0804] Optionally, the access network equipment maintains the mapping between RRC-ID and device NGAP ID.

[0805] Optionally, the access network device sends the device NGAP ID to the core network device.

[0806] Optionally, the access network equipment sends an inventory report to the core network equipment.

[0807] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and third identifier.

[0808] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and device NGAP ID.

[0809] Optionally, core network devices may store a third identifier, such as the device NGAP ID.

[0810] Optionally, the core network equipment sends a command request to the access network equipment.

[0811] Optionally, the command request may carry a third identifier, such as the device NGAP ID.

[0812] Optionally, the access network device forwards the command request to the terminal device.

[0813] Optionally, the command request forwarded by the access network device carries a second identifier, such as RRC-ID.

[0814] Optionally, the command request is sent by the access network device to the terminal device via the first RRC signaling.

[0815] Optionally, the command request is carried in a container within the first RRC signaling.

[0816] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0817] Optionally, the terminal device receives a command request from the core network device forwarded by the access network device.

[0818] Optionally, the command request received by the terminal device includes a second identifier, such as RRC-ID.

[0819] Optionally, the terminal device sends the A-IoT upper-layer data content in the command request to the target device.

[0820] Optionally, the terminal device receives a command response sent by the target device.

[0821] Optionally, the terminal device sends the A-IOT upper-layer data content in the command response to the access network device.

[0822] Optionally, the command response is carried in a container in the form of a second RRC signaling. Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer and / or ULInformationTransfer.

[0823] Optionally, the command response or second RRC signaling sent by the terminal device carries a second identifier, such as RRC-ID.

[0824] Optionally, the first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4.

[0825] Optionally, the access network device sends a command response to the core network device.

[0826] Optionally, the command response may carry a third identifier, such as the device NGAP ID.

[0827] By establishing the correspondence between the first and second identifiers, as well as between the second and third identifiers, end-to-end bearers can be established to enable A-IoT data communication between the target device and the core network device, thereby improving the A-IoT data communication mechanism.

[0828] Through the technical solution of this embodiment, the target device sends a device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device responds by receiving the second identifier and determines or generates a third identifier, thereby supporting the establishment of end-to-end bearers and improving the A-IoT data communication mechanism.

[0829] Sixth Embodiment

[0830] Referring to Figure 13, which is a schematic diagram of the interaction flow between a terminal device, an access network device, a core network device, and a target device according to the sixth embodiment of the communication method, the sixth embodiment of this application proposes a communication method including steps S0-S3:

[0831] Step S0: The target device sends a device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device, in response to receiving the second identifier, determines or generates a third identifier;

[0832] Step S1: The terminal device sends a second identifier so that the access network device can determine or generate a third identifier;

[0833] Step S2: Upon receiving the second identifier, the access network device determines or generates a third identifier;

[0834] Step S3: The core network device receives the third identifier, which is determined or generated by the access network device in response to receiving the second identifier.

[0835] This embodiment proposes a technical solution whereby the target device sends a device ID, the terminal device determines or generates a second identifier and sends the second identifier, and the access network device, upon receiving the second identifier, determines or generates a third identifier, thereby supporting the establishment of an end-to-end bearer to improve the A-IoT data communication mechanism.

[0836] Optionally, the second identifier is determined or generated by the terminal device.

[0837] Optionally, the second identifier is determined or generated by the terminal device after receiving the device ID.

[0838] Optionally, the device ID is sent by the target device.

[0839] Optionally, the target device is an Internet of Things (IoT) device, such as an A-IoT device.

[0840] Optionally, the device ID is used to uniquely identify an A-IoT device, such as a Device.

[0841] Alternatively, the device ID can be an EPC (Electronic Product Code) or other ID used to identify the target device, such as a temporary ID assigned by the core network.

[0842] Optionally, EPC is the device ID, i.e., the device ID.

[0843] Optionally, the terminal device is configured as a reader.

[0844] Optionally, the terminal device can perform A-IoT operations as a reader.

[0845] Optionally, the network device configures the terminal device as a reader.

[0846] Alternatively, the network device can be an access network device.

[0847] Alternatively, the access network equipment can be a base station, etc.

[0848] Optionally, when configuring a terminal device as a reader, the network device can configure a new SRB for that terminal device.

[0849] Optionally, the new SRB is specifically designed for sending signaling related to A-IOT operations.

[0850] Optionally, if no new SRB is configured, the terminal device uses SRB1, SRB2, or SRB4 to send signaling related to A-IOT operations.

[0851] Optionally, the terminal device can communicate with IoT devices (such as devices) as a reader and transmit data between the target device (IoT device) and the access network device (such as a base station) (e.g., forwarding A-IoT data from the base station to the device, and / or forwarding data from the device to the base station). The access network device can forward A-IoT data from the core network device (such as the CN) to the target device, and / or forward the received A-IoT data from the IoT device to the core network device.

[0852] Optionally, as shown in Figures 7 and 8, the terminal device and the access network device transmit data via RRC signaling; alternatively, the access network device and the core network device transmit data via NGAP signaling.

[0853] Optionally, the RRC signaling can be at least one of the following: R2D command, downlink information transmission signaling, D2R response command, uplink information transmission signaling, inventory request, inventory response, command request, and command response.

[0854] Optionally, the RRC signaling may include at least one of the following: the RRC signaling container, RRC-ID, AS-ID, and inventory report.

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

[0856] Optionally, NGAP signaling may include at least one of the following: AS-ID, reader ID of the terminal device, container of NGAP signaling, Device NGAP ID, command response, and inventory report.

[0857] Optionally, the target device and / or terminal device and / or access network device and / or core network device establish an end-to-end bearer through a first identifier and / or a second identifier and / or a third identifier to realize A-IoT data communication.

[0858] Optionally, the signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier.

[0859] Optionally, the signaling sent by the access network device to the core network device and / or the signaling sent by the core network device to the access network device includes a third identifier.

[0860] Optionally, the terminal device establishes or maintains the correspondence between the first identifier and the second identifier.

[0861] Optionally, the access network equipment establishes or maintains the correspondence between the second identifier and the third identifier.

[0862] Optionally, the first identifier is assigned to the target device by the terminal device.

[0863] Optionally, the second identifier is assigned by the terminal device to the target device.

[0864] Optionally, the third identifier is determined or generated by the access network device for the target device.

[0865] Optionally, the first identifier is used to identify the target device between the terminal device and the target device.

[0866] Optionally, the second identifier is used to identify the target device on the UU interface.

[0867] Optionally, the third identifier is used to identify the target device on the NGAP interface.

[0868] Optionally, the second identifier may be the same as or different from the first identifier.

[0869] Optionally, the second identifier includes the first identifier.

[0870] Optionally, the first identifier includes the AS-ID.

[0871] Optionally, the second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device.

[0872] Optionally, the third identifier includes the device NGAP ID.

[0873] Optionally, the terminal device assigns a first identifier to the target device.

[0874] Optionally, the terminal device assigns a second identifier to the target device.

[0875] Optionally, the second identifier and the first identifier are different. For example, as shown in Figure 7, an access network device (such as a base station) covers an area with at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.). The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to each target device is RRC-ID. RRC-ID is used to identify the target device between the terminal device and the target device on the uu interface. Data is transmitted on the uu interface through RRC signaling, and the terminal device maintains the correspondence between AS-ID and RRC-ID.

[0876] Optionally, the second identifier is the same as the first identifier. For example, as shown in Figure 8, an access network device (such as a base station) has at least one terminal device (such as terminal device 1, terminal device 2, ..., terminal device x, etc.) and at least one target device (such as device 1, device 2, ..., device x, etc.) in its coverage area. The first identifier assigned by the terminal device to the target device is AS-ID, and the second identifier assigned by the terminal device to the target device is also AS-ID. That is, the terminal device does not assign RRC-ID. When transmitting data of the target device through RRC signaling on the uu interface, if the data is related to a target device, it needs to carry AS-ID. The access network device maintains the correspondence between AS-ID and device NGAP ID.

[0877] Optionally, as one scenario, the target device sends a device ID to the terminal device.

[0878] Optionally, after receiving the device ID, the terminal device determines or generates an RRC-ID and assigns it to the target device. The RRC-ID is used to identify the target device on the uu interface.

[0879] Optionally, the terminal device establishes and / or maintains the correspondence between AS-ID and RRC-ID.

[0880] Optionally, the terminal device sends an RRC-ID to the access network device.

[0881] Optionally, after receiving the RRC-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0882] Optionally, the access network equipment establishes and / or maintains the mapping between RRC-ID and device NGAP ID.

[0883] Optionally, the access network device sends the device NGAP ID to the core network device.

[0884] By establishing the correspondence between AS-ID and RRC-ID, as well as the correspondence between RRC-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is supported, thereby improving the A-IoT data communication mechanism.

[0885] Optionally, RRC-ID can be replaced with AS-ID, or AS-ID and the reader ID of the terminal device.

[0886] Optionally, taking the replacement of RRC-ID with AS-ID as an example, as another scenario, the target device sends the device ID to the terminal device.

[0887] Optionally, after receiving the device ID, the terminal device assigns an AS-ID to the target device to identify the target device on the uu interface.

[0888] Optionally, the terminal device sends the AS-ID to the access network device.

[0889] Optionally, after receiving the AS-ID, the access network device determines or generates a device NGAP ID and assigns it to the target device. The device NGAP ID is used to identify the target device on the NGAP interface.

[0890] Optionally, the access network device establishes and / or maintains the mapping between AS-ID and device NGAP ID.

[0891] Optionally, the access network device sends the device NGAP ID to the core network device.

[0892] By leveraging the AS-ID and the mapping between AS-ID and device NGAP ID, A-IoT data communication between the target device and the core network device is enabled, thereby improving the A-IoT data communication mechanism.

[0893] Optionally, the target device sends its device ID to the terminal device via radio resource information.

[0894] Optionally, radio resource information is obtained based on A-IoT services triggered by core network equipment.

[0895] Optionally, after the core network equipment triggers a service, the core network equipment sends an inventory request to the access network equipment (such as a base station).

[0896] Optionally, the inventory request carries configuration information related to triggering paging, such as device identification information paging ID, AIOT-F node identification, business identification Correlation ID, key parameter N1, etc.

[0897] Optionally, the inventory request is sent by the access network device to the terminal device via the first RRC signaling.

[0898] Optionally, the inventory request is carried in a container within the first RRC signaling.

[0899] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0900] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0901] Optionally, upon receiving an inventory request, the terminal device sends an inventory response to the access network device.

[0902] Optionally, the inventory response is sent by the terminal device to the access network device via a second RRC signaling.

[0903] Optionally, the inventory response is carried in a container within a second RRC signaling.

[0904] Optionally, the second RRC signaling is a D2R response command and / or uplink information transmission signaling.

[0905] Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer, and / or ULInformationTransfer.

[0906] Optionally, the access network device sends an inventory response to the core network device.

[0907] Optionally, the terminal device sends an A-IoT paging command to the target device.

[0908] Optionally, the A-IoT paging command includes at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters.

[0909] Optionally, the target device receives an A-IoT paging command sent by the terminal device.

[0910] Optionally, if the target device determines that it needs to respond to the A-IoT paging command, it performs at least one of the following operations:

[0911] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0912] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

[0913] Optionally, the random response message includes a first identifier assigned by the terminal device to the target device.

[0914] Optionally, the random response message includes an AS-ID assigned by the terminal device to the target device. Optionally, the AS-ID uniquely identifies a target device between the terminal device and the target device.

[0915] Optionally, the target device sends MSG3 (message 3) on the acquired radio resources. Optionally, MSG3 carries the device ID.

[0916] Optionally, after receiving the device ID, the terminal device maintains the mapping relationship between the device ID and the first identifier, that is, maintains the correspondence between the device ID and the first identifier.

[0917] Optionally, after receiving the device ID, the terminal device assigns a second identifier to the target device, for example, assigning an RRC-ID to the target device. Optionally, the RRC-ID is used to uniquely identify a target device on the uu interface.

[0918] Optionally, the terminal device maintains a mapping relationship between the first identifier and the second identifier, that is, the terminal device maintains a correspondence relationship between the first identifier and the second identifier. For example, the terminal device maintains a correspondence relationship between AS-ID and RRC-ID.

[0919] Optionally, the terminal device sends an inventory report to the access network device.

[0920] Optionally, the inventory report is sent via a second RRC signaling.

[0921] Optionally, the inventory report is carried in a container within the first RRC signaling. Optionally, the first RRC signaling includes a second identifier, such as RRC-ID.

[0922] Optionally, the first RRC signaling is an R2D command and / or downlink information transmission signaling.

[0923] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0924] Optionally, the inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2.

[0925] Optionally, after receiving the first signaling, the access network device obtains the inventory report from the first signaling and obtains the second identifier, such as RRC-ID.

[0926] Optionally, the access network device assigns a third identifier to the target device. Optionally, the third identifier is the device NGAP ID.

[0927] Optionally, the access network equipment maintains the correspondence between the second identifier and the third identifier.

[0928] Optionally, the access network equipment maintains the mapping between RRC-ID and device NGAP ID.

[0929] Optionally, the access network device sends the device NGAP ID to the core network device.

[0930] Optionally, the access network equipment sends an inventory report to the core network equipment.

[0931] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and third identifier.

[0932] Optionally, the inventory report sent by the access network device to the core network device includes at least one of the following: device ID, security parameter X, N2, and device NGAP ID.

[0933] Optionally, core network devices may store a third identifier, such as the device NGAP ID.

[0934] Optionally, the core network equipment sends a command request to the access network equipment.

[0935] Optionally, the command request may carry a third identifier, such as the device NGAP ID.

[0936] Optionally, the access network device forwards the command request to the terminal device.

[0937] Optionally, the command request forwarded by the access network device carries a second identifier, such as RRC-ID.

[0938] Optionally, the command request is sent by the access network device to the terminal device via the first RRC signaling.

[0939] Optionally, the command request is carried in a container within the first RRC signaling.

[0940] Optionally, the first RRC signaling can be a new RRC signaling, such as R2DInformationTransfer, and / or DLInformationTransfer.

[0941] Optionally, the terminal device receives a command request from the core network device forwarded by the access network device.

[0942] Optionally, the command request received by the terminal device includes a second identifier, such as RRC-ID.

[0943] Optionally, the terminal device sends the A-IoT upper-layer data content in the command request to the target device.

[0944] Optionally, the terminal device receives a command response sent by the target device.

[0945] Optionally, the terminal device sends the A-IOT upper-layer data content in the command response to the access network device.

[0946] Optionally, the command response is carried in a container in the form of a second RRC signaling. Optionally, the second RRC signaling can be a new RRC signaling, such as D2RInformationTransfer and / or ULInformationTransfer.

[0947] Optionally, the command response or second RRC signaling sent by the terminal device carries a second identifier, such as RRC-ID.

[0948] Optionally, the first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4.

[0949] Optionally, the access network device sends a command response to the core network device.

[0950] Optionally, the command response may carry a third identifier, such as the device NGAP ID.

[0951] By establishing the correspondence between the first and second identifiers, as well as between the second and third identifiers, end-to-end bearers can be established to enable A-IoT data communication between the target device and the core network device, thereby improving the A-IoT data communication mechanism.

[0952] Through the technical solution of this embodiment, the target device sends a device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device responds by receiving the second identifier and determines or generates a third identifier, thereby supporting the establishment of end-to-end bearers and improving the A-IoT data communication mechanism.

[0953] Seventh Embodiment

[0954] 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 terminal device in the above method embodiments. The communication device shown in Figure 14 can be used to perform some or all of the functions in the method embodiments described above. As shown in Figure 14, the communication device 140 includes:

[0955] The first transmitting module 1401 is used to transmit the second identifier so that the access network device can determine or generate the third identifier.

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

[0957] The second identifier is determined or generated by the terminal device;

[0958] The second identifier is determined or generated by the terminal device after receiving the device ID;

[0959] The terminal device is configured as a reader;

[0960] Assign a first identifier to the target device;

[0961] Upon receiving an inventory request, an inventory response is sent to the access network equipment;

[0962] Send an A-IoT paging command to the target device;

[0963] Assign a second identifier to the target device;

[0964] Send inventory reports to access network equipment;

[0965] The access network equipment sends inventory reports to the core network equipment.

[0966] Receive command requests from core network devices forwarded by access network devices;

[0967] Send the A-IoT upper-layer data content in the command request to the target device;

[0968] Receive command responses sent by the target device;

[0969] Send the A-IOT upper-layer data content in the command response to the access network device.

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

[0971] The device ID is sent by the target device;

[0972] Maintain the correspondence between the first identifier and the second identifier;

[0973] Access network equipment maintains the correspondence between the second and third identifiers;

[0974] The first identifier is used to identify the target device between the terminal device and the target device;

[0975] The second identifier is used to identify the target device on the UU interface;

[0976] The third identifier is used to identify the target device on the NGAP interface;

[0977] The second identifier may be the same as or different from the first identifier;

[0978] The second identifier includes the first identifier;

[0979] The first identifier includes AS-ID;

[0980] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[0981] The third identifier includes the device NGAP ID;

[0982] Data is transmitted between the device and the access network via RRC signaling;

[0983] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[0984] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[0986] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[0987] Inventory requests and / or command requests are sent by the access network equipment via the first RRC signaling;

[0988] Inventory responses and / or inventory reports are sent via a second RRC signaling;

[0989] The inventory report sent to the access network equipment includes at least one of the following: device ID, security parameter X, and N2;

[0990] The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[0991] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[0992] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[0994] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[0995] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[0996] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[0997] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[0998] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[0999] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[1001] Eighth embodiment

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

[1003] Processing module 1501 is used to determine or generate a third identifier in response to receiving a second identifier.

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

[1005] The second identifier is determined or generated by the terminal device;

[1006] The second identifier is determined or generated by the terminal device after receiving the device ID;

[1007] The terminal device is configured as a reader;

[1008] The terminal device assigns a first identifier to the target device;

[1009] Send an inventory request to the terminal device;

[1010] Receive inventory response sent by terminal device;

[1011] The terminal device sends an A-IoT paging command to the target device;

[1012] The terminal device assigns a second identifier to the target device;

[1013] Receive inventory reports sent by terminal devices;

[1014] Send inventory reports to core network equipment;

[1015] Send command requests from core network devices to terminal devices;

[1016] The terminal device sends the A-IoT upper-layer data content in the command request to the target device;

[1017] Receive the A-IoT upper-layer data content from the command response forwarded by the terminal device from the target device;

[1018] Send the A-IOT upper-layer data content from the command response of the target device to the core network device.

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

[1020] The device ID is sent from the target device to the terminal device;

[1021] The terminal device maintains the correspondence between the first identifier and the second identifier;

[1022] Maintain the correspondence between the second and third identifiers;

[1023] The first identifier is used to identify the target device between the terminal device and the target device;

[1024] The second identifier is used to identify the target device on the UU interface;

[1025] The third identifier is used to identify the target device on the NGAP interface;

[1026] The second identifier may be the same as or different from the first identifier;

[1027] The second identifier includes the first identifier;

[1028] The first identifier includes AS-ID;

[1029] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[1030] The third identifier includes the device NGAP ID;

[1031] Data is transmitted between the terminal device and the terminal device via RRC signaling;

[1032] The signaling sent to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier;

[1033] Signaling sent to core network devices and / or signaling sent by core network devices to access network devices contains a third identifier.

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

[1035] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[1036] Inventory requests and / or command requests are sent via the first RRC signaling;

[1037] Inventory responses and / or inventory reports are sent by the terminal device via a second RRC signaling;

[1038] The inventory report received from the terminal device includes at least one of the following: device ID, security parameter X, and N2;

[1039] The inventory report sent to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[1040] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[1041] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[1043] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[1044] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[1045] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[1046] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[1047] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[1048] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[1050] Ninth Embodiment

[1051] Please refer to Figure 16, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This device can be mounted on or is the core network device in the above method embodiments. The communication device shown in Figure 16 can be used to perform some or all of the functions in the method embodiments described above. As shown in Figure 16, the communication device 160 includes:

[1052] The receiving module 1601 is used to receive a third identifier, which is determined or generated by the access network device in response to receiving the second identifier.

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

[1054] The second identifier is determined or generated by the terminal device;

[1055] The second identifier is determined or generated by the terminal device after receiving the device ID;

[1056] The terminal device is configured as a reader;

[1057] The terminal device assigns a first identifier to the target device;

[1058] Send inventory requests to terminal devices via access network equipment;

[1059] The receiving terminal device receives the inventory response forwarded by the access network equipment;

[1060] The terminal device sends an A-IoT paging command to the target device;

[1061] The terminal device assigns a second identifier to the target device;

[1062] Receive inventory reports from terminal devices forwarded by access network devices;

[1063] Send command requests to terminal devices through access network devices;

[1064] The terminal device sends the A-IoT upper-layer data content in the command request to the target device;

[1065] The terminal device receives the command response sent by the target device;

[1066] Receive A-IOT upper-layer data content from the command response forwarded by the access network device from the terminal device.

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

[1068] The device ID is sent by the target device;

[1069] The terminal device maintains the correspondence between the first identifier and the second identifier;

[1070] Access network equipment maintains the correspondence between the second and third identifiers;

[1071] The first identifier is used to identify the target device between the terminal device and the target device;

[1072] The second identifier is used to identify the target device on the UU interface;

[1073] The third identifier is used to identify the target device on the NGAP interface;

[1074] The second identifier may be the same as or different from the first identifier;

[1075] The second identifier includes the first identifier;

[1076] The first identifier includes AS-ID;

[1077] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[1078] The third identifier includes the device NGAP ID;

[1079] Terminal equipment and access network equipment transmit data via RRC signaling;

[1080] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[1081] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[1083] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[1084] Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling;

[1085] The inventory response and / or inventory report are sent by the terminal device to the access network device via a second RRC signaling; the inventory report sent by the terminal device to the access network device includes at least one of the device ID, security parameter X, and N2.

[1086] Inventory reports received from access network devices include at least one of the following: device ID, security parameter X, N2, and third identifier;

[1087] If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information.

[1088] If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

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

[1090] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[1091] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[1092] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[1093] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[1094] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[1095] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[1097] Tenth Embodiment

[1098] Please refer to Figure 17, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This device can be mounted on or is the target device (such as a device) in the above method embodiments. The communication device shown in Figure 17 can be used to perform some or all of the functions described in the method embodiments above. As shown in Figure 17, the device 170 includes:

[1099] The second sending module 1701 is used to send the device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device can determine or generate a third identifier in response to receiving the second identifier.

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

[1101] The terminal device is configured as a reader;

[1102] The terminal device assigns a first identifier to the target device;

[1103] Upon receiving an inventory request, the terminal device sends an inventory response to the access network device;

[1104] Receive A-IoT paging commands sent by the target device;

[1105] Send the device ID to the terminal device based on the A-IoT paging command;

[1106] The terminal device assigns a second identifier to the target device;

[1107] Terminal devices send inventory reports to core network devices through access network devices;

[1108] Receive command requests from core network devices forwarded by terminal devices;

[1109] The A-IOT upper-layer data content is sent from the terminal equipment and access network equipment to the core network equipment in the command response.

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

[1111] The terminal device maintains the correspondence between the first identifier and the second identifier;

[1112] Access network equipment maintains the correspondence between the second and third identifiers;

[1113] The first identifier is used to identify the target device between the terminal device and the target device;

[1114] The second identifier is used to identify the target device on the UU interface;

[1115] The third identifier is used to identify the target device on the NGAP interface;

[1116] The second identifier may be the same as or different from the first identifier;

[1117] The second identifier includes the first identifier;

[1118] The first identifier includes AS-ID;

[1119] The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device;

[1120] The third identifier includes the device NGAP ID;

[1121] Terminal equipment and access network equipment transmit data via RRC signaling;

[1122] The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier;

[1123] The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

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

[1125] A-IoT paging commands include at least one of the following: device identification information paging ID, key parameter N1, and random access resource configuration parameters;

[1126] Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling;

[1127] The inventory response and / or inventory report are sent by the terminal device to the access network device via a second RRC signaling; the inventory report sent by the terminal device to the access network device includes at least one of the device ID, security parameter X, and N2.

[1128] The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier;

[1129] If the AIoT paging command triggers CBRA, a random access procedure is initiated, and a random response message is received to obtain radio resource information from the random response message.

[1130] If the AIoT paging command triggers CFRA, then the radio resource information is obtained from the AIoT paging command.

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

[1132] The first RRC signaling is an R2D command and / or downlink information transmission signaling;

[1133] Inventory requests and / or command requests are carried in a container within the first RRC signaling;

[1134] The second RRC signaling is a D2R command and / or uplink information transmission signaling;

[1135] Inventory responses and / or command responses are carried in a container within a second RRC signaling;

[1136] The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4;

[1137] The random response message includes a first identifier assigned by the terminal device to the target device.

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

[1139] Referring to Figure 18, 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 an access network device or a core network device or a target device (or a component that can be used in an access network device or a core network device or a target 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, an access network device, a core network device or a target device, as detailed in the descriptions in the above method embodiments.

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

[1141] 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, access network device, core network device, or target device.

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

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

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

[1145] 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, access network device, core network device, or target device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transceiver functions of the communication device 180.

[1146] Optionally, if the communication device 180 is used to implement the operation corresponding to the access network device in the above embodiments, for example, the transceiver 1805 may receive the second identifier; and the processor 1801 may determine or generate a third identifier in response to receiving the second identifier.

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

[1148] 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 can send the second identifier.

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

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

[1151] In this application, the communication device can be a terminal device (such as a mobile phone), an access network device (such as a base station), a core network device (such as a CN), or a target device (such as an A-IoT device), 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.

[1152] Although the communication device is described in the above embodiments as a terminal device, access network device, core network device, or target device, the scope of the communication device described in this application is not limited to the aforementioned terminal device, access network device, core network device, or target device, and the structure of the communication device is not limited to FIG18. The communication device can be a standalone device or can be part of a larger device.

[1153] This application also provides a communication system, including: a terminal device as described in any of the above embodiments; and an access network device, core network device, or target device as described in any of the above embodiments.

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

[1155] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), an access network device (such as a base station), a core network device (such as a CN), a target device (such as an A-IoT device), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

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

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

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

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

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

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

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

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

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

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

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

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

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

[1169] 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: S1: Send the second identifier so that the access network device can determine or generate the third identifier.

2. The method according to claim 1, wherein, It also includes at least one of the following: The second identifier is determined or generated by the terminal device; The second identifier is determined or generated by the terminal device after receiving the device ID; The terminal device is configured as a reader; Assign a first identifier to the target device; Upon receiving an inventory request, an inventory response is sent to the access network equipment; Send an A-IoT paging command to the target device; Assign a second identifier to the target device; Send inventory reports to access network equipment; The access network equipment sends inventory reports to the core network equipment. Receive command requests from core network devices forwarded by access network devices; Send the A-IoT upper-layer data content in the command request to the target device; Receive command responses sent by the target device; Send the A-IOT upper-layer data content in the command response to the access network device.

3. The method according to claim 2, wherein, It also includes at least one of the following: The device ID is sent by the target device; Maintain the correspondence between the first identifier and the second identifier; Access network equipment maintains the correspondence between the second and third identifiers; The first identifier is used to identify the target device between the terminal device and the target device; The second identifier is used to identify the target device on the UU interface; The third identifier is used to identify the target device on the NGAP interface; The second identifier may be the same as or different from the first identifier; The second identifier includes the first identifier; The first identifier includes AS-ID; The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device; The third identifier includes the device NGAP ID; Data is transmitted between the device and the access network via RRC signaling; The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier; The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

4. The method according to claim 3, wherein, It also includes at least one of the following: A-IoT paging commands include at least one of the following: device identification information pagingID, key parameter N1, and random access resource configuration parameters; Inventory requests and / or command requests are sent by the access network equipment via the first RRC signaling; Inventory responses and / or inventory reports are sent via a second RRC signaling; The inventory report sent to the access network equipment includes at least one of the following: device ID, security parameter X, and N2; The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier; If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information. If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

5. The method according to claim 4, wherein, It also includes at least one of the following: The first RRC signaling is an R2D command and / or downlink information transmission signaling; Inventory requests and / or command requests are carried in a container within the first RRC signaling; The second RRC signaling is a D2R command and / or uplink information transmission signaling; Inventory responses and / or command responses are carried in a container within a second RRC signaling; The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4; The random response message includes a first identifier assigned by the terminal device to the target device.

6. A communication method, wherein, Applied to access network equipment, including the following steps: S2: In response to receiving the second identifier, determine or generate the third identifier.

7. The method according to claim 6, wherein, It also includes at least one of the following: The second identifier is determined or generated by the terminal device; The second identifier is determined or generated by the terminal device after receiving the device ID; The terminal device is configured as a reader; The terminal device assigns a first identifier to the target device; Send an inventory request to the terminal device; Receive inventory response sent by terminal device; The terminal device sends an A-IoT paging command to the target device; The terminal device assigns a second identifier to the target device; Receive inventory reports sent by terminal devices; Send inventory reports to core network equipment; Send command requests from core network devices to terminal devices; The terminal device sends the A-IoT upper-layer data content in the command request to the target device; Receive the A-IoT upper-layer data content from the command response forwarded by the terminal device from the target device; Send the A-IOT upper-layer data content from the command response of the target device to the core network device.

8. The method according to claim 7, wherein, It also includes at least one of the following: The device ID is sent from the target device to the terminal device; The terminal device maintains the correspondence between the first identifier and the second identifier; Maintain the correspondence between the second and third identifiers; The first identifier is used to identify the target device between the terminal device and the target device; The second identifier is used to identify the target device on the UU interface; The third identifier is used to identify the target device on the NGAP interface; The second identifier may be the same as or different from the first identifier; The second identifier includes the first identifier; The first identifier includes AS-ID; The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device; The third identifier includes the device NGAP ID; Data is transmitted between the terminal device and the terminal device via RRC signaling; The signaling sent to the terminal device and / or the signaling sent by the terminal device to the access network device includes a second identifier; Signaling sent to core network devices and / or signaling sent by core network devices to access network devices contains a third identifier.

9. The method according to claim 8, wherein, It also includes at least one of the following: A-IoT paging commands include at least one of the following: device identification information pagingID, key parameter N1, and random access resource configuration parameters; Inventory requests and / or command requests are sent via the first RRC signaling; Inventory responses and / or inventory reports are sent by the terminal device via a second RRC signaling; The inventory report received from the terminal device includes at least one of the following: device ID, security parameter X, and N2; The inventory report sent to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier; If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information. If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

10. The method according to claim 9, wherein, It also includes at least one of the following: The first RRC signaling is an R2D command and / or downlink information transmission signaling; Inventory requests and / or command requests are carried in a container within the first RRC signaling; The second RRC signaling is a D2R command and / or uplink information transmission signaling; Inventory responses and / or command responses are carried in a container within a second RRC signaling; The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4; The random response message includes a first identifier assigned by the terminal device to the target device.

11. A communication method, wherein, Applied to core network equipment, including the following steps: S3: Receive the third identifier, which is determined or generated by the access network device in response to receiving the second identifier.

12. The method according to claim 11, wherein, It also includes at least one of the following: The second identifier is determined or generated by the terminal device; The second identifier is determined or generated by the terminal device after receiving the device ID; The terminal device is configured as a reader; The terminal device assigns a first identifier to the target device; Send inventory requests to terminal devices via access network equipment; The receiving terminal device receives the inventory response forwarded by the access network equipment; The terminal device sends an A-IoT paging command to the target device; The terminal device assigns a second identifier to the target device; Receive inventory reports from terminal devices forwarded by access network devices; Send command requests to terminal devices through access network devices; The terminal device sends the A-IoT upper-layer data content in the command request to the target device; The terminal device receives the command response sent by the target device; Receive A-IOT upper-layer data content from the command response forwarded by the access network device from the terminal device.

13. The method according to claim 12, wherein, It also includes at least one of the following: The device ID is sent by the target device; The terminal device maintains the correspondence between the first identifier and the second identifier; Access network equipment maintains the correspondence between the second and third identifiers; The first identifier is used to identify the target device between the terminal device and the target device; The second identifier is used to identify the target device on the UU interface; The third identifier is used to identify the target device on the NGAP interface; The second identifier may be the same as or different from the first identifier; The second identifier includes the first identifier; The first identifier includes AS-ID; The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device; The third identifier includes the device NGAP ID; Terminal equipment and access network equipment transmit data via RRC signaling; The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier; The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

14. The method according to claim 13, wherein, It also includes at least one of the following: A-IoT paging commands include at least one of the following: device identification information pagingID, key parameter N1, and random access resource configuration parameters; Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling; Inventory response and / or inventory report are sent by the terminal equipment to the access network equipment via a second RRC signaling; The inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2; Inventory reports received from access network devices include at least one of the following: device ID, security parameter X, N2, and third identifier; If the AIoT paging command triggers CBRA, the target device initiates a random access procedure and receives a random response message, from which it obtains radio resource information. If the AIoT paging command triggers CFRA, the target device obtains radio resource information from the AIoT paging command.

15. The method according to claim 14, wherein, It also includes at least one of the following: The first RRC signaling is an R2D command and / or downlink information transmission signaling; Inventory requests and / or command requests are carried in a container within the first RRC signaling; The second RRC signaling is a D2R command and / or uplink information transmission signaling; Inventory responses and / or command responses are carried in a container within a second RRC signaling; The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4; The random response message includes a first identifier assigned by the terminal device to the target device.

16. A communication method, wherein, Applied to the target device, including the following steps: S0: Send the device ID so that the terminal device can determine or generate a second identifier and send the second identifier, and the access network device can determine or generate a third identifier in response to receiving the second identifier.

17. The method according to claim 16, wherein, It also includes at least one of the following: The terminal device is configured as a reader; The terminal device assigns a first identifier to the target device; Upon receiving an inventory request, the terminal device sends an inventory response to the access network device; Receive A-IoT paging commands sent by the target device; Send the device ID to the terminal device based on the A-IoT paging command; The terminal device assigns a second identifier to the target device; Terminal devices send inventory reports to core network devices through access network devices; Receive command requests from core network devices forwarded by terminal devices; The A-IOT upper-layer data content is sent from the terminal equipment and access network equipment to the core network equipment in the command response.

18. The method according to claim 17, wherein, It also includes at least one of the following: The terminal device maintains the correspondence between the first identifier and the second identifier; Access network equipment maintains the correspondence between the second and third identifiers; The first identifier is used to identify the target device between the terminal device and the target device; The second identifier is used to identify the target device on the UU interface; The third identifier is used to identify the target device on the NGAP interface; The second identifier may be the same as or different from the first identifier; The second identifier includes the first identifier; The first identifier includes AS-ID; The second identifier includes at least one of RRC-ID, AS-ID, AS-ID, and the reader ID of the terminal device; The third identifier includes the device NGAP ID; Terminal equipment and access network equipment transmit data via RRC signaling; The signaling sent by the access network device to the terminal device and / or the signaling sent by the terminal device to the access network device contains a second identifier; The signaling sent from the access network device to the core network device and / or the signaling sent from the core network device to the access network device contains a third identifier.

19. The method according to claim 18, wherein, It also includes at least one of the following: A-IoT paging commands include at least one of the following: device identification information pagingID, key parameter N1, and random access resource configuration parameters; Inventory requests and / or command requests are sent by the access network equipment to the terminal equipment via the first RRC signaling; Inventory response and / or inventory report are sent by the terminal equipment to the access network equipment via a second RRC signaling; The inventory report sent by the terminal device to the access network device includes at least one of the following: device ID, security parameter X, and N2; The inventory report sent by the access network equipment to the core network equipment includes at least one of the following: device ID, security parameter X, N2, and third identifier; If the AIoT paging command triggers CBRA, a random access procedure is initiated, and a random response message is received, from which radio resource information is obtained; if the AIoT paging command triggers CFRA, radio resource information is obtained from the AIoT paging command.

20. The method according to claim 19, wherein, It also includes at least one of the following: The first RRC signaling is an R2D command and / or downlink information transmission signaling; Inventory requests and / or command requests are carried in a container within the first RRC signaling; The second RRC signaling is a D2R command and / or uplink information transmission signaling; Inventory responses and / or command responses are carried in a container within a second RRC signaling; The first RRC signaling and / or the second RRC signaling are carried by at least one of the new SRB, SRB1, SRB2 and SRB4; The random response message includes a first identifier assigned by the terminal device to the target device.

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

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

Images