A communication method, communication device, communication system, and computer-readable storage media.

BR112019018044B1Active Publication Date: 2026-09-08HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
BR112019018044
Authority / Receiving Office
BR · BR
Patent Type
Patents
Current Assignee / Owner
Publication Date
2026-09-08

Smart Images

  • Figure 00000070_0000
    Figure 00000070_0000
  • Figure 00000070_0001
    Figure 00000070_0001
  • Figure 00000071_0000
    Figure 00000071_0000
Patent Text Reader

Abstract

This application discloses a method of communication and a communications device. The method includes: sending, by a distributed unit, a connection setup request message to a central unit; and receiving, by the distributed unit, a connection setup reply message from the central unit, wherein the connection setup request message or the connection setup reply message includes network slice information supported by the distributed unit. The corresponding device is also disclosed. In this application, the network slice information supported by the distributed unit is exchanged between the distributed unit and the central unit using a connection setup process, so that a network slice-based service in a distributed unit and central unit architecture can be implemented.
Need to check novelty before this filing date? Find Prior Art

Description

1 / 64 “COMMUNICATION METHOD, COMMUNICATION DEVICE, COMMUNICATION SYSTEM AND COMPUTER-READABLE STORAGE MEDIA” TECHNICAL FIELD

[0001] This application relates to the field of communications technologies, and in particular, to a method of communication and a communications apparatus. FUNDAMENTALS

[0002] A network slicing concept is introduced in a next-generation mobile communications network technology (e.g., 5th generation mobile communications (5G)) to serve different tenants and differentiated services through the use of a customized network. A core network (CN) device, a radio access network (RAN) device, and a terminal device can each support a plurality of network slices. Because RAN devices from different vendors differ in function, or because different RAN devices have different capabilities to support network slicing due to operator policies, RAN devices also support different services based on network slice within the coverage areas of the RAN devices.

[0003] In next-generation mobile communications network technology, a RAN device architecture is sliced. Specifically, a RAN device includes a central unit (CU) and one or more distributed units (DU). How to implement a network slice-based service in a CU-DU architecture is a problem that deserves consideration. SUMMARY

[0004] This application provides a communication method and a communications device for implementing a network slice-based service in a CU-DU architecture.

[0005] According to one aspect, a communication method is provided, and the method includes: sending, by a distributed unit, a connection configuration request message to a central unit; and receiving, by the distributed unit, a configuration response message. Petition 870260050283, dated 05 / 26 / 2026, page 19 / 104 2 / 64 connection from the central unit, where the connection configuration request message or the connection configuration response message includes network slice information supported by the distributed unit.

[0006] In this project, network slice information supported by the distributed unit is exchanged between the distributed unit and the central unit using a connection configuration process, so that the distributed unit and the central unit provide a network slice-based service to an end device.

[0007] In a possible project, the connection configuration response message additionally includes information on the network slice supported by the central unit.

[0008] In this project, the central unit notifies the distributed unit of a network slice supported by the central unit, and the distributed unit can provide the terminal device only with a network slice-based service that is supported by both the distributed unit and the central unit.

[0009] In another possible project, the method additionally includes: sending, by the distributed unit, a configuration update message to the central unit, where the configuration update message includes updated information on the network slice supported by the distributed unit.

[0010] In this project, when a network slice supported by the distributed unit is updated, the distributed unit needs to update the network slice information to the central unit.

[0011] In yet another possible design, the network slice information supported by the distributed unit includes at least one or a combination of the following: network slice indication information supported by at least one cell of the distributed unit; a cell identifier of at least one cell of the distributed unit and network slice indication information supported by each of the at least one cell; or an identifier of a tracking area or a recording area that corresponds to at least one cell of the distributed unit and network slice indication information supported by each tracking area or each recording area in the tracking area or recording area that corresponds to at least one cell. Petition 870260050283, dated 05 / 26 / 2026, page 20 / 104 3 / 64

[0012] In this project, a plurality of ways of representing network slice information is provided. Certainly, this request is not limited to these various forms of representation.

[0013] Correspondingly, another aspect of this application further provides a communications device, which can implement the aforementioned communication method. The communications device has a function of implementing the behavior of the distributed unit in the aforementioned method. The function can be implemented by using hardware, or it can be implemented by using software that executes corresponding hardware. The hardware or software includes one or more modules that correspond to the aforementioned function.

[0014] In a possible project, the communications apparatus includes: a transmitting unit, configured to send a connection configuration request message to a central unit; and a receiving unit, configured to receive a connection configuration reply message from the central unit, wherein the connection configuration request message or the connection configuration reply message includes network slice information supported by the distributed unit.

[0015] In a possible project, the connection configuration response message additionally includes information on the network slice supported by the central unit.

[0016] In a possible project, the transmitting unit is additionally configured to send a configuration update message to the central unit, where the configuration update message includes updated information on the network slice supported by the distributed unit.

[0017] In a possible project, the network slice information supported by the distributed unit includes at least one or a combination of the following: network slice indication information supported by at least one cell of the distributed unit; a cell identifier of at least one cell of the distributed unit and network slice indication information supported by each of the at least one cell; or an identifier of a tracking area or a recording area that corresponds to the at least one cell. Petition 870260050283, dated 05 / 26 / 2026, page 21 / 104 4 / 64 minus one cell of the distributed unit and indication information of the network slice supported by each tracking area or each registration area in the tracking area or registration area that corresponds to at least one cell.

[0018] When the distributed unit is a chip, the receiving unit can be an input unit such as an input circuit or a communications interface, and the transmitting unit can be an output unit such as an output circuit or a communications interface. When the communications apparatus is a device, the receiving unit can be a receiving device (or can be referred to as a receiver), and the transmitting unit can be a transmitting device (or can be referred to as a transmitter).

[0019] In another possible design, the communications apparatus includes a receiver, a transmitter, a memory, and a processor. The memory stores a set of program code, and the processor is configured to invoke the program code stored in memory to perform the following operations: control the transmitter to send a connection configuration request message to a central unit; and control the receiver to receive a connection configuration response message from the central unit, wherein the connection configuration request message or the connection configuration response message includes network slice information supported by the distributed unit.

[0020] Based on the same invention concept, regarding a problem-solving principle and beneficial effects of the device, refer to the aforementioned possible method implementations and beneficial effects brought about by the distributed unit. Therefore, for the device implementation, refer to the method implementation. Repeated parts are not described again.

[0021] According to yet another aspect, a communication method is provided, and the method includes: receiving, by a central unit, a connection configuration request message from a distributed unit; and sending, by the central unit, a connection configuration response message to the distributed unit, wherein the connection configuration request message or the response message Petition 870260050283, dated 05 / 26 / 2026, page 22 / 104 5 / 64 connection configuration includes network slice information supported by the distributed unit.

[0022] In this project, the distributed unit and the central unit obtain, through the use of a connection configuration process, the network slice information supported by the distributed unit, so that the distributed unit and the central unit subsequently provide a network slice-based service to an end device.

[0023] In a possible project, the connection configuration response message additionally includes information on the network slice supported by the central unit.

[0024] In this project, the central unit notifies the distributed unit of a network slice supported by the central unit, and the distributed unit can only support a network slice that is supported by both the distributed unit and the central unit.

[0025] In another possible project, the method additionally includes: receiving, by the central unit, a configuration update message from the distributed unit, where the configuration update message includes updated information on the network slice supported by the distributed unit.

[0026] In this project, when a network slice supported by the distributed unit is updated, the distributed unit needs to update the network slice information to the central unit.

[0027] In yet another possible project, the method additionally includes: sending, from the central unit, a configuration update message to the distributed unit, where the configuration update message includes updated information on the network slice supported by the central unit.

[0028] In this project, when a network slice supported by the central unit is updated, the central unit needs to update the network slice information for the distributed unit.

[0029] In yet another possible design, the configuration update message or the connection configuration response message additionally includes network slice configuration information. The network slice configuration information includes at least one of Petition 870260050283, dated 05 / 26 / 2026, page 23 / 104 6 / 64 the following configuration information: Layer 1 protocol stack configuration information, Layer 2 protocol stack configuration information, physical resource information, frequency band information corresponding to a network slice, frequency information corresponding to a network slice, or status information supported by a network slice.

[0030] In this project, since the network slice information from the distributed unit is configured for the central unit, the central unit can additionally send the network slice configuration information when sending the network slice information supported by the central unit to the distributed unit, so that the distributed unit can configure a network slice based on the configuration information, to provide a network slice-based service to the terminal device.

[0031] Correspondingly, yet another aspect of this application additionally provides a communications apparatus, which can implement the aforementioned communication method. The communications apparatus has a function of implementing the behavior of the central unit in the aforementioned method. The function can be implemented by using hardware, or it can be implemented by using software that executes corresponding hardware. The hardware or software includes one or more modules that correspond to the aforementioned function.

[0032] In a possible design, the communications apparatus includes: a receiving unit, configured to receive a connection configuration request message from a distributed unit; and a transmitting unit, configured to send a connection configuration reply message to the distributed unit, wherein the connection configuration request message or the connection configuration reply message includes network slice information supported by the distributed unit.

[0033] In a possible project, the connection configuration response message additionally includes information on the network slice supported by the central unit.

[0034] In a possible project, the transmitter unit is additionally configured to send an update message of Petition 870260050283, dated 05 / 26 / 2026, page 24 / 104 7 / 64 configuration for the distributed unit, where the configuration update message includes updated information on the network slice supported by the central unit.

[0035] In a possible project, the configuration update message additionally includes network slice configuration information. The network slice configuration information or the connection configuration response message includes at least one of the following configuration information: Layer 1 protocol stack configuration information, Layer 2 protocol stack configuration information, physical resource information, frequency band information corresponding to a network slice, frequency information corresponding to a network slice, or status information supported by a network slice.

[0036] When the communications device is a chip, the receiving unit may be an input unit such as an input circuit or a communications interface, and the transmitting unit may be an output unit such as an output circuit or a communications interface. When the communications device is a device, the receiving unit may be a receiving device (or may be referred to as a receiver), and the transmitting unit may be a transmitting device (or may be referred to as a transmitter).

[0037] In another possible design, the communications apparatus includes a receiver, a transmitter, a memory, and a processor. The memory stores a set of program code, and the processor is configured to invoke the program code stored in memory to perform the following operations: control the receiver to receive a connection configuration request message from a distributed unit; and control the transmitter to send a connection configuration reply message to the distributed unit, wherein the connection configuration request message or the connection configuration reply message includes network slice information supported by the distributed unit.

[0038] Based on the same invention concept, regarding a problem-solving principle and beneficial effects of the device, make reference to the aforementioned possible implementations of the method and effects. Petition 870260050283, dated 05 / 26 / 2026, page 25 / 104 8 / 64 benefits derived from the central unit. Therefore, for the implementation of the device, refer to the implementation of the method. Repeated parts are not described.

[0039] According to yet another aspect, a communication method is provided, and the method includes: sending, by a central unit, a first message to a distributed unit, wherein the first message includes information indicating the network slice that corresponds to a session, a carrier, or a flow; and receiving, by the central unit, a reply message from the distributed unit.

[0040] In this project, since different network slices have different Layer 1 or Layer 2 configurations on one side of the RAN, different sessions may correspond to different network slices. During session setup or modification, the central unit notifies the distributed unit of network slice indication information that corresponds to a session, carrier, or flow to be established or modified, so that the distributed unit establishes or modifies the session, carrier, or flow on an indicated network slice. Therefore, the distributed unit can accurately select a network slice, and can configure, based on network slice information that corresponds to the session, an L1 / L2 parameter that corresponds to the network slice for an endpoint device, so that sessions belonging to different network slices meet a specific requirement for QoS.

[0041] In a possible project, the method additionally includes: sending, by the central unit, a radio resource control message to the terminal device by the use of the distributed unit, wherein the radio resource control message includes an identifier of a session, carrier, or flow that is successfully established.

[0042] In this project, the terminal device obtains the session identifier, bearer, or flow that is successfully established, to conduct a session with a network device.

[0043] In another possible design, the method additionally includes: sending, by the central unit, a path switching request message to a network core device, wherein the path switching request message includes an identifier of a session successfully established by the central unit or the distributed unit, and / or Petition 870260050283, dated 05 / 26 / 2026, page 26 / 104 9 / 64 is a flow identifier that matches the session identifier and is successfully established by the central unit or the distributed unit.

[0044] In this project, due to the mobility of the terminal device, the terminal device moves from an original central server unit or original distributed server unit to a new central unit or distributed unit. In this scenario, the central unit notifies the network core device of a session or flow that requires path switching, so that the network core device can send downlink data and receive uplink data based on a switched path.

[0045] In yet another possible design, the first message or the reply message additionally includes carrier duplication indication information. In this design, the terminal device can transmit the same data over two paths, thereby increasing the reliability of data transmission.

[0046] In yet another possible design, the first message additionally includes DU UE-AMBR indication information, and the DU UE-AMBR indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0047] In this project, the terminal device can perform data transmission with at least two distributed units that correspond to the same central unit, and the terminal device can transmit different data to different distributed units. The DU UEAMBR indication information is from the first message, so that the data transmission rate from each distributed unit to the terminal device does not exceed the maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0048] In yet another possible design, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack.

[0049] In this project, the central unit adds information to the first message to be sent to the distributed unit, Petition 870260050283, dated 05 / 26 / 2026, page 27 / 104 10 / 64 configuration of the source network device for a protocol stack that corresponds to a terminal device carrier, so that the distributed unit can perform differentiated configuration on protocol stacks, thereby simplifying distributed unit operations.

[0050] In yet another possible design, the source network device includes any one of the following: the central unit, a source base station, a source central unit, and the network core device.

[0051] Correspondingly, yet another aspect of this application additionally provides a communications apparatus, which can implement the aforementioned communication method. The communications apparatus has a function of implementing the behavior of the central unit in the aforementioned method. The function can be implemented by using hardware, or it can be implemented by using software that executes corresponding hardware. The hardware or software includes one or more modules that correspond to the aforementioned function.

[0052] In a possible design, the communications apparatus includes: a transmitting unit, configured to send an initial message to a distributed unit, wherein the initial message includes network slice indication information corresponding to a session, a carrier, or a stream; and a receiving unit, configured to receive a reply message from the distributed unit.

[0053] In a possible design, the transmitting unit is additionally configured to send a radio resource control message to a terminal device by use of the distributed unit, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established.

[0054] In a possible design, the transmitting unit is additionally configured to send a path switching request message to a network core device, wherein the path switching request message includes an identifier of a session successfully established by the central unit or the distributed unit, and / or an identifier of a flow that corresponds to the session identifier and that is successfully established by the central unit or the distributed unit. Petition 870260050283, dated 05 / 26 / 2026, page 28 / 104 11 / 64

[0055] In a possible project, the first message or the reply message additionally includes carrier duplication indication information.

[0056] In a possible design, the first message additionally includes UE-AMBR DU indication information, and the UE-AMBR DU indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0057] In a possible design, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack.

[0058] In a possible project, the source network device includes any of the following: the central unit, a source base station, a source central unit, and the network core device.

[0059] When the communications device is a chip, the receiving unit may be an input unit such as an input circuit or a communications interface, and the transmitting unit may be an output unit such as an output circuit or a communications interface. When the communications device is a device, the receiving unit may be a receiving device (or may be referred to as a receiver), and the transmitting unit may be a transmitting device (or may be referred to as a transmitter).

[0060] In another possible design, the central unit includes a receiver, a transmitter, a memory, and a processor. The memory stores a set of program code, and the processor is configured to invoke the program code stored in memory to perform the following operations: send an initial message to a distributed unit using the transmitter, where the initial message includes network slice indication information corresponding to a session, a carrier, or a stream; and receive a response message from the distributed unit using the receiver.

[0061] Based on the same invention concept, regarding a problem-solving principle and beneficial effects of the device, make Petition 870260050283, dated 05 / 26 / 2026, page 29 / 104 12 / 64 refers to the aforementioned possible method implementations and beneficial effects brought about by the central unit. Therefore, for the implementation of the device, refer to the method implementation. Repeated parts are not described.

[0062] According to yet another aspect, a communication method is provided, and the method includes: receiving, by a distributed unit, a first message from a central unit, wherein the first message includes information indicating the network slice that corresponds to a session, a carrier, or a flow; and sending, by the distributed unit, a reply message to the central unit.

[0063] In this project, since different network slices have different Layer 1 or Layer 2 configurations on one side of the RAN, different sessions can correspond to different network slices. During session setup or modification, the central unit notifies the distributed unit of network slice indication information that corresponds to a session, carrier, or flow to be established or modified, so that the distributed unit establishes or modifies the session, carrier, or flow on an indicated network slice. Therefore, the distributed unit can accurately select a network slice, and can configure, based on network slice information that corresponds to the session, an L1 / L2 parameter that corresponds to the network slice for an endpoint device. Therefore, sessions belonging to different network slices meet a specific requirement for QoS.

[0064] In a possible project, the method additionally includes: sending, by the distributed unit, a radio resource control message from the central unit to the terminal device, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established.

[0065] In this project, the terminal device obtains the session identifier, bearer, or flow that is successfully established, to conduct a session with a network device.

[0066] In another possible project, after a distributed unit receives an initial message from a central unit, the method additionally includes: determining, by the distributed unit, whether or not the distributed unit supports a network slice that corresponds to Petition 870260050283, dated 05 / 26 / 2026, page 30 / 104 13 / 64 network slice indication information.

[0067] In this project, the distributed unit determines, based on a network slice supported by the distributed unit, whether or not the distributed unit supports the network slice that corresponds to the network slice indication information of the first message, in order to ensure that a session service can be provided.

[0068] In yet another possible design, the first message or the reply message additionally includes carrier duplication indication information.

[0069] In this project, the terminal device can transmit the same data over two paths, thereby increasing the reliability of data transmission.

[0070] In yet another possible design, the first message additionally includes DU UE-AMBR indication information, and the DU UE-AMBR indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0071] In this project, the DU UE-AMBR indication information is from the first message, so that a transmission data rate from the distributed unit to the terminal device does not exceed the maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0072] In yet another possible design, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack.

[0073] In this project, the central unit adds, to the first message to be sent to the distributed unit, configuration information of the source network device for a protocol stack that corresponds to a terminal device carrier, so that the distributed unit can perform differentiated configuration in protocol stacks, thereby simplifying operations of the distributed unit.

[0074] Correspondingly, yet another aspect of this Petition 870260050283, dated 05 / 26 / 2026, page 31 / 104 14 / 64 application additionally provides a communications device, and the communications device has a function to implement the behavior of the distributed unit in the aforementioned method. The function can be implemented by using hardware, or it can be implemented by using software that executes corresponding hardware. The hardware or software includes one or more modules that correspond to the aforementioned function.

[0075] In a possible design, the communications apparatus includes: a receiving unit, configured to receive an initial message from a central unit, wherein the initial message includes network slice indication information corresponding to a session, a carrier, or a stream; and a transmitting unit, configured to send a reply message to the central unit.

[0076] In a possible design, the transmitting unit is additionally configured to send a radio resource control message from the central unit to a terminal device, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established.

[0077] In one possible design, the communications device additionally includes a processing unit, configured to determine whether or not the communications device supports a network slice that matches the network slice indication information.

[0078] In a possible project, the first message or the reply message additionally includes carrier duplication indication information.

[0079] In a possible design, the first message additionally includes UE-AMBR DU indication information, and the UE-AMBR DU indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0080] In a possible design, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack.

[0081] In a possible project, the source network device includes Petition 870260050283, dated 05 / 26 / 2026, p. 32 / 104 15 / 64 any one of the following: the central unit, a source base station, a source central unit, and a network core device.

[0082] When the communications device is a chip, the receiving unit may be an input unit such as an input circuit or a communications interface, and the transmitting unit may be an output unit such as an output circuit or a communications interface. When the communications device is a device, the receiving unit may be a receiving device (or may be referred to as a receiver), and the transmitting unit may be a transmitting device (or may be referred to as a transmitter).

[0083] In another possible design, the communications apparatus includes a receiver, a transmitter, a memory, and a processor. The memory stores a set of program code, and the processor is configured to invoke the program code stored in memory to perform the following operations: send an initial message from a central unit using the receiver, where the initial message includes network slice indication information corresponding to a session, a carrier, or a stream; and send a reply message to the central unit using the transmitter.

[0084] Based on the same invention concept, regarding a problem-solving principle and beneficial effects of the device, refer to the aforementioned possible method implementations and beneficial effects brought about by the distributed unit. Therefore, for the device implementation, refer to the method implementation. Repeated parts are not described.

[0085] According to yet another aspect, a communications system is provided, and the communications system includes the aforementioned communication devices.

[0086] According to yet another aspect, a method of communication is provided, and the method includes: receiving, by a terminal device, a radio resource control message, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established; and sending, by the terminal device, a reply radio resource control message to a Petition 870260050283, dated 05 / 26 / 2026, page 33 / 104 16 / 64 central unit. In this design, the terminal device obtains the session identifier, bearer, or flow that is successfully established, to conduct a session with a network device.

[0087] In a possible design, the radio resource control message additionally includes configuration information for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes at least one of the following protocol stacks: an RLC protocol stack, a MAC protocol stack, or a PHY protocol stack.

[0088] In this project, the central unit adds, to the first message to be sent to a distributed unit, configuration information from a source network device to a protocol stack that corresponds to a carrier of the terminal device, and the distributed unit sends the configuration information to the protocol stack that corresponds to the carrier to the terminal device, so that the terminal device can perform differentiated configuration on protocol stacks, thereby simplifying terminal device operations.

[0089] In another possible design, configuration information for at least one protocol stack that corresponds to the carrier is obtained after the distributed unit performs differential configuration based on configuration information from the source network device for at least one protocol stack that corresponds to the carrier.

[0090] In yet another possible design, the source network device includes any one of the following: the central unit, a source base station, a source central unit, and a network core device.

[0091] Correspondingly, this application further provides a communications apparatus which can implement the aforementioned communication method. For example, the communications apparatus can be a chip (e.g., a baseband chip or a communications chip) or a transmitting device (e.g., a terminal device). The aforementioned method can be implemented by software or hardware, or by running corresponding software on hardware.

[0092] In a possible design, a communications device structure includes a processor and memory. The processor is Petition 870260050283, dated 05 / 26 / 2026, page 34 / 104 17 / 64 configured to support the device in performing a corresponding function in the aforementioned communication method. The memory is configured to be coupled to the processor, and stores a necessary program (instruction) (a) and / or data from the communications device. Optionally, the communications device may additionally include a communications interface, configured to support communication between the device and another network element.

[0093] In another possible design, the communications apparatus may include: a receiver unit, configured to receive a radio resource control message, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established; and a transmitter unit, configured to send a reply radio resource control message to a central unit.

[0094] In a possible design, the radio resource control message additionally includes configuration information for at least one protocol stack obtained after a distributed unit performs differential configuration based on configuration information from a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes at least one of the following protocol stacks: an RLC protocol stack, a MAC protocol stack, or a PHY protocol stack.

[0095] In a possible project, the source network device includes any of the following: the central unit, a source base station, a source central unit, and a network core device.

[0096] When the communications device is a chip, the receiving unit may be an input unit such as an input circuit or a communications interface, and the transmitting unit may be an output unit such as an output circuit or a communications interface. When the communications device is a device, the receiving unit may be a receiving device (or may be referred to as a receiver), and the transmitting unit may be a transmitting device (or may be referred to as a transmitter).

[0097] According to yet another aspect, a media of Petition 870260050283, dated 05 / 26 / 2026, page 35 / 104 18 / 64 computer-readable storage is provided. The computer-readable storage medium stores an instruction, and when the instruction is executed on a computer, the computer performs the methods described above.

[0098] According to yet another aspect, a computer program product including an instruction is provided. When the instruction is executed on a computer, the computer performs the methods in the aforementioned aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] To describe the technical solutions in embodiments of the present invention or the fundamentals more clearly, the accompanying drawings required to describe embodiments of the present invention or the fundamentals are briefly described below.

[0100] Figure 1 is a schematic diagram of an example of a communications system according to an embodiment of the present invention;

[0101] Figure 2 is the schematic architectural diagram of an example of a next-generation communications system according to an embodiment of the present invention;

[0102] Figure 3 is a schematic diagram of an example of CU-DU architecture according to an embodiment of the present invention;

[0103] Figure 4a is a schematic diagram of an interaction procedure of a communication method according to an embodiment of the present invention;

[0104] Figure 4b is a schematic diagram of an interaction procedure of another communication method according to an embodiment of the present invention;

[0105] Figure 5 is a schematic diagram of an interaction procedure of a communication method in a specific example;

[0106] Figure 6 is a schematic diagram of updating specific network slice information in an example;

[0107] Figure 7 is a schematic diagram of an interaction procedure of another communication method in a specific example;

[0108] Figure 8 is another schematic diagram of updating Petition 870260050283, dated 05 / 26 / 2026, page 36 / 104 19 / 64 specific network slice information in an example;

[0109] Figure 9 is a schematic diagram of an interaction procedure of yet another communication method according to an embodiment of the present invention;

[0110] Figure 10 is a schematic diagram of a PDU session setup procedure in an example;

[0111] Figure 11 is a schematic diagram of another PDU session configuration procedure in an example;

[0112] Figure 12 is a schematic diagram of a duplication transmission in an example;

[0113] Figure 13 is a schematic diagram of an interaction procedure of yet another communication method according to an embodiment of the present invention;

[0114] Figure 14 is a schematic flowchart of yet another method of communication according to an embodiment of the present invention;

[0115] Figure 15 is a schematic diagram of modules of a communications apparatus according to an embodiment of the present invention;

[0116] Figure 16 is a schematic diagram of modules of another communication device according to an embodiment of the present invention;

[0117] Figure 17 is a schematic diagram of modules of yet another communication device according to an embodiment of the present invention;

[0118] Figure 18 is a schematic diagram of modules of yet another communication device according to an embodiment of the present invention;

[0119] Figure 19 is a schematic diagram of a hardware architecture of a communication device according to an embodiment of the present invention; and

[0120] Figure 20 is a schematic structural diagram of a simplified terminal device. DETAILED DESCRIPTION

[0121] The embodiments of the present invention are described below. Petition 870260050283, dated 05 / 26 / 2026, p. 37 / 104 20 / 64 with reference to the attached drawings in embodiments of the present invention.

[0122] Figure 1 is a schematic diagram of an example of a communications system according to an embodiment of the present invention. The communications system may include at least one network device 100 (only one is shown) and one or more terminal devices 200 connected to the network device 100.

[0123] Network device 100 can be a device that can communicate with terminal device 200. Network device 100 can be any type of device that has a wireless receive / send function. Network device 100 includes, but is not limited to, a base station (e.g., a NodeB, an evolved NodeB eNodeB, a base station in a fifth-generation (5G) communications system, a base station or network device in a future communications system, an access node in a Wi-Fi system, a radio relay node, or a wireless return transport channel node) and the like. Network device 100 can alternatively be a radio controller in a cloud radio access network (CRAN) scenario.Network device 100 may alternatively be a network device in a 5G network or a network device in a future evolved network, or it may be a wearable device, a vehicle-mounted device, or similar. Network device 100 may alternatively be a small cell, a transmission reference point (TRP), or similar. Certainly, in this application, network device 100 is not limited to the same.

[0124] Terminal device 200 is a device that has a wireless receive / transmit function. Terminal device 200 can be deployed on land and includes a closed or open device, a handheld device, a wearable device, or a vehicle-mounted device; it can be deployed on a surface over water (e.g., a ship) or in the air (e.g., an airplane, a balloon, or a satellite). The terminal device can be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal device. Petition 870260050283, dated 05 / 26 / 2026, page 38 / 104 21 / 64 a wireless terminal in industrial control, a wireless terminal in self-driving mode, a wireless terminal in remote medical support, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or similar. An application scenario is not limited in this embodiment of this application. The terminal device may sometimes be referred to as user equipment (UE), an access terminal device, a UE unit, a UE station, a mobile station, a mobile console, a remote station, a remote terminal device, a mobile device, a UE terminal device, a terminal device, a wireless communications device, a UE agent, a UE appliance, or similar.

[0125] A next-generation communications system is used as an example. Figure 2 is a schematic architectural diagram of an example of a next-generation communications system according to an embodiment of the present invention. In Figure 2, in the third-generation partnership project (3GPP) access mode, an access network device in Figure 1 is referred to as a radio access network (RAN) element. In a non-3GPP (N3G) access mode, an access network device is referred to as an access network (AN) element or a non-3GPP interworking function (N3IWF) network element. The network device in Figure 1 may be the access network device in the present document. The communications system additionally includes a network core device.The network core device includes a mobility management and access management function, which is referred to as an access and mobility management function (AMF) network element in this application. The terminal device accesses a network through the use of the access network device, and the AMF is primarily responsible for access management and mobility management on the terminal device.

[0126] In Figure 2, another functional entity can be additionally included, and only some functional entities in this request. Petition 870260050283, dated 05 / 26 / 2026, page 39 / 104 22 / 64 are described in this document for emphasis. The entities are connected by the use of interfaces (e.g., interfaces N1 and N2 in the figure). It can be understood that the network core device may additionally include a session management function, such as a session management function (SMF) entity or another function, and there is no limitation to this in this document.

[0127] A RAN device architecture can be further divided. Figure 3 is a schematic diagram of an example of a CU-DU architecture according to an embodiment of the present invention. A network device (e.g., a base station) includes a CU, and a CU is connected to one or more DUs. CU and DU constitute a complete base station protocol stack function. For example, the CU includes a radio resource control (RRC) protocol stack function, a packet data convergence protocol (PDCP) protocol stack function, and an SDAP protocol stack function, and the DU includes a radio link control (RLC) protocol stack function, a media access control (MAC) protocol stack function, and a physical layer (PHY) protocol stack function.Certainly, the CU-DU architecture can alternatively be another way of distributing a protocol stack, and this is not specifically limited in this application. There is an interface between the CU and the DU. In this application, the interface is referred to as an F1 interface. However, a specific name is not limited. A DU can include one or more cells.

[0128] In this request, network slice indication information may be represented by using at least one of the following parameters:

[0129] 1. Network slice identifier. The network slice identifier may be specifically listed in one or more of the following 1.1 to 1.7.

[0130] 1.1. Network slice type information. Network slice type information can be used to indicate a network slice type such as enhanced mobile broadband (eMBB), ultra-reliable communications, and ultra-low latency communications. Petition 870260050283, dated 05 / 26 / 2026, page 40 / 104 23 / 64 low latency communications (URLLC), or massive machine type communications (mMTC). Optionally, the network slice type information may additionally indicate an end-to-end network slice type, including a RAN-to-CN network slice type, or it may indicate a (R)AN side network slice type or a CN side network slice type.

[0131] 1.2. Service type information relating to a specific service. Service type information may indicate a service characteristic such as a video service, a Vehicle Internet service, or a voice service, or information about a specific service.

[0132] 1.3. Tenant information used to indicate customer information used to create or grant the network slice. For example, a customer is Tencent or the State Grid Corporation of China.

[0133] 1.4. User group information used to indicate group information used to group users according to a specific characteristic, for example, according to a user level.

[0134] 1.5. Slice group information used to indicate that, for example, all network slices that can be accessed by UE can be used as a slice group according to a specific characteristic, or a group can be obtained by grouping network slices according to another criterion.

[0135] 1.6. Network slice instance information used to indicate an identifier and characteristic information of an instance created for the network slice. For example, an identifier may be allocated to a network slice instance to indicate the network slice instance; or a new identifier may be mapped based on a network slice instance identifier to be associated with the network slice instance so that a receiving party can identify, based on the identifier, a specific network slice instance indicated by the identifier.

[0136] 1.7. Dedicated core network (DCN) identifier. The identifier is used to uniquely indicate a dedicated core network in an LTE or eLTE system, for example, a dedicated Internet of Things core network. Optionally, mapping can be performed between the DCN identifier and a network slice identifier, and the Petition 870260050283, dated 05 / 26 / 2026, page 41 / 104 The 24 / 64 DCN identifier can be mapped to the network slice identifier, or the network slice identifier can be mapped to the DCN identifier.

[0137] It should be understood that if a network allows, in a registration area or a tracking area to which a source cell belongs, the UE to access a plurality of network slices, or for a specific public land mobile network (PLMN), a network allows, in a registration area or a tracking area to which a source cell belongs, the UE to access a plurality of network slices, an indication of an allowed network slice includes a plurality of allowed network slice identifiers.

[0138] 2. Single-network slice selection assistance information (S-NSSAI). S-NSSAI includes at least slice / service type (SST) information, and optionally may additionally include slice differentiator (SD) information. SST information is used to indicate the behavior of a network slice, such as a characteristic and a service type that belong to that network slice. SD information is complementary to SST information. If the SST corresponds to the implementation of a plurality of network slices, the SD may correspond to a single network slice instance.

[0139] It should be understood that if a network allows, in a registration area or a tracking area to which a source cell belongs, the UE to access a plurality of network slices, or for the specific public land mobile network (PLMN), a network allows, in a registration area or a tracking area to which a source cell belongs, the UE to access a plurality of network slices, the indicated allowed network slice includes a plurality of allowed S-NSSAI.

[0140] 3. S-NSSAI group information used to indicate grouping performed according to a specific characteristic. For example, all network slices of a common AMF that are accessible to a UE can be used as an S-NSSAI group. NSSAI include a plurality of S-NSSAI.

[0141] 4. Temporary ID: Temporary identifier information is allocated by an AMF for the EU that has been registered. Petition 870260050283, dated 05 / 26 / 2026, p. 42 / 104 25 / 64 with one CN side, and the temporary ID can only correspond to a specific AMF.

[0142] 5. Network access (radio) network slice selection assistance information ((R)AN-NSSAI, R-NSSAI): indicates a set of specific SNSSAI, namely, a set of specific S-NSSAI. It should be understood that if the network allows, in a registration area or a tracking area to which the source cell belongs, the UE to access a plurality of network slices, or the specific public land mobile network (PLMN), the network allows, in a registration area or a tracking area to which the source cell belongs, the UE to access a plurality of network slices, the indication of permitted network slice may include an identifier of a set of a plurality of permitted RNSSAI.

[0143] 6. Allowed NSSAI (permitted). Allowed NSSAI indicates NSSAI that a network allows a terminal device to access in a current registration area.

[0144] It should be understood that a specific form of encoding of permitted network slice indication information is not limited. Certainly, in addition to the aforementioned identifiers, network slice information may be another identifier, and there is no limitation to this in the present document. If the network allows the UE to access a plurality of network slices, the permitted network slice indication may be a form of list of permitted network slice indications, for example, a list of permitted Network Slice Selection Assistance Information (allowed NSSAI list), or a list of permitted Single Network Slice Selection Assistance Information (allowed S-NSSAI list).

[0145] In this modality of this request, the network slice may use at least one of the aforementioned parameters to represent the network slice indication information. For example, the network slice indication information may be represented by the network slice type, or it may be represented by the network slice type and the service type, or it may be represented by the service type and the tenant information. There is no limitation in this modality of this request. As Petition 870260050283, dated 05 / 26 / 2026, page 43 / 104 26 / 64 representing network slice indication information for a network slice is not described again below. It should be understood that if the terminal device, the access network device, or the network core device supports a plurality of network slices, indication information of the network slices supported by the terminal device, the access network device, or the network core device may be incorporated in a list form of the aforementioned at least one identifier.

[0146] Because there is a plurality of service types on the terminal device, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), and different types of service sessions may correspond to different network slices, even the same type of service may correspond to different network slices due to different operators or service providers offering the same type of service. Different access network devices may support different network slices. Thus, when the terminal device needs to access the network and configure a plurality of sessions, a connected access network device needs to support network slices that correspond to all sessions or some sessions on the terminal device.

[0147] The embodiments of the present invention can be applied to another communications system that supports a network slice. The terms system and network can be interchanged with each other. The system architecture described in the embodiments of the present invention is intended to describe the technical solutions in the embodiments of the present invention more clearly, but does not constitute a limitation on the technical solutions provided in the embodiments of the present invention. A person of ordinary skill in the art can understand that the technical solutions provided in the embodiments of the present invention are also applicable to a similar technical problem as a network architecture evolves.

[0148] It should be noted that the terms system and network in embodiments of the present invention may be used interchangeably. A plurality of means two or more, and in view of this, a plurality of may also be understood as at least two in embodiments Petition 870260050283, dated 05 / 26 / 2026, page 44 / 104 27 / 64 of the present invention. The term and / or describes an association relationship to describe associated objects and represents that three relationships can exist. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists. Furthermore, the character / typically indicates an OR relationship between the associated objects.

[0149] The embodiments of the present invention provide a communication method and a communications apparatus. Network slice information supported by a distributed unit is exchanged between the distributed unit and a central unit by means of a connection configuration process, to implement a network slice-based service in a distributed unit and central unit architecture.

[0150] How a CU obtains network slice information supported by a DU is specifically described below by the use of modalities.

[0151] Figure 4a is a schematic diagram of an interaction procedure of a communication method according to an embodiment of the present invention. The method may include the following steps:

[0152] S401: A distributed unit sends a connection configuration request message to a central unit, and the central unit receives the connection configuration request message from the distributed unit.

[0153] S402: The central unit sends a connection configuration response message to the distributed unit, and the distributed unit receives the connection configuration response message from the central unit.

[0154] In this mode, the connection configuration request message includes information about the network slice supported by the distributed unit. The connection configuration request message can be an interface configuration request message, and it can certainly be another message to configure the connection. There is no limitation on this in the present document.

[0155] Furthermore, the interface can be an F1 interface between the CU and the DU. Specifically, the DU sends an F1 interface setup request message to the CU. Of course, there is no limitation as to the name of the interface. Petition 870260050283, dated 05 / 26 / 2026, page 45 / 104 28 / 64

[0156] Network slice information supported by the distributed unit includes at least one combination of the following: network slice indication information supported by at least one cell of the distributed unit; a cell identifier of at least one cell of the distributed unit and network slice indication information supported by each of the at least one cell; or an identifier of a tracking area or a registration area that corresponds to at least one cell of the distributed unit and network slice indication information supported by each tracking area or each registration area in the tracking area or by the registration area that corresponds to at least one cell.

[0157] Optionally, the connection configuration response message additionally includes information on the network slice supported by the central unit.

[0158] Specifically, it is assumed that network slice information supported by a DU cell is already configured for the DU, for example, an operation, administration and maintenance (OAM) system configures the network slice information supported by the DU cell.

[0159] Figure 5 is a schematic diagram of specific network slice information transmission in an example. In Figure 5, a DU and a CU can configure an interface for connection, for example, an F1 interface, and there is no limitation to this in the present document. Network slice information supported by the DU is exchanged when the interface is configured between the DU and the CU.

[0160] As shown in Figure 5, the method includes the following steps.

[0161] S501: A DU sends an interface configuration request message to a CU, and the CU receives the interface configuration request message.

[0162] The request message includes network slice indication information (which are S-NSSAI in Figure 5) supported by the DU. In addition, the request message may also include a DU cell, or a tracking area identity / identifier (TAI) or a registration area identity / identifier (RAI) to which the cell belongs. The tracking area identifier may also Petition 870260050283, dated 05 / 26 / 2026, page 46 / 104 29 / 64 may be referred to as a tracking area code (TAC), the registration area identifier may also be referred to as a registration area code (RAC), and the names of the tracking area identifier and registration area identifier are not limited. Alternatively, a public land mobile network (PLMN) identifier may be used when the TAC or RAC is given.

[0163] Specifically, the network slice information supported by DU can be in the following three ways, but is not limited to the following three ways:

[0164] (a) The request message includes network slice information supported by DU. Name of IE / Group Explanation Network slice indication information supported by a DU The network slice indication information supported by a DU is, for example, a list of S-NSSAI (S-NSSAI list) or a single part of the S-NSSAI.

[0165] (b) The request message includes network slice information supported by the DU cell plurality. Name of IE / Group Explanation Cell Identifier The cell identifier can be a global cell ID (CGI), or it can be a physical cell ID (PCI) or another identifier. Network Slice Indication Information Supported by Each Cell The network slice indication information supported by each cell is, for example, an S-NSSAI list or a single part of the S-NSSAI.

[0166] In this implementation, the request message may include an identifier for at least one DU cell and at least one piece of network slice indication information that corresponds to each cell identifier. A DU may include one or more cells, and each cell is identified by the use of a cell identifier. The cell identifier may identify Petition 870260050283, dated 05 / 26 / 2026, page 47 / 104 30 / 64 uniquely a cell within a specific range. Each cell can support one or more network slices. Each cell supports a different network slice, and a cell identifier can thus correspond to at least one piece of network slice indication information.

[0167] (c) The request message includes a network slice supported by a TA / RA that corresponds to a plurality of DU cells. Name of IE / Group Explanation Tracking Area Identifier or Registration Area Identifier The tracking area identifier or registration area identifier is a tracking area identifier (TAI), a registration area identifier (RAI), a tracking area code (TAC), a registration area code (RAC), or a PLMN identifier. Network Slice Indication Information Supported by Each TAI / RAI The network slice indication information supported by each TAI / RAI is, for example, an S-NSSAI list or a single part of the S-NSSAI.

[0168] In an implementation, information about the network slice supported by the DU may include at least one piece of network slice indication information that corresponds to a tracking area (TA) or a registration area (RA) to which a DU cell belongs. Each TA / RA may support one or more network slices, and a piece of TA / RA information may thus correspond to at least one piece of network slice indication information. The tracking area identifier or tracking area code may uniquely identify a tracking area in a specific range, the registration area identifier or registration area code may uniquely identify the registration area in a specific range. For example, if a piece of network slice indication information is indicated by a list of S-NSSAI, a TAI / RAI / TAC / RAC may correspond to a list of S-NSSAI.

[0169] S502: The CU sends a response message to the configuration. Petition 870260050283, dated 05 / 26 / 2026, page 48 / 104 31 / 64 interface to the DU, and the DU receives the interface configuration response message. If a supported network slice is also configured for the CU, optionally, the CU additionally returns, in this message, information about the network slice supported by the CU, to notify the DU of the information about the network slice supported by the CU.

[0170] By using the aforementioned interaction process, the DU notifies the CU of the supported network slice information, so that the CU verifies whether the CU also supports the network slice supported by the DU.

[0171] It should be noted that if the CU does not support a network slice configured for the DU, this CU-DU architecture can only support the slice supported by the CU. In this case, if a DU needs to broadcast the network slice supported by the DU, each cell of the DU cannot broadcast the network slice configured for the DU, but only broadcasts a network slice configured by OAM for the DU and also supported by the CU.

[0172] In this mode, the network slice information supported by the distributed unit is independently configured with flexibility for the distributed unit.

[0173] Furthermore, Figure 6 is a schematic diagram of updating specific network slice information in an example. As shown in Figure 6, when a network slice supported by a DU is updated, S601 is performed: the DU uses a configuration update message to send updated network slice information from the DU to a CU, and the CU receives the configuration update message from the DU. S602: The CU sends a response configuration update message to the DU. If a network slice supported by the CU is updated, the CU can also use the response configuration update message to send updated network slice information from the CU to the DU.

[0174] In an alternative embodiment of Figure 4a, Figure 4b is a schematic diagram of an interaction procedure of another communication method according to an embodiment of the present invention. The method may include the following steps:

[0175] S401': A distributed unit sends a connection configuration request message to a central unit, and the central unit receives the connection configuration request message from Petition 870260050283, dated 05 / 26 / 2026, page 49 / 104 32 / 64 of the distributed unit.

[0176] S402': The central unit sends a connection configuration response message to the distributed unit, and the distributed unit receives the connection configuration response message from the central unit.

[0177] Unlike the mode shown in Figure 4a, in the mode shown in Figure 4b, the connection configuration response message includes network slice information supported by the distributed unit. In this way, the network slice information supported by the DU can be controlled by the CU in a centralized manner, thus reducing signaling overloads and simplifying operations.

[0178] Specifically, it is assumed that a network slice supported by each DU is configured for the CU, or network slice information supported by all CU cells or TAs that correspond to all cells is configured for the CU.

[0179] Figure 7 is a schematic diagram of an interaction procedure for another communication method in a specific example. The method may include the following steps.

[0180] S701: A DU sends an interface configuration request message to a CU, and the CU receives the interface configuration request message.

[0181] If DU cell information is configured for the DU, the request message may include a DU cell identifier (list). The cell identifier may be a CGI, or it may be a PCI.

[0182] S702: The CU sends an interface configuration response message to the DU, and the DU receives the interface configuration response message.

[0183] The response message includes at least one of the following: network slice information supported by the DU, network slice information supported by all DU cells, or network slices supported by TAs / RAs that correspond to all DU cells. A specific format is shown in the aforementioned three ways.

[0184] Optionally, the connection configuration response message or a configuration update message may Petition 870260050283, dated 05 / 26 / 2026, page 50 / 104 33 / 64 additionally include configuration information for each network slice.The configuration information includes at least one of the following: Layer 1 (Layer 1, L1) protocol stack configuration information, Layer 2 (Layer 2, L2) protocol stack configuration information, available physical resource information (such as a frequency band, a frequency, or a numerology), frequency band information (namely, a frequency band used by the network slice) that corresponds to the network slice, frequency information (namely, a center frequency of a frequency band used by the network slice) that corresponds to the network slice, supportable status information (including an idle state, a connected state, and an inactive state), or a parameter (such as a maximum bit rate, a latency requirement, a reliability requirement, or a supported MTC quantity) of a KPI (key performance indicator).

[0185] Furthermore, Figure 8 is another schematic diagram of updating specific network slice information in an example. As shown in Figure 8, when network slice information supported by any cell of a CU is updated, S801 is performed: the CU uses a configuration update message to send updated network slice information from the CU to a DU, and the DU receives the configuration update message from the CU. The configuration update message includes updated network slice information supported by the central unit or the distributed unit. S802: The DU sends a configuration information response message to the CU.

[0186] It can be learned from the description so far that, in this application, after the network slice information supported by the DU is exchanged between the DU and the CU by using a connection configuration request message or a connection configuration response message, the CU and the DU can provide a network slice-based service to a terminal device based on the network slice information supported by the DU. Therefore, for example, the CU can notify a network core of a CU cell and the network slice information supported by the CU, so that an AMF can allocate a corresponding TA or RA range to the terminal device. As another example, the CU can notify a Petition 870260050283, dated 05 / 26 / 2026, page 51 / 104 34 / 64 neighboring base station information on the network slice supported by the CU helps the neighboring base station make a handover decision. For example, the neighboring base station can determine, based on whether or not the CU supports a network slice to which a CU terminal device currently belongs, whether or not to initiate a handover request to the CU. As another example, the CU can become aware of a network slice supported by the DU, so that the CU can determine whether or not to initiate a corresponding session request message to the DU. For example, when dual connectivity needs to be configured for the terminal device, the terminal device reports a plurality of accessible DUs to the CU using a metering report, and the CU can determine, based on whether or not the DU supports a current network slice of the terminal device, whether or not to add the DU as a Secondary gNB device of the terminal device.Specifically, a DU 1 supports network slices 1 and 2, and a DU 2 supports network slices 2 and 3. During dual connectivity configuration, the measurement report sent by the terminal device to the CU shows that the signal strength of DU 1 is greater than the signal strength of DU 2, but a current session of the terminal device belongs to network slice 3. Since DU 1 does not support network slice 3, even though a signal from DU 1 is strong, the CU still selects DU 2 as the terminal's secondary RAN device. Certainly, the exchange of network slice information supported by the DU between the DU and the CU can also be used in another scenario.

[0187] According to the communication method provided in this embodiment of the present invention, network slice information supported by the distributed unit is exchanged between the distributed unit and the central unit by using a connection configuration process, so that a network slice-based service in a distributed unit and central unit architecture can be implemented.

[0188] In the aforementioned embodiment, the network slice information supported by the distributed unit is exchanged between the distributed unit and the central unit using a connection configuration process, so that the DU and the CU can subsequently provide a network slice-based service to the terminal device. The network slice-based service is incorporated into processes such as cell handover, state transition of Petition 870260050283, dated 05 / 26 / 2026, page 52 / 104 35 / 64 terminal device, and session configuration.

[0189] Figure 9 is a schematic diagram of an interaction procedure of yet another communication method according to an embodiment of the present invention. The method may include the following steps.

[0190] S901: A central unit sends a first message to a distributed unit. The distributed unit receives the first message from the central unit. The first message includes network slice indication information that corresponds to a session, a carrier, or a flow.

[0191] The first message is used to request the distributed unit to establish or modify a session, establish or modify a bearer, or establish or modify a flow for an endpoint device. The first message may be a session configuration request message, a session modification request message, a bearer configuration request message, a bearer modification request message, a flow configuration request message, or a flow modification request message, or it may be a UE context configuration request message. It may be understood that a message name is not limited in this request.

[0192] S902: The distributed unit sends a reply message to the central unit, and the central unit receives the reply message from the distributed unit.

[0193] This modality can be based on the distributed unit obtaining supported network slice information.

[0194] A session, bearer, or flow setup process can be a process of setting up a session, bearer, or flow when the terminal device accesses a network device for the first time, or a process of reconfiguring the session, bearer, or flow after the terminal device performs a handover, or it can be a process of setting up a session, bearer, or flow for a new DU connected by the terminal device after a terminal device status changes (for example, from an inactive state to an active state). A session, bearer, or flow setup process can also be a process of modifying a session, bearer, or flow after the terminal device accesses a network device. Petition 870260050283, dated 05 / 26 / 2026, page 53 / 104 36 / 64

[0195] Optionally, the first message additionally includes an identifier of a session to be established or modified, an identifier of a carrier to be established or modified, or an identifier of a flow to be established or modified.

[0196] A session includes at least one carrier, and a carrier corresponds to at least one flow. Specifically, if the session request message is to establish or modify a session, the session request message includes an identifier of the session that needs to be established or modified, and a network slice that corresponds to each session; if the session request message is to establish or modify a carrier, the session request message includes an identifier of the carrier that needs to be established or modified, and a network slice that corresponds to a session to which each carrier or each group of carriers belongs, and may additionally include a session identifier that corresponds to the session to which each carrier or each group of carriers belongs and a network slice that corresponds to the session identifier;If the session request message is to establish or modify a flow, the session request message includes an identifier for each flow and a network slice that corresponds to a session to which each flow or group of flows belongs, and may additionally include a session identifier that corresponds to the session to which each flow or group of flows belongs and a network slice that corresponds to the session identifier.

[0197] Based on the description so far, the distributed unit obtains, from the session configuration request message, network slice indication information that corresponds to a session, carrier, or flow to be established or modified, so that the distributed unit establishes or modifies the session, carrier, or flow on an indicated network slice, to conduct a session on a corresponding network slice, for example, it configures a protocol stack parameter that corresponds to the session or carrier based on a network slice indicated by the network slice indication information, and selects a physical transmission resource appropriate for the session or carrier, for example, a numerology.

[0198] In addition, after step S901 and before step S902, the method may additionally include the following steps: Petition 870260050283, dated 05 / 26 / 2026, page 54 / 104 37 / 64

[0199] The distributed unit determines whether or not to support the network slice that corresponds to the network slice indication information.

[0200] Specifically, for the network slice indication information received, the DU needs to determine, based on the network slice supported by the DU and obtained in the aforementioned mode, whether the DU supports the network slice that corresponds to the network slice indication information. Specifically, the DU determines whether the network slice that corresponds to the network slice indication information is within a range of network slices supported by the DU. If the DU does not support all network slices to which the session, carrier, or flow of the first message belongs, the DU may refuse to establish or modify the session, carrier, or flow whose network slice is not supported by the DU, and notify, by using a reply message, the CU of the session, carrier, or flow that the DU refuses to establish or modify. Optionally, the response message may additionally carry rejection reason information, to indicate that session, carrier, or flow establishment or modification is rejected because the DU does not support a network slice to which the session, carrier, or flow belongs.

[0201] A session, carrier, or flow can be established (a) or modified (a) between a CU and a DU. A process of configuring or modifying a session, carrier, or flow between the CU and the DU can also be part of a PDU session configuration process. The PDU session configuration process is described in detail below.

[0202] Figure 10 is a schematic diagram of a PDU session setup process. The session setup process may include the following steps.

[0203] Step S101: An AMF sends a PDU session configuration request message to a CU.

[0204] The message includes identifying information for a session that needs to be established / modified, identifying information for a flow that needs to be established or modified in the session, and a QoS profile that corresponds to each flow, such as a priority.

[0205] Step S102: The CU sends the PDU session configuration request message to a DU, and the DU receives the message. Petition 870260050283, dated 05 / 26 / 2026, page 55 / 104 38 / 64 PDU session configuration request.

[0206] In Figure 10, the first message described above is specifically the PDU session configuration request message in this document. For details, refer to the description of S901 in the mode shown in Figure 9.

[0207] Step S103: The DU sends a PDU session configuration response message to the CU, and the CU receives the PDU session configuration response message.

[0208] In Figure 10, the response message described above is specifically the response message to the PDU session configuration in this document. For details, refer to the description of S902 in the mode shown in Figure 9.

[0209] Step S104: The CU sends an RRC message to the DU. The DU transparently transmits the RRC message to the UE, and the UE receives the RRC message.

[0210] In this document, the RRC message may be an RRC connection reconfiguration message, an RRC connection setup message, an RRC connection resume message, an RRC connection suspend message, or similar.

[0211] Step S105: The UE sends an RRC reply message to the UC. The RRC reply message can be routed using the DU. CU receives the RRC reply message.

[0212] Step S106: The CU sends a response message to the session configuration for the AMF.

[0213] The order of this step can be adjusted as long as this step is after step 103.

[0214] Optionally, the RRC message may include an identifier of a session that is successfully established. In another example, if S101 is to request establishing a bearer, the RRC message may include an identifier of a bearer that is successfully established; or if S101 is to request configuring a flow, the RRC message may include an identifier of a flow that is successfully established.

[0215] In the example in Figure 10, a configuration process of Petition 870260050283, dated 05 / 26 / 2026, page 56 / 104 A 39 / 64 session is described. In this example, after the DU sends the session configuration response message to the CU, the CU sends the RRC message to a terminal device using the DU. If this mode is used, an existing pattern is slightly modified, and a DU function does not need to be added.

[0216] Figure 11 is a schematic diagram of another PDU session setup process. The session setup process may include the following steps.

[0217] Step S111: An AMF sends a PDU session request message to a CU.

[0218] The message includes identifying information for a session that needs to be established / modified, identifying information for a flow that needs to be established or modified in the session, and a QoS profile that corresponds to each flow, such as a priority.

[0219] Step S112: The CU sends the PDU session configuration request message to a DU. The DU receives the PDU session configuration request message.

[0220] In Figure 11, the first message described above is specifically the PDU session configuration request message in this document. For details, refer to the description of S901 in the mode shown in Figure 9.

[0221] Step S113: The DU sends a radio resource control (RRC) message to a terminal device, and the terminal device receives the RRC message.

[0222] One difference from the above example is that the DU can directly generate or modify the RRC message, and then send the RRC message directly to UE.

[0223] Step S114: The DU sends a PDU session configuration response message to the CU, and the CU receives the PDU session configuration response message.

[0224] In Figure 11, the response message described above is specifically the response message to the PDU session configuration in this document. For details, refer to the description of S902 in the mode shown in Figure 9. Petition 870260050283, dated 05 / 26 / 2026, page 57 / 104 40 / 64

[0225] Step S115: UE sends an RRC reply message to CU, where the RRC reply message can be forwarded using DU.

[0226] Step S116: The CU sends a response message to the session configuration to the AMF. This step can be any step after step S114.

[0227] Optionally, the RRC message may include an identifier of a session that is successfully established. In another example, if S111 is to request establishing a bearer, the RRC message may include an identifier of a bearer that is successfully established; or if S111 is to request configuring a flow, the RRC message may include an identifier of a flow that is successfully established.

[0228] In the example in Figure 11, a complete session setup process is described. In this mode, the DU can directly generate the RRC message, so that the DU can send the RRC message to the terminal device more quickly without needing to send the RRC message back to the CU, thus reducing latency.

[0229] In one implementation, the first message or the reply message additionally includes carrier duplication indication information. Carrier duplication indication information is used to indicate that a duplication transmission configuration is performed in the session or on the carrier.

[0230] As shown in Figure 12, the replicated transmission configuration means that the UE can simultaneously perform data transmission with two DUs or two cells of a DU. For example, the UE can perform data transmission with a DU 1 and a DU 2 at the same time. A specific process is as follows: for downlink data transmission, data from a network core is duplicated to obtain two identical copies in a PDCP layer of the CU, one copy is transmitted to DU 1 and is then transmitted to the UE by DU 1, and the other copy is transmitted to DU 2 and is then transmitted to the UE by DU 2. For uplink data, the UE duplicates the data to obtain two identical copies in a PDCP layer of the UE, transmits one copy to DU 1, and transmits the other Petition 870260050283, dated 05 / 26 / 2026, p. 58 / 104 41 / 64 copy to DU 2. In this implementation, the terminal device can transmit the same data over two paths, thereby increasing reliability in data transmission. Data transmission is successful as long as transmission on either of the two links is successful. Whether or not carrier duplication indication information is included in the first message or the reply message depends on whether the duplication transmission configuration is performed by the CU or the DU. For example, if the duplication transmission configuration is performed by the CU, the carrier duplication indication information is included in the first message. If the duplication transmission configuration is performed by the DU, the carrier duplication indication information is included in the reply message.

[0231] In another implementation, the first message additionally includes information indicating the maximum aggregation bit rate of the distributed unit UE (DU UE-AMBR). The DU UE-AMBR indication information is used to indicate a maximum aggregation bit rate that can be provided by the distributed unit to the terminal device.

[0232] Specifically, if a network performs dual connectivity (DC) or multiconnectivity (MC) configuration for a UE carrier or session, i.e., the UE can perform data transmission with at least two DUs at the same time, a UE capability in the session configuration request may optionally include a UE-AMBR DU (UE-AMBR DU). The CU obtains the UE-AMBR DU based on the UE-AMBR (the UE-AMBR may be obtained by the CU based on a UE-AMBR received from the network core, or it may be obtained in another way), the metering report, a resource usage status of the DU, and / or similar.

[0233] For example, if the UE can be served by two DUs (one DU 1 and one DU 2) at the same time, and it is assumed that the UE-AMBR is 90 (bps), and according to the measurement report, the current spectral efficiency of DU 1 is twice the current spectral efficiency of DU 2, the CU learns that a DU 1 UE-AMBR and a DU 2 UE-AMBR are in a 2:1 ratio; specifically, a DU 1 UE-AMBR is 60 (bps) and a DU 2 UE-AMBR is 30 (bps). As another example, the CU can also obtain, based on a Petition 870260050283, dated 05 / 26 / 2026, page 59 / 104 42 / 64 current resource usage status, that an AMBR that can be provided by DU 1 to UE is 20 (bps), and the CU determines that a DU 1 UE-AMBR is 20 (bps) and a DU 2 UE-AMBR is 70 (bps). CU coordination prevents a case where the UE-AMBR is exceeded due to independent scheduling of a target base station and a source base station (for example, the UE-AMBR is 50 bits, and if the DU does not know that the UE-AMBR is 50 bits, DU 1 allocates 40 bits to the UE, i.e., DU 1 UE-AMBR is 40 bits, and DU 2 allocates 20 bits to the UE, i.e., the AMBR of DU 2 is 20 bits; and finally, the sum of the two is greater than 50 bits), thus ensuring successful data transmission based on DC. It can be understood that the DU UE-AMBR can also be represented by another name, for example, a split UE-AMBR or a partial UE-AMBR, and there is no limitation in this request.

[0234] It can be learned from the description so far that in this embodiment of the present invention, during session setup or modification, a central unit notifies a distributed unit of the network slice indication information corresponding to the session, carrier, or flow to be established or modified, so that a distributed unit establishes or modifies a session, carrier, or flow on the indicated network slice, a distributed unit can accurately select a network slice and can configure, based on the network slice information corresponding to the session, an L1 / L2 parameter corresponding to the network slice for the terminal device, and sessions corresponding to different network slices meet a specific requirement for QoS. Therefore, different Layer 1 or Layer 2 configurations can be used for different network slices on one side of a RAN.For example, a carrier for a massive machine-type communications (mTC) network slice and a carrier for an ultra-reliable and low-latency communications (URLLC) network slice may have different MAC layer configurations or RLC layer configurations (e.g., the number of RLC layer retransmissions is different) on the RAN side, or they may have different PHY layer configurations (e.g., different frequencies or numerologies are used, or different TTI durations are used). During modification or configuration. Petition 870260050283, dated 05 / 26 / 2026, pp. 60 / 104 43 / 64 of a session, a carrier, or a flow, a network slice to which a session, a carrier, or a flow that needs to be established (a) or modified (a) belongs is specified (a) in this embodiment of the present invention. Thus, a UE side can pertinently configure RLC / MAC / PHY for a network slice to which the session, carrier, or flow belongs. If network slice information is not ported, a DU cannot pertinently perform a configuration, and consequently network performance is degraded. For example, a QoS requirement of the terminal device cannot be met, or a frequent radio link failure (e.g., caused by improper configuration of RLC retransmission times) may occur, thus increasing signaling overheads.

[0235] According to the communication method provided in this embodiment of the present invention, the central unit notifies the distributed unit of the network slice indication information corresponding to the session, carrier, or flow to be established or modified, so that the distributed unit establishes or modifies the session, carrier, or flow on the indicated network slice, and the distributed unit can accurately select a network slice, and perform corresponding configuration on the network slice to provide, to the terminal device, a network slice-based service that meets a requirement.

[0236] Figure 13 is a schematic diagram of an interaction procedure of yet another communication method according to an embodiment of the present invention. The method includes the following steps.

[0237] S131: A source network device sends a handover request to a CU 1. CU 1 receives the handover request.

[0238] The source network device can be a gNB source, a CU 2, or an AMF.

[0239] Optionally, the handover request includes configuration information from the source network device for at least one protocol stack that corresponds to a carrier. The at least one protocol stack includes: an RLC protocol stack, a MAC protocol stack, or a PHY protocol stack.

[0240] S132: CU 1 sends a first message to DU 1. DU 1 receives the first message from the central unit. Petition 870260050283, dated 05 / 26 / 2026, pp. 61 / 104 44 / 64

[0241] The first message includes network slice indication information that corresponds to a session, a carrier, or a flow. The first message additionally includes configuration information for the source network device for at least one protocol stack that corresponds to the carrier.

[0242] S133: DU 1 sends a reply message to CU 1. CU 1 receives the reply message from DU 1.

[0243] In Figure 13, the response message is a response message to the PDU session configuration.

[0244] The first message is used to request a distributed unit to establish or modify a session, establish or modify a bearer, or establish or modify a flow to an endpoint device. The first message may be a session configuration request message, a session modification request message, a bearer configuration request message, a bearer modification request message, a flow configuration request message, or a flow modification request message, or it may be a UE context configuration request message. It may be understood that a message name is not limited in this request. In Figure 13, a session configuration request message is used as an example of the first message for description.

[0245] For a session setup process, refer to the description in the aforementioned modality.

[0246] S134: CU 1 sends a radio resource control message to UE using DU 1, where the RRC message is forwarded by a distributed unit. UE receives the RRC message.

[0247] The RRC message includes an identifier for a session, bearer, or flow that is successfully established. The RRC message additionally includes configuration information for at least one protocol stack obtained after the distributed unit performs differential configuration based on the configuration information of the source network device for at least one protocol stack that corresponds to the bearer, and the at least one protocol stack includes at least one of the following protocol stacks: a protocol stack Petition 870260050283, dated 05 / 26 / 2026, pp. 62 / 104 45 / 64 RLC, a MAC protocol stack, or a PHY protocol stack.

[0248] S135: UE sends an RRC reply message to CU 1 using DU 1. CU 1 receives the RRC reply message from UE.

[0249] S136: CU 1 sends a handover reply message to the source network device. The source network device receives the handover reply message from CU 1.

[0250] In a handover scenario, CU 1 and DU 1 belong to a target base station, and CU 1 receives the handover request message from the source network device (for example, an AMF, a gNB, or a CU 2). If the handover request message includes configuration information (it may include configuration information from an RRC protocol stack, a PDCP protocol stack, or an SDAP protocol stack on the source network device) from the source network device to an RLC protocol stack, a MAC protocol stack, or the PHY protocol stack of a terminal device carrier, the session request message from CU 1 to DU 1 also carries the configuration information from the source network device to the RLC protocol stack, the MAC protocol stack, or the PHY protocol stack of the terminal device carrier.The protocol stack configuration information is used by DU 1 for configuration reference, so that DU 1 can perform differentiated configuration based on the configuration information.

[0251] For each carrier, there may be different RLC, MAC, or PHY parameter settings. For example, for RLC, different carriers may use different transmission modes, including a transparent transmission mode or a confirmed mode or an unconfirmed mode, or different maximum numbers of RLC retransmission times may be configured for different carriers. For MAC, different carriers may use different scheduling priorities. For PHY, different carriers may use different numerologies.

[0252] For example, in a handover scenario, the PHY configuration and RLC configuration of a carrier 1 that needs to be transferred can be found in a PHY layer by using numerology 1 and numerology 2. On the source network device, the source network device configures Petition 870260050283, dated 05 / 26 / 2026, pp. 63 / 104 46 / 64 the carrier in numerology 1 to serve the carrier and configures the maximum number of RLC layer retransmission times to five, and after receiving a configuration message from the source network device for carrier 1, DU 2 also configures the maximum number of RLC retransmission times to five based on QoS requirement information and similar and with reference to configuration information from the source network device. However, for PHY layer configuration, DU 1 is overloaded in numerology 1, and therefore DU 1 configures the carrier in numerology 2 to serve the carrier. Therefore, DU 1 performs differentiated configuration. Specifically, DU 1 only needs to instruct the terminal device (or instruct the terminal device using the CU) to modify the PHY numerology configuration, and not modify the number of RLC retransmission times.In this way, a protocol configuration operation stack corresponding to the DU 1 carrier is simplified, and air interface resource overhead between DU 1 and the terminal device is reduced.

[0253] Furthermore, in a terminal device state transition scenario, if the terminal device is currently in an inactive state, and the terminal device wants to resume a connected state or invoke an RNA update procedure for CU 1, the following scenarios exist.

[0254] In one scenario, the terminal device moves from a network coverage area of ​​CU 2 or another gNB to a network coverage area of ​​CU 1, and CU 1 first sends a context request message to the gNB or CU 2. The context request message includes terminal device identification information. After receiving the context request message, the gNB or CU 2 returns a context response message based on the identification information. The message includes configuration information for at least one of the RLC, MAC, or PHY protocol stack, configured (a) by the gNB or CU 2, of the terminal device carrier.

[0255] In another scenario, the terminal device performs a state transition within the network coverage area of ​​CU 1, and CU 1 stores the configuration information for the RLC, MAC, and PHY protocol stack of the terminal device carrier. In both scenarios, a second message from CU 1 to a DU 1 carrier contains configuration information from the terminal device. Petition 870260050283, dated 05 / 26 / 2026, pp. 64 / 104 47 / 64 network source for at least one or a combination of the RLC, MAC, and PHY protocol stack of the terminal device carrier. The protocol stack configuration information is used by the DU for configuration reference, so that the DU can perform differentiated configuration based on the configuration information. It can be understood that configuration information that is for the carrier's RLC, MAC, and PHY protocol stack and that is ported in the second message from CU 1 to the DU may also be configuration information stored by CU 1 for the RLC, MAC, PHY protocol stack that corresponds to the inactive terminal.

[0256] According to the communication method provided in this embodiment of the present invention, the central unit adds, to the first message to be sent to the distributed unit, configuration information from the source network device to a protocol stack that corresponds to the terminal device carrier, so that the distributed unit can perform differentiated configuration in protocol stacks, thereby simplifying operations of the distributed unit.

[0257] Figure 14 is a schematic flowchart of yet another communication method according to an embodiment of the present invention. Specifically, a schematic diagram of a session setup procedure during handover performed based on an interface (e.g., an Xn interface) between network devices is provided. The method includes the following steps.

[0258] S141: A source network device sends a handover request message to a central unit, and the central unit receives the handover request message.

[0259] The source network device can be a gNB source, a CU 2, or an AMF.

[0260] S142: The central unit sends a first message to a distributed unit, and the distributed unit receives the first message from the central unit.

[0261] In Figure 14, a PDU session configuration request message is used as an example of the first message for description.

[0262] S143: The distributed unit sends a reply message Petition 870260050283, dated 05 / 26 / 2026, pp. 65 / 104 48 / 64 to the central unit, and the central unit receives the response message from the distributed unit.

[0263] In Figure 14, the response message is a response message to the PDU session configuration.

[0264] S144: The central unit sends a radio resource control message to the UE using the distributed unit, where the RRC message is forwarded by the distributed unit; and the UE receives the RRC message.

[0265] The RRC message includes an identifier of a session, bearer, or flow that is successfully established. The RRC message additionally includes configuration information for at least one protocol stack obtained after the distributed unit performs differential configuration based on configuration information from the source network device for at least one protocol stack that corresponds to a bearer, and the at least one protocol stack includes at least one of the following protocol stacks: an RLC protocol stack, a MAC protocol stack, or a PHY protocol stack.

[0266] S145: The UE sends an RRC reply message to the central unit using the distributed unit, and the central unit receives the RRC reply message from the UE.

[0267] S146: The central unit sends a handover reply message to the source network device, and the source network device receives the handover reply message from the central unit.

[0268] For S141 to S146, refer to the corresponding description in the embodiment of Figure 13. Details are not described again in this document.

[0269] S147: The central unit sends a path switching request message to a network core device, and the central unit receives the path switching request message.

[0270] S148: The network core device sends a path switching reply message to the central unit, and the source network device receives the path switching reply message.

[0271] Due to the mobility of the terminal device, the terminal device moves from an original central server unit or unit Petition 870260050283, dated 05 / 26 / 2026, pp. 66 / 104 In a 49 / 64 distributed server, the original server is transferred to a new central unit or distributed unit. In this scenario, the central unit notifies the network core device of a session or flow that requires path switching, so that the network core device can send downlink data and receive uplink data based on a switched path.

[0272] Specifically, when the central unit or the distributed unit performs access control, due to reasons such as resource limitation, the central unit or the distributed unit may only accept certain sessions in a handover request, and support only certain flows for an accepted session.

[0273] For example, the handover request message includes a distributed unit session P1, a distributed unit session P2, and a distributed unit session P3. Specifically, the source network device requests to transfer the distributed unit session P1, the distributed unit session P2, and the distributed unit session P3 from the endpoint device to a central unit and a distributed unit of a target network device. Distributed unit P1 session 1 includes a flow 1, a flow 2, and a flow 3. Distributed unit P2 session 2 includes a flow 4, a flow 5, and a flow 6. Distributed unit P3 session 3 includes a flow 7, a flow 8, and a flow 9.However, due to reasons such as resource limitations, the central unit or the distributed unit only allows handover of session 1 of distributed unit P and session 2 of distributed unit P, and only accepts handover of flow 1 and flow 2 to session 1 of distributed unit P. In this case, the central unit needs to add, to the path switching request to be sent to the network core device, identification information of a distributed unit P session whose handover is accepted, and identification information of a corresponding accepted flow.In other words, in the path switching request from the central unit to the network core device, the network core device needs to be notified that the central unit accepts handover of session 1 from distributed unit P and session 2 from distributed unit P, and regarding session 1 from distributed unit P, only flow 1 and flow 2 can be transferred to the central unit or the distributed unit.

[0274] Optionally, the central unit can additionally Petition 870260050283, dated 05 / 26 / 2026, pp. 67 / 104 50 / 64 add, to the path switching request to be sent to the network core device, identification information of a distributed unit P session whose handover is rejected. Optionally, the central unit may additionally add, to the path switching request to be sent to the network core device, identification information of a distributed unit P session whose handover is accepted, and identification information of a corresponding rejected flow, for example, an identifier of distributed unit P session 1 and an identifier of the corresponding flow 3.

[0275] For example, the information carried in the path switching request message can be represented as: List of sessions requiring path switching > PDU session identifier (PDU) Session ID) >>Flow ID / Identifier List (flow ID (list))

[0276] It can be understood that the PDU session identifier and flow identifier in the aforementioned table can be transmitted by the central unit to the network core device as an application layer message (e.g., an NGAP message), or they can be transmitted to the network core device with a container, or they can be transmitted to the network core device in another way. There is no limitation on this in this application.

[0277] After receiving the path switching request, the network core device performs a path switching operation and sends a path switching response message to the central unit. The response message carries an identifier of a PDU session that requires uplink path switching. Optionally, the response message may additionally include an identifier, which corresponds to the identifier of the PDU session requiring uplink path switching, of a flow that requires uplink path switching. This is because it is possible that only some flows will be successfully switched to a specific session. Petition 870260050283, dated 05 / 26 / 2026, pp. 68 / 104 51 / 64

[0278] It can be understood that the flow in this descriptive report can be a QoS flow, or it can be a data flow, or it can be a service flow, or it can be a data packet, and there is no limitation as to this in this request.

[0279] According to the communication method provided in embodiments of the present invention, the central unit notifies the network core device of a session or flow that requires path switching, so that the network core device can send downlink data and receive uplink data based on a switched path.

[0280] The method in embodiments of the present invention is described in detail above, and an apparatus in one embodiment of the present invention is provided below.

[0281] Figure 15 is a schematic diagram of modules of a communications apparatus according to an embodiment of the present invention. The communications apparatus 1500 may include a transmitter unit 151 and a receiver unit 152.

[0282] Transmitter unit 151 is configured to send a connection configuration request message to a central unit.

[0283] Receiver unit 152 is configured to receive a connection configuration reply message from the central unit.

[0284] The connection configuration request message or the connection configuration response message includes information about the network slice supported by the distributed unit.

[0285] In one implementation, the connection configuration response message additionally includes information about the network slice supported by the central unit.

[0286] In another implementation, the transmitting unit is additionally configured to send a configuration update message to the central unit, where the configuration update message includes updated information on the network slice supported by the distributed unit.

[0287] In yet another implementation, the network slice information supported by the distributed unit includes at least one or one Petition 870260050283, dated 05 / 26 / 2026, pp. 69 / 104 52 / 64 combination of the following: network slice indication information supported by at least one cell of the distributed unit; a cell identifier of at least one cell of the distributed unit and network slice indication information supported by each of the at least one cell; or an identifier of a tracking area or a registration area that corresponds to at least one cell of the distributed unit and network slice indication information supported by each tracking area or each registration area in the tracking area or registration area that corresponds to at least one cell.

[0288] According to the communications apparatus provided in this embodiment of the present invention, network slice information supported by the distributed unit is exchanged between the distributed unit and the central unit by means of a connection configuration process, so that a network slice-based service in a distributed unit and central unit architecture can be implemented.

[0289] Figure 16 is a schematic diagram of modules of another communications apparatus according to an embodiment of the present invention. The communications apparatus 1600 may include a receiver unit 161 and a transmitter unit 162.

[0290] Receiver unit 161 is configured to receive a connection configuration request message from a distributed unit.

[0291] Transmitting unit 162 is configured to send a connection configuration response message to the distributed unit.

[0292] The connection configuration request message or the connection configuration response message includes information about the network slice supported by the distributed unit.

[0293] In one implementation, the connection configuration response message additionally includes information about the network slice supported by the central unit.

[0294] In another implementation, the transmitting unit is additionally configured to send a configuration update message to the distributed unit, where the configuration update message includes updated information on the network slice supported by Petition 870260050283, dated 05 / 26 / 2026, pp. 70 / 104 53 / 64 central unit.

[0295] In yet another implementation, the configuration update message or the connection configuration response message additionally includes network slice configuration information. The network slice configuration information includes at least one of the following configuration information: Layer 1 protocol stack configuration information, Layer 2 protocol stack configuration information, physical resource information, frequency band information corresponding to a network slice, frequency information corresponding to a network slice, or status information supported by a network slice.

[0296] According to the communications apparatus provided in this embodiment of the present invention, network slice information supported by the distributed unit is exchanged between the central unit and the distributed unit by means of a connection configuration process, so that a network slice-based service in a distributed unit and central unit architecture can be implemented.

[0297] Figure 17 is a schematic diagram of modules of yet another communications apparatus according to an embodiment of the present invention. The communications apparatus 1700 may include a transmitter unit 171 and a receiver unit 172.

[0298] Transmitting unit 171 is configured to send a first message to a distributed unit, where the first message includes network slice indication information that corresponds to a session, a carrier, or a flow.

[0299] Receiver unit 172 is configured to receive a reply message from the distributed unit.

[0300] In one implementation, transmitter unit 171 is additionally configured to send a radio resource control message to a terminal device by use of the distributed unit, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established.

[0301] In another implementation, transmitter unit 171 is additionally configured to send a request message of Petition 870260050283, dated 05 / 26 / 2026, pp. 71 / 104 54 / 64 path switching to a network core device, where the path switching request message includes an identifier of a session successfully established by the central unit or the distributed unit, and / or an identifier of a flow that corresponds to the session identifier and that is successfully established by the central unit or the distributed unit.

[0302] In yet another implementation, the first message or the reply message additionally includes carrier duplication indication information.

[0303] In yet another implementation, the first message additionally includes UE-AMBR DU indication information, and the UE-AMBR DU indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0304] In yet another implementation, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack.

[0305] In yet another implementation, the source network device includes any of the following: the central unit, a source base station, a source central unit, and the network core device.

[0306] According to the communications apparatus provided in this embodiment of the present invention, since different network slices have different Layer 1 or Layer 2 configurations on one side of the RAN, different sessions may correspond to different network slices. During session setup or modification, the central unit notifies the distributed unit of network slice indication information corresponding to a session, carrier, or flow to be established or modified, and the distributed unit establishes or modifies the session, carrier, or flow on an indicated network slice, so that the distributed unit can accurately select a network slice, and can configure, based on the network slice information corresponding to the session, an L1 / L2 parameter corresponding to the network slice for the terminal device. Therefore, sessions belonging to different slices of Petition 870260050283, dated 05 / 26 / 2026, pp. 72 / 104 55 / 64 networks meet a specific requirement for QoS.

[0307] Figure 18 is a schematic diagram of modules of yet another communications apparatus according to an embodiment of the present invention. The communications apparatus 1800 may include a receiver unit 181 and a transmitter unit 182, and may additionally include a processing unit 183.

[0308] Receiver unit 181 is configured to receive a first message from a central unit, where the first message includes network slice indication information that corresponds to a session, a carrier, or a flow.

[0309] Transmitter unit 182 is configured to send a reply message to the central unit.

[0310] In one implementation, transmitter unit 182 is additionally configured to send a radio resource control message from the central unit to a terminal device, wherein the radio resource control message includes an identifier of a session, carrier, or stream that is successfully established.

[0311] In another implementation, the communications device 1800 additionally includes a processing unit 183, configured to determine whether or not the communications device supports a network slice that matches the network slice indication information.

[0312] In yet another implementation, the first message or the reply message additionally includes carrier duplication indication information.

[0313] In yet another implementation, the first message additionally includes UE-AMBR DU indication information, and the UE-AMBR DU indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

[0314] In yet another implementation, the first message additionally includes configuration information for a source network device for at least one protocol stack that corresponds to a carrier, and the at least one protocol stack includes an RLC protocol stack, a MAC protocol stack, and a PHY protocol stack. Petition 870260050283, dated 05 / 26 / 2026, pp. 73 / 104 56 / 64

[0315] In yet another implementation, the source network device includes any of the following: the central unit, a source base station, a source central unit, and the network core device.

[0316] According to the communications apparatus provided in this embodiment of the present invention, since different network slices have different Layer 1 or Layer 2 configurations on one side of the RAN, different sessions can correspond to different network slices. During session setup or modification, the central unit notifies the distributed unit of network slice indication information corresponding to a session, carrier, or flow to be established or modified, and the distributed unit establishes or modifies the session, carrier, or flow on an indicated network slice, so that the distributed unit can accurately select a network slice, and can configure, based on the network slice information corresponding to the session, an L1 / L2 parameter corresponding to the network slice for the terminal device. Therefore, sessions belonging to different network slices meet a specific requirement for QoS.

[0317] An embodiment of the present invention further provides a communications apparatus. The communications apparatus may be a distributed unit in the aforementioned communications system, and the communications apparatus may use a hardware architecture shown in Figure 19. The communications apparatus may include a receiver, a transmitter, a memory, and a processor, and the receiver, transmitter, memory, and processor are connected to each other by the use of a bus. Related functions implemented by the receiver unit 152 in Figure 15 may be implemented by the receiver, and related functions implemented by the transmitter unit 151 may be implemented by the transmitter.Related functions implemented by receiver unit 181 in Figure 18 can be implemented by the receiver, related functions implemented by transmitter unit 182 can be implemented by the transmitter, and related functions implemented by processing unit 183 can be implemented by using one or more processors.

[0318] Memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), and programmable read-only memory. Petition 870260050283, dated 05 / 26 / 2026, pp. 74 / 104 57 / 64 erasable (Erasable Programmable Read Only Memory, EPROM), or a compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), and the memory is configured to store instructions and related data.

[0319] The receiver is configured to receive data and / or a signal, and the transmitter is configured to send data and / or a signal. The transmitter and receiver can be independent components, or they can be an integrated component.

[0320] The processor may include one or more processors, for example, including one or more central processing units (CPUs). When the processor is a CPU, the CPU is a single-core CPU, or it may be a multi-core CPU.

[0321] The memory is configured to store program code and data from a network device.

[0322] In one implementation, the transmitter is configured to send a connection configuration request message to a central unit, for example, performing step S401 in the mode shown in Figure 4, and the receiver is configured to receive a connection configuration response message from the central unit, for example, performing step S402 in the mode shown in Figure 4.

[0323] In another implementation, the receiver is configured to receive an initial message from a central unit, for example, performing step S901 in the mode shown in Figure 9, and the transmitter is configured to send a reply message to the central unit, for example, performing step S902 in the mode shown in Figure 9.

[0324] For details, refer to the description in the aforementioned method modalities. Details are not described again in this document.

[0325] It may be understood that Figure 19 shows only a simplified design of the communications apparatus. In actual application, the communications apparatus may additionally include other necessary elements, including, but not limited to, any number of transceivers, processors, controllers, memories, and the like, and all communication apparatus that may implement the modes of Petition 870260050283, dated 05 / 26 / 2026, pp. 75 / 104 58 / 64 of the present invention are covered by the scope of protection of the present invention.

[0326] An embodiment of the present invention further provides a communications apparatus. The communications apparatus may be a central unit in the aforementioned communications system, and the communications apparatus may use a hardware architecture shown in Figure 19. The communications apparatus may include a receiver, a transmitter, a memory, and a processor, and the receiver, transmitter, memory, and processor are connected to each other by the use of a bus. Related functions implemented by the receiver unit 161 in Figure 16 may be implemented by the receiver, and related functions implemented by the transmitter unit 162 may be implemented by the transmitter. Related functions implemented by the receiver unit 172 in Figure 17 may be implemented by the receiver, and related functions implemented by the transmitter unit 171 may be implemented by the transmitter.

[0327] Memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and memory is configured to store instructions and related data.

[0328] The receiver is configured to receive data and / or a signal, and the transmitter is configured to send data and / or a signal. The transmitter and receiver may be independent components, or they may be an integrated component.

[0329] The processor may include one or more processors, for example, including one or more central processing units (CPUs). When the processor is a CPU, the CPU is a single-core CPU, or it may be a multi-core CPU.

[0330] The memory is configured to store program code and data from a network device.

[0331] In one implementation, the receiver is configured to receive a connection configuration request message from a Petition 870260050283, dated 05 / 26 / 2026, pp. 76 / 104 59 / 64 distributed unit, for example, perform step S401 in the mode shown in Figure 4, and the transmitter is configured to send a connection configuration response message to the distributed unit, for example, perform step S402 in the mode shown in Figure 4.

[0332] In another implementation, the transmitter is configured to send an initial message to the distributed unit, for example, performing step S901 in the mode shown in Figure 9, and the receiver is configured to receive a reply message from the distributed unit, for example, performing step S902 in the mode shown in Figure 9.

[0333] For details, refer to the description in the aforementioned method modalities. Details are not described again in this document.

[0334] It may be understood that Figure 19 shows only a simplified design of the communications apparatus. In actual application, the communications apparatus may additionally include other necessary elements, including, but not limited to, any number of transceivers, processors, controllers, memories, and the like, and all communications apparatus that may implement embodiments of the present invention are covered by the scope of protection of the present invention.

[0335] One embodiment of the present invention further provides a communications system, including the aforementioned communication apparatus.

[0336] Figure 20 is a schematic structural diagram of a simplified terminal device. To facilitate understanding and illustrate more conveniently, in Figure 20, a mobile phone is used as an example of the terminal device. As shown in Figure 20, the terminal device includes a processor, memory, a radio frequency circuit, an antenna, and an input / output device. The processor is primarily configured to: process a communications protocol and communication data, and control the terminal device, to execute a software program, process data from the software program, and the like. The memory is configured to store a software program and data. The circuit of Petition 870260050283, dated 05 / 26 / 2026, pp. 77 / 104 60 / 64 GHz radio frequency is primarily used for conversion between a baseband signal and a radio frequency signal, and for processing the radio frequency signal. The antenna is mainly configured to receive and transmit a radio frequency signal in an electromagnetic waveform. The input / output device, such as a touchscreen, display, or keyboard, is mainly configured to receive data fed by a user and output data to the user. It should be noted that some types of terminal devices may not have an input / output device.

[0337] When data needs to be sent, the processor performs baseband processing on the data to be sent and emits a baseband signal to the radio frequency circuit. After performing radio frequency processing on the baseband signal, the radio frequency circuit sends the radio frequency signal using the antenna in the form of an electromagnetic wave. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal using the antenna, converts the radio frequency signal into a baseband signal, and emits the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data. For ease of description, Figure 20 shows only one memory and one processor. In a real terminal device product, there may be one or more processors and one or more memories.Memory can also be referred to as a storage medium, a storage device, or similar. Memory can be arranged independently of the processor, or it can be integrated with the processor. There is no limitation regarding this aspect in this application.

[0338] In this embodiment of this application, the antenna and radio frequency circuit that have a receive / transmit function can be considered as a receiver unit and a transmitter unit (or can be collectively referred to as a transceiver) of the terminal device, and the processor that has a processing function can be considered as a processing unit of the terminal device. As shown in Figure 20, the terminal device includes a receiver unit 2001, a processing unit 2002, and a transmitter unit 2003. The unit Petition 870260050283, dated 05 / 26 / 2026, pp. 78 / 104 The receiving unit 2001 may also be referred to as a receiving device, a receiver, a receiving circuit, or the like, and the transmitting unit 2003 may also be referred to as a transmitting device, a transmitter, a transmitting circuit, or the like. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing apparatus, or the like.

[0339] For example, in one embodiment, receiver unit 2001 is configured to receive a radio resource control message, for example, perform S104 in the mode shown in Figure 10, S113 in the mode shown in Figure 11, or S135 in the mode shown in Figure 13. Transmitter unit 2003 sends a radio resource response message to a central unit, for example, perform S105 in the mode shown in Figure 10, S115 in the mode shown in Figure 11, or S136 in the mode shown in Figure 13.

[0340] According to the terminal device provided in this embodiment of the present invention, the terminal device obtains an identifier of a session, carrier, or stream that is successfully established, to conduct a session with a network device.

[0341] An embodiment of the present invention further provides a computer-readable storage medium. The computer-readable storage medium stores an instruction, and when the instruction is executed on a computer, the computer performs the methods in the aforementioned aspects.

[0342] An embodiment of the present invention further provides a computer program product including an instruction. When the instruction is executed on a computer, the computer performs the methods in the aforementioned aspects.

[0343] A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this descriptive report, algorithm units and steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use Petition 870260050283, dated 05 / 26 / 2026, pp. 79 / 104 62 / 64 different methods exist for implementing the functions described for each particular application, but it should not be considered that the implementation goes beyond the scope of this request.

[0344] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed process of operation of the aforementioned system, apparatus, and unit, reference may be made to a corresponding process in the aforementioned method embodiments, and details are not described again in the present document.

[0345] In the descriptive report, claims, and drawings attached to this application, the terms first, second, third, fourth, and so forth are intended to distinguish between different objects, but do not indicate a particular order. Furthermore, the terms including and having, and any other variants thereof, are intended to encompass non-exclusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or units is not limited to the steps or units listed, but optionally additionally includes a step or unit not listed, or optionally additionally includes another step or unit inherent to the process, method, product, or device.

[0346] A person of average skill in the technique can understand that sequential numbers of the aforementioned processes do not signify execution sequences in various modalities of this request. The execution sequences of the processes must be determined according to the functions and internal logic of the processes, and should not be interpreted as any limitation to the implementation processes of the modalities of this request.

[0347] In the various embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the described embodiment of the apparatus is merely an example. For example, division into units is merely division in logical function and may be another division in the actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not realized. Furthermore, mutual couplings Petition 870260050283, dated 05 / 26 / 2026, pp. 80 / 104 63 / 64 or direct couplings or communication connections shown or discussed can be implemented using some interfaces. Indirect couplings or communication connections between devices or units can be implemented electronically, mechanically, or in other ways.

[0348] The units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one position, or may be distributed across a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the modal solutions.

[0349] Furthermore, functional units in the modalities of this application may be integrated into a processing unit, or each of the units may exist physically on its own, or two or more units may be integrated into a unit.

[0350] All or some of the aforementioned embodiments may be implemented by the use of software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented wholly or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedure or functions according to the embodiments of the present invention are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instruction may be stored on a computer-readable storage medium, or it may be transmitted by the use of computer-readable storage media.Computer instructions can be transmitted from one site, computer, server, or data center to another network site, computer, server, or data center in a wired manner (e.g., a coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or a wireless manner (e.g., infrared, radio, or microwave). The computer-readable storage medium can be any media that can be. Petition 870260050283, dated 05 / 26 / 2026, pp. 81 / 104 64 / 64 used is accessible by a computer, or a data storage device, such as a server or data center, integrating one or more media that can be used. The media that can be used can be magnetic media (e.g., a floppy disk, a hard disk, or magnetic tape), optical media (e.g., a digital versatile disc (DVD)), semiconductor media (e.g., a solid-state drive (SSD)), or similar.

[0351] A person of ordinary skill in the art can understand that all or some of the processes of the methods in the embodiments can be implemented by a computer program that instructs relevant hardware. The program can be stored on a computer-readable storage medium. When the program is executed, the processes of the methods in the embodiments are performed. The aforementioned storage medium includes: any medium that can store program code, such as read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. Petition 870260050283, dated 05 / 26 / 2026, pp. 82 / 104

Claims

1 / 5 CLAIMS 1. Communication method, CHARACTERIZED in that the method comprises: sending (S901), by a central unit of a radio access network device, a first message to a distributed unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and receiving, by the central unit, a reply message from the distributed unit.

2. Method according to claim 1, CHARACTERIZED in that the first message additionally comprises a carrier identifier.

3. A method according to claim 1 or 2, characterized in that the central unit and the distributed unit belong to a target base station, and the first message comprises configuration information from a source network device for at least one protocol stack that corresponds to the carrier.

4. A method according to claim 3, characterized in that at least one protocol stack comprises at least one of: a Radio Link Control (RLC) protocol stack, a Medium Access Control (MAC) protocol stack, or a Physical Layer (PHY) protocol stack.

5. Method according to claim 3, CHARACTERIZED in that the source network device comprises any one of the following: a source base station, a source access and mobility management network element, or a source central unit.

6. Method, according to any one of claims 1 to 5, CHARACTERIZED in that the first message is a request message for EU context configuration.

7. Method, according to any one of claims 1 to 6, CHARACTERIZED in that the network slice indication information comprises single network slice selection assistance information Petition 870260050283, dated 05 / 26 / 2026, page 83 / 104 2 / 5 (S-NSSAI).

8. A method according to any one of claims 1 to 7, characterized in that the first message additionally comprises distributed unit UE-AMBR maximum aggregation bit rate indication information, and the DU UE-AMBR indication information is used to indicate a maximum aggregation bit rate applied by the distributed unit to the terminal device.

9. A method according to any one of claims 1 to 8, characterized in that the method further comprises: sending, by the central unit, a radio resource control message to the terminal device using the distributed unit, wherein the radio resource control message comprises a carrier identifier that is successfully established.

10. A method, according to any one of claims 1 to 9, CHARACTERIZED in that the method further comprises: sending, by the central unit, a path switching request message to a network core device, wherein the path switching request message comprises an identifier of a session successfully established by the central unit or the distributed unit, and / or an identifier of a flow that corresponds to the session identifier and that is successfully established by the central unit or the distributed unit.

11. Communication method, CHARACTERIZED in that the method comprises: receiving, by a distributed unit of a radio access network device, a first message from a central unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and sending (S902), by the distributed unit, a reply message to the central unit.

12. Communication apparatus (170), CHARACTERIZED in that the communication apparatus (170) is a central unit of a radio access network device, and the central unit comprises: a transmitting unit (171), configured to send a first message to a distributed unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and a receiving unit (172), configured to receive a reply message from the distributed unit.

13. Communication apparatus (180), CHARACTERIZED in that the communication apparatus (180) is a distributed unit of a radio access network device, and the distributed unit comprises: a receiving unit (181), configured to receive a first message from a central unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and a transmitting unit (182), configured to send a reply message to the central unit.

14. Computer-readable storage media, CHARACTERIZED in that the computer-readable storage media stores an instruction, and when the instruction is executed on a computer, the method as defined in any one of claims 1 to 11 is performed.

15. Communication apparatus, CHARACTERIZED by the fact that the communication apparatus is a central unit of a radio access network device, and the central unit comprises a receiver, a transmitter, a memory, and a processor, wherein the memory stores instructions, and the processor is configured to invoke the instructions to perform the following operations: controlling the transmitter to send a first message to a distributed unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier to a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and controlling the receiver to receive a reply message from the distributed unit.

16. Communication apparatus, CHARACTERIZED by the fact that the communication apparatus is a distributed unit of a radio access network device, and the central unit comprises a receiver, a transmitter, a memory, and a processor, wherein the memory stores instructions, and the processor is configured to invoke the instructions to perform the following operations: controlling the receiver to receive a first message from a central unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and controlling the transmitter to send a reply message to the central unit.

17. Communication method, CHARACTERIZED in that it comprises: sending (S901), by a central unit of a radio access network device, a first message to a distributed unit of the radio access network device, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and sending (S902), by the distributed unit, a reply message to the central unit.

18. Communication system, CHARACTERIZED by the fact that it comprises a central unit and a distributed unit, wherein the central unit is configured to send a first message to the distributed unit, wherein the first message is used to request the distributed unit to establish a carrier for a terminal device, and the first message comprises network slice indication information corresponding to the carrier; and Petition 870260050283, dated 05 / 26 / 2026, p. 86 / 104 5 / 5 the distributed unit is configured to send a reply message to the central unit. Petition 870260050283, dated 05 / 26 / 2026, p. 87 / 104