Response message receiving method and apparatus

Abstract

Provided in the present disclosure are a response message receiving method and apparatus, and a device and a storage medium. The method comprises: sending at least one of data and signaling to a network device, and waiting to receive a response message sent by the network device. The present disclosure can improve the accuracy of response message reception, and thus can improve the communication quality.

Description

Response message receiving method and device Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method, apparatus, device, and storage medium for receiving a response message. Background Art

[0002] In communication systems, the technology for early data transmission by mobile terminals is becoming increasingly mature. Mobile Originated Extended Data Transfer (MO-EDT) is a mechanism for a mobile terminal to send data to the core network. Through MO-EDT, a mobile terminal can transmit data to the core network for further processing and distribution. In some embodiments, the EDT process can be based on a random access process.

[0003] Summary of the Invention

[0004] The present disclosure proposes a response message receiving method, apparatus, device and storage medium to improve the accuracy of response message reception and improve communication quality.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for receiving a response message is proposed, the method being executed by a terminal, the method including:

[0006] Send at least one of data and signaling to the network device, and wait to receive a response message sent by the network device.

[0007] According to a second aspect of an embodiment of the present disclosure, a method for receiving a response message is provided, the method being executed by a network device, the method comprising:

[0008] receiving at least one of data and signaling sent by a terminal, and sending a response message to the terminal.

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

[0010] The transceiver module is used to send at least one of data and signaling to the network device and wait to receive a response message sent by the network device.

[0011] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, comprising:

[0012] The transceiver module is used to receive at least one of data and signaling sent by the terminal and send a response message to the terminal.

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

[0014] one or more processors;

[0015] The terminal is used to execute the response message receiving method described in any one of the first aspects.

[0016] According to a sixth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0017] one or more processors;

[0018] Wherein, the network device is used to execute the response message sending method described in any one of the second aspects.

[0019] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the response message receiving method described in any one of the first aspects and the network device is configured to implement the response message sending method described in any one of the second aspects.

[0020] According to the eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the response message receiving method as described in any one of the first aspect or the response message sending method as described in any one of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0022] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0023] FIG2A is a schematic diagram illustrating an example of a control plane CIoT EPS optimized MO-EDT according to an embodiment of the present disclosure;

[0024] FIG2B is a schematic diagram illustrating an example of a control plane CIoT 5GS optimized MO-EDT provided by an embodiment of the present disclosure;

[0025] FIG2C is a schematic diagram illustrating an example of a user plane CIoT EPS optimized MO-EDT according to an embodiment of the present disclosure;

[0026] FIG2D is a schematic diagram illustrating an example of a location where a terminal identification ID appears, provided by an embodiment of the present disclosure;

[0027] FIG2E is a schematic diagram illustrating an example of a location where a terminal identification ID appears, provided by an embodiment of the present disclosure;

[0028] FIG2F is a schematic diagram illustrating an example of a location where a terminal identification ID appears, provided by an embodiment of the present disclosure;

[0029] FIG2G is a schematic diagram illustrating an example of a location where a terminal identification ID appears, provided by an embodiment of the present disclosure;

[0030] FIG3A is an interactive diagram of a response message receiving method provided by an embodiment of the present disclosure;

[0031] FIG4A is a schematic flow chart of a method for receiving a response message according to another embodiment of the present disclosure;

[0032] FIG5A is a schematic diagram of a flow chart of a method for sending a response message according to another embodiment of the present disclosure;

[0033] FIG6A is a schematic flow chart of a method for receiving a response message according to another embodiment of the present disclosure;

[0034] FIG7A is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure;

[0035] FIG7B is a schematic diagram of the structure of a network device provided by an embodiment of the present disclosure;

[0036] FIG8A is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0037] FIG8B is a schematic structural diagram of a chip provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] The present disclosure proposes a response message receiving method, apparatus, device and storage medium to improve the accuracy of response message reception and improve communication quality.

[0039] According to a first aspect of an embodiment of the present disclosure, a method for receiving a response message is proposed, the method being executed by a terminal, the method including:

[0040] Send at least one of data and signaling to the network device, and wait to receive a response message sent by the network device.

[0041] In the above embodiment, a response message receiving mechanism can be provided, which can wait for receiving a response message after sending data or signaling, thereby improving the accuracy of receiving the response message, improving the transmission efficiency of the response message, reducing the situation where data transmission failures caused by inaccurate response message reception, increasing the capacity of the response message, and improving the communication quality.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, sending at least one of data and signaling to a network device and waiting to receive a response message sent by the network device includes:

[0043] The device sends a message 3 Msg3 of Extended Data Transfer (EDT) Msg1-Less EDT to the network device, and waits to receive a message 4 Msg4 of Msg1-Less EDT sent by the network device.

[0044] In the above embodiment, a Msg4 receiving mechanism can be provided. After sending message 3Msg3 of Msg1-Less EDT, the mechanism can wait for receiving Msg4 of Msg1-Less EDT. This can improve the accuracy of receiving Msg4 of Msg1-Less EDT, improve the transmission efficiency of Msg4 of Msg1-Less EDT, reduce the situation where data transmission failure is caused by inaccurate reception of Msg4, increase the capacity of Msg4, and improve communication quality.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the Msg4 does not include a radio resource control (RRC) message.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the message 3 Msg3 of the Msg1-Less EDT is at least one of the following:

[0047] Control plane Cellular Internet of Things (CIOT) Evolved Packet System (EPS) optimized uplink (UL) RRC EarlyDataRequest message and control plane CIOT EPS optimization UL RRCEarlyDataRequest message;

[0048] Control plane 5G system 5GS optimization uplink ULRRC EarlyDataRequest message control plane 5GS optimization ULRRCEarlyDataRequest message;

[0049] User plane CIOT EPS optimization uplink user data transmitted on DTCH multiplexed with UL RRC Connection Resume Request message on CCCH;

[0050] User plane 5GS optimization uplink user data transmitted on DTCH multiplexed with UL RRC Connection Resume Request message on CCCH.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the Msg1-Msg3 of the Less EDT is sent using competitive resources, and the Msg4 includes terminal identification information.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal identification information is at least one of the following:

[0053] The first X bits of the Common Control Channel (CCCH) service data unit (SDU) included in Msg3 of the Msg1-Less EDT, where X is any natural number from 1 to 48;

[0054] The last T bits of the first R bits of the CCCH SDU included in Msg3 of the Msg1-Less EDT, where T is less than or equal to R, R is any natural number from 1 to 64, and T is any natural number from 1 to 48;

[0055] The Msg3 of the Msg1-Less EDT includes N bits of the CCCH SDU starting from the Mth bit, where the value of M is any natural number from 1 to 48, and the value of N is any natural number from 1 to 48.

[0056] In the above embodiment, the specific type of the terminal identification information included in Msg4 can be provided, the terminal identification information can be clarified, the accuracy of the terminal identification information provided can be improved, and the accuracy of sending Msg4 can be improved.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the CCCH SDU is at least one of the following:

[0058] RRC advance data request;

[0059] RRC connection resumption request Connection Resume Request.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal identification information is carried by at least one of the following:

[0061] Layer 1 L1 signaling;

[0062] Media Access Control-Control Elements (MAC CE) signaling;

[0063] Media Access Control-MAC sub header.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the L1 signaling is physical downlink control channel (PDCCH) downlink control information (DCI).

[0065] In combination with some embodiments of the first aspect, in some embodiments, the MAC CE signaling is at least one of the following:

[0066] Terminal contention resolution identifier MAC CE;

[0067] Newly defined MAC CE.

[0068] In combination with some embodiments of the first aspect, in some embodiments, the Msg4 includes a demodulation reference signal (Dedicated Reference Signal, DMRS) resource identifier resource ID.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the DMRS resource ID is carried in at least one of the following:

[0070] PDCCH DCI;

[0071] MAC CE;

[0072] MAC subheader of the response message.

[0073] In combination with some embodiments of the first aspect, in some embodiments, the DMRS resource ID is the DMRS resource ID used by the terminal to send the Msg3 of the Msg1-Less EDT.

[0074] In combination with some embodiments of the first aspect, in some embodiments, the Msg4 includes an orthogonal cover code (OCC) resource identifier resource ID.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, the OCC resource ID is carried in at least one of the following:

[0076] PDCCH DCI;

[0077] MAC CE;

[0078] MAC subheader of the response message.

[0079] In combination with some embodiments of the first aspect, in some embodiments, the OCC resource ID is the OCC resource ID used by the terminal to send Msg3 of the Msg1-Less EDT.

[0080] In combination with some embodiments of the first aspect, in some embodiments, Msg3 of the Msg1-Less EDT is sent using non-competitive resources, and the Msg4 includes first indication information, and the first indication information is used to indicate confirmation of receipt of Msg3.

[0081] In the above embodiment, a mechanism for confirming the receipt of Msg3 can be provided, which can clarify the information that Msg3 was successfully transmitted and improve the communication quality.

[0082] In combination with some embodiments of the first aspect, in some embodiments, the Msg1-Less EDT is a control plane (CP) Msg1-Less EDT.

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

[0084] When the network device does not send the RRC early data completion message, the Msg4 sent by the network device is received, wherein the Msg4 carries L1 confirmation ACK information.

[0085] In combination with some embodiments of the first aspect, in some embodiments, the Msg4 includes second indication information, and the second indication information is used to indicate network fallback.

[0086] In combination with some embodiments of the first aspect, in some embodiments, the Msg4 includes third indication information, and the third indication information is used to indicate the adjustment of the number of repetitions of the Msg3 of the Msg1-Less EDT.

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

[0088] The Msg3 repetition count adjustment sent by the network device is received, and the stored Msg3 repetition count of the Msg1-Less EDT is updated.

[0089] In the above embodiment, a mechanism for updating the number of Msg3 repetitions of the Msg1-Less EDT may be provided, thereby improving the accuracy of the stored number of Msg3 repetitions of the Msg1-Less EDT and improving the communication quality.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the first indication information, the second indication information or the third indication information is PDCCH DCI.

[0091] According to a second aspect of an embodiment of the present disclosure, a method for sending a response message is proposed, the method being executed by a network device, the method comprising:

[0092] receiving at least one of data and signaling sent by a terminal, and sending a response message to the terminal.

[0093] In the above embodiment, a response message sending mechanism can be provided, which can send a response message to the terminal after receiving data or signaling, thereby improving the accuracy of response message sending, improving the transmission efficiency of response messages, reducing the situation where data transmission failures caused by inaccurate response message sending, increasing the capacity of response messages, and improving communication quality.

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

[0095] The transceiver module is used to send at least one of data and signaling to the network device and wait to receive a response message sent by the network device.

[0096] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, comprising:

[0097] The transceiver module is used to receive at least one of data and signaling sent by the terminal and send a response message to the terminal.

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

[0099] one or more processors;

[0100] The terminal is used to execute the response message receiving method described in any one of the first aspects.

[0101] According to a sixth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0102] one or more processors;

[0103] Wherein, the network device is used to execute the response message sending method described in any one of the second aspects.

[0104] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the response message receiving method described in any one of the first aspects and the network device is configured to implement the response message sending method described in any one of the second aspects.

[0105] According to the eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the response message receiving method as described in any one of the first aspect or the response message sending method as described in any one of the second aspect.

[0106] The present disclosure provides a method for receiving a response message. In some embodiments, the terms "response message receiving method" and "information processing method" and "communication method" are interchangeable; "response message receiving device" and "information processing device" and "communication device" are interchangeable; and "information processing system" and "communication system" are interchangeable.

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

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

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

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

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

[0112] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

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

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

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

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

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

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

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

[0120] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0121] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0122] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

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

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

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

[0126] FIG1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

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

[0128] In some embodiments, the network device 102 may include, for example, at least one of an access network device and a core network device.

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

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

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

[0132] In some embodiments, a core network device may be a device comprising one or more network elements, or may be multiple devices or device groups, each of which includes all or part of the one or more network elements. The network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0133] In some embodiments, the core network device may be a single device including a first network element, a second network element, etc., or may be a plurality of devices or a group of devices, each including all or part of the first network element, the second network element, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0134] In some embodiments, the first network element is, for example, an Access and Mobility Management Function (AMF).

[0135] In some embodiments, the first network element is used to "be responsible for functions such as terminal identity authentication, authorization, registration, mobility management and connection management", but the name is not limited to this.

[0136] In some embodiments, the second network element is, for example, a Session Management Function (SMF).

[0137] In some embodiments, the second network element is used to "be responsible for interacting with the decoupled data plane, creating, updating and deleting protocol data unit (PDU) sessions, and user plane function (UPF) management session context", and the name is not limited thereto.

[0138] In some embodiments, the third network element is, for example, a user plane function (UPF).

[0139] In some embodiments, the third network element is used to "implement user plane interface services of the 5G network, including but not limited to: air interface, routing, QoS (quality of service) and security of the network architecture", and the name is not limited to this.

[0140] In some embodiments, the third network element may be independent of the core network device.

[0141] In some embodiments, the third network element may be part of a core network device.

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

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

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

[0145] In some embodiments, Mobile Originated Extended Data Transfer (MO-EDT) is a mechanism for a mobile terminal to send data to the core network. Through MO-EDT, the mobile terminal can transmit data to the core network for further processing and distribution.

[0146] In some embodiments, MO-EDT allows selective uplink data transmission followed by downlink data transmission during the random access procedure.

[0147] In some embodiments, MO-EDT is triggered when upper layers have requested the establishment or resumption of an RRC connection for mobile originated data (i.e., not signaling or SMS) and the uplink data size is less than or equal to the TB size indicated in the system information. MO-EDT is not used for data on the control plane when using user plane cellular IoT (CIoT) Evolved Packet System (EPS) / 5G System (5GS) optimization.

[0148] In some embodiments, MO-EDT is only applicable to narrowband low complexity (BL) terminals, terminals in enhanced coverage, and narrowband Internet of Things (NB-IoT) terminals.

[0149] In some embodiments, in the control plane CIoT EPS / 5GS optimized MO-EDT, the control plane CIoT EPS optimized MO-EDT defined in some embodiments and the controller plane CIoT 5GS optimized MO-EDT defined in some embodiments are characterized as follows:

[0150] Sending uplink user data in a Non-Access Stratum (NAS) message concatenated with an Uplink (UL) RRC Early Data Request message on a Common Control Channel (CCCH);

[0151] Downlink user data is optionally transmitted in a NAS message concatenated with an RRC Early Data Complete message on the CCCH.

[0152] The state RRC CONNECTED is not switched to.

[0153] In some embodiments, the MO-EDT process for control plane CIoT EPS optimization and control plane CIoT 5GS optimization is shown in Figures 2A and 2B, respectively. Figure 2A is an example schematic diagram of a control plane CIoT EPS optimized MO-EDT provided by an embodiment of the present disclosure, and Figure 2B is an example schematic diagram of a control plane CIoT 5GS optimized MO-EDT provided by an embodiment of the present disclosure, including:

[0154] 0. Following a connection establishment request for mobile originated data from upper layers, the terminal initiates the MO-EDT procedure and selects a random access preamble configured for EDT.

[0155] 1. The terminal sends an RRC Early Data Request message for connecting user data on CCCH. For EPS enabled in the cell, or for 5GS, the terminal can instruct the Assistance (AS) to release the assistance information.

[0156] 2. For EPS, the eNB initiates the S1 Application Protocol (S1-AP) Initial Terminal Message procedure to forward NAS messages and establish an S1 connection. For 5GS, the ng eNB initiates the ng-AP Initial Terminal Message procedure to forward NAS messages. An Evolved Node B (eNB) in an LTE (Long-Term Evolution) network can indicate during this procedure that the connection is triggered for EDT.

[0157] 3. For EPS, the MME requests the Serving GateWay (S-GW) to reactivate the EPS bearer for the terminal. For 5GS, the AMF determines the PDU session contained in the NAS message.

[0158] 4. For EPS, MME sends uplink data to S-GW. For 5GS, AMF sends PDU session ID and uplink data to SMF, and SMF forwards the uplink data to UPF.

[0159] 5. For EPS, if downlink data is available, the S-GW sends the downlink data to the Mobility Management Entity (MME). For 5GS, if downlink information is available, the UPF forwards the downlink information to the SMF, and the SFM sends the downlink information to the AMF.

[0160] 6. If downlink data is received from the S-GW or SMF, the MME or AMF forwards the data to the eNB or ng eNB via the DL NAS Transfer procedure and may also indicate whether further data is expected. Otherwise, the MME or AMF may trigger the Connection Establishment Indication procedure and also indicate whether further data is expected.

[0161] 7. If no further data is expected, the (ng-)eNB may send an RRC Early Data Complete message on CCCH to keep the terminal in RRC_IDLE. If downlink data is received in step 6, they are concatenated in the RRC Early Data Complete message.

[0162] 8. For EPS, the S1 connection is released and the EPS bearer is deactivated. For 5GS, the AN release procedure is initiated.

[0163] NOTE 1: If the MME / AMF or (ng-)eNB decides to move the terminal in RRC_CONNECTED mode, an RRCConnectionSetup message is sent in step 7 to fall back to the legacy RRC connection establishment procedure; the (ng-)eNB shall discard the zero-length NAS PDU received in the RRCConnectionSetupComplete message.

[0164] NOTE 2: If neither RRC Early Data Complete nor RRC Connection Setup is received in response to an RRC Early Data Request, the terminal considers that the UL data transmission is unsuccessful.

[0165] In some embodiments, in MO-EDT for user plane CIoT EPS / 5GS optimization, features of MO-EDT for user plane CIoT EPS optimization defined in some embodiments and MO-EDT for user plane CIoT 5GS optimization defined in some embodiments are as follows:

[0166] The Next Hop Chaining Count has been provided to the terminal in the RRC Connection Release message with a suspend indication;

[0167] Uplink user data is transmitted on the DTCH multiplexed with the UL RRC Connection Resume Request message on the CCCH;

[0168] Optionally, downlink user data is transmitted on the DTCH multiplexed with the DL RRC Connection Release message on the DCCH;

[0169] The short resume Media Access Control-identify (MAC-I) is reused as the authentication token for the RRC Connection Resume Request message and is calculated using the integrity key from the previous connection;

[0170] User data in uplink and downlink is encrypted. The key is derived using the Next Hop Chaining Count hopping configuration provided in the RRC Connection Release message of the previous RRC connection;

[0171] The RRC Connection Release message is integrity protected and encrypted using the newly derived key;

[0172] No transition to the RRC connected state CONNECTED.

[0173] In some embodiments, FIG2C is a schematic diagram illustrating an example of a MO-EDT process for user plane CIoT EPS optimization provided by an embodiment of the present disclosure, including:

[0174] 0. Following a connection resumption request for mobile originated data from upper layers, the terminal initiates the MO-EDT procedure and selects a random access preamble configured for EDT.

[0175] 1. The terminal sends an RRC Connection Resume Request to the eNB, including its resume identifier ResumeID, establishment cause, and authentication token. The terminal resumes all signaling radio bearers (SRBs) and data radio bearers (DRBs), uses the Next Hop Chaining Count provided in the RRC Connection Release message of the previous RRC connection to derive new security keys, and re-establishes AS security. User data is encrypted and transmitted on the Dedicated Traffic CHannel (DTCH), which is multiplexed with the RRC Connection Resume Request message on the CCCH. If enabled in the cell, the terminal can instruct the AS to release auxiliary information.

[0176] 2. The eNB initiates the S1-AP context restoration procedure to restore the S1 connection and reactivate the S1-U bearer.

[0177] 3. The MME requests the S-GW to reactivate the S1-U bearer for the terminal.

[0178] 4. The MME confirms the terminal context recovery to the eNB.

[0179] 5. Uplink data is transmitted to the S-GW.

[0180] 6. If downlink data is available, the S-GW sends the downlink data to the eNB.

[0181] 7. If no further data is expected, the eNB may initiate suspension of the S1 connection and deactivation of the S1-U bearer.

[0182] 8. The eNB sends an RRC Connection Release message to keep the terminal in RRC_IDLE. This message includes the Release Cause (set to RRC Suspend), the resumeID, the Next Hop Chaining Count, and the DRBC Continue ROHC, which are stored by the terminal. If downlink data is received in step 6, it is encrypted and sent on the DTCH multiplexed with the RRC Connection Release message on the DCCH. The process ends with the receipt of Hybrid Automatic Repeat reQuest (HARQ) feedback (ARQ) confirming the successful DL transmission.

[0183] In some embodiments, some EDT procedures are based on random access procedures. To send uplink data, the terminal must go through at least four steps:

[0184] 1. Send Msg1;

[0185] 2. Receive Msg2;

[0186] 3. Send Msg3;

[0187] 4. Receive Msg4.

[0188] In some embodiments, 3GPP is studying the use of OCC (orthogonal cover code) to increase uplink capacity. However, this uplink capacity increase can only increase the capacity of Msg1 and Msg3. Msg2 and Msg4 will become bottlenecks that restrict system capacity. To solve this problem, 3GPP is studying an EDT method without Msg1 / Msg2, that is, only Msg3 and Msg4, and calls it Msg1-Less EDT. A key focus of Msg3 research is how to directly send Msg3 without Msg1 and Msg2. The focus of Msg4 research is how to efficiently transmit Msg4 to increase Msg4 capacity.

[0189] In the case of using competitive resources to send Msg3, the terminal identification ID needs to be carried in Msg4. In some embodiments, the CCCH SDU in Msg3 already carries the terminal ID. Figures 2D to 2G show the location of the terminal ID in the ASN.1 structure of the RRC resume request and RRC early data request messages in the ASN.1 bit stream, where:

[0190] FIG2D shows an example schematic diagram of an RRC resume request with resume ID, wherein in FIG2D , the Resume Identity (a type of terminal ID) consists of 40 bits starting from the 5th bit.

[0191] FIG2E shows an example schematic diagram of an RRC resume request with Truncated resume ID, wherein in FIG2E , the Resume Identity (a type of terminal ID) consists of 24 bits starting from the 5th bit.

[0192] FIG2F shows an example schematic diagram of an Rrc Early Data Request (connected to EPC), wherein in FIG2F , the S-TMSI (a type of terminal ID) consists of 40 bits starting from the 8th bit.

[0193] FIG2G shows an example schematic diagram of Rrc Early Data Request (connected to 5GC), wherein, in FIG2F , the S-TMSI (a type of terminal ID) is 48 bits starting from the 10th bit.

[0194] In summary, the starting bit of the terminal ID in the CCCH SDU is not the first bit, but starts from the 5th / 8th / 10th bit. Therefore, it is best not to start the terminal ID in the CCCH SDU from the first bit.

[0195] The following describes in detail a response message receiving method, apparatus, device, and storage medium provided by embodiments of the present disclosure with reference to the accompanying drawings.

[0196] FIG3A is an interactive diagram of a response message receiving method provided by an embodiment of the present disclosure. As shown in FIG3A , the method may include the following steps:

[0197] Step S3101: receiving message 3 Msg3 of advance data transmission Msg1-Less EDT without Msg1 from a terminal, and the network device sends message 4 Msg4 of Msg1-Less EDT to the terminal;

[0198] In one embodiment of the present disclosure, the early data transmission Msg1-Less EDT without Msg1 may refer to an EDT without Msg1 / Msg2, for example, an EDT with only Msg3 and Msg4.

[0199] For example, in one embodiment of the present disclosure, the Msg4 does not include a radio resource control RRC message.

[0200] In some embodiments, the names of messages and the like are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0201] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0202] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0203] Step S3102: Sending message 3 Msg3 of the advance data transmission Msg1-Less EDT that does not require Msg1 to the network device, and the terminal waits to receive message 4 Msg4 of the Msg1-Less EDT sent by the network device.

[0204] In one embodiment of the present disclosure, Msg4 does not include a radio resource control RRC message.

[0205] In one embodiment of the present disclosure, the message 3 Msg3 of Msg1-Less EDT is at least one of the following:

[0206] Control plane Cellular Internet of Things (CIOT) Evolved Packet System (EPS) optimized uplink (UL) RRC EarlyDataRequest message and control plane CIOT EPS optimization UL RRCEarlyDataRequest message;

[0207] Control plane 5G system 5GS optimization uplink ULRRC EarlyDataRequest message control plane 5GS optimization ULRRCEarlyDataRequest message;

[0208] User plane CIOT EPS optimization uplink user data transmitted on DTCH multiplexed with UL RRC Connection Resume Request message on CCCH;

[0209] User plane 5GS optimization uplink user data transmitted on DTCH multiplexed with UL RRC Connection Resume Request message on CCCH.

[0210] In one embodiment of the present disclosure, Msg1-Less EDT message 3, Msg3, includes a control plane cellular Internet of Things (CIOT) evolved packet system (EPS) optimized uplink (UL) RRC EarlyDataRequest message and a control plane CIOT EPS optimization UL RRC EarlyDataRequest message.

[0211] In one embodiment of the present disclosure, message 3Msg3 of Msg1-Less EDT includes an uplink UL RRC early data request EarlyDataRequest message of control plane 5G system 5GS optimization.

[0212] In one embodiment of the present disclosure, Msg1-Less EDT message 3, Msg3, includes uplink data transmitted on a dedicated traffic channel (DTCH) optimized by user plane CIOT EPS and an uplink UL RRC Connection Resume Request message transmitted on a common control channel (CCCH) multiplexed with the uplink data.

[0213] In one embodiment of the present disclosure, message 3 Msg3 of Msg1-Less EDT includes uplink data optimized by the user plane 5GS and transmitted on a dedicated traffic channel DTCH, and an uplink UL RRC Connection Resume Request message ConnectionResumeRequest transmitted on a common control channel CCCH multiplexed with the uplink data. User plane 5GS optimization Uplink user data transmitted on DTCH multiplexed with UL RRC Connection Resume Request message on CCCH.

[0214] In one embodiment of the present disclosure, Msg3 of Msg1-Less EDT is sent using competitive resources, and Msg4 includes terminal identification information.

[0215] For example, in one embodiment of the present disclosure, the terminal may use competitive resources to send Msg3 of Msg1-Less EDT, and the terminal may use non-competitive resources to send Msg3 of Msg1-Less EDT. This embodiment of the present disclosure is not limited to this.

[0216] In one embodiment of the present disclosure, when the terminal uses competitive resources to send Msg3 of Msg1-Less EDT, the terminal is not configured with a unique OCC resource or DMRS resource for the competitive resources. When the terminal uses competitive resources to send Msg3 of Msg1-Less EDT, the terminal can, for example, select an OCC resource from an OCC resource pool, or select a DMRS resource from a DMRS resource pool.

[0217] For example, in one embodiment of the present disclosure, when a terminal uses non-competitive resources to send Msg3 of Msg1-Less EDT, the non-competitive resources may be, for example, preconfigured uplink resources (PUR) that include a terminal-specific OCC resource configuration. The non-competitive resources may be, for example, sent by a network device to the terminal via dedicated signaling.

[0218] In one embodiment of the present disclosure, the terminal identification information is at least one of the following:

[0219] The first X bits of the CCCH service data unit (SDU) included in Msg3 of Msg1-Less EDT, where X is a natural number from 1 to 48;

[0220] The last T bits of the first R bits of the CCCH SDU included in Msg3 of Msg1-Less EDT, where Y is less than or equal to R, R is a natural number from 1 to 64, and Y is a natural number from 1 to 48;

[0221] Msg3 of Msg1-Less EDT includes N bits of the CCCH SDU starting from the Mth bit in front, where M is any natural number from 1 to 48, and N is any natural number from 1 to 48.

[0222] In one embodiment of the present disclosure, the CCCH SDU is at least one of the following:

[0223] RRC Early Data Request

[0224] RRC Connection Resume Request RRC Connection Resume Request.

[0225] For example, in one embodiment of the present disclosure, the CCCH SDU is an RRC early data request.

[0226] For example, in one embodiment of the present disclosure, the CCCH SDU is an RRC connection recovery request.

[0227] In one embodiment of the present disclosure, the terminal identification information is the first X bits of the common control channel CCCH service data unit SDU included in Msg3 of Msg1-Less EDT, and the value of X is any natural number from 1 to 48.

[0228] For example, in one embodiment of the present disclosure, X does not specifically refer to a fixed value. The first digit in X is used only to distinguish the remaining values. The value of X can be any natural number from 1 to 48, and specifically can be 8, 16, or 32. This embodiment of the present disclosure is not limited to this.

[0229] In one embodiment of the present disclosure, the terminal identification information is the last T bits of the first R bits of the CCCH SDU included in Msg3 of Msg1-Less EDT, T is less than or equal to R, R is any natural number from 1 to 64, and T is any natural number from 1 to 48.

[0230] For example, in one embodiment of the present disclosure, the value of R can be any natural number from 1 to 64, for example, R can be 8, R can also be 16, and R can also be 24. For the RRC Connection Resume Request, if the truncated Resume ID is not used, R can be 44, for example, and if the truncated Resume ID is used, R can be 28, for example. Alternatively, for all cases of the RRC Connection Resume Request, R can be 28, for example, or any natural number between 1 and 28, for example, R can be 20, 16, or 10. This embodiment of the present disclosure is not limited to this.

[0231] For example, in one embodiment of the present disclosure, for an RRC Early Data Request, when the terminal is connected to the EPC, R may be, for example, 47; and when the terminal is connected to the 5GC, R may be, for example, 57. For an RRC Early Data Request, whether the terminal is connected to the EPC or the 5GC, R may be, for example, 47. For an RRC Early Data Request, whether the terminal is connected to the EPC or the 5GC, R may be, for example, 40. For an RRC Early Data Request, whether the terminal is connected to the EPC or the 5GC, R may be, for example, an integer power of 2, such as 8, 16, or 32. For an RRC Early Data Request, whether the terminal is connected to the EPC or the 5GC, R may be, for example, any natural number from 1 to 47.

[0232] For example, in one embodiment of the present disclosure, for all cases, R may be 28, 16, 20, or any natural number between 1 and 28. This embodiment of the present disclosure is not limited thereto.

[0233] For example, in one embodiment of the present disclosure, the value of T may be 4, 5, 8, 16, or 24. This embodiment of the present disclosure does not limit this.

[0234] In one embodiment of the present disclosure, the terminal identification information is N bits starting from the front M-th bit of the CCCH SDU included in Msg3 of Msg1-Less EDT, M is any natural number from 1 to 48, and N is any natural number from 1 to 48.

[0235] For example, in one embodiment of the present disclosure, the value of M may be any natural number from 1 to 48, for example, M may be 4, M may also be 5, M may also be 7, M may also be 8, M may also be 16, and M may also be 24. For RRC Connection Resume Request, M may be 5, for example (assuming that the first digit is counted from the first digit, if counting starts from 0, the value of M is 4).

[0236] For example, in one embodiment of the present disclosure, for RRC Early Data Request, when the terminal is connected to EPC, M can be, for example, 8 (assuming that the first bit is counted from the first bit, if counting starts from 0, the value of M is 7), and when the terminal is connected to 5GC, M can be, for example, 10 (assuming that the first bit is counted from the first bit, if counting starts from 0, the value of M is 9).

[0237] For example, in one embodiment of the present disclosure, for RRC Early Data Request, whether the terminal is connected to EPC or 5GC, M may be, for example, 10 (assuming the first digit is counted from the first digit). For example, in one embodiment of the present disclosure, for RRC Early Data Request, whether the terminal is connected to EPC or 5GC, M may be, for example, the next integer power of 2, such as 9, 17, or 33.

[0238] For example, in one embodiment of the present disclosure, for all cases, M can be, for example, 10 (assuming the first digit is counted from the first digit), or the next integer power of 2, such as 9, 17, or 33.

[0239] For example, in one embodiment of the present disclosure, the value of N may be 4, 8, 16, 24, or 48. This embodiment of the present disclosure does not limit this.

[0240] In one embodiment of the present disclosure, the terminal identification information is carried by at least one of the following:

[0241] Layer 1 L1 signaling;

[0242] Media Access Control - Control Element MAC CE signaling;

[0243] Media Access Control-MAC sub header.

[0244] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) state", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", "panel" and the like can be used interchangeably.

[0245] In one embodiment of the present disclosure, the terminal identification information is carried via layer 1 L1 signaling.

[0246] In one embodiment of the present disclosure, the terminal identification information is carried through Media Access Control-Control Element MAC CE signaling.

[0247] In one embodiment of the present disclosure, the terminal identification information is carried by a media access control-sub-header MAC sub header.

[0248] In one embodiment of the present disclosure, the L1 signaling is physical downlink control channel PDCCH downlink control information DCI.

[0249] In one embodiment of the present disclosure, the MAC CE signaling is at least one of the following:

[0250] Terminal contention resolution identity MAC CEUE Contention Resolution Identity MAC Control Element;

[0251] Newly defined MAC CE.

[0252] For example, in one embodiment of the present disclosure, the MAC CE signaling is a terminal contention resolution identifier MAC CE.

[0253] For example, in one embodiment of the present disclosure, the MAC CE signaling is a newly defined MAC CE.

[0254] For example, in one embodiment of the present disclosure, Msg4 includes a demodulation reference signal resource identifier DMRS resource ID.

[0255] In one embodiment of the present disclosure, the DMRS resource ID is carried in at least one of the following:

[0256] PDCCH DCI;

[0257] MAC CE;

[0258] MAC subheader of the response message.

[0259] For example, in one embodiment of the present disclosure, the DMRS resource ID is carried in the PDCCH DCI.

[0260] For example, in one embodiment of the present disclosure, the DMRS resource ID is carried in the MAC CE.

[0261] For example, in one embodiment of the present disclosure, the DMRS resource ID is carried in the MAC subheader of the response message.

[0262] In one embodiment of the present disclosure, the DMRS resource ID is the DMRS resource ID used by the terminal to send Msg3 of the Msg1-Less EDT. For example, the DMRS resource ID is used to indicate the DMRS resource used by the terminal to send Msg3 of the Msg1-Less EDT.

[0263] In one embodiment of the present disclosure, Msg4 includes an orthogonal cover code resource identifier OCC resource ID.

[0264] In one embodiment of the present disclosure, the OCC resource ID is carried in at least one of the following:

[0265] PDCCH DCI;

[0266] MAC CE;

[0267] MAC subheader of the response message.

[0268] For example, in one embodiment of the present disclosure, the OCC resource ID is carried in the PDCCH DCI.

[0269] For example, in one embodiment of the present disclosure, the OCC resource ID is carried in the MAC CE.

[0270] For example, in one embodiment of the present disclosure, the OCC resource ID is carried in the MAC subheader of the response message.

[0271] In one embodiment of the present disclosure, the OCC resource ID is the OCC resource ID used by the terminal to send Msg3 of the Msg1-Less EDT. The OCC resource ID is used to indicate the OCC resource used by the terminal to send Msg3 of the Msg1-Less EDT.

[0272] In one embodiment of the present disclosure, Msg3 of Msg1-Less EDT is sent using non-competitive resources, and Msg4 includes first indication information, where the first indication information is used to indicate confirmation of receipt of Msg3.

[0273] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0274] For example, in one embodiment of the present disclosure, if the terminal uses non-competitive resources to send Msg3 of Msg1-Less EDT, Msg4 includes first indication information, and the first indication information is used to indicate confirmation of receipt of Msg3.

[0275] For example, in one embodiment of the present disclosure, the first indication information may be, for example, Msg3 of Msg1-Less EDT, which is sent using non-competitive resources, and the indication information included in Msg4, where the first indication information is used to indicate that Msg3 has been received. The first in the first indication information is used to distinguish it from the remaining indication information.

[0276] In one embodiment of the present disclosure, Msg1-Less EDT is CP Msg1-Less EDT. For example, Msg3, which can be used for Msg1-Less EDT, is sent using non-competitive resources, and Msg4 includes first indication information, where the first indication information is used to indicate that a method for confirming receipt of Msg3 is applicable to CP Msg1-Less EDT.

[0277] In one embodiment of the present disclosure, the method further includes:

[0278] When the network device does not send the RRC Early Data Complete message, it receives Msg4 sent by the network device, where Msg4 carries L1 confirmation ACK information.

[0279] For example, in one embodiment of the present disclosure, if the network device does not have an RRC Early Data Complete message to send, the network device may send Msg4 carrying L1 ACK information.

[0280] For example, in one embodiment of the present disclosure, Msg4 includes second indication information, and the second indication information is used to indicate network fallback.

[0281] In one embodiment of the present disclosure, the second indication information may be, for example, information for indicating Fallback, and the second in the second indication information is used to distinguish it from other indication information.

[0282] For example, in one embodiment of the present disclosure, the indication information confirming the receipt of Msg3 may be indicated by, for example, a PDCCH DCI.

[0283] In one embodiment of the present disclosure, Msg4 includes third indication information, and the third indication information is used to indicate adjustment of the number of repetitions of Msg3 of Msg1-Less EDT.

[0284] In one embodiment of the present disclosure, the third indication information may be, for example, information for indicating adjustment of the number of repetitions of Msg3 of Msg1-Less EDT, and the third in the third indication information is used to distinguish it from other indication information.

[0285] In one embodiment of the present disclosure, the method further includes:

[0286] The repetition count adjustment of Msg3 sent by the network device is received, and the repetition count of Msg3 of the stored Msg1-Less EDT is updated.

[0287] In one embodiment of the present disclosure, the first indication information, the second indication information or the third indication information is PDCCH DCI.

[0288] For example, in one embodiment of the present disclosure, the first indication information is PDCCH DCI.

[0289] For example, in one embodiment of the present disclosure, the second indication information is PDCCH DCI.

[0290] For example, in one embodiment of the present disclosure, the third indication information is PDCCH DCI.

[0291] In some embodiments, steps S3101 to S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0292] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and steps S3101 and S3102 may be implemented as independent embodiments, but are not limited thereto.

[0293] In some embodiments, step S3102 is optional and may be omitted or replaced in different embodiments.

[0294] FIG4A is a flow chart of a method for receiving a response message according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for receiving a response message, which is executed by a first node and includes at least one of the following:

[0295] Step S4101: Send at least one of data and signaling to a network device, and wait to receive a response message sent by the network device.

[0296] In one embodiment of the present disclosure, data is sent to a network device, and a response message sent by the network device is waited for.

[0297] In one embodiment of the present disclosure, a signaling is sent to a network device, and a response message sent by the network device is waited for.

[0298] In one embodiment of the present disclosure, data may refer to any data, and signaling may refer to any signaling, which is not limited in this embodiment of the present disclosure.

[0299] In one embodiment of the present disclosure, sending at least one of data and signaling to a network device and waiting to receive a response message sent by the network device includes:

[0300] The system sends message 3Msg3 of Msg1-Less EDT that does not require advance data transmission of Msg1 to the network device, and waits to receive message 4Msg4 of Msg1-Less EDT sent by the network device.

[0301] The optional implementation of step S4101 can refer to the optional implementation of step S3102 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0302] FIG5A is a flow chart of a method for sending a response message according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a method for sending a response message, which is executed by a network device and includes:

[0303] Step S5101: Receive at least one of data and signaling sent by the terminal, and send a response message to the terminal.

[0304] In one embodiment of the present disclosure, receiving at least one of data and signaling sent by a terminal and sending a response message to the terminal includes:

[0305] The receiving terminal sends message 3Msg3 of Msg1-Less EDT without the advance data transmission of Msg1, and sends message 4Msg4 of Msg1-Less EDT to the terminal.

[0306] The optional implementation of step S5101 can refer to the optional implementation of step S3101 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0307] FIG6A is a flow chart of a method for receiving a response message according to an embodiment of the present disclosure. As shown in FIG6A , the embodiment of the present disclosure relates to a method for receiving a response message, and the method includes:

[0308] In step S6101, after sending an extended data transfer (EDT) Msg1-less EDT Msg3 that does not require a message (Message) Msg1, the user equipment (UE) waits to receive Msg4 of the less EDT Msg1-less EDT, where the Msg4 does not include an RRC message.

[0309] Optionally, the resources sent by the Msg3 used for Msg1-Less EDT can be competitive resources or non-competitive resources. For non-competitive resources, they can be pre-configured UL resources (PUR resources) that include a UE-specific orthogonal cover code (OCC) resource configuration. For competitive resources, the UE is not configured with a unique OCC / demodulation reference signal (DMRS) resource. When using competitive resources, the UE can select an OCC / DMRS resource from the OCC / DMRS resource pool. Competitive resources can be sent to the UE via system messages or dedicated signaling, and non-competitive resources can be sent to the UE via dedicated signaling.

[0310] In some embodiments, Msg3 of the Msg1-Less EDT may include one or more of the following: a control plane cellular IoT extended packet exchange or an uplink RRC advance data request message for 5G system optimization, a control plane CIOT EPS / 5GS optimization UL RRC EarlyDataRequest message; a user plane cellular IoT extended packet exchange or a 5G system optimization uplink user data on DTCH multiplied with UL RRC Connection Resume Request message on CCCH.

[0311] In some embodiments, if Msg3 of Msg1-Less EDT is sent using contention resources, the Msg4 may include UE identification information.

[0312] In some embodiments, the UE identification information may be the first X bits of a Common Control Channel (CCCH) service data unit (SDU) included in Msg3 of Msg1-Less EDT.

[0313] In some embodiments, the CCCH SDU may be a Radio Resource Control (RRC) Early Data Request or an RRC Connection Resume Request.

[0314] In some embodiments, the value of X may be a natural number from 1 to 48, such as 8, 16, or 24.

[0315] In some embodiments, the UE identity may be carried by layer 1 L1 signaling or media access control-control elements (MAC CE) signaling or media access control-subheader MAC sub header.

[0316] In some embodiments, the L1 signaling may be physical downlink control channel (PDCCH) downlink control information (DCI).

[0317] In some embodiments, the MAC CE may be a terminal contention resolution identifier UE Contention Resolution Identity MAC Control Element, or a newly defined MAC CE.

[0318] In some embodiments, the UE identification information may be the last Y bits of the first X bits of the CCCH SDU included in Msg3 of Msg1-Less EDT.

[0319] In some embodiments, the CCCH SDU is an RRC Early Data Request or an RRC Connection Resume Request.

[0320] In some embodiments, the value of X can be a natural number from 1 to 64, such as 8, 16, or 24. For RRC Connection Resume Request, if the truncated Resume ID is not used, X = 44; if the truncated Resume ID is used, X = 28. Alternatively, for all cases of RRC Connection Resume Request, X = 28, or any value between 1 and 28, such as 20, 16, or 10. For RRC Early Data Request, when the UE is connected to EPC, X = 47; when the UE is connected to 5GC, X = 57. Alternatively, for RRC Early Data Request, regardless of whether the UE is connected to EPC or 5GC, X = 47, or 40, or an integer power of 2 (such as 8, 16, or 32), or any value between 1 and 47. Alternatively, for all cases, X = 28, or 16, or 20, or any value between 1 and 28.

[0321] In some embodiments, the value of Y can be a natural number from 1 to 48, such as 4, 5, 8, 16, or 24.

[0322] In some embodiments, the UE identification information may be N bits starting from the front M-th bit of the CCCH SDU included in Msg3 of Msg1-Less EDT.

[0323] In some embodiments, the CCCH SDU may be an RRC Early Data Request or an RRC Connection Resume Request.

[0324] In some embodiments, the value of M is a natural number from 1 to 48, such as 4, 5, 7, 8, 16, and 24. For RRCConnectionResumeRequest, M=5 (assuming the first digit starts counting from the first digit, if counting from 0, then M=4). For RRC EarlyDataRequest, when the UE is connected to the Evolved Packet Core (EPC), M=8 (assuming the first digit starts counting from 1, if counting from 0, then M=7), and when the UE is connected to the 5G Core Network (5GC), M=10 (assuming the first digit starts counting from 1, if counting from 0, then M=9). Or for RRC EarlyDataRequest, regardless of whether the UE is connected to the EPC or 5GC, M=10 (assuming the first digit starts counting from 1), or the next integer power of 2 (such as 9, 17, or 33) is taken. Alternatively, for all cases, M=10 (assuming the first digit starts counting from 1), or the next integer power of 2 (such as 9, 17, 33) is taken.

[0325] In some embodiments, the value of N may be a natural number from 1 to 48, such as 4, 8, 16, 24, or 48.

[0326] In some embodiments, the Msg4 may include a DMRS resource ID.

[0327] In some embodiments, the DMRS resource ID may be carried in the PDCCH DCI, or in the MAC CE or in the MAC subheader of the response message.

[0328] In some embodiments, the DMRS resource ID may be the DMRS resource ID used by the UE to send EDT Msg3.

[0329] In some embodiments, the Msg4 may include an OCC resource ID.

[0330] In some embodiments, the OCC resource ID may be carried in the PDCCH DCI, or in the MAC CE or in the MAC subheader of the response message.

[0331] In some embodiments, the OCC resource ID may be the OCC resource ID used by the UE to send EDT Msg3.

[0332] In some embodiments, if Msg3 is sent using non-competitive resources, Msg4 may carry indication information for indicating confirmation of receipt of Msg3.

[0333] In some embodiments, the indication information confirming receipt of Msg3 may be indicated by PDCCH DCI.

[0334] In some embodiments, the method is applicable to CP Msg1-Less EDT.

[0335] In some embodiments, if the base station does not have RRC EarlyDataComplete to send, the base station may send Msg4 carrying the L1ACK.

[0336] In some embodiments, the Msg4 carries indication information, which can be used to indicate Fallback.

[0337] In some embodiments, the indication information confirming receipt of Msg3 may be indicated by PDCCH DCI.

[0338] In some embodiments, the Msg4 may carry indication information for indicating adjustment of the number of repetitions of Msg3 of Msg1-Less EDT.

[0339] In some embodiments, the Msg3 repetition number adjustment information indicating Msg1-Less EDT may be indicated through PDCCH DCI.

[0340] In some embodiments, after receiving the repetition number adjustment, the UE may update the stored msg3 repetition number of the Msg1-Less EDT.

[0341] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

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

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

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

[0345] Figure 7A is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in Figure 7A, network device 7100 may include a transceiver module 7101. In some embodiments, the transceiver module is used to send at least one of data and signaling to the network device and wait for a response message sent by the network device. Optionally, the transceiver module 7101 is used to perform at least one of the communication steps such as sending and / or receiving performed in any of the above methods (such as step S3102, but not limited thereto), and will not be repeated here.

[0346] FIG7B is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG7B , the terminal 7200 may include a transceiver module 7201 , which is configured to receive at least one of data and signaling sent by the terminal and send a response message to the terminal.

[0347] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0348] In some embodiments, the processing module can be a single module or include multiple submodules. Optionally, the multiple submodules each execute all or part of the steps required to be executed by the processing module. Optionally, the processing module and the processor can be interchangeable.

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

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

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

[0352] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S3101 and step S3102, but not limited thereto), and the processor 8101 performs at least one of the other steps.

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

[0354] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

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

[0357] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0358] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0359] In some embodiments, the interface circuit 8202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S3101, step S3102, but not limited thereto), and the processor 8201 executes at least one of the other steps.

[0360] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

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

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

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

[0364] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A method for receiving a response message, characterized in that: The method is executed by a terminal, and includes: Send at least one of data and signaling to the network device, and wait to receive a response message sent by the network device.

2. The method according to claim 1, wherein The sending at least one of data and signaling to the network device and waiting to receive a response message sent by the network device includes: The network device sends a message 3 Msg3 of Msg1-Less EDT that does not require advance data transmission of Msg1 to the network device, and waits for receiving a message 4 Msg4 of Msg1-Less EDT sent by the network device.

3. The method according to claim 2, wherein in, The Msg4 does not include a radio resource control RRC message.

4. The method according to claim 2, wherein in, The message 3Msg3 of the Msg1-Less EDT is at least one of the following: Control plane Cellular Internet of Things (CIOT) Evolved Packet System (CIOT) EPS optimized uplink ULRRC EarlyDataRequest message; Control plane 5G system 5GS optimized uplink ULRRC early data request EarlyDataRequest message; Uplink data transmitted on the dedicated traffic channel DTCH optimized by the user plane CIOT EPS and the uplink UL RRC connection resumption request ConnectionResumeRequest message transmitted on the common control channel CCCH multiplexed with it; The user plane 5GS optimizes the uplink data transmitted on the dedicated traffic channel DTCH and the uplink UL RRC connection resumption request ConnectionResumeRequest message transmitted on the common control channel CCCH multiplexed with it.

5. The method according to claim 2, wherein in, The Msg3 of the Msg1-Less EDT is sent using competitive resources, and the Msg4 includes terminal identification information.

6. The method according to claim 5, wherein in, The terminal identification information is at least one of the following: The first X bits of the Common Control Channel (CCCH) Service Data Unit (SDU) included in Msg3 of the Msg1-Less EDT, where X is any natural number from 1 to 48; The last T bits of the first R bits of the CCCH SDU included in Msg3 of the Msg1-Less EDT, where T is less than or equal to R, R is any natural number from 1 to 64, and T is any natural number from 1 to 48; The Msg3 of the Msg1-Less EDT includes N bits of the CCCH SDU starting from the Mth bit, where the value of M is any natural number from 1 to 48, and the value of N is any natural number from 1 to 48.

7. The method according to claim 6, wherein The CCCH SDU is at least one of the following: RRC advance data request; RRC connection resumption request.

8. The method according to any one of claims 5 to 7, wherein: in, The terminal identification information is carried by at least one of the following: Layer 1 L1 signaling; Media Access Control - Control Element MAC CE signaling; Media Access Control-MAC sub header.

9. The method according to claim 8, wherein in, The L1 signaling is physical downlink control channel PDCCH downlink control information DCI.

10. The method according to claim 8, wherein in, The MAC CE signaling is at least one of the following: Terminal contention resolution identifier MAC CE; Newly defined MAC CE.

11. The method according to claim 2 or 3, wherein: in, The Msg4 includes a demodulation reference signal resource identifier DMRS resource ID.

12. The method according to claim 11, wherein in, The DMRS resource ID is carried in at least one of the following: PDCCH DCI; MAC CE; MAC subheader of the response message.

13. The method according to claim 11, wherein in, The DMRS resource ID is the DMRS resource ID used by the terminal to send the Msg3 of the Msg1-Less EDT.

14. The method according to claim 2 or 3, wherein: in, The Msg4 includes an orthogonal cover code resource identifier OCC resource ID.

15. The method according to claim 14, wherein in, The OCC resource ID is carried in at least one of the following: PDCCH DCI; MAC CE; MAC subheader of the response message.

16. The method according to claim 14, wherein in, The OCC resource ID is the OCC resource ID used by the terminal to send Msg3 of the Msg1-Less EDT.

17. The method according to claim 2, wherein in, The Msg3 of the Msg1-Less EDT is sent using non-competitive resources, and the Msg4 includes first indication information, where the first indication information is used to indicate confirmation of receipt of the Msg3.

18. The method according to claim 17, wherein in, The Msg1-Less EDT is CP Msg1-Less EDT.

19. The method according to claim 17, wherein The method further comprises: When the network device does not send the RRC early data completion message, the Msg4 sent by the network device is received, wherein the Msg4 carries L1 confirmation ACK information.

20. The method according to claim 2, wherein in, The Msg4 includes second indication information, and the second indication information is used to indicate network fallback.

21. The method according to claim 2, wherein in, The Msg4 includes third indication information, and the third indication information is used to indicate adjustment of the number of repetitions of the Msg3 of the Msg1-Less EDT.

22. The method according to claim 21, wherein The method further comprises: Receive the Msg3 repetition times adjustment sent by the network device and update the stored Msg1-Less EDT The number of times Msg3 is repeated.

23. The method according to claim 17, 20 or 21, wherein: in, The first indication information, the second indication information or the third indication information is PDCCH DCI.

24. A message sending method, characterized in that: The method is performed by a network device, and includes: receiving at least one of data and signaling sent by a terminal, and sending a response message to the terminal.

25. A terminal, characterized in that: The terminal includes: The transceiver module is used to send at least one of data and signaling to the network device and wait to receive a response message sent by the network device.

26. A network device, characterized in that: The network equipment includes: The transceiver module is used to receive at least one of data and signaling sent by the terminal and send a response message to the terminal.

27. A terminal, characterized in that: include: one or more processors; The terminal is used to execute the response message receiving method according to any one of claims 1 to 23.

28. A network device, characterized in that: include: one or more processors; Wherein, the network device is used to execute the response message receiving method described in claim 24.

29. A communication system, characterized in that: It comprises a network device and a terminal, wherein the terminal is configured to implement the response message receiving method according to any one of claims 1 to 23, and the network device is configured to implement the response message receiving method according to claim 24.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the response message receiving method according to any one of claims 1 to 23 or 24.

Images