CN114979966B

CN114979966B - Method and apparatus in a communication node for wireless communication

Info

Publication number: CN114979966B
Application number: CN202111625104.8A
Authority: CN
Inventors: 张晓博
Original assignee: Shanghai Tuluo Communication Technology Partnership LP
Current assignee: Shanghai Tuluo Communication Technology Partnership LP
Priority date: 2021-02-23
Filing date: 2021-12-28
Publication date: 2024-02-09
Anticipated expiration: 2041-12-28
Also published as: CN114979966A

Abstract

A method and apparatus in a communication node for wireless communication is disclosed. The method comprises the steps that a first node receives a first RRC message, wherein the first RRC message comprises a first domain, at least one second domain and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message. The scheme has the advantages that the bearing configuration of Broadcast (Broadcast)/Multicast (Multicast) is solved, and particularly the problems of PTP branch and PTM branch association are solved; the saved configuration parameters are multiplexed as much as possible, and the signaling overhead is reduced.

Description

Method and apparatus in a communication node for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a multi-connection transmission method and apparatus.

Background

Future wireless communication systems have more and more diversified application scenes, and different application scenes have different performance requirements on the system. To meet the different performance requirements of various application scenarios, a New air interface technology (NR) is decided to be researched in the 3GPP (3 rd Generation Partner Project, third Generation partnership project) RAN (Radio Access Network ) #72 times of the whole meeting, and standardized Work is started on NR by the 3GPP RAN #75 times of the whole meeting through the WI (Work Item) of NR.

Broadcast/Multicast (Multicast) transmission techniques are widely used in cellular network systems, such as MBMS (Multimedia Broadcast Multicast Service ) in a 4G LTE (Long Term Evolution, long term evolution) system. The main characteristic of broadcast/multicast transmission is that the network device can send the same broadcast/multicast data to a plurality of terminal nodes at the same time, and the network device has important value in the scenes of broadcast television, disaster early warning, emergency service, industrial control, internet of vehicles and the like. In LTE MBMS, the eNB schedules multiple terminal nodes to receive PDSCH (Physical Downlink Shared Channel ) or PMCH (Physical Multicast Channel, physical multicast channel) containing broadcast/multicast data through one PDCCH (Physical Downlink Control Channel ). The broadcast/multicast related identities include SC-RNTI (Single Cell RNTI), SC-N-RNTI (Single Cell Notification RNTI ) and G-RNTI (Group RNTI).

Disclosure of Invention

The network side may select PTM (Point-to-MultiPoint) or PTP (Point-to-MultiPoint) as a transmission mode of broadcast/multicast data according to the user distribution and the change of the channel state, and select the transmission mode of PTM (Point-to-MultiPoint) or PTP (Point-to-MultiPoint). There may be data loss during the switching between PTP and PTM transmission modes. Therefore, in order to support lossless transmission, the logical channels used for PTM transmission and PTP transmission are typically associated to the same higher layer entity, e.g. the same PDCP entity or the same RLC entity. There is no solution how to perform a Broadcast (Broadcast)/Multicast (Multicast) bearer configuration in order to achieve the association of PTP transmissions (PTP branches) and PTM transmissions (PTM branches).

In view of the above problems, the present application provides a solution. In the description for the above problems, a ground network (Terrestrial Network, TN) scenario is taken as an example; the method and the device are also applicable to scenes such as Non-terrestrial communication (Non-Terrestrial Network, NTN) and V2X, and achieve technical effects similar to TN scenes. Furthermore, the adoption of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

As an example, the term (terminality) in the present application is explained with reference to the definition of the 3GPP specification protocol TS36 series.

As an embodiment, the term in the present application is explained with reference to the definition of the 3GPP specification protocol TS38 series.

As an embodiment, the term in the present application is explained with reference to the definition of the 3GPP specification protocol TS37 series.

As one example, the term in the present application is explained with reference to the definition of the specification protocol of IEEE (Institute of Electrical and Electronics Engineers ).

It should be noted that, in the case of no conflict, the embodiments in any node of the present application and the features in the embodiments may be applied to any other node. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict.

The application discloses a method used in a first node of wireless communication, comprising the following steps:

receiving a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the first RRC message is CellGroupConfig IE, the first domain is a CellGroupId domain, and the second domain is an RLC-beaererconfig domain.

As a sub-embodiment of the above embodiment, the comment text tag (comment text tag) of the third domain is a Need M.

As a sub-embodiment of the above embodiment, the comment text tag (comment text tag) of the third domain is a Need N.

As a sub-embodiment of the above embodiment, the comment text tag (comment text tag) of the third domain is a Need R.

As a sub-embodiment of the above embodiment, the comment text tag (comment text tag) of the third domain is a Need S.

As a sub-embodiment of the above embodiment, the comment text tag (comment text tag) of the third field is mac-CellGroupConfig.

As a sub-embodiment of the above embodiment, the third domain includes at least one of a mac-CellGroupConfig domain, a physiologicellgroupconfig domain, or a speccellconfig domain.

As an embodiment, the first RRC Message includes an RRC (Radio Resource Control ) Message (Message).

As an embodiment, the first RRC message includes all or part of an IE (Information Element ) in one RRC message.

For one embodiment, the first RRC message includes all or part of the Field (Field) in one IE in one RRC message.

As an embodiment, the cell group configured by the first RRC message includes at least one of MCG (Master Cell Group, primary cell group) or SCG (Secondary Cell Group ).

As an embodiment, the second RRC message is CellGroupConfig IE.

As a sub-embodiment of the above embodiment, the first domain is absent from the second RRC message.

As a sub-embodiment of the above embodiment, the fourth domain is absent from the first RRC message.

As a sub-embodiment of the above embodiment, the value range of the fourth domain is the same as the value range of the first domain.

As an embodiment, the second RRC message is CellGroupConfig IE, the second domain is the RLC-beaderconfig domain, and the fourth domain is the servedradio bearer domain.

As an embodiment, the second RRC message is CellGroupConfig IE, the second domain is an RLC-beaderconfig domain, and the fourth domain is an associpedradio bearer domain.

As an embodiment, the second RRC message is an RLC-beaderconfig domain.

As a sub-embodiment of the above embodiment, the second domain of the second RRC message is the second RRC message.

As a sub-embodiment of the above embodiment, the second Field of the second RRC message includes all or part of a Field (Field) in the second RRC message.

As a sub-embodiment of the above embodiment, the second field of the second RRC message includes all or part of a field IE in the second RRC message.

As a sub-embodiment of the above embodiment, the fourth domain is a serverradiobearer domain.

As a sub-embodiment of the above embodiment, the fourth domain is an associpedservdiradiobearer domain.

As an embodiment, the fourth domain of the second RRC message belongs to the second domain of the second RRC message.

As an embodiment, the second RRC message is a RLC-beadertoaddmodlist field, and the second RRC message includes one or more RLC-beaderconfig fields.

As a sub-embodiment of the above embodiment, the second domain is an RLC-beareconfig domain, and the second domain of the second RRC message is one of the one or more RLC-beareconfig domains.

As one embodiment, the second RRC message configured cell group is associated with at least one of MCG (Master Cell Group, primary cell group) or SCG (Secondary Cell Group ).

As an embodiment, the second RRC message is used to configure one RLC entity, a connection with one PDCP entity, and a corresponding logical channel in the MAC.

As an embodiment, the second RRC message is used to configure at least one of an RLC entity, a connection with one PDCP entity, or a corresponding logical channel in the MAC.

As a sub-embodiment of the foregoing embodiment, the logical channel corresponding to the MAC is a logical channel corresponding to the RLC entity configured by the second RRC message.

As a sub-embodiment of the above embodiment, the connection with one PDCP entity indicates a radio bearer served by the RLC entity configured by the second RRC message.

As one embodiment, the act of determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message based on the fourth domain of the second RRC message comprises: determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to whether the value of the fourth domain of the second RRC message is the same as the value of the first domain of the first RRC message.

As an embodiment, the first RRC message includes at least one fourth domain; the act of determining, from the fourth domain of the second RRC message, whether to apply the third domain of the first RRC message to the second domain of the second RRC message includes: determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to whether the value of the fourth domain of the second RRC message is the same as the value of at least one of the fourth domains of the first RRC message.

As one embodiment, the act of applying the third domain of the first RRC message to the second domain of the second RRC message comprises: the current value of the third field is used.

As one embodiment, the act of applying the third domain of the first RRC message to the second domain of the second RRC message comprises: the previously configured values of the third domain are used.

As an embodiment, the current value of the third domain is a value of the third domain of the first RRC message.

As an embodiment, the previously configured value of the third domain is a value of the third domain of the first RRC message.

As one embodiment, the phrase that the fourth domain is two different domains than the first domain includes: the fourth field and the first field correspond to different IEs, respectively.

As one embodiment, the phrase that the fourth domain is two different domains than the first domain includes: the value range of the fourth domain is different from the name of the first domain.

According to an aspect of the application, the act of determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message comprises: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of the first domain of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of the first domain of the first RRC message, not applying the third domain of the first RRC message to the second domain of the second RRC message; the first domain is absent from the second RRC message, or the fourth domain is absent from the first RRC message.

As an embodiment, the first RRC message is CellGroupConfig IE, the first domain is a CellGroupId domain, the second domain is an RLC-beaderconfig domain, the second RRC message is CellGroupConfig IE, and the second RRC message is CellGroupConfig IE.

As a sub-embodiment of the above embodiment, the fourth domain is an associtedclelgroupid domain.

As a sub-embodiment of the above embodiment, the second RRC message is used to configure a cell group, and the cell group configured by the second RRC message is identified by the fourth field of the second RRC message.

As a sub-embodiment of the above embodiment, the third domain is a mac-CellGroupConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses MAC parameters configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses L1 parameters configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a spCellConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses parameters of a special cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message includes: the third domain of the first RRC message is not applied to a cell group configured by the second RRC message.

According to yet another aspect of the present application, the first RRC message includes at least one fourth domain; the act of determining, from the fourth domain of the second RRC message, whether to apply the third domain of the first RRC message to the second domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fourth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from any of the values of the fourth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

As an embodiment, the first RRC message is CellGroupConfig IE, the second domain is RLC-beaderconfig domain, and the fourth domain is serverradio bearer domain; the second RRC message is an RLC-bearconfig domain.

As a sub-embodiment of the above embodiment, the radio bearer served by the RLC entity configured by the second RRC message is identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, radio bearers served by RLC entities configured by any one of the second domains of the first RRC message are identified by the fourth one of the second domains of the first RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the radio bearer identified by at least one of the fourth domains of the first RRC message is the same as the radio bearer identified by the fourth domain of the second RRC message; the cell group to which the RLC entity of the second RRC message configuration belongs is the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the cell group to which the RLC entity of the second RRC message configuration belongs is the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the third domain is a mac-CellGroupConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses the MAC parameter configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses the L1 parameter configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a spCellConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses parameters of a special cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message includes: the third domain of the first RRC message is not applied to a cell group to which the RLC entity configured by the second RRC message belongs.

The application discloses a method used for a second node of wireless communication, which is characterized by comprising the following steps:

transmitting a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain;

wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is used to determine whether to apply the third domain of the first RRC message to the second domain of the second RRC message; the fourth domain is two different domains than the first domain.

The application discloses a first node used for wireless communication, which is characterized by comprising:

a first receiver that receives a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

The application discloses a second node for wireless communication, comprising:

a second transmitter transmitting a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain;

As one embodiment, the problems to be solved by the present application include: bearer configuration of Broadcast/Multicast (Multicast), in particular the problem of PTP-branch being associated with PTM-branch.

As one example, the benefits of the above method include: the saved configuration parameters are multiplexed as much as possible, and the signaling overhead is reduced.

As one example, the benefits of the above method include: the existing data structure is multiplexed to the greatest extent, and standard workload is reduced.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings in which:

fig. 1 shows a flow chart of transmission of a first signaling according to an embodiment of the present application;

FIG. 2 shows a schematic diagram of a network architecture according to one embodiment of the present application;

fig. 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to one embodiment of the present application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application;

fig. 5 shows a flow chart of wireless signal transmission according to one embodiment of the present application;

Fig. 6 shows a flow chart of wireless signal transmission according to yet another embodiment of the present application;

FIG. 7 illustrates a block diagram of a processing device for use in a first node according to one embodiment of the present application;

fig. 8 shows a block diagram of a processing arrangement for a second node according to an embodiment of the present application.

Detailed Description

The technical solution of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that, without conflict, the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other.

Example 1

Embodiment 1 illustrates a flow chart of transmission of a first signaling according to an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is emphasized that the order of the blocks in the drawing does not represent temporal relationships between the represented steps.

In embodiment 1, a first node in the present application receives a first RRC message in step 101, the first RRC message including a first domain, at least one second domain, and a third domain; in step 102, receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; in step 103, determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

As a sub-embodiment of the above embodiment, the third domain is a mac-CellGroupConfig domain.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain.

As a sub-embodiment of the above embodiment, the third domain is a spCellConfig domain.

As a sub-embodiment of the above embodiment, the second domain is used to configure one RLC entity, a connection with one PDCP entity, and a corresponding logical channel in the MAC.

As a sub-embodiment of the above embodiment, the logical channel corresponding to the MAC is a logical channel corresponding to an RLC entity configured by the second domain.

As a sub-embodiment of the above embodiment, the logical channel corresponding in the MAC is a logical channel configured by the second domain.

As a sub-embodiment of the above embodiment, the connection with one PDCP entity indicates a radio bearer served by the RLC entity of the second domain configuration.

As a sub-embodiment of the above embodiment, the PDCP entity belongs to a radio bearer served by an RLC entity configured by the second RRC message.

As an embodiment, the first RRC message includes all or part of an rrcrecon configuration message.

As an embodiment, the first RRC message includes all or part of an RRCConnectionReconfiguration message.

As an embodiment, the first RRC message includes K second domains, the one second domain is one of the K second domains, and the K is a positive integer greater than 1.

As a sub-embodiment of the above embodiment, the K is equal to 32.

As a sub-embodiment of the above embodiment, the K is not more than 10000.

As an embodiment, the first RRC message includes a plurality of second domains, and the one second domain is one of the plurality of second domains.

As an embodiment, the logical channel identified by the logical channel identity in the at least one second domain of the first RRC message belongs to a PTP branch of the first radio bearer.

As an embodiment, the logical channel identified by the logical channel identity in the at least one second domain of the first RRC message belongs to a PTM branch of the first radio bearer.

As an example, the PTP branch in the present application includes leg.

As an embodiment, the PTP branch in the present application includes link.

As an example, the PTP branch in the present application includes branch.

As an embodiment, the PTP branch in this application includes RLC bearer.

As an embodiment, the PTP branch in this application includes RLC channel.

As an embodiment, the PTP branch in the present application includes RLC entity.

As an embodiment, the PTM branch in the present application comprises leg.

As an embodiment, the PTM branch includes link in the present application.

As an embodiment, the PTM branch in the present application includes a branch.

As an embodiment, the PTM branch in the present application includes RLC bearer.

As an embodiment, the PTM branch in the present application comprises RLC channel.

As an embodiment, the PTM branch in the present application includes RLC entity.

As an embodiment, the at least one second domain of the first RRC message includes the fourth domain, and the first radio bearer is identified by the fourth domain in the at least one second domain of the first RRC message.

As an embodiment, the first RRC message is CellGroupConfig IE, the first domain is a CellGroupId domain, the second domain is an RLC-beaererconfig domain, and the fourth domain is a serverradio bearer domain.

As an embodiment, the first RRC message is CellGroupConfig IE, the first domain is a CellGroupId domain, the second domain is an RLC-beaderconfig domain, and the fourth domain is an associpedservdiradiobearer domain.

As an embodiment, the first radio bearer is an SRB (Signalling Radio Bearer, data radio bearer).

As an embodiment, the first radio bearer is a DRB (Data Radio Bearer ).

As an embodiment, the first radio bearer is an MRB (Multicast Radio Bearer ).

As an embodiment, the first Radio Bearer is an MBS-RB (Multicast and Broadcast Service-Radio Bearer), multicast broadcast service Radio Bearer.

As an embodiment, the first radio bearer is an SC-MRB (Single Cell-Multicast Radio Bearer), single Cell multicast radio bearer.

As an embodiment, the second RRC message is used to configure one cell group.

As a sub-embodiment of the above embodiment, the second RRC message configured cell group reuses some or all of the parameters of one configured cell group.

As a sub-embodiment of the above embodiment, the cell group configured by the second RRC message corresponds to a configured cell group, and the configured cell group is identified by the fourth field of the second RRC message.

As a sub-embodiment of the above embodiment, the cell group configured by the second RRC message is identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the cell group configured by the second RRC message does not have a cell group identity.

As a sub-embodiment of the above embodiment, the cell group configured by the second RRC message is a virtual cell group.

As an embodiment, the cell group identified by the fourth domain of the second RRC message includes at least one of MCG (Master Cell Group, primary cell group) or SCG (Secondary Cell Group ).

As an embodiment, the second domain of the second RRC message is used to configure one RLC entity, a connection with one PDCP entity, and a corresponding logical channel in the MAC.

As an embodiment, the second domain is used to configure at least one of an RLC entity, a connection with a PDCP entity, or a corresponding logical channel in the MAC.

As a sub-embodiment of the above embodiment, the logical channel corresponding in the MAC is a logical channel configured by the second domain of the second RRC message configuration.

As a sub-embodiment of the above embodiment, the PDCP entity is a PDCP entity associated with the RLC entity of the second RRC message configuration.

As a sub-embodiment of the above embodiment, the RLC entity of the second domain configuration of the second RRC message is an RLC entity of the second RRC message configuration.

As a sub-embodiment of the above embodiment, the logical channel configured by the second domain of the second RRC message is a logical channel configured by the second RRC message.

As an embodiment, the second RRC message is CellGroupConfig IE.

As a sub-embodiment of the above embodiment, the value range of the fourth domain is different from the value range of the first domain.

As a sub-embodiment of the above embodiment, the second Field includes all or part of a Field (Field) in an IE.

As a sub-embodiment of the above embodiment, the fourth Field includes all or part of a Field (Field) in one IE.

As an embodiment, the second RRC message includes all or part of an rrcrecon configuration message.

As an embodiment, the second RRC message includes all or part of an RRCConnectionReconfiguration message.

As an embodiment, the second RRC Message includes an RRC (Radio Resource Control ) Message (Message).

As an embodiment, the second RRC message includes all or part of an IE (Information Element ) in one RRC message.

For one embodiment, the second RRC message includes all or part of the Field (Field) in one IE in one RRC message.

As an embodiment, the logical channel identified by the logical channel identity in the second domain of the second RRC message belongs to a PTP branch of the second radio bearer.

As an embodiment, the logical channel identified by the logical channel identity in the second domain of the second RRC message belongs to a PTM leg of a second radio bearer.

As a practical example, the first radio bearer is identical to the second radio bearer.

As one embodiment, the second radio bearer is different from the second radio bearer.

As an embodiment, the second radio bearer is an SRB (Signalling Radio Bearer, data radio bearer).

As an embodiment, the second radio bearer is a DRB (Data Radio Bearer ).

As an embodiment, the second radio bearer is an MRB (Multicast Radio Bearer ).

As an embodiment, the second Radio Bearer is an MBS-RB (Multicast and Broadcast Service-Radio Bearer), multicast broadcast service Radio Bearer.

As an embodiment, the second radio bearer is an SC-MRB (Single Cell-Multicast Radio Bearer), single Cell multicast radio bearer.

As an embodiment, the second domain of the first RRC message includes the fourth domain, and the second radio bearer is identified by the fourth domain in the second domain of the second RRC message.

As an embodiment, the second RRC message is used to configure at least one of an RLC entity, a corresponding logical channel in the MAC, or an associated PDCP entity.

As an embodiment, the second RRC message is used to configure one RLC entity, a corresponding logical channel in the MAC, and an associated PDCP entity.

As an embodiment, the RLC entity configured by the second RRC message is identified by the fourth domain.

As an embodiment, the logical channel corresponding to the second RRC message configured in the MAC is identified by the fourth domain.

As an embodiment, the second RRC message is an RLC-beaderconfig domain.

As a sub-embodiment of the above embodiment, the second domain is a logicalChannelIdentity domain.

As a sub-embodiment of the above embodiment, the second domain is a serverradiobearer domain.

As a sub-embodiment of the above embodiment, the second domain is a reestablishRLC domain.

As a sub-embodiment of the above embodiment, the second domain is a rl-Config domain.

As a sub-embodiment of the above embodiment, the second domain is a mac-LogicalChannelConfig domain.

As a sub-embodiment of the above embodiment, the second domain is the rl-Config-v 1610 domain.

As a sub-embodiment of the above embodiment, the second domain is an associable logicalchannelidentity domain.

As a sub-embodiment of the above embodiment, the second domain is an associpedservdiradiobearer domain.

As a sub-embodiment of the above embodiment, the fourth domain is a logicalChannelIdentity domain.

As a sub-embodiment of the above embodiment, the fourth domain is a reestablishRLC domain.

As a sub-embodiment of the above embodiment, the fourth domain is a rl-Config domain.

As a sub-embodiment of the above embodiment, the fourth domain is a mac-LogicalChannelConfig domain.

As a sub-embodiment of the above embodiment, the fourth domain is the rl-Config-v 1610 domain.

As a sub-embodiment of the above embodiment, the fourth domain is an associable logicalchannelidentity domain.

As a sub-embodiment of the above embodiment, the second domain includes at least one of a logicalChannelIdentity domain, a servedobeeser domain, a resestishrlc domain, a rl-Config-v 1610 domain, a mac-LogicalChannelConfig domain, an associtachanneiidentity domain, or an associtdservedobeeser.

As a sub-embodiment of the above embodiment, the fourth domain includes at least one of a logicalChannelIdentity domain, a servedobeeser domain, a reestishrlc domain, a rl-Config-v 1610 domain, a mac-LogicalChannelConfig domain, an associtachanneiidentity domain, or an associtdservedobeeser.

As a sub-embodiment of the above embodiment, the value of the second field includes at least one of srb-Identity, drb-Identity or mrb-Identity.

As a sub-embodiment of the above embodiment, the value of the fourth field includes at least one of srb-Identity, drb-Identity or mrb-Identity.

As a sub-embodiment of the above embodiment, the value of the second field includes at least one of associatedSrb-Identity, associatedDrb-Identity, or associatedMrb-Identity.

As a sub-embodiment of the above embodiment, the value of the fourth field includes at least one of associatedSrb-Identity, associatedDrb-Identity, or associatedMrb-Identity.

As an embodiment, the second RRC message is used to configure at least one RLC entity, a connection with one PDCP entity, and a corresponding logical channel in the MAC.

As an embodiment, the scheduling signaling of the first RRC message on the air interface is identified by a unicast RNTI.

As an embodiment, the scheduling signaling of the second RRC message over the air interface is identified by a non-unicast RNTI.

As an embodiment, the scheduling signaling of the first RRC message on the air interface is identified by a non-unicast RNTI.

As an embodiment, the scheduling signaling of the second RRC message on the air interface is identified by a unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a non-unicast RNTI includes: and determining whether the scheduling signaling of the first RRC message on an air interface exists or not according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a non-unicast RNTI includes: and determining the time-frequency resource occupied by the first RRC message transmission according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a non-unicast RNTI includes: the non-unicast RNTI is used for CRC scrambling of scheduling signaling of the first RRC message over the air interface.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a non-unicast RNTI includes: and determining whether the scheduling signaling of the second RRC message on an air interface exists or not according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a non-unicast RNTI includes: and determining the time-frequency resource occupied by the second RRC message transmission according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a non-unicast RNTI includes: the non-unicast RNTI is used for CRC scrambling of scheduling signaling of the second RRC message over the air interface.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a unicast RNTI includes: and determining whether the scheduling signaling of the first RRC message on an air interface exists or not according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a unicast RNTI includes: and determining the time-frequency resource occupied by the first RRC message transmission according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the first RRC message over the air interface is identified by a unicast RNTI includes: the unicast RNTI is used for CRC scrambling of scheduling signaling of the first RRC message over the air interface.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a unicast RNTI includes: and determining whether the scheduling signaling of the second RRC message on an air interface exists or not according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a unicast RNTI includes: and determining the time-frequency resource occupied by the second RRC message transmission according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the second RRC message over the air interface is identified by a unicast RNTI includes: the unicast RNTI is used for CRC scrambling of scheduling signaling of the second RRC message over the air interface.

As one embodiment, the unicast RNTI includes a C-RNTI (Cell RNTI ).

As an embodiment, the unicast RNTI includes a number of bits that is a positive integer multiple of 8.

As an embodiment, the unicast RNTI includes 24 bits.

As an embodiment, the non-unicast RNTI includes a G-RNTI (Group RNTI).

As one embodiment, the non-unicast RNTI includes MBS-RNTI (Multicast/Broadcast RNTI).

As an embodiment, the non-unicast RNTI includes a number of bits that is a positive integer multiple of 8.

As an embodiment, the non-unicast RNTI includes 24 bits.

As one embodiment, the act of determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message based on the fourth domain of the second RRC message comprises: determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to whether the fourth domain of the first RRC message is absent.

As one embodiment, the act of determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message based on the fourth domain of the second RRC message comprises: determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to a value of the fourth domain of the second RRC message.

As one embodiment, the act of applying the third domain of the first RRC message to the second domain of the second RRC message comprises: and taking the value of the third domain of the first RRC message as the value of the second domain of a second RRC message.

As one embodiment, the phrase that the fourth domain is two different domains than the first domain includes: the range of values of the fourth domain is different from the range of values of the first domain.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates a diagram of a network architecture 200 of a 5G NR (New Radio, new air interface), LTE (Long-Term Evolution) and LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System)/EPS (Evolved Packet System ) 200 by some other suitable terminology. The 5GS/EPS 200 may include one or more UEs (User Equipment) 201, ng-RAN (next generation radio access network) 202,5GC (5G Core Network)/EPC (Evolved Packet Core, evolved packet core) 210, hss (Home Subscriber Server )/UDM (Unified Data Management, unified data management) 220, and internet service 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, 5GS/EPS provides packet switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gNB203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communication device, a land-based vehicle, an automobile, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. gNB203 is connected to 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity )/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function ) 211, other MME/AMF/SMF214, S-GW (Service Gateway)/UPF (User Plane Function ) 212, and P-GW (Packet Date Network Gateway, packet data network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet Protocal, internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address assignment as well as other functions. The P-GW/UPF213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IP Multimedia Subsystem ) and packet-switched streaming services.

As an embodiment, the UE201 corresponds to the first node in the present application.

As one embodiment, the UE201 supports transmissions in a non-terrestrial network (NTN).

As an embodiment, the UE201 supports transmissions in a large latency difference network.

As an embodiment, the UE201 supports transmission of a Terrestrial Network (TN).

As an embodiment, the UE201 is a User Equipment (UE).

As an embodiment, the UE201 is an aircraft.

As an embodiment, the UE201 is a vehicle terminal.

As an embodiment, the UE201 is a relay.

As an example, the UE201 is a ship.

As an embodiment, the UE201 is an internet of things terminal.

As an embodiment, the UE201 is a terminal of an industrial internet of things.

As an embodiment, the UE201 is a device supporting low latency and high reliability transmissions.

As an embodiment, the gNB203 corresponds to the second node in the present application.

As an embodiment, the gNB203 includes a primary node.

As an embodiment, the gNB203 includes an auxiliary node.

As an embodiment, the gNB203 includes a Base Station (BS).

As an embodiment, the gNB203 includes a user equipment.

As an embodiment, the gNB203 supports transmissions in a non-terrestrial network (NTN).

As an embodiment, the gNB203 supports transmissions in a large latency difference network.

As one embodiment, the gNB203 supports transmission of a Terrestrial Network (TN).

As an example, the gNB203 is a macro cell (Marco cell) base station.

As one example, the gNB203 is a Micro Cell (Micro Cell) base station.

As an example, the gNB203 is a Pico Cell (Pico Cell) base station.

As an example, the gNB203 is a home base station (Femtocell).

As an embodiment, the gNB203 is a base station device supporting a large delay difference.

As an embodiment, the gNB203 is a flying platform device.

As one embodiment, the gNB203 is a satellite device.

As an embodiment, the gNB203 is a UE (user equipment).

As an embodiment, the gNB203 is a gateway.

As an embodiment, the gNB203 is a base station device supporting NR.

As an embodiment, the gNB203 is a base station device supporting EUTRA.

As an embodiment, the gNB203 is a base station device supporting WLAN.

As an embodiment, the gNB203 is a base station device supporting BT.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture according to one user plane and control plane of the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 shows the radio protocol architecture for the control plane 300 with three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and includes a MAC (Medium Access Control ) sublayer 302, an RLC (Radio Link Control, radio link layer control protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol ) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out of order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control ) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), in which user plane 350 the radio protocol architecture is substantially the same for the physical layer 351, PDCP sublayer 354 in the L2 layer 355, RLC sublayer 353 in the L2 layer 355 and MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is an SDAP (Service Data Adaptation Protocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS flows and data radio bearers (DRBs, data Radio Bearer) to support diversity of traffic.

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the first node in the present application.

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the second node in the present application.

As an embodiment, the first RRC message in the present application is generated in the RRC306.

As an embodiment, the second RRC message in the present application is generated in the RRC306.

As an embodiment, the third RRC message in the present application is generated in the RRC306.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

The first communication device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.

In the transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to a controller/processor 475 at the second communication device 410. The controller/processor 475 implements the functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, a controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., physical layer). Transmit processor 416 performs coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal clusters based on various modulation schemes, e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM). The multi-antenna transmit processor 471 digitally space-precodes the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. A transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying the time domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 to a radio frequency stream and then provides it to a different antenna 420.

In a transmission from the second communication device 410 to the first communication device 450, each receiver 454 receives a signal at the first communication device 450 through its respective antenna 452. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream that is provided to a receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions for the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multicarrier symbol stream after receiving the analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, wherein the reference signal is to be used for channel estimation, and the data signal is subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals that were transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller/processor 459. The controller/processor 459 implements the functions of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In the transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the transmit functions at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations, implementing L2 layer functions for the user and control planes. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, with the multi-antenna transmit processor 457 performing digital multi-antenna spatial precoding, after which the transmit processor 468 modulates the resulting spatial stream into a multi-carrier/single-carrier symbol stream, which is analog precoded/beamformed in the multi-antenna transmit processor 457 before being provided to the different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides it to an antenna 452.

In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the receiving function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, a controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from the controller/processor 475 may be provided to the core network.

As an embodiment, the first communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, the first communication device 450 at least: receiving a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message; wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message; wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As one embodiment, the second communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 at least: transmitting a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain; wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is used to determine whether to apply the third domain of the first RRC message to the second domain of the second RRC message; the fourth domain is two different domains than the first domain.

As one embodiment, the second communication device 410 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain; wherein the second domain comprises a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is used to determine whether to apply the third domain of the first RRC message to the second domain of the second RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is configured to receive a first RRC message; the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a first RRC message.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 is used to send a first RRC message; the antenna 420, the receiver 418, the receive processor 470, and at least one of the controller/processors 475 are configured to receive a first RRC message.

As an embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is configured to receive a second RRC message; the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a second RRC message.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 is used to send a second RRC message; the antenna 420, the receiver 418, the receive processor 470, at least one of the controller/processor 475 is configured to receive a second RRC message.

As an embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 is configured to receive a third RRC message; the antenna 420, the transmitter 418, the transmit processor 416, and at least one of the controller/processors 475 are used to transmit a third RRC message.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 is used to send a third RRC message; the antenna 420, the receiver 418, the receive processor 470, at least one of the controller/processors 475 is configured to receive a third RRC message.

As an embodiment, the first communication device 450 corresponds to the first node in the present application.

As an embodiment, the second communication device 410 corresponds to the second node in the present application.

As an embodiment, the first communication device 450 is a user device.

As an embodiment, the first communication device 450 is a user device supporting a large delay difference.

As an embodiment, the first communication device 450 is a NTN-enabled user device.

As an example, the first communication device 450 is an aircraft device.

For one embodiment, the first communication device 450 is provided with positioning capabilities.

For one embodiment, the first communication device 450 is not capable.

As an embodiment, the first communication device 450 is a TN enabled user device.

As an embodiment, the second communication device 410 is a base station device (gNB/eNB/ng-eNB).

As an embodiment, the second communication device 410 is a base station device supporting a large delay difference.

As an embodiment, the second communication device 410 is a base station device supporting NTN.

As an embodiment, the second communication device 410 is a satellite device.

As an example, the second communication device 410 is a flying platform device.

As an embodiment, the second communication device 410 is a base station device supporting TN.

As an embodiment, the second communication device 410 is a user device.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow diagram according to one embodiment of the present application, as shown in fig. 5. It is specifically noted that the order in this example is not limiting of the order of signal transmission and the order of implementation in this application.

For the followingFirst node U01Receiving a third RRC message in step S5101, the third RRC message including a first domain, at least one second domain, and a third domain; receiving a first RRC message in step S5102, the first RRC message including a first domain, at least one second domain, and a third domain; in step S5103, a second RRC message is received after the first RRC message is received, the second RRC message including a second domain and a fourth domain; determining in step S5104 whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

for the followingSecond node N02Transmitting a third RRC message at step S5201; transmitting a first RRC message in step S5202; in step S5203, transmitting a second RRC message after transmitting the first RRC message;

in embodiment 5, the second domain includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the third RRC message is sent before the first RRC message is sent.

As one embodiment, the first RRC message is sent before the second RRC message is sent.

As one embodiment, the third RRC message is received before the first RRC message is received.

As an embodiment, the first RRC message and the second RRC message correspond to the same IE.

As an embodiment, the first RRC message and the second RRC message correspond to different IEs.

As an embodiment, the first RRC message and the second RRC message correspond to the same domain.

As an embodiment, the first RRC message and the second RRC message correspond to different domains.

As an embodiment, the third domain is absent in the second RRC message.

As an embodiment, the receiving node of the first RRC message saves the value of the third field of the first RRC message.

As an example of this, the acts described in this application include: and (5) maintaining.

As an example of this, the acts described in this application include: and (5) maintenance.

As one embodiment, the act of determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message based on the fourth domain of the second RRC message comprises: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of the first domain of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of the first domain of the first RRC message, not applying the third domain of the first RRC message to the second domain of the second RRC message; the first domain is absent from the second RRC message, or the fourth domain is absent from the first RRC message.

As an embodiment, the first RRC message is CellGroupConfig IE.

As a sub-embodiment of the above embodiment, the first domain is a CellGroupId domain.

As an embodiment, the second RRC message is CellGroupConfig IE.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being the same as the value of the first domain of the first RRC message includes: the cell group configured by the first RRC message is the same as the cell group configured by the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of the first domain of the first RRC message includes: the cell group configured by the first RRC message is different from the cell group configured by the second RRC message.

As a sub-embodiment of the above embodiment, the third domain is a mac-CellGroupConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses a MAC entity configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses physical layer parameters configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses a physical layer configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a spCellConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses a special cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a sCellToAddModList domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses parameters of the secondary cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a sCellToAddModList domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the second RRC message configured cell group uses secondary cells configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the RLC entity configured by the second domain of the second RRC message belongs to the cell group identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the RLC entity configured by the second domain of the second RRC message belongs to a cell group configured by the second RRC message.

As a sub-embodiment of the above embodiment, the logical channel configured by the second domain of the first RRC message and the logical channel configured by the second domain of the second RRC message are associated to the same higher layer entity.

As an subsidiary embodiment of the sub-embodiment described above, said higher layer entity is an RLC entity.

As an subsidiary embodiment of the above sub-embodiment, the higher layer entity is a PDCP entity.

As one embodiment, the behavior processing described in the present application includes: and (5) transmitting.

As one embodiment, the behavior processing described in the present application includes: and (5) receiving.

As one embodiment, the behavior processing described in the present application includes: and (5) transmission.

As an embodiment, the first RRC message includes at least one fourth domain; the act of determining, from the fourth domain of the second RRC message, whether to apply the third domain of the first RRC message to the second domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fourth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from any of the values of the fourth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

As an embodiment, the first RRC message includes M fourth domains, the one fourth domain is one of the M fourth domains, and the M is a positive integer greater than 1.

As a sub-embodiment of the above embodiment, the M is greater than the K.

As a sub-embodiment of the above embodiment, the M is equal to the K.

As a sub-embodiment of the above embodiment, said M is equal to 32.

As a sub-embodiment of the above embodiment, the M is not more than 10000.

As an embodiment, the first RRC message includes a plurality of fourth domains, and the one fourth domain is one of the plurality of fourth domains.

As an embodiment, any one of the fourth domains in the first RRC message belongs to one of the second domains of the first RRC message.

As a sub-embodiment of the above embodiment, a radio bearer served by an RLC entity configured by the second domain of the second RRC message is identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the radio bearers identified by at least one of the fourth domains of the first RRC message are the same as the radio bearers identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the RLC bearer configured by the second domain to which at least one of the fourth domains of the first RRC message belongs is associated with the same PDCP entity as the RLC bearer configured by the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the RLC entity configured by the second domain to which at least one of the fourth domains of the first RRC message belongs is associated with the RLC entity configured by the second RRC message to the same PDCP entity.

As a sub-embodiment of the above embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the first RRC message includes: the logical channel configured by the second domain to which at least one of the fourth domains of the first RRC message belongs is associated with the logical channel configured by the second RRC message to the same upper layer entity.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fourth domains of the first RRC message includes: the radio bearer identified by any fourth domain of the first RRC message is different from the radio bearer identified by the fourth domain of the second RRC message; the cell group to which the RLC entity of the second RRC message configuration belongs is different from the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fourth domains of the first RRC message includes: the cell group to which the RLC entity of the second RRC message configuration belongs is different from the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fourth domains of the first RRC message includes: the radio bearers identified by any fourth domain of the first RRC message are different from the radio bearers identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fourth domains of the first RRC message includes: RLC beacons configured by a second domain to which any fourth domain of the first RRC message belongs are respectively associated with different PDCP entities.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fourth domains of the first RRC message includes: the RLC entity configured by the second domain to which any one of the fourth domains of the first RRC message belongs and the RLC entity configured by the second RRC message are respectively associated to different PDCP entities.

As a sub-embodiment of the above embodiment, the third domain is a mac-CellGroupConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses the MAC entity configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses physical layer parameters configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a physical cellgroupconfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses a physical layer configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a spCellConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the cell group to which the RLC entity configured by the second RRC message belongs uses a special cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a sCellToAddModList domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: and the cell group to which the RLC entity configured by the second RRC message belongs uses parameters of the secondary cell configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a sCellToAddModList domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: and the cell group of the RLC entity configured by the second RRC message uses the secondary cell configured by the third domain of the first RRC message.

As an embodiment, the first RRC message includes at least one fifth domain; the act of determining, from the fourth domain of the second RRC message, whether to apply the third domain of the first RRC message to the second domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of any of the fifth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

As an embodiment, the first RRC message includes N fourth domains, the one fourth domain is one of the N fourth domains, and the N is a positive integer greater than 1.

As a sub-embodiment of the above embodiment, the N is greater than the K.

As a sub-embodiment of the above embodiment, the N is equal to the K.

As a sub-embodiment of the above embodiment, the N is equal to 32.

As a sub-embodiment of the above embodiment, the N is not more than 10000.

As an embodiment, the first RRC message includes a plurality of fifth domains, and the one fifth domain is one of the plurality of fifth domains.

As an embodiment, any of the fifth domains in the first RRC message belongs to one of the second domains of the first RRC message.

As an embodiment, the third domain in the first RRC message belongs to one of the second domains of the first RRC message.

As an embodiment, the second RRC message includes the fifth domain.

As an embodiment, the fifth domain of the second RRC message belongs to the second domain of the second RRC message.

As an embodiment, the second RRC message is an RLC-beaderconfig domain.

As a sub-embodiment of the above embodiment, the fifth domain is absent from the second RRC message.

As a sub-embodiment of the above embodiment, the fifth domain exists in the second RRC message.

As a sub-embodiment of the above embodiment, the third domain is a logicalChannelIdentity domain.

As a sub-embodiment of the above embodiment, the third domain is a serverradiobearer domain.

As a sub-embodiment of the above embodiment, the third domain is a reestablishRLC domain.

As a sub-embodiment of the above embodiment, the third domain is a rl-Config domain.

As a sub-embodiment of the above embodiment, the third domain is a mac-LogicalChannelConfig domain.

As a sub-embodiment of the above embodiment, the third domain is the rl-Config-v 1610 domain.

As a sub-embodiment of the above embodiment, the third domain is an associable logicalchannelidentity domain.

As a sub-embodiment of the above embodiment, the third domain is an associpedservdiradiobearer domain.

As a sub-embodiment of the above embodiment, the third domain includes at least one of a logicalChannelIdentity domain, a servedobeeser domain, a resestishrlc domain, a rl-Config-v 1610 domain, a mac-LogicalChannelConfig domain, an associtachanneiidentity domain, or an associtdservedobeeser.

As an subsidiary embodiment of the above sub-embodiment, the value of the fourth field of the second RRC message is the same as the value of the fifth field of the second RRC message.

As an subsidiary embodiment of the above sub-embodiment, the value of the fourth field of the second RRC message is different from the value of the fifth field of the second RRC message.

As a sub-embodiment of the above embodiment, the value range of the fourth domain is the same as the value range of the fifth domain.

As a sub-embodiment of the above embodiment, the value range of the fourth domain is different from the value range of the fifth domain.

As a sub-embodiment of the above embodiment, the logical channel identified by the fourth domain of the second RRC message is associated with the same RLC entity as the logical channel configured by the second RRC message.

As a sub-embodiment of the above embodiment, the logical channel configured by the second RRC message is identified by the fifth domain of the second RRC message.

As an embodiment, the first RRC message is CellGroupConfig IE, the second domain is RLC-beaderconfig domain, and the fifth domain is logicalChannelIdentity domain.

As a sub-embodiment of the above embodiment, the second RRC message is an RLC-beaderconfig domain.

As a sub-embodiment of the above embodiment, the second RRC message is an associable rlc-bearrerconfig domain

As a sub-embodiment of the above embodiment, the RLC entity configured by the second RRC message is identified by the fourth domain in the second RRC message.

As a sub-embodiment of the above embodiment, the second RRC message is used to configure one logical channel.

As a sub-embodiment of the above embodiment, the logical channel configured by the second RRC message is identified by the fourth domain in the second RRC message.

As a sub-embodiment of the above embodiment, the logical channel configured by the second RRC message is identified by the fifth domain in the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message includes: the cell group to which the RLC entity of the second RRC message configuration belongs is the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message includes: the logic channel configured by the second domain to which at least one of the fifth domains of the first RRC message belongs is associated with the logic channel configured by the second RRC message to the same RLC entity; the cell group to which the RLC entity of the second RRC message configuration belongs is the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message includes: the logical channel configured by the second domain to which at least one of the fifth domains of the first RRC message belongs is associated with the logical channel configured by the second RRC message to the same upper layer entity.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message includes: the RLC bearer identified by at least one of the fifth domains of the first RRC message is the same as the RLC bearer identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fifth domains of the first RRC message includes: the cell group to which the RLC entity of the second RRC message configuration belongs is different from the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fifth domains of the first RRC message includes: the logic channel configured by the second domain to which any of the fifth domains belongs of the first RRC message is associated with a different RLC entity from the logic channel configured by the second RRC message; the cell group to which the RLC entity of the second RRC message configuration belongs is different from the cell group of the first RRC message configuration.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fifth domains of the first RRC message includes: the logical channel configured by the second domain to which any one of the fifth domains belongs in the first RRC message is associated with a different RLC entity from the logical channel configured by the second RRC message.

As a sub-embodiment of the above embodiment, the value of the fourth domain of the second RRC message being different from the value of any of the fifth domains of the first RRC message includes: the RLC bearer identified by any of the fifth domains of the first RRC message is different from the RLC bearer identified by the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the phrase the RLC entity of the second RRC message configuration includes: and the second RRC message configures a logic channel.

As a sub-embodiment of the above embodiment, the phrase the RLC entity of the second RRC message configuration includes: and the second RRC message configures a logical channel of the RLC entity in the MAC.

As a sub-embodiment of the above embodiment, the phrase the RLC entity of the second RRC message configuration includes: the PDCP entity configured by the second RRC message.

As a sub-embodiment of the above embodiment, the phrase the RLC entity of the second RRC message configuration includes: and the radio bearer configured by the second RRC message.

As a sub-embodiment of the above embodiment, the phrase the RLC entity of the second RRC message configuration includes: and the radio bearer served by the RLC entity configured by the second RRC message.

As a sub-embodiment of the above embodiment, the third domain is a rl-Config domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the RLC entity configured by the second RRC message uses the RLC mode configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a mac-LogicalChannelConfig domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the RLC entity configured by the second RRC message uses logical channel parameters configured by the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain is a reestablishRLC domain; the act of applying the third domain of the first RRC message to the second domain of the second RRC message includes: the RLC entity of the second RRC message configuration uses the value of the third domain of the first RRC message.

As a sub-embodiment of the above embodiment, the third domain of the first RRC message belongs to a second domain of the first RRC message, and a value of the fifth domain of the second domain of the first RRC message is the same as a value of the fourth domain of the second RRC message.

As a sub-embodiment of the above embodiment, the act of applying the third domain of the third RRC message to the second domain of the second RRC message includes:

As a sub-embodiment of the above embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message includes: the third domain of the first RRC message is not applied to the RLC entity configured by the second RRC message.

As an embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message comprises: applying a value of the second domain of the second RRC message.

As an embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message comprises: the value of the third field of the first RRC message is not applied.

As an embodiment, the act of not applying the third domain of the first RRC message to the second domain of the second RRC message comprises: the third domain of the third RRC message is applied to the second domain of the second RRC message.

As one embodiment, the act of applying the third domain of the third RRC message to the second domain of the second RRC message comprises: the current value of the third field is used.

As one embodiment, the act of applying the third domain of the third RRC message to the second domain of the second RRC message comprises: the previously configured values of the third domain are used.

As one embodiment, the act of applying the third domain of the third RRC message to the second domain of the second RRC message comprises: a value of the third field of a third RRC message.

As an embodiment, the current value of the third domain is a value of the third domain of the third RRC message.

As an embodiment, the previously configured value of the third domain is a value of the third domain of the third RRC message.

As an embodiment, the receiving node of the third RRC message saves a value of the third domain of the third RRC message.

As an embodiment, the third RRC message is used to configure a cell group, and the cell group configured by the third RRC message is identified by the first domain of the third RRC message.

As an embodiment, the third RRC message includes K second domains, the one second domain is one of the K1 second domains, and the K1 is a positive integer greater than 1.

As a sub-embodiment of the above embodiment, the K1 is equal to 32.

As a sub-embodiment of the above embodiment, the K1 is not more than 10000.

As an embodiment, the third RRC message includes a plurality of second domains, and the one second domain is one of the plurality of second domains.

As an embodiment, the third RRC message includes at least one fourth domain.

As a sub-embodiment of the above embodiment, any fourth domain in the third RRC message belongs to a second domain of the third RRC message.

As an embodiment, the third RRC message includes M1 fourth domains, the one fourth domain is one of the M1 fourth domains, and the M1 is a positive integer greater than 1.

As a sub-embodiment of the above embodiment, the M is greater than the K1.

As a sub-embodiment of the above embodiment, said M is equal to said K1.

As a sub-embodiment of the above embodiment, said M is equal to 32.

As a sub-embodiment of the above embodiment, the M is not more than 10000.

As an embodiment, the third RRC message includes a plurality of fourth domains, and the one fourth domain is one of the plurality of fourth domains.

As an embodiment, the value of the fourth field of the second RRC message is the same as the value of the first field of the third RRC message.

As an embodiment, the value of the fourth field of the second RRC message is the same as the value of at least one of the fourth fields of the third RRC message.

As an embodiment, the third RRC message is CellGroupConfig IE, the first domain is a CellGroupId domain, and the second domain is an RLC-beaererconfig domain.

As an embodiment, the scheduling signaling of the third RRC message on the air interface is identified by a non-unicast RNTI.

As an embodiment, the scheduling signaling of the third RRC message on the air interface is identified by a unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a non-unicast RNTI includes: and determining whether the scheduling signaling of the third RRC message on an air interface exists or not according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a non-unicast RNTI includes: and determining the time-frequency resource occupied by the third RRC message transmission according to the non-unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a non-unicast RNTI includes: the non-unicast RNTI is used for CRC scrambling of scheduling signaling of the third RRC message over the air interface.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a unicast RNTI includes: and determining whether the scheduling signaling of the third RRC message on an air interface exists or not according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a unicast RNTI includes: and determining the time-frequency resource occupied by the third RRC message transmission according to the unicast RNTI.

As an embodiment, the phrase that the scheduling signaling of the third RRC message over the air interface is identified by a unicast RNTI includes: the unicast RNTI is used for CRC scrambling of scheduling signaling of the third RRC message over the air interface.

As an example, the dashed box F5.1 is optional.

As a sub-embodiment of this embodiment, the dashed box F5.1 exists.

As a sub-embodiment of this embodiment, the dashed box F5.1 does not exist.

Example 6

Embodiment 6 illustrates a wireless signal transmission flow diagram according to yet another embodiment of the present application, as shown in fig. 5. It is specifically noted that the order in this example is not limiting of the order of signal transmission and the order of implementation in this application.

For the followingFirst node U01Receiving a third RRC message in step S6101, the third RRC message including a first domain, at least one second domain, and a third domain; transmitting a sixth RRC message in step S6102; receiving a first RRC message in step S6103, the first RRC message including a first domain, at least one second domain, and a third domain; transmitting a fourth RRC message in step S6104; in step S6105, a second RRC message is received after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message in step S6106; transmitting a fifth RRC message in step S6107;

For the followingSecond node N02Transmitting a third RRC message in step S6201; receiving a sixth RRC message in step S6202; transmitting a first RRC message in step S6203; receiving a fourth RRC message in step S6204; in step S6205, transmitting a second RRC message after transmitting the first RRC message; receiving a fifth RRC message in step S6206;

in embodiment 6, the second domain includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the fourth RRC message is used to determine successful completion of the first RRC message.

As an embodiment, the fourth RRC message is sent in response to receiving the first RRC message.

As an embodiment, the fourth RRC message indicates successful completion of the first RRC message.

As an embodiment, the fourth RRC message includes all or part of an rrcrecon configuration complete message.

As an embodiment, the fourth RRC message includes all or part of an RRCConnectionReconfigurationComplete message.

As an embodiment, the fourth RRC Message includes an RRC (Radio Resource Control ) Message (Message).

As an embodiment, the fourth RRC message includes all or part of an IE (Information Element ) in one RRC message.

For one embodiment, the fourth RRC message includes all or part of the Field (Field) in one IE in one RRC message.

As an embodiment, the fifth RRC message is used to determine successful completion of the second RRC message.

As an embodiment, the fifth RRC message is sent in response to receiving the second RRC message.

As an embodiment, the fifth RRC message includes all or part of an rrcrecon configuration complete message.

As an embodiment, the fifth RRC message includes all or part of an RRCConnectionReconfigurationComplete message.

As an embodiment, the fifth RRC Message includes an RRC (Radio Resource Control ) Message (Message).

As an embodiment, the fifth RRC message includes all or part of an IE (Information Element ) in one RRC message.

For one embodiment, the fifth RRC message includes all or part of the Field (Field) in one IE in one RRC message.

As an embodiment, the sixth RRC message is used to determine successful completion of the third RRC message.

As an embodiment, the sixth RRC message is sent in response to receiving the third RRC message.

As an embodiment, the sixth RRC message includes all or part of an rrcrecon configuration complete message.

As an embodiment, the sixth RRC message includes all or part of an RRCConnectionReconfigurationComplete message.

As an embodiment, the sixth RRC Message includes an RRC (Radio Resource Control ) Message (Message).

As an embodiment, the sixth RRC message includes all or part of an IE (Information Element ) in one RRC message.

For one embodiment, the sixth RRC message includes all or part of the Field (Field) in one IE in one RRC message.

As one embodiment, the phrase successful completion in this application includes: successfully performs.

As one embodiment, the phrase successful completion in this application includes: successful configuration.

As one embodiment, the phrase successful completion in this application includes: the configuration is completed.

As an example, the dashed box F6.1 is optional.

As a sub-embodiment of this embodiment, the dashed box F6.1 exists.

As a sub-embodiment of this embodiment, the dashed box F6.1 does not exist.

As an example, the dashed box F6.2 is optional.

As a sub-embodiment of this embodiment, the dashed box F6.2 exists.

As a sub-embodiment of this embodiment, the dashed box F6.2 does not exist.

As a sub-embodiment of this embodiment, the dashed box F6.2 is absent when the dashed box F6.1 is absent.

As an example, the dashed box F6.3 is optional.

As a sub-embodiment of this embodiment, the dashed box F6.3 exists.

As a sub-embodiment of this embodiment, the dashed box F6.3 does not exist.

As an example, the dashed box F6.4 is optional.

As a sub-embodiment of this embodiment, the dashed box F6.4 exists.

As a sub-embodiment of this embodiment, the dashed box F6.4 does not exist.

Example 7

Embodiment 7 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the present application; as shown in fig. 7. In fig. 7, the processing means 700 in the first node comprises a first receiver 701 and a first transmitter 702.

A first receiver 701 receiving a first RRC message, the first RRC message including a first domain, at least one second domain, and a third domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

in embodiment 7, the second domain includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain is two different domains than the first domain.

As an embodiment, the second RRC message is CellGroupConfig IE.

As an embodiment, the second RRC message is an RLC-beaderconfig domain.

The first transmitter 702 transmits a fourth RRC message.

As an embodiment, the fourth RRC message is used to confirm successful completion of the first RRC message.

The first transmitter 702 transmits a fifth RRC message.

As an embodiment, the fifth RRC message is used to confirm successful completion of the second RRC message.

The first transmitter 702 transmits a sixth RRC message.

As an example, the first receiver 701 includes an antenna 452, a receiver 454, a multi-antenna receive processor 458, a receive processor 456, a controller/processor 457, a memory 460, and a data source 467 of fig. 4 of the present application.

As an embodiment, the first receiver 701 includes an antenna 452, a receiver 454, a multi-antenna receiving processor 458, and a receiving processor 456 in fig. 4 of the present application.

As an embodiment, the first receiver 701 includes an antenna 452, a receiver 454, and a receiving processor 456 in fig. 4 of the present application.

As an example, the first transmitter 702 includes the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an example, the first transmitter 702 includes an antenna 452, a transmitter 454, a multi-antenna transmit processor 457, and a transmit processor 468 of fig. 4 of the present application.

As an example, the first transmitter 702 includes an antenna 452, a transmitter 454, and a transmission processor 468 of fig. 4 of the present application.

Example 8

Embodiment 8 illustrates a block diagram of a processing apparatus for a second node according to one embodiment of the present application; as shown in fig. 8. In fig. 8, the processing means 800 in the second node comprises a second transmitter 801 and a second receiver 802.

A second transmitter 801 transmitting a first RRC message including a first domain, at least one second domain, and a third domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

in embodiment 8, the second domain includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is used to determine whether to apply the third domain of the first RRC message to the second domain of the second RRC message; the fourth domain is two different domains than the first domain.

The second receiver 802 receives the fourth RRC message.

The second receiver 802 receives the fifth RRC message.

The second receiver 802 receives the sixth RRC message.

As an example, the second transmitter 801 includes the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second transmitter 801 includes the antenna 420, the transmitter 418, the multi-antenna transmission processor 471, and the transmission processor 416 shown in fig. 4 of the present application.

As an example, the second transmitter 801 includes the antenna 420, the transmitter 418, and the transmitting processor 416 of fig. 4 of the present application.

The second receiver 802 includes, as one example, the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 802 includes the antenna 420, the receiver 418, the multi-antenna receiving processor 472, and the receiving processor 470 of fig. 4 of the present application.

As an example, the second receiver 802 includes the antenna 420, the receiver 418, and the receiving processor 470 of fig. 4 of the present application.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the application is not limited to any specific combination of software and hardware. User equipment, terminals and UEs in the present application include, but are not limited to, unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control airplanes, aircraft, mini-planes, mobile phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, internet of things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication ) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low cost mobile phones, low cost tablet computers, and other wireless communication devices. The base station or system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point, transmitting and receiving node), and other wireless communication devices.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims

1. A first node for wireless communication, comprising:

a first receiver that receives a first RRC message, the first RRC message including a first domain, a third domain, and at least one second domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

wherein said second domain of said first RRC message includes a logical channel identity; the second domain of the second RRC message includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is two different domains than the first domain of the first RRC message.

2. The first node of claim 1, wherein the determining from the fourth domain of the second RRC message whether to apply the third domain of the first RRC message to the second domain of the second RRC message comprises: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of the first domain of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of the first domain of the first RRC message, not applying the third domain of the first RRC message to the second domain of the second RRC message; the first domain is absent from the second RRC message, or the fourth domain is absent from the first RRC message.

3. The first node of claim 1, wherein the first RRC message includes at least one fourth domain; the determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fourth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from any of the values of the fourth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

4. The first node of claim 1, wherein the first RRC message includes at least one fifth domain; the determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of any of the fifth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

5. The first node according to any of claims 1 to 4, comprising:

the second RRC message does not include a domain having the same name as the third domain included in the first RRC message.

6. The first node according to any of claims 1 to 4, comprising:

the second RRC message does not include a domain having the same name as the first domain included in the first RRC message.

7. The first node of claim 5, comprising:

8. A second node for wireless communication, comprising:

a second transmitter that transmits a first RRC message, the first RRC message including a first domain, a third domain, and at least one second domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain;

wherein said second domain of said first RRC message includes a logical channel identity; the second domain of the second RRC message includes a logical channel identity; the first RRC message is used to configure a cell group, and the cell group configured by the first RRC message is identified by the first domain of the first RRC message; the fourth domain of the second RRC message is used to determine whether to apply the third domain of the first RRC message to the second domain of the second RRC message; the fourth domain of the second RRC message is two different domains than the first domain of the first RRC message.

9. A method in a first node for wireless communication, comprising:

receiving a first RRC message, the first RRC message including a first domain, a third domain, and at least one second domain; receiving a second RRC message after receiving the first RRC message, the second RRC message including a second domain and a fourth domain; determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message;

10. The method in a first node according to claim 9,

the determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of the first domain of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of the first domain of the first RRC message, not applying the third domain of the first RRC message to the second domain of the second RRC message; the first domain is absent from the second RRC message, or the fourth domain is absent from the first RRC message.

11. The method in a first node according to claim 9,

the first RRC message includes at least one fourth domain; the determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fourth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from any of the values of the fourth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

12. The method in a first node according to claim 9,

the first RRC message includes at least one fifth domain; the determining whether to apply the third domain of the first RRC message to the second domain of the second RRC message according to the fourth domain of the second RRC message includes: applying the third domain of the first RRC message to the second domain of the second RRC message if the value of the fourth domain of the second RRC message is the same as the value of at least one of the fifth domains of the first RRC message; if the value of the fourth domain of the second RRC message is different from the value of any of the fifth domains of the first RRC message, the third domain of the first RRC message is not applied to the second domain of the second RRC message.

13. The method in a first node according to any of the claims 9 to 12, characterized in,

14. The method in a first node according to any of the claims 9 to 12, characterized in,

15. The method in a first node according to claim 13,

16. A method in a second node for wireless communication, comprising:

transmitting a first RRC message, the first RRC message including a first domain, a third domain, and at least one second domain; transmitting a second RRC message after transmitting the first RRC message, the second RRC message including a second domain and a fourth domain;