Information receiving method and apparatus, information sending method and apparatus, and communication system

By reusing existing base station deployments and optimizing information exchange methods in 5G systems, the limited processing power and energy of tag-type terminal devices have been solved, enabling low-cost and efficient IoT communication and supporting the application of tag-type terminal devices in business management and industrial manufacturing.

WO2026232505A1PCT designated stage Publication Date: 2026-11-121FINITY INC +5
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/093863
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing IoT technology standards cannot meet the needs of extreme environments and extremely small, low-cost terminal devices. RFID systems are insufficient in terms of information reading range and deployment cost. In 5G systems, the processing power and energy of tag-type terminal devices are limited, and they cannot efficiently utilize existing mechanisms to receive downlink signals.

Method used

By reusing existing base station deployments in 5G systems, tagged terminal devices are supported. Information exchange methods and apparatus between network devices and terminal devices, including sending and receiving multiple response messages, are used to optimize the processing power and energy utilization of terminal devices and achieve random access.

Benefits of technology

It effectively reduces the deployment and use costs of tag-based terminal devices, improves system capacity and spectrum utilization efficiency, supports the application of tag-based terminal devices in business management and industrial manufacturing, and promotes the digitalization process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025093863_12112026_PF_FP_ABST
    Figure CN2025093863_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide an information receiving method and apparatus, an information sending method and apparatus, and a communication system. The information receiving method comprises: a terminal device sends a first message to a network device, wherein the first message is related to a first identifier of the terminal device; the terminal device receives a first response message sent by the network device, wherein the first response message is related to the first message, and / or the first response message is related to the first identifier; and the terminal device receives a second response message sent by the network device, wherein the second response message is related to the first message, and / or the second response message is related to the first identifier and / or a second identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Information receiving and transmitting method, device and communication system TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology. BACKGROUND

[0002] Digital mobile communication has gone through 2G, 3G, 4G, and up to the current 5G, which has well met the needs of people in voice communication, digital mobile communication and mobile broadband networking communication, etc. However, with the development of society and economy, the demand for Internet of Things communication is gradually emerging. In order to meet the demand for Internet of Things communication, 3GPP (3rd Generation Partnership Project, Third Generation Partnership Project) defines a series of standards for Internet of Things technologies such as MTC (Machine-Type Communication, Machine-Type Communication), NB-IoT (Narrow Band Internet of Things, Narrow Band Internet of Things), RedCap (Reduced Capability, Reduced Capability) and the like.

[0003] Although the existing Internet of Things technology standards have realized the demand for low cost, low power consumption and large connection of Internet of Things terminal devices, there are still many scenarios where the demand for Internet of Things communication cannot use the existing Internet of Things technology standards, such as extreme working environment, which is not conducive to the maintenance of Internet of Things terminal devices; the demand for terminal devices with extremely small size and extremely low cost, etc. In the cellular system, how 3GPP supports the demand of the above-mentioned Internet of Things terminal devices is a problem to be solved.

[0004] It should be noted that the above introduction to the technical background is only to facilitate the clear and complete description of the technical solutions of the present application, and to facilitate the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application. SUMMARY

[0005] The inventors discovered that RFID (Radio Frequency Identification) technology is a widely used communication technology that can identify specific targets and read / write related data in a non-contact manner. The advantages of RFID systems include low tag cost and small size, making them frequently used in various applications such as logistics information collection, retail, libraries, and identity verification. One disadvantage of RFID systems is the limited information reading range (based on the wireless signal communication range) of RFID tags. Using manual handheld tag readers can result in high labor costs, which may be the main expense. Using dedicated RFID gateways to read and manage RFID tags requires significant deployment costs. Furthermore, the simple logical architecture of RFID systems makes it difficult to effectively coordinate with interference in radio wave transmission, resulting in generally low system capacity and spectrum utilization efficiency.

[0006] Compared to RFID systems, 3GPP's 5G systems support tag-based terminal devices, allowing for the reuse of existing base stations and leveraging existing cellular networks to support industry applications based on this type of terminal, thereby effectively reducing deployment and usage costs. 3GPP's 5G systems can provide reliable authentication, network coordination, and accurate and stable terminal device management mechanisms, and can also optimize the network to improve system capacity and spectrum utilization efficiency.

[0007] As a new type of IoT terminal in 5G systems, Ambient IoT devices (AIoT devices) are severely limited in cost. Their capabilities are significantly weaker than those of ordinary smartphones and other IoT devices supported by existing cellular mobile communication systems. For example, AIoT devices have limited processing power and stored energy for communication, and the mechanisms for receiving downlink signals in existing 5G systems cannot be reused. How to efficiently utilize the limited processing power of AIoT devices to receive downlink signals is a problem that needs to be solved.

[0008] To address at least one of the above-mentioned problems or other similar problems, embodiments of this application provide an information receiving and sending method, apparatus, and communication system.

[0009] According to one aspect of the embodiments of this application, an information receiving method is provided, including:

[0010] The terminal device sends a first message to the network device, the first message being related to a first identifier of the terminal device;

[0011] The terminal device receives a first response message sent by the network device, wherein the first response message is related to the first message and / or the first response message is related to the first identifier;

[0012] The terminal device receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0013] According to another aspect of the embodiments of this application, an information receiving device is provided, comprising:

[0014] A transmitter that sends a first message to a network device, the first message being related to a first identifier of a terminal device;

[0015] A receiver that receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier;

[0016] The receiver also receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0017] According to another aspect of the embodiments of this application, an information sending method is provided, including:

[0018] The network device sends an indication message to the terminal device, the indication message being used at least to instruct / configure / trigger the terminal device to send a first message;

[0019] The network device receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device;

[0020] The network device sends a third response message to the terminal device, the third response message being at least used to respond to the first message;

[0021] The network device sends a fourth response message to the terminal device, the fourth response message being used at least in response to the first message.

[0022] According to another aspect of the embodiments of this application, an information transmitting apparatus is provided, comprising:

[0023] A transmitter that sends an indication message to a terminal device, the indication message being used at least to instruct / configure / trigger the terminal device to send a first message;

[0024] A receiver that receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device;

[0025] The transmitter sends a third response message to the terminal device, the third response message being at least used to respond to the first message;

[0026] The transmitter also sends a fourth response message to the terminal device, the fourth response message being at least used to respond to the first message.

[0027] According to another aspect of the embodiments of this application, a communication system is provided, including...

[0028] A network device that sends an indication message to a terminal device, the indication message being at least used to instruct / configure / trigger the terminal device to send a first message; and receives the first message sent by the terminal device, the first message being related to a first identifier of the terminal device.

[0029] A terminal device sends the first message to a network device; receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier; and receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0030] One of the beneficial effects of the embodiments of this application includes: the terminal device receives the first response message and the second response message sent by the network device, thereby enabling efficient use of the limited processing capabilities of the tag-type terminal device to receive downlink signals.

[0031] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0032] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0033] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0034] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0035] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0036] Figure 2 is another schematic diagram of the communication system according to an embodiment of this application;

[0037] Figure 3 is another schematic diagram of the communication system according to an embodiment of this application;

[0038] Figure 4 is a schematic diagram of an information receiving method according to an embodiment of this application;

[0039] Figure 5 is a schematic diagram of an information sending method according to an embodiment of this application;

[0040] Figure 6 is a schematic diagram of an information receiving device according to an embodiment of this application;

[0041] Figure 7 is a schematic diagram of an information transmission device according to an embodiment of this application;

[0042] Figure 8 is a schematic diagram of a terminal device according to an embodiment of this application;

[0043] Figure 9 is a schematic diagram of a network device according to an embodiment of this application. Detailed Implementation

[0044] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0045] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0046] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0047] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Ambient IoT, etc.

[0048] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.

[0049] In this application embodiment, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, devices such as: base stations (BS), access points (AP), transmission reception points (TRP), broadcast transmitters, mobile management entities (MME), gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc. Furthermore, network devices may also include readers or interrogators used for AIoT, but this application is not limited to these devices.

[0050] In the above embodiments, base stations may include, but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base stations (gNB), IAB hosts (Donor), etc. They may also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.), readers, or interrogators. The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0051] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), tag, etc.

[0052] In the above embodiments, the terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, tag, device attached to or related to an item (e.g., for item management), etc.

[0053] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, ambient IoT devices, etc.

[0054] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0055] RFID systems are solutions for the large-scale, low-cost Internet of Things (IoT) terminal devices. RFID systems have wide applications. The advantages of RFID systems include low tag cost and low price. RFID tags are small, with fewer restrictions on the size and material of the items they can be used with, making them easy to apply to various item management and tracking scenarios. Although RFID tags are inexpensive, the deployment and usage costs of RFID systems are higher than wide-area commercial networks. In terms of deployment, RFID systems are typically deployed locally, with dedicated networks, making it difficult to effectively amortize deployment costs. In terms of usage, if a manual handheld tag reader solution is used, labor costs may become the main operating expense and are difficult to reduce; if dedicated RFID ports or gateways are used for reading and management, deployment costs will increase significantly. Furthermore, the simple logical architecture of RFID systems and loose wireless resource management, such as the difficulty in effectively coordinating interference in radio wave transmission, generally result in lower system capacity and spectrum utilization efficiency.

[0056] Compared to existing RFID systems, leveraging existing commercial mobile cellular networks (such as LTE and 5G NR systems) to support industry applications requiring tag-based IoT devices can effectively reduce deployment costs, thereby lowering the barrier to entry for this type of IoT device deployment. Furthermore, existing commercial mobile cellular networks (such as LTE and 5G NR systems) offer significantly better network security and wireless resource management than existing RFID systems. Taking 5G systems as an example, 5G can provide high-security authentication, network coordination, and accurate and stable terminal device management mechanisms, effectively reducing labor costs and thus lowering the overall cost of using this type of IoT. It can also optimize the network to improve system capacity and spectrum utilization efficiency. This reduction in deployment and usage costs can effectively promote the application of tag-based IoT devices in business management and industrial manufacturing, accelerate the digitalization process of related industries, improve production efficiency, and ultimately contribute more effectively to social development.

[0057] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0058] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, Figure 2 is another schematic diagram of a communication system according to an embodiment of this application, and Figure 3 is yet another schematic diagram of a communication system according to an embodiment of this application. Figures 1 to 3 schematically illustrate the situation using terminal devices and network devices as examples.

[0059] As shown in Figure 1, network devices can communicate directly with AIoT devices, sending signals directly to or receiving signals directly from AIoT devices. As shown in Figure 2, network devices can also send signals to or receive signals from AIoT devices through intermediate nodes. As shown in Figure 3, network devices can also send signals to AIoT devices or receive signals from AIoT devices via auxiliary nodes with the assistance of auxiliary nodes.

[0060] In the above examples, intermediate nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Intermediate nodes have the function of communicating with the network devices in Figure 2, and at least have the ability to send signals to and / or receive signals from AIoT devices. Auxiliary nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Auxiliary nodes have the function of communicating with the network devices in Figure 3, and at least have the ability to send signals to and / or receive signals from AIoT devices. The signals sent to and received from AIoT devices as described here conform to the specifications and descriptions of AIoT devices in communication standard protocols.

[0061] In the embodiments of this application, the network device sending signals / information / configurations to the AIoT device, or the AIoT device receiving signals / information / configurations from the network device, can be done in several ways: the network device directly sends the signal to the AIoT device, which then receives it; the network device sends the signal to the AIoT device via an intermediate node, which then receives it; the network device sends the signal to the AIoT device with the assistance of an auxiliary node, which then receives it; or the network device sends the signal to the AIoT device through other methods, which then receives it. Unless otherwise specified, this application is not limited to these methods.

[0062] In the embodiments of this application, the AIoT device sending signals / information to the network device or the network device receiving signals / information from the AIoT device can be done in various ways: the AIoT device sends the signal and the network device receives it directly; the AIoT device sends the signal and the network device receives it via an intermediate node; the AIoT device sends the signal and the network device receives it with the help of an auxiliary node; or the AIoT device sends the signal and the network device receives it through other methods. Unless otherwise specified, this application is not limited to these methods.

[0063] As a new type of IoT terminal in 5G systems, tagged terminal devices (Ambient IoT devices) face significant cost constraints. Their hardware capabilities are considerably weaker than traditional terminal devices, such as smartphones and other IoT devices supported by existing cellular mobile communication systems. For example, during random access, in response to a terminal device sending msg1, the network device repeatedly sends msg2. When deploying tagged terminal devices in cellular network systems, their processing power and stored energy for communication are limited. Furthermore, they do not support ARQ (Automatic Repeat reQuest) and HARQ (Hybrid Automatic Repeat reQuest), nor do they support retransmission merging. Existing 5G systems' schemes for receiving msg2 cannot be reused for tagged terminal devices. Therefore, determining the appropriate action or behavior when receiving repeatedly sent msg2 that both conserves energy and completes the random access process is a problem that needs to be solved.

[0064] To address at least one of the aforementioned problems or other similar issues, the embodiments of this application will be described below with reference to the accompanying drawings and specific implementation details. The above content can be incorporated as part of the embodiments of this application and combined with one or more of the following embodiments.

[0065] In the embodiments of this application, unless otherwise specified, expressions such as "in the case of," "if," and "when" have the same meaning and can be interchanged; tag-type terminal devices are also referred to as "first devices," "terminals," or "AIoT devices," and network devices are also referred to as "second devices," "networks," or "reading devices." They can be network devices in the examples of Figures 1 to 3, intermediate nodes in the example of Figure 2, or auxiliary nodes in the example of Figure 3. For example, they can be readers or interrogators, etc.

[0066] In the embodiments of this application, uplink / downlink signal transmission and reception can be performed between the first device and the second device. Downlink can also be an R2D link (reader-to-device link) or an R2T link (reader-to-tag link), etc., while uplink can also be a D2R link (device-to-reader link) or a T2R link (tag-to-reader link), etc. This application is not limited to these.

[0067] First aspect of the embodiments

[0068] This application provides an information receiving method, which will be described from the perspective of a terminal device.

[0069] Figure 4 is a schematic diagram of an information receiving method according to an embodiment of this application. As shown in Figure 4, the method includes:

[0070] 401: The terminal device sends a first message to the network device, the first message being related to a first identifier of the terminal device;

[0071] 402: The terminal device receives a first response message sent by the network device, wherein the first response message is related to the first message, and / or the first response message is related to the first identifier;

[0072] 403: The terminal device receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0073] It is worth noting that Figure 4 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 4 above.

[0074] In the embodiments of this application, the terminal device is, for example, a tag-type terminal device in the scenarios shown in Figures 1 to 3, which may be referred to as other devices, such as a first device or an IoT device; the network device is, for example, a network device in the scenarios shown in Figures 1 to 3, an intermediate node in the scenario shown in Figure 2, or an auxiliary node in the scenario shown in Figure 3, which may also be referred to as other devices, such as a second device or a reader. For ease of explanation, this application uses a tag-type terminal device as the first device and a network device as the second device as an example for description.

[0075] According to an embodiment of this application, a terminal device receives a first response message and a second response message sent by a network device. The first response message and the second response message are related to the first message, and / or the first response message is related to a first identifier, and the second response message is related to the first identifier and / or the second identifier. Thus, the terminal device can confirm that it has repeatedly received a response message that responds to the first message sent by the network device based on the first identifier and / or the second identifier. The tag-type terminal device receives the downlink signals repeatedly sent by the network device based on its limited processing capabilities and stored energy, and completes random access.

[0076] In this embodiment of the application, the first message is used to respond to the indication message sent by the network device. For example, the first message is message 1 (hereinafter referred to as "msg1") sent by the terminal device to the network device during the random access process. The indication message is a paging message or trigger message sent by the network device to the terminal device. The paging message or trigger message is used to instruct or trigger the terminal device to implement random access. msg1 is used to respond to the paging message or trigger message. After the terminal device determines that it has been selected to participate in this round of random access through the indication message, such as the paging message, it randomly selects a transmission occasion to send msg1.

[0077] In some embodiments, the first message includes a first identifier of the terminal device, which is at least randomly generated by the terminal device. For example, the terminal device randomly generates a 16-bit random number and uses this random number as the value of the first identifier.

[0078] In some embodiments, the terminal device sending a first message to the network device includes: the terminal device generating a value for a first identifier; setting / filling the information field corresponding to the first identifier in the first message with the value; and instructing the physical layer to send the first message at the selected access time.

[0079] For example, the actions or behaviors of a terminal device in sending the first message include:

[0080] 1. The terminal device generates a value for the first identifier, for example, the terminal device randomly generates a 16-bit random number;

[0081] 2. Set / fill the information field corresponding to the first identifier (Random ID) in msg1 with the stated value.

[0082] 3. Instruct the physical layer to send msg1 at the selected access time.

[0083] In some embodiments, the terminal device sending a first message to the network device further includes: the terminal device storing a first identifier generated therein.

[0084] For example, after the aforementioned action 1, the terminal device stores the generated first identifier. As another example, before the aforementioned action 2, the terminal device stores the generated first identifier, or after the aforementioned action 2. Yet another example, before the aforementioned action 3, the terminal device stores the generated first identifier, or after the aforementioned action 3.

[0085] In some embodiments, the terminal device releases its stored first identifier.

[0086] For example, after sending the first message, when the terminal device receives a paging message for a new round of random access, it releases its stored first identifier. Alternatively, when the terminal device receives a paging message and is selected to participate in that location or round of random access, it releases its stored first identifier. Or, when the terminal device receives a paging message and needs to regenerate random numbers, it releases its stored first identifier.

[0087] For example, after sending the first message, the terminal device receives a trigger message and releases its stored first identifier.

[0088] For example, after sending the first message, when the terminal device receives the msg4 (NACK message) sent to the terminal device, it releases the first identifier it stores. The terminal device can determine whether the msg4 was sent to the terminal device through the access layer ID (AS ID).

[0089] For example, after sending the first message, when the terminal receives other R2D messages, it releases the first identifier it stores. Other R2D messages include, but are not limited to, command messages sent by network devices, such as reading / writing information in the storage unit on the terminal device.

[0090] For example, after sending the first message, the terminal device receives the first response message and releases its stored first identifier. In some implementations, the terminal device stores the second identifier and then releases its stored first identifier. That is, the terminal device does not store the first identifier and the second identifier simultaneously.

[0091] In some embodiments, after the terminal device sends a first message, it receives at least one response message sent by the network device. The at least one response message is used to respond to the first message, and the at least one response message is related to the first message, and / or, the at least one response message is related to a first identifier and / or a second identifier.

[0092] For example, the response message is message 2 (or simply "msg2"), used to respond to msg1 sent by the terminal device. msg2 includes at least one of the following information fields:

[0093] --Message type. Used to identify or indicate that the downlink message is msg2. In some embodiments, the message type is determined in a predefined manner. For example, a communication standard uses n bits to identify different downlink messages, where n is greater than or equal to 1.

[0094] --The first identifier of the terminal device. The first identifier carried in msg2 is the same as the first identifier of the terminal device carried in msg1. After receiving msg1, the network device obtains the first identifier. The network device sets the first identifier information field in msg2, which responds to msg1, to the first identifier it obtained from msg1.

[0095] --A second identifier for the terminal device. The second identifier is used at least for network device scheduling / configuration / instruction of the terminal device to receive downlink information or send uplink information. In some embodiments, the second identifier may be an identifier of the terminal device assigned / assigned by the network device, different from the first identifier. For example, the second identifier is an Access Layer ID (AS layer ID); in other embodiments, the second identifier is the first identifier.

[0096] --Configuration / scheduling information for D2R messages. This configuration / scheduling information is used at least to schedule / configure / instruct the transmission of D2R messages. In some embodiments, the configuration / scheduling information for D2R messages includes at least time-domain or frequency-domain resource allocation information. The terminal device determines the time-frequency resources for transmitting D2R messages, such as the time-frequency resources for msg3 (described later), based on the configuration / scheduling information.

[0097] In some embodiments, at least one response message includes a first response message and a second response message.

[0098] For example, the terminal device receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier.

[0099] For example, after sending msg1, the terminal device receives msg2 sent by the network device. If msg2 is the first message the terminal device has received, and it is a response to msg1, then the msg2 received by the terminal device is a first response message. And / or if msg2 is the first message the terminal device has received, and it contains the first identifier carried in msg1, then the msg2 received by the terminal device is a first response message. In the embodiments of this application, the first response message is sometimes also referred to as "first msg2".

[0100] In some embodiments, the terminal device receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0101] For example, after receiving the first msg2, the terminal device also receives another msg2 sent by the network device. If this msg2 is a response to the msg1 sent by the terminal device, then the msg2 received by the terminal device is a second response message. And / or, if this msg2 contains the first identifier carried in msg1, then the msg2 received by the terminal device is a second response message. And / or, if the second identifier contained in this msg2 is the same as the second identifier stored by the terminal device, then the msg2 received by the terminal device is a second response message. And / or, if the first identifier contained in this msg2 is the same as the second identifier stored by the terminal device, then the msg2 received by the terminal device is a second response message. In embodiments of this application, the second response message is sometimes also referred to as "second msg2".

[0102] In some embodiments, the first response message is received before the second response message.

[0103] For example, the terminal device receives the first msg2 before the terminal device receives the second msg2. After the terminal device sends msg1 to the network device and receives the first msg2 sent by the network device, the terminal device also receives the second msg2 sent by the network device.

[0104] In some embodiments, before receiving the second response message, the terminal device sends a third message to the network device in response to the received first response message.

[0105] In this embodiment, the third message is message 3 (hereinafter referred to as "msg3") sent by the terminal device to the network device during the random access process. The third message is at least used to respond to msg2 received by the terminal device. The terminal device sends msg3 to the network device based on the information in msg2. msg3 may carry the EPC ID (Electronic Product Code ID) of the terminal device or information stored in the terminal device's storage unit.

[0106] For example, after receiving the first msg2 and before receiving the second msg2, the terminal device sends msg3 to the network device. msg3 is used in response to the first msg2 received by the terminal device. If the network device fails to successfully receive msg3, it sends msg2 to the terminal device again, for example, by sending msg2 once more, or multiple times. The msg2 received by the terminal device again is the second msg2. In some embodiments, the terminal device receives more than one second msg2. These more than one second msg2 are carried using different time-domain resources on the time axis; that is, they are sent using time-division multiplexing (TDM), or they do not overlap in the time domain.

[0107] In some embodiments, the terminal device also receives a fourth message sent by the network device, the fourth message being used at least in response to the third message.

[0108] In this embodiment, the fourth message is message 4 (hereinafter referred to as "msg4") sent by the network device to the terminal device during the random access process. In some embodiments, after successfully receiving msg3, the network device sends msg4 to the terminal device, such as an ACK message, or it may not send msg4 to the terminal device. In this case, if the terminal device does not receive msg4, it is assumed or considered that msg3 has been successfully received by the network device. In other embodiments, after failing to successfully receive msg3, the network device sends msg4 to the terminal device, such as a NACK message. After receiving msg4, the terminal device assumes or considers that msg3 has not been successfully received by the network device.

[0109] In some embodiments, the first response message and / or the second response message includes at least one of the following information fields: message type; first identifier of the terminal device.

[0110] In some embodiments, the first response message and / or the second response message may further include at least one of the following information fields: a second identifier of the terminal device; configuration / scheduling information for the D2R message.

[0111] In some embodiments, the second identifier is configured by the network device and is used at least to schedule / configure / instruct the terminal device to receive downlink information or send uplink information; the configuration / scheduling information of the D2R message is configured by the network device and is used at least to schedule / configure / instruct the terminal device to send a third message.

[0112] In some embodiments, the information fields contained in the first response message and the second response message may be the same. In other embodiments, the information fields contained in the first response message and the second response message may be different.

[0113] For example, the information fields contained in the first response message and the second response message can be the same. For example, both the first response message and the second response message contain a message type, a first identifier, and a second identifier, or both the first response message and the second response message contain a message type, a first identifier, and configuration / scheduling information for the D2R message.

[0114] For example, the information fields contained in the first response message and the second response message may be different. For instance, the first response message contains the message type, the first identifier, and the configuration / scheduling information of the D2R message, while the second response message contains the message type, the first identifier, and the second identifier.

[0115] In some embodiments, the information carried in the information fields of the first response message and the second response message may be the same. In other embodiments, the information carried in the information fields of the first response message and the second response message may be different.

[0116] For example, if the configuration / scheduling information of the D2R message is the same in the first response message and the second response message, the terminal device will send msg3 using the same time-frequency resources when it receives the first response message and the second response message. As another example, if the configuration / scheduling information of the D2R message is different in the first response message and the second response message, the terminal device will send msg3 using different time-frequency resources when it receives the first response message and the second response message.

[0117] In some embodiments, the first response message and / or the second response message further include indication information, which indicates whether the first response message and / or the second response message contains an information field corresponding to the second identifier, or indicates whether the first response message and / or the second response message carries the second identifier.

[0118] In some embodiments, the second identifier is optional in the first response message and / or the second response message.

[0119] For example, in some implementations, the network device does not assign / specify a second identifier to the terminal device, the network device does not send the second identifier in the information field corresponding to the second identifier, or msg2 does not contain the information field corresponding to the second identifier. The network device uses the first identifier to schedule / configure / instruct the terminal device to receive downlink information or send uplink information.

[0120] In some embodiments, the msg2 message may include indication information to indicate whether msg2 contains an information field corresponding to the second identifier, or whether msg2 carries the second identifier. For example, 1 bit may be used to indicate whether msg2 contains an information field corresponding to the second identifier or whether msg2 carries the second identifier. In other embodiments, the network device does not assign / specify a second identifier to the terminal device, and the network device sends padding bits in the information field corresponding to the second identifier, or the information field corresponding to the second identifier in msg2 carries padding bits.

[0121] In some embodiments, the first response message and / or the second response message further include indication information, which indicates whether the response message contains an information field corresponding to the configuration / scheduling information of the D2R message, or indicates whether the first response message and / or the second response message carries the configuration / scheduling information of the D2R message.

[0122] In some embodiments, the configuration / scheduling information of the D2R message is optional in the first response message and / or the second response message.

[0123] For example, in some implementations, the network device does not perform corresponding scheduling or configuration for sending D2R messages; the network device does not send information in the information field corresponding to the configuration / scheduling information of the D2R message, or msg2 does not contain the corresponding information field. The terminal device reuses the time-frequency resources of msg1 to send D2R messages; for example, the terminal device reuses the time-frequency resources of msg1 to send msg3. The time-frequency resource information for sending msg1 is carried in the paging message.

[0124] In some embodiments, the msg2 message may include indication information to indicate whether msg2 contains the information field corresponding to the configuration / scheduling information of the D2R message, or to indicate whether msg2 carries the configuration / scheduling information. For example, 1 bit may be used to indicate whether msg2 contains the information field or whether msg2 carries the configuration / scheduling information. In other embodiments, the network device does not perform corresponding scheduling or configuration for D2R message transmission, and the network device sends padding information in the corresponding information field, or the corresponding information field in msg2 carries padding bits.

[0125] In some embodiments, the information contained in the first response message and / or the second response message is carried in the PDU of the downlink MAC layer, or in the control signaling of the downlink layer 1. In other embodiments, part of the information contained in the first response message and / or the second response message is carried in the PDU of the downlink MAC layer, and another part is carried in the control signaling of the downlink layer 1. For example, the message type and / or the first identifier is carried in the control signaling of the downlink L1, and the second identifier and / or the configuration / scheduling information of the D2R message is carried in the PDU of the downlink MAC layer.

[0126] In some embodiments, the terminal device receives a first response message, and the receiving method includes: determining whether the downlink signal or message it receives is the msg2 based on the message type.

[0127] For example, message type information is carried in downlink L1 control signaling. The time-domain resources carrying the control signaling are located before the time-domain resources carrying the downlink message on the time axis. After the terminal device determines that the message type is msg2, it continues to receive downlink signals, demodulates and decodes the downlink signals, and then transmits the information bit stream to the MAC layer. Otherwise, the terminal device stops receiving subsequent downlink signals or skips receiving subsequent downlink signals and waits for the next downlink signal. In some embodiments, message type information is carried in a downlink MAC PDU. After the terminal device determines that the message type is msg2, it performs the next step related to receiving msg2; otherwise, it does not perform the next step related to receiving msg2.

[0128] Furthermore, the terminal device receives a first response message, and the receiving method further includes: if the received downlink signal or message is msg2, the terminal device determines whether the first identifier carried in msg2 is the same as the first identifier in its sent msg1. In some embodiments, the information of the first identifier is carried in the control signaling of downlink L1, and the time-domain resources carrying the control signaling are located before the time-domain resources carrying the downlink message on the time axis. After receiving the first identifier, the terminal device compares the received first identifier with the stored first identifier or the first identifier carried in msg1. If they are the same, the terminal device determines that the downlink signal or message is msg2 in response to its sent msg1. The terminal device continues to receive downlink signals, and after demodulating and decoding the downlink signals, it transmits the information bit stream to the MAC layer. Otherwise, the terminal device stops receiving subsequent downlink signals or skips the reception of subsequent downlink signals and waits for the next downlink signal. In some embodiments, the first identification information is carried in a downlink MAC PDU. After receiving the first identification, the terminal device compares the received first identification with the stored first identification or the first identification carried in msg1. If they are the same, the next step related to receiving msg2 is performed; otherwise, the next step related to receiving msg2 is not performed.

[0129] In some embodiments, the terminal device receives a first response message sent by a network device, wherein the first identifier in the first identifier information field of the first response message is the same as the first identifier in the first message sent by the terminal device.

[0130] In some embodiments, after the terminal device sends a first message to the network device and successfully receives a first response message, the terminal device assumes or believes that the contention conflict has been successfully resolved, or that the contention-based random access has successfully ended.

[0131] In some embodiments, the terminal device receiving the first response message includes:

[0132] The terminal device assumes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed.

[0133] The terminal device sets the value in the second identifier information field of the first response message as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier;

[0134] The application or storage of the information in the configuration / scheduling information field of the D2R message in the first response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0135] Initiate the sending of D2R messages.

[0136] For example, after a terminal device sends msg1 to a network device and receives the first msg2, the actions / behaviors of its MAC layer entity include:

[0137] If the first identifier in the first identifier information field of msg2 is the same as the first identifier in the msg1 it sent,

[0138] 1. The terminal device believes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed.

[0139] 2. The terminal device sets the value in the second identifier field as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier.

[0140] 3. Apply or store the information in the configuration / scheduling information field of the D2R message, and instruct / transmit the information in that information field to the physical layer.

[0141] 4. Initialize the sending of D2R messages.

[0142] In some embodiments, the terminal device receiving the first response message further includes:

[0143] If the first response message contains a second identification information field...

[0144] The terminal device sets the value in the second identifier information field as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier;

[0145] If the second response message does not contain a second identification information field.

[0146] The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification.

[0147] For example, the second identifier field in msg2 is optional. Action / behavior 2 above can also be:

[0148] 2a. If msg2 contains a second identifier field,

[0149] a) The terminal device sets the value in the second identifier information field as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier.

[0150] 2b. Otherwise,

[0151] a) The terminal device sets the value in the first identifier field to the second identifier and stores the second identifier, or the terminal device stores the value in the first identifier field as the second identifier.

[0152] In some embodiments, the terminal device receiving the first response message further includes:

[0153] If the first response message contains a configuration / scheduling information field for a D2R message,

[0154] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer;

[0155] If the first response message does not contain the configuration / scheduling information field of the D2R message,

[0156] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer reuses the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message.

[0157] For example, the configuration / scheduling information field of the D2R message in msg2 is optional. Action / behavior 3 above can also be...

[0158] 3a. If msg2 contains the configuration / scheduling information field of a D2R message,

[0159] a) Apply or store the information in the information domain, and instruct / transmit the information in the information domain to the physical layer.

[0160] 3b. Otherwise,

[0161] a) Indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer reuses the time-frequency resources of msg1 to send D2R messages, or that the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of D2R messages.

[0162] The MAC entity of the terminal device does not perform any actions / behaviors related to the configuration / scheduling information of the D2R message, including but not limited to not applying or storing the information in the configuration / scheduling information field of the D2R message, and not indicating / transmitting the information in the information field to the physical layer;

[0163] In some embodiments, after receiving the first response message, the terminal device receives a second response message. The receiving method includes determining whether the received downlink signal or message is msg2 based on the message type. The method and actions described are similar to those of the terminal device receiving the first response message. Specific implementation details can be found in the foregoing embodiments and will not be repeated here.

[0164] Furthermore, after receiving the first response message, the terminal device receives a second response message. The receiving method further includes: if the received downlink signal or message is msg2, the terminal device determines whether the first identifier carried in msg2 is the same as the first identifier in the first message it sent. The method and actions described are similar to those for receiving the first response message; specific implementation details can be found in the foregoing embodiments and will not be repeated here.

[0165] In some embodiments, after receiving a first response message, the terminal device receives a second response message. The receiving method further includes: if the received downlink signal or message is msg2, the terminal device determines whether the second identifier carried in msg2 is the same as a stored second identifier, or whether the first identifier carried in msg2 is the same as a stored second identifier. In some embodiments, the terminal device determines whether msg2 is a response to its first message by comparing whether the second identifier carried in msg2 is the same as the stored second identifier. If they are the same, the terminal device performs a next step related to receiving the second response message; otherwise, it does not perform a next step related to receiving the second msg2. In other embodiments, the terminal device determines whether msg2 is a response to its first message by comparing whether the first identifier carried in msg2 is the same as the stored second identifier. If they are the same, the terminal device performs a next step related to receiving the second msg2; otherwise, it does not perform a next step related to receiving the second msg2.

[0166] In some embodiments, the first identifier in the first identifier information field of the second response message is the same as the first identifier in the first message sent by the terminal device, and / or the second identifier in the second identifier information field of the second response message is the same as the second identifier stored by the terminal device, and / or the first identifier in the first identifier information field of the second response message is the same as the second identifier stored by the terminal device.

[0167] In some embodiments, the terminal device receiving the second response message includes: the terminal device believes or assumes that the contention conflict has been successfully resolved, or that the random access process has been successfully completed;

[0168] The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier;

[0169] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0170] Initiate the sending of D2R messages.

[0171] In the above embodiments, the terminal device receiving the second response message further includes:

[0172] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0173] The MAC entity of the terminal device does not perform any actions / behaviors related to the second identifier, including but not limited to: not setting the value in the second identifier information field to the second identifier; not storing the second identifier; and not updating the stored second identifier.

[0174] In the above embodiments, the terminal device receiving the second response message further includes:

[0175] The terminal device compares the information in the configuration / scheduling information field of the D2R message of the second response message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0176] For example, when a terminal device receives the second msg2, the actions / behaviors of its MAC layer entity include:

[0177] If the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the first identifier in the first message sent by the terminal device, and / or if the second identifier in the second identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device, and / or if the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device,

[0178] 1. The terminal device believes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed.

[0179] 2. The terminal device sets the value in the second identifier field to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier, or the MAC entity of the terminal device does not perform any action / behavior related to the second identifier. Alternatively,

[0180] 2'. The terminal device compares the value in the second identifier field with the stored second identifier.

[0181] a) If they are the same, the MAC entity of the terminal device does not have any actions / behaviors related to the second identifier;

[0182] b) If they are different, the terminal device sets the value in the second identifier field to the second identifier and updates the stored second identifier.

[0183] 3. Apply or store the information in the configuration / scheduling information field of the D2R message, and instruct / pass the information in that field to the physical layer. Alternatively,

[0184] 3'. The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information.

[0185] a) If the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer;

[0186] b) If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0187] 4. Initialize the sending of D2R messages.

[0188] In some embodiments, the terminal device receiving the second response message further includes:

[0189] When the second response message includes a second identification information field.

[0190] The terminal device sets the value in the second identification information field to the second identification and stores the second identification; or the terminal device stores the value in the second identification information field as the second identification; or the MAC entity of the terminal device does not perform any action / behavior related to the second identification; or...

[0191] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0192] If the second response message does not contain a second identification information field.

[0193] The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification, or the MAC entity of the terminal device does not have any action / behavior related to the second identification.

[0194] For example, the second identifier field in msg2 is optional. The aforementioned actions / behaviors 2 and 2' can also be:

[0195] 2a. If msg2 contains a second identifier field,

[0196] a) The terminal device sets the value in the second identifier information field as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not perform any action / behavior related to the second identifier. Or

[0197] a') The terminal device compares the value in the second identifier information field with the stored second identifier.

[0198] i. If they are the same, the MAC entity of the terminal device does not have any actions / behaviors related to the second identifier.

[0199] ii. If they are different, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0200] 2b. Otherwise,

[0201] a) The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification, or the MAC entity of the terminal device does not have any action / behavior related to the second identification.

[0202] In some embodiments, the terminal device receiving the second response message further includes:

[0203] If the second response message includes the configuration / scheduling information field of the D2R message,

[0204] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer; or,

[0205] The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0206] If the second response message does not contain the configuration / scheduling information field of the D2R message,

[0207] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer has reused the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0208] For example, the configuration / scheduling information field of the D2R message in msg2 is optional. Actions / behaviors 3 and 3' mentioned above can also be:

[0209] 3a. If msg2 contains the configuration / scheduling information field of a D2R message,

[0210] a) Apply or store the information in the information domain, and instruct / transmit the information in the information domain to the physical layer.

[0211] or

[0212] a') The terminal device compares the information in this information field with the stored configuration / scheduling information.

[0213] i. If the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0214] ii. If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0215] 3b. Otherwise,

[0216] a) Indicates that the physical layer has not configured or scheduled D2R, or instructs the physical layer to reuse the time-frequency resources of msg1 to send D2R messages, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of D2R messages, or instructs / transmits stored information to the physical layer.

[0217] In some embodiments, the terminal device receiving the second response message further includes:

[0218] The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier;

[0219] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0220] Initiate the sending of D2R messages.

[0221] In the above embodiments, the terminal device receiving the second response message further includes:

[0222] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0223] In the above embodiments, the terminal device receiving the second response message further includes:

[0224] The terminal device compares the information in the configuration / scheduling information field of the D2R message of the second response message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0225] For example, when a terminal device receives the second msg2, the actions / behaviors of its MAC layer entity include:

[0226] If the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the first identifier in the first message sent by the terminal device, and / or if the second identifier in the second identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device, and / or if the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device,

[0227] 1. The terminal device sets the value in the second identifier field to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier, or the MAC entity of the terminal device does not perform any action / behavior related to the second identifier. Alternatively,

[0228] 1'. The terminal device compares the value in the second identifier field with the stored second identifier.

[0229] a) If they are the same, the MAC entity of the terminal device does not have any actions / behaviors related to the second identifier;

[0230] b) If they are different, the terminal device sets the value in the second identifier field to the second identifier and updates the stored second identifier.

[0231] 2. Apply or store the information in the configuration / scheduling information field of the D2R message, and instruct / pass the information in that field to the physical layer. Alternatively,

[0232] 2'. The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information.

[0233] a) If the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer;

[0234] b) If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0235] 3. Initialize the sending of D2R messages.

[0236] Therefore, the terminal device does not need to assume / believe that the contention conflict has been successfully resolved, or that the random access based on the contention has successfully ended, thereby reducing the complexity of the terminal device in processing downlink signals / messages and saving the terminal device's energy.

[0237] In some embodiments, the terminal device receiving the second response message further includes:

[0238] When the second response message includes a second identification information field.

[0239] The terminal device sets the value in the second identification information field to the second identification and stores the second identification; or the terminal device stores the value in the second identification information field as the second identification; or the MAC entity of the terminal device does not perform any action / behavior related to the second identification; or...

[0240] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0241] If the second response message does not contain a second identification information field.

[0242] The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification, or the MAC entity of the terminal device does not have any action / behavior related to the second identification.

[0243] For example, the second identifier field in msg2 is optional. The aforementioned actions / behaviors 1 and 1' can also be:

[0244] 1a. If msg2 contains a second identifier field,

[0245] a) The terminal device sets the value in the second identifier field to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier, or the MAC entity of the terminal device does not perform any action / behavior related to the second identifier. Or

[0246] a') The terminal device compares the value in the second identifier field with the stored second identifier.

[0247] i. If they are the same, the MAC entity of the terminal device does not have any actions / behaviors related to the second identifier.

[0248] ii. If they are different, the terminal device sets the value in the second identifier field to the second identifier and updates the stored second identifier.

[0249] 1b. Otherwise,

[0250] a) The terminal device sets the value in the first identifier field as the second identifier and stores the second identifier, or the terminal device stores the value in the first identifier field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier.

[0251] In some embodiments, the terminal device receiving the second response message further includes:

[0252] If the second response message includes the configuration / scheduling information field of the D2R message,

[0253] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer; or,

[0254] The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0255] If the second response message does not contain the configuration / scheduling information field of the D2R message,

[0256] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer has reused the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0257] For example, the configuration / scheduling information field of the D2R message in msg2 is optional. Actions / behaviors 2 and 2' mentioned above can also be:

[0258] 2a. If msg2 contains the configuration / scheduling information field of a D2R message,

[0259] a) Apply or store the information in the information domain, and instruct / transmit the information in the information domain to the physical layer.

[0260] or

[0261] a') The terminal device compares the information in this information field with the stored configuration / scheduling information.

[0262] i. If the same, the MAC entity of the terminal device does not perform any actions related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0263] ii. If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0264] 2b. Otherwise,

[0265] a) Indicates that the physical layer has not configured or scheduled D2R, or instructs the physical layer to reuse the time-frequency resources of msg1 to send D2R messages, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of D2R messages, or instructs / transmits stored information to the physical layer.

[0266] In some embodiments, the terminal device receiving the second response message further includes:

[0267] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0268] Initiate the sending of D2R messages.

[0269] For example, when a terminal device receives the second msg2, the actions / behaviors of its MAC layer entity include:

[0270] If the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the first identifier in the first message sent by the terminal device, and / or if the second identifier in the second identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device, and / or if the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device,

[0271] 1. Apply or store the information in the configuration / scheduling information field of the D2R message, and instruct / pass the information in that field to the physical layer. Alternatively,

[0272] 1'. The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information.

[0273] a) If the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer;

[0274] b) If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0275] 2. Initialize the sending of D2R messages.

[0276] Therefore, the terminal device does not need to assume / consider that the contention conflict has been successfully resolved, or that the contention-based random access has successfully ended, nor does it need to process the second identifier. The terminal device uses the second identifier obtained and stored from the first msg2. This reduces the complexity of the terminal device in processing downlink signals / messages and saves the terminal device's energy.

[0277] In some embodiments, the terminal device receiving the second response message further includes:

[0278] If the second response message includes the configuration / scheduling information field of the D2R message,

[0279] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer; or,

[0280] The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0281] If the second response message does not contain the configuration / scheduling information field of the D2R message,

[0282] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer has reused the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0283] For example, the configuration / scheduling information field of the D2R message in msg2 is optional. Actions / behaviors 1 and 1' mentioned above can also be:

[0284] 1a. If msg2 contains the configuration / scheduling information field of a D2R message,

[0285] a) Apply or store the information in the information domain, and instruct / transmit the information in the information domain to the physical layer.

[0286] or

[0287] a') The terminal device compares the information in this information field with the stored configuration / scheduling information.

[0288] i. If the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0289] ii. If they are different, apply or store the information in that information domain and instruct / pass the information in that information domain to the physical layer.

[0290] 1b. Otherwise,

[0291] a) Indicates that the physical layer has not configured or scheduled D2R, or instructs the physical layer to reuse Msg1's time-frequency resources to send D2R messages, or the MAC entity of the terminal device has not taken any action / behavior related to the configuration / scheduling information of D2R messages, or indicates / transmits stored information to the physical layer.

[0292] In some embodiments, the terminal device receiving the second response message further includes:

[0293] Initiate the sending of D2R messages.

[0294] For example, when a terminal device receives the second msg2, the actions / behaviors of its MAC layer entity include:

[0295] If the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the first identifier in the first message sent by the terminal device, and / or if the second identifier in the second identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device, and / or if the first identifier in the first identifier information field of msg2 received by the terminal device is the same as the second identifier stored by the terminal device,

[0296] 1. Initialize the sending of D2R messages.

[0297] Therefore, the terminal device does not need to assume again that the contention conflict has been successfully resolved, or that the contention-based random access has successfully ended, nor does it need to process the second identifier. The terminal device uses the second identifier obtained and stored from the first msg2. Furthermore, it does not need to process the configuration / or scheduling information of the D2R message; the terminal device uses the configuration / or scheduling information of the D2R message obtained from the first msg2 to send msg3. This reduces the complexity of the terminal device processing downlink signals / messages and saves the terminal device's energy.

[0298] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0299] According to the above embodiments, the limited processing power and / or limited energy of tag-type terminal devices can be efficiently utilized to receive downlink signals.

[0300] Second aspect of the embodiments

[0301] This application provides an information transmission method, described from the perspective of a network device. The second aspect of the embodiment can be implemented in conjunction with or separately from the first aspect of the embodiment; content identical to that in the first aspect of the embodiment will not be repeated.

[0302] Figure 5 is a schematic diagram of an information sending method according to an embodiment of this application. As shown in Figure 5, the method includes:

[0303] 501: The network device sends an indication message to the terminal device, the indication message being used at least to instruct / configure / trigger the terminal device to send a first message;

[0304] 502: The network device receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device;

[0305] 503: The network device sends a third response message to the terminal device, the third response message being used at least to respond to the first message;

[0306] 504: The network device sends a fourth response message to the terminal device, the fourth response message being used at least in response to the first message.

[0307] It is worth noting that Figure 5 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 5 above.

[0308] In the embodiments of this application, the indication message is at least used to instruct / configure / trigger the terminal device to send a first message. For example, the indication message is a paging message or trigger message sent by the network device to the terminal device during random access. The paging message or trigger message is used to instruct or trigger the terminal device to implement random access. Sometimes the paging message or trigger message is also referred to as "message0" or "msg0".

[0309] In some embodiments, the paging message further includes transmission timing information for one or more terminal devices to send msg1, and the number of transmission timings, wherein the terminal device randomly selects one transmission timing to send msg1. In some embodiments, the trigger message is at least used by the terminal device to determine the timing for sending msg1.

[0310] In the embodiments of this application, the third response message and / or the fourth response message may be the first response message and / or the second response message described in the embodiments of the first aspect, or other response messages in response to the first message, hereinafter collectively referred to as response messages.

[0311] In some embodiments, the network device sends a response message to one or more terminal devices, the response message responding to a first message sent by one or more terminal devices.

[0312] For example, a network device sends a msg2 to one or more terminal devices in response to a msg1 sent by one or more terminal devices. The msg2 is related to one or more msg1, and / or the msg2 is related to one or more first identifiers, such as containing one or more first identifiers.

[0313] In some embodiments, the network device sends one or more response messages to one or more terminal devices, and each response message responds to a first message sent by a terminal device.

[0314] For example, a network device sends one or more msg2 messages to one or more terminal devices. One msg2 message is used in response to a msg1 message sent by one terminal device. One msg2 message is related to one msg1 message, and / or one msg2 message is related to a first identifier, such as containing a first identifier. The network device sends one or more msg2 messages in response to msg1 messages sent by one or more terminal devices.

[0315] In some embodiments, the network device sends one or more response messages to a terminal device, and the one or more response messages respond to the first message sent by the terminal device.

[0316] For example, a network device sends one or more msg2 messages to a terminal device. These one or more msg2 messages are used in response to msg1 messages sent by the terminal device, and are related to one msg1 message, or are related to a first identifier, such as containing the same first identifier.

[0317] For example, after the network device sends msg2a (i.e., the third response message) in response to msg1 sent by the terminal device, it sends msg2b (i.e., the fourth response message) to the terminal device again in response to msg1. msg2a and msg2b are related to a msg1, and / or msg2a and msg2b are related to a first identifier, that is, msg2a and msg2b contain the same first identifier.

[0318] In some implementations, the network device may also send msg2b to the terminal device multiple times in response, and this application does not limit the number of times msg2b can be sent.

[0319] In some implementations, after the network device sends msg2a in response to msg1 sent by the terminal device, it receives msg3a (i.e., msg3 corresponding to msg2a) sent by the terminal device on uplink time-frequency resources. If the network device fails to receive msg3a sent by the terminal device on the uplink resources or fails to successfully receive msg3a sent by the terminal device on the uplink resources (including but not limited to the terminal device failing to successfully receive msg2a, failing to successfully send msg3a, or the network device failing to successfully demodulate and decode msg3a), the network device sends msg2b to the terminal device again; or, after sending msg4 (NACK message) to the terminal device, the network device sends msg2b to the terminal device again. The uplink time-frequency resources are used by the terminal device to send msg3, and the uplink time-frequency resource information is carried in the relevant information field of msg2, or the communication protocol predefines the time-frequency resources used to send msg3. The terminal device determines the time and frequency resources for sending msg3 by receiving msg2 or by a predefined method.

[0320] In some embodiments, if the network device sends msg2a but does not successfully receive msg3a from the corresponding terminal device, the network device sends msg4 (NACK message) to the terminal device; or if the network device sends msg2a and repeatedly sends msg2b but still fails to receive msg3 from the corresponding terminal device, the network device sends msg4 (NACK message) to the terminal device.

[0321] In some embodiments, msg2a and msg2b are distributed across different time-domain resources on the time axis; that is, msg2a and msg2b are transmitted in a TDM manner, or carry time-frequency resources for msg2a and msg2b, and do not overlap in the time domain. The network device transmits msg2a earlier than msg2b; in other words, the time-frequency resources carrying msg2a are earlier on the time axis than the time-frequency resources carrying msg2b.

[0322] In some embodiments, the network device also sends other downlink messages between msg2a and msg2b on the timeline. These downlink messages can be msg4 or paging / trigger messages. Alternatively, no other downlink messages may be sent between msg2a and msg2b.

[0323] The following explains the relationship between the first msg2 and the second msg2 received by the terminal device and the msg2a and msg2b sent by the network device, as well as the relationship between the first response message and the second response message received by the terminal device and the third response message and the fourth response message sent by the network device.

[0324] In this embodiment, after the terminal device sends msg1 to the network device, on the timeline, it first receives msg2, whose first identifier is the same as the first identifier in msg1. This msg2 is the first msg2 (i.e., the first response message). Upon receiving another msg2, whose first identifier is the same as the first identifier in msg1, this msg2 is the second msg2 (i.e., the second response message). In some embodiments, after the terminal device sends msg1 to the network device, it successfully receives msg2a (i.e., the third response message) sent by the network device. In this case, the first msg2 is msg2a. If the terminal device then successfully receives msg2b (i.e., the fourth response message) sent by the network device, the second msg2 is msg2b. In some other embodiments, if the terminal device fails to receive msg2a sent by the network device, but successfully receives msg2b, then the first msg2 is msg2b. In this case, if the terminal device successfully receives another msg2b sent by the network device (which can also be denoted as "msg2c"), then the second msg2 is msg2c.

[0325] In some embodiments, the third response message and / or the fourth response message are related to the first message, and / or the third response message and / or the fourth response message are related to the first identifier.

[0326] In some embodiments, the network device does not receive or fails to receive a third message from the terminal device in response to the third response message before sending the fourth response message to the terminal device.

[0327] In some embodiments, the third response message and / or the fourth response message includes at least one of the following information fields:

[0328] Message type;

[0329] The first identifier of the terminal device.

[0330] In some embodiments, the third response message and / or the fourth response message further include at least one of the following information fields:

[0331] The second identifier of the terminal device;

[0332] Configuration / scheduling information for D2R messages.

[0333] In some embodiments, the third response message and / or the fourth response message further include indication information, which indicates whether the response message contains an information field corresponding to the second identifier, or indicates whether the response message carries the second identifier; and / or,

[0334] The third response message and / or the fourth response message further include indication information, which indicates whether the response message contains an information field corresponding to the configuration / scheduling information of the D2R message, or whether the response message carries the configuration / scheduling information of the D2R message.

[0335] In some embodiments, the third response message and the fourth response message are distributed on different time-domain resources on the time axis, or the third response message and the fourth response message are transmitted in a TDM manner, or the time-frequency resources carrying the third response message and the fourth response message do not overlap in the time domain.

[0336] In some embodiments, at least a portion of the information contained in the third response message and / or the fourth response message is carried in the PDU of the downlink MAC layer, and / or in the control signaling of the downlink layer 1.

[0337] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0338] According to the above embodiments, the limited processing power and / or limited energy of tag-type terminal devices can be efficiently utilized to receive downlink signals.

[0339] Third aspect of the embodiments

[0340] This application provides an information receiving device. This device may be, for example, a tag-type terminal device (referred to as the first device), or one or more components or parts configured on the tag-type terminal device. Contents identical to those in the first aspect of the embodiment will not be repeated.

[0341] Figure 6 is a schematic diagram of an information receiving device according to an embodiment of the present application. As shown in Figure 6, the information receiving device 600 according to an embodiment of the present application includes a transmitter 601 and a receiver 602.

[0342] The transmitter 601 sends a first message to the network device, the first message being related to a first identifier of the terminal device;

[0343] Receiver 602 receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier;

[0344] The receiver 602 also receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0345] In some embodiments, the first response message is received before the second response message.

[0346] In some embodiments, before the receiver receives the second response message, the transmitter sends a third message to the network device in response to the received first response message.

[0347] In some embodiments, the first response message and / or the second response message includes at least one of the following information fields:

[0348] Message type;

[0349] The first identifier of the terminal device.

[0350] In some embodiments, the first response message and / or the second response message further include at least one of the following information fields:

[0351] The second identifier of the terminal device;

[0352] Configuration / scheduling information for D2R messages.

[0353] In some embodiments, the first response message and / or the second response message further includes indication information, which indicates whether the first response message and / or the second response message contains an information field corresponding to the second identifier, or indicates whether the first response message and / or the second response message carries the second identifier; and / or,

[0354] The first response message and / or the second response message further include indication information, which indicates whether the response message contains an information field corresponding to the configuration / scheduling information of the D2R message, or indicates whether the first response message and / or the second response message carries the configuration / scheduling information of the D2R message.

[0355] In some embodiments, the second identifier is configured by the network device and is used at least for scheduling / configuring / instructing the terminal device to receive downlink information or send uplink information;

[0356] The configuration / scheduling information of the D2R message is configured by the network device and is used at least for scheduling / configuring / instructing the third message sent by the terminal device.

[0357] In some embodiments, the first message includes a first identifier of the terminal device, which is at least randomly generated by the terminal device.

[0358] In some embodiments, the first identifier in the first identifier information field of the second response message is the same as the first identifier in the first message sent by the terminal device, and / or the second identifier in the second identifier information field of the second response message is the same as the second identifier stored by the terminal device, and / or the first identifier in the first identifier information field of the second response message is the same as the second identifier stored by the terminal device.

[0359] In some embodiments, the terminal device receiving the second response message includes:

[0360] The terminal device assumes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed.

[0361] The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier;

[0362] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0363] Initiate the sending of D2R messages.

[0364] In some embodiments, the terminal device receiving the second response message further includes:

[0365] The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier;

[0366] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0367] Initiate the sending of D2R messages.

[0368] In some embodiments, the terminal device receiving the second response message further includes:

[0369] The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0370] Initiate the sending of D2R messages.

[0371] In some embodiments, the terminal device receiving the second response message further includes:

[0372] Initiate the sending of D2R messages.

[0373] In some embodiments, the terminal device receiving the second response message further includes:

[0374] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0375] In some embodiments, the terminal device receiving the second response message further includes:

[0376] The terminal device compares the information in the configuration / scheduling information field of the D2R message of the second response message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0377] In some embodiments, the terminal device receiving the second response message further includes:

[0378] When the second response message includes a second identification information field.

[0379] The terminal device sets the value in the second identification information field to the second identification and stores the second identification; or the terminal device stores the value in the second identification information field as the second identification; or the MAC entity of the terminal device does not perform any action / behavior related to the second identification; or...

[0380] The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

[0381] If the second response message does not contain a second identification information field.

[0382] The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification, or the MAC entity of the terminal device does not have any action / behavior related to the second identification.

[0383] In some embodiments, the terminal device receiving the second response message further includes:

[0384] If the second response message includes the configuration / scheduling information field of the D2R message,

[0385] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer; or,

[0386] The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

[0387] If the second response message does not contain the configuration / scheduling information field of the D2R message,

[0388] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer has reused the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

[0389] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0390] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The information receiving device 600 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies. The transmitter 601 and receiver 602 may be signal transceiver units, modules, circuits, etc. on the terminal side, or may include signal processing modules or circuits, chips, etc.

[0391] Furthermore, for simplicity, Figure 6 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0392] According to the above embodiments, the limited processing power and / or limited energy of tag-type terminal devices can be efficiently utilized to receive downlink signals.

[0393] Fourth aspect of the embodiment

[0394] This application provides an information transmission device. This device may be, for example, a network device, an intermediate node, or an auxiliary node, referred to as a second device, or it may be one or more components or parts configured in a network device, intermediate node, or auxiliary node. Contents identical to those in the embodiments of the first to third aspects will not be repeated.

[0395] Figure 7 is another schematic diagram of an information transmitting device according to an embodiment of this application. As shown in Figure 7, the information transmitting device 700 includes a transmitter 701 and a receiver 702.

[0396] The transmitter 701 sends an indication message to the terminal device, the indication message being at least used to instruct / configure / trigger the terminal device to send a first message;

[0397] Receiver 702 receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device;

[0398] The transmitter 701 also sends a third response message to the terminal device, the third response message being used at least in response to the first message;

[0399] The transmitter 701 also sends a fourth response message to the terminal device, the fourth response message being used at least in response to the first message.

[0400] In some embodiments, the third response message and / or the fourth response message are related to the first message, and / or the third response message and / or the fourth response message are related to the first identifier.

[0401] In some embodiments, before the transmitter sends a fourth response message to the terminal device, the receiver does not receive or fails to receive a third message from the terminal device in response to the third response message.

[0402] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0403] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The information transmitting device 700 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies. The transmitter 701 and receiver 702 may be signal transceiver units, modules, circuits, etc. on the network side, or may include signal processing modules or circuits, chips, etc.

[0404] Furthermore, for simplicity, Figure 7 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0405] According to the above embodiments, the limited processing power and / or limited energy of tag-type terminal devices can be efficiently utilized to receive downlink signals.

[0406] Fifth aspect of the embodiment

[0407] This application also provides a communication system, which can be referred to in Figures 1 to 3. The same content as in the embodiments of the first to fourth aspects will not be repeated. The communication system may include at least a terminal device and a network device. The terminal device is, for example, a tag-type terminal device in the scenario of Figures 1 to 3. The network device is, for example, a network device in the scenario of Figures 1 to 3, or an intermediate node in the scenario of Figure 2, or an auxiliary node in the scenario of Figure 3.

[0408] In some embodiments, the communication system 100 includes:

[0409] A terminal device sends a first message to a network device, the first message being related to a first identifier of the terminal device; receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier; and also receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0410] A network device that sends an indication message to a terminal device, the indication message being at least used to instruct / configure / trigger the terminal device to send a first message; and receives the first message sent by the terminal device, the first message being related to a first identifier of the terminal device.

[0411] This application also provides a terminal device, which may be the tag-type terminal device described in the foregoing embodiments, but this application is not limited to this and may also be other devices.

[0412] Figure 8 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 8, the terminal device 800 may include a processor 810 and a memory 820; for example, the memory 820 stores data and programs and is coupled to the processor 810. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0413] For example, processor 810 may be configured to execute a program to implement the information receiving method as described in the first aspect embodiment. For example, processor 810 may be configured to perform the following control: send a first message to a network device, the first message relating to a first identifier of a terminal device; receive a first response message sent by the network device, the first response message relating to the first message, and / or, the first response message relating to the first identifier; and further receive a second response message sent by the network device, the second response message relating to the first message, and / or, the second response message relating to the first identifier and / or the second identifier.

[0414] As shown in Figure 8, the terminal device 800 may further include a communication module 830; it may or may not have a power supply. It is worth noting that the terminal device 800 is not necessarily required to include all the components shown in Figure 8; these components are not essential. Furthermore, the terminal device 800 may also include components not shown in Figure 8, which can be found in existing technologies.

[0415] This application also provides a network device, which can be the network device of the foregoing embodiments, such as a base station, an intermediate node of the foregoing embodiments, or an auxiliary node of the foregoing embodiments. However, this application is not limited to these, and it can also be other devices.

[0416] Figure 9 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 9, the network device 900 may include: a processor 910 (e.g., a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores an information processing program 930, and executes the program 930 under the control of the processor 910.

[0417] For example, processor 910 may be configured to execute a program to implement the information transmission method as described in the second aspect of the embodiment. For example, processor 910 may be configured to perform the following control: send an indication message to a terminal device, the indication message being at least used to instruct / configure / trigger the terminal device to send a first message; receive the first message sent by the terminal device, the first message relating to a first identifier of the terminal device; further send a third response message to the terminal device, the third response message being at least used to respond to the first message; and further send a fourth response message to the terminal device, the fourth response message being at least used to respond to the first message.

[0418] In addition, as shown in Figure 9, the network device 900 may also include a transceiver 940 and an antenna 950, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the network device 900 does not necessarily have to include all the components shown in Figure 9; in addition, the network device 900 may also include components not shown in Figure 9, which can be referred to in the prior art.

[0419] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the information receiving method described in the first aspect of the embodiment.

[0420] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the information receiving method described in the first aspect of the embodiment.

[0421] This application also provides a computer program in which, when executed in a network device, intermediate node, or auxiliary node, the program causes the network device, intermediate node, or auxiliary node to perform the information transmission method described in the second aspect of the embodiment.

[0422] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device, an intermediate node, or an auxiliary node to execute the information transmission method described in the second aspect of the embodiment.

[0423] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0424] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0425] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0426] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0427] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0428] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0429] 1. An information receiving method, comprising:

[0430] The terminal device sends a first message to the network device, the first message being related to a first identifier of the terminal device;

[0431] The terminal device receives a first response message sent by the network device, wherein the first response message is related to the first message and / or the first response message is related to the first identifier;

[0432] The terminal device receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

[0433] 2. According to the information receiving method described in Appendix 1, the first identifier in the first identifier information field of the first response message is the same as the first identifier in the first message sent by the terminal device.

[0434] 3. The information receiving method according to Appendix 1 or 2, wherein the terminal device receiving the first response message includes:

[0435] The terminal device assumes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed.

[0436] The terminal device sets the value in the second identifier information field of the first response message as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier field as the second identifier;

[0437] The application or storage of the information in the configuration / scheduling information field of the D2R message in the first response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer;

[0438] Initiate the sending of D2R messages.

[0439] 4. The information receiving method according to Appendix 1 or 2, wherein the terminal device receiving the first response message further includes:

[0440] If the first response message contains a second identification information field...

[0441] The terminal device sets the value in the second identifier information field as the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier;

[0442] If the second response message does not contain a second identification information field.

[0443] The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification.

[0444] 5. The information receiving method according to Appendix 1 or 2, wherein the terminal device receiving the first response message further includes:

[0445] If the first response message contains a configuration / scheduling information field for a D2R message,

[0446] The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer;

[0447] If the first response message does not contain the configuration / scheduling information field of the D2R message,

[0448] The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer reuses the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message.

[0449] 6. According to the information receiving method described in Appendix 1, the terminal device sending a first message to the network device includes:

[0450] The terminal device generates the value of the first identifier;

[0451] Use the stated value to set / fill the information field corresponding to the first identifier in the first message;

[0452] Instruct the physical layer to send the first message at the selected access time.

[0453] 7. The information receiving method according to Appendix 6, wherein the terminal device sending the first message to the network device further includes:

[0454] The terminal device stores the generated first identifier.

[0455] 8. A method for sending information, comprising:

[0456] The network device sends an indication message to the terminal device, the indication message being used at least to instruct / configure / trigger the terminal device to send a first message;

[0457] The network device receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device;

[0458] The network device sends a third response message to the terminal device, the third response message being at least used to respond to the first message;

[0459] The network device sends a fourth response message to the terminal device, the fourth response message being used at least in response to the first message.

[0460] 9. The information transmission method according to Appendix 8, wherein the third response message and / or the fourth response message includes at least one of the following information fields:

[0461] Message type;

[0462] The first identifier of the terminal device.

[0463] and / or

[0464] The third response message and / or the fourth response message further include at least one of the following information fields:

[0465] The second identifier of the terminal device;

[0466] Configuration / scheduling information for D2R messages.

[0467] 10. The information transmission method according to Appendix 9, wherein,

[0468] The third response message and / or the fourth response message further include indication information, which indicates whether the response message contains an information field corresponding to the second identifier, or whether the response message carries the second identifier; and / or,

[0469] The third response message and / or the fourth response message further include indication information, which indicates whether the response message contains an information field corresponding to the configuration / scheduling information of the D2R message, or whether the response message carries the configuration / scheduling information of the D2R message.

Claims

1. An information receiving device, comprising: A transmitter that sends a first message to a network device, the first message being related to a first identifier of a terminal device; A receiver that receives a first response message sent by the network device, the first response message being related to the first message, and / or the first response message being related to the first identifier; The receiver also receives a second response message sent by the network device, the second response message being related to the first message, and / or the second response message being related to the first identifier and / or the second identifier.

2. The apparatus according to claim 1, wherein, The first response message was received before the second response message.

3. The apparatus according to claim 2, wherein, Before the receiver receives the second response message, the transmitter sends a third message to the network device in response to the received first response message.

4. The apparatus according to claim 2, wherein, The first response message and / or the second response message include at least one of the following information fields: Message type; The first identifier of the terminal device.

5. The apparatus according to claim 4, wherein, The first response message and / or the second response message further include at least one of the following information fields: The second identifier of the terminal device; Configuration / scheduling information for D2R messages.

6. The apparatus according to claim 5, wherein, The first response message and / or the second response message further include indication information, which indicates whether the first response message and / or the second response message contains an information field corresponding to the second identifier, or indicates whether the first response message and / or the second response message carries the second identifier; and / or, The first response message and / or the second response message further include indication information, which indicates whether the response message contains an information field corresponding to the configuration / scheduling information of the D2R message, or indicates whether the first response message and / or the second response message carries the configuration / scheduling information of the D2R message.

7. The apparatus according to claim 5, wherein, The second identifier is configured by the network device and is used at least for scheduling / configuring / instructing the terminal device to receive downlink information or send uplink information; The configuration / scheduling information of the D2R message is configured by the network device and is used at least for scheduling / configuring / instructing the third message sent by the terminal device.

8. The apparatus according to claim 1, wherein, The first message contains a first identifier of the terminal device, which is at least randomly generated by the terminal device.

9. The apparatus according to claim 1, wherein, The first identifier in the first identifier information field of the second response message is the same as the first identifier in the first message sent by the terminal device, and / or the second identifier in the second identifier information field of the second response message is the same as the second identifier stored by the terminal device, and / or the first identifier in the first identifier information field of the second response message is the same as the second identifier stored by the terminal device.

10. The apparatus according to claim 9, wherein, The receiver receives the second response message, including: The terminal device assumes or assumes that the contention has been successfully resolved, or that the random access process has been successfully completed. The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier; The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer; Initiate the sending of D2R messages.

11. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: The terminal device sets the value in the second identifier information field of the second response message to the second identifier and stores the second identifier, or the terminal device stores the value in the second identifier information field as the second identifier, or the MAC entity of the terminal device does not have any action / behavior related to the second identifier; The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer; Initiate the sending of D2R messages.

12. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: The application or storage of the information in the configuration / scheduling information field of the D2R message in the second response message, and the information in the configuration / scheduling information field of the D2R message is indicated / transmitted to the physical layer; Initiate the sending of D2R messages.

13. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: Initiate the sending of D2R messages.

14. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier.

15. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: The terminal device compares the information in the configuration / scheduling information field of the D2R message of the second response message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer.

16. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: When the second response message includes a second identification information field. The terminal device sets the value in the second identifier information field to the second identifier and stores the second identifier; or the terminal device stores the value in the second identifier information field as the second identifier; or the MAC entity of the terminal device does not perform any action / behavior related to the second identifier; or... The terminal device compares the value in the second identifier information field of the second response message with the stored second identifier. If they are the same, the MAC entity of the terminal device has no action / behavior related to the second identifier. Otherwise, the terminal device sets the value in the second identifier information field to the second identifier and updates the stored second identifier. If the second response message does not contain a second identification information field. The terminal device sets the value in the first identification information field as the second identification and stores the second identification, or the terminal device stores the value in the first identification information field as the second identification, or the MAC entity of the terminal device does not have any action / behavior related to the second identification.

17. The apparatus according to claim 9, wherein, The receiver receiving the second response message also includes: If the second response message includes the configuration / scheduling information field of the D2R message, The terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and instructs / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer; or, The terminal device compares the information in the configuration / scheduling information field of the D2R message with the stored configuration / scheduling information. If they are the same, the MAC entity of the terminal device does not perform any action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer. Otherwise, the terminal device applies or stores the information in the configuration / scheduling information field of the D2R message, and indicates / transmits the information in the configuration / scheduling information field of the D2R message to the physical layer. If the second response message does not contain the configuration / scheduling information field of the D2R message, The terminal device indicates that the physical layer has not configured or scheduled D2R, or indicates that the physical layer has reused the time-frequency resources of the first message to send the D2R message, or the MAC entity of the terminal device has no action / behavior related to the configuration / scheduling information of the D2R message, or indicates / transmits the stored information to the physical layer.

18. An information transmitting device, comprising: A transmitter that sends an indication message to a terminal device, the indication message being used at least to instruct / configure / trigger the terminal device to send a first message; A receiver that receives a first message sent by the terminal device, the first message being related to a first identifier of the terminal device; The transmitter also sends a third response message to the terminal device, the third response message being at least used to respond to the first message; The transmitter also sends a fourth response message to the terminal device, the fourth response message being at least used to respond to the first message.

19. The apparatus according to claim 18, wherein, The third response message and / or the fourth response message are related to the first message, and / or the third response message and / or the fourth response message are related to the first identifier; Before the transmitter sends the fourth response message to the terminal device, the receiver does not receive or fails to receive the third message from the terminal device in response to the third response message.

20. A communication system, comprising: A terminal device sends a first message to a network device, the first message being related to a first identifier of the terminal device; Receive a first response message sent by the network device, wherein the first response message is related to the first message and / or the first response message is related to the first identifier; receive a second response message sent by the network device, wherein the second response message is related to the first message and / or the second response message is related to the first identifier and / or the second identifier; A network device that sends an indication message to a terminal device, the indication message being at least used to instruct / configure / trigger the terminal device to send a first message; and receives the first message sent by the terminal device, the first message being related to a first identifier of the terminal device.