Communication method and device

Abstract

A communication method and a communication device, the communication method comprising: a sending end sending an MAC sub PDU to a receiving end, an RRC message included in the MAC sub PDU comprising one or more of a UL CCCH message, a UL CCCH1 message, or a UL DCCH message. Specifically, the header of the MAC sub PDU comprises an LCID domain, and the sending end can transmit indication information for auxiliary communication through the LCID domain. In addition, the MAC sub PDU further comprises a first domain, and when the values of the first domain are different, the meaning represented by the LCID domain is determined according to different LCID tables. By carrying the first domain in the MAC sub PDU, the meaning represented by the LCID domain can be determined based on the value of the first domain and the value of the LCID domain, and does not depend on the value of the LCID domain independently, so that more indication information can be indicated through the LCID domain, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] In wireless communication, some indication information for assisting communication may be exchanged between the transmitting end and the receiving end, for example, information indicating the type of device, information indicating the logical channel, etc. These indication information may be carried in messages of various protocol layers, including but not limited to being carried in radio resource control (RRC) messages or media access control (MAC) packets. When the indication information is carried in a MAC packet, it may be carried in the header of a MAC packet data unit (PDU) or in a MAC service data unit (SDU) or in a MAC control element (CE).

[0003] The indication information can be indicated using the LCID field in the MAC PDU header, but with the evolution of the standard, more and more content that needs to be indicated is introduced in the standard, and the existing LCID indication method is far from meeting the needs. Therefore, how to indicate more content through the existing fields has become an urgent problem to be solved. Summary of the invention

[0004] The present application provides a communication method that can indicate more indication information through existing fields, enrich the service types of terminal devices and improve user experience.

[0005] In a first aspect, a communication method is provided, which can be executed by a sending end, wherein the sending end can be a terminal device, a network device, or a chip of a terminal device, a chip of a network device, etc., without limitation.

[0006] The communication method includes: determining a media access control MAC sub-packet data unit PDU, the MAC sub-PDU including an RRC message, the RRC message including an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU including a logical channel identifier LCID field, the MAC sub-PDU including a first field; sending the MAC sub-PDU; wherein, when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0007] Based on the above scheme, the MAC sub-PDU determined by the transmitting end includes, in addition to the LCID domain, a first domain that affects the meaning represented by the LCID domain. Specifically, the value of the first domain is used to indicate which LCID table the meaning represented by the LCID domain is determined based on, so that the meaning represented by the LCID domain can be determined based on the value of the first domain and the value of the LCID domain, and no longer depends solely on the value of the LCID domain, so that more indication information can be indicated by the LCID domain. For example, in this scheme, there can be multiple LCID tables that represent the value of the LCID domain and the meaning represented by the LCID domain. When actually determining the meaning represented by the LCID domain, the LCID table used can be determined based on the value of the first domain, and then the meaning represented by the LCID domain can be determined based on the value of the LCID domain and the determined LCID table. Compared with determining the meaning represented by the LCID domain based only on the value of the LCID domain, more indication information is indicated by the LCID domain. Further, expanding the information that the LCID domain can indicate can enrich the service types of the terminal device and improve the user experience.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the MAC sub-PDU includes a first field, including: the header of the MAC sub-PDU includes the first field; or the RRC message includes the first field.

[0009] Based on the above scheme, the first domain can be carried in the header of the MAC sub-PDU, or can also be carried in the RRC message in the MAC sub-PDU. The scheme does not limit the specific carrying method of the first domain. It can be used as a domain in the header of the MAC sub-PDU, or as a domain in the RRC message in the MAC sub-PDU, thereby improving the flexibility of the scheme.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the LCID table is a correspondence between the index value of the LCID domain and the meaning represented by the index value of the LCID domain.

[0011] In combination with the first aspect, in certain implementations of the first aspect, before sending the MAC sub-PDU, the method further includes: determining that the receiving end supports parsing the MAC sub-PDU.

[0012] Based on the above scheme, before sending a MAC sub-PDU to a receiving end, the sending end can determine that the receiving end supports parsing the MAC sub-PDU, thereby avoiding the situation where the MAC sub-PDU sent to the receiving end cannot be correctly parsed by the receiving end, resulting in communication errors.

[0013] In combination with the first aspect, in certain implementations of the first aspect, determining that the receiving end supports parsing the MAC sub-PDU includes: receiving indication information, wherein the indication information is used to indicate that the receiving end supports parsing the MAC sub-PDU; or, determining that the receiving end supports parsing the MAC sub-PDU based on whether the receiving end supports the characteristics indicated by the MAC sub-PDU.

[0014] Based on the above scheme, the sending end can determine whether the receiving end can parse the MAC sub-PDU by: through the indication information sent by the receiving end, or the receiving end can determine whether the receiving end supports parsing the corresponding MAC sub-PDU based on the characteristics supported by the receiving end without displaying the indication information sent to indicate whether the MAC sub-PDU is supported. In this scheme, the sending end can determine whether the receiving end supports parsing the MAC sub-PDU to be sent in different ways, thereby improving the flexibility of the scheme.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

[0016] Based on the above solution, the receiving end may send the indication information to the sending end in the form of broadcast, multicast or unicast, which is not limited in this solution.

[0017] In combination with the first aspect, in certain implementations of the first aspect, sending the MAC sub-PDU includes: sending the MAC sub-PDU during a random access process.

[0018] In combination with the first aspect, in certain implementations of the first aspect, if the first field is carried in the header of the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the size of the LCID field is 6 bits, and the size of the first field is 1 or 2 bits.

[0019] In combination with the first aspect, in certain implementations of the first aspect, if the first field is carried in the RRC message in the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, and the header of the MAC sub-PDU also includes two reserved fields, the size of the LCID field is 6 bits, and the size of each of the reserved fields is 1 bit.

[0020] Based on the above scheme, the size of the header of the above MAC sub-PDU is one byte, that is, the scheme can indicate more indication information through the LCID field without increasing the size of the MAC sub-PDU. Furthermore, expanding the information that the LCID field can indicate can enrich the service types of the terminal device and improve the user experience.

[0021] In a second aspect, a communication method is provided, which can be executed by a receiving end, wherein the sending end can be a terminal device, a network device, or a chip of a terminal device, a chip of a network device, etc., without limitation. For example, the sending end in the first aspect is a terminal device or a chip of a terminal device, and the receiving end can be a network device or a chip of a network device.

[0022] The communication method includes: receiving a media access control MAC sub-packet data unit PDU, the MAC sub-PDU including an RRC message, the RRC message including an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU including a logical channel identifier LCID field, the MAC sub-PDU including a first field; determining a meaning represented by the LCID field according to a value of the first field and a value of the LCID field, wherein when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0023] In combination with the second aspect, in certain implementations of the second aspect, the MAC sub-PDU includes a first field, including: the header of the MAC sub-PDU includes the first field; or the RRC message includes the first field.

[0024] In combination with the second aspect, in certain implementations of the second aspect, the LCID table is a correspondence between the index value of the LCID domain and the meaning represented by the index value of the LCID domain.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, before receiving the MAC sub-PDU, the method further includes: sending indication information, wherein the indication information is used to indicate support for parsing the MAC sub-PDU. The description of the indication information can refer to the description in the first aspect, which will not be repeated here.

[0026] In combination with the second aspect, in certain implementations of the second aspect, the indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the receiving the MAC sub-PDU includes: receiving the MAC sub-PDU during a random access process.

[0028] In combination with the second aspect, in certain implementations of the second aspect, if the first field is carried in the header of the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the size of the LCID field is 6 bits, and the size of the first field is 1 or 2 bits.

[0029] In combination with the second aspect, in certain implementations of the second aspect, if the first field is carried in the RRC message in the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, and the header of the MAC sub-PDU also includes two reserved fields, the size of the LCID field is 6 bits, and the size of each of the reserved fields is 1 bit.

[0030] The technical effects of the method shown in the above second aspect and its possible design can refer to the technical effects in the first aspect and its possible design.

[0031] On the third aspect, a communication method is provided, which can be executed by a sending end, wherein the sending end can be a terminal device, a network device, or a chip of a terminal device, a chip of a network device, etc., without limitation.

[0032] The communication method includes: determining a media access control MAC sub-packet data unit PDU, the MAC sub-PDU including an RRC message, the RRC message including an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU including a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; sending the MAC sub-PDU.

[0033] Based on the above scheme, the size of the LCID field included in the header of the MAC sub-PDU determined by the sending end is greater than 6 bits. Compared with the LCID field when the size of the LCID field is 6 bits, the value range of the LCID field in this scheme is larger and the meanings that can be represented are also more. Therefore, more indication information can be indicated through the LCID field. Furthermore, expanding the information that the LCID field can indicate can enrich the service types of terminal devices and improve user experience.

[0034] In combination with the third aspect, in certain implementations of the third aspect, at least one bit among the N bits occupied by the LCID field is a bit occupied by the reserved field in the header of a traditional MAC sub-PDU, and the header of the traditional MAC sub-PDU has a reserved field of two bits and an LCID field of 6 bits.

[0035] In combination with the third aspect, in certain implementations of the third aspect, before sending the MAC sub-PDU, the method further includes: determining that the receiving end supports parsing the MAC sub-PDU.

[0036] Based on the above scheme, before sending a MAC sub-PDU to a receiving end, the sending end can determine that the receiving end supports parsing the MAC sub-PDU, thereby avoiding the MAC sub-PDU sent to the receiving end not being correctly parsed by the receiving end, resulting in errors.

[0037] In combination with the third aspect, in certain implementations of the third aspect, determining that the receiving end supports parsing the MAC sub-PDU includes: receiving indication information, wherein the indication information is used to indicate that the receiving end supports parsing the MAC sub-PDU; or, determining that the receiving end supports parsing the MAC sub-PDU based on whether the receiving end supports the characteristics indicated by the MAC sub-PDU.

[0038] Based on the above scheme, the sending end can determine whether the receiving end can parse the MAC sub-PDU by: through the indication information sent by the receiving end, or the receiving end can determine whether the receiving end supports parsing the corresponding MAC sub-PDU based on the characteristics supported by the receiving end without displaying the indication information sent to indicate whether the MAC sub-PDU is supported. In this scheme, the sending end can determine whether the receiving end supports parsing the MAC sub-PDU to be sent in different ways, thereby improving the flexibility of the scheme.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

[0040] Based on the above solution, the receiving end may send the indication information to the sending end in the form of broadcast, multicast or unicast, which is not limited in this solution.

[0041] In combination with the third aspect, in certain implementations of the third aspect, sending the MAC sub-PDU includes: sending the MAC sub-PDU during a random access process.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the header of the MAC sub-PDU further includes less than two reserved fields.

[0043] In a fourth aspect, a communication method is provided, which can be executed by a receiving end, wherein the sending end can be a terminal device, a network device, or a chip of a terminal device, a chip of a network device, etc., without limitation. For example, the sending end in the third aspect is a terminal device or a chip of a terminal device, and the receiving end can be a network device or a chip of a network device.

[0044] The communication method includes: receiving a media access control MAC sub-packet data unit PDU, the MAC sub-PDU including an RRC message, the RRC message including an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU including a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; determining the meaning represented by the LCID field according to the value of the LCID field.

[0045] In combination with the fourth aspect, in certain implementations of the fourth aspect, before receiving the MAC sub-PDU, the method further includes: sending indication information, wherein the indication information is used to indicate support for parsing the MAC sub-PDU.

[0046] In combination with the fourth aspect, in certain implementations of the fourth aspect, the indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

[0047] In combination with the fourth aspect, in certain implementations of the fourth aspect, the header of the MAC sub-PDU also includes less than two reserved fields.

[0048] The technical effects of the method shown in the fourth aspect and its possible design above can refer to the technical effects in the third aspect and its possible design.

[0049] In a fifth aspect, a communication device is provided, which is used to execute the method provided in the first aspect or the third aspect. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method provided in any one of the above implementations of the first aspect or the third aspect.

[0050] Exemplarily, when the communication device is the transmitting end in the above-mentioned first aspect, the processing unit is used to determine the media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes a wireless resource control RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; the communication unit is used to send the MAC sub-PDU; wherein, when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0051] Exemplarily, when the communication device is the transmitting end in the third aspect above, the processing unit is used to determine the media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; the communication unit is used to send the MAC sub-PDU.

[0052] In one implementation, the apparatus is a terminal device. When the apparatus is a terminal device, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0053] Exemplarily, when the communication device is the transmitting end in the above-mentioned first aspect, the processor is used to determine a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes a radio resource control RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; a transceiver is used to send the MAC sub-PDU; wherein, when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0054] Exemplarily, when the communication device is the transmitting end in the third aspect above, the processor is used to determine the media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; the transceiver is used to send the MAC sub-PDU.

[0055] In another implementation, the device is a chip, a chip system or a circuit used in a terminal device. When the device is a chip, a chip system or a circuit used in a terminal device, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit.

[0056] In a sixth aspect, a communication device is provided, which is used to execute the method provided in the second aspect or the fourth aspect. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method provided in any one of the above implementations of the second aspect or the fourth aspect.

[0057] Exemplarily, when the communication device is the receiving end in the above-mentioned second aspect, the communication unit is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; the processing unit is used to determine the meaning represented by the LCID field according to the value of the first field and the value of the LCID field, wherein when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0058] Exemplarily, when the communication device is the receiving end in the fourth aspect above, the communication unit is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; the processing unit is used to determine the meaning represented by the LCID field according to the value of the LCID field.

[0059] In one implementation, the device is a network device. When the device is a network device, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0060] Exemplarily, when the communication device is the receiving end in the above-mentioned second aspect, the transceiver is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; the processor is used to determine the meaning represented by the LCID field according to the value of the first field and the value of the LCID field, wherein when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0061] Exemplarily, when the communication device is the receiving end in the fourth aspect above, the transceiver is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6; the processor is used to determine the meaning represented by the LCID field according to the value of the LCID field.

[0062] In another implementation, the device is a chip, a chip system or a circuit used in a network device. When the device is a chip, a chip system or a circuit used in a network device, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit.

[0063] In the seventh aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute any one of the above-mentioned implementations of the first to fourth aspects, or a method provided by any one of the above-mentioned implementations of the second to fourth aspects.

[0064] In an eighth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0065] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0066] In a ninth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any one of the above-mentioned implementations of the first to fourth aspects.

[0067] In a tenth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer executes the method provided in any one of the above-mentioned implementations of the first to fourth aspects.

[0068] In the eleventh aspect, a chip is provided, the chip including a processor and a communication interface, the processor reads instructions stored in a memory through the communication interface, and executes the method provided by any one of the above-mentioned implementation methods of the first to fourth aspects.

[0069] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the above implementation methods.

[0070] In a twelfth aspect, a communication system is provided, comprising the transmitting end of the first aspect and the receiving end of the second aspect above.

[0071] In a thirteenth aspect, a communication system is provided, comprising the transmitting end of the third aspect and the receiving end of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 It is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0073] Figure 2 It is a schematic diagram of the format of MAC PDU.

[0074] Figure 3 (a) to (c) in FIG. 1 are schematic diagrams of the format of the MAC subheader.

[0075] Figure 4 It is a schematic flow chart of a communication method provided by the present application.

[0076] Figure 5It is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.

[0077] Figure 6 It is a schematic diagram of another communication device 20 provided in an embodiment of the present application.

[0078] Figure 7 It is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0079] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0080] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions of the embodiments of the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of things (IoT) communication system or other communication systems.

[0081] To facilitate understanding of the embodiments of the present application, first Figure 1 The communication system shown in the figure is used as an example to describe in detail the communication system applicable to the embodiments of the present application. Figure 1 1 is a schematic diagram of a communication system 100 to which the present application embodiment is applicable. Figure 1 As shown, the communication system 100 may include at least one network device, such as Figure 1 The network device 110 shown; the communication system 100 may also include at least one terminal device, such as Figure 1The terminal device 120 shown. The network device 110 and the terminal device 120 can communicate via a wireless link. Each communication device, such as the network device 110 and the terminal device 120, can be configured with multiple antennas. For each communication device in the communication system 100, the configured multiple antennas may include at least one transmitting antenna for sending signals and at least one receiving antenna for receiving signals. Therefore, the communication devices in the communication system 100, such as the network device 110 and the terminal device 120, can communicate via a multi-antenna technology.

[0082] By way of example and not limitation, Figure 1 The network devices and terminal devices in the scenario shown can communicate with each other in a variety of ways, such as communication between the network devices and the terminal devices through point-to-point transmission, communication between the network devices and the terminal devices through multi-hop (or relay) transmission, communication between multiple network devices and terminal devices through dual connectivity (dual connectivity, DC) or multi-connection transmission, etc.

[0083] In the embodiments of the present application, there is no limitation on the communication mode between the network device and the terminal device. For example, the transmission between the network device and the terminal device can be uplink, downlink, access link, backhaul link or sidelink.

[0084] The terminal equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, a user equipment (UE), a terminal, a wireless communication device, a user agent or a user device. The terminal equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved public land mobile communication network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0085] As an example and not a limitation, in the embodiments of the present application, wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0086] In addition, in the embodiment of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. In the embodiment of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.

[0087] The network device in the embodiment of the present application can be any device with wireless transceiver function for communicating with the terminal device. The device includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be a gNB in ​​5G, such as NR, system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or, it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0088] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (core network, CN), which is not limited in the present application.

[0089] In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call a program and execute a program.

[0090] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0091] It should be understood that Figure 1 Taking the communication between a network device and a terminal device as an example, a communication scenario to which the present application can be applied is briefly explained, without limiting other scenarios to which the present application can be applied.

[0092] It should also be understood that Figure 1 This is a simplified schematic diagram for ease of understanding only. The communication system may also include other network devices or other terminal devices. Figure 1 Not drawn in.

[0093] For example, the communication system may also include core network equipment for managing terminal equipment and network equipment configuration, such as access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, etc.

[0094] In order to facilitate understanding of the technical solutions of the embodiments of the present application, before introducing the solutions of the embodiments of the present application based on the 5G architecture, some terms or concepts in 5G that may be involved in the embodiments of the present application are first briefly described.

[0095] 1. MAC packet data unit (PDU) format: contains at least one MAC subPDU (MACsubPDU), which contains a MAC subheader (MAC subheader). In addition, the MAC subPDU also contains a MAC SDU, a MAC control element (CE) or padding.

[0096] For ease of understanding, combined Figure 2 Briefly explain the format of MAC PDU. Figure 2 It can be seen that a MAC PDU includes at least one MAC subPDU (e.g., Figure 2 MAC subPDU#1, MAC subPDU#2, MAC subPDU#3, MACsubPDU#4 and MAC subPDU#5) shown in the figure, wherein each MAC subPDU includes a MAC subheader.

[0097] Exemplarily, the MAC subPDU may also include a MAC SDU, such as Figure 2 MAC subPDU#1 and MACsubPDU#2 shown in , optionally, the MAC subPDU including the MAC SDU can be referred to as MAC subPDU including MAC SDU.

[0098] Exemplarily, the MAC subPDU may also include a MAC CE, such as Figure 2MAC subPDU#3 and MACsubPDU#4 shown in FIG. 1 , optionally, the MAC subPDU including the MAC CE may be referred to as a MAC subPDU including MAC CE. The size of the MAC CE included in different MAC subPDUs may be different, for example, the MAC CE included in the MAC subPDU#3 is a fixed-sized MAC CE, and the MAC CE included in the MAC subPDU#4 is a variable-sized MAC CE.

[0099] Exemplarily, the MAC subPDU may also include padding, such as Figure 2 In the MAC subPDU#5 shown in FIG, optionally, the MAC subPDU including padding may be referred to as a MAC subPDU including padding.

[0100] 2. MAC subheader: The MAC subheader contains at least one of the following fields: R field (reserved field, reserved for future use, set to 0), LCID field (logical channel identification field, used to identify the logical channel instance of the corresponding MAC SDU or the type of MAC CE or to identify padding or to identify whether the eLCID field exists), eLCID field (extended logical channel identification field, used to identify the logical channel instance of the corresponding MAC SDU or the type of MAC CE), L field (length field, used to identify the length of the corresponding MAC SDU or the length of a MAC CE of variable size), F field (format field, used to identify the size of the length field), such as Figure 3 As shown in (a) in .

[0101] The MAC subheader has multiple formats. As one example, when the MAC SDU contained in the MAC subPDU carries a UL CCCH message, a UL CCCH1 message, or an uplink dedicated control channel (Dedicated Control Channel, DCCH) message, the corresponding MAC subheader contains an R field and an LCID field.

[0102] For ease of understanding, combined Figure 3 (b) and (c) in the figure briefly illustrate two possible MAC subheader formats.

[0103] like Figure 3The MAC subheader shown in (b) includes an R field and an LCID field, where the R field and the LCID field occupy a total of 1 byte (such as Figure 3 As shown in (b) in Oct1), the 8-bit R field occupies 2 bits and the LCID field occupies 6 bits.

[0104] like Figure 3 The MAC subheader shown in (c) includes an R field, an LCID field, and an eLCID field, wherein the R field and the LCID field occupy a total of 1 byte (e.g. Figure 3 In Oct1, the R field occupies 2 bits, the LCID field occupies 6 bits, and the eLCID field occupies 1 byte (as shown in (c) in FIG. Figure 3 Oct2 shown in (c)).

[0105] It should be noted that Figure 3 The MAC subheader format shown in (b) does not contain the eLCID field. The advantage of using this format of MAC subheader is that it does not require an additional increase in the size of the MAC PDU. In scenarios where uplink coverage is limited, the uplink resources allocated by the access network device each time are usually relatively small, because the smaller the data packet (including the MAC PDU) is, the easier it is to send successfully. Therefore, unless coverage is not a concern, it will be used first. Figure 3 Therefore, the following mainly uses the MAC subheader format as Figure 3 The MAC subheader format shown in (b) is used as an example to illustrate. When the MAC subheader format is Figure 3 For the MAC subheader format shown in (c) in the figure, the setting of the LCID field in the MAC subheader can refer to Figure 3 The setting of the LCID field in the MAC subheader shown in the MAC subheader format shown in (b) will not be repeated.

[0106] 3. Indicator space of LCID domain: As shown above, the size of LCID domain is 6 bits, and the LCID value of LCID domain has 2 6 =64, different LCID values ​​represent different situations, and can indicate up to 64 different situations. At this time, it can be considered that the indication space size of the LCID field is 64. The indication space of the LCID field can be understood as: the number of indication information indicated by the LCID field.

[0107] As shown in Table 1 below, different LCID values ​​represent different situations. Currently, 57 LCID values ​​are in use, and 7 LCID values ​​are reserved and can be used as new indications (for example, 37-42 in bold in Table 1 below can be used as new indications).

[0108] Table 1

[0109]

[0110]

[0111] The first column index or code point in Table 1 can be determined by the value of the LCID field. For example, if the value of the LCID field is 000000, the index or code point is 0. The second column LCID value in Table 1 is understood as the meaning represented by the LCID field or the meaning indicated by the LCID value. For example, if the value of the LCID field is 000000, the index or code point is 0, then the meaning represented by the LCID field is that the MAC PDU contains a 64-bit CCCH message (i.e., CCCH1 message). Among them, the meaning represented by the LCID field includes: identifying the logical channel instance (logical channel number) corresponding to the MAC SDU, identifying the type of MAC CE, or identifying padding, etc.; the size of the index value can be equal to the numerical size of the LCID field.

[0112] The above table 1 is Figure 3 The meanings (LCID values) corresponding to different values ​​(index values) of the LCID field in the MAC subheader format shown in (b) can be summarized as an LCID table. The LCID table mentioned below can also be replaced by the corresponding relationship, mapping relationship, or association relationship between the value of the LCID field and the meaning represented by the LCID field.

[0113] Exemplarily, when the MAC subheader includes an eLCID field, the LCID table involved in the present application may also be a correspondence between the code point, index, and meaning (LCID value) represented by the LCID field, as shown in Table 2 below:

[0114] Table 2:

[0115]

[0116]

[0117] In this application, code points and index values ​​can be replaced with each other, or code points and index values ​​can be used to determine each other, and the two have a corresponding relationship. The size of the index value can be equal to the value of the eLCID domain, and the value of the code point is accumulated from 0, and corresponds to the value of the eLCID. For example, code point 0 corresponds to index 64, code point 1 corresponds to index 65, and so on.

[0118] In addition, it should be noted that the LCID values ​​shown in the above Tables 1 and 2 can refer to the description in the existing protocol (such as Tables 6.2.1-2 and 6.2.2-2a in TS38321), which will not be repeated here.

[0119] In addition, in order to facilitate understanding of the embodiments of the present application, the following points are explained.

[0120] First, in this application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that A must be included in the indication information.

[0121] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and / or sending time of these sub-information can be pre-defined, for example, pre-defined according to the protocol, or can be configured by the transmitting end device by sending configuration information to the receiving end.

[0122] Second, "at least one" shown in the present application refers to one or more, and "multiple" refers to two or more. In addition, in the embodiments of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process below does not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged in appropriate circumstances, so that the schemes outside the embodiments of the present application can be described. In addition, in the embodiments of the present application, the words "410", "420" and the like are only for the convenience of description, and the order of execution steps is not limited.

[0123] Third, in this application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific way.

[0124] Fourth, the “protocol” involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, which is not limited in the present application.

[0125] Fifth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0126] Sixth, in the embodiments of the present application, various terms and English abbreviations, such as radio resource control (RRC), etc., are illustrative examples given for the convenience of description and should not constitute any limitation to the present application. The present application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future protocols.

[0127] Seventh, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0128] Combination of the above Figure 1 The present invention briefly introduces the scenarios in which the communication method provided in the embodiments of the present application can be applied, as well as the basic concepts that may be involved in the embodiments of the present application. The LCID domain and the indication space of the LCID domain are introduced in the basic concepts. As mentioned above, the current size of the indication space of the LCID domain is 64, and 57 LCID values ​​are currently in use. There are 7 reserved LCID values ​​that can be used for new indications. The problem is that with the evolution of the standard, more and more features are introduced in the standard, and many of these features require the use of new LCID values ​​to indicate new meanings to the receiving end. The reserved 7 values ​​are far from meeting the demand.

[0129] The present application provides a communication method which can be applied in Figure 1 In the communication system shown, by setting the first field in the MAC sub-PDU, more situations that can be indicated by LCID values ​​are created without increasing the header size of the MAC sub-PDU, that is, the indication space of the LCID is increased.

[0130] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application may be a sending end and a receiving end, or a functional module in the sending end and the receiving end that can call and execute the program.

[0131] Figure 4 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:

[0132] S410, the transmitting end determines a MAC sub-PDU.

[0133] Exemplarily, the transmitting end determines a MAC PDU, which includes at least one MAC sub-PDU. For example, the format of the MAC PDU is as described above. Figure 2 The format shown is not described in detail here. The MAC sub-PDU shown in step S410 may be any one of the at least one MAC sub-PDU.

[0134] Specifically, the MAC sub-PDU may include an RRC message, which may include one or more of an uplink common control channel ULCCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message. For example, the MAC SDU included in the MAC sub-PDU carries a UL CCCH message or a UL CCCH1 message or a UL DCCH message.

[0135] Furthermore, in this embodiment, the header of the MAC sub-PDU includes a logical channel identifier LCID field. For example, the LCID field can be Figure 3 Alternatively, the LCID domain may be the LCID domain shown in (a) above. Figure 3 Alternatively, the LCID domain may be the LCID domain shown in (b) above. Figure 3 Alternatively, the LCID domain may be the eLCID domain shown in (b) above. Figure 3 The LCID domain and eLCID domain shown in (b).

[0136] It should be understood that the above is only an example of the possible forms of the LCID field involved in this embodiment, and does not constitute any limitation on the scope of protection of the present application. The LCID field involved in this embodiment may also be the LCID field included in the header of the MAC sub-PDU defined in the future protocol, and examples will not be given one by one here.

[0137] For ease of description, the LCID domain is used below. Figure 3 The LCID domain shown in (a) is used as an example for explanation.

[0138] As shown above, Figure 3 The indication space size of the LCID domain shown in (a) is 64. In this embodiment, the indication space of the LCID domain can be expanded in the following two ways so that the indication space of the LCID domain is larger than 64. It should be noted that the LCID domain is Figure 3 The LCID domain shown in (a) is only an example and does not constitute any limitation on the scope of protection of this application. Figure 3 For the eLCID domain shown in (a), the following method of expanding the indication space can also expand the indication space of the eLCID domain.

[0139] Method 1: By carrying the first field in the MAC sub-PDU, the indication space of the LCID field is expanded.

[0140] In the case shown in mode 1, the MAC sub-PDU includes a first field. Wherein, when the value of the first field is different, the meaning represented by the LCID field is determined according to different LCID tables, and the LCID table can represent the corresponding relationship between the index value or code point of the LCID field and the meaning represented by the index value or code point of the LCID field, and the index value or code point of the LCID field is determined based on the value of the LCID field.

[0141] As can be seen from the above, when the value of the first domain is different, the meaning represented by the LCID domain is determined according to different LCID tables, which can be understood as: the meaning represented by the LCID domain is determined according to the value of the first domain and the value of the LCID domain, or, the meaning represented by the LCID domain is related to the LCID domain and the first domain, or, the meaning represented by the LCID domain is determined based on the LCID domain and the first domain. Among them, the LCID table can be understood as a correspondence between an LCID index, a code point, and its meaning. When the first domain is the first value, the LCID index, the code point, and its meaning are the first correspondence, and when the first domain is the second value, the LCID index, the code point, and its meaning are the second correspondence.

[0142] It should be noted that, in this embodiment, only the MAC sub-PDU determined by the transmitting end is limited to include the first field, but no limitation is made on the manner in which the first field is carried in the MAC sub-PDU, including but not limited to the following two possible implementations:

[0143] As a possible implementation, the header of the MAC sub-PDU includes a first field. For example, the first field may be Figure 3 At least one R field is included in the header of the MAC sub-PDU shown in (a).

[0144] In this implementation, at least one R field in the header of the MAC sub-PDU can be used in combination with the LCID field to determine multiple LCID field indication spaces of size 64.

[0145] It should be noted that when one of the two R domains in the header of the MAC sub-PDU is used, the used R domain is the first domain mentioned above. If it is necessary to further expand the LCID domain indication space, the other R domain of the two R domains in the header of the MAC sub-PDU can be reused. The other R domain used is the first domain or other names (such as the third domain, etc.).

[0146] In this implementation, if the LCID field is Figure 3 The LCID field is included in the header of the MAC sub-PDU shown in (a), the size of the header of the MAC sub-PDU is one byte, the size of the LCID field is 6 bits, and the size of the first field is 1 or 2 bits.

[0147] As another possible implementation manner, the MAC sub-PDU includes an RRC message, and the RRC message includes the first field.

[0148] In this implementation, at least one bit in the RRC message (eg, a reserved bit in the RRC message) can be combined with the LCID field to create multiple LCID field indication spaces of size 64.

[0149] In this implementation, if the LCID field is Figure 3 The LCID field is included in the header of the MAC sub-PDU shown in (a). The size of the MAC sub-PDU header is one byte, the size of the LCID field is 6 bits, and the header of the MAC sub-PDU also includes two reserved fields. The size of the LCID field is 6 bits, and the size of each reserved field is 1 bit.

[0150] It should be understood that the above two implementations are only examples of the possible ways in which the first domain may be carried, and do not constitute any limitation on the scope of protection of this application. In this embodiment, the first domain may also be carried in other positions of the MAC sub-PDU, which will not be described one by one here. Or the first domain may also be sent to the receiving end through other messages. For example, before the sending end sends the MAC sub-PDU to the receiving end, the sending end has provided the first domain to the receiving end, which will not be described in detail here.

[0151] Compared to the indication space of the LCID domain introduced in the basic concept in the previous text, the indication space of the LCID domain in this embodiment is determined based on the LCID domain and the first domain, and is no longer determined based on the LCID domain alone, so that the indication space of the LCID domain can be expanded, and more indication information can be indicated through the LCID domain, enriching the service types of the terminal device and improving the user experience. For example, in this scheme, there can be multiple LCID tables representing the value of the LCID domain and the meaning represented by the LCID domain. When actually determining the meaning represented by the LCID domain, the LCID table used can be determined based on the value of the first domain, and then the meaning represented by the LCID domain can be determined based on the value of the LCID domain and the LCID table obtained by the determination. Compared with determining the meaning represented by the LCID domain based only on the value of the LCID domain (such as Table 1 in the previous text), the indication space of the LCID domain is expanded.

[0152] In this embodiment, the value of the first domain is different, and the LCID table based on which the meaning represented by the LCID domain is determined is different. For example, when the value of the first domain is a first value, the meaning represented by the LCID domain is determined according to the first LCID table; when the value of the first domain is a second value, the meaning represented by the LCID domain is determined according to the second LCID table.

[0153] To facilitate understanding, the corresponding relationship between the value of the first domain and the LCID table is explained below with reference to specific examples.

[0154] Example 1: The first field is 1 bit.

[0155] When the value of the first domain is 0, the meaning represented by the LCID domain is determined according to the first LCID table. For example, the meanings corresponding to different values ​​of the LCID domain are shown in Table 1 above; when the value of the first domain is 1, the meaning represented by the LCID domain is determined according to the second LCID table.

[0156] For example, when the value of the first domain is 1, the meanings corresponding to different values ​​of the LCID domain are shown in Table 3 below. Table 3 may be a new table defined in a protocol (such as a MAC protocol). In Table 3, the meaning corresponding to the value of each LCID domain may be the same as or different from the meaning shown in Table 1. As shown in Table 3 below:

[0157] Table 3

[0158] Index or Codepoint LCID values 0 XXXX 1 YYYY … … M ZZZ … … NP Reserved … … 63 UUU

[0159] The first column in Table 3 above is the index value or code point corresponding to the value of the LCID domain, which is the same as the index value or code point shown in Table 1 above. The second column is the meaning represented by the LCID domain corresponding to different index values ​​or code points when the value of the first domain is 1, which can be the same or different from the meaning shown in Table 1, as an example but not a limitation.

[0160] The meaning represented by the LCID field in Table 3 may include one or more of the following:

[0161] a) Indicates the type of reduced capability device (Redcap) or enhanced reduced capability device (eRedcap);

[0162] b) indicating a request for repeated transmission of HARQ-ACK for message 4 on PUCCH during the RACH process or a corresponding capability report (for example, in non-terrestrial networks);

[0163] c) Indicates the limited capabilities of multi-card UEs;

[0164] d) indicates the situation where at least one of the above-mentioned meanings is superimposed on each other, or indicates the situation where at least one of the above-mentioned meanings is superimposed on other meanings: for example, simultaneously indicating a) and b) or simultaneously indicating a), b) and c) or indicating a) and other meanings, etc.

[0165] It should be understood that the above is only an example to illustrate the possible meanings of different index values ​​in Table 3, and does not constitute any limitation on the scope of protection of the present application.

[0166] Example 2: The first field is 2 bits.

[0167] When the value of the first domain is 00, the meaning represented by the LCID domain is determined according to the first LCID table. For example, the meanings corresponding to different values ​​of the LCID domain are shown in Table 1 above; when the value of the first domain is 01, the meanings corresponding to different values ​​of the LCID domain can define a new table, such as Table a (similar to Table 2); and so on, when the value of the first domain is 10, the meanings corresponding to different values ​​of the LCID domain can define a new table, such as Table b; when the value of the first domain is 11, the meanings corresponding to different values ​​of the LCID domain can define a new table, such as Table c.

[0168] Example 3: The first field is N bits.

[0169] The value of the first domain includes 2 N possibilities, so the LCID table can have 2N , 2 N The LCID tables include the traditional LCID table (e.g., Table 1), as well as definition 2 N - 1 brand new table.

[0170] Exemplarily, when the values ​​of the LCID fields in different LCID tables are the same, the corresponding meanings in different tables may be the same or different.

[0171] The above-mentioned LCID table may also be referred to as a corresponding relationship, a mapping relationship, an association relationship, etc. In this embodiment, no limitation is imposed on the name of the information representing the association relationship between the value of the LCID domain and the meaning represented by the LCID domain.

[0172] Because the value of the first domain is different, the LCID table based on which the meaning represented by the LCID domain is determined is different. Exemplarily, the transmitting end may set the value of the first domain according to the characteristics of the receiving end or the current transmission scenario. For example, if the value of the first domain is as shown in Example 1 above, and the transmitting end knows that the receiving end is a Redcap device, the transmitting end may set the value of the first domain to 1; for another example, if the value of the first domain is as shown in Example 1 above, and the transmitting end determines that the current transmission scenario is: During the RACH process, for the repeated transmission request or corresponding capability report of the HARQ-ACK of message 4 on the PUCCH, the transmitting end may set the value of the first domain to 1.

[0173] It should be understood that the above is only an example to illustrate that the sender can set the value of the first field according to known information so that the receiver can determine the meaning represented by the LCID field in the LCID table indicated by the first field. It does not constitute any limitation on the protection scope of the present application. For example, the value of the first field is random or the value of the first field can be determined based on historical communication data, which will not be explained one by one here.

[0174] In addition, in the above description, it is assumed that when the first domain takes different values, different tables are defined accordingly. Another implementation method is to expand on the existing table. For example, when the first domain takes different values, the meaning represented by the LCID value is represented in different areas of the same table (each area can contain multiple rows of the table).

[0175] Method 2: By increasing the size of the LCID field, the indication space of the LCID field is expanded.

[0176] In the case shown in method 2, the size of the LCID field is N bits, where N is an integer greater than 6.

[0177] Optionally, in the case shown in method 2, at least one bit of the R bits occupied by the reserved field in the header of the MAC sub-PDU is used as part of the LCID field and combined with the original LCID to form a new LCID field containing more bits.

[0178] For example, assuming that 1 R field in the header of the MAC sub-PDU is used, it can be combined with the original LCID field to form a 7-bit LCID field; assuming that 2 R fields in the header of the MAC sub-PDU are used, it can be combined with the original LCID field to form an 8-bit LCID field.

[0179] In the case shown in the second method, the LCID field can indicate more meanings, which is equivalent to forming a larger indication space. For example, the LCID field can indicate an indication space of 128 or 256 in size.

[0180] Different from the situation shown in the above-mentioned method 1, in the situation shown in the method 2, the size of the original table 1 is expanded (more values ​​greater than 63 are added on the basis of the original 64 values ​​to identify more meanings), rather than defining one or more new tables.

[0181] In the case shown in method 2, if the header of the MAC sub-PDU is Figure 3 The header of the MAC sub-PDU shown in (a) above is one byte in size, the size of the LCID field is greater than 6 bits, and the header of the MAC sub-PDU also includes less than two reserved fields.

[0182] Furthermore, after the transmitting end determines the MAC sub-PDU, the MAC sub-PDU can be sent to the receiving end. Figure 4 The method flow shown also includes:

[0183] S420, the transmitting end sends a MAC sub-PDU to the receiving end.

[0184] In this embodiment, the transmitting end sends the MAC sub-PDU to the receiving end in the random access process (including the four-step random access process or the two-step random access process). For example, the transmitting end may send the MAC sub-PDU to the receiving end via message 3 or message A.

[0185] As a possible implementation manner, the sending end is a terminal device, and the receiving end is an access network device. The terminal device can send a MAC sub-PDU to the access network device through a transmission link between the terminal device and the access network device.

[0186] As another possible implementation, the sending end is an access network device, and the receiving end is a terminal device. The access network device can send a MAC sub-PDU to the terminal device via a transmission link between the terminal device and the access network device.

[0187] It should be understood that sending the MAC sub-PDU here does not limit the final sending form on the air interface. For example, the sending end can further process the MAC PDU where the MAC sub-PDU is located, convert it into a transmission block or other form that can be transmitted on the air interface, and send it on the air interface. Since the useful information sent is contained in the MAC sub-PDU, it is described here as sending the MAC sub-PDU.

[0188] It should be understood that the specific entities of the transmitter and the receiver are not limited in this embodiment, and any transceiver device that transmits a MAC sub-PDU can be used as the transmitter and the receiver in this embodiment.

[0189] Exemplarily, when a transmitting end sends a MAC sub-PDU to a receiving end, a receiving end that supports parsing the MAC sub-PDU constructed according to the above-mentioned method one and method two can correctly parse the received MAC sub-PDU; a receiving end that does not support parsing the MAC sub-PDU constructed according to the above-mentioned method one and method two may parse the MAC sub-PDU according to the format of the MAC sub-PDU defined in the existing protocol after receiving the above-mentioned MAC sub-PDU, resulting in a parsing failure. For example, some receiving ends believe that the reserved field in the header of the MAC sub-PDU must be 0, so if the transmitting end sends a MAC sub-PDU with an R field of 1 to such a receiving end, it is very likely that the receiving end cannot correctly parse the MAC sub-PDU or directly ignores the R field, resulting in inconsistent understanding between the transmitting end and the receiving end.

[0190] Specifically, in this embodiment, in order to prevent the sending end from sending the MAC sub-PDU to the receiving end that cannot correctly parse the MAC sub-PDU, it can be determined before sending the MAC sub-PDU that the receiving end can correctly parse the MAC sub-PDU.

[0191] As a possible implementation method, the receiving end shown in this embodiment supports parsing the MAC sub-PDU, which can be understood as: the receiving end can recognize or correctly understand the format of the MAC sub-PDU, supports the format of the MAC sub-PDU, supports the MAC sub-PDU, or can parse the format of the MAC sub-PDU, etc.

[0192] When the first field is at least one R field in the header of the MAC sub-PDU, the format of the MAC sub-PDU may be a MAC sub-PDU including at least one R field whose value may not be 0 in the header of the MAC sub-PDU; or,

[0193] When the above-mentioned first field is a field in the RRC message in the MAC sub-PDU, the format of the MAC sub-PDU may be a MAC sub-PDU including an RRC message whose corresponding field may not be 0.

[0194] As another possible implementation method, the receiving end shown in this embodiment supports parsing the MAC sub-PDU, which can be understood as: the receiving end can recognize or correctly understand the format of the header of the MAC sub-PDU, supports the format of the header of the MAC sub-PDU, supports the header of the MAC sub-PDU, or can parse the format of the header of the MAC sub-PDU, etc.

[0195] When the above-mentioned first field is at least one R field in the header of the MAC sub-PDU, the format of the header of the MAC sub-PDU may be a header of the MAC sub-PDU including at least one R field whose value may not be 0.

[0196] Exemplarily, in this embodiment, the sender may determine that the sender can parse the MAC sub-PDU through the following two possible implementations:

[0197] As a possible implementation, the receiving end sends specific indication information to the sending end, and the indication information indicates whether the receiving end supports parsing the above-mentioned MAC sub-PDU. For example, if the indication information value is a specific value (such as true), it means support; if the value is false, it means unsupport; in addition, the absence of the indication information also means unsupport. Alternatively, if the indication information is sent, it means support; otherwise, it means unsupport.

[0198] Exemplarily, the MAC sub-PDU is the MAC sub-PDU shown in the above-mentioned method 1. The indication information indicates whether the receiving end supports parsing the MAC sub-PDU whose meaning is jointly determined based on the first field and the LCID field.

[0199] For example, the MAC sub-PDU is the MAC sub-PDU including the first field as shown in the above method 1, and the first field is carried in the header of the MAC sub-PDU. The indication information is used to indicate whether the receiving end supports parsing the MAC sub-PDU in which at least one value in the header of the MAC sub-PDU may not be a reserved field of 0.

[0200] For example, the MAC sub-PDU is the MAC sub-PDU including the first field as shown in the above method 1, and the first field is carried in the RRC message in the MAC sub-PDU. The indication information is used to indicate whether the receiving end supports parsing the MAC sub-PDU determined based on the RRC message and the LCID field.

[0201] Exemplarily, the MAC sub-PDU is the MAC sub-PDU shown in the above-mentioned mode 2. The indication information indicates whether the receiving end supports parsing the MAC sub-PDU whose LCID field size is greater than 6 bits.

[0202] Exemplarily, the indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

[0203] For example, the receiving end is an access network device, the sending end is a terminal device, and the dedicated signaling may be an RRC signaling; the broadcast signaling may be targeted at a terminal device in a cell or a terminal device in an area (e.g., the broadcast signaling is a management information block (MIB), a system information block 1 (SIB1) or other SIBs); and the multicast signaling may be targeted at a specific group of terminal devices.

[0204] In this implementation, after receiving the indication information, the sending end can determine whether the receiving end supports parsing the above-mentioned MAC sub-PDU based on the indication information, and send the MAC sub-PDU to the receiving end if supported.

[0205] As another possible implementation manner, the transmitting end determines whether the receiving end supports parsing the MAC sub-PDU according to whether the receiving end supports the characteristics indicated by the above MAC sub-PDU.

[0206] In this implementation, the receiving end may not send additional explicit indication information to indicate whether it supports parsing the above MAC sub-PDU. Instead, the sending end infers whether the receiving end can support parsing the above MAC sub-PDU by reading the existing receiving end information.

[0207] For example, the receiving end information indicates that the receiving end supports the redcap feature, and the redcap type indication needs to be indicated through a new format MAC sub-PDU (i.e., the MAC sub-PDU determined according to method one or method two mentioned above). The sending end knows that the receiving end supports the redcap feature, and can infer that the receiving end supports the interpretation of the new format MAC sub-PDU.

[0208] In addition, it should be noted that the above-mentioned sending end determining whether the receiving end supports parsing the MAC sub-PDU is an optional step. For example, the sending end can send the MAC sub-PDU to the receiving end after receiving the indication information, without determining that the receiving end supports parsing the MAC sub-PDU.

[0209] Furthermore, after receiving the MAC sub-PDU, the receiving end can determine the meaning represented by the LCID field, then Figure 4 The method flow shown also includes:

[0210] S430: The receiving end determines the meaning represented by the LCID field.

[0211] As a possible implementation method, the MAC sub-PDU received by the receiving end is the MAC sub-PDU determined according to the above-mentioned method 1, and the receiving end can determine the meaning represented by the LCID field based on the value of the first field and the value of the LCID field.

[0212] For example, the receiving end determines the LCID table according to the value of the first field, and then determines the meaning represented by the LCID field according to the value of the LCID field and the LCID table.

[0213] When the LCID table is a correspondence between the index value of the LCID domain and the meaning represented by the index value, the index value of the LCID domain can be determined according to the value of the LCID domain. Thus, after the LCID table is determined according to the value of the first domain, the meaning represented by the index value can be determined according to the index value of the LCID domain and the LCID table.

[0214] When the LCID table is a correspondence between the code point of the LCID domain and the meaning represented by the code point, the code point of the LCID domain can be determined according to the value of the LCID domain. Therefore, after the LCID table is determined according to the value of the first domain, the meaning represented by the code point can be determined according to the code point of the LCID domain and the LCID table.

[0215] As another possible implementation method, the MAC sub-PDU received by the receiving end is the MAC sub-PDU determined according to the above-mentioned method 2, and the receiving end can determine the meaning represented by the LCID field according to the value of the LCID field.

[0216] Figure 4 In the communication method shown, the MAC sub-PDU determined by the sending end includes, in addition to the LCID field, a first field that affects the meaning represented by the LCID field, or the size of the LCID field is greater than 6 bits to expand the indication space of the LCID field, so that more indication information can be indicated through the LCID field, thereby enriching the service types of the terminal device and improving the user experience.

[0217] It should be understood that the order of execution of the above-mentioned processes does not necessarily mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. Figure 4 Step S410 in the communication method shown is optional, that is, the sending end can send the MAC sub-PDU obtained by the above-mentioned method one or method two to the receiving end, but the determination step before the sending end is not mandatory, such as, the sending end locally saves the MAC sub-PDU to be sent before sending the MAC sub-PDU, or the sending end generates the MAC sub-PDU before sending the MAC sub-PDU.

[0218] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0219] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for exemplary description (such as a transmitting end and a receiving end, etc.), and it should be understood that the specific form of the device is not limited in the embodiments of the present application. For example, devices that can achieve the same function in the future are applicable to the embodiments of the present application.

[0220] It can be understood that in the above-mentioned various method embodiments, the methods and operations implemented by devices (such as a transmitter and a receiver, etc.) can also be implemented by components of the device (such as a chip or a circuit).

[0221] Above, combined Figure 4 The communication method provided by the embodiment of the present application is described in detail. The above communication method is mainly introduced from the perspective of interaction between the sending end and the receiving end. It can be understood that in order to realize the above functions, the sending end and the receiving end include hardware structures and / or software modules corresponding to the execution of each function.

[0222] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0223] The following combination Figures 5 to 7 The communication device provided by the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, the content not described in detail can be referred to the method embodiment above, and some content will not be repeated for the sake of brevity.

[0224] The embodiment of the present application can divide the functional modules of the transmitting end or the receiving end according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0225] Figure 5 1 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to perform data processing, or in other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations besides receiving and sending. The transceiver module 11 can also be called a communication interface or a communication unit.

[0226] Optionally, the device 10 may further include a storage module 13, which may be used to store instructions and / or data. The processing module 12 may read the instructions and / or data in the storage module so that the device implements the actions of the devices in the aforementioned method embodiments.

[0227] In one design, the device 10 may correspond to the transmitting end in the above method embodiment, or a component (such as a chip) of the transmitting end.

[0228] The device 10 can implement the steps or processes executed by the sending end in the above method embodiment, wherein the transceiver module 11 can be used to execute the sending and receiving related operations of the sending end in the above method embodiment, and the processing module 12 can be used to execute the processing related operations of the sending end in the above method embodiment.

[0229] In a possible implementation, the processing module 12 is used to determine a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a ULCCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field. The transceiver module 11 is used to send the MAC sub-PDU; wherein, when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0230] In another possible implementation, the processing module 12 is used to determine a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a ULCCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6. The transceiver module 11 is used to send the MAC sub-PDU.

[0231] Wherein, when the device 10 is used to perform Figure 4 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S420; the processing module 12 can be used to execute the processing steps in the method, such as step S410.

[0232] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0233] In another design, the device 10 may correspond to the receiving end in the above method embodiment, or a component (such as a chip) of the receiving end.

[0234] The device 10 can implement the steps or processes executed by the receiving end in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the receiving end in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the receiving end in the above method embodiment.

[0235] In a possible implementation, the transceiver module 11 is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a ULCCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field. The processing module 12 is used to determine the meaning represented by the LCID field according to the value of the first field and the value of the LCID field, wherein when the first field takes different values, the meaning represented by the LCID field is determined according to different LCID tables.

[0236] In another possible implementation, the transceiver module 11 is used to receive a media access control MAC sub-packet data unit PDU, the MAC sub-PDU includes an RRC message, the RRC message includes an uplink common control channel UL CCCH message or a ULCCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, the header size of the MAC sub-PDU is one byte, the size of the LCID field is N bits, and N is an integer greater than 6. The processing module 12 is used to determine the meaning represented by the LCID field according to the value of the LCID field.

[0237] Wherein, when the device 10 is used to perform Figure 4 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S420; the processing module 12 can be used to execute the processing steps in the method, such as step S430.

[0238] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0239] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 10 can be specifically the transmitting end or the receiving end in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the transmitting end or the receiving end in the above-mentioned method embodiments.

[0240] The device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the device (such as the transmitting end or the receiving end, etc.) in the above method. This function can be implemented by hardware, or by hardware executing the corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor, respectively performing the transceiver operations and related processing operations in each method embodiment.

[0241] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.

[0242] Figure 6 2 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is used to execute a computer program or instruction stored in a memory 22, or read data / signaling stored in the memory 22 to execute the method in each method embodiment above. Optionally, there are one or more processors 21.

[0243] Alternatively, if Figure 6 As shown, the device 20 also includes a memory 22, which is used to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21, or can also be separately set. Optionally, the memory 22 is one or more.

[0244] Alternatively, if Figure 6As shown, the device 20 further includes a transceiver 23, and the transceiver 23 is used for receiving and / or sending signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0245] As a solution, the device 20 is used to implement the operations performed by the sending end in the above various method embodiments.

[0246] As another solution, the device 20 is used to implement the operations performed by the receiving end in the above various method embodiments.

[0247] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0248] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0249] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0250] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0251] Figure 7 Schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0252] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 30 can implement the methods and functions of each embodiment of the present application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting information processed by the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.

[0253] As a solution, the chip system 30 is used to implement the operations performed by the transmitting end or the receiving end in each of the above method embodiments.

[0254] For example, the logic circuit 31 is used to implement the processing-related operations performed by the transmitter or receiver in the above method embodiments; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the transmitter or receiver in the above method embodiments.

[0255] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by a sending end or a receiving end in the above-mentioned method embodiments are stored.

[0256] For example, when the computer program is executed by a computer, the computer can implement the method executed by the sending end or the receiving end in each embodiment of the above method.

[0257] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by a sending end or a receiving end in the above-mentioned method embodiments.

[0258] An embodiment of the present application also provides a communication system, including the aforementioned transmitting end and receiving end.

[0259] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0260] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0261] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0262] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: Determine a media access control MAC sub-packet data unit PDU, wherein the MAC sub-PDU includes a radio resource control RRC message, wherein the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, wherein a header of the MAC sub-PDU includes a logical channel identifier LCID field, and wherein the MAC sub-PDU includes a first field; Sending the MAC sub-PDU; When the first domain takes different values, the meaning represented by the LCID domain is determined according to different LCID tables.

2. The method according to claim 1, characterized in that The MAC sub-PDU includes a first field, including: The header of the MAC sub-PDU includes the first field; or the RRC message includes the first field.

3. The method according to claim 1 or 2, characterized in that: The LCID table is a correspondence between the index value of the LCID domain and the meaning represented by the index value of the LCID domain.

4. The method according to any one of claims 1 to 3, characterized in that Before sending the MAC sub-PDU, the method further includes: Determine whether the receiving end supports parsing the MAC sub-PDU.

5. The method according to claim 4, characterized in that The determining that the receiving end supports parsing the MAC sub-PDU includes: receiving indication information, where the indication information is used to indicate that the receiving end supports parsing the MAC sub-PDU; or, According to whether the receiving end supports the characteristics indicated by the MAC sub-PDU, it is determined that the receiving end supports parsing the MAC sub-PDU.

6. The method according to claim 5, characterized in that The indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

7. The method according to any one of claims 1 to 6, characterized in that The sending the MAC sub-PDU comprises: The MAC sub-PDU is sent during a random access procedure.

8. The method according to any one of claims 1 to 7, characterized in that If the first field is carried in the header of the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the size of the LCID field is 6 bits, and the size of the first field is 1 or 2 bits.

9. The method according to any one of claims 1 to 7, characterized in that If the first domain is carried in the RRC message in the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the header of the MAC sub-PDU also includes two reserved domains, the size of the LCID domain is 6 bits, and the size of each of the reserved domains is 1 bit.

10. A communication method, characterized in that: include: Receive a media access control MAC sub-packet data unit PDU, wherein the MAC sub-PDU includes a radio resource control RRC message, the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, the header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; Determine the meaning represented by the LCID domain according to the value of the first domain and the value of the LCID domain, When the first domain takes different values, the meaning represented by the LCID domain is determined according to different LCID tables.

11. The method according to claim 10, characterized in that The MAC sub-PDU includes a first field, including: The header of the MAC sub-PDU includes the first field; or the RRC message includes the first field.

12. The method according to claim 10 or 11, characterized in that: The LCID table is a correspondence between the index value of the LCID domain and the meaning represented by the index value of the LCID domain.

13. The method according to any one of claims 10 to 12, characterized in that Before receiving the MAC sub-PDU, the method further includes: Send indication information, where the indication information is used to indicate support for parsing the MAC sub-PDU.

14. The method according to claim 13, characterized in that The indication information is carried in dedicated signaling, multicast signaling, or broadcast signaling.

15. The method according to any one of claims 10 to 14, characterized in that The receiving the MAC sub-PDU comprises: The MAC sub-PDU is received during a random access procedure.

16. The method according to any one of claims 10 to 15, characterized in that If the first field is carried in the header of the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the size of the LCID field is 6 bits, and the size of the first field is 1 or 2 bits.

17. The method according to any one of claims 10 to 15, characterized in that If the first domain is carried in the RRC message in the MAC sub-PDU, the size of the header of the MAC sub-PDU is one byte, the header of the MAC sub-PDU also includes two reserved domains, the size of the LCID domain is 6 bits, and the size of each of the reserved domains is 1 bit.

18. A communication device, characterized in that: The device comprises: a processing unit, configured to determine a media access control MAC sub-packet data unit PDU, wherein the MAC sub-PDU includes a radio resource control RRC message, wherein the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, wherein a header of the MAC sub-PDU includes a logical channel identifier LCID field, and wherein the MAC sub-PDU includes a first field; A transceiver unit, configured to send the MAC sub-PDU; When the first domain takes different values, the meaning represented by the LCID domain is determined according to different LCID tables.

19. A communication device, characterized in that: The device comprises: A transceiver unit, configured to receive a media access control MAC sub-packet data unit PDU, wherein the MAC sub-PDU includes a radio resource control RRC message, wherein the RRC message includes an uplink common control channel UL CCCH message or a UL CCCH1 message or an uplink dedicated control channel UL DCCH message, wherein a header of the MAC sub-PDU includes a logical channel identifier LCID field, and the MAC sub-PDU includes a first field; a processing unit, configured to determine the meaning represented by the LCID field according to the value of the first field and the value of the LCID field, When the first domain takes different values, the meaning represented by the LCID domain is determined according to different LCID tables.

20. A communication device, characterized in that: include: A processor, configured to execute a computer program stored in a memory, so that the apparatus performs the method according to any one of claims 1 to 9; or, so that the apparatus performs the method according to any one of claims 10 to 17.

21. A computer program product, characterized in that The computer program product comprises instructions for performing the method of any one of claims 1 to 17.

22. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program; when the computer program is executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 17.

Images