CN115085877B - Information transmission method and device and IAB node - Google Patents

Information transmission method and device and IAB node Download PDF

Info

Publication number
CN115085877B
CN115085877B CN202110268074.3A CN202110268074A CN115085877B CN 115085877 B CN115085877 B CN 115085877B CN 202110268074 A CN202110268074 A CN 202110268074A CN 115085877 B CN115085877 B CN 115085877B
Authority
CN
China
Prior art keywords
pdu
type field
pdu type
extended
indication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110268074.3A
Other languages
Chinese (zh)
Other versions
CN115085877A (en
Inventor
刘进华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN202110268074.3A priority Critical patent/CN115085877B/en
Priority to PCT/CN2022/079249 priority patent/WO2022188705A1/en
Publication of CN115085877A publication Critical patent/CN115085877A/en
Application granted granted Critical
Publication of CN115085877B publication Critical patent/CN115085877B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses an information transmission method and device and an IAB node, and belongs to the technical field of communication. The method comprises the following steps: transmitting BAP Control PDU to the second IAB node; the packet header of BAP ControlPDU includes a first indication, where the first indication is used to indicate whether there is an extended PDU type field, where the extended PDU type field is a PDU type field obtained by extending a first PDU type field, and the first PDU type field supports indication of K PDU types, where K is a positive integer. By the information transmission method provided by the application, the variety of the PDU type capable of supporting indication can be increased through the expanded PDU type field under the condition that the types of the BAP control PDU are increased.

Description

Information transmission method and device and IAB node
Technical Field
The present application belongs to the field of communication technologies, and in particular, to an information transmission method, an information transmission device, and an IAB node.
Background
A backhaul adaptation protocol control protocol data unit (Backhaul Adaptation Protocol control Protocol Data Unit, BAP control PDU) is used to carry control information of the BAP layer. Currently, as shown in fig. 1, a header of a BAP control PDU may include an information Type field (D/C), a PDU Type field (PDU Type) and three reserved bits (R), wherein the D/C field is used to indicate whether the PDU is a control signal or data, and the PDU Type field is used to indicate a Type of the BAP control PDU. In the prior art, the PDU Type field only includes 4 bits, and the Type of the BAP control PDU only includes four types, which are indicated by four indication values of the PDU Type field, respectively. However, in the case where the types of BAP control PDUs are increasing, there is no solution how to indicate the types of BAP control PDUs.
Disclosure of Invention
The embodiment of the application provides an information transmission method, an information transmission device and an IAB node, which can provide a type indication mode of a BAP control PDU under the condition that the types of the BAP control PDU are increased so as to support indication of more PDU types.
In a first aspect, an embodiment of the present application provides an information transmission method, performed by a first self-Backhaul (IAB) node, including:
transmitting BAP Control PDU to the second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In a second aspect, an embodiment of the present application further provides an information transmission method, performed by a second IAB node, where the method includes:
receiving a BAP Control PDU from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In a third aspect, an embodiment of the present application provides an information transmission apparatus, including:
a sending module, configured to send a BAP Control PDU to a second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In a fourth aspect, an embodiment of the present application further provides an information transmission apparatus, including:
a receiving module, configured to receive a BAP Control PDU from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In a fifth aspect, an embodiment of the present application further provides a first IAB node, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the steps of the method according to the first aspect when executed by the processor.
In a sixth aspect, embodiments of the present application also provide a second IAB node comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps of the method according to the second aspect.
In a seventh aspect, embodiments of the present application also provide a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect.
In an eighth aspect, an embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network device program or an instruction, to implement a method as described in the first aspect, or to implement a method as described in the second aspect.
In the embodiment of the application, the BAP Control PDU is sent to the second IAB node; the packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer. This makes it possible to increase the variety of the supportable indicated PDU types by the extended PDU type field in case the types of BAP control PDUs are increased.
Drawings
Fig. 1 is a schematic diagram of a BAP Control PDU header format provided in the related art;
FIG. 2 is a schematic diagram of an IAB system according to an embodiment of the present application;
Fig. 3 is a schematic structural diagram of a CU-DU of an AB system according to an embodiment of the present application;
FIG. 4 is a block diagram of a network system to which embodiments of the present application are applicable;
Fig. 5 is a flowchart of an information transmission method according to an embodiment of the present application;
FIG. 6a is a schematic diagram of an extended PDU type field provided by an embodiment of the present application;
FIG. 6b is a second diagram of an extended PDU type field provided by an embodiment of the present application;
FIG. 6c is a third diagram illustrating an extended PDU type field provided by an embodiment of the present application;
FIG. 7 is a diagram of an extended PDU type field according to an embodiment of the present application;
fig. 8 is a flowchart of another information transmission method according to an embodiment of the present application;
Fig. 9 is a block diagram of an information transmission apparatus according to an embodiment of the present application;
fig. 10 is a block diagram of another information transmission apparatus according to an embodiment of the present application;
Fig. 11 is a block diagram of a first IAB node according to an embodiment of the present application;
fig. 12 is a block diagram of a second IAB node according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the application may be practiced otherwise than as specifically illustrated and described herein, and that the "first" and "second" distinguishing between objects generally being of the same type, and not necessarily limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "means a relationship in which the associated object is an" or "in general.
It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. However, the following description describes a New air interface (NR) system for purposes of example, and NR terminology is used in much of the following description, although these techniques are also applicable to applications other than NR system applications, such as the 6th generation (6th Generation,6G) communication system.
For ease of understanding, some of the following descriptions are directed to embodiments of the present application:
self-backhauling (INTEGRATED ACCESS Backhaul, IAB):
The IAB system is a technology of starting to make standards in a sixteenth version (Release 16, rel-16) of a New Radio, NR. As shown in fig. 2, an IAB node includes a Distributed Unit (DU) function and a mobile device (Mobile Termination, MT) function. By means of MT, an access IAB node (i.e., IAB node) can find an upstream IAB node (i.e., parent IAB node) and establish a wireless connection with a DU accessing the IAB node, which is called backhaul link. After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU provides cell service, i.e. the DU may provide access service for the UE. A self-access backhaul loop also includes a host IAB node (i.e., donor IAB node) having a wired transmission network directly connected thereto.
Fig. 3 is a schematic diagram of a central Unit-Distributed Unit (CU-DU) of an IAB system. In a self-access backhaul loop, all IAB node DUs are connected to a CU node, which includes a CU control plane (i.e., CU-CP) and a CU user plane (i.e., CU-UP), the DUs are configured by the CU node via F1-C or a protocol called F1-AP (i.e., F1 application protocol), and the MTs are configured via a radio resource control (Radio Resource Control, RRC) protocol. The home IAB node has no MT functional part. The IAB system is introduced to solve the problem that when the access points are densely deployed, the wired transmission network is not deployed in place, that is, when the wired transmission network is not available, the access points can rely on wireless backhaul.
BAP Control PDU：
The BAP control PDU is used to carry control information of the BAP layer. According to the BAP layer protocol of R16, the third generation partnership project (3rd Generation Partnership Project,3GPP) has defined 4 BAP control PDU types:
Returning a radio link failure indication (BH RLF Indication): an IAB node may use the BAP control PDU to notify its sub-IAB node of its radio link restoration failure message;
Flow control feedback (Flow control Feedback per BH RLC CHANNEL) of the backhaul radio link control channel: the sub IAB node reports the BAP control PDU type of the downlink flow control report to the father IAB node according to the feedback wireless link control channel (BH RLC CHANNEL);
Flow control feedback (Flow control feedback per BAP routing ID) of the adaptation protocol route identification is passed back: performing a BAP control PDU type of a downlink flow control report according to a backhaul adaptation protocol routing identifier (BAP routing ID), and reporting the BAP control PDU type to a parent IAB node by a child IAB node;
flow control feedback query (Flow control Feedback polling): the parent IAB node inquires the child IAB node about the BAP control PDU type of the downlink flow control report, and the parent IAB node sends the BAP control PDU type to the child IAB node.
Specifically, the header of the BAP control PDU may be as shown in fig. 1, wherein the PDU Type field is used to indicate the Type of the BAP control PDU, and the existing BAP control PDU Type indication may be as shown in table 1.
Table 1PDU type
Bits Description of the invention
0000 Flow control feedback for backhaul radio link control channels
0001 Flow control feedback for backhaul adaptation protocol routing identification
0010 Flow control feedback interrogation
0011 Returning radio link failure indications
0100-1111 Reservation of
Currently, the following scenario is being discussed by 3GPP, possibly introducing a new BAP control PDU type:
An IAB node and a father IAB node thereof fail in radio link, and the child IAB node is informed of RLF discovery;
After the radio link between one IAB node and the father IAB node fails, the radio link is successfully recovered, and the child IAB node is informed of the successful recovery of the RLF;
Using BAPcontrol PDU to inform the downstream node of the start of the handover in IAB network handover, and requiring a new BAP control PDU type;
An IAB node informs a sub IAB node of uplink flow information, and two BAP control PDU types are needed;
Existing BAP control PDUs for downstream flow control may need improvement, e.g., reporting per BH RLC CHANNEL group;
for reporting congestion information based on data latency or rate;
information potentially useful for alternative link state monitoring and notification for local rerouting (local rerouting).
The embodiment of the application provides an information transmission method aiming at the indication of the BAP control PDU type under the condition that the BAP control PDU type is increased, and the indication value field of the PDU type field is expanded to support the indication of more types of BAP control PDU types.
Fig. 4 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system comprises a first IAB node 11 and a second IAB node 12. The first IAB node 11 may be a child node of the second IAB node 12, or may be a parent node of the second IAB node 12, which is not limited in this embodiment.
The information transmission method provided by the embodiment of the application is described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.
Referring to fig. 5, fig. 5 is a flowchart of an information transmission method according to an embodiment of the present application, where the method may be performed by a first IAB node, as shown in fig. 5, and includes the following steps:
step 501, sending BAP Control PDU to the second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In this embodiment, the second IAB node may be a child node of the first IAB node, or may be a parent node of the first IAB node.
The above-described first PDU Type field may be understood as a predefined PDU Type field or a PDU Type field in the related art, for example, a PDU Type field as shown in fig. 1. The first PDU Type field supports and indicates PDU types in K, where K is a positive integer, and the first PDU Type field is the PDU Type field shown in fig. 1, and the first PDU Type field supports and indicates 4 PDU types, and the indication values of the first PDU Type fields corresponding to the various PDU types may be shown in table 1.
The extended PDU type field is a PDU type field obtained by extending the first PDU type field, and can be understood as a PDU type field obtained by extending the first PDU type field. For example, the above-mentioned extended PDU type field may be a PDU type field obtained by extending bits for indicating the PDU type on the basis of the first PDU type field, or a PDU type field obtained by extending an indication value field for indicating the PDU type on the basis of the first PDU type field. Wherein the extended PDU type field supports indicating at least one PDU type, e.g., the extended PDU type field may support indicating at least one PDU type different from the K PDU types, or the extended PDU type field may support indicating more than K PDU types, or a combination of the extended PDU type field and the first PDU type field may support indicating more than K PDU types.
It should be noted that the first PDU type field corresponds to a first BAP Control PDU format, and for example, a PDU header of the first BAP Control PDU format may be as shown in fig. 1. The extended PDU type field corresponds to a second BAP Control PDU format, and a PDU header of the second BAP Control PDU format may be as shown in fig. 6a to 6c, for example.
The first indication is used to indicate whether the second IAB node has an extended PDU type field. The first indication may be indicated by a bit in the packet header of the BAP Control PDU, for example, may be indicated by a PDU type field of the packet header of the first BAP Control PDU format shown in fig. 1, or may be indicated by at least one reserved bit (i.e., R) of the packet header of the first BAP Control PDU format shown in fig. 1.
In the case where the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU may be indicated only by the extended PDU type field, or may be indicated together by the extended PDU type field and the first PDU type field. In case that the first indication indicates that there is no extended PDU type field, the PDU type of the BAP Control PDU may be indicated by the first PDU type field.
The information transmission method provided by the embodiment of the application is that BAP Control PDU is sent to the second IAB node; the packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, K types of PDU types are supported and indicated by the first PDU type domain, K is a positive integer, and therefore the variety of the PDU types which can be supported and indicated can be increased through the extended PDU type domain under the condition that the types of the BAP Control PDU are increased.
Optionally, the extended PDU type field support indicates M PDU types, or the extended PDU type field support indicates N PDU types, where N PDU types are different from the K PDU types, M and N are both positive integers, and M is greater than K.
In an embodiment, the extended PDU type field may support more than K PDU types, that is, the number of types of PDU types indicated by the extended PDU type field support is greater than the number of types of PDU types indicated by the first PDU type field support. For example, the number of bits of the extended PDU type field may be greater than the number of bits of the first PDU type field, or the number of indication values for indicating a PDU type in the extended PDU type field may be greater than the number of indication values for indicating a PDU type in the first PDU type field.
In another embodiment, the extended PDU type field and the first PDU type field may be used to indicate different PDU types, respectively. For example, the first PDU Type field is a PDU Type field shown in fig. 1, the first PDU Type field may support 16 PDU types, and the extended PDU Type field may support a PDU Type indicating other than the 16 PDU types.
Optionally, the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, where the first BAP Control PDU format is a BAP Control PDU format corresponding to the first PDU type field;
Or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
In an embodiment, the first indication may be indicated by a reserved bit of a PDU header of the first BAP Control PDU format, where the first reserved bit may include at least one reserved bit of the PDU header of the first BAP Control PDU format. For example, whether an extended PDU type field exists may be indicated by at least one reserved bit (i.e., R) of a PDU header of the first BAP Control PDU format shown in fig. 1.
As another example, as shown in fig. 6a to 6c, the last R bit (bit) of the PDU header of the first BAP Control PDU format is redefined as E bit to indicate whether there is an extended PDU type field, where if e=1, it indicates that there is an extended PDU type field, otherwise it indicates that there is no extended PDU type field.
In another embodiment, the first indication may be indicated by an indication value of a first PDU type field, where the first indication value may include at least one indication value of the first PDU type field. For example, the presence and absence of the extended PDU type field may be indicated by two different indication values of the above-mentioned first PDU type field, respectively, or the presence of the extended PDU type field may be indicated by one indication value of the above-mentioned first PDU type field.
As another example, as shown in fig. 7, the existence of the extended PDU type field is indicated by a specific indication value of the first PDU type field, such as x1x2x3x4=1111, and an indication value of the first PDU type field other than the above specific indication value is used to indicate the PDU type. In this way, the second IAB node considers that there is an extended PDU type field when the indication value resolved to the first PDU type field is 1111, and determines the PDU type according to the indication value if the indication value resolved to the first PDU type field is an indication value other than 1111.
Optionally, the extended PDU type field may include at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
In this embodiment, the bits of the first PDU type field may include some or all bits of the first PDU type field.
The second reserved bits may include part or all of reserved bits of a PDU header of the first BAP Control PDU format. In the case where the first instruction is an instruction of the first reserved bit of the PDU header in the first BAP Control PDU format, the first reserved bit and the second reserved bit are different.
The bits located outside the PDU header of the first BAP Control PDU format may include one or more bits located outside the PDU header of the first BAP Control PDU format, for example, 8 bits filled with crossing lines as shown in fig. 6c and 7.
In an embodiment, the extended PDU type field may include only some or all bits of the first PDU type field. For example, the first PDU type field comprises four bits X1, X2, X3 and X4, the extended PDU type field also comprises four bits X1, X2, X3 and X4, wherein X1X2X3X4 = 0001 indicates PDU type a in case the first indication is not present for the extended PDU type field and X1X2X3X4 = 0001 indicates PDU type b in case the first indication is present for the extended PDU type field.
In another embodiment, the extended PDU type field may include only some or all of the reserved bits of the PDU header of the first BAP Control PDU format. For example, the extended PDU type field may include only 3R bits as shown in fig. 1, wherein in case that the extended PDU type field does not exist as the first indication, a PDU type different from the kind of the PDU type supported by the first PDU type field is indicated by the above 3R bits, or the PDU type may be indicated by a combination of all bits of the first PDU type field and the above 3R bits.
In another embodiment, the extended PDU type field may include only at least one bit located outside the PDU header of the first BAP Control PDU format.
For example, as shown in fig. 6c, the extended PDU type field includes 8 bits located outside the PDU header of the first BAP Control PDU format, and the last Rbit of the PDU header of the first BAP Control PDU format is redefined as E bit, which is used to indicate that there is an extended PDU type field when e=1, otherwise there is no extended PDU type.
As another example, as shown in fig. 7, the extended PDU type field includes 8 bits located outside the PDU header of the first BAP Control PDU format, and the existence of the extended PDU type field is indicated by one specific indication value of the first PDU type field.
In another embodiment, the extended PDU type field may include some or all of the bits of the first PDU type field and some or all of the reserved bits of the PDU header of the first BAP Control PDU format.
For example, as shown in fig. 6a, the extended PDU type field includes 4 bits and 2 reserved bits of the first PDU type field, and the last Rbit of the PDU header of the first BAP Control PDU format is redefined as E bit, indicating that the PDU type field is extended from 4 bits to 6 bits when e=1, i.e. there is an extended PDU type, otherwise there is no extended PDU type.
As another example, as shown in fig. 6b, the extended PDU type field includes 4 bits and 1 reserved bit of the first PDU type field, redefine the last Rbit of the PDU header of the first BAP Control PDU format as E bit, and when e=1 indicates that the PDU type field is extended from 4bit to 5bit, i.e. there is an extended PDU type, otherwise there is no extended PDU type.
In another embodiment, the extended PDU type field may include some or all bits of the first PDU type field and at least one bit located outside the PDU header of the first BAP Control PDU format. For example, the extended PDU type field may include 4 bits of the first PDU type field and 8 bits located outside the PDU header of the first BAP Control PDU format, wherein in case the first indication that the extended PDU type field exists, the PDU type may be indicated by the indicated value of the 12 bits.
In another embodiment, the extended PDU type field may include a part or all of reserved bits of the PDU header of the first BAP Control PDU format and at least one bit located outside the PDU header of the first BAP Control PDU format. For example, the extended PDU type field may include 2 reserved bits of the PDU header of the first BAP Control PDU format and 8 bits located outside the PDU header of the first BAP Control PDU format, wherein in case that the first indication exists the extended PDU type field, the PDU type may be indicated by the indicated value of the above 10 bits.
In another embodiment, the extended PDU type field may include a part or all of bits of the first PDU type field, a part or all of reserved bits of a PDU header of the first BAP Control PDU format, and at least one bit located outside the PDU header of the first BAP Control PDU format. For example, the extended PDU type field may include 4 bits of the first PDU type field, 2 reserved bits of the PDU header of the first BAP Control PDU format, and 8 bits located outside the PDU header of the first BAP Control PDU format, wherein in case that the first indication exists the extended PDU type field, the PDU type may be indicated by the indicated value of the 14 bits.
Optionally, the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
In this embodiment, the indicated value range is understood as a range of values of the indicated value. The indicated value range of the extended PDU type field is different from the indicated value range of the first PDU type field, e.g. the indicated value range of the extended PDU type field is larger than the indicated value range of the first PDU type field or the intersection of the indicated value range of the first PDU type field and the indicated value range of the first PDU type field is empty.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field.
In this embodiment, in the case where the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by the indication value of the extended PDU type field, so that the second IAB node may determine the PDU type of the BAP Control PDU directly based on the indication value of the extended PDU type field.
Optionally, the indication value field of the extended PDU type field is: [0,2 r -1], or [2 q,2q+2r -1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
In an embodiment, the indication value field of the extended PDU type field may be [0,2 r -1], i.e. the indication value of the extended PDU type field is 0 to 2 r -1, for example, if r=5, the indication value field of the extended PDU type field may be [0, 31].
In this embodiment, in the case where the indication value field of the first PDU type field is [0,2 q -1], the indication value field of the extended PDU type field may include the same indication value as the indication value of the first PDU type field.
In another embodiment, the indicated value range of the extended PDU type field may be [2 q,2q+2r -1], i.e. the indicated value of the extended PDU type field is 2 q to 2 q+2r -1, e.g. if r=5, q=4, the indicated value range of the extended PDU type field may be [16, 31].
In this embodiment, in the case where the indication value field of the first PDU type field is [0,2 q -1], the indication value field of the extended PDU type field includes only an indication value different from the indication value of the first PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
In this embodiment, in the case where the first indication indicates that the extended PDU type field exists, the PDU type of the above BAP Control PDU may be indicated by the extended PDU type field and the first PDU type field together. For example, the extended PDU type field includes 2 bits, and the first PDU type field includes 4 bits, and the PDU type of the above BAP Control PDU may be indicated by an indication value of 6 bits.
Optionally, the indication value field of the second PDU type field may be: [0,2 i+j -1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
In this embodiment, the indication value of the second PDU type field may be [0,2 i+j -1], that is, the indication value of the second PDU type field is 0 to 2 i+j -1, for example, if i= 4,j =2, the indication value of the second PDU type field may be [0, 63].
Optionally, in the case that the first indication indicates that the extended PDU type field does not exist, the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field.
In this embodiment, in the case where the first indication indicates that the extended PDU type field does not exist, the PDU type of the BAP Control PDU is indicated by the indication value of the first PDU type field, so that the second IAB node may determine the PDU type of the BAP Control PDU directly based on the indication value of the first PDU type field.
Referring to fig. 8, fig. 8 is a flowchart of another information transmission method provided in an embodiment of the present application, and the method is performed by a second IAB node, as shown in fig. 8, and includes the following steps:
step 801, receiving BAP Control PDU from the first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
In this embodiment, the first PDU Type field may be understood as a predefined PDU Type field or a PDU Type field in the prior art, for example, the PDU Type field shown in fig. 1. The first PDU Type field supports and indicates PDU types in K, where K is a positive integer, and the first PDU Type field is the PDU Type field shown in fig. 1, and the first PDU Type field supports and indicates 4 PDU types, and the indication values of the first PDU Type fields corresponding to the various PDU types may be shown in table 1.
The extended PDU type field is a PDU type field obtained by extending the first PDU type field, and can be understood as a PDU type field obtained by extending the first PDU type field. For example, the above-mentioned extended PDU type field may be a PDU type field obtained by extending bits for indicating the PDU type on the basis of the first PDU type field, or a PDU type field obtained by extending an indication value field for indicating the PDU type on the basis of the first PDU type field. Wherein the extended PDU type field supports indicating at least one PDU type, e.g., the extended PDU type field may support indicating at least one PDU type different from the K PDU types, or the extended PDU type field may support indicating more than K PDU types, or a combination of the extended PDU type field and the first PDU type field may support indicating more than K PDU types.
The first indication is used to indicate whether the second IAB node has an extended PDU type field. The first indication may be indicated by a bit in the packet header of the BAP Control PDU, for example, may be indicated by a PDU type field of the packet header of the BAP Control PDU shown in fig. 1, or may be indicated by at least one reserved bit (i.e., R) of the packet header of the BAP Control PDU shown in fig. 1.
In the case where the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU may be indicated only by the extended PDU type field, or may be indicated together by the extended PDU type field and the first PDU type field. In case that the first indication indicates that there is no extended PDU type field, the PDU type of the BAP Control PDU may be indicated by the first PDU type field.
In practical application, if the second IAB node supports indicating the PDU type through the extended PDU type field under the condition that the second IAB node receives the BAP Control PDU, whether the extended PDU type field exists or not may be determined according to the first indication of the packet header of the BAP Control PDU, and if the extended PDU type field exists, the PDU type of the BAP Control PDU may be determined according to the extended PDU type field, otherwise, the PDU type of the BAP Control PDU may be determined according to the first PDU type field. If the second IAB node does not support the indication of the PDU type by the extended PDU type field, the PDU type of the BAP Control PDU may be determined based on the first PDU type field, and if the analysis results in that the first PDU type field does not indicate the PDU type of the BAP Control PDU, the BAP Control PDU may be discarded.
The information transmission method provided by the embodiment of the application receives BAP Control PDU from the first IAB node; the packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, K types of PDU types are supported and indicated by the first PDU type domain, K is a positive integer, and therefore the variety of the PDU types which can be supported and indicated can be increased through the extended PDU type domain under the condition that the types of the BAP Control PDU are increased.
Optionally, the extended PDU type field support indicates M PDU types, or the extended PDU type field support indicates N PDU types, where N PDU types are different from the K PDU types, M and N are both positive integers, and M is greater than K.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, where the first BAP Control PDU format is a BAP Control PDU format corresponding to the first PDU type field;
Or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the indication value field of the extended PDU type field is: [0,2 r -1], or [2 q,2q+2r -1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the indication value field of the second PDU type field is: [0,2 i+j -1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, in the case that the first indication indicates that the extended PDU type field does not exist, the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field.
The implementation of this embodiment may be referred to in the related description of the embodiment shown in fig. 5, which is not described herein.
Optionally, the method may further include:
and if the second IAB node does not support the PDU type indication through the extended PDU type field, discarding the BAP Control PDU if the first indication indicates that the extended PDU type field exists.
In this embodiment, the second IAB node does not support the indication of the PDU type by the extended PDU type field, i.e. the second IAB node does not support the BAP Control PDU format shown in fig. 6a to 6c and fig. 7, etc. described above. Specifically, in the case that the second IAB node does not support the indication of the PDU type by the extended PDU type field, the PDU type of the received BAP Control PDU may be directly parsed according to the first PDU type field, and if the PDU type of the BAP Control PDU is not parsed, the BAP Control PDU may be discarded.
It should be noted that, in this embodiment, as an implementation manner of the second IAB node corresponding to the embodiment shown in fig. 5, a specific implementation manner of the second IAB node may refer to the description related to the embodiment shown in fig. 5, and achieve the same beneficial effects, so that the description is not repeated here.
Referring to fig. 9, fig. 9 is a block diagram of an information transmission apparatus according to an embodiment of the present application, and as shown in fig. 9, an information transmission apparatus 900 includes:
A sending module 901, configured to send a BAP Control PDU to a second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
Optionally, the extended PDU type field support indicates M PDU types, or the extended PDU type field support indicates N PDU types, where N PDU types are different from the K PDU types, M and N are both positive integers, and M is greater than K.
Optionally, the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, where the first BAP Control PDU format is a BAP Control PDU format corresponding to the first PDU type field;
Or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
Optionally, the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
Optionally, the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field.
Optionally, the indication value field of the extended PDU type field is: [0,2 r -1], or [2 q,2q+2r -1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
Optionally, the indication value field of the second PDU type field is: [0,2 i+j -1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field does not exist, the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field.
The information transmission device provided by the embodiment of the present application can implement each process in the method embodiment of fig. 5, and in order to avoid repetition, a description thereof will not be repeated here.
It should be noted that, the information transmission device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in the first IAB node.
Referring to fig. 10, fig. 10 is a block diagram of another information transmission apparatus according to an embodiment of the present application, and as shown in fig. 10, an information transmission apparatus 1000 includes:
A receiving module 1001, configured to receive a BAP Control PDU from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
Optionally, the extended PDU type field support indicates M PDU types, or the extended PDU type field support indicates N PDU types, where N PDU types are different from the K PDU types, M and N are both positive integers, and M is greater than K.
Optionally, the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, where the first BAP Control PDU format is a BAP Control PDU format corresponding to the first PDU type field;
Or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
Optionally, the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
Optionally, the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field.
Optionally, the indication value field of the extended PDU type field is: [0,2r-1], or [2q,2q+2r-1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field exists, the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
Optionally, the indication value field of the second PDU type field is: [0,2i+j-1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
Optionally, in the case that the first indication indicates that the extended PDU type field does not exist, the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field.
Optionally, the apparatus further comprises:
And the discarding module is configured to discard the BAP Control PDU if the first indication indicates that the extended PDU type field exists in the case that the second IAB node does not support the PDU type indicated by the extended PDU type field.
The information transmission device provided in the embodiment of the present application can implement each process in the method embodiment of fig. 8, and in order to avoid repetition, a description thereof will not be repeated here.
It should be noted that, the information transmission device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in the second IAB node.
Referring to fig. 11, fig. 11 is a block diagram of a network device according to an embodiment of the present application, where the network device 1100 includes: processor 1101, transceiver 1102, memory 1103 and bus interface, wherein:
a transceiver 1102 for transmitting a BAP Control PDU to a second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
It should be understood that, in this embodiment, the processor 1101 and the transceiver 1102 can implement each process implemented by the first IAB node in the method embodiment of fig. 5, and achieve the same technical effects, and are not repeated here.
It should be noted that, the transceiver 1102 is configured to receive and transmit data under the control of the processor 1101, and the transceiver 1102 includes at least two antenna ports.
In fig. 11, a bus architecture may comprise any number of interconnecting buses and bridges, with various circuits of the one or more processors, as represented by the processor 1101, and the memory, as represented by the memory 1103, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1102 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 1104 may also be an interface capable of interfacing with an inscribed desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing the operations.
Optionally, the embodiment of the present application further provides a first IAB node, which includes a processor 1101, a memory 1103, and a program or an instruction stored in the memory 1103 and capable of running on the processor 1101, where the program or the instruction implements each process of the above embodiment of the information transmission method when executed by the processor 1101, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
Referring to fig. 12, fig. 12 is a block diagram of a second IAB node according to an embodiment of the present application, where a second IAB node 1200 includes: a processor 1201, a transceiver 1202, a memory 1203, and a bus interface, wherein:
A transceiver 1202 for receiving a BAP Control PDU from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
It should be understood that, in this embodiment, the processor 1201 and the transceiver 1202 can implement the respective processes implemented by the second IAB node in the method embodiment of fig. 8, and achieve the same technical effects, and are not described herein again for avoiding repetition.
It should be noted that, the transceiver 1202 is configured to receive and transmit data under the control of the processor 1201, and the transceiver 1202 includes at least two antenna ports.
In fig. 12, a bus architecture may be comprised of any number of interconnected buses and bridges, and in particular, one or more processors represented by the processor 1201 and various circuits of memory represented by the memory 1203. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1202 may be a number of elements, i.e., include a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 1204 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 1201 is responsible for managing the bus architecture and general processing, and the memory 1203 may store data used by the processor 1201 in performing operations.
Optionally, the embodiment of the present application further provides a second IAB node, which includes a processor 1201, a memory 1203, and a program or an instruction stored in the memory 1203 and capable of running on the processor 1201, where the program or the instruction implements each process of the above embodiment of the information transmission method when executed by the processor 1201, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored in the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the first IAB node side information transmission method or the second IAB node side information transmission method embodiment, and the same technical effect can be achieved, so that repetition is avoided, and no further description is given here.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network device program or an instruction, so as to implement the above processes of implementing the embodiment of the information transmission method on the first IAB node side or the information transmission method on the second IAB node side, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims (32)

1. An information transmission method, performed by a first self-backhauled IAB node, the method comprising:
transmitting a backhaul adaptation protocol Control protocol data unit (BAP Control PDU) to a second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
2. The method of claim 1, wherein the extended PDU type field support indicates M PDU types or the extended PDU type field support indicates N PDU types, the N PDU types being different from the K PDU types, M and N being positive integers, and M being greater than K.
3. The method of claim 1, wherein the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, the first BAP Control PDU format being a BAP Control PDU format corresponding to the first PDU type field;
Or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
4. The method of claim 1, wherein the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
5. The method of claim 1, wherein the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
6. The method of claim 1, wherein the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field if the first indication indicates the presence of the extended PDU type field.
7. The method of claim 6, wherein the indication value field of the extended PDU type field is: [0,2 r -1], or [2 q,2q+2r -1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
8. The method according to claim 1, wherein, in case the first indication indicates the presence of the extended PDU type field, the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
9. The method of claim 8, wherein the indication value field of the second PDU type field is: [0,2 i +j -1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
10. The method of claim 1, wherein the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field if the first indication indicates that the extended PDU type field is not present.
11. An information transmission method, performed by a second IAB node, the method comprising:
Receiving a backhaul adaptation protocol Control protocol data unit (BAP Control PDU) from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
12. The method of claim 11, wherein the extended PDU type field support indicates M PDU types or the extended PDU type field support indicates N PDU types, the N PDU types being different from the K PDU types, M and N being positive integers, and M being greater than K.
13. The method of claim 11, wherein the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, the first BAP Control PDU format being a BAP Control PDU format corresponding to the first PDU type field; or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
14. The method of claim 11, wherein the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
15. The method of claim 11, wherein the indication value range of the extended PDU type field is different from the indication value range of the first PDU type field.
16. The method of claim 11, wherein the PDU type of the BAP Control PDU is indicated by an indication value of the extended PDU type field if the first indication indicates the presence of the extended PDU type field.
17. The method of claim 16, wherein the indication value field of the extended PDU type field is: [0,2 r -1], or [2 q,2q+2r -1];
Wherein r is the number of bits of the extended PDU type field, and q is the number of bits of the first PDU type field.
18. The method of claim 11, wherein the PDU type of the BAP Control PDU is indicated by an indication value of a second PDU type field if the first indication indicates the presence of the extended PDU type field;
Wherein the second PDU type field includes a bit of the extended PDU type field and a bit of the first PDU type field, the bit of the extended PDU type field being different from the bit of the first PDU type field.
19. The method of claim 18, wherein the indication value field of the second PDU type field is: [0,2 i +j -1];
wherein i is the number of bits of the first PDU type field, and j is the number of bits of the extended PDU type field.
20. The method of claim 11, wherein the PDU type of the BAP Control PDU is indicated by an indication value of the first PDU type field if the first indication indicates that the extended PDU type field is not present.
21. The method of claim 11, wherein the method further comprises:
and if the second IAB node does not support the PDU type indication through the extended PDU type field, discarding the BAP Control PDU if the first indication indicates that the extended PDU type field exists.
22. An information transmission apparatus, characterized in that the apparatus comprises:
A sending module, configured to send a backhaul adaptation protocol Control protocol data unit (BAP Control PDU) to a second IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
23. The apparatus of claim 22, wherein the extended PDU type field support indicates M PDU types or the extended PDU type field support indicates N PDU types, the N PDU types being different from the K PDU types, M and N being positive integers, and M being greater than K.
24. The apparatus of claim 22, wherein the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, the first BAP Control PDU format being a BAP Control PDU format corresponding to the first PDU type field; or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
25. The apparatus of claim 22, wherein the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
26. An information transmission apparatus, characterized in that the apparatus comprises:
a receiving module, configured to receive a backhaul adaptation protocol Control protocol data unit (BAP Control PDU) from a first IAB node;
The packet header of the BAP Control PDU comprises a first indication, wherein the first indication is used for indicating whether an extended PDU type domain exists, the extended PDU type domain is a PDU type domain obtained by extending a first PDU type domain, the first PDU type domain supports K PDU types, and K is a positive integer.
27. The apparatus of claim 26, wherein the extended PDU type field support indicates M PDU types or the extended PDU type field support indicates N PDU types, the N PDU types being different from the K PDU types, M and N being positive integers, and M being greater than K.
28. The apparatus of claim 26, wherein the first indication is indicated by a first reserved bit of a PDU header of a first BAP Control PDU format, the first BAP Control PDU format being a BAP Control PDU format corresponding to the first PDU type field; or alternatively
The first indication is indicated by a first indication value of the first PDU type field.
29. The apparatus of claim 26, wherein the extended PDU type field comprises at least one of:
Bits of the first PDU type field;
A second reserved bit of a PDU packet header of the first BAP Control PDU format;
bits located outside the PDU header of the first BAP Control PDU format;
Wherein, the first BAP Control PDU format is the BAP Control PDU format corresponding to the first PDU type domain.
30. A first IAB node comprising: memory, a processor and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the information transmission method according to any one of claims 1 to 10.
31. A second IAB node comprising: memory, a processor and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps in the information transmission method according to any one of claims 11 to 21.
32. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions which, when executed by a processor, realizes the steps of the information transmission method according to any one of claims 1 to 10, or which, when executed by a processor, realizes the steps of the information transmission method according to any one of claims 11 to 21.
CN202110268074.3A 2021-03-11 2021-03-11 Information transmission method and device and IAB node Active CN115085877B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110268074.3A CN115085877B (en) 2021-03-11 2021-03-11 Information transmission method and device and IAB node
PCT/CN2022/079249 WO2022188705A1 (en) 2021-03-11 2022-03-04 Information transmission method and apparatus, and iab node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110268074.3A CN115085877B (en) 2021-03-11 2021-03-11 Information transmission method and device and IAB node

Publications (2)

Publication Number Publication Date
CN115085877A CN115085877A (en) 2022-09-20
CN115085877B true CN115085877B (en) 2024-05-03

Family

ID=83227395

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110268074.3A Active CN115085877B (en) 2021-03-11 2021-03-11 Information transmission method and device and IAB node

Country Status (2)

Country Link
CN (1) CN115085877B (en)
WO (1) WO2022188705A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351700A (en) * 2018-04-05 2019-10-18 中兴通讯股份有限公司 A kind of relay transfer method and node from access return link
CN110351860A (en) * 2018-04-02 2019-10-18 中国移动通信有限公司研究院 A kind of MAC PDU transmission method and device
CN110392992A (en) * 2017-02-03 2019-10-29 瑞典爱立信有限公司 Header extension format
CN110831248A (en) * 2018-08-10 2020-02-21 华为技术有限公司 Notification method, device and base station
CN110958642A (en) * 2018-09-27 2020-04-03 华为技术有限公司 Data transmission method and device for wireless backhaul network
CN111510929A (en) * 2019-01-31 2020-08-07 中兴通讯股份有限公司 Method and device for L CID expansion in IAB network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101471924A (en) * 2007-12-27 2009-07-01 华为技术有限公司 Method and apparatus for indicating data packet head
US20190297529A1 (en) * 2018-03-23 2019-09-26 Qualcomm Incorporated Extension of logical channel number in cellular radio access technologies

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110392992A (en) * 2017-02-03 2019-10-29 瑞典爱立信有限公司 Header extension format
CN110351860A (en) * 2018-04-02 2019-10-18 中国移动通信有限公司研究院 A kind of MAC PDU transmission method and device
CN110351700A (en) * 2018-04-05 2019-10-18 中兴通讯股份有限公司 A kind of relay transfer method and node from access return link
CN110831248A (en) * 2018-08-10 2020-02-21 华为技术有限公司 Notification method, device and base station
CN110958642A (en) * 2018-09-27 2020-04-03 华为技术有限公司 Data transmission method and device for wireless backhaul network
CN111510929A (en) * 2019-01-31 2020-08-07 中兴通讯股份有限公司 Method and device for L CID expansion in IAB network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
IPv6中的网络隐蔽通道技术研究;杨智丹;刘克胜;李丽;;东南大学学报(自然科学版)(第S1期);全文 *
ZTE, Sanechips.R2-2000510 "Discussion on BAP control PDU of RLF indication".3GPP tsg_ran\wg2_rl2.2020,(第tsgr2_109_e期),全文. *
杨智丹 ; 刘克胜 ; 李丽 ; .IPv6中的网络隐蔽通道技术研究.东南大学学报(自然科学版).2007,(第S1期),全文. *

Also Published As

Publication number Publication date
WO2022188705A1 (en) 2022-09-15
CN115085877A (en) 2022-09-20

Similar Documents

Publication Publication Date Title
CN110636628B (en) Information transmission method and device
US11096184B2 (en) Data processing method, terminal device, and base station
US20200107342A1 (en) Route update method, scheduling request cancellation method, and device
CN109246770B (en) Switching method, terminal equipment and network equipment
CN114651470A (en) Method and apparatus for performing dynamic cross link interference measurement and reporting in next generation mobile communication system
WO2019096274A1 (en) Signal transmission method and device
CN113746585A (en) Time service method and communication device
US20210219171A1 (en) Communication method and device
US11006478B2 (en) Enhanced procedure transaction ID handling
JP2019527503A (en) Data retransmission method and apparatus
US8503333B2 (en) Reestablishment of an interface between nodes in a network using a backoff time
US20230269653A1 (en) Rerouting method and apparatus, and communication device
CN112994920B (en) SCTP connection management method and device
CN104221463B (en) Device and method for the operation of spontaneous execution implicit detach
CN115085877B (en) Information transmission method and device and IAB node
CN111726240B (en) Terminal control method, device and system
JP7305628B2 (en) Signal interference avoidance methods and network equipment
CN108029154A (en) Radio bearer management method, apparatus and system
EP3534662B1 (en) Bearer configuration method and related product
JP2006217110A (en) Radio lan system and multi-rate control method thereof
US11368949B2 (en) Information indication method and apparatus
CN113475159A (en) Method for avoiding transmission of unnecessary messages in wireless communication and related network and network node
WO2022206544A1 (en) Data scheduling method and apparatus, and device
EP1678965B1 (en) Method and arrangement for polling management
CN112218305B (en) Configuration updating method, communication device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant