Paging-related method and apparatus in node used for wireless communication

Abstract

The present application discloses a paging-related method and apparatus in a node used for wireless communication. The method comprises: a communication node receiving a first message on a downlink, the first message comprising first core network information; sending a target message, the first message triggering the sending of the target message; and receiving a second message on the downlink, the target message being configured for waking up at least one device, and the second message indicating to stop sending the target message. This helps reduce unnecessary sending of a target message.

Description

A method and apparatus related to paging in a node used for wireless communication TECHNICAL FIELD

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, in particular to a paging method and apparatus. BACKGROUND

[0002] With the continuous development of wireless communication, the demand for low power consumption of wireless access equipment is getting higher and higher; in particular, the Internet of Things is getting more and more attention in the field of wireless communication, and the large number of Internet of Things devices makes the battery that needs to be manually replaced or charged lead to high maintenance cost, serious environmental problems and even safety hazards. The 3GPP(the 3rd Generation Partnership Project, 3rd Generation Partnership Project) Release19 established the "NR(New Radio, New Radio) Ambient Internet of Things(Ambient Internet of Things, A-IoT) Solution Research" research group(Study Item, SI), which aims to evaluate the deployment of ambient Internet of Things in 3GPP system, including paging mechanism and process design. SUMMARY

[0003] The inventor found through research that, after a message for waking up at least one device is triggered by a message including core network information, how to stop sending the message for waking up the device is a problem that needs to be solved.

[0004] To solve the above problems, the present application provides a solution. In the above problem description, although the present application gives a specific implementation for receiving the first message and the second message on the downlink, the present application can also be used in the scenario of receiving the first message on the non-downlink, and similar technical effects of receiving the first message and the second message on the downlink can be achieved. In the above problem description, although the present application gives a specific implementation for the first message including the first core network information, the present application can also be used in the scenario of the first message not including the first core network information, and similar technical effects of the first message including the first core network information can be achieved. Further, using a unified design scheme for different scenarios can also help to reduce hardware complexity and cost.

[0005] As an embodiment, the explanation of the terms in the present application refers to the definition of the specification protocol TS38 series of 3GPP.

[0006] It should be noted that, in the case of no conflict, the embodiments in any node of the present application and the features in the embodiments can be applied to any other node. The embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other without conflict.

[0007] The application discloses a method used in a first node for wireless communication, and has the characteristics that the method comprises the following steps:

[0008] receiving a first message on a downlink, wherein the first message comprises first core network information;

[0009] sending a target message; wherein the first message triggers the sending of the target message;

[0010] receiving a second message on the downlink;

[0011] wherein the target message is used to wake up at least one device, and the second message indicates to stop sending the target message.

[0012] In order to successfully wake up the device, the target message may need to be sent for multiple times. Unnecessary sending of the target message will cause waste of resources and increase the power consumption of the sender and the receiver of the target message. Therefore, it is necessary to design a mechanism to stop sending the message used to wake up the device. The above method solves the above problem by indicating, through the second message, to stop sending the target message.

[0013] The above method is beneficial to the control of the network side.

[0014] The above method is beneficial to avoiding waste of resources.

[0015] The above method is beneficial to reducing unnecessary sending of the target message.

[0016] The above method is beneficial to reducing the power consumption of the sender and the receiver of the target message.

[0017] According to one aspect of the application, the second message indicating to stop sending the target message comprises:

[0018] the first transmitter stops sending the target message when the number of times of sending the target message reaches Q1;

[0019] wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0020] How the second message indicates to stop sending the target message is a problem to be solved. The above method determines to stop sending the target message by indicating, through the second message, the maximum number of times of sending the target message.

[0021] The above method is beneficial to controlling the number of times of sending the target message.

[0022] The above method reduces the core network information interaction.

[0023] The above method is simple to implement.

[0024] According to an aspect of the present application, the second message indicating to stop sending the target message comprises:

[0025] stopping sending the target message at a first time;

[0026] wherein the first time is dependent on the second message; and the first message comprises the second message.

[0027] How the second message indicates to stop sending the target message is a problem to be solved. The above method solves the above problem by the first time dependent on the second message.

[0028] The above method is beneficial to control the time of the target message.

[0029] The above method reduces the core network information interaction.

[0030] The above method is simple to implement.

[0031] According to an aspect of the present application, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0032] How to determine the device that needs to be woken up is a problem to be solved. In the above method, the device that needs to be woken up is indicated by the core network information, thereby solving the above problem.

[0033] As an embodiment, the at least one device is the plurality of devices.

[0034] The above method avoids re-sending the target message and reduces implementation complexity.

[0035] As an embodiment, the at least one device is at least part of the plurality of devices.

[0036] The above method is beneficial to flexible setting of the target message.

[0037] According to an aspect of the present application, the second message comprises second core network information, the second core network information indicates at least one of the plurality of devices, and the second message does not belong to the first core network information.

[0038] How the second message indicates to stop sending the target message is a problem to be solved. The above solution solves the above problem by the second message comprising a core network information subsequent to the first core network information.

[0039] The above method is beneficial to dynamic control of the target message by the core network.

[0040] According to an aspect of the present application, the target message comprises one device group identifier and P1 device identifiers, P1 is a positive integer; the one device group identifier is associated with a plurality of devices, and the P1 device identifiers respectively indicate P1 devices; the at least one device is a device other than the P1 devices in the plurality of devices.

[0041] How to determine the devices that need to be woken up is a problem to be solved. The above method solves the above problem by the one device group identifier and the P1 device identifiers comprised in the target message.

[0042] The above method is beneficial to the device receiving the target message to determine whether to be woken up.

[0043] The above method reduces the core network information interaction.

[0044] According to an aspect of the present application, it comprises:

[0045] The first transmitter starts a target timer along with the target message.

[0046] The first transmitter re-sends the target message if no response message is received from at least part of the at least one device when the target timer expires.

[0047] Sending too many target messages will increase air interface resources and energy consumption; the sending of the traditional paging message depends on the pre-determined paging occasion, and considering that the traditional paging mechanism is not suitable for communication between the first node and the third node; how to control the sending of the target message is a problem to be solved. The above method introduces the target timer, which solves the above problem.

[0048] The above method is beneficial to avoid too frequent sending of the target message.

[0049] The above method is beneficial to save air interface resources.

[0050] The above method is beneficial to reduce the energy consumption of the first node and / or the third node.

[0051] According to an aspect of the present application, it comprises:

[0052] In response to the reception of the second message, if the target timer is running, stop the target timer.

[0053] According to an aspect of the present application, it comprises:

[0054] If the response message is received from all devices in the at least one device and the target timer is running, stop the target timer.

[0055] According to an aspect of the present application, there is provided a method comprising:

[0056] listening for a response message from the at least one device in response to the target message being transmitted;

[0057] wherein the response message indicates a device identity.

[0058] According to an aspect of the present application, there is provided a method comprising:

[0059] transmitting, by the first transmitter, a third message in response to ceasing to transmit the target message;

[0060] wherein the third message indicates a device that was unsuccessfully woken up.

[0061] The above method is advantageous in that the network can obtain information about devices that were not woken up.

[0062] The above method is advantageous in that the network can be optimized.

[0063] The present application discloses a method in a second node used for wireless communication, comprising:

[0064] transmitting a first message on a downlink, the first message comprising first core network information; wherein the first message triggers a recipient of the first message to transmit a target message; and transmitting a second message on the downlink;

[0065] wherein the target message is for waking up at least one device, and the second message instructs the recipient of the first message to cease transmitting the target message.

[0066] According to an aspect of the present application, the second message instructing the recipient of the first message to cease transmitting the target message comprises: when a number of times of transmission of the target message reaches Q1, the recipient of the first message ceases to transmit the target message; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0067] According to an aspect of the present application, the second message instructing the recipient of the first message to cease transmitting the target message comprises: at a first time, the recipient of the first message ceases to transmit the target message; wherein the first time depends on the second message; and the first message comprises the second message.

[0068] According to an aspect of the present application, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0069] According to an aspect of the present application, the second message comprises second core network information, the second core network information indicating at least one of the plurality of devices, the second message not belonging to the first core network information.

[0070] According to an aspect of the present application, the target message comprises one device group identifier and P1 device identifiers, P1 being a positive integer; the one device group identifier being associated with a plurality of devices, the P1 device identifiers respectively indicating P1 devices; the at least one device being a device other than the P1 devices among the plurality of devices.

[0071] According to an aspect of the present application, the receiver of the first message starts a target timer in response to the target message; when the target timer expires, the receiver of the first message re-sends the target message if no response message is received from at least part of the at least one device.

[0072] According to an aspect of the present application, the receiver of the first message stops the target timer in response to the second message being received.

[0073] According to an aspect of the present application, the receiver of the first message stops the target timer in response to the second message being received.

[0074] According to an aspect of the present application, the receiver of the first message listens for a response message from the at least one device in response to the target message being sent; wherein the response message indicates a device identifier.

[0075] According to an aspect of the present application, the method comprises:

[0076] receiving a third message;

[0077] wherein the receiver of the first message sends a third message in response to the receiver of the first message stopping sending the target message; the third message indicating a device that is not successfully woken up.

[0078] The present application discloses a method in a third node used for wireless communication, comprising:

[0079] receiving a target message; wherein the first message triggers sending of the target message; a sender of the target message receives the first message on a downlink, the first message comprising first core network information; the sender of the target message receives a second message on the downlink;

[0080] wherein the target message is for waking up at least one device, and the second message instructs the sender of the target message to stop sending the target message.

[0081] As an embodiment, the third node comprises one of the at least one device.

[0082] As an embodiment, the third node is one of the at least one device.

[0083] According to an aspect of the present application, the second message instructing the sender of the target message to stop sending the target message comprises: when the sending times of the target message reach Q1, the sender of the target message stops sending the target message; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0084] According to an aspect of the present application, the second message instructing the sender of the target message to stop sending the target message comprises: at a first time, the sender of the target message stops sending the target message; wherein the first time depends on the second message; and the first message comprises the second message.

[0085] According to an aspect of the present application, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0086] According to an aspect of the present application, the second message comprises second core network information, the second core network information indicating at least one of the plurality of devices, and the second message not belonging to the first core network information.

[0087] According to an aspect of the present application, the target message comprises one device group identifier and P1 device identifiers, the P1 being a positive integer; the one device group identifier being associated with a plurality of devices, and the P1 device identifiers respectively indicating P1 devices; and the at least one device being a device other than the P1 devices among the plurality of devices.

[0088] According to an aspect of the present application, the sender of the target message starts a target timer in response to the target message being received; and re-sends the target message when the target timer expires and no response message is received from at least some of the at least one device.

[0089] According to an aspect of the present application, the sender of the target message stops the target timer in response to the second message being received and the target timer being running.

[0090] According to an aspect of the present application, the sender of the target message stops the target timer in response to the second message being received and the target timer being running.

[0091] According to an aspect of the present application, a response message is sent in response to the target message being received; wherein the response message indicates a device identity of the third node.

[0092] According to an aspect of the present application, the sender of the target message sends a third message in response to the sender of the target message stopping sending the target message; wherein the third message indicates a device that is not successfully woken up.

[0093] The present application discloses a first node for wireless communication, comprising:

[0094] a first receiver configured to receive a first message on a downlink, the first message comprising first core network information;

[0095] a first transmitter configured to send a target message; wherein the first message triggers sending of the target message;

[0096] the first receiver configured to receive a second message on the downlink;

[0097] wherein the target message is for waking up at least one device, and the second message indicates to stop sending the target message.

[0098] The present application discloses a second node for wireless communication, comprising:

[0099] a second transmitter configured to send a first message on a downlink, the first message comprising first core network information; wherein the first message triggers a receiver of the first message to send a target message; and send a second message on the downlink;

[0100] The target message is for waking up at least one device, and the second message instructs the sender of the target message to stop sending the target message.

[0101] A third node for wireless communication is disclosed, comprising:

[0102] a third receiver configured to receive a target message, wherein a first message triggers sending of the target message, the sender of the target message receives the first message on a downlink, the first message comprises first core network information, and the sender of the target message receives a second message on the downlink;

[0103] The target message is for waking up at least one device, and the second message instructs the sender of the target message to stop sending the target message. BRIEF DESCRIPTION OF DRAWINGS

[0104] Other features, objects, and advantages of the application will become more apparent from the following detailed description when read in conjunction with the accompanying drawings:

[0105] FIG. 1 shows a flowchart of transmission of a first message, a target message, and a second message according to one embodiment of the present application;

[0106] FIG. 2 shows a schematic diagram of a network architecture according to one embodiment of the present application;

[0107] FIG. 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and control plane according to one embodiment of the present application;

[0108] FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application;

[0109] FIG. 5 shows a flowchart of wireless signal transmission according to one embodiment of the present application;

[0110] FIG. 6 shows a schematic diagram of the second message instructing the first node to stop sending the target message according to one embodiment of the present application;

[0111] FIG. 7 shows a schematic diagram of the second message instructing the first node to stop sending the target message according to another embodiment of the present application;

[0112] FIG. 8 shows a schematic diagram of the first core network information according to one embodiment of the present application;

[0113] FIG. 9 shows a schematic diagram of the second message according to one embodiment of the present application;

[0114] FIG. 10 shows a schematic diagram of the target message according to one embodiment of the present application;

[0115] Figure 11 shows a structural block diagram of a processing apparatus in a first node according to an embodiment of the present application;

[0116] Figure 12 shows a structural block diagram of a processing apparatus in a second node according to an embodiment of the present application;

[0117] Figure 13 shows a structural block diagram of a processing apparatus in a third node according to an embodiment of the present application;

[0118] Figure 14 shows a schematic diagram of an A-IoT logical system architecture according to an embodiment of the present application. DETAILED DESCRIPTION

[0119] The technical solutions of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily without conflict.

[0120] Embodiment 1

[0121] Embodiment 1 shows a flowchart of the transmission of a first message, a target message and a second message according to an embodiment of the present application, as shown in Figure 1. In Figure 1, each block represents a step, and in particular, the order of the blocks in the figure does not represent the time sequence between the steps represented.

[0122] In embodiment 1, the first node in the present application receives a first message on a downlink in step 101, the first message including first core network information; sends a target message in step 102; wherein the first message triggers the sending of the target message; receives a second message on the downlink in step 103; wherein the target message is used to wake up at least one device, and the second message indicates to stop sending the target message.

[0123] As an embodiment, the downlink is a link from a base station device to a user equipment.

[0124] As an embodiment, the downlink is a Uu interface.

[0125] As an embodiment, the downlink is an NR Uu interface.

[0126] As an embodiment, the downlink refers to Downlink (DL).

[0127] As an embodiment, the downlink refers to PDSCH (Physical Downlink Shared Channel).

[0128] As one embodiment, the downlink refers to a DL-SCH (Downlink Shared Channel).

[0129] As one embodiment, the sender of the first message is a maintenance base station of a serving cell of the first node.

[0130] As one embodiment, the sender of the first message is a core network device.

[0131] As one embodiment, the sender of the first message is a NAS device.

[0132] As one embodiment, the first message is received on a control plane.

[0133] As one embodiment, the first message is received on a user plane.

[0134] As one embodiment, the first message is received through an SRB (Signalling Radio Bearer).

[0135] As one embodiment, the first message is received through a DRB (Data Radio Bearer).

[0136] As one embodiment, the first message is a NAS message.

[0137] As one embodiment, the first message is the first core network information.

[0138] As one embodiment, the first message includes the first core network information and RRC information.

[0139] As one embodiment, the RRC (Radio Resource Control) information is generated at an RRC sublayer.

[0140] As one embodiment, the first message includes one RRC message, and the one RRC message includes the first core network information.

[0141] As one embodiment of the above embodiment, the one RRC message is an RRC container.

[0142] As one embodiment of the above embodiment, the one RRC message includes one RRC IE (Information Element), and the one RRC IE includes the first core network information.

[0143] As an embodiment, the first message comprises a device identity of each device in the at least one device.

[0144] As an embodiment, the first message comprises a device group identity, the device group identity being associated with a plurality of device identities.

[0145] As an embodiment, the plurality of device identities are device identities of each device in the at least one device.

[0146] As an embodiment, the plurality of device identities comprise device identities of each device in the at least one device.

[0147] As an embodiment, the core network (CN) refers to an A-IoT CN.

[0148] As an embodiment, the core network is a 5G core network.

[0149] As an embodiment, the core network is a 6G core network.

[0150] As an embodiment, the first core network information refers to information generated by a core network.

[0151] As an embodiment, the first core network information refers to information from a core network.

[0152] As an embodiment, the first core network information comprises a first paging identity.

[0153] The paging identity introduced by the above method is beneficial to the management of the paging process.

[0154] As an embodiment, the first paging identity is a logical identity.

[0155] As an embodiment, the first paging identity is a non-negative integer.

[0156] As an embodiment, the first paging identity is a positive integer.

[0157] As an embodiment, the first core network information comprises a plurality of paging identities, and the first paging identity is any one of the plurality of paging identities.

[0158] As an embodiment, any two paging identities in the plurality of paging identities are different.

[0159] As an embodiment, the target message is sent on a physical channel.

[0160] As one embodiment, the target message is transmitted on a PRDCH (Physical reader-to-device channel).

[0161] As one embodiment, the target message comprises a TB (Transport Block).

[0162] As one embodiment, the target message comprises a MAC PDU (Protocol Data Unit).

[0163] As one embodiment, the target message comprises a MAC subPDU.

[0164] As one embodiment, the target message comprises a MAC payload.

[0165] As one embodiment, the target message comprises at least one message of the first protocol layer.

[0166] As one embodiment, the target message comprises at least one IE of the first protocol layer.

[0167] As one embodiment, the target message comprises at least one field of the first protocol layer.

[0168] As one embodiment, the time-frequency resource occupied by the target message is predefined.

[0169] As one embodiment, the time-frequency resource occupied by the target message is preconfigured.

[0170] As one embodiment, the time-frequency resource occupied by the target message is configured by the first message.

[0171] As one embodiment, the time-frequency resource occupied by the target message is configured by the first core network information in the first message.

[0172] As one embodiment, the time-frequency resource occupied by the target message is configured by the RRC information in the first message.

[0173] As one embodiment, the time-frequency resource occupied by the target message is an occasion.

[0174] As one embodiment, the time-frequency resource occupied by the target message is a paging occasion.

[0175] As one embodiment, the time-frequency resource occupied by the target message is a WUS (Wake-Up Signal) occasion.

[0176] As an embodiment, the time-frequency resource occupied by the target message is determined by the first node.

[0177] As an embodiment, the determining by the first node refers to being configured by the first node.

[0178] As an embodiment, the determining by the first node refers to being selected by the first node.

[0179] As an embodiment, the determining by the first node refers to being determined by the first node by itself.

[0180] As an embodiment, the determining by the first node refers to being determined by the first node based on implementation.

[0181] As an embodiment, the determining by the first node refers to being determined by the first node randomly.

[0182] As an embodiment, the determining by the first node refers to being determined by the first node according to at least priority.

[0183] As an embodiment, the target message comprises a Wake-Up Signal (WUS).

[0184] As an embodiment, the Wake-Up Signal is generated at a physical layer.

[0185] As an embodiment, the Wake-Up Signal is generated at a protocol layer above the physical layer.

[0186] As an embodiment, the Wake-Up Signal is generated at a MAC sublayer.

[0187] As an embodiment, the Wake-Up Signal is generated at an RRC sublayer.

[0188] As an embodiment, the target message comprises a Paging Message.

[0189] As an embodiment, the Paging Message is generated at a physical layer.

[0190] As an embodiment, the Paging Message is generated at a protocol layer above the physical layer.

[0191] As an embodiment, the Paging Message is generated at the first protocol layer.

[0192] As an embodiment, the target message comprises a Short Message.

[0193] As an embodiment, the Short Message is generated at a physical layer.

[0194] As one embodiment, the short message occupies at least one bit.

[0195] As one embodiment, the target message comprises at least one of a paging message or a short message.

[0196] As one embodiment, the target message comprises a first field, the first field indicating that the target message comprises at least one of a paging message or a short message.

[0197] As one embodiment, the first field is a Short Message indicator.

[0198] As one embodiment, the short message comprises at least one of a system information change, an earthquake and tsunami warning system information, a commercial mobile alert service.

[0199] The above method is beneficial to further broadcast of information by carrying a short message in a target message, avoiding natural disasters or losses.

[0200] As one embodiment, the target message depends on the first core network information.

[0201] As one embodiment, the target message comprises at least part of the first core network information.

[0202] As one embodiment, the first core network information comprises the target message.

[0203] As one embodiment, at least one field in the target message is set depending on the first core network information.

[0204] As one embodiment, a value of at least one field in the target message depends on the first core network information.

[0205] As one embodiment, one field in the target message indicates a wake-up reason; the first core network information comprises the wake-up reason.

[0206] As one embodiment, one field in the target message indicates the at least one device; the first core network information indicates the at least one device.

[0207] As one embodiment, the target message comprises the first paging identifier.

[0208] As one embodiment, the target message comprises a target sequence and a target load, the target sequence indicating the target load.

[0209] The above method is simple to implement.

[0210] The above method has low complexity.

[0211] The above method is especially suitable for A-IoT wireless air interface.

[0212] As an embodiment, the target sequence is predefined.

[0213] As an embodiment, the target sequence is configurable.

[0214] As an embodiment, the target sequence indicates the target message.

[0215] As an embodiment, the target sequence is an OOK (On-Off Keying) signal.

[0216] As an embodiment, the target sequence is a bit string.

[0217] As an embodiment, the target sequence indicates the time domain location of the target load.

[0218] As an embodiment, the target sequence indicates the time domain location and the frequency domain location of the target load.

[0219] As an embodiment, the target sequence indicates the type of the target load.

[0220] As an embodiment, the time domain resource occupied by the target sequence is earlier than the time domain resource occupied by the target load.

[0221] As an embodiment, the last symbol occupied by the target sequence and the first symbol occupied by the target load are adjacent.

[0222] As an embodiment, between the last symbol occupied by the target sequence and the first symbol occupied by the target load, there are at least S1 symbols, and S1 is a positive integer.

[0223] As an embodiment, the S1 symbols are configurable.

[0224] As an embodiment, the S1 symbols are predefined.

[0225] As an embodiment, the at least S1 symbols are S2 symbols, and S2 is equal to the sum of S1 and S3; wherein S1 is predefined, and S3 is configurable.

[0226] As an embodiment, the target message is sent in response to the first message being received.

[0227] As an embodiment, the first message indicates that the first node sends the target message.

[0228] As one embodiment, the first message triggers the first node to start sending the target message.

[0229] As one embodiment, the first message includes the first core network information triggers the sending of the target message.

[0230] As one embodiment, the first core network information in the first message triggers the sending of the target message.

[0231] As one embodiment, the second message indicates to stop sending the target message for the at least one device.

[0232] As one embodiment, the second message indicates to stop sending the target message for the first paging identity.

[0233] As one embodiment, the second message indicates to stop sending the target message for the plurality of devices.

[0234] As one embodiment, the second message indicates to stop sending the target message for at least part of the plurality of devices.

[0235] As one embodiment, the second message indicates to stop sending the target message for at least part of the at least one device.

[0236] As one embodiment, the second message includes an RRC message.

[0237] As one embodiment, the second message is an RRC message.

[0238] As one embodiment, the second message includes a MAC CE.

[0239] As one embodiment, the second message is a MAC CE.

[0240] As one embodiment, the second message includes a DCI (Downlink Control Information).

[0241] As one embodiment, the second message is a DCI.

[0242] As one embodiment, the second message includes a core network message.

[0243] As one embodiment, the second message is a core network message.

[0244] As one embodiment, the second message includes a NAS message.

[0245] As one embodiment, the second message is a NAS message.

[0246] As one embodiment, the second message is used to determine to stop sending the target message.

[0247] As one embodiment, the second message is used to instruct to stop sending the target message.

[0248] As one embodiment, the second message explicitly instructs to stop sending the target message.

[0249] As one embodiment, the second message implicitly instructs to stop sending the target message.

[0250] As one embodiment, the second message triggers to stop sending the target message.

[0251] As one embodiment, a field in the second message instructs to stop sending the target message.

[0252] As one embodiment, in response to the second message being received, stop sending the target message.

[0253] As one embodiment, in response to the second message being received, reset the MAC entity; the resetting the MAC entity comprises: stop sending the target message.

[0254] As one subembodiment of the above embodiment, the above method reduces the processing complexity of the MAC entity.

[0255] As one subembodiment of the above embodiment, the second message is an RRCRelease message.

[0256] As one subembodiment of the above embodiment, the second message is an RRCReestablishment message.

[0257] As one embodiment, in response to the second message being received, perform a synchronous reconfiguration procedure; the performing the synchronous reconfiguration procedure comprises: stop sending the target message.

[0258] As one subembodiment of the above embodiment, the above method facilitates mobility management.

[0259] As one subembodiment of the above embodiment, the second message is an RRCReconfiguration message, the RRCReconfiguration message comprises a CellGroupConfig, the CellGroupConfig comprises a spCellConfig carrying reconfigurationWithSync.

[0260] As one embodiment, the meaning of the stop comprises pause.

[0261] As one embodiment, the meaning of the stop comprises no more.

[0262] As one embodiment, the meaning of the stop comprises cancel.

[0263] As one embodiment, the meaning of the stop comprises end.

[0264] As one embodiment, the meaning of the stop comprises terminate.

[0265] As one embodiment, the stop sending the target message comprises at least one of the following actions:

[0266] - release time-frequency resources on the first interface for the target message;

[0267] - stop listening to the response message on the first interface;

[0268] - stop the target timer;

[0269] - stop the first timer;

[0270] - send the third message;

[0271] - release cache for the target message;

[0272] - release storage information for the target message.

[0273] As one embodiment, the at least one device is one device.

[0274] As one embodiment, the at least one device is one or more devices.

[0275] As one embodiment, the at least one device is more than one device.

[0276] As one embodiment, the at least one device does not belong to any device group.

[0277] As one embodiment, the at least one device belongs to the same device group.

[0278] As one embodiment, the at least one device belongs to more than one device group.

[0279] As one embodiment, the at least one device is associated to the same device group identifier.

[0280] As one embodiment, the at least one device is associated to more than one device group identifier.

[0281] As a sub-example of the above embodiment, each of the at least one device is associated to only one of the plurality of device group identities.

[0282] As a sub-example of the above embodiment, each of the at least one device is associated to one or more of the plurality of device group identities.

[0283] As an example, the device is an access device.

[0284] As an example, the access device is a low-power device.

[0285] As an example, the access device is a low-function device.

[0286] As an example, the access device is passive.

[0287] As an example, the access device is RF-charged.

[0288] As an example, the access device is an IoT device.

[0289] As an example, the access device is an A-IoT device.

[0290] As an example, the device is a network device.

[0291] As an example, the network device is a base station device.

[0292] As an example, the network device is a TRP.

[0293] As an example, the network device is a DU.

[0294] As an example, the network device is a CU.

[0295] As an example, the wake-up comprises paging.

[0296] As an example, the wake-up comprises seeking.

[0297] As an example, the wake-up comprises activating.

[0298] As an example, the wake-up comprises searching.

[0299] As an example, the wake-up comprises indicating.

[0300] As an example, the wake-up comprises triggering.

[0301] As one embodiment, the target message is for triggering a random access of the at least one device.

[0302] As one embodiment, the target message is for triggering a response message of the at least one device.

[0303] As one embodiment, the target message indicates the at least one device.

[0304] As one embodiment, the target message indicates a device identity of each device of the at least one device.

[0305] As one embodiment, the target message indicates a device group identity to which the at least one device belongs.

[0306] As one embodiment, the device identity is a logical identity.

[0307] As one embodiment, the device identity is a physical identity.

[0308] As one embodiment, the device identity is a non-negative integer.

[0309] As one embodiment, the device identity is a positive integer.

[0310] As one embodiment, the device identity is a bit string.

[0311] As one embodiment, the device identity is a random number.

[0312] As one embodiment, the device identity is configured by a network.

[0313] As one embodiment, the device identity is allocated by a core network.

[0314] As one embodiment, the device identity is allocated by NAS.

[0315] As one embodiment, the device identity is unique within one area.

[0316] As one embodiment, the one area relies on a PCI (physical cell identity).

[0317] As one embodiment, the one area relies on a location coordinate.

[0318] As one embodiment, the one area relies on a beam.

[0319] As one embodiment, the one area relies on a reference signal.

[0320] Embodiment 2

[0321] Embodiment 2 illustrates a diagram of a network architecture according to one embodiment of the application, as shown in FIG. 2. FIG. 2 illustrates a network architecture 200. The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or the network architecture 200 is a 5G+ network architecture, or the network architecture 200 is a 6G network architecture, or the network architecture 200 is a network architecture of future continued evolution of 3GPP; the network architecture 200 can be referred to as a 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 can be referred to as a 6GS (6G System); the network architecture 200 includes a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a core network 210, a HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and at least one of an Internet service 230. The network architecture 200 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application are amenable to use with networked or other cellular networked environments providing circuit-switched services. The RAN includes a node 203 and other nodes 204. The node 203 provides user and control plane protocol terminations toward the UE 201. The node 203 can be connected to the other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 can also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (Transmit Receive Point), or some other suitable terminology. The core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or the core network 210 is a 6GC; the node 203 provides an access point to the core network 210 for the UE 201.Examples of a UE 201 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a non-tethered base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, a flying vehicle, a narrowband internet of things device, a machine type communication device, a land vehicle, a car, a wearable device, or any other similar functional device. Those skilled in the art will also The node 203 is connected by an S1 / NG interface to the core network 210. The core network 210 includes a MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, a S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Date Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that handles signaling between the UE 201 and the core network 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transferred through the S-GW / UPF 212, which itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW / UPF 213 is connected to the Internet services 230. The Internet services 230 include operator corresponding Internet protocol services, which can specifically include the Internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet switched streaming service.

[0322] As one embodiment, the UE 201 corresponds to the first node in the present application, and the node 203 is the second node in the present application.

[0323] As one subembodiment of the above embodiment, the UE 201 is a user equipment, and the node 203 is a base station device.

[0324] As one subembodiment of the above embodiment, the UE 201 is a user equipment, and the node 203 is a core network device.

[0325] As one embodiment, the UE 201 corresponds to the first node in the present application, the node 203 is the second node in the present application, and the UE 241 corresponds to the third node in the present application.

[0326] As one subembodiment of the above embodiment, the node 203 is a base station device.

[0327] As one subembodiment of the above embodiment, the node 203 is a core network device.

[0328] As one subembodiment of the above embodiment, the node 203 supports A-IoT.

[0329] As one subembodiment of the above embodiment, the node 203 supports A-IoT RAN node function.

[0330] As one subembodiment of the above embodiment, the UE 201 is a user equipment.

[0331] As one subembodiment of the above embodiment, the UE 201 is a reader device.

[0332] As one subembodiment of the above embodiment, the UE 201 supports Common reader function.

[0333] As one subembodiment of the above embodiment, the UE 201 supports A-IoT.

[0334] As one subembodiment of the above embodiment, the UE 201 is an A-IoT-enabled UE.

[0335] As one subembodiment of the above embodiment, the UE 241 is an A-IoT device.

[0336] As one embodiment, the reader device is a reader.

[0337] As one embodiment, the reader device is an A-IoT reader.

[0338] As one embodiment, the reader device is a UE.

[0339] As one embodiment, the reading device is a module.

[0340] As one embodiment, the reading device is a terminal.

[0341] Embodiment 3

[0342] Figure 3 is a diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3 shows three layers for the radio protocol architecture for the control plane 300: Layer 1, Layer 2, and Layer 3. Layer 1 (LI layer) is the lowest layer and implements various PHY (Physical layer) signal processing functions. The LI layer will be referred to as the PHY 301 herein. Layer 2 (L2 layer) 305 is above the PHY 301 and includes a MAC (Medium Access Control) sublayer 302, a RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security functions, such as ciphering of the data packets, and header compression. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling to configure the lower layers. The radio protocol architecture for the user plane 350 includes Layer 1 (LI layer) and Layer 2 (L2 layer), which are substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support diverse service

[0343] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the first node in the present application.

[0344] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the second node in the present application.

[0345] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the third node in the present application.

[0346] As one embodiment, the wireless protocol architecture of the third node comprises a user plane and a control plane.

[0347] As one embodiment, the wireless protocol architecture of the third node does not comprise at least one of the user plane and the control plane.

[0348] As one embodiment, the wireless protocol architecture of the third node comprises at least layer 1.

[0349] As one embodiment, the wireless protocol architecture of the third node comprises at least layer 1 and layer 2, and the layer 2 comprises at least a MAC sublayer.

[0350] As one embodiment, the layer 2 of the wireless protocol architecture of the third node comprises at least one of an RRC sublayer or an SDAP sublayer or a PDCP sublayer or an RLC sublayer, and the layer 2 of the wireless protocol architecture of the first node does not comprise at least one of the RRC sublayer or the SDAP sublayer or the PDCP sublayer or the RLC sublayer; the RRC sublayer or the SDAP sublayer or the PDCP sublayer or the RLC sublayer refer to embodiment 3, which is not repeated here.

[0351] As one embodiment, the layer 2 of the wireless protocol architecture of the third node does not comprise any one of the RRC sublayer or the SDAP sublayer or the PDCP sublayer or the RLC sublayer.

[0352] As one embodiment, the first message in the present application is generated at the RRC 306.

[0353] As one embodiment, the first message in the present application is generated at a first protocol layer.

[0354] As one embodiment, the second message in the present application is generated at a first protocol layer.

[0355] As one embodiment, the second message in the present application is generated at the RRC 306.

[0356] As one embodiment, the second message in the present application is generated at the MAC 302 or the MAC 352.

[0357] As one embodiment, the second message in the present application is generated at the PHY 301 or PHY 351.

[0358] As one embodiment, at least part of the target message in the present application is generated at a first protocol layer.

[0359] As one embodiment, at least part of the target message in the present application is generated at the RRC 306.

[0360] As one embodiment, at least part of the target message in the present application is generated at the MAC 302 or MAC 352.

[0361] As one embodiment, at least part of the target message in the present application is generated at the PHY 301 or PHY 351.

[0362] As one embodiment, the third message in the present application is generated at a first protocol layer.

[0363] As one embodiment, the third message in the present application is generated at the RRC 306.

[0364] As one embodiment, the third message in the present application is generated at the MAC 302 or MAC 352.

[0365] As one embodiment, the third message in the present application is generated at the PHY 301 or PHY 351.

[0366] As one embodiment, at least part of the response message in the present application is generated at a first protocol layer.

[0367] As one embodiment, at least part of the response message in the present application is generated at the RRC 306.

[0368] As one embodiment, at least part of the response message in the present application is generated at the MAC 302 or MAC 352.

[0369] As one embodiment, at least part of the response message in the present application is generated at the PHY 301 or PHY 351.

[0370] As one embodiment, the first protocol layer is a protocol layer above the RRC 306.

[0371] As one embodiment, the first protocol layer is a protocol layer above the SDAP 356.

[0372] As one embodiment, the first protocol layer is an application layer (not shown).

[0373] As an embodiment, the first protocol layer is a NAS layer (not shown).

[0374] Embodiment 4

[0375] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0376] The first communication device 450 comprises a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and antennas 452.

[0377] The second communication device 410 comprises a controller / processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418 and antennas 420.

[0378] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations for the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets, and signaling to the first communication device 450. The transmit processor 416 and the multiple antenna transmit processor 471 implement various signal processing functions for the LI layer (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of coded bits to modulation symbols based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multiple antenna transmit processor 471 performs digital spatial pre-coding of the coded and modulated symbols, including codebook-based and non-codebook-based pre-coding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps to each spatial stream to the subcarriers, multiplexes with reference signals (e.g., pilots) in the time and / or frequency domain, and then performs an inverse fast Fourier transform (IFFT) to generate a time-domain multicarrier symbol stream for the physical channel. The multiple antenna transmit processor 471 then performs transmit analog pre-coding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 into a radio frequency stream, and then provides the radio frequency stream to the corresponding antenna 420.

[0379] In transmissions from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and provides the recovered information at baseband as a stream of symbols to a receive processor 456. The receive processor 456 and a multiple access receiver processor 458 implement various signal processing functions of the Ll layer. The multiple access receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multiple access symbol streams from the receivers 454. The receive processor 456 converts the baseband multiple access symbol streams from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals are demultiplexed from the received symbol streams, with the reference signals to be used for channel estimation and the data signals to be recovered after multiple access detection in the multiple access receiver processor 458 for any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered by the receive processor 456 and used to generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to a controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In transmissions from the second communication device 410 to the first communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals can also be provided to the L3 for L3 processing.

[0380] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations, implements L2 layer functionality for the user plane and control plane. The controller / processor 459 is also responsible for error detection, retransmission of lost packets, and signaling to the second communication device 410. A transmit processor 468 performs modulation mapping, channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, and then the transmit processor 468 modulates the resulting spatial streams into multi-carrier / single-carrier symbol streams, which are then provided to different antennas 452 via transmitters 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency signal, and then provides the radio frequency signal to the antenna 452.

[0381] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receive functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its respective antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functionality of the L1 layer. A controller / processor 475 implements the functionality of the L2 layer. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer data packets from the controller / processor 475 can be provided to a core network.

[0382] The third communication device 480 comprises an antenna (Antenna) 481, energy related blocks 484, processing related blocks 488. The third communication device 480 can also comprise a matching network (Matching network) 482, which is used to match the impedance between the antenna 481 and other components, including a radio frequency (RF) energy harvester (energy harvester) 483 and reception related blocks 489. The third communication device 480 can also comprise an energy harvester, which can be a RF energy harvester 483 or a non-RF energy harvester 487. The RF energy harvester 483 can comprise a rectifier to perform RF signal (AC) to DC conversion. The RF energy harvester 483 and the receiver / transmitter can share the antenna 481, or they can use separate antennas. The energy related blocks 484 can comprise a power management unit (PMU) 485, which is responsible for storing energy from the energy harvester to an energy storage 486, and providing power to active component blocks that need power supply. The energy related blocks 484 can also comprise an energy storage (Energy storage) 486, which stores energy collected from the energy harvester, and the energy storage 486 can be a capacitor. The processing related blocks 488 can comprise BB (Base Band) logic 490, memory 495 and clock generator 496; the BB logic 490 can comprise a decoder 491, a controller 492 and an encoder 493; the memory 495 can comprise two types, one is a non-volatile memory (NVM), such as an EEPROM, which is used to permanently store the device ID; one is a register, which is used to temporarily save information that is only temporarily needed for operation when the energy in the energy storage 486 is available; the clock generator 496 provides the required clock signal. The processing related blocks 488 can also comprise reception related blocks 489 and transmission related blocks 494, and for different A-IoT devices, the reception related blocks 489 and the transmission related blocks 494 can comprise different blocks.The receiving related module 489 can employ a radio frequency envelope detector receiver (RF envelope detector receiver) or an intermediate frequency envelope detector receiver (IF envelope detector receiver) or employ a zero intermediate frequency (Zero IF, ZIF) receiver. The receiving related module 489 can include an RF BPF, a radio frequency envelope detector (RF envelope detector, RF-ED), a BB LPF and a comparator. Alternatively, the receiving related module 489 can include an RF BPF, an LNA (Low-noise amplifier), a radio frequency envelope detector, a BB amplifier, a BB LPF and a comparator / N-bit ADC. Alternatively, the receiving related module 489 can include an RF BPF, an LNA, a radio frequency envelope detector, a BB amplifier, a BB LPF, a comparator / N-bit ADC. Alternatively, the receiving related module 489 can include an RF BPF, an LNA, a mixer, an intermediate frequency amplifier (IF amplifier), an intermediate frequency filter (IF filter), an intermediate frequency envelope detector (IF envelope detector, IF-ED), a BB amplifier, a BB LPF, a comparator / N-bit ADC. Alternatively, the receiving related module 489 can include an RF BPF, an LNA, a mixer, a BB amplifier, a BB LPF, a comparator / N-bit ADC. The transmitting related module 494 can include a backscatter modulator. Alternatively, the transmitting related module 494 can include a large frequency shifter (e.g., tens of megahertz), a backscatter modulator, a reflection amplifier. Alternatively, the transmitting related module 494 can include a Tx modulator, a digital to analog converter (DAC), a low pass filter, a mixer, a LO (Local oscillator) / FLL ( / PLL) and a power amplifier (PA). Alternatively, the transmitting related module 494 can include a Tx modulator, a digital to analog converter, a low pass filter, a mixer, a LO / FLL ( / PLL) and a power amplifier. Alternatively, the transmitting related module 494 can include a Tx modulator, a digital to analog converter, a low pass filter, a mixer, a LO / FLL ( / PLL) and a power amplifier. It is particularly stated that the structure of the A-IoT device in the present example does not limit the specific implementation form of the A-IoT in the present application.Specifically, according to different functions and actual application scenarios of the A-IoT device, the A-IoT device can adopt the structure of the A-IoT device in the present example, can include only part of the modules in the structure of the A-IoT device in the present example, and can further include other modules not shown in the accompanying drawing 4.

[0383] As one embodiment, the first communication device 450 comprises at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the first communication device 450 at least to receive a first message on a downlink, the first message comprising first core network information; transmit a target message; wherein the first message triggers transmission of the target message; receive a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing to stop transmitting the target message.

[0384] As one embodiment, the first communication device 450 comprises a memory storing a program of computer readable instructions which, when executed by at least one processor, causes actions comprising receiving a first message on a downlink, the first message comprising first core network information; transmitting a target message; wherein the first message triggers transmission of the target message; receiving a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing to stop transmitting the target message.

[0385] As one embodiment, the second communication device 410 comprises at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the second communication device 410 at least to transmit a first message on a downlink, the first message comprising first core network information; wherein the first message triggers a receiver of the first message to transmit a target message; transmit a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing the receiver of the first message to stop transmitting the target message.

[0386] As one embodiment, the second communication device 410 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, results in actions comprising: sending a first message on a downlink, the first message comprising first core network information; wherein the first message triggers a recipient of the first message to send a target message; sending a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing the recipient of the first message to stop sending the target message.

[0387] As one embodiment, the third communication device 480 comprises: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, at least: receive a target message; wherein a first message triggers sending of the target message; a sender of the target message receives the first message on a downlink, the first message comprising first core network information; the sender of the target message receives a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing the sender of the target message to stop sending the target message.

[0388] As one embodiment, the third communication device 480 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, results in actions comprising: receiving a target message; wherein a first message triggers sending of the target message; a sender of the target message receives the first message on a downlink, the first message comprising first core network information; the sender of the target message receives a second message on a downlink; wherein the target message is for waking up at least one device, the second message instructing the sender of the target message to stop sending the target message.

[0389] As one embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, the controller / processor 459 is configured to receive the first message.

[0390] As one embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, the controller / processor 475 is configured to send the first message.

[0391] As one embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, the controller / processor 459 is configured to receive the second message.

[0392] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, the controller / processor 475 is configured to transmit the second message.

[0393] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, the controller / processor 459 is configured to transmit the third message.

[0394] As an embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, the controller / processor 475 is configured to receive the third message.

[0395] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, the controller / processor 459 is configured to transmit the target message.

[0396] As an embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, the controller / processor 475 is configured to receive the target message.

[0397] As an embodiment, at least one of the antenna 481, the matching network 482, the receive correlation module 489, the decoder 491, the controller 492 is configured to receive the target message.

[0398] As an embodiment, the first communication device 450 corresponds to a first node in the present application.

[0399] As an embodiment, the first node in the present application comprises the first communication device 450.

[0400] As an embodiment, the second communication device 410 corresponds to a second node in the present application.

[0401] As an embodiment, the second node in the present application comprises the second communication device 410.

[0402] As an embodiment, the third communication device 480 corresponds to a third node in the present application.

[0403] As an embodiment, the third node in the present application comprises the third communication device 480.

[0404] As an embodiment, the first communication device 450 is a user equipment.

[0405] As an embodiment, the first communication device 450 is a reading device.

[0406] As an embodiment, the first communication device 450 is a relay device.

[0407] As an embodiment, the second communication device 410 is a base station device.

[0408] As an embodiment, the second communication device 410 is a core network device.

[0409] As an embodiment, the second communication device 410 is a relay device.

[0410] As an embodiment, the third communication device 480 is an IoT device.

[0411] As an embodiment, the third communication device 480 is an A-IoT device.

[0412] Embodiment 5

[0413] Embodiment 5 illustrates a flow chart of wireless signal transmission according to an embodiment of the present application, as shown in FIG. 5. It is particularly stated that the sequence in this example does not limit the sequence of signal transmission and implementation in the present application.

[0414] For the first node U01, in step S5101, a first message is received on a downlink, the first message comprising first core network information; in step S5102, a target message is sent; wherein the first message triggers sending of the target message; in step S5103, a target timer is started along with the target message; in step S5104, in response to the target message being sent, a response message from the at least one device is listened for; wherein the response message indicates a device identity; in step S5105, the target timer expires; in step S5106, the target message is sent; in step S5107, a second message is received on a downlink; in step S5108, sending of the target message is stopped; in step S5109, the target timer is stopped; in step S5110, in response to sending of the target message being stopped, a third message is sent; wherein the third message indicates a device that was not successfully woken up.

[0415] For the second node N02, in step S5201, the first message is sent; in step S5202, the second message is sent; in step S5203, the third message is received.

[0416] For the third node N03, in step S5301, the target message is received; in step S5302, in response to the target message being received, a response message is sent; wherein the response message indicates a device identity of the third node N03; in step S5303, the target message is received.

[0417] In embodiment 5, the target message is for waking up at least one device, and the second message indicates to stop sending the target message.

[0418] As an embodiment, the first node U01 is a user equipment, the second node N02 comprises at least one of a base station device or a core network device, and the third node N03 is a base station device.

[0419] As a sub-embodiment of the above embodiment, the above method is applicable to network energy saving.

[0420] As a sub-embodiment of the above embodiment, the third node N03 is the second node N02.

[0421] As a sub-embodiment of the above embodiment, the third node N03 is not the second node N02.

[0422] As a sub-embodiment of the above embodiment, the third node N03 is a serving node of the first node U01.

[0423] As a sub-embodiment of the above embodiment, the third node N03 is not a serving node of the first node U01.

[0424] As a sub-embodiment of the above embodiment, the serving node is a base station device.

[0425] As a sub-embodiment of the above embodiment, the serving node is part of a base station device.

[0426] As a sub-embodiment of the above embodiment, the serving node is a TRP (Transmitter Receiver Point).

[0427] As a sub-embodiment of the above embodiment, the serving node is a CU (Centralized Unit).

[0428] As a sub-embodiment of the above embodiment, the serving node is a DU (Distributed Unit).

[0429] As a sub-embodiment of the above-mentioned embodiment, the second node N02 is a serving node of the first node U01.

[0430] As an embodiment, the first node U01 is a reading device, the third node N03 is an A-IoT device, and the second node N02 comprises at least one of a base station device or a core network device.

[0431] As a sub-embodiment of the above-mentioned embodiment, the third node comprises one of the at least one device.

[0432] As a sub-embodiment of the above-mentioned embodiment, the third node is one of the at least one device.

[0433] As a sub-embodiment of the above-mentioned embodiment, the second node N02 comprises a base station device.

[0434] As a sub-embodiment of the above-mentioned embodiment, the second node N02 comprises a core network device.

[0435] As a sub-embodiment of the above-mentioned embodiment, the second node N02 comprises a base station device and a core network device.

[0436] As an auxiliary embodiment of the above-mentioned sub-embodiment, the one core network device in the second node N02 sends the first message to the one base station device in the second node N02; the one base station device in the second node N02 sends the first message to the first node U01.

[0437] As an auxiliary embodiment of the above-mentioned sub-embodiment, the one core network device in the second node N02 sends a core network message to the one base station device in the second node N02; the one base station device in the second node N02 sends the first message to the first node U01 according to the one core network message, the one core network message comprising the first core network information.

[0438] As an auxiliary embodiment of the above-mentioned sub-embodiment, the one core network message comprises an Inventory request.

[0439] As an auxiliary embodiment of the above-mentioned sub-embodiment, the name of the one core network message comprises Inventory request.

[0440] As an auxiliary embodiment of the above-mentioned sub-embodiment, the one core network message is for Inventory.

[0441] As one embodiment, the target message in the step S5102 is the first target message sent after the first node U01 receives the first message.

[0442] As one embodiment, the target message in the step S5102 is any target message sent after the first node U01 receives the first message.

[0443] As one embodiment, the dashed box F5.1 is optional.

[0444] As one embodiment, the dashed box F5.1 is not present.

[0445] As one embodiment, the dashed box F5.1 is present.

[0446] As one embodiment, the listening on the first interface for the response message from the at least one device.

[0447] As one embodiment, the listening comprises detecting.

[0448] As one embodiment, the listening comprises receiving.

[0449] As one embodiment, the listening comprises decoding.

[0450] As one embodiment, the response message comprises physical layer information and information of the first protocol layer.

[0451] As one embodiment, the response message is physical layer information.

[0452] As one embodiment, the physical layer information is a physical layer signal.

[0453] As one embodiment, the physical layer information is physical layer signaling.

[0454] As one embodiment, the response message is a system message.

[0455] As one embodiment, the response message is SIB1.

[0456] As one embodiment, the response message is a reference signal.

[0457] As one embodiment, the response message is SSB.

[0458] As one embodiment, the response message is CSI-RS.

[0459] As one embodiment, the response message is Preamble.

[0460] As one embodiment, the response message is a Preamble of CFRA (Contention Free Random Access).

[0461] As one embodiment, the response message is a signaling of a MAC sublayer.

[0462] As one embodiment, the response message is a MAC CE.

[0463] As one embodiment, the response message is a MAC subPDU.

[0464] As one embodiment, the response message is a MAC payload.

[0465] As one embodiment, the response message is a message of the first protocol layer.

[0466] As one embodiment, the response message is a core network message.

[0467] As one embodiment, the response message from one device implicitly indicates a device identity of the one device.

[0468] As one embodiment, the response message from one device explicitly indicates a device identity of the one device.

[0469] As one embodiment, the response message from one device carries a device identity of the one device.

[0470] As one embodiment, the response message from one device is associated to a device identity of the one device.

[0471] As one embodiment, the response message from one device comprises a device identity of the one device.

[0472] As one embodiment, the response message from one device indicates a PCI, the device identity of the one device comprising the PCI.

[0473] As one embodiment, the listening for the response message from the at least one device relies on the target message comprising a second field.

[0474] As one embodiment, the listening for the response message from the at least one device relying on the target message comprising a second field comprises: the listening for the response message from the at least one device is performed only if the target message comprises the second field.

[0475] As one embodiment, said listening for a response message from said at least one device in dependence of said target message including a second field comprises: said listening for a response message from said at least one device is not performed under an assumption that said target message does not include said second field.

[0476] As one embodiment, said second field indicates that said at least one device sends said response message.

[0477] As one embodiment, said second field indicates that said at least one device should or shall or need send said response message.

[0478] As one embodiment, said second field indicates that said target message is for Command.

[0479] As one embodiment, said second field indicates a wake-up reason; said wake-up reason is a first candidate reason or a second candidate reason; said first candidate reason includes Command; said second candidate reason includes Inventory.

[0480] As one embodiment, said second field is for said at least one of said at least one device.

[0481] As one embodiment, said target message includes at least one said second field; said at least one of said at least one device is one of said at least one device.

[0482] As one embodiment, said target message includes at least one said second field; said at least one of said at least one device is a part of said at least one device.

[0483] As one embodiment, said target message includes only one said second field; said at least one of said at least one device is said at least one device.

[0484] As one embodiment, dashed box F5.2 is optional.

[0485] As one embodiment, said dashed box F5.2 is not present.

[0486] As one embodiment, said dashed box F5.2 is present.

[0487] As one embodiment, if said target timer expires and no response message is received from at least a part of said at least one device, said target message is re-sent.

[0488] As an embodiment, if the target timer expires and no response message is received from at least part of the at least one device and the number of times of sending the target message does not reach the Q1, the target message is re-sent.

[0489] As an embodiment, if the target timer expires and no response message is received from at least part of the at least one device and the current time is earlier than the first time, the target message is re-sent.

[0490] As an embodiment, if the target timer expires and no response message is received from at least part of the at least one device and the first timer is running, the target message is re-sent.

[0491] As an embodiment, the re-sent target message is the same as the last target message.

[0492] As an embodiment, the re-sent target message is different from the last target message.

[0493] As an embodiment, the re-sent target message is the same as at least part of the last target message.

[0494] As an embodiment, the re-sent target message includes at least part of the first core network information.

[0495] As an embodiment, the re-sent target message includes the first paging identity.

[0496] As an embodiment, the re-sent target message includes a device group identity of a device group to which the at least part of the at least one device is associated.

[0497] As an embodiment, the re-sent target message includes a device identity of the at least part of the at least one device.

[0498] As an embodiment, the re-sent target message includes one device group identity and device identities of devices other than the at least part of the at least one device in the plurality of devices; the one device group identity is associated with the plurality of devices.

[0499] As an embodiment, the dashed box F5.3 is optional.

[0500] As an embodiment, the dashed box F5.3 does not exist.

[0501] As an embodiment, the dashed box F5.3 exists.

[0502] As one embodiment, the not being successfully woken up refers to a wake-up failure.

[0503] As one embodiment, the not being successfully woken up comprises not successfully completing a random access procedure.

[0504] As one embodiment, the not being successfully woken up comprises not successfully completing a data transmission procedure.

[0505] As one embodiment, the not being successfully woken up comprises not receiving a corresponding response message.

[0506] As one embodiment, the third message is a NAS message.

[0507] As one embodiment, the third message is a core network message.

[0508] As one embodiment, the third message is a message of the first protocol layer.

[0509] As one embodiment, the third message comprises an Inventory Report.

[0510] As one embodiment, the name of the third message comprises Inventory and Report.

[0511] As one embodiment, the third message is an RRC message.

[0512] As one embodiment, the third message is an RRC container.

[0513] As one embodiment, the third message is at least one RRC IE.

[0514] As one embodiment, the third message is at least one RRC field.

[0515] As one embodiment, the third message is a MAC CE.

[0516] As one embodiment, the third message is a MAC PDU.

[0517] As one embodiment, the third message is a MAC subPDU.

[0518] As one embodiment, the third message comprises a device identity of the device not being successfully woken up.

[0519] As one embodiment, the third message comprises the first paging identity.

[0520] As one embodiment, the third message indicates, for the device that is not successfully woken up, a reason why the device is not successfully woken up.

[0521] As one embodiment, the third message indicates, for the device that is not successfully woken up, whether a response message from the device is received.

[0522] As one embodiment, the step S5103 is optional.

[0523] As one embodiment, the step S5105 is optional.

[0524] As one embodiment, the step S5109 is optional.

[0525] As one embodiment, the step S5103 is not present.

[0526] As one sub-embodiment of the above-mentioned embodiment, the target timer is not present.

[0527] As one sub-embodiment of the above-mentioned embodiment, the target timer is not configured.

[0528] As one embodiment, the step S5103 is present.

[0529] As one sub-embodiment of the above-mentioned embodiment, the present embodiment does not limit the order of the step S5102 and the step S5103.

[0530] As one sub-embodiment of the above-mentioned embodiment, the target timer is configured.

[0531] As one sub-embodiment of the above-mentioned embodiment, the value of the target timer is configured by a serving base station of the first node U01.

[0532] As one sub-embodiment of the above-mentioned embodiment, the value of the target timer is configured by a core network.

[0533] As one sub-embodiment of the above-mentioned embodiment, the value of the target timer is configured by the first core network information.

[0534] As one sub-embodiment of the above-mentioned embodiment, the accompanying the target message means during transmission of the target message.

[0535] As one sub-embodiment of the above-mentioned embodiment, the accompanying the target message means before submitting the target message to a lower layer.

[0536] As one sub-embodiment of the above-mentioned embodiment, the accompanying the target message means during setting of the target message.

[0537] As a sub-example of the above example, the target message is not sent while the target timer is running.

[0538] As a sub-example of the above example, the step S5105 is absent.

[0539] As a sub-example of the above example, the step S5105 is present.

[0540] As a sub-example of the above example, the target message is re-sent if the target timer expires and no response message is received from at least some of the at least one device.

[0541] As a sub-example of the above example, the no response message is received from at least some of the at least one device means no response message is received from any of the at least one device.

[0542] As a sub-example of the above example, the no response message is received from at least some of the at least one device means no response message is received from each of the at least one device.

[0543] As a sub-example of the above example, the step S5109 is absent.

[0544] As a sub-example of the above example, the step S5109 is present.

[0545] As a sub-example of the above example, the target timer is stopped in response to the second message being received if the target timer is running.

[0546] As a sub-example of the above example, the target timer is stopped if a response message is received from all of the at least one device and the target timer is running.

[0547] As an example, the step S5107 is after the step S5102 and the step S5201 is after the step S5202.

[0548] As an example, for a first node U01, the following steps are performed in sequence: receiving a first message in step S5101; sending a target message in step S5102; receiving a second message in step S5107; and stopping sending the target message in step S5108.

[0549] As an example, the step S5107 is before the step S5102.

[0550] As an embodiment, the step S5107 belongs to the step S5101, and the step S5202 belongs to the step S5201.

[0551] As an embodiment, for the first node U01, the following are performed in sequence: in the step S5101, the first message and the second message are received; in the step S5102, the target message is sent; wherein, the number of times of sending the target message reaches Q1; in the step S5108, the sending of the target message is stopped.

[0552] As an embodiment, for the first node U01, the following are performed in sequence: in the step S5101, the first message and the second message are received; in the step S5102, the target message is sent; in the step S5108, at the first time, the sending of the target message is stopped.

[0553] As an embodiment, the step S5108 is only for illustration that the target message is not continued to be sent, and can be based on implementation operation.

[0554] As an embodiment, the step S5108 includes the step S5109.

[0555] As an embodiment, the step S5108 includes the step S5110.

[0556] Embodiment 6

[0557] Embodiment 6 illustrates a schematic diagram of the second message indicating the first node to stop sending the target message according to an embodiment of the present application. In FIG. 6, the horizontal axis represents time; target message #1, …, target message #q, …, target message #Q1 are Q1 target messages sent in sequence after the first message is received.

[0558] In embodiment 6, the second message indicating to stop sending the target message includes: when the number of times of sending the target message reaches Q1, the sending of the target message is stopped; wherein, the second message indicates the Q1, the Q1 is a positive integer, and the first message includes the second message.

[0559] As an embodiment, the second message is an IE in the first message.

[0560] As an embodiment, the second message is a domain in the first message.

[0561] As an embodiment, the first core network information includes the second message.

[0562] As an embodiment, the second message is an IE in the first core network information.

[0563] As one embodiment, the second message is a field in the first core network information.

[0564] As one embodiment, the first message comprises the first core network information and RRC information; the RRC information comprises the second message.

[0565] As one embodiment, the second message is an IE in the RRC information.

[0566] As one embodiment, the second message is a field in the RRC information.

[0567] As one embodiment, the candidate of Q1 comprises 1.

[0568] As one embodiment, any candidate of Q1 is greater than 1.

[0569] As one embodiment, the candidate of Q1 comprises 2.

[0570] As one embodiment, the candidate of Q1 comprises 4.

[0571] As one embodiment, any two of the Q1 target messages are the same.

[0572] As one embodiment, at least two of the Q1 target messages are different.

[0573] As one embodiment, the Q1 target messages are continuous in time domain.

[0574] As one embodiment, the Q1 target messages are discontinuous in time domain.

[0575] As one embodiment, a first counter is increased by 1 each time a target message is sent; the number of times the target message is sent reaches Q1 means that the first counter equals the Q1.

[0576] As one embodiment, if the number of times the target message is sent does not reach the Q1, the sending of the target message is not stopped.

[0577] As one embodiment, a target timer is started along with the target message; if the target timer expires and no response message is received from at least part of the at least one device, the target message is re-sent.

[0578] As one sub-embodiment of the above-mentioned embodiment, the first counter is increased by 1 when the target timer expires.

[0579] As a sub-embodiment of the above-mentioned embodiment, when the target timer expires, the first counter is first increased by 1, and then it is determined whether the first counter after being increased by 1 is equal to Q1.

[0580] As a sub-embodiment of the above-mentioned embodiment, when the target timer expires, it is determined whether the number of times of sending the target message reaches Q1.

[0581] As a sub-embodiment of the above-mentioned embodiment, if the target timer expires and no response message is received from at least part of the at least one device and the number of times of sending the target message does not reach Q1, the target message is re-sent.

[0582] As an embodiment, a first counter is increased by 1 for each of the paging messages sent by the first node; wherein Q1 is the maximum value of the first counter.

[0583] Embodiment 7

[0584] Embodiment 7 illustrates a schematic diagram of a second message indicating a first node to stop sending a target message according to another embodiment of the present application. In FIG. 7, the horizontal axis represents time; after the first message is received and before the first time, at least one target message is sent.

[0585] In embodiment 7, the second message indicating to stop sending the target message comprises: at a first time, stopping sending the target message; wherein the first time depends on the second message; the first message comprises the second message.

[0586] As an embodiment, the first time is a time after the first message is received.

[0587] As an embodiment, from the first message is received to the first time, at least one target message is sent.

[0588] As an embodiment, the first time depending on the second message means that the second message indicates the first time.

[0589] As an embodiment, the first time depending on the second message means that the second message is used to determine the first time.

[0590] As an embodiment, the first time depending on the second message means that the second message indicates a first time length; the first time depends on the first time length.

[0591] As an embodiment, the first time length is used to determine the maximum time interval for sending the target message.

[0592] As one embodiment, the first time length is a value of a first timer; the first time instant is when the first timer expires.

[0593] As one embodiment, the first processor starts the first timer in conjunction with the first message.

[0594] As one embodiment, the first processor starts the first timer in conjunction with a first target message sent after the first message is received.

[0595] As one embodiment, the first processor starts the first timer in response to the first message being received.

[0596] As one embodiment, the first processor starts the first timer when a first target message is sent after the first message is received.

[0597] As one embodiment, the first timer is running during the first time length.

[0598] As one embodiment, the target message is sent during the first time length.

[0599] As one embodiment, the first timer is stopped in response to the response message from the at least one device being successfully received.

[0600] As one embodiment, the first timer is stopped in response to the second message being received.

[0601] As one embodiment, the first time instant is when the first timer expires.

[0602] As one embodiment, the first timer is a timer.

[0603] As one embodiment, the first timer is a window.

[0604] As one embodiment, the first time length is a positive integer number of time units.

[0605] As one embodiment, the time unit is a time slot.

[0606] As one embodiment, the time unit is a half time slot.

[0607] As one embodiment, the time unit is a millisecond.

[0608] As one embodiment, the time unit is a half millisecond.

[0609] As an embodiment, the second message is an IE in the first message.

[0610] As an embodiment, the second message is a field in the first message.

[0611] As an embodiment, the first core network information comprises the second message.

[0612] As an embodiment, the second message is an IE in the first core network information.

[0613] As an embodiment, the second message is a field in the first core network information.

[0614] As an embodiment, the first message comprises the first core network information and RRC information; the RRC information comprises the second message.

[0615] As an embodiment, the second message is an IE in the RRC information.

[0616] As an embodiment, the second message is a field in the RRC information.

[0617] Embodiment 8

[0618] Embodiment 8 illustrates a diagram of first core network information according to an embodiment of the present application. As shown in FIG. 8.

[0619] In embodiment 8, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0620] As an embodiment, the first core network information comprises a plurality of device identities; the plurality of device identities respectively indicate the plurality of devices.

[0621] The above method is beneficial to improve the paging freedom degree.

[0622] As an embodiment, the first core network information comprises at least one device group identity; the at least one device group identity indicates the plurality of devices.

[0623] The above method reduces the signaling overhead.

[0624] As an embodiment, the first core network information comprises at least one device group identity and at least one device identity; the at least one device group identity indicates part of the plurality of devices, and the at least one device identity indicates part of the plurality of devices.

[0625] The above method balances the signaling overhead and the paging freedom degree.

[0626] As one embodiment, the at least one device group identity is one device group identity.

[0627] As one embodiment, the at least one device group identity is a plurality of device group identities.

[0628] As one embodiment, the at least one core network information configures, for a device, a device group identity to which the device is associated.

[0629] As one embodiment, the at least one core network information configures, for a device group identity, devices to which the device group identity is associated.

[0630] As one embodiment, the at least one core network information comprises a block of information that configures a device of the plurality of devices, a field in the block of information indicating a device group identity to which the device is associated.

[0631] As one embodiment, the at least one core network information comprises a block of information that configures a device group, the block of information indicating at least some of the plurality of devices and a device group identity to which the at least some of the plurality of devices are associated.

[0632] As one embodiment, the at least one core network information comprises a plurality of blocks of information, the block of information being any of the plurality of blocks of information.

[0633] As one embodiment, the at least one core network information is the first core network information.

[0634] As one embodiment, the at least one core network information is core network information other than the first core network information.

[0635] As one embodiment, the at least one core network information is received prior to the first core network information.

[0636] As one embodiment, the block of information is an IE.

[0637] As one embodiment, the block of information is a field.

[0638] As one embodiment, the at least one device is a subset of the plurality of devices.

[0639] As one embodiment, the at least one device is the plurality of devices.

[0640] As one embodiment, the at least one device is only some of the plurality of devices.

[0641] As an embodiment, the target message comprises a device group identification of a device group to which the at least one device is associated.

[0642] Embodiment 9

[0643] Embodiment 9 illustrates a schematic diagram of a second message according to an embodiment of the present application, as shown in FIG. 9.

[0644] In embodiment 9, the first core network information indicates a plurality of devices, the at least one device is at least part of the plurality of devices; the second message comprises second core network information, the second core network information indicates at least one of the plurality of devices, the second message does not belong to the first core network information.

[0645] As an embodiment, the second message is the second core network information.

[0646] As an embodiment, the second core network information is information generated by a core network.

[0647] As an embodiment, the second core network information is information from a core network.

[0648] As an embodiment, the second message comprises another RRC message, the another RRC message comprises the second core network information.

[0649] As an embodiment of the above embodiment, the another RRC message is another RRC container.

[0650] As an embodiment of the above embodiment, the another RRC message comprises another RRC IE, the another RRC IE comprises the second core network information.

[0651] As an embodiment, the first core network information comprises at least one device group identification, the second core network information comprises the at least one device group identification.

[0652] As an embodiment, the first core network information comprises the first paging identification, the second core network information comprises the first paging identification.

[0653] As an embodiment, the first core network information indicates the plurality of devices, the second core network information indicates the plurality of devices.

[0654] As an embodiment, the second message and the first message do not belong to the same PDU.

[0655] As an embodiment, the second message is later than the first message in time domain.

[0656] Embodiment 10

[0657] Embodiment 10 illustrates a diagram of a target message according to an embodiment of the present application, as shown in FIG. 10.

[0658] In Embodiment 10, the target message comprises one device group identity and P1 device identities, the P1 is a positive integer; the one device group identity is associated with a plurality of devices, and the P1 device identities respectively indicate P1 devices; the at least one device is a device other than the P1 devices in the plurality of devices.

[0659] As an embodiment, for a device other than the P1 devices in the plurality of devices, a target action is performed in response to the target message being received.

[0660] As an embodiment, the target action comprises sending the response message.

[0661] As an embodiment, the target action comprises triggering a random access procedure; the random access procedure comprises sending the response message.

[0662] As an embodiment, for a device in the P1 devices, the target action is not performed in response to the target message being received.

[0663] As an embodiment, the P1 devices are devices in the plurality of devices.

[0664] As an embodiment, the target message comprises that the P1 device identities depend on the first core network information.

[0665] As an embodiment, the first core network information indicates the one device group identity and the P1 device identities.

[0666] As an embodiment, the target message comprises that the P1 device identities depend on receiving the response messages from the P1 devices.

[0667] As an embodiment, the target message comprises the P1 device identities if the response messages from the P1 devices are received.

[0668] As an embodiment, the first core network information indicates the one device group identity.

[0669] As an embodiment, the at least one device is all devices other than the P1 devices in the plurality of devices.

[0670] As an embodiment, the at least one device is part of the P1 devices among the plurality of devices.

[0671] Embodiment 11

[0672] Embodiment 11 illustrates a structural block diagram of a processing apparatus in a first node according to an embodiment of the present application; as shown in Figure 11. In Figure 11, the processing apparatus 1100 in the first node comprises a first receiver 1101, a first transmitter 1102.

[0673] The first receiver 1101 receives a first message on a downlink, the first message comprising first core network information;

[0674] The first transmitter 1102 transmits a target message; wherein the first message triggers transmission of the target message;

[0675] The first receiver 1101 receives a second message on a downlink;

[0676] In Embodiment 11, the target message is for waking up at least one device, and the second message indicates to stop transmitting the target message.

[0677] As an embodiment, the second message indicating to stop transmitting the target message comprises: the first transmitter 1202 stops transmitting the target message when the number of times of transmitting the target message reaches Q1; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0678] As an embodiment, the second message indicating to stop transmitting the target message comprises: the first transmitter 1202 stops transmitting the target message at a first time; wherein the first time depends on the second message; and the first message comprises the second message.

[0679] As an embodiment, the first core network information indicates a plurality of devices, and the at least one device is part of the plurality of devices.

[0680] As an embodiment, the second message comprises second core network information, the second core network information indicates at least one of the plurality of devices, and the second message does not belong to the first core network information.

[0681] As an embodiment, the target message comprises one device group identifier and P1 device identifiers, the P1 is a positive integer; the one device group identifier is associated with a plurality of devices, and the P1 device identifiers respectively indicate P1 devices; and the at least one device is a device other than the P1 devices among the plurality of devices.

[0682] As one embodiment, the first transmitter 1102, in conjunction with the target message, starts a target timer; the first transmitter 1102, when the target timer expires, retransmits the target message if a response message is not received from at least some of the at least one device.

[0683] As one embodiment, the first transmitter 1102, in response to the second message being received, stops the target timer if the target timer is running.

[0684] As one embodiment, the first transmitter 1102, if a response message is received from all of the at least one device and the target timer is running, stops the target timer.

[0685] As one embodiment, the first receiver 1101, in response to the target message being transmitted, listens for a response message from the at least one device; wherein the response message indicates a device identification.

[0686] As one embodiment, the first transmitter 1102, in response to the transmission of the target message being stopped, transmits a third message; wherein the third message indicates a device that was not successfully awoken.

[0687] As one embodiment, the first receiver 1101 comprises at least one of the antenna 452 or the receiver 454 or the multi-antenna reception processor 458 or the reception processor 456 or the controller / processor 459 or the memory 460 or the data source 467 in FIG.4.

[0688] As one embodiment, the first receiver 1101 comprises at least the antenna 452 and the receiver 454 in FIG.4.

[0689] As one embodiment, the first transmitter 1102 comprises at least one of the antenna 452 or the transmitter 454 or the multi-antenna transmission processor 457 or the transmission processor 468 or the controller / processor 459 or the memory 460 or the data source 467 in FIG.4.

[0690] As one embodiment, the first transmitter 1102 comprises at least the antenna 452 and the transmitter 454 in FIG.4.

[0691] As one embodiment, the first node is a UE.

[0692] As one embodiment, the first node is a reading device.

[0693] As an embodiment, the first node is a terminal.

[0694] As an embodiment, the first node is a relay.

[0695] Embodiment 12

[0696] Embodiment 12 illustrates a structural block diagram of a processing apparatus in a second node according to an embodiment of the present application; as shown in FIG. 12. In FIG. 12, the processing apparatus 1200 in the second node comprises at least the first transmitter 1201 and the second receiver 1202.

[0697] The second transmitter 1201 transmits a first message comprising first core network information on a downlink; wherein the first message triggers a receiver of the first message to transmit a target message; and transmits a second message on the downlink.

[0698] In embodiment 12, the target message is for waking up at least one device, and the second message instructs the receiver of the first message to stop transmitting the target message.

[0699] As an embodiment, the second message instructing the receiver of the first message to stop transmitting the target message comprises: when the number of times of transmitting the target message reaches Q1, the receiver of the first message stops transmitting the target message; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0700] As an embodiment, the second message instructing the receiver of the first message to stop transmitting the target message comprises: at a first time, the receiver of the first message stops transmitting the target message; wherein the first time depends on the second message; and the first message comprises the second message.

[0701] As an embodiment, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0702] As an embodiment, the second message comprises second core network information, the second core network information indicates at least one of the plurality of devices, and the second message does not belong to the first core network information.

[0703] As an embodiment, the target message comprises one device group identifier and P1 device identifiers, the P1 is a positive integer; the one device group identifier is associated with a plurality of devices, and the P1 device identifiers respectively indicate P1 devices; and the at least one device is a device other than the P1 devices among the plurality of devices.

[0704] As one embodiment, the recipient of the first message starts a target timer in response to the target message; when the target timer expires, the recipient of the first message re-sends the target message if no response message is received from at least some of the at least one device.

[0705] As one embodiment, the recipient of the first message stops the target timer in response to the second message being received.

[0706] As one embodiment, the recipient of the first message stops the target timer in response to the second message being received.

[0707] As one embodiment, the recipient of the first message listens for a response message from the at least one device in response to the target message being sent; wherein the response message indicates a device identity.

[0708] As one embodiment, the second receiver 1202 receives a third message; wherein the recipient of the first message sends the third message in response to the recipient of the first message stopping sending the target message; the third message indicates a device that is not successfully woken up.

[0709] As one embodiment, the second transmitter 1201 comprises at least one of the antenna 420 or the transmitter 418 or the multi-antenna transmit processor 471 or the transmit processor 416 or the controller / processor 475 or the memory 476 in FIG.4.

[0710] As one embodiment, the second transmitter 1201 comprises at least the antenna 420 and the transmitter 418 in FIG.4.

[0711] As one embodiment, the second receiver 1202 comprises at least one of the antenna 420 or the receiver 418 or the multi-antenna receive processor 472 or the receive processor 470 or the controller / processor 475 or the memory 476 in FIG.4.

[0712] As one embodiment, the second receiver 1202 comprises at least the antenna 420 and the receiver 418 in FIG.4.

[0713] As one embodiment, the second node is a RAN node.

[0714] As one embodiment, the second node is a base station device.

[0715] As an embodiment, the second node is a core network device.

[0716] As an embodiment, the second node is a NAS device.

[0717] As an embodiment, the second node comprises a base station device and a core network device.

[0718] Embodiment 13

[0719] Embodiment 13 illustrates a structural block diagram of a processing apparatus in a third node according to an embodiment of the present application; as shown in FIG. 13. In FIG. 13, the processing apparatus 1300 in the third node comprises at least the first receiver 1302 and the third transmitter 1301.

[0720] The third receiver 1302 receives a target message; wherein the first message triggers the sending of the target message; the sender of the target message receives the first message on a downlink, the first message comprising first core network information; the sender of the target message receives a second message on a downlink;

[0721] In embodiment 13, the target message is for waking up at least one device, and the second message instructs the sender of the target message to stop sending the target message.

[0722] As an embodiment, the second message instructing the sender of the target message to stop sending the target message comprises: when the sending times of the target message reach Q1, the sender of the target message stops sending the target message; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

[0723] As an embodiment, the second message instructing the sender of the target message to stop sending the target message comprises: at a first time, the sender of the target message stops sending the target message; wherein the first time depends on the second message; and the first message comprises the second message.

[0724] As an embodiment, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

[0725] As an embodiment, the second message comprises second core network information, the second core network information indicating at least one of the plurality of devices, and the second message does not belong to the first core network information.

[0726] As an embodiment, the target message comprises one device group identifier and P1 device identifiers, P1 is a positive integer; the one device group identifier is associated with a plurality of devices, and the P1 device identifiers respectively indicate P1 devices; the at least one device is a device other than the P1 devices in the plurality of devices.

[0727] As an embodiment, the sender of the target message starts a target timer along with the target message; when the target timer expires, if a response message is not received from at least part of the at least one device, the target message is re-sent.

[0728] As an embodiment, as a response to the second message being received, if the target timer is running, the sender of the target message stops the target timer.

[0729] As an embodiment, if a response message is received from all of the at least one device and the target timer is running, the sender of the target message stops the target timer.

[0730] As an embodiment, the third transmitter 1301 sends a response message as a response to the target message being received; wherein the one response message indicates a device identifier of the third node.

[0731] As an embodiment, as a response to the sender of the target message stopping sending the target message, the sender of the target message sends a third message; wherein the third message indicates a device that is not successfully woken up.

[0732] As an embodiment, the third transmitter 1301 comprises at least one of the antenna 420 or the transmitter 418 or the multi-antenna transmission processor 471 or the transmission processor 416 or the controller / processor 475 or the memory 476 in FIG. 4.

[0733] As an embodiment, the third transmitter 1301 comprises at least the antenna 420 and the transmitter 418 in FIG. 4.

[0734] As an embodiment, the third transmitter 1301 comprises at least one of the antenna 481, the transmission-related module 494, the encoder 493, and the controller 492 in FIG. 4.

[0735] As an embodiment, the third receiver 1302 comprises at least one of the antenna 420 or the receiver 418 or the multi-antenna reception processor 472 or the reception processor 470 or the controller / processor 475 or the memory 476 in FIG. 4.

[0736] As an example, the third receiver 1302 comprises at least the antenna 420 and the receiver 418 in FIG.4 of this application.

[0737] As an example, the third receiver 1302 comprises at least one of the antenna 481, the matching network 482, the receive correlation module 489, the decoder 491, the controller 492 in FIG.4 of this application.

[0738] As an example, the third node comprises one of the at least one device.

[0739] As an example, the third node is one of the at least one device.

[0740] As an example, the third node is an A-IoT device.

[0741] As an example, the third node is a terminal.

[0742] As an example, the third node is a module.

[0743] As an example, the third node is a UE.

[0744] Embodiment 14

[0745] Embodiment 14 illustrates a schematic diagram of an A-IoT logical system architecture according to an embodiment of the application; as shown in FIG.14. In FIG.14, block 1501 represents an A-IoT device, block 1502 represents a user equipment, block 1503 represents a base station device, and block 1504 represents an A-IoT core network.

[0746] In embodiment 14, the A-IoT device 1501 and the user equipment 1502 are connected through a first interface; the user equipment 1502 and the base station device 1503 are connected through a Uu interface; the base station device 1503 and the A-IoT core network 1504 are connected through a second interface; the user equipment 1502 comprises a common reading function 1505; and the base station device 1503 comprises an A-IoT RAN node function 1506.

[0747] As an example, the first node comprises the user equipment 1502, the second node comprises the base station device 1503, and the third node comprises the A-IoT device 1501; the downlink is the Uu interface; and the third node is one of the at least one device.

[0748] As an embodiment, the first node comprises the user equipment 1502, the second node comprises the A-IoT core network 1504, and the third node comprises the A-IoT device 1501; the downlink is the Uu interface; and the third node is one of the at least one device.

[0749] As an embodiment, the first node comprises the user equipment 1502, the second node comprises the base station device 1503 and the A-IoT core network 1504, and the third node comprises the A-IoT device 1501; the downlink is the Uu interface; and the third node is one of the at least one device.

[0750] As an embodiment, the A-IoT device 1501 is passive.

[0751] As an embodiment, the A-IoT device 1501 is equipped with energy storage function.

[0752] As an embodiment, the A-IoT device 1501 is not equipped with energy storage function.

[0753] As an embodiment, the peak power consumption of the A-IoT device 1501 is about 1 μW.

[0754] As an embodiment, the peak power consumption of the A-IoT device 1501 is less than or equal to a few hundred μW.

[0755] As an embodiment, the A-IoT device 1501 employs external carrier wave.

[0756] As an embodiment, the A-IoT device 1501 employs internally-generated carrier wave.

[0757] As an embodiment, the user equipment 1502 is a UE.

[0758] As an embodiment, the user equipment 1502 is a terminal.

[0759] As an embodiment, the user equipment 1502 is a reading device.

[0760] As an embodiment, the base station device 1503 performs radio resource management of A-IoT related radio resources.

[0761] As an embodiment, the base station device 1503 supports NR.

[0762] As an embodiment, the base station device 1503 is a gNB.

[0763] As an embodiment, the base station device 1503 supports 6G.

[0764] As an embodiment, the A-IoT core network 1504 can comprise an AMF and A-IoT related functions.

[0765] As an embodiment, the Uu interface is a NR Uu interface.

[0766] As an embodiment, the Uu interface is a 6G Uu interface.

[0767] As an embodiment, the Uu interface is responsible for data transmission between the base station device 1503 and the user device 1502.

[0768] As an embodiment, the Uu interface is responsible for signaling transmission between the base station device 1503 and the user device 1502.

[0769] As an embodiment, the first interface is an A-IoT radio interface.

[0770] As an embodiment, the first interface comprises a PRDCH.

[0771] As an embodiment, the first interface comprises a PDRCH.

[0772] As an embodiment, the first interface is responsible for data transmission between the A-IoT device 1501 and the user device 1502.

[0773] As an embodiment, the first interface is responsible for signaling transmission between the A-IoT device 1501 and the user device 1502.

[0774] As an embodiment, the second interface is an NG interface.

[0775] As an embodiment, the second interface is an NG based interface.

[0776] As an embodiment, the second interface is an A-IoT dedicated interface.

[0777] As an embodiment, the second interface is responsible for data transmission between the base station device 1503 and the A-IoT core network 1504.

[0778] As an embodiment, the second interface is responsible for signaling transmission between the base station device 1503 and the A-IoT core network 1504.

[0779] As an embodiment, the first message is transmitted through the Uu interface; the second message is transmitted through the Uu interface; and the target message is transmitted through the first interface.

[0780] As an embodiment, the A-IoT core network 1504 sends the first core network information to the base station device 1503 through the second interface; the base station device 1503 generates the first message according to the first core network information and sends the first message to the user equipment 1502 through the Uu interface; and the user equipment 1502 generates the target message according to the first message and sends the target message to the A-IoT device 1501 through the first interface.

[0781] A person of ordinary skill in the art can understand that all or part of the steps of the above method can be instructed by a program to complete the relevant hardware, and the program can be stored in a computer readable storage medium, such as a read-only memory, a hard disk, or an optical disk, etc. Alternatively, all or part of the steps of the above embodiment can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal, and UE in the present application include but are not limited to a drone, a communication module on a drone, a remote control airplane, a flying vehicle, a small airplane, a mobile phone, a tablet computer, a notebook computer, a vehicle-mounted communication device, a wireless sensor, a network card, an Internet of Things terminal, an RFID terminal, an NB-IOT terminal, an MTC (Machine Type Communication) terminal, an eMTC (enhanced MTC) terminal, a data card, a network card, a vehicle-mounted communication device, a low-cost mobile phone, a low-cost tablet computer, and other wireless communication devices. The base station or system device in the present application includes but is not limited to a macro cellular base station, a micro cellular base station, a home base station, a relay base station, a gNB (NR Node B), a TRP (Transmitter Receiver Point), and other wireless communication devices.

[0782] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node configured for wireless communication, the first node comprising: Comprising: a first receiver, receiving a first message on a downlink, the first message comprising first core network information; a first transmitter, transmitting a target message; wherein the first message triggers transmission of the target message; the first receiver, receiving a second message on the downlink; wherein the target message is for waking up at least one device, and the second message indicates to stop transmitting the target message.

2. The first node of claim 1, characterized in that, the second message indicating to stop transmitting the target message comprises: the first transmitter, stopping transmitting the target message when a number of times of transmitting the target message reaches Q1; wherein the second message indicates the Q1, the Q1 is a positive integer, and the first message comprises the second message.

3. The first node of claim 1, wherein, the second message indicating to stop transmitting the target message comprises: the first transmitter, stopping transmitting the target message at a first time; wherein the first time depends on the second message; and the first message comprises the second message.

4. The first node of any of claims 1 to 3, wherein, the first core network information indicates a plurality of devices, and the at least one device is at least part of the plurality of devices.

5. The first node of claim 4, wherein, the second message comprises second core network information, the second core network information indicates at least one of the plurality of devices, and the second message does not belong to the first core network information.

6. The first node of any of claims 1 to 5, wherein, the target message comprises one device group identifier and P1 device identifiers, the P1 is a positive integer; the one device group identifier is associated with a plurality of devices, and the P1 device identifiers respectively indicate P1 devices; and the at least one device is a device other than the P1 devices among the plurality of devices.

7. The first node of any of claims 1-6, wherein, Comprising: the first transmitter, starting a target timer along with the target message; the first transmitter, retransmitting the target message if the target timer expires and no response message is received from at least part of the at least one device.

8. The first node of claim 7, wherein, Comprising: the first transmitter, stopping the target timer if the target timer is running as a response to the second message being received.

9. The first node of claim 7 or 8, wherein, Comprising: the first transmitter, stopping the target timer if response messages are received from all of the at least one device and the target timer is running.

10. A method, used for wireless communication, in a first node used for wireless communication, characterized in that, Comprising: receiving a first message on a downlink, the first message comprising first core network information; transmitting a target message; wherein the first message triggers transmission of the target message; receiving a second message on the downlink; wherein the target message is for waking up at least one device, and the second message indicates to stop transmitting the target message.

11. A second node configured for wireless communication, the second node comprising: Comprising: a second transmitter, transmitting a first message on a downlink, the first message comprising first core network information; wherein the first message triggers a receiver of the first message to transmit a target message; and transmitting a second message on the downlink; wherein the target message is for waking up at least one device, and the second message indicates to the receiver of the first message to stop transmitting the target message.

12. A third node used for wireless communication, characterized in that, Comprising: a third receiver configured to receive a target message; wherein the first message triggers transmission of the target message; the sender of the target message receives the first message on a downlink, the first message comprising first core network information; the sender of the target message receives a second message on a downlink; wherein the target message is for waking up at least one device, and the second message instructs the sender of the target message to stop sending the target message.

Images