Communication method and apparatus

Abstract

Disclosed in the present application are a communication method and apparatus. The method comprises: a terminal device sending a first message, wherein the first message comprises a CCCH SDU; the terminal device receiving a second message, wherein the second message is used for responding to the first message; and on the basis of whether the second message carries a C-RNTI or a first RRC message, the terminal device determining whether to terminate data transmission. In the method, whether to terminate data transmission is determined by means of whether a second message carries a C-RNTI or a first RRC message, thereby helping to reduce the transmission overhead of the second message.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 2024106773187, filed on May 28, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0003] In communication systems, terminal devices need to obtain uplink synchronization through a random access procedure (RA) to facilitate communication with access network devices. Typically, no data is transmitted during the R15 ... In addition, Msg4 may also carry a layer 3 (L3) message, such as the Radio Resource State Early Data Complete (RRCE) message, to indicate that the terminal device has completed the transmission and has returned to / remained in the idle state. However, this method of sending an L3 message to indicate that the terminal device has returned to / remained in the idle state increases the transmission overhead of Msg4. Summary of the Invention

[0004] This application provides a communication method and apparatus that determines whether a terminal device should terminate data transmission by whether the second message carries layer 3 or layer 2 (L2) information, which helps to reduce the transmission overhead of the second message.

[0005] In a first aspect, this application provides a communication method that can be applied to a terminal device or a chip within the terminal device. Using a terminal device as an example, the method includes: the terminal device sending a first message, which includes a Common Control Channel (CCCH) Service Data Unit (SDU); the terminal device receiving a second message, which is used in response to the first message; and the terminal device determining whether to terminate data transmission based on whether the second message carries a Cell Radio Network Temporary Identifier (C-RNTI) or a first Radio Resource Control (RRC) message.

[0006] Based on this method, the terminal device can determine whether to terminate data transmission by whether the second message carries a Layer 3 message (i.e., the first RRC message) or Layer 2 information (i.e., C-RNTI). Compared with the current method of instructing the terminal device to terminate data transmission by carrying a Layer 3 message (e.g., RRC EarlyDataComplete message) in the second message, this method helps to reduce the transmission overhead of the second message.

[0007] In one possible embodiment, the second message includes a first response unit, which includes a first contention resolution identifier that matches the CCCH SDU; the above-mentioned determination of whether to terminate data transmission based on whether the second message carries a C-RNTI includes: the terminal device determining whether to terminate data transmission based on whether the first response unit carries a C-RNTI.

[0008] In one possible embodiment, determining whether to terminate data transmission based on whether the first response unit carries a C-RNTI includes: if the terminal device carries a C-RNTI in the first response unit, continuing data transmission; if the terminal device does not carry a C-RNTI in the first response unit, terminating data transmission.

[0009] In one possible embodiment, the above-mentioned continued data transmission includes: the terminal device receiving and / or sending data according to C-RNTI.

[0010] In one possible embodiment, the second message includes a first sub-header corresponding to a first response unit, the first sub-header including first information; when the value of the first information is a first value, it indicates that the first response unit carries C-RNTI; when the value of the first information is a second value, it indicates that the first response unit does not carry C-RNTI.

[0011] In one possible embodiment, the second message includes a second response unit, which includes a second contention resolution identifier and a CCCH SDU match; the determination of whether to terminate data transmission based on whether the second message carries a first RRC message includes: if the second message carries a first RRC message, the terminal device continues data transmission; if the second message does not carry a first RRC message, the terminal device terminates data transmission.

[0012] In one possible embodiment, the first RRC message is an RRC connection establishment message or an RRC connection recovery message.

[0013] In one possible embodiment, the terminal device continues data transmission, including: the terminal device receiving and / or sending data based on the RRC connection.

[0014] In one possible embodiment, terminating data transmission when the second message does not carry the first RRC message includes: terminating data transmission when the second message does not include a third response unit; or terminating data transmission when the second message includes N third response units, and none of the N third response units carry the first RRC message, where N is an integer greater than 0. The third response unit carries a Media Access Control (MAC) SDU, and the MAC SDU carries the first RRC message.

[0015] In one possible embodiment, the second message includes a second sub-header corresponding to a second response unit, and the second sub-header includes second information used to indicate N.

[0016] In one possible embodiment, the N third response units and the second response unit are associated.

[0017] Secondly, this application provides a communication device that includes units for performing the method described in the first aspect.

[0018] Thirdly, this application provides a chip including a processor and a communication interface. The processor is configured to cause the chip to perform the method described in the first aspect above, and the communication interface is configured to receive signals from other devices outside the chip and transmit them to the processor, or to send signals from the processor to other devices outside the chip.

[0019] Fourthly, this application provides a module device, which includes a communication module, a power module, a storage module, and a chip, wherein: the power module is used to provide power to the module device; the storage module is used to store data and instructions; the communication module is used to perform internal communication within the module device or to communicate between the module device and external devices; and the chip is used to execute the method described in the first aspect.

[0020] Fifthly, embodiments of this application disclose a communication device, which includes a memory and a processor. The memory is used to store a computer program, which includes program instructions. The processor is configured to invoke the program instructions to execute the method described in the first aspect.

[0021] In a sixth aspect, this application provides a computer-readable storage medium storing computer-readable instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect.

[0022] In a seventh aspect, this application provides a computer program or computer program product, including code or instructions, which, when run on a computer, cause the computer to perform the method described in the first aspect above. Attached Figure Description

[0023] Figure 1 is a schematic diagram of a communication system 10 provided in an embodiment of this application;

[0024] Figure 2 is a schematic diagram of a random access process provided in an embodiment of this application;

[0025] Figure 3 is a schematic diagram of another random access process provided in an embodiment of this application;

[0026] Figure 4a is a schematic diagram of a control plane-based EDT transmission provided in an embodiment of this application;

[0027] Figure 4b is a schematic diagram of a user plane-based EDT transmission process provided in an embodiment of this application;

[0028] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0029] Figure 6a is a schematic diagram of the structure of Msg4 provided in an embodiment of this application;

[0030] Figure 6b is a schematic diagram of another Msg4 structure provided in an embodiment of this application;

[0031] Figure 6c is a schematic diagram of a subPDU provided in an embodiment of this application;

[0032] Figure 6d is a schematic diagram of the structure of a payload provided in an embodiment of this application;

[0033] Figure 7 is a schematic diagram of the structure of a first sub-head provided in an embodiment of this application;

[0034] Figure 8 is a schematic diagram of the structure of an LTE / NR control plane protocol stack provided in an embodiment of this application;

[0035] Figure 9 is a schematic diagram of the structure of a second sub-head provided in an embodiment of this application;

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

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

[0038] Figure 12 is a schematic diagram of the structure of a module device provided in an embodiment of this application. Detailed Implementation

[0039] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0040] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise.

[0041] In the embodiments of this application, "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone; A and B exist simultaneously; B exists alone. Among them, A and B can be singular or plural.

[0042] In this embodiment of the application, the symbol " / " can indicate that the preceding and following related objects are in an "or" relationship.

[0043] In the embodiments of this application, "at least one item" or its similar expression refers to any combination of these items, including any combination of a single item or a plurality of items. "One or more" means one or more, while "multiple" means two or more. For example, "at least one item" of a, b, or c can represent the following seven cases: a, b, c; a and b; a and c; b and c; a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0044] In the embodiments of this application, "equal to" can be used with "greater than" and is applicable to technical solutions used when "greater than" is used; it can also be used with "less than" and is applicable to technical solutions used when "less than" is used. When "equal to" is used with "greater than", it is not used with "less than"; when "equal to" is used with "less than", it is not used with "greater than".

[0045] It should be noted that the terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the term "comprising" and any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices.

[0046] To facilitate understanding of the embodiments of this application, the system architecture involved in this application will be described below.

[0047] This application can be applied to fourth-generation (4G) systems, also known as long-term evolution (LTE) systems; or to fifth-generation (5G) systems, also known as new radio (NR) systems; or to sixth-generation (6G) systems, or seventh-generation (7G) systems, or other future communication systems; or it can also be used for device-to-device (D2D) systems, machine-to-machine (M2M) systems, vehicle-to-everything (V2X) systems, etc.

[0048] This application can be applied to the system architecture shown in Figure 1. As shown, the communication system may include at least one wireless access network device, such as access network device 110 shown in Figure 1; the communication system may also include at least one terminal device, such as terminal device 120 shown in Figure 1. Access network device 110 and terminal device 120 can establish a direct communication connection through wired communication, or access network device 110 and terminal device 120 can establish an indirect communication connection through wireless communication.

[0049] I. Terminal Equipment

[0050] Terminal devices include devices that provide voice and / or data connectivity to users. For example, a terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). The terminal can be a mobile phone, vehicle, roadside unit, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. The embodiments in this application do not limit the application scenarios. A terminal may also be referred to as a terminal device, user equipment (UE), access terminal device, vehicle-mounted terminal, industrial control terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal device, mobile device, user terminal device, terminal device, wireless communication device, user agent, or user apparatus, etc. A terminal can be fixed or mobile. In the embodiments of this application, the device used to implement the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This device can be installed in the terminal device.

[0051] II. Access Network Equipment

[0052] Access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. Access network equipment can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU) or a distributed unit (DU). Here, the CU performs the functions of the base station's Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). Access network equipment can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. In the embodiments of this application, the device used to implement the functions of the access network equipment can be the access network equipment itself, or a device capable of supporting the access network equipment in implementing this function, such as a chip system or a combination of devices or components capable of implementing the functions of the access network equipment. This device can be installed in the access network equipment. The embodiments of this application do not limit the specific technology or specific equipment form used in the access network equipment.

[0053] It should be noted that the embodiments of this application can be applied to various communication systems, as long as there is an entity in the communication system that needs to send information and another entity that needs to receive information. It is understood that the communication system architecture or scenario in Figure 1 above is only an exemplary implementation method in the embodiments of this application, and the communication system architecture or scenario in the embodiments of this application includes, but is not limited to, the above-described communication system architecture or scenario.

[0054] To facilitate understanding of the embodiments of this application, the relevant names or terms involved in this application will be described below.

[0055] I. Random Access (RA)

[0056] Random access control (RA) is divided into contention-based random access and non-contention-based random access. The following section mainly introduces contention-based random access. As shown in Figure 2, the contention-based random access process mainly includes four steps, each corresponding to a message: S1, the terminal device sends message 1 (Msg1) to the access network device; S2, the access network device sends message 2 (Msg2) to the terminal device; S3, the terminal device sends message 3 (Msg3) to the access network device; S4, the access network device sends message 4 (Msg4) to the terminal device. Each message carries different signaling or information. For example, Msg1 is the terminal device sending an uplink random access preamble, which mainly informs the access network device of a random access request and enables the access network device to estimate the transmission delay between itself and the terminal device, calibrating the uplink transmission timing, i.e., timing advance (TA) adjustment. Msg2 carries the preamble index of Msg1, uplink resource allocation for TA and Msg3, temporary cell radio network temporary identifier (TC-RNTI), backoff parameters, etc. Msg3 may include an RRC connection establishment request message. Msg4 may include the contention resolution identifier of the terminal device.

[0057] It should be noted that when the TA of the terminal device is valid, a random access procedure without Msg1 and Msg2 can be considered. That is, the terminal device only sends message 3 (Msg3) and receives message 4 (Msg4) to complete the random access. In the random access procedure shown in Figure 3, multiple terminal devices send Msg3 on shared resources. The content of Msg3 is the same as that in the random access procedure in Figure 2, such as RRC connection establishment request message. The access network device responds and confirms in Msg4, and the message it carries can also be the same as that carried in Msg4 in Figure 2, such as the contention resolution identification information of the terminal device.

[0058] II. Early Data Transmission (EDT)

[0059] For terminal devices in a disconnected state (i.e., radio resource control (RRC) idle or inactive state), early data transmission can be performed through a random access procedure (e.g., automatic reporting by water meters) to avoid changing the RRC state and incurring RRC signaling overhead. In other words, in a communication system, terminal devices in an idle or deactivated state can transmit data without switching RRC states; this data transmission mechanism is called EDT.

[0060] It should be noted that the random access procedure is generally used to establish a connection between the terminal device and the access network device. Initially, no data is transmitted during the random access procedure, but during the EDT, the terminal device can send uplink data to or receive downlink data from the access network device (such as the base station) during the RA procedure.

[0061] Currently, considering random access procedures without Msg1 and Msg2 for EDT, such EDT procedures only include Msg3 and Msg4. For example, in the control plane-based EDT transmission process shown in Figure 4a, the terminal device can carry an RRC Early Data Request in the Msg3 sent to the access network device. Optionally, this RRC Early Data Request can also carry dedicated information non-access stratum (dedicatedInfo NAS), and the dedicatedInfo NAS further carries user data (or uplink data), thus achieving the purpose of sending data to the access network device in Msg3. In addition to carrying the contention resolution identifier, the Msg4 sent by the access network device to the terminal device may also carry an L3 message, namely the RRC Early Data Complete message. The RRC Early Data Complete message is used to indicate that the data transmission of the terminal device is complete, and the terminal device switches to / returns to / remains in an idle state. Optionally, the access network device may also carry redirection-related instructions or configuration information related to cell reselection priority in the RRCEarlyDataComplete message. In addition, there may be situations where the access network device, for various reasons such as having a large amount of data to transmit subsequently, wants the terminal device to enter the connected state. In this case, instead of sending an RRCEarlyDataComplete message, the access network device sends an L3 message (i.e., an RRC connection establishment (RRCConnectionSetup) message) to instruct the terminal device to enter the connected state to continue data transmission.

[0062] In the user plane-based EDT transmission process shown in Figure 4b, the terminal device can carry an RRC connection resumption request (RRCConnectionResumeRequest) in the Msg3 message sent to the access network device. Optionally, it can also carry user data (or uplink data). The user data and RRCConnectionResumeRequest are multiplexed, thus achieving the purpose of sending data to the access network device in Msg3. In addition to carrying a contention resolution identifier, the Msg4 message sent by the access network device to the terminal device may also carry an L3 message, namely an RRC connection release message. This RRCConnectionRelease message is used to indicate that the data transmission of the terminal device is complete, and the terminal device remains in an idle state. The access network device can also carry a release cause value, a resume identifier (resumeID), and a next-hop counter (NextHopChainingCount) in the RRCConnectionRelease message. In addition, there may be situations where the access network device wants the terminal device to enter the connected state for various reasons, such as when there is a large amount of data to be transmitted. In this case, the access network device does not send an RRCConnectionRelease message, but instead sends an L3 message (i.e., an RRC Connection Resume message) to instruct the terminal device to return to the connected state to continue data transmission.

[0063] It should be noted that the above method of indicating the termination of data transmission by carrying an L3 message (i.e., RRCEarlyDataComplete message or RRCConnectionRelease message) has a large transmission overhead.

[0064] Based on this, embodiments of this application provide a communication method and apparatus. In this method, the terminal device can determine whether to terminate data transmission by whether the second message carries an L3 message (i.e., an RRC connection establishment message or an RRC connection recovery message) or L2 information (i.e., a cell radio network temporary identifier (C-RNTI)). Compared with the current method of instructing the terminal device to terminate data transmission by carrying an L3 message (i.e., an RRC EarlyDataComplete message or an RRCConnectionRelease message) in the second message, this method helps to reduce the transmission overhead of the second message.

[0065] The communication method and apparatus provided in the embodiments of this application are further described below:

[0066] Please refer to Figure 5, which is a flowchart of a communication method provided in an embodiment of this application. This communication method includes steps S501-S503. The method shown in Figure 5 can be interactively executed by a terminal device and an access network device. Wherein:

[0067] S501, The terminal device sends a first message to the access network device. Correspondingly, the access network device receives the first message from the terminal device.

[0068] The first message may be, for example, Msg3. This first message includes a Common Control Channel (CCCH) Service Data Unit (SDU). Optionally, the first message may also include uplink data. The uplink data may be user data sent by the terminal device to the access network device, such as video data, voice data, etc. The CCCH SDU can be used to carry RRC messages, such as RRCEarlyDataRequest, RRCConnectionResumeRequest, etc. It should be understood that the uplink data in this application is not a CCCH SDU; for example, the uplink data may be carried by a Dedicated Traffic Channel (DTCH) SDU.

[0069] S502, the access network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the access network device.

[0070] The second message is used in response to the first message. The second message can be, for example, Msg4. In the EDT, whether Msg4 contains downlink data is optional. Downlink data refers to user data sent from the access network device to the terminal device, such as video data, voice data, etc. For ease of understanding, the following text will primarily use Msg3 as the first message and Msg4 as the second message as an example. Below, we will first introduce two formats of Msg4.

[0071] For example, the format of Msg4 can be as shown in Figure 6a. As shown in Figure 6a, taking the example that Msg4 includes 4 subheaders and 4 payloads, the 4 subheaders can be subheader 610-1, subheader 610-2, subheader 610-3 and subheader 610-4 shown in Figure 6a, and the 4 payloads can be payload 620-1, payload 620-2, payload 620-3 and payload 620-4 shown in Figure 6a. Specifically, subheader 610-1 (the first subheader in Msg4) corresponds to payload 620-1 (the first payload in Msg4), subheader 610-2 (the second subheader in Msg4) corresponds to payload 620-2 (the second payload in Msg4), subheader 610-3 (the third subheader in Msg4) corresponds to payload 620-3 (the third payload in Msg4), and subheader 610-4 (the fourth subheader in Msg4) corresponds to payload 620-4 (the fourth payload in Msg4).

[0072] As another example, the format of Msg4 can also be as shown in Figure 6b. As shown in Figure 6b, Msg4 includes one or more subprotocol data units (subPDUs). One possible format of a subPDU is shown in Figure 6c, where a subPDU can consist of a subheader and a payload.

[0073] For example, one possible format of the payload is shown in Figure 6d. The payload can be the payload in Figure 6a or the payload in Figure 6c, and this application does not limit it. The payload includes UE contention resolution identity, R (i.e., reserved bit), channel access-cyclic prefix extension (ChannelAccess-CPext), transmit power control (TPC), hybrid automatic repeat request (HARQ) feedback timing indicator, physical uplink control channel (PUCCH) resource indicator, timing advance command (TAC), and C-RNTI information. The UE contention resolution identity occupies 48 bits and is used by the terminal device to determine whether the corresponding payload is sent to the terminal itself. The ChannelAccess-CPext indicates the channel access type and the cyclic prefix extension of PUCCH resources, used for channel access in the shared spectrum. The TPC can be used to dynamically adjust the transmit power to optimize system performance, improve coverage, reduce power consumption and interference, thereby achieving more reliable and efficient communication services. The HARQ Feedback Timing Indicator can be used to indicate the timing of HARQ feedback. By performing HARQ feedback at the appropriate time, data transmission performance can be optimized, transmission latency can be reduced, and system throughput and channel utilization can be improved. The PUCCH Resource Indicator can be used to indicate the resource allocation status of the terminal device on the physical uplink control channel, optimize resource allocation, improve system performance and efficiency, and ensure the transmission of important control information. The TAC can be used to adjust the uplink timing of the terminal device. The C-RNTI can be used for subsequent scheduling to indicate the resources allocated to the terminal device by the access network device. Subsequent scheduling is a dynamic resource allocation mechanism in a communication system, used to optimize the utilization of system resources and meet the communication needs of different terminal devices.In subsequent scheduling, the access network equipment dynamically adjusts the resources allocated to the terminal equipment based on the terminal equipment's current status, channel conditions, and communication requirements. These resources include time-frequency resources, modulation schemes, and coding schemes.

[0074] S503: The terminal device determines whether to terminate data transmission based on whether the second message carries a C-RNTI or the first RRC message.

[0075] The following two schemes explain the specific methods by which the terminal device determines whether to terminate data transmission based on whether the second message carries a C-RNTI or the first RRC message.

[0076] Option 1: The terminal device determines whether to terminate data transmission based on whether the second message carries a C-RNTI.

[0077] Generally speaking, if the second message carries the C-RNTI, the terminal device can determine to continue data transmission (or not terminate data transmission); if the second message does not carry the C-RNTI, the terminal device can determine to terminate data transmission (or not continue data transmission).

[0078] Specifically, the second message may include a response unit (hereinafter referred to as the first response unit for ease of distinction). This first response unit may be, for example, the payload in Msg4, and it includes a contention resolution identifier (hereinafter referred to as the first contention resolution identifier). In one possible implementation, if the first contention resolution identifier matches the CCCH SDU, the terminal device can determine whether to terminate data transmission based on whether the first response unit carries a C-RNTI. Alternatively, if the first contention resolution identifier is the same as the terminal identification information included in the first message, the terminal device can determine whether to terminate data transmission based on whether the first response unit carries a C-RNTI. Specifically, this terminal identification information is carried in the CCCH SDU. For example, the terminal identification information may specifically be the information carried in the first 48 bits of the CCCH SDU; that is, if the first 48 bits of the CCCH SDU match the first contention resolution identifier, the terminal device can determine whether to terminate data transmission based on whether the first response unit carries a C-RNTI. Understandably, when the first contention resolution identifier matches the CCCH SDU sent by the access network device, the terminal device considers the first response unit to be for itself, and then the terminal device can determine whether it should terminate data transmission based on whether the first response unit carries C-RNTI.

[0079] It is understandable that the terminal device continues data transmission when the C-RNTI is carried in the first response unit. In Scheme 1, the so-called continued data transmission by the terminal device can be understood as the terminal device receiving and / or sending data based on the C-RNTI. Specifically, the access network device can schedule data transmission based on the C-RNTI, and correspondingly, the terminal device can receive and / or send data based on the C-RNTI. For example, in the case of downlink data transmission, the access network device can schedule resources on the physical downlink shared channel (PDSCH) for transmitting downlink data through downlink control information (DCI). This DCI is scrambled with C-RNTI. Accordingly, the terminal device can receive the downlink data carried on the resources on the PDSCH scheduled by the DCI based on the C-RNTI, or the terminal device can descramble the DCI based on the C-RNTI to obtain the resources scheduled by the DCI on the PDSCH, and further receive downlink data on those resources. For example, in the case of uplink data transmission, the access network device can schedule resources on the physical uplink shared channel (PUSCH) for uplink data transmission through the DCI. In other words, the access network device will inform the terminal device of the resources allocated to it for uplink transmission through the DCI. Therefore, the terminal device can send uplink data on the resources allocated to it. The DCI sent by the access network device for scheduling resources on the PUSCH is scrambled by C-RNTI. Accordingly, the terminal device can receive the DCI that has scheduled resources on the PUSCH based on C-RNTI, or the terminal device can descramble the DCI based on C-RNTI to obtain the resources allocated to it on the PUSCH, and then the terminal device can send uplink data on the resources.

[0080] It should be noted that under the implementation of Scheme 1 above, although the terminal device continues data transmission, it does not actually switch to connected mode. In other words, under Scheme 1, the terminal device remains in an idle state, but it is an idle state in which the terminal device can perform a small amount of data transmission; that is, the terminal device is still executing the EDT process.

[0081] It is understandable that if the C-RNTI is not carried in the first response unit, the terminal device terminates data transmission. This termination of data transmission can be understood as the terminal device terminating the EDT process, or the terminal device switching to / returning to / remaining in an idle state, or the terminal device ceasing user data transmission, or the terminal device stopping user data transmission altogether.

[0082] Optionally, the second message in this application also includes a first sub-header, which corresponds to the first response unit. This first sub-header can be the subheader in Figure 6a or the subheader in Figure 6c; this application does not limit the specific sub-header. For example, the first sub-header can be subheader 610-1 as shown in Figure 6a, and the first response unit can be payment 620-1 as shown in Figure 6a. Alternatively, the first sub-header can be the subheader as shown in Figure 6c, and the first response unit can be payment 620-1 as shown in Figure 6c; that is, the first sub-header and the first response unit can form a subPDU. The first sub-header includes first information. When the value of the first information is a first value, it indicates that the first response unit carries a C-RNTI; when the value of the first information is a second value, it indicates that the first response unit does not carry a C-RNTI. For example, taking 1 bit of the first information in the first sub-header as an example, when the value of this 1 bit is 1, it indicates that the first response unit carries a C-RNTI; when the value of this 1 bit is 0, it indicates that the first response unit does not carry a C-RNTI.

[0083] For example, the format of the first subheader is illustrated using the structure in Figure 6a. The format of the first subheader can be as shown in Figure 7. In Figure 7, E can be used to indicate whether this is the last subheader. E can occupy 1 bit in the first subheader (e.g., the first bit in the first subheader). When the value of this 1 bit is 1, it indicates that there is another subheader following; when the value of this 1 bit is 0, it indicates that there is no more subheader following. In Figure 7, S can be used to indicate whether a subheader associated with a payload including a MAC SDU immediately follows this subheader. It should be understood that the MAC SDU carries information from layers above the MAC layer. S can also occupy 1 bit in the first subheader (e.g., the second bit in the first subheader). When the value of this 1 bit is 1, it indicates that a subheader associated with a payload including a MAC SDU immediately follows this subheader; when the value of this 1 bit is 0, it indicates that there is no subheader associated with a payload carrying a MAC SDU following this subheader. As shown in Figure 7, S1 is a newly added field (i.e., the first information in this application), used to indicate whether the payload carries a C-RNTI. For example, S1 can occupy 1 bit in the first sub-header (e.g., the 3rd bit in the first sub-header). When the value of this 1 bit is 1, it indicates that the payload carries a C-RNTI; when the value of this 1 bit is 0, it indicates that the payload does not carry a C-RNTI. Optionally, S1 can also occupy multiple bits, such as 2 bits. When the value of these 2 bits is 11, it indicates that the payload carries a C-RNTI; when the value of this 1 bit is 00, it indicates that the payload does not carry a C-RNTI. It can be understood that when the terminal device determines that the payload carries a C-RNTI based on the value of S1, the terminal device can use the C-RNTI to continue receiving subsequent scheduling. When the terminal device determines that the payload does not carry a C-RNTI based on the value of S1, the terminal device can terminate data transmission, or terminate the EDT process, or the terminal device can remain in an idle state. R in Figure 7 is a reserved bit.

[0084] To illustrate further, let's take the structure in Figure 6b as an example to explain the format of the first subheader. The format of the first subheader can also be as shown in Figure 7. In Figure 7, E can be used to indicate whether this is the last subPDU. E can occupy 1 bit in the first subheader (for example, it can be the first bit in the first subheader). When the value of this 1 bit is 1, it indicates that there is a subPDU following. When the value of this 1 bit is 0, it indicates that there is no subPDU following. In Figure 7, S can be used to indicate whether a subPDU containing a MAC SDU follows this subPDU. S can also occupy 1 bit in the first subheader (for example, it can be the second bit in the first subheader). When the value of this 1 bit is 1, it indicates that a subPDU containing a MAC SDU follows this subPDU. When the value of this 1 bit is 0, it indicates that there is no subPDU containing a MAC SDU following this subPDU. In Figure 7, S1 is a newly added field (i.e., the first information in this application), which is used to indicate whether the payload carries a C-RNTI. For example, S1 can occupy 1 bit in the first sub-header (e.g., the 3rd bit in the first sub-header). When the value of this 1 bit is 1, it indicates that the payload carries a C-RNTI; when the value of this 1 bit is 0, it indicates that the payload does not carry a C-RNTI. Optionally, S1 can also occupy multiple bits, such as 2 bits. When the value of these 2 bits is 11, it indicates that the payload carries a C-RNTI; when the value of this 1 bit is 00, it indicates that the payload does not carry a C-RNTI. It is understood that when the terminal device determines that the payload carries a C-RNTI based on the value of S1, the terminal device can use the C-RNTI to continue receiving subsequent scheduling. When the terminal device determines that the payload does not carry a C-RNTI based on the value of S1, the terminal device can terminate data transmission, or terminate the EDT process, or the terminal device can remain in an idle state. R in Figure 7 is a reserved bit.

[0085] Option 2: The terminal device determines whether to terminate data transmission based on whether the second message carries the first RRC message.

[0086] Generally speaking, if the second message carries the first RRC message, the terminal device can determine to continue data transmission (or not terminate data transmission); if the second message does not carry the first RRC message, the terminal device can determine to terminate data transmission (or not continue data transmission).

[0087] The first RRC message can be either an RRC connection establishment message or an RRC connection recovery message.

[0088] Specifically, the second message may include a response unit (hereinafter referred to as the second response unit for ease of distinction). This second response unit may, for example, be the payload in Msg4, and it includes a contention resolution identifier (hereinafter referred to as the second contention resolution identifier for ease of distinction). In one possible implementation, if the second contention resolution identifier matches the CCCH SDU, the terminal device can determine whether to terminate data transmission based on whether the second message carries a first RRC message. For a detailed description of the specific implementation of "the second contention resolution identifier matching the CCCH SDU," please refer to the description of the specific implementation of "the first contention resolution identifier matching the CCCH SDU," which will not be repeated here.

[0089] It is understandable that when the second message carries the first RRC message, the terminal device continues data transmission. In Scheme 2, the so-called continued data transmission by the terminal device can be understood as the terminal device receiving and / or sending data based on the RRC connection. That is, when the first RRC message is an RRC connection establishment message, the terminal device can establish an RRC connection with the access network device based on the RRC connection establishment message, and then receive downlink data and / or send uplink data on the RRC connection; when the first RRC message is an RRC connection recovery message, the terminal device can restore the RRC connection with the access network device based on the RRC connection recovery message, and then receive downlink data and / or send uplink data on the RRC connection. For example, if the terminal device receives downlink data sent by the access network device based on the RRC connection, the downlink data may be control information, broadcast messages, system information, etc. Optionally, the downlink data may also be user data, such as voice call data, video stream data, etc. As another example, if the terminal device sends uplink data to the access network device based on the RRC connection, the uplink data may be user data, such as voice call data, video stream data, etc. Optionally, the terminal device can also send location update requests, measurement reports, etc. to the access network device via the RRC connection for network management and optimization.

[0090] It should be noted that in the implementation of Scheme 2 above, the terminal device switches to a connected state for data transmission. In other words, in Scheme 2, the data transmission performed by the terminal device is no longer the data transmission during the EDT process.

[0091] It is understandable that if the second message does not carry the first RRC message, the terminal device terminates data transmission. This termination of data transmission can be understood as the terminal device terminating the EDT process, or the terminal device switching to / returning to / remaining in an idle state, or the terminal device ceasing user data transmission, or the terminal device stopping user data transmission altogether.

[0092] It should be noted that the MAC SDU carries information from layers above the MAC layer. Figure 8 shows a schematic diagram of the LTE / NR control plane protocol stack, which includes the physical layer (PHY), medium access control layer (MAC), radio link control layer (RLC), packet data convergence protocol layer (PDCP), RRC layer, and non-access stratum (NAS). The RLC, PDCP, RRC, and NAS layers are all layers above the MAC layer. Since both the RRC connection establishment message and the RRC connection recovery message are generated by the RRC layer, the first RRC message in this application can be specifically carried in the MAC SDU for transmission. The MAC SDU is carried in the response unit (hereinafter referred to as the third response unit for ease of distinction). Based on this, the termination of data transmission in the second message without carrying the first RRC message, as described in this application, may have the following two scenarios:

[0093] Case 1: When the second message does not include a third response unit, the data transmission is terminated.

[0094] Case 2: When the second message includes N third response units, and none of the N third response units carry the first RRC message, the data transmission is terminated, where N is an integer greater than 0.

[0095] Optionally, the second message in this application also includes a second sub-header, which corresponds to a second response unit. This second sub-header can be the subheader in Figure 6a or the subheader in Figure 6c; this application does not limit the specific sub-header. For example, the second sub-header can be subheader 610-1 as shown in Figure 6a, and the second response unit can be payment 620-1 as shown in Figure 6a. Alternatively, the second sub-header can be the subheader as shown in Figure 6c, and the second response unit can be payment 620-1 as shown in Figure 6c; that is, the second sub-header and the second response unit can form a subPDU. The second sub-header includes second information, which indicates N, or, in other words, indicates the number of third response units including the MAC SDU. For example, taking 1 bit of the second information in the second sub-header as an example, when the value of this 1 bit is 0, it indicates that the size of N is 1; when the value of this 1 bit is 0, it indicates that the size of N is 2. For another example, the second information can also be multiple bits in the second sub-header. For example, taking 2 bits as an example, when the value of the 1 bit is 00, it means that the size of N is 0; when the value of the 1 bit is 01, it means that the size of N is 1; when the value of the 1 bit is 10, it means that the size of N is 2; when the value of the 1 bit is 11, it means that the size of N is 3.

[0096] For example, the format of the second subheader is illustrated using the structure in Figure 6b. The format of the second subheader can be as shown in Figure 9. In Figure 9, E can be used to indicate whether this is the last subPDU. E can occupy 1 bit in the first subheader (for example, it can be the first bit in the first subheader). When the value of this 1 bit is 1, it indicates that there is a subPDU following. When the value of this 1 bit is 0, it indicates that there is no more subPDU following.

[0097] As shown in Figure 9, S can be used to indicate whether at least one subPDU containing a MAC SDU follows this subPDU. It should be understood that the MAC SDU carries information from layers above the MAC layer, such as RRC connection establishment messages. S can also occupy 1 bit in the second sub-header (for example, the second bit in the second sub-header). When the value of this 1 bit is 1, it indicates that at least one subPDU containing a MAC SDU follows this subPDU. When the value of this 1 bit is 0, it indicates that no subPDU containing a MAC SDU follows this subPDU.

[0098] As shown in Figure 9, S2 is a newly added field (i.e., the second information in this application), which is used to indicate the specific number of MAC SDUs (or the number of third response units including MAC SDUs). Figure 9 only shows the case where S2 occupies only 1 bit; in practice, S2 can also occupy multiple bits. R in Figure 9 is a reserved bit.

[0099] Optionally, S and S2 in Figure 9 above can also be combined into a single indicator field S' for joint indication. For example, S' can be 2 bits. When the value of S' is 00, it indicates that there is no subPDU containing a MAC SDU following it. When the value of S' is 01, it indicates that one subPDU containing a MAC SDU follows it. When the value of S' is 10, it indicates that two subPDUs containing MAC SDUs follow it. When the value of S' is 11, it indicates that three subPDUs containing MAC SDUs follow it.

[0100] It is understandable that the aforementioned N third response units and second response units are related, or that the N third response units and second response units are associated. This association means that the second response unit and the N third response units are response units targeting the same terminal device.

[0101] It is understood that the first response unit, second response unit, and third response unit mentioned in the embodiments of this application can all be understood as payloads, or as random access responses (RARs). The first and second response units carry information generated by the MAC layer itself, such as C-RNTI and contention resolution identifiers. The third response unit carries a MAC SDU, which contains information generated by layers above the MAC layer, such as CCCH SDU, dedicated control channel (DCCH) SDU, and dedicated traffic channel (DTCH) SDU.

[0102] As can be seen, based on the method described in Figure 2, the terminal device can determine whether to terminate data transmission by whether the second message carries a Layer 3 message (i.e., the first RRC message) or Layer 2 information (i.e., C-RNTI). Compared to the current method of instructing the terminal device to terminate data transmission by carrying a Layer 3 message (e.g., an RRC EarlyDataComplete message) in the second message, this method helps reduce the transmission overhead of the second message. Furthermore, when the total uplink and downlink resources are limited, reducing the transmission overhead of downlink transmission (i.e., the second message) also helps increase the availability of uplink resources, thereby improving uplink capacity.

[0103] Please refer to Figure 10, which is a schematic diagram of a communication device according to an embodiment of this application. This communication device can be used to perform some or all of the functions of the reader / writer in the above method embodiments. The communication device can be a device with computing capabilities (e.g., a terminal device) or a device with computing capabilities (e.g., a chip in a terminal device). The communication device shown in Figure 10 includes a communication unit 1001 and a processing unit 1002. The communication unit 1001 is used for sending and receiving data. The communication unit 1001 integrates a receiving unit and a sending unit. The communication unit 1001 can also be called a transceiver unit. Alternatively, the communication unit 1001 can be split into a receiving unit and a sending unit. The processing unit 1002 is used to process the data. Wherein:

[0104] Communication unit 1001 is used to send a first message, the first message including a Common Control Channel (CCCH) Service Data Unit (SDU);

[0105] The communication unit 1001 is also used to receive a second message, which is used to respond to the first message;

[0106] The processing unit 1002 is configured to determine whether to terminate data transmission based on whether the second message carries a Cell Radio Network Temporary Identifier (C-RNTI) or a first Radio Resource Control (RRC) message.

[0107] In one possible embodiment, the second message includes a first response unit, which includes a first contention resolution identifier that matches the CCCH SDU; when performing the above-described determination of whether to terminate data transmission based on whether the second message carries a C-RNTI, the processing unit 1002 is specifically used to determine whether to terminate data transmission based on whether the first response unit carries a C-RNTI.

[0108] In one possible embodiment, when performing the above-described determination of whether to terminate data transmission based on whether the first response unit carries a C-RNTI, the processing unit 1002 is specifically used to continue data transmission if the first response unit carries a C-RNTI; the processing unit 1002 is also used to terminate data transmission if the first response unit does not carry a C-RNTI.

[0109] In one possible embodiment, during the aforementioned continued data transmission, the communication unit 1001 is specifically configured to receive and / or send data according to C-RNTI.

[0110] In one possible embodiment, the second message includes a first sub-header corresponding to a first response unit, the first sub-header including first information; when the value of the first information is a first value, it indicates that the first response unit carries C-RNTI; when the value of the first information is a second value, it indicates that the first response unit does not carry C-RNTI.

[0111] In one possible embodiment, the second message includes a second response unit, which includes a second contention resolution identifier and a CCCH SDU match; when performing the above-described determination of whether to terminate data transmission based on whether the second message carries a first RRC message:

[0112] Processing unit 1002 is specifically used to continue data transmission when the second message carries the first RRC message;

[0113] The processing unit 1002 is also configured to terminate data transmission if the second message does not carry the first RRC message.

[0114] In one possible embodiment, the first RRC message is an RRC connection establishment message or an RRC connection recovery message.

[0115] In one possible embodiment, during the aforementioned continued data transmission, the communication unit 1001 is used to receive and / or send data based on the RRC connection.

[0116] In one possible embodiment, when terminating data transmission in the case where the second message does not carry the first RRC message, the processing unit 1002 is configured to terminate data transmission when the second message does not include a third response unit; or, the processing unit 1002 is further configured to terminate data transmission when the second message includes N third response units and none of the N third response units carry the first RRC message, where N is an integer greater than 0.

[0117] The third response unit carries the Media Access Control (MAC) SDU, and the MAC SDU carries the first RRC message.

[0118] In one possible embodiment, the second message includes a second sub-header corresponding to a second response unit, and the second sub-header includes second information used to indicate N.

[0119] In one possible embodiment, the N third response units and the second response unit are associated.

[0120] This application also provides a chip that can execute the relevant steps of the terminal device in the foregoing method embodiments. The chip includes a processor and a communication interface. The processor is configured to cause the chip to perform the following operations:

[0121] Send the first message, which includes the Common Control Channel (CCCH) Service Data Unit (SDU).

[0122] Receive the second message, which is used in response to the first message;

[0123] Whether to terminate data transmission depends on whether the second message carries the Cell Radio Network Temporary Identifier (C-RNTI) or the first Radio Resource Control (RRC) message.

[0124] In one possible embodiment, the second message includes a first response unit, which includes a first contention resolution identifier that matches the CCCH SDU; when performing the above-described determination of whether to terminate data transmission based on whether the second message carries a C-RNTI, the chip is further configured to determine whether to terminate data transmission based on whether the first response unit carries a C-RNTI.

[0125] In one possible embodiment, when performing the above-described determination of whether to terminate data transmission based on whether the first response unit carries a C-RNTI, the chip is further configured to continue data transmission if the first response unit carries a C-RNTI; and to terminate data transmission if the first response unit does not carry a C-RNTI.

[0126] In one possible embodiment, while performing the aforementioned continued data transmission, the chip is also used to receive and / or send data according to C-RNTI.

[0127] In one possible embodiment, the second message includes a first sub-header corresponding to a first response unit, the first sub-header including first information; when the value of the first information is a first value, it indicates that the first response unit carries C-RNTI; when the value of the first information is a second value, it indicates that the first response unit does not carry C-RNTI.

[0128] In one possible embodiment, the second message includes a second response unit, which includes a second contention resolution identifier and a CCCH SDU match; when performing the above-described determination of whether to terminate data transmission based on whether the second message carries a first RRC message, the chip is further configured to continue data transmission if the second message carries a first RRC message; the chip is further configured to terminate data transmission if the second message does not carry a first RRC message.

[0129] In one possible embodiment, the first RRC message is an RRC connection establishment message or an RRC connection recovery message.

[0130] In one possible embodiment, while performing the aforementioned continued data transmission, the chip is also used to receive and / or send data based on the RRC connection.

[0131] In one possible embodiment, when terminating data transmission in the case where the second message does not carry the first RRC message, the chip is further configured to terminate data transmission when the second message does not include a third response unit; or, the chip is further configured to terminate data transmission when the second message includes N third response units, and none of the N third response units carry the first RRC message, where N is an integer greater than 0; wherein the third response unit carries a Media Access Control (MAC) SDU, and the MAC SDU carries the first RRC message.

[0132] In one possible embodiment, the second message includes a second sub-header corresponding to a second response unit, and the second sub-header includes second information used to indicate N.

[0133] In one possible embodiment, the N third response units and the second response unit are associated.

[0134] Optionally, the chip includes at least one processor, at least one first memory, and at least one second memory; wherein the at least one first memory and the at least one processor are interconnected by a circuit, and the first memory stores instructions; the at least one second memory and the at least one processor are interconnected by a circuit, and the second memory stores data that needs to be stored in the above method embodiments.

[0135] For each device or product applied to or integrated into a chip, each of its modules can be implemented using hardware methods such as circuits, or at least some modules can be implemented using software programs that run on a processor integrated inside the chip, while the remaining (if any) modules can be implemented using hardware methods such as circuits.

[0136] Referring to Figure 11, which is a schematic diagram of a communication device according to an embodiment of this application, the communication device may include a memory 1101 and a processor 1102. Optionally, it may also include a communication interface 1103. The memory 1101, processor 1102, and communication interface 1103 are connected through one or more communication buses. The communication interface 1103 is controlled by the processor 1102 for sending and receiving information.

[0137] Memory 1101 may include read-only memory and random access memory, and provides instructions and data to processor 1102. A portion of memory 1101 may also include non-volatile random access memory.

[0138] Communication interface 1103 is used to receive or send data.

[0139] Processor 1102 can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor; optionally, processor 1102 can also be any conventional processor. Wherein:

[0140] Memory 1101 is used to store program instructions.

[0141] Processor 1102 is used to call program instructions stored in memory 1101.

[0142] The processor 1102 calls the program instructions stored in the memory 1101, causing the communication device 1100 to execute the method executed by the terminal device in the above method embodiment.

[0143] Referring to Figure 12, which is a schematic diagram of the structure of a module device provided in an embodiment of this application, the module device 1200 can perform the relevant steps of the terminal device in the aforementioned method embodiment. The module device 1200 includes: a communication module 1201, a power module 1202, a storage module 1203, and a chip 1204.

[0144] The power module 1202 is used to provide power to the module device; the storage module 1203 is used to store data and instructions; the communication module 1201 is used for internal communication within the module device or for communication between the module device and external devices; and the chip 1204 is used to execute the method executed by the terminal device in the above method embodiment.

[0145] It should be noted that the contents not mentioned in the embodiments corresponding to Figures 11 and 12, as well as the specific implementation methods of each step, can be found in the content of the method embodiments, and will not be repeated here.

[0146] This application also provides a computer-readable storage medium storing instructions that, when executed on a processor, enable the implementation of the method flow described in the above method embodiments.

[0147] This application also provides a computer program product that stores computer-readable instructions. When the computer-readable instructions are run on a computer, the computer executes the method flow of the above-described method embodiments.

[0148] Regarding the modules / units included in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or a combination of both. For example, for various devices and products applied to or integrated into a chip, all of their modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on the chip's integrated processor, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into a chip module, all of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same part (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units... It can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, the modules / units they contain can all be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0149] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some operations can be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0150] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and operations of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0151] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: Send a first message, which includes a Common Control Channel (CCCH) Service Data Unit (SDU). Receive a second message, which is used in response to the first message; Whether to terminate data transmission depends on whether the second message carries a Cell Radio Network Temporary Identifier (C-RNTI) or a First Radio Resource Control (RRC) message.

2. The method according to claim 1, characterized in that, The second message includes a first response unit, which includes a first contention resolution identifier that matches the CCCH SDU; the step of determining whether to terminate data transmission based on whether the second message carries a C-RNTI includes: Whether to terminate data transmission is determined based on whether the first response unit carries a C-RNTI.

3. The method according to claim 2, characterized in that, The step of determining whether to terminate data transmission based on whether the first response unit carries a C-RNTI includes: If the C-RNTI is carried in the first response unit, data transmission continues; If the C-RNTI is not carried in the first response unit, the data transmission is terminated.

4. The method according to claim 3, characterized in that, The continued data transmission includes: Data is received and / or transmitted according to the C-RNTI.

5. The method according to any one of claims 2-4, characterized in that, The second message includes a first sub-header, which corresponds to the first response unit, and the first sub-header includes first information; When the value of the first information is the first value, it indicates that the first response unit carries the C-RNTI; When the value of the first information is the second value, it indicates that the first response unit does not carry the C-RNTI.

6. The method according to claim 1, characterized in that, The second message includes a second response unit, which includes a second contention resolution identifier that matches the CCCH SDU; the step of determining whether to terminate data transmission based on whether the second message carries a first RRC message includes: If the first RRC message is carried in the second message, data transmission continues; If the second message does not carry the first RRC message, the data transmission is terminated.

7. The method according to claim 6, characterized in that, The first RRC message is either an RRC connection establishment message or an RRC connection recovery message.

8. The method according to claim 6 or 7, characterized in that, The continued data transmission includes: Data is received and / or sent via an RRC connection.

9. The method according to any one of claims 6-8, characterized in that, The termination of data transmission when the second message does not carry the first RRC message includes: When the second message does not include a third response unit, data transmission is terminated; or... When the second message includes N third response units, and none of the N third response units carry the first RRC message, the data transmission is terminated, where N is an integer greater than 0. The third response unit carries the Media Access Control (MAC) SDU, and the MAC SDU carries the first RRC message.

10. The method according to claim 9, characterized in that, The second message includes a second sub-header, which corresponds to the second response unit. The second sub-header includes second information, which is used to indicate the N.

11. The method according to claim 9 or 10, characterized in that, The N third response units and the second response unit are related.

12. A communication device, characterized in that, The apparatus includes a unit for performing the method as described in any one of claims 1 to 11.

13. A chip, characterized in that, The device includes a processor and a communication interface, the processor being configured to perform the method as described in any one of claims 1 to 11, and the communication interface being configured to receive signals from other devices outside the chip and transmit them to the processor or to send signals from the processor to other devices outside the chip.

14. A module device, characterized in that, The module device includes a communication module, a power module, a storage module, and a chip, wherein: The power module is used to provide electrical energy to the module device; The storage module is used to store data and instructions; The communication module is used for internal communication within the module device, or for communication between the module device and external devices; The chip is used to perform the method as described in any one of claims 1 to 11.

15. A communication device, characterized in that, The device includes a memory and a processor, the memory being used to store a computer program, the computer program including program instructions, and the processor being configured to invoke the program instructions to perform the method as described in any one of claims 1 to 11.

16. A computer-readable storage medium, characterized in that, The computer storage medium stores computer-readable instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 11.

Images