Information indication method and apparatus, communication device, communication system and storage medium

Abstract

The embodiments of the present disclosure provide an information indication method and apparatus, a communication device, a communication system and a storage medium. The method is executed by a terminal. The method comprises: receiving first information sent by an access network device; and sending a first message, wherein the first message is used by a terminal to request any message which enters a connected state or any message which has entered the connected state; the first message comprises the first information, which indicates that the terminal has second information to be sent; and the second information is transmitted to the terminal by a first device on the basis of the triggering of a first signal of the terminal.

Description

Information indication method and device, communication equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to an information indication method and apparatus, a communication device, a communication system, and a storage medium. Background Art

[0002] Internet of Things (IoT) devices are generally low-power devices, so they can maintain long-term operation based on their own batteries. However, battery life is limited. Once the battery life is exhausted, the IoT device will stop working, affecting users.

[0003] Summary of the Invention

[0004] With the development of technology, a backscatter communication mechanism has been proposed to reduce the problem of short battery life of terminals as incentive devices for IoT devices.

[0005] Embodiments of the present disclosure provide an information indication method and apparatus, a communication device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided, wherein the method includes:

[0007] The terminal sends a first message, wherein the first message is used for the terminal to request to enter any message of the connected state or any message after entering the connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0008] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, comprising:

[0009] An access network device receives a first message from a terminal, wherein the first message is any message for the terminal to request entering a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates second information to be sent by the terminal; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0010] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0011] The sending module is configured to send a first message, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0012] According to a fourth aspect of an embodiment of the present disclosure, an access network device is provided, including:

[0013] The receiving module is configured to receive a first message from the terminal, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a communication method is provided, wherein the method includes:

[0015] The terminal executes the communication method described in any technical solution of the first aspect;

[0016] The access network device executes the communication method described in any technical solution of the second aspect.

[0017] According to the sixth aspect of an embodiment of the present disclosure, a communication system is provided, wherein the information indication system includes a terminal, an access network device and a first network element; the target terminal is configured to implement the communication method described in any technical solution of the first aspect, and the access network device is configured to implement the communication method described in any one of the technical solutions of the second aspect.

[0018] According to a seventh aspect of an embodiment of the present disclosure, a communication device is provided, wherein the communication device includes:

[0019] one or more processors;

[0020] The processor is used to call instructions to enable the communication device to execute the communication method described in any technical solution of the first aspect or any technical solution of the second aspect.

[0021] According to a tenth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the communication method described in any technical solution of the first aspect or any technical solution of the second aspect.

[0022] The technical solution provided by the embodiments of the present disclosure facilitates a terminal to collect second information returned by a first device based on stimulation of the first signal by sending a first signal in a non-connected state, and to carry the second information in a first message when entering a connected state or after entering a connected state. In this way, after receiving the second information, the access network device will establish an RRC connection with the terminal, thereby enabling the terminal to successfully report the second information in the non-connected state to the network device. Furthermore, the terminal can receive the second information in the non-connected state, thereby saving power consumption and extending the terminal's standby time.

[0023] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0025] FIG1A is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0026] FIG1B is a schematic diagram showing wireless communication based on a backscatter transmission mechanism according to an exemplary embodiment;

[0027] FIG1C is a schematic topology diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0028] FIG1D is a schematic diagram showing wireless communication based on a backscatter transmission mechanism according to an exemplary embodiment;

[0029] FIG1E is a schematic topology diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0030] FIG1F is a topological diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0031] FIG1G is a schematic diagram of a device that performs wireless communication using three backscatter transmission mechanisms according to an exemplary embodiment;

[0032] FIG2 is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0033] FIG3 is a flow chart showing a communication method according to an exemplary embodiment;

[0034] FIG4 is a flow chart showing a communication method according to an exemplary embodiment;

[0035] FIG5A is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0036] FIG5B is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0037] FIG6A is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0038] FIG6B is a schematic structural diagram of an access network device according to an exemplary embodiment;

[0039] FIG7A is a schematic structural diagram of a UE according to an exemplary embodiment;

[0040] Fig. 7B is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0041] Embodiments of the present disclosure provide a communication method and apparatus, communication equipment, a communication system, and a storage medium.

[0042] In a first aspect, an embodiment of the present disclosure provides a communication method, which includes:

[0043] The terminal sends a first message, wherein the first message is used for the terminal to request to enter any message of the connected state or any message after entering the connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0044] In the above embodiment, the terminal receives any message when entering the connected state or after entering the connected state, and the terminal caches the second information received from the first device in the non-connected state. In this way, the second information cached by the terminal in the non-connected state will be sent to the network side after entering the connected state or entering the connected state, without the terminal having to remain in the connected state to trigger or stimulate the first device to return the second information through the first signal, so that the terminal, as an anchor point or reader of the first device, can also be in relatively low power consumption.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes at least one of the following:

[0046] Radio Resource Control (RRC) setup request message for idle state;

[0047] RRC recovery request message for inactive state;

[0048] RRC connection establishment completion message for idle state;

[0049] RRC connection recovery complete message for inactive state.

[0050] In the above embodiment, a terminal in an idle state or an inactive state uses an RRC message entering a connected state to inform a network-side device that there is second information to be sent to the network device, thereby reusing the original RRC message signaling. In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following:

[0051] A first reason, indicating that the terminal requests the second information to be sent;

[0052] The second reason indicates that the terminal requests to establish only an RRC signaling connection;

[0053] A third reason indicates that the terminal moves and initiates data;

[0054] a first identifier, indicating that the terminal serves as an identifier of the first device reader;

[0055] A task identifier, indicating a collection task for obtaining the second information of the first device;

[0056] The second identifier indicates the first device.

[0057] In the above embodiment, the first information may be indication information that explicitly indicates that the second information is to be sent, or may be information indicating other contents such as a task identifier and a device identifier, while implicitly indicating that the terminal has the second information to be sent.

[0058] In combination with some embodiments of the first aspect, in some embodiments, sending the first message includes: detecting a preset event, and sending the first message.

[0059] In the above embodiment, the terminal in the unconnected state sends the first message only after detecting a preset event, rather than sending the second information cached in the first device, thereby reducing unnecessary sending of the first message.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, an RRC signaling-only connection is established with the access device;

[0061] Wherein, when the RRC signaling connection is established, a signaling radio bearer SRB1 is established for the terminal.

[0062] In the above embodiment, since the purpose of establishing this connection is to send the second message, in order to reduce unnecessary resource waste, an RRC signaling-only connection is established in the embodiment of the present disclosure. This RRC signaling-only connection is simpler to establish than a normal RRC connection. For example, for an RRC signaling-only connection, the access network device can only configure SRB1 for the terminal without configuring SRB2 and DRB, which reduces the operation of resource configuration and reduces the waste of unnecessary resources.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments,

[0064] The terminal is established with SRB1, SRB2 and / or data radio bearer DRB.

[0065] In the above embodiment, if a conventional RRC connection is established for the terminal, the necessary SRB1 can be configured for the terminal, and at least one of SRB2 and / or DRB can also be configured for the terminal. In this way, SRB1, SRB2 and / or DRB can be used to send the second information as needed, making the sending of the second information more flexible.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the second information sent based on the RRC connection carries a task identifier added by the first device;

[0067] or,

[0068] The second information sent based on the RRC connection carries the task identifier added by the terminal.

[0069] In some cases, the first device will obtain the task identifier, and the first device can automatically add the task identifier to the second information; in some embodiments, if the first device does not add the task identifier to the second information, the terminal can add the task identifier to the second information, so that the second information has the task identifier. In this way, when the network side receives the second information with the task identifier added, it can know the task to which the current second information is directed.

[0070] By sending the first information through dedicated signaling, existing signaling can be reused to reduce signaling overhead.

[0071] In a second aspect, an embodiment of the present disclosure provides a communication method, including:

[0072] The access network device receives a first message from the terminal, wherein the first message is any message for the terminal to request entering a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates second information to be sent by the terminal; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal from the terminal. In the above embodiment, the network device can establish a connection with the terminal based on the first message from the terminal, and after the connection is established, the second information of the first device cached by the terminal in the non-connected state is transmitted.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes at least one of the following:

[0074] Radio Resource Control (RRC) setup request message for idle state;

[0075] RRC recovery request message for inactive state;

[0076] RRC connection establishment completion message for idle state;

[0077] RRC connection recovery complete message for inactive state.

[0078] In the above embodiment, the terminal in the idle state or inactive state uses the RRC message for entering the connected state to inform the network side device that there is second information to be sent to the network device, thereby reusing the original RRC message signaling.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following:

[0080] A first reason, indicating that the terminal requests the second information to be sent;

[0081] The second reason indicates that the terminal requests to establish only an RRC signaling connection;

[0082] A third reason indicates that the terminal moves and initiates data;

[0083] A fourth reason is to instruct the terminal to report drive test data;

[0084] a first identifier, indicating that the terminal serves as an identifier of the first device reader;

[0085] A task identifier, indicating a collection task for obtaining the second information of the first device;

[0086] The second identifier indicates the first device.

[0087] The first information may be indication information that explicitly indicates that the second information is to be sent, or may be information indicating other contents such as a task identifier and a device identifier, while implicitly indicating that the terminal has the second information to be sent.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0089] Establish an RRC connection with the terminal based on the first message.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0091] Receive the first information sent based on the RRC connection.

[0092] In combination with some embodiments of the second aspect, in some embodiments, the RRC connection includes: only RRC signaling connection.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0094] The RRC signaling-only connection is established with the terminal, and a signaling radio bearer SRB1 is configured for the terminal.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0096] Establish an SRB1, SRB2 and / or data radio bearer for the terminal.

[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0098] Send the second information to the core network device; wherein, the second information is sent by the core network device to the second device.

[0099] or,

[0100] The second information is sent to the second device.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the second information includes a task identifier added by the first device;

[0102] or,

[0103] The second information includes a task identifier added by the terminal;

[0104] or,

[0105] The second information includes a task identifier added by the access network device.

[0106] In a third aspect, an embodiment of the present disclosure provides a terminal, comprising:

[0107] The sending module is configured to send a first message, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0108] In conjunction with some embodiments of the third aspect, in some embodiments, the first message includes at least one of the following:

[0109] Radio Resource Control (RRC) setup request message for idle state;

[0110] RRC recovery request message for inactive state;

[0111] RRC connection establishment completion message for idle state;

[0112] RRC connection recovery complete message for inactive state.

[0113] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes at least one of the following:

[0114] A first reason, indicating that the terminal requests the second information to be sent;

[0115] The second reason indicates that the terminal requests to establish only an RRC signaling connection;

[0116] A third reason indicates that the terminal moves and initiates data;

[0117] a first identifier, indicating that the terminal serves as an identifier of the first device reader;

[0118] A task identifier, indicating a task for the first device to send the first information;

[0119] The second identifier indicates the first device.

[0120] In combination with some embodiments of the third aspect, in some embodiments, the transceiver module is configured to send the first message upon detecting a preset event.

[0121] In conjunction with some embodiments of the third aspect, in some embodiments, the preset event includes at least one of the following:

[0122] The terminal completes the task of collecting the second information;

[0123] The cache amount of the second information reaches a first threshold;

[0124] The current time reaches the reporting time configured for the first information;

[0125] The cache duration of the second information is equal to or greater than the first duration;

[0126] The remaining cache space of the terminal is less than a preset value;

[0127] The terminal receives the delay-sensitive second information.

[0128] In conjunction with some embodiments of the third aspect, in some embodiments, the terminal further includes:

[0129] A processing module is configured to establish an RRC connection with an access network device;

[0130] The transceiver module is configured to send the second information based on the RRC connection.

[0131] In combination with some embodiments of the third aspect, in some embodiments, the processing module is configured to establish only an RRC signaling connection with the access device; wherein, when the RRC signaling connection is established, a signaling radio bearer SRB1 is established with the terminal.

[0132] In combination with some embodiments of the third aspect, in some embodiments, the terminal is established with SRB1, SRB2 and / or data radio bearer DRB.

[0133] In combination with some embodiments of the third aspect, in some embodiments, the second information sent based on the RRC connection carries a task identifier added by the first device;

[0134] or,

[0135] The second information sent based on the RRC connection carries the task identifier added by the terminal.

[0136] In a fourth aspect, an embodiment of the present disclosure provides an access network device, including:

[0137] The receiving module is configured to receive a first message from the terminal, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0138] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first message includes at least one of the following:

[0139] Radio Resource Control (RRC) setup request message for idle state;

[0140] RRC recovery request message for inactive state;

[0141] RRC connection establishment completion message for idle state;

[0142] RRC connection recovery complete message for inactive state.

[0143] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information includes at least one of the following:

[0144] A first reason, indicating that the terminal requests the second information to be sent;

[0145] The second reason indicates that the terminal requests to establish only an RRC signaling connection;

[0146] A third reason indicates that the terminal moves and initiates data;

[0147] A fourth reason is to instruct the terminal to report drive test data;

[0148] a first identifier, indicating that the terminal serves as an identifier of the first device reader;

[0149] A task identifier, indicating a task for the first device to send the first information;

[0150] The second identifier indicates the first device.

[0151] In conjunction with some embodiments of the fourth aspect, in some embodiments, the access network device further includes:

[0152] A processing module is configured to establish an RRC connection with the terminal based on the first message.

[0153] In combination with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to receive the first information sent based on the RRC connection.

[0154] In combination with some embodiments of the fourth aspect, in some embodiments, the RRC connection includes: only RRC signaling connection.

[0155] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is configured to establish the RRC signaling-only connection with the terminal and configure a signaling radio bearer SRB1 for the terminal.

[0156] In combination with some embodiments of the fourth aspect, in some embodiments, the processing module is configured to establish SRB1, SRB2 and / or data radio bearer for the terminal.

[0157] In conjunction with some embodiments of the second aspect, in some embodiments, the transceiver module is further configured to send the second information to a core network device; wherein the second information is sent by the core network device to the second device;

[0158] or,

[0159] The second information is sent to the second device.

[0160] In conjunction with some embodiments of the second aspect, in some embodiments, the second information includes a task identifier added by the first device;

[0161] or,

[0162] The second information includes a task identifier added by the terminal;

[0163] or,

[0164] The second information includes a task identifier added by the access network device.

[0165] In a fifth aspect, an embodiment of the present disclosure provides a communication method, wherein:

[0166] The terminal executes the communication method provided by any technical solution of the first aspect.

[0167] The communication method provided by any technical solution of the second aspect of the access network device.

[0168] In a sixth aspect, an embodiment of the present disclosure provides a communication system, wherein the information indication system includes a terminal and an access network device; the target terminal is configured to implement the communication method provided by any technical solution of the first aspect, and the access network device is configured to implement the communication method of any technical solution of the second aspect. In a seventh aspect, an embodiment of the present disclosure provides a communication device, wherein the communication device includes:

[0169] one or more processors;

[0170] The processor is used to call instructions to enable the communication device to execute the communication method described in the optional implementation manner of the first aspect or the second aspect.

[0171] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the communication method described in the optional implementation of the first aspect or the second aspect.

[0172] In a ninth aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the communication method described in the optional implementation manner of the first aspect or the second aspect.

[0173] In a tenth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the communication method described in the optional implementation manner of the first aspect or the second aspect.

[0174] It is understandable that the above-mentioned terminals, access network devices, communication devices, communication systems, storage media, program products, and computer programs are all used to execute the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0175] The present disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method" are interchangeable; the terms "information indicating device" and "information processing device" are interchangeable; and the terms "communication system" and "information processing system" are interchangeable.

[0176] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0177] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0178] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0179] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0180] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0181] In some embodiments, the terms "at least one (at least one of)," "one or more (one or more)", "plurality (aplurality of)", "multiple (multiple)" and the like can be used interchangeably.

[0182] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0183] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0184] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0185] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0186] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0187] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0188] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0189] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0190] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0191] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0192] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0193] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0194] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0195] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0196] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0197] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0198] As shown in FIG1A , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0199] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0200] In some embodiments, the access network device 102 can be, for example, a node or device that accesses the terminal to the wireless network. The access network device may include an evolved Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (CloudRAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0201] In some embodiments, the technical solution of the present disclosure can be applied to the OpenRAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of OpenRAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0202] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0203] In some embodiments, the core network device 103 may be a single device including the first network element 1031, or may be a plurality of devices or a group of devices, each including the first network element 1031. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0204] In some embodiments, the first network element 1031 is, for example, an access and mobility management function (AMF).

[0205] In some embodiments, the first network element 1031 is, for example, a Mobility Management Entity (MME).

[0206] In some embodiments, the first network element 1031 is used for access and mobility management, such as registration management, connection management, and mobility management, etc., but the name is not limited thereto.

[0207] In some embodiments, the first network element 1031 may be a network element independent of the core network device.

[0208] In some embodiments, the core network may further include a second network element, etc. The second network element may include: User Data Management (UDM), etc.

[0209] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0210] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0211] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0212] In some cases, IoT devices are often powered by traditional batteries with limited lifespans, negatively impacting the user experience. The expected astronomical growth in the number of IoT network devices, coupled with the massive number of IoT devices, has pushed maintenance expenses, including labor and battery costs, to a whole new level. Billions of traditional batteries are discarded each year, with only a small fraction effectively recycled, negatively impacting the Earth's ecosystem. Maintaining IoT network operations and replacing batteries can be extremely challenging in extreme environmental conditions. Battery-free IoT communications have been proposed to improve network performance and sustainability, expanding their application scenarios. Furthermore, battery-free communications are more environmentally friendly and safer for children and the elderly. By eliminating traditional batteries, device size and cost can be significantly reduced, paving the way for a variety of new applications.

[0213] In some implementations, various Low Power Wide Area (LPWA) technologies, such as Machine Type Communication (MTC), Narrow Band Internet of Things (NB-IoT), and Reduced Capability (RedCap), have been developed to meet the growing demands of various vertical sectors. These LPWA technologies offer low cost, low power consumption, and large-scale connectivity, meeting the requirements of many applications. However, many use cases and applications remain unaddressed. First, battery-powered devices are not suitable, such as in extreme environmental conditions (e.g., high voltage, extremely high / low temperatures, and humid environments). Second, maintenance-free devices are required (e.g., devices without traditional batteries requiring replacement). Finally, ultra-low complexity, very small device size / form factor (e.g., mm thickness), and extended lifecycles are required. Ambient-powered IoT devices are promising technologies that can address these unmet needs. Ambient-powered IoT devices are IoT devices powered by energy harvesting, either without batteries or with limited energy storage capabilities (e.g., using capacitors). Energy is collected from radio waves, light, motion, heat, or any other suitable power source.

[0214] Energy obtained from the environment can drive data transmission and wireless communication of sensing nodes. The current mainstream low-power IoT communication chips (such as BLE, LoRa, NB-IoT) have a transmit and receive power consumption of tens or even hundreds of milliwatts, while the energy obtained by environmental energy harvesting is only at the microwatt level, which is unable to drive these types of nodes to work. Therefore, a new wireless communication technology is needed to reduce communication energy consumption to tens of microwatts or even less than ten microwatts. The current mainstream method uses backscatter communication technology. Backscatter Communications is one of the key technologies for building a green, energy-saving, low-cost, and flexibly deployable future Internet of Things, and is an important means to achieve "Intelligent Connection of Everything". The methods that can be used include backscatter transmission (Backscatter Communications) technology.

[0215] As shown in Figure 1B, backscatter transmission can utilize the principle of RF signal backscattering to design extremely low-power modulation and transmission technologies. A reader sends a physical layer signal to an ambient IoT device. This physical layer signal can be a pulse signal or other AC signal. In some embodiments, this physical layer signal is used to provide energy for the ambient IoT device to transmit the signal. Therefore, this physical layer signal can be referred to as an excitation signal or trigger signal. For example, since a portion of the excitation signal is reflected when it reaches the ambient IoT device, the ambient IoT device can adjust the matching between the receiving antenna and the impedance according to the intended information to enhance the reflection of the incident excitation signal and modulate the acquired sensor data onto the reflected signal to complete the data transmission. This process is similar to a reflector. Compared to other communication technologies, backscatter transmission does not require complex RF structures, reducing the use of components such as power amplifiers, high-precision crystal oscillators, duplexers, and high-precision filters. It also does not require complex baseband processing. Therefore, it can simplify the design of ambient IoT devices and significantly reduce the cost of ambient IoT device nodes. Ambient IoT devices are IoT devices that use environmental energy to operate. This environmental energy can include the aforementioned wireless signal energy, as well as other environmental capabilities such as geothermal energy and / or light energy.

[0216] Here, the device that sends a physical layer signal to the ambient IoT device and triggers the ambient IoT device to return a reflected signal can be called an anchor point of the ambient IoT device reader.

[0217] It is worth noting that an ambient IoT device is a device that uses the backscatter transmission mechanism for wireless communication. In specific implementations, other devices can also use the backscatter transmission mechanism for wireless communication.

[0218] The anchor point or reader of the ambient IoT device may be a network node of a wireless communication network, such as an access network device, a relay node (or intermediate node), or a terminal.

[0219] Backscatter transmission network topologies can include one of the following:

[0220] Topology 1: As shown in Figure 1C, uplink (UL) and downlink (DL) data transmission is carried out directly between ambient IoT devices and access network devices.

[0221] Topology 2: As shown in Figure 1D, DL and UL data transmission occurs indirectly between ambient IoT devices and access network equipment. Intermediate nodes (also called auxiliary nodes) provide forwarding services. These intermediate nodes can include relays, integrated access backhaul (IAB), user equipment (UE), and repeaters (RP).

[0222] Topology 3: As shown in Figure 1E, ambient IoT devices and access network devices directly transmit or receive data in the DL or UL. Auxiliary nodes are located on the UL or DL, responsible for receiving or sending UL or DL ​​data. Examples of auxiliary nodes include relays, integrated access backhaul (IAB) nodes, terminals, and network controlled repeaters (NCRs).

[0223] Topology 4: As shown in Figure 1F, ambient IoT devices and UEs directly receive and transmit data on the downlink and uplink. The UE collects data and forwards it to the network.

[0224] As shown in Figure 1G, devices that use the backscatter transmission mechanism for wireless communication can be divided into three types:

[0225] Device A: has no energy storage, cannot generate or amplify signals independently, and can only perform backscatter transmission.

[0226] Device B: Has energy storage, cannot generate signals independently, and can only perform backscatter transmission. The use of stored energy can include amplification of the backscattered signal.

[0227] Device C: has energy storage and can independently generate signals, that is, it has active radio frequency (RF) components for transmission.

[0228] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to a communication method for a communication system 100, the method comprising:

[0229] S2101: The terminal sends a first message.

[0230] In some embodiments, the first message is any message for the terminal to request to enter the connected state or any message after entering the connected state.

[0231] In some embodiments, the first message includes: first information.

[0232] In some embodiments, the first information indicates that the terminal has second information to send.

[0233] In some embodiments, the second information is transmitted to the terminal by the first device based on a trigger of the first signal of the terminal.

[0234] The terminal may be any communication terminal that includes a power supply module. For example, the target terminal may be any type of communication terminal that includes a battery. For example, the communication terminal may include, but is not limited to, a mobile phone, a tablet computer, an in-vehicle device, a wearable device, a smart home device, and / or a smart office device.

[0235] The terminal may be a device that has the capability and / or agrees (or desires or is willing) to serve as the first device reader. The reader may also be referred to as an anchor point.

[0236] Before sending the first message, the terminal may send third information to the network device.

[0237] In some embodiments, the third information includes one of the following:

[0238] Capability information, indicating whether the terminal supports the reader as the first device;

[0239] Indication information indicating whether the terminal agrees or desires to serve as the reader of the first device.

[0240] In some embodiments, the third information further includes at least one of the following:

[0241] Proposed spatiotemporal information, indicating the time information and / or spatial information that the terminal agrees with or expects to be the reader of the first device;

[0242] Bandwidth information, indicating the radio frequency information used when the terminal acts as a reader.

[0243] Of course, the above is just an example of the third information, and the specific implementation is not limited to the above example.

[0244] The network device receives the third information from the terminal. For example, the access network device receives the third information from the terminal. For example, the UDM and / or UDR of the core network device stores part of the third information and obtains the entire information. The second base station may obtain the third information from the UDM or UDR based on forwarding or transparent transmission of the AMF.

[0245] According to the third information, a terminal that supports and agrees (or desires or is willing) to serve as a reader is selected.

[0246] In some embodiments, the third information may further include one of the following:

[0247] Time information, indicating the time at which the target terminal agrees or expects to act as a reader;

[0248] Spatial information, indicating the location area in which the target terminal agrees or expects to act as a reader;

[0249] Status information indicates whether the target terminal agrees or expects to act as a reader. This terminal status may be related to the terminal's load rate, whether the terminal has service data to send, the terminal's remaining battery power, and / or the terminal's temperature.

[0250] For example, the time information may indicate that the target terminal may act as a reader when its own traffic volume is generally relatively low.

[0251] For another example, the time information may indicate that the target terminal has free traffic or is in a low-rate area and can act as a reader.

[0252] For another example, the status information may indicate that the terminal itself can act as a reader when it has no service data to send.

[0253] For example, the status information may indicate that the terminal can act as a reader when the remaining power of the terminal itself is greater than a power threshold.

[0254] For another example, the status information may indicate that the terminal can act as a reader when its own temperature is lower than a temperature threshold.

[0255] By sending the third information, the communication interference of the target terminal itself when the target terminal acts as the first device reader is reduced, thereby ensuring the communication quality of the target terminal itself.

[0256] In other embodiments, the third information is reported to the core network device, and the terminal serving as the reader of the first device can be selected by the core network device. In still other embodiments, the third information can be sent to the second device, and the terminal serving as the reader of the first device can be selected by the second device.

[0257] After the core network device and / or the second device is selected as the reader of the first device, the device information of the reader of the first device is sent to the second base station.

[0258] In short, the terminal is selected by the network device as the reader of the first device based on the third information reported by the terminal and / or the contract data of the terminal.

[0259] In some embodiments, the first device may be any terminal that uses a backscatter transmission mechanism for wireless communication.

[0260] In some embodiments, the first device may be the device of Figure 1G.

[0261] In some embodiments, the terminal sends a first message to the network device.

[0262] In other embodiments, the terminal sends a first message to the access network device.

[0263] In some embodiments, the network device receives a first message.

[0264] Exemplarily, the access network device receives the first message.

[0265] In some instances, the first message may be any message in which a non-connected terminal requests to switch to a connected state, or the first message may be any message in which a terminal switches from a non-connected state to a connected state, or the first message may be any message in which a non-connected terminal switches to a connected state.

[0266] In some embodiments, the first message may be any access stratum (AS) layer message, including but not limited to an RRC message, a MAC layer message, or uplink control information (UCI).

[0267] In some embodiments, the first message includes first information, which may be indicated by one or more bits. The first information may be indicated explicitly by one or more bits, or implicitly by one or more bits.

[0268] The unconnected state may include an idle state and / or an inactive state.

[0269] In some embodiments, the terminal sends a first signal to the first device when in a non-connected state;

[0270] The first device returns second information to the terminal based on the first signal.

[0271] At this time, the terminal serves as an anchor point for the first device. In other words, the terminal serves as a reader for the first device.

[0272] A wireless device that has a power supply module but the power supply module has lost its power supply capability, or any wireless device that supports backscatter communication.

[0273] In some embodiments, the first device may be any passive device, an ambient energy device, or an ambient IoT device.

[0274] In some embodiments, the first signal at least triggers the first device to send the second information. That is, in some cases, the first signal can serve as a trigger signal for the first device to send the second information.

[0275] In some embodiments, the first signal is an excitation signal for the first device, and the first signal excites the first device to send the second information.

[0276] In some embodiments, the first signal provides energy for the first device to transmit the second information. Exemplarily, the first device receives the first signal and transmits the second information based on the signal energy of the first signal.

[0277] In some embodiments, the second information may include data and / or signaling. For example, the second information may include pre-configured data on the first device and data and / or signaling written to the first device by a third device. For example, the third device may be various sensors. The pre-configured data herein may be any data written to the first device before the first device is put into use.

[0278] Exemplarily, the preset data of the first device includes but is not limited to one of the following:

[0279] a device identifier of the first device;

[0280] device type information of the first device;

[0281] The identification and / or target information of the target carrying the first device. For example, the target carrying the first device may include an object such as a courier. The pre-set data on the first device may include the identification of the target and / or information about the type of courier, the origin and destination of the courier, and / or security information.

[0282] In some embodiments, although the first device does not have its own power supply or only has a power supply module for temporary energy storage or a power supply module with limited power supply capacity, the first device has storage space and serves as an external storage device for a third device, allowing the third device to write data and / or signaling. In this way, even if the first device does not have pre-configured data, the second information in the first device is dynamically updated.

[0283] In this way, through the first message, the terminal can report the relevant information of the second data of the first device cached by the terminal in the non-connected state to the network device.

[0284] In some embodiments, the first message may be any one of message 1 to message 5 sent by the terminal when the terminal switches from the non-connected state to the connected state. That is, the first message may be any one of message 1, message 3 and message 5.

[0285] Exemplarily, the message carrying the first information may be Msg3 and / or Msg5.

[0286] In some embodiments, the terminal is in an idle state, and the terminal sends the first information via an RRC Setup Request message or an RRC Setup Complete message for the idle state.

[0287] In some embodiments, the terminal is in an inactive state, and the terminal may send the first information via an RRC resume request (RRC Resume Request) message for the inactive state or an RRC resume complete (RRC Resume Complete) message for the inactive state.

[0288] The RRC establishment request message and the RRC recovery request message here can both be the aforementioned message three.

[0289] The RRC connection establishment complete message and the RRC connection recovery complete message here can both be the aforementioned message five.

[0290] In some embodiments, the first information includes at least one of the following:

[0291] A first reason, indicating that the terminal requests the second information to be sent;

[0292] The second reason indicates that the terminal requests to establish an RRC signaling connection only;

[0293] The third reason indicates that the terminal moves and initiates data;

[0294] A first identifier, indicating that the terminal serves as an identifier of a first device reader;

[0295] A task identifier, indicating a collection task for obtaining the second information of the first device;

[0296] The second identifier indicates the first device.

[0297] In some embodiments, the first reason may be equivalent to an explicit indication that the second information is to be sent. For example, the first reason may include a reason code, and a value of "1" in the bit corresponding to the reason code indicates that the terminal has requested the second information to be sent. If the second information does not include the reason code, or the value of the bit corresponding to the reason code is "0," the terminal may not have requested the second information to be sent.

[0298] In some embodiments, the terminal may default to sending the second cause because the second information triggers a preset event. The second cause indicates that the terminal requests to establish an RRC signaling-only connection.

[0299] In some embodiments, if the terminal desires to enter the connected state due to reasons such as the second information, other service data of the terminal itself, or the terminal receiving a system message update notification, a third reason is sent via the first information. The third reason may be used to request the establishment of an RRC connection, which may include but is not limited to a conventional RRC connection.

[0300] In some embodiments, the terminal needs to send the second information, and the terminal is a reader of the first device. In this case, the terminal may be assigned a first identifier of the reader.

[0301] In some embodiments, the first identifier may include one or more parts. For example, the first identifier may include at least: a first part and a second part.

[0302] The first part may include but is not limited to one of the following:

[0303] cell identification;

[0304] Base station identification;

[0305] Cell group ID;

[0306] Tracking area identifier.

[0307] The second part may be the reader's serial number (SN) assigned by the network device.

[0308] In some embodiments, the first identifier may further include a third part. The third part may be determined according to a type and / or service type lower than the first device type agreed to or signed by the user of the terminal.

[0309] For example, the third part may include but is not limited to at least one of the following:

[0310] The first device may include a device type code;

[0311] The terminal can support the service code forwarded by the first device, etc.

[0312] The task identifier indicates the collection task. Thus, the first information is the task identifier. The network device can know from the task identifier that the reason for entering the connection state this time is to report the second information sent by the first device.

[0313] The second identifier may be the second identifier of the first device. The identifier of the first device may include one or more parts. For example, the second identifier of the first device may include: a first part and a second part.

[0314] Illustratively, the first part may include at least one of the following:

[0315] Business code;

[0316] Task identification;

[0317] a device type code of the first device;

[0318] The first device is assigned an associated identifier.

[0319] In some embodiments, when the base station allocates an identifier to the first device, the related identifier may include a base station identifier or a cell identifier of the base station.

[0320] In another embodiment, when the core network allocates an identifier to the second device, the related identifier may be a device identifier of the second device.

[0321] Also illustratively, the second part may include at least one of the following:

[0322] Sequential coding of the device;

[0323] Random number.

[0324] In some embodiments, the terminal is in a non-connected state and detects a preset event, and sends a first message.

[0325] In this way, unnecessary sending of first messages by the terminal is reduced.

[0326] The preset event may also be referred to as a trigger event.

[0327] The first message is sent only when a preset event is detected, thereby reducing unnecessary information transmission by the terminal and further reducing signaling overhead.

[0328] In some embodiments, the terminal completes a collection task associated with the second information;

[0329] The cache amount of the second information reaches a first threshold;

[0330] The current time reaches the reporting time configured for the first information;

[0331] The cache duration of the second information is equal to or greater than the first duration;

[0332] The remaining cache space of the terminal is less than the preset value;

[0333] The terminal receives delay-sensitive second information.

[0334] The cache amount of the second information here may be the total amount of data of the second information of one or more second devices.

[0335] When the cache amount of the second information reaches a first threshold, the terminal exits the non-connected state and enters the connected state, and reports the cached second information to the network device.

[0336] In some cases, the cached second information is configured to be reported periodically or irregularly. If the reporting time is reached and the terminal has cached the second information that has not been reported in the flying connection state, it can be considered that a preset event has been detected.

[0337] In some implementations, the cache time of the second information is relatively long. In order to report it as quickly as possible, even when the cache time is relatively long and the data volume may be relatively small, the connection state is entered to report the second information to the network device side in a timely manner.

[0338] In some cases, the terminal caches the second information of one or more first devices. For example, when caching the second information of multiple first devices, the multiple first devices may be devices of the same type, or devices that need to report data of the same type.

[0339] If the amount of data currently cached by the terminal is large, the cache space in the terminal will be occupied. When the remaining cache space of the terminal gradually decreases to a certain extent, for example, when it decreases to less than a preset value, it can be considered that a preset event is detected.

[0340] In some embodiments, when the terminal receives the second information sent by the second device and finds that the second information is delay-sensitive information and needs to be reported in a timely manner, it can also be considered that a preset event is detected.

[0341] In other embodiments, if the terminal has service data to report, or needs to enter a connected state by monitoring a system message update, and the terminal happens to have second information to send, the first information can also be sent in a first message triggered by the terminal's own service data reporting and / or system message update, thereby incidentally notifying the network device that the terminal currently has cached the second information. In some embodiments, the access network device receives the first message sent by the terminal.

[0342] S2102: The terminal establishes an RRC connection with the access network device.

[0343] In some embodiments, the terminal establishes an RRC connection with the access network device by sending one or more messages between the terminal and the access network device.

[0344] After the terminal establishes an RRC connection with the access network device, the terminal exits the non-connected state and enters the connected state. This connected state is the abbreviation of the RRC connection state.

[0345] Establishing an RRC connection includes establishing a signaling bearer and / or a data bearer between the terminal and the access network device.

[0346] The establishment of a signaling bearer may include, but is not limited to, allocating a signaling radio bearer (SRB) to the terminal. The SRB may include SRB1 and / or SRB2. The SRB may be used for signaling transmission on the control plane. SRBs may also include SRB0. The SRB0 does not need to be established and can be used for signaling transmission on the Common Control Channel (CCCH). The signaling transmitted by the CCCH may include, but is not limited to, an RRC connection request message, an RRC connection rejection message, an RRC connection establishment message, an RRC connection reestablishment message, and / or an RRC connection reestablishment rejection message.

[0347] SRB1 can be used to transmit various RRC messages, including all RRC messages except CCCH transmission RRC signaling.

[0348] SRB2 can be used to establish reconfiguration messages. The priority of SRB2 is lower than that of SRB1. For example, SRB2 can be used to transmit Non-Access Stratum (NAS) messages.

[0349] Exemplarily, SRB0 may be used for signaling of various CCCH transmissions.

[0350] The establishment of a data bearer may include but is not limited to: allocating a Data Radio Bearer (DRB) to the terminal. The DRB may be used for data transmission on the data plane.

[0351] In some embodiments, after the access network device receives the first message carrying the second information, the core network device establishes an RRC connection with the terminal.

[0352] S2103: During the process of establishing the RRC connection, configure SRB1, SRB2 and / or DRB for the terminal.

[0353] In some embodiments, the second information is sent based on a radio bearer allocated for the RRC connection during the RRC connection establishment process by the access network device.

[0354] The radio bearer includes but is not limited to a signaling radio bearer (SRB) and / or a data radio bearer (DRB).

[0355] In some embodiments, an RRC connection may include a regular RRC connection and an RRC signaling-only connection. Establishing an RRC signaling-only connection involves only establishing SRB1 and AS security activation, without establishing SRB2 or DRBs. This means that an RRC signaling-only connection is a simplified RRC connection.

[0356] In some embodiments, if a conventional RRC connection is established between the terminal and the access network device, the RRC connection may need to establish not only SRBs but also DRBs. Therefore, in this case, the terminal may be configured with SRB1, SRB2, and / or DRBs.

[0357] In some embodiments, if the second information cached in the terminal causes a preset event to be triggered, a request may be made to establish an RRC signaling connection only. In this case, the first information may include but is not limited to at least one of the following:

[0358] A first reason, indicating that the terminal requests the second information to be sent;

[0359] The second reason indicates that the terminal requests to establish an RRC signaling connection only;

[0360] A first identifier, indicating that the terminal serves as an identifier of a first device reader;

[0361] A task identifier, indicating a collection task for obtaining the second information of the first device;

[0362] The second identifier indicates the first device.

[0363] In other embodiments, when a preset event is triggered by the terminal's own service and / or system message update, the terminal may request to establish a regular RRC connection. In this case, the first information may include but is not limited to at least one of the following:

[0364] The third reason indicates that the terminal moves and initiates data;

[0365] The fourth reason indicates a request to obtain updated system information;

[0366] The fifth reason indicates a response to a paging message from a network device.

[0367] Of course, the above is merely an example of determining the type of RRC connection to be established based on the information content of the first information, and the specific implementation is not limited to this example.

[0368] In some embodiments, only an RRC signaling connection is established between the terminal and the access network device, and the terminal may be configured with SRB1.

[0369] In some embodiments, a conventional RRC connection is established between the terminal and the access network device. In this case, the terminal is configured with SRB1 and may also be configured with at least one of SRB2 and DRB.

[0370] In some embodiments, the second information sent based on the RRC connection carries a task identifier added by the first device; or, the second information sent based on the RRC connection carries a task identifier added by the terminal.

[0371] Adding a task identifier in the second information can facilitate the network device to distinguish whether the second information comes from the terminal itself or the first device.

[0372] In some embodiments, the second information may not include the task identifier, but may include the device identifier of the first device.

[0373] In other embodiments, the second information may include a task identifier and a device identifier of the first device. The device identifier of the first device may be added to the second information by the terminal or by the first device.

[0374] Since the first device itself is a passive device or has very low energy consumption, the task identifier and / or the device identifier of the first device can be added to the second information by the terminal, thereby reducing the energy consumption required for transmitting the task identifier and / or the device identifier of the first device.

[0375] S2104: Send second information based on the RRC connection.

[0376] The terminal sending the second information based on the RRC connection may include: sending the second information based on the resource configuration associated with the RRC connection.

[0377] In some embodiments, the resource configuration associated with the RRC connection may include:

[0378] Resource configuration for sending any type of data and / or signaling to the terminal;

[0379] Resource configuration for sending the second information to the terminal.

[0380] The resource configuration may include but is not limited to at least one of the following:

[0381] Bearer configuration, indicating the RBs configured for the terminal, which may include but are not limited to SRBs and / or DRBs;

[0382] Channel configuration indicates the channel configured for the terminal, which may include but is not limited to a logical channel and / or a physical channel.

[0383] These resource configurations can be carried in any message sent by the access network device to the terminal when the terminal establishes a connection with the access network device.

[0384] Exemplarily, resource configuration regarding the second information includes but is not limited to at least one of the following:

[0385] Bearer configuration, indicating an RB for sending the second information, where the RB may include but is not limited to an SRB and / or a DRB;

[0386] The channel configuration indicates a physical channel and / or a logical channel for sending the second information.

[0387] The physical channel includes but is not limited to a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) and / or a physical uplink control channel (Physical Uplink Control Channel, PUCCH).

[0388] The configuration of the logical channel may include but is not limited to an identifier of the logical channel and / or an identifier of a logical channel group.

[0389] The access network device receives the second information based on the RRC connection.

[0390] In some embodiments, neither the terminal nor the first device adds the task identifier and / or the device identifier of the first device to the second information, but the access network device adds the task identifier and / or the device identifier of the first device.

[0391] In some embodiments, the core network device receives the second information based on an RRC connection established with the terminal.

[0392] In some embodiments, the second information received by the access network device may be added with a task identifier by the terminal or the first device.

[0393] In other embodiments, if the access network device receives the second information without adding a task identifier, the access network device will add task information to the second information.

[0394] In some embodiments, the second information may also include other task information related to the collection task, which may be used for routing and forwarding the second information. In some embodiments, the terminal or first device may add the second information to the task information, and the access network device may then directly perform routing and forwarding based on the task information. In other embodiments, if the terminal or first device does not add the task information to the second information, the access network device may add the task information to the second information.

[0395] In some embodiments, the task information may be used for routing, addressing, or forwarding of the second information.

[0396] The task information may include at least one of the following:

[0397] address information of the second device;

[0398] Channel information for sending the second information to the second device. The channel may include tunnel and / or connection information based on various interfaces.

[0399] In some embodiments, the terminal or access network device may be given priority to add task information to the second information, thereby reducing the power consumption that the terminal needs to provide to the first device.

[0400] As shown in FIG3 , an embodiment of the present disclosure provides a communication method, which is executed by a terminal. The method includes:

[0401] S3101: Send a first message, wherein the first message is used for the terminal to request any message to enter the connected state or any message after entering the connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

[0402] The terminal may be any terminal as shown in Figure 2. The terminal may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, a smart home device and / or a smart office device.

[0403] In some embodiments, the terminal is in a non-connected state and sends a first message, which may be a request for the terminal to enter a connected state.

[0404] In other embodiments, the terminal is in a non-connected state and has cached the second information, and the terminal requests to enter a connected state; after entering the connected state, the first message is sent.

[0405] In some embodiments, the terminal is in an idle state, and the first message is an RRC establishment request message or an RRC connection establishment completion message.

[0406] In some embodiments, the terminal is in an inactive state, and the first message may be an RRC recovery request message or an RRC connection recovery complete message.

[0407] The information content of the first information can refer to any embodiment shown in FIG2 .

[0408] S3102: Establish an RRC connection with the access network device;

[0409] In some embodiments, only an RRC signaling connection is established with the access network device.

[0410] Exemplarily, when only the second information is sent, only an RRC signaling connection is established with the access network device.

[0411] As another example, when only the second information is sent and the data volume of the second information is less than a specified threshold, only an RRC signaling connection is established with the access network device.

[0412] In some embodiments, a conventional RRC connection is established with the access network device for data and / or signaling transmission other than the second information. For example, if the terminal needs to upload its own service data and / or control signaling in addition to the second information, a conventional RRC connection is established with the access network device.

[0413] S3103: Send the second information through the established RRC connection.

[0414] In some embodiments, the second information is sent via SRB1, SRB2 and / or DRB corresponding to the established RRC connection.

[0415] In other embodiments, the second information is sent via a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH) corresponding to the established RRC connection. The PUSCH and / or PUCCH herein may be indicated by a channel configuration.

[0416] As shown in FIG4 , an embodiment of the present disclosure provides a communication method, which is performed by an access network device. The method includes:

[0417] S4101: Receive the first message.

[0418] In some embodiments, the first message is any message for the terminal to request to enter the connected state or any message after entering the connected state.

[0419] In some embodiments, the first message includes: first information; wherein the first information indicates second information to be sent by the terminal.

[0420] In some embodiments, the second information is transmitted to the terminal by the first device based on a trigger of the first signal of the terminal.

[0421] The access network device may be any access network device as shown in FIG1A . Specifically, the access network device may be various types of base stations, for example, the base station may be an eNB and / or a gNB.

[0422] The access network device may be the terminal's serving base station. For example, if the terminal is not performing cell reselection in a non-connected state, the serving base station may be the base station that distributes the collection task. For another example, if the terminal is performing cell reselection in a non-connected state, the serving base station may be the target base station for the terminal's cell reselection.

[0423] The first device may be any device as shown in FIG. 2 .

[0424] The terminal may be any terminal as shown in Figure 2. The terminal may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, a smart home device and / or a smart office device.

[0425] In some embodiments, the terminal is in a non-connected state and sends a first message, where the first message may be a request for the terminal to enter a connected state.

[0426] In other embodiments, the terminal is in a non-connected state and has cached the second information, and the terminal requests to enter a connected state; after entering the connected state, the first message is sent.

[0427] In some embodiments, the terminal is in an idle state, and the first message is an RRC establishment request message or an RRC connection establishment completion message.

[0428] In some embodiments, the terminal is in an inactive state, and the first message may be an RRC recovery request message or an RRC connection recovery complete message.

[0429] For the information content of the first information, please refer to the relevant description of the embodiment shown in FIG2 .

[0430] For the information content of the second information, please refer to the relevant description of the embodiment shown in FIG2 .

[0431] In some embodiments, a preset event is detected and a first message is sent.

[0432] In some embodiments, the terminal detects a preset event in a non-connected state and sends a first message.

[0433] The relevant details of the preset event can be found in the embodiment shown in FIG2 , and will not be repeated here.

[0434] S4102: Establish an RRC connection with the terminal.

[0435] The RRC connection may be an RRC signaling-only connection, and / or a regular RRC connection.

[0436] In some embodiments, only an RRC signaling connection is established with the terminal.

[0437] Exemplarily, when the first message sent by the terminal indicates that only the second information is involved in sending, only an RRC signaling connection is established with the terminal.

[0438] As another example, when the first message sent by the terminal indicates that only the second information is involved and the data volume of the second information is less than a specified threshold, only an RRC signaling connection is established with the access network device.

[0439] In some embodiments, the first message sent by the terminal indicates that data and / or signaling other than the second information is to be transmitted, and a regular RRC connection is established with the terminal. For example, in addition to uploading the second information, the terminal's own service data and / or control signaling also needs to be uploaded, and a regular RRC connection is established with the access network device.

[0440] In some embodiments, during the process of establishing an RRC connection with a terminal, the access network device provides resource configuration to the terminal in a message used to establish the RRC connection.

[0441] Exemplarily, the resource configuration may be used by the terminal to send any information (the information includes data and / or signaling) that the terminal needs to report, and may also be used to send the second information.

[0442] The resource configuration may include: bearer configuration and / or channel configuration.

[0443] S4103: Receive second information through the established RRC connection.

[0444] In some embodiments, the second information is sent via SRB1, SRB2, and / or DRB corresponding to the established RRC connection. For example, SRB1, SRB2, and DRB herein may all be indicated by a bearer configuration.

[0445] In other embodiments, the second information is sent via a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH) corresponding to the established RRC connection. The PUSCH and / or PUCCH herein may be indicated by a channel configuration.

[0446] In some embodiments, after receiving the second information, the access network device sends the second information to the second device through the first channel between the access network device and the second device.

[0447] In other embodiments, after receiving the second information, the access network device sends the second information to the core network device via a second channel between the access network device and the core network device. The second information is sent from the core network device to the second device.

[0448] The present disclosure provides a communication method, wherein:

[0449] The terminal is a communication method provided by any technical solution of the first aspect above;

[0450] The access network device executes the communication method provided by any solution of the aforementioned second aspect.

[0451] To rapidly and cost-effectively deploy the passive IoT, a passive IoT data collection method based on the UE as an anchor point was proposed. As a reader, the UE does not necessarily need to collect and report data in real time. Data can be cached on the UE side and then uniformly reported and routed after the UE enters the connected state. The UE does not need to maintain an RRC connection state to collect a small data packet, thus saving power. Therefore, supporting UEs in the RRC_IDLE / INACTIVE state as readers is a problem that needs to be solved. For example, how to obtain relevant configurations and how to perform reporting are issues that need to be clarified.

[0452] Data reporting by RRC_IDLE / INACTIVE UE as reader:

[0453] Option 1: Second information reporting based on message 3 (MSG3 based indication):

[0454] When the data collected and / or stored by an RRC_IDLE / INACTIVE UE as a reader exceeds a certain threshold, such as mbyte, or when the RRC_IDLE / INACTIVE UE has completed its task as a reader, the RRC_IDLE / INACTIVE UE reader initiates the RRC connection establishment process. The MSG3 message (RRCSetupRequest) carries the cause value for the RRC connection establishment, i.e., EstablishmentCause, which is an IoT data collection and reporting request. This cause value is generated by the access layer (AS) layer.

[0455] Alternatively, the RRC connection establishment cause value carried in the MSG3 message, namely, EstablishmentCause, indicates a request to establish an RRC signaling-only connection. This means that the RRC connection only establishes SRB1, AS security is activated, and SRB2 and DRB are not established. Alternatively, the RRC connection only establishes SRB1, SRB2, and / or other SRBs for other purposes, AS security is activated, and DRB is not established. This cause value is generated by the access stratum (AS) layer. This establishment cause value can be the first cause, second cause, or third cause mentioned above.

[0456] Alternatively, the UE identification information carried in the MSG3 message is the temporary UE ID assigned when the base station configured the UE as a reader. The UE ID information includes the reader identifier assigned when assigning a task or configuring the UE as a reader, which uniquely identifies a UE as a reader. The UE reader identifier contains two parts of information, one part is information identifying the gNB, and the other part is information identifying the UE.

[0457] After receiving the MSG3 message from the UE, the base station determines, based on the cause value or UE identifier, that the UE is reporting the collected task information. It then establishes SRB1, activates AS security, and / or an SRB to carry the collected data. Alternatively, it establishes a DRB for reporting the collected data.

[0458] After receiving the MSG5 message from the UE, the base station determines the task information that the UE wants to report based on the UE identifier or task ID. At the same time, the base station identifies the routing and forwarding information of the collected data on the access network side based on the task ID, namely the GTP tunnel, XnAP connection information, NGAP connection information, or IP address.

[0459] Option 2: Second information reporting based on message 5 (MSG5 based indication).

[0460] When the data collected and / or stored by the RRC_IDLE / INACTIVE UE as a reader is larger than a certain threshold, such as mbyte, or when the task of collecting by the RRC_IDLE / INACTIVE UE as a reader has been completed, the RRC_IDLE / INACTIVE UE reader initializes the RRC connection establishment process. The optional MSG3 message (RRCSetupRequest) carries the cause value of the RRC connection establishment, which may be "MO-data".

[0461] The MSG5 (RRC Setup Complete) message carries an indication, a task ID, and / or a UE reader identifier. The indication indicates a request for IoT data collection and reporting for the purpose of establishing the RRC connection. The UE reader identifier is assigned when a task is assigned or when a UE is configured as a reader. It uniquely identifies a UE as a reader and consists of two parts: information identifying the gNB and information identifying the UE. The task ID is the task identifier assigned when the UE is assigned an IoT task.

[0462] After receiving the MSG5 message from the UE, the base station determines, based on the indication information, UE identifier, or task ID, that the UE intends to report the collected task information. It then establishes SRB1, activates AS security, and / or establishes an SRB to carry the collected data. Furthermore, based on the task ID, it identifies the routing and forwarding information for the collected data on the access network, such as the GTP tunnel, XnAP connection information, NGAP connection information, or IP address.

[0463] After receiving the MSG5 message from the UE, the base station determines the task information that the UE intends to report based on the indication information, UE identifier, or task ID. It then establishes a DRB for transmitting the collected data and, based on the task ID, identifies the routing and forwarding information for the collected data on the access network side, such as the GTP tunnel, XnAP connection information, NGAP connection information, or IP address.

[0464] Option 3: MDT-similar solution: MDT is a shortened form of Minimization of Drive-Test.

[0465] When the amount of data collected and / or stored by an RRC_IDLE / INACTIVE UE acting as a reader exceeds a certain threshold (e.g., mbyte), or when the RRC_IDLE / INACTIVE UE's task as a reader has completed, the RRC_IDLE / INACTIVE UE reader initiates the RRC connection establishment process. In the MSG5 message, the UE indicates that there is collected data available for reporting. The UE then issues RRC signaling requesting data reporting, and the UE reader reports the data.

[0466] Option 4: Collected data is routed and forwarded with addressing.

[0467] Method 1: Each base station has only one data collection task at a time. After receiving the collected data report, the base station performs data routing and addressing according to the current unique task configuration information.

[0468] Method 2: Each UE has only one data collection task at a time. After receiving the collected data report, the UE reports the collected data and the task ID to the base station. The base station performs data routing and addressing based on the task configuration information corresponding to the task ID.

[0469] Method 3: The tag carries the task ID when reporting data. After receiving the collected data report, the UE reader reports the collected data and the task ID to the base station. The base station performs data routing and addressing based on the task configuration information corresponding to the task ID.

[0470] The disclosed embodiment proposes RRC_IDLE / INCTIVE UE as a data reporting method for UE readers, which enables fast and low-cost deployment of passive IoT while achieving the goal of UE power saving.

[0471] In order to quickly deploy the passive Internet of Things and at low cost, a passive Internet of Things data collection method based on terminals as anchor points is proposed. However, how to enable the terminal to become the anchor point for passive Internet of Things data collection and how to route and forward the collected data are problems that need to be solved.

[0472] Referring to Figures 5A and 5B , a terminal reports its capability information, which includes its ability to serve as an anchor point to collect passive IoT data, i.e., to read passive IoT data as a reader. Optionally, the terminal may also indicate to a base station or core network (CN) whether it is willing to serve as a reader. This passive IoT data is a type of the aforementioned first information.

[0473] The terminal is in the RRC connected state and can report its terminal capabilities and / or user consent.

[0474] Option 1: The terminal reports its capabilities and / or user consent via AS layer messages. For example, the terminal capability reporting process is reported to the gNB.

[0475] Option 2: The terminal reports terminal capabilities and / or user consent to the core network (CN) via NAS signaling, such as during terminal registration. The gNB obtains terminal capabilities and / or user consent via the core network signaling to the gNB, such as during initial context establishment.

[0476] Option 3: User consent can be obtained without the terminal reporting. This consent can be provided as user subscription data, which can be sent to the gNB via the core network. For example, the base station obtains the terminal's capability information and user consent during the initial context establishment process.

[0477] The IoT server issues the task and generates a task ID and task-related parameters. For example, these parameters describe information such as the purpose of the task, the type of data and / or the target environment IoT device. Optionally, the IoT server also configures an IP address for the task, which is used as the data routing terminal node for the environmental IoT device to report data. Optionally, the task information also includes the area scope for issuing the task, and the task area scope can be a cell list (cell lsit) or a base station identification list. Optionally, the task information also includes the start time and / or end time of the task. The cell list and base station identification list can be used as a type of area information of the aforementioned configuration information terminal.

[0478] Optionally, the task information may include a correspondence between the task ID and the ambient device ID (ambient id) or the ID of some ambient IoT devices.

[0479] Optionally, it also includes instruction information for designating the terminal as a reader. Optionally, it also includes configuration information for the terminal as a reader.

[0480] The IoT server sends the generated task and related information to the core network (CN). Based on the task area information preconfigured by OAM or sent by the IoT server, the CN determines the target base station information and forwards the task to the corresponding base station. Optionally, the CN also indicates the identity of the target terminal to be the reader.

[0481] The base station saves the task information and IP address and determines the target cell list for the task. The base station selects a terminal that supports passive IoT data collection as the anchor point for passive IoT data collection and configures the terminal as the anchor point for passive IoT data collection. Optionally, a new SRB or DRB is configured for the terminal to collect and report passive IoT data.

[0482] At the same time, the base station forwards the task to the terminal. The base station also configures the terminal with the task ID, task information, cell information, and a new SRB or DRB for IoT data reporting.

[0483] The terminal saves the task ID and task information, and prepares to become a reader, such as sending cell information and trigger information, that is, preparing to send tasks.

[0484] Option 1: The task information or data request message sent by the terminal to the environmental IoT device includes a task ID, and / or data reporting type or category, and / or identification information of the target environmental IoT device or a target group of environmental IoT devices.

[0485] Option 2: The task information or data request message sent by the terminal to the environmental IoT device includes the data reporting type or category, and / or identification information of the target environmental IoT device or a group of target environmental IoT devices.

[0486] The terminal receives data reports from surrounding IoT devices and reports them to the base station via new SRBs or DRBs. If reporting via SRBs, the reported data can be included in a container in a newly defined RRC message, such as IoT Data Reporting.

[0487] As shown in FIG5A , option 1: the data reported by the environmental IoT device includes information such as the task ID. The base station matches the IP address according to the task ID and forwards the received data to the target IP address.

[0488] As shown in Figure 5B, option 2: The data reported by the environmental IoT device does not contain information such as the task ID, but contains the environmental IoT device ID information. The base station matches the task ID through the ID of the environmental IoT device or part of the ID of the environmental IoT device, and then matches the IP address based on the task ID, or directly matches the IP address, and then forwards the received data to the target IP address. Or:

[0489] Option a: The data reported by the environmental IoT device contains task ID information. The base station matches the GTP tunnel or NGAP signaling connection based on the task ID and forwards the data to the CN through the GTP tunnel or NGAP signaling connection.

[0490] Option b: The data reported by the environmental IoT device does not contain task ID information, but contains environmental IoT device ID information. The base station matches the task ID through the environmental IoT device ID or part of the information in the environmental IoT device ID, and then matches the GTP tunnel or NGAP signaling connection based on the task ID, or directly matches the GTP tunnel or NGAP signaling connection, and then forwards the received data to the CN through the GTP tunnel or NGAP signaling connection.

[0491] Based on option a or b, the CN matches the IP address based on the data received through the CTP tunnel or NGAP signaling and sends the data to the target node.

[0492] The embodiments of the present disclosure also provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., a terminal, an access network device, or a core network device) in any of the above methods.

[0493] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0494] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0495] Figure 6A is a schematic diagram of the terminal structure provided by an embodiment of the present disclosure. As shown in Figure 6A, the terminal includes: a sending module 601, which is configured to send a first message, wherein the first message is used for the terminal to request any message to enter the connected state or any message after entering the connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal. Optionally, the receiving module is used to execute the steps related to information reception performed by the terminal in any of the above communication methods, which will not be repeated here. Optionally, the terminal may also include one or more processing modules, which are used to execute the steps related to information determination performed by the terminal in any of the above communication methods, which will not be repeated here.

[0496] Figure 6B is a schematic diagram of the structure of the access network device provided by an embodiment of the present disclosure. As shown in Figure 6B, the access network device includes: a receiving module 602, which is configured to receive a first message from a terminal, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state, wherein the first message includes: first information; wherein the first information indicates that the terminal has second information to be sent; wherein the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal. Optionally, the transceiver module is used to execute the steps related to information reception performed by the terminal in any of the above communication methods, which are not repeated here. Optionally, the access network device also includes one or more processing modules. The processing module is used to execute the steps related to sending performed by the access network device in any of the above methods. The embodiment of the present disclosure provides a communication system, which includes at least a terminal and an access network device. The terminal is used to execute the communication method provided by any technical solution of the first aspect. The access network device is used to execute the communication method provided by any technical solution of the second aspect.

[0497] Figure 7A is a schematic diagram of the structure of a communication device 8100 provided in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device or a core network device), a terminal (e.g., a user device), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above communication methods. Communication device 8100 can be used to implement the communication methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0498] As shown in Figure 7A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 8101 is used to call instructions to enable the communication device 8100 to perform any of the above communication methods.

[0499] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0500] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0501] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0502] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0503] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0504] 7B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG7B , but the present disclosure is not limited thereto.

[0505] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above communication methods.

[0506] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0507] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0508] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0509] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above communication methods. Optionally, the program product is a computer program product.

[0510] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0511] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0512] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method, wherein: The method comprises: The terminal sends a first message, wherein the first message is used for the terminal to request to enter any message of the connected state or any message after entering the connected state; the first message includes: first information; the first information indicates that the terminal has second information to be sent; the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

2. The method according to claim 1, wherein: The first message includes at least one of the following: A request message for establishing a radio resource control (RRC) in an idle state; RRC recovery request message for inactive state; RRC connection establishment completion message for idle state; RRC connection recovery complete message for inactive state.

3. The method according to claim 1 or 2, wherein: The first information includes at least one of the following: A first reason, indicating that the terminal requests the second information to be sent; The second reason indicates that the terminal requests to establish only an RRC signaling connection; A third reason indicates that the terminal moves and initiates data; A first identifier, indicating that the terminal serves as an identifier of the first device reader; A task identifier, indicating a task for the first device to send the first information; The second identifier indicates the first device.

4. The method according to any one of claims 1 to 3, wherein: The terminal sending the first message includes: A preset event is detected and the first message is sent.

5. The method according to claim 4, wherein: The preset event includes at least one of the following: The terminal completes the task of collecting the second information; The cache amount of the second information reaches a first threshold; The current time reaches the reporting time configured for the first information; The cache duration of the second information is equal to or greater than the first duration; The remaining cache space of the terminal is less than a preset value; The terminal receives the delay-sensitive second information.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: Establish an RRC connection with the access network device; The second information is sent based on the RRC connection.

7. The method according to claim 6, wherein: The establishing of an RRC connection with the access network device comprises: Establishing an RRC signaling-only connection with the access device; Wherein, when the RRC signaling connection is established, a signaling radio bearer SRB1 is established with the terminal.

8. The method according to claim 6, wherein: The terminal is established with SRB1, SRB2 and / or data radio bearer DRB.

9. The method according to claim 6, wherein: The second information sent based on the RRC connection carries a task identifier added by the first device; or, The second information sent based on the RRC connection carries the task identifier added by the terminal.

10. A communication method, wherein: include: An access network device receives a first message from a terminal, wherein the first message is any message for the terminal to request entering a connected state or any message after entering a connected state; the first message includes: first information; the first information indicates second information to be sent by the terminal; the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

11. The method according to claim 10, wherein: The first message includes at least one of the following: A request message for establishing a radio resource control (RRC) in an idle state; RRC recovery request message for inactive state; RRC connection establishment completion message for idle state; RRC connection recovery complete message for inactive state.

12. The method according to claim 10 or 11, wherein: The first information includes at least one of the following: A first reason, indicating that the terminal requests the second information to be sent; The second reason indicates that the terminal requests to establish only an RRC signaling connection; A third reason indicates that the terminal moves and initiates data; A fourth reason is to instruct the terminal to report drive test data; A first identifier, indicating that the terminal serves as an identifier of the first device reader; A task identifier, indicating a task for the first device to send the first information; The second identifier indicates the first device.

13. The method according to any one of claims 10 to 12, wherein: The method further comprises: Establish an RRC connection with the terminal based on the first message.

14. The method according to claim 13, wherein: The method comprises: The first information sent based on the RRC connection is received.

15. The method according to claim 13, wherein: The RRC connection includes: only an RRC signaling connection.

16. The method according to claim 15, wherein: The method comprises: The RRC signaling-only connection is established with the terminal, and a signaling radio bearer SRB1 is configured for the terminal.

17. The method according to claim 14, wherein: The method further comprises: An SRB1, SRB2 and / or data radio bearer is established for the terminal.

18. The method according to any one of claims 10 to 17, wherein: The method further comprises: Sending the second information to a core network device; wherein the second information is sent by the core network device to the second device; or The second information is sent to the second device.

19. The method according to any one of claims 10 to 18, wherein: The second information includes one of the following: a task identifier added by the first device; The task identifier added by the terminal; and, Task identifier added by the access network device.

20. A terminal, wherein: include: The sending module is configured to send a first message, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state; the first message includes first information; the first information is used to indicate second information to be sent by the terminal; the second information is transmitted to the terminal by the first device based on the triggering of the first signal of the terminal.

21. An access network device, wherein: include: The receiving module is configured to receive a first message from a terminal, wherein the first message is any message for the terminal to request to enter a connected state or any message after entering a connected state; the first message includes first information; the first information is used to indicate second information to be sent by the terminal; and the second information is transmitted to the terminal by a first device based on the triggering of a first signal from the terminal.

22. A communication system comprising: A terminal, configured to implement the communication method according to any one of claims 1 to 9; Access network equipment, used to implement the communication method according to any one of claims 10 to 19.

23. A communication device, wherein: The communication device comprises: one or more processors; The processor is used to call instructions so that the communication device executes the communication method according to any one of claims 1 to 9 or claims 10 to 19.

24. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the communication method according to any one of claims 1 to 9 or claims 10 to 19.

Images