CN111866908A - A communication system and network equipment - Google Patents

Abstract

The present application provides a communication system and network equipment, in order to reduce the transmission delay of data transmission and save the cost. The communication system may include: a first network unit and a second network unit, the first network unit and the second network unit communicate through a communication interface, wherein the first network unit is used to implement: a user plane processing function corresponding to layer 1, a layer The user plane processing function corresponding to 2, and the user plane processing function corresponding to the user plane function UPF; the second network unit is used to implement: a part of the radio resource control RRC function and the core network function, wherein the core network function includes one or more of the following Item: Access and Mobility Management Function AMF, Session Management Function SMF, Policy Control Function PCF, or Authentication Service Function AUSF.

Description

A communication system and network equipment

technical field

The present application relates to the field of communication, and more particularly, to a communication system and a network device.

Background technique

In the Industrial Internet, there are some requirements for industrial control, such as end-to-end ultra-reliable and low latency communication (URLLC), low cost, and rapid deployment. Taking the transmission delay as an example, the end-to-end transmission delay of the user plane required by industrial control should be at least less than 2 milliseconds (millisecond, ms).

In the 5th Generation (5G) network of the 3rd Generation Partnership Project (3GPP), the transmission delay of data from one terminal device to another terminal device is much greater than 2ms, which cannot meet the requirements of industrial control. Low latency requirements.

In addition, the network nodes and functions in the current 3GPP 5G network are complex, resulting in high implementation costs.

Then, how to reduce the delay as much as possible is an urgent problem to be solved.

SUMMARY OF THE INVENTION

The present application provides a communication system and network equipment, so as to reduce the transmission delay of data transmission.

In a first aspect, a communication system is provided, the communication system may include: a first network unit and a second network unit, the first network unit and the second network unit communicate through a communication interface, wherein the first network unit and the second network unit communicate A network element is used to implement: the user plane processing function corresponding to layer 1, the user plane processing function corresponding to layer 2, and the user plane processing function corresponding to the user plane function UPF; the second network element is used to implement: the first wireless Resource control RRC function and core network function; wherein, the core network function includes one or more of the following: access and mobility management function AMF, session management function SMF, policy control function PCF, or authentication service function AUSF.

Based on the above technical solutions, with the communication system provided by the embodiments of the present application, the network part may include a first network unit and a second network unit, which can not only implement corresponding network functions, but also meet the requirements of vertical industries such as industrial control when the communication network is low. Extend the need for reliability, low cost, and rapid deployment. In addition, the first network element implements: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane processing function corresponding to the user plane function UPF, so that when data is transmitted, such as data from a terminal device To another terminal device, through the first network unit, the data can be quickly transmitted to another terminal device, avoiding the need to first pass through the core network and then sending it to another terminal device, so that low-latency transmission can be achieved, and ultra-high-speed transmission can be supported. Low-latency services.

Optionally, the user plane processing function (handling) corresponding to Layer 1 or Layer 2 may include, but is not limited to, one or more of the following: functions corresponding to Service Data Adaptation Protocol (SDAP), packet data The function corresponding to the Packet Data Convergence Protocol (PDCP), the function corresponding to the Radio Link Control Protocol (Radio Link Control, RLC), the function corresponding to the Media Access Control (MAC) layer, or the physical layer (physical layer) layer, PHY) corresponding functions.

Optionally, the user plane processing function corresponding to the user plane function UPF, for example, may include but not limited to one or more of the following: data to QoS flow, QoS flow to DRB mapping function, or data directly to DRB mapping function, etc. .

With reference to the first aspect, in some implementations of the first aspect, the first network element is further configured to implement a second RRC function, and the second RRC function includes: configuring one or more of the following: special Cell configuration (specialcell configuration, SpCellConfig), secondary cell configuration (SCell configuration, SCellConfig), radio link control configuration (RLC configuration, RLC-config), media intervention control layer cell group configuration (MAC-cell group configuration, MAC-cellGroupConfig ), or physical cell group configuration (physical cellgroup config, PhysicalCellGroupConfig). The specific content of these configurations can refer to 3GPPTS38.331v15.4.0.

The first network element may perform (or process, or perform, or configure) one or more of the following configurations: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig.

Optionally, a special cell (SpCell, or may also be referred to as a primary cell), if it is a master base station or a master node (master node, MN), the primary cell may refer to a primary cell (primary cell, PCell); if it is a secondary base station Or a secondary node (secondary node, SN), the primary cell may refer to a primary secondary cell (primary secondary cell, PSCell).

Optionally, the second RRC function can be used to configure parameters related to one or more of the following functions: power control, random access, beam management, hybrid automatic repeat request (HARQ), physical layer measurement, link adaptation, scheduling Request, uplink and downlink scheduling, rate matching, automatic repeat request ARQ, discontinuous reception DRX.

Based on the foregoing technical solutions, the first network unit may be used for any one or more of the foregoing parameter configurations.

With reference to the first aspect, in some implementations of the first aspect, the SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

The first network element may perform (or process, or perform) one or more of the following configurations: cell or BWP related configuration, CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the first aspect, in some implementations of the first aspect, the cell or bandwidth part BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel.

The first network element may be configured with one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.

Optionally, the physical channels include: a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical broadcast channel (physical broadcast channel, PBCH), a physical random access channel ( physical random access channel, PRACH), physical uplink shared channel (physical uplink shared channel, PUSCH), physical uplink control channel (physical uplink control channel, PUCCH).

With reference to the first aspect, in some implementations of the first aspect, the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or radio bearer configuration.

The second network element may implement (or process, or execute): RRM measurement configuration and/or radio bearer configuration.

Based on the above technical solutions, the first network unit performs part of the RRC function, and the second network unit performs another part of the RRC function, so that the system can quickly adapt to changes in the state of the radio link of the air interface and ensure the transmission performance of the air interface.

Optionally, the first RRC function and the second RRC function may be completely different, or may be partially the same, and the functions may be flexibly deployed on the two units as required during specific implementation, which is not strictly limited.

Optionally, the radio bearer configuration includes, for example, configuring SDAP and PDCP-related parameters of the radio bearer, such as Radiobearerconfig and RRMmeasurementconfig in 3GPPTS 38.331v15.4.0.

The second network element may configure UE-specific RRC process-related parameters, for example, including but not limited to: RRM measurement, and/or SDAP and PDCP-related parameters of the radio bearer, as in 3GPPTS 38.331v15.4.0 Radiobearerconfig and RRMmeasurementconfig.

With reference to the first aspect, in some implementations of the first aspect, the layer 1 includes: a physical layer PHY; and/or the layer 2 includes: a service data adaptation protocol SDAP layer, a packet data convergence protocol PDCP layer, Radio link layer control protocol RLC layer, media intervention control layer MAC layer.

With reference to the first aspect, in some implementations of the first aspect, the first network element is further configured to implement mapping of downlink data to data radio bearers DRB.

With reference to the first aspect, in some implementations of the first aspect, the second network unit is further configured to implement network capability opening and/or network data analysis functions.

Based on the above technical solution, the network capability opening function is realized through the second network unit, which can facilitate vertical industry service providers or third-party application developers to manage and control the network or obtain network information. In addition, by implementing a network data analytics function (NWDAF) through the second network unit, data collection and big data analysis can be performed in the second network unit, thereby making the network intelligent.

With reference to the first aspect, in some implementations of the first aspect, the first network unit is a local transmission unit LTU, and the second network unit is a remote control unit RCU.

In a second aspect, a communication system is provided, and the communication system may include: the first network element and the second network element communicate through a communication interface, and the second network element is configured to implement the first radio resource control RRC The first network element is configured to implement the second RRC function, wherein the second RRC function includes: configuring one or more of the following: special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC -config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig; the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or radio bearer configuration.

Based on the above technical solution, by configuring one or more items listed above by the first network unit, the second network unit may no longer implement this part of the RRC function (ie, the second RRC function), that is, the RCU may implement the first RRC function. Therefore, the system can quickly adapt to changes in the state of the radio link of the air interface and ensure the transmission performance of the air interface.

With reference to the second aspect, in some implementations of the second aspect, the first network element is further configured to implement mapping of downlink data to data radio bearers DRB.

With reference to the second aspect, in some implementations of the second aspect, the second network unit is further configured to implement network capability opening and/or network data analysis related functions.

With reference to the second aspect, in some implementations of the second aspect, the SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

The first network element may perform (or process, or perform) one or more of the following configurations: cell or BWP related configuration, CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the second aspect, in some implementations of the second aspect, the cell or bandwidth part BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel.

Optionally, the physical channels include: PDSCH, PDCCH, PBCH, PRACH, PUSCH, and PUCCH.

With reference to the second aspect, in some implementations of the second aspect, the layer 1 includes: a physical layer PHY; and/or the layer 2 includes: a service data adaptation protocol SDAP layer, a packet data convergence protocol PDCP layer, Radio link layer control protocol RLC layer, media intervention control layer MAC layer.

With reference to the second aspect, in some implementations of the second aspect, the first network unit is a local transmission unit LTU, and the second network unit is a remote control unit RCU.

In a third aspect, a network device is provided, the network device may include: a processor and a communication interface, the processor is configured to implement: a function corresponding to the service data adaptation protocol SDAP, a function corresponding to the packet data convergence protocol PDCP, a wireless link The function corresponding to the road layer control protocol RLC, the function corresponding to the media intervention control layer MAC, the function corresponding to the physical layer PHY, and the user plane processing function corresponding to the user plane function UPF; the communication interface is used for communication with the target device.

Based on the above technical solutions, the network device can implement: the user plane processing function corresponding to layer 1 (that is, the function corresponding to the physical layer PHY), the user plane processing function corresponding to layer 2 (that is, the function corresponding to the service data adaptation protocol SDAP, packet data aggregation) The function corresponding to the protocol PDCP, the function corresponding to the radio link layer control protocol RLC, the function corresponding to the media intervention control layer MAC), and the user plane processing function corresponding to the user plane function UPF, so that when data is transmitted, such as data from a terminal From the device to another terminal device, through the first network unit, data can be quickly transmitted to another terminal device, avoiding the need to pass through the core network and then sending it to another terminal device, so that low-latency transmission can be achieved, and it can support Ultra-low latency service

With reference to the third aspect, in some implementations of the third aspect, the processor further implements a second RRC function, and the second RRC function includes: configuring one or more of the following: special cell configuration SpCellConfig, Secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig.

With reference to the third aspect, in some implementations of the third aspect, the SpCellConfig includes at least one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate Matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the third aspect, in some implementations of the third aspect, the cell or BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block , or physical channel.

Optionally, the physical channels include: PDSCH, PDCCH, PBCH, PRACH, PUSCH, and PUCCH.

With reference to the third aspect, in some implementations of the third aspect, the processor is further configured to implement: downlink data to data radio bearer DRB mapping.

In a fourth aspect, a network device is provided, the network device may include: a processor and a communication interface, the processor is configured to implement: a first RRC function and a core network function, the core network function includes one or more of the following Item: access and mobility management function AMF, session management function SMF, policy control function PCF, or authentication service function AUSF, wherein the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or radio bearer configuration ; the communication interface is used to communicate with the target device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the processor is further configured to implement functions related to network capability opening and network data analysis.

In a fifth aspect, a method for data transmission is provided, and the method may be executed by a network device, or may also be executed by a chip or circuit configured in the network device, which is not limited in this application.

The method may include: a first network device receives a data packet from a first terminal device; and the first network device routes the data packet to a destination address corresponding to the data packet.

Based on the above technical solution, through the direct routing of the first network device, the data can be quickly routed to the destination address, avoiding the need to pass through the core network first and then route to the destination address corresponding to the data packet, so that the terminal device (for example, denoted as the first destination address) can be realized. The low-latency transmission between a terminal device) and other devices can support ultra-low-latency services.

With reference to the fifth aspect, in some implementations of the fifth aspect, the destination address corresponds to one or more of the following: a data network, a second terminal device, a network device where the second terminal device is located, the first A native application of a network device, or a second network device.

Based on the above technical solutions, through the direct routing of the first network device, data can be quickly sent to the data network, the second terminal device, the network device where the second terminal device is located, the local application of the first network device, or the second network device, etc. One or more of the routes avoid the need to pass through the core network and then send to these devices, so that the terminal device (for example, denoted as the first terminal device) and network device applications or other terminal devices (for example, denoted as the second terminal device) Low-latency transmission between terminal devices) can support ultra-low-latency services. In addition, the first network device may also route the data packet to the second network device, and further, the second network device may route the data packet to the data network and so on.

Optionally, the second terminal device may include: a terminal device under the first network device, and/or may also be a terminal device under other network devices.

The first network device may route the data packets to other network devices first, and then the other network devices route the data to the data network, and then transmit the data to the second terminal device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the first network device is configured to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane function corresponding to UPF User plane processing function.

With reference to the fifth aspect, in some implementations of the fifth aspect, the user plane processing function corresponding to the layer 1 and the user plane processing function corresponding to the layer 2 include one or more of the following: functions corresponding to SDAP , the function corresponding to PDCP, the function corresponding to RLC, the function corresponding to MAC, or the function corresponding to PHY.

With reference to the fifth aspect, in some implementations of the fifth aspect, the second network device is configured to implement a first RRC function, and the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or Radio bearer configuration.

With reference to the fifth aspect, in some implementations of the fifth aspect, the first network device is configured to implement a second radio resource control RRC function, where the second RRC function includes: configuring one or more of the following : Special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig.

With reference to the fifth aspect, in some implementations of the fifth aspect, the SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the fifth aspect, in some implementations of the fifth aspect, the cell or bandwidth part BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel.

With reference to the fifth aspect, in some implementations of the fifth aspect, the data packet is not processed by the service data adaptation protocol SDAP entity.

With reference to the fifth aspect, in some implementations of the fifth aspect, the method further includes: the first network device sets a quality of service QoS reflection function in the PDCP layer of the radio bearer RB corresponding to the data packet.

In a sixth aspect, a data transmission method is provided, the method may include: a first network device receiving a data packet from a terminal device; the first network device routing the data packet to a second network device; the The second network device routes the data packet to the data network.

Based on the above technical solutions, when the first network device is not directly connected to the data network, the routing function module of the first network device can forward the uplink data to the second network device by routing, and then the second network device will forward the uplink data to the second network device. The upstream data is routed to the data network.

With reference to the sixth aspect, in some implementations of the sixth aspect, the first network device is configured to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane function corresponding to UPF User plane processing function.

With reference to the sixth aspect, in some implementations of the sixth aspect, the user plane processing function corresponding to the layer 1 and the user plane processing function corresponding to the layer 2 include one or more of the following: functions corresponding to SDAP , the function corresponding to PDCP, the function corresponding to RLC, the function corresponding to MAC, or the function corresponding to PHY.

With reference to the sixth aspect, in some implementations of the sixth aspect, the second network device is configured to implement the first RRC function, and the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or or radio bearer configuration.

With reference to the sixth aspect, in some implementations of the sixth aspect, the first network device is configured to implement a second radio resource control RRC function, wherein the second RRC function includes: configuring one or more of the following Item: special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig.

With reference to the sixth aspect, in some implementations of the sixth aspect, the SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the sixth aspect, in some implementations of the sixth aspect, the cell or bandwidth part BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel.

With reference to the sixth aspect, in some implementations of the sixth aspect, the data packet is not processed by the service data adaptation protocol SDAP entity.

With reference to the sixth aspect, in some implementations of the sixth aspect, the method further includes: the first network device sets a quality of service QoS reflection function in the PDCP layer of the radio bearer RB corresponding to the data packet.

In a seventh aspect, a communication device is provided, comprising a processing unit and a communication unit, the communication unit is configured to receive a data packet from a first terminal device; the processing unit is configured to: send the data packet to the data packet The destination address route corresponding to the packet.

With reference to the seventh aspect, in some implementations of the seventh aspect, the destination address corresponds to one or more of the following: a data network, a second terminal device, a network device where the second terminal device is located, the first A native application of a network device, or a second network device.

With reference to the seventh aspect, in some implementations of the seventh aspect, the processing unit is further configured to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane function corresponding to UPF User plane processing function.

With reference to the seventh aspect, in some implementations of the seventh aspect, the user plane processing function corresponding to the layer 1 and the user plane processing function corresponding to the layer 2 include one or more of the following: functions corresponding to SDAP , the function corresponding to PDCP, the function corresponding to RLC, the function corresponding to MAC, or the function corresponding to PHY.

With reference to the seventh aspect, in some implementations of the seventh aspect, the second network device is configured to implement a first RRC function, and the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or Radio bearer configuration.

With reference to the seventh aspect, in some implementations of the seventh aspect, the processing unit is further configured to implement: a second radio resource control RRC function, wherein the second RRC function includes: configuring one or more of the following : Special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig.

With reference to the seventh aspect, in some implementations of the seventh aspect, the SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; the SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

With reference to the seventh aspect, in some implementations of the seventh aspect, the cell or bandwidth part BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel.

With reference to the seventh aspect, in some implementations of the seventh aspect, the data packet is not processed by the service data adaptation protocol SDAP entity.

With reference to the seventh aspect, in some implementations of the seventh aspect, the method further includes: the processing unit sets a quality of service QoS reflection function in the PDCP layer of the radio bearer RB corresponding to the data packet.

In an eighth aspect, a communication device is provided, which has the function of implementing the first network unit of the first aspect or the second aspect. These functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In a ninth aspect, a communication device is provided, which has the function of implementing the second network unit of the first aspect or the second aspect. These functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

A tenth aspect provides a communication apparatus having the function of implementing the network device of the third aspect. These functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In an eleventh aspect, a communication apparatus is provided, which has the function of implementing the network device of the fourth aspect. These functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

A twelfth aspect provides a communication device, the device includes a memory, a communication interface and a processor, wherein the memory is used to store computer programs or instructions, the processor is coupled with the memory and the communication interface, when the processor executes the When a computer program or instruction is used, the apparatus is made to perform the function of the first network element of the first aspect or the second aspect.

A thirteenth aspect provides a communication device, the device includes a memory, a communication interface and a processor, wherein the memory is used to store computer programs or instructions, the processor is coupled with the memory and the communication interface, when the processor executes the When a computer program or instruction is used, the apparatus is made to perform the function of the second network element of the first aspect or the second aspect.

A fourteenth aspect provides a communication device comprising a memory, a communication interface and a processor, wherein the memory is used to store computer programs or instructions, the processor is coupled to the memory and the communication interface, and when the processor executes the When a computer program or instruction is used, the apparatus is made to perform the function of the network device of the third aspect.

A fifteenth aspect provides a communication device comprising a memory, a communication interface and a processor, wherein the memory is used to store computer programs or instructions, the processor is coupled to the memory and the communication interface, and when the processor executes the When a computer program or instruction is used, the apparatus is made to perform the function of the network device of the fourth aspect.

A sixteenth aspect provides a communication device, the device includes a memory, a communication interface and a processor, wherein the memory is used to store computer programs or instructions, the processor is coupled with the memory and the communication interface, when the processor executes the When a computer program or instruction is used, the apparatus is made to perform the function of the first network device of the fifth aspect.

A seventeenth aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to execute the first aspect of the first aspect or the second aspect The function of the network element.

In an eighteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to execute the first aspect or the second aspect of the second aspect The function of the network element.

In a nineteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform the function of the network device of the third aspect.

In a twentieth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run on a computer, the computer is made to perform the function of the network device of the fourth aspect.

A twenty-first aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is run on a computer, the computer program code causes the computer to execute the first network device of the fifth aspect above. Function.

A twenty-second aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the first network unit of the first aspect or the second aspect is implemented. Function.

A twenty-third aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the second network unit of the first aspect or the second aspect is implemented. Function.

A twenty-fourth aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the functions of the network device of the third aspect are implemented.

A twenty-fifth aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the functions of the network device of the fourth aspect above are implemented.

A twenty-sixth aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the function of the first network device of the fifth aspect is implemented.

In a twenty-seventh aspect, a communication system is provided, the communication system including the first network device and the second network device as described above.

Description of drawings

Fig. 1 is a schematic diagram of 3GPP 5G system architecture;

2 and 3 are schematic diagrams of the NG-RAN architecture;

FIG. 4 is a schematic diagram of the distribution of the air interface protocol stack when the CU is divided into CU-UP and CU-CP;

5 is a schematic block diagram of a communication system provided according to an embodiment of the present application;

6 is a schematic block diagram of yet another communication system provided according to an embodiment of the present application;

7 is a schematic block diagram of a network device provided according to an embodiment of the present application;

8 is a schematic block diagram of yet another network device provided according to an embodiment of the present application;

FIG. 9 is a schematic interaction diagram of a terminal device access process applicable to an embodiment of the present application;

FIG. 10 is a schematic interaction diagram of data transmission applicable to an embodiment of the present application;

Fig. 11 is a schematic diagram of the QoS framework defined by the existing protocol of 3GPP NR;

12 is a schematic diagram of a PDCP PDU format applicable to an embodiment of the present application;

13 is a schematic block diagram of a communication device provided according to an embodiment of the present application;

14 is a schematic structural diagram of a communication device provided according to an embodiment of the present application;

FIG. 15 is another schematic structural diagram of a communication apparatus provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application may be applied to various communication systems, for example, a fifth generation (5th Generation, 5G) system, a new radio (New Radio, NR), or a future communication system.

It should be understood that the embodiments of the present application do not specifically limit the specific structure of the execution body of the methods provided by the embodiments of the present application, as long as the methods provided by the embodiments of the present application can be executed, or the methods provided by the embodiments of the present application can be recorded through operation records. The program of the code can be communicated according to the method provided by the embodiment of the present application. For example, the execution body of the method provided in the embodiment of the present application may be a terminal or a network device, or a functional module in the terminal device or network device that can call and execute a program.

To facilitate understanding of the embodiments of the present application, a schematic diagram of a 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) 5G system architecture is first described in detail with reference to FIG. 1 .

As shown, the network architecture may be, for example, a non-roaming architecture. The network architecture may specifically include the following network elements:

1. User equipment (UE): may refer to terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment, User Agent or User Device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminals in the future evolved Public Land Mobile Network (PLMN) equipment, etc., which are not limited in this embodiment of the present application.

2. An access network (AN): provides a network access function for authorized users in a specific area, and can use transmission tunnels of different qualities according to user levels and service requirements. The access network may be an access network using different access technologies. There are two types of current radio access technologies: 3rd Generation Partnership Project (3GPP) access technologies (such as those used in 3G, 4G or 5G systems) and non-3rd generation partnership Planned (non-3GPP) access technology. 3GPP access technology refers to an access technology that conforms to 3GPP standards and specifications. An access network using 3GPP access technology is called a Radio Access Network (RAN). Among them, the access network equipment in the 5G system is called a radio access network (RAN). Next generation Node Base station (gNB). The non-3GPP access technology refers to an access technology that does not conform to 3GPP standard specifications, for example, an air interface technology represented by an access point (access point, AP) in wifi.

An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN). RAN). The radio access network can manage radio resources, provide access services for terminals, and then complete the forwarding of control signals and user data between the terminal and the core network.

The wireless access network can be, for example, a base station (BaseTransceiver Station, BTS) in the Global System of Mobile communication (GSM) system or a code division multiple access (Code Division Multiple Access, CDMA), or a broadband code division multiple access. The base station (NodeB, NB) in the (Wideband Code Division Multiple Access, WCDMA) system may also be an evolved base station (EvolutionalNodeB, eNB or eNodeB) in the LTE system, or may be a Cloud Radio Access Network (Cloud Radio Access Network, A wireless controller in a CRAN) scenario, or the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.

3. Access and mobility management function (AMF) entity: mainly used for mobility management and access management.

4. Session management function (session management function, SMF) entity: mainly used for session management, UE's Internet Protocol (Internet Protocol, IP) address allocation and management, and the like.

5. User plane function (User Plane Function, UPF) entity: that is, a user plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. User data can be accessed to a data network (DN) through the network element.

6. Data Network (DN): A network for providing data transmission. For example, an operator's service network, an Internet (Internet) network, a third-party service network, and the like.

7. Authentication server function (AUSF) entity: mainly used for user authentication and the like.

8. A network exposure function (NEF) entity: used to safely open services and capabilities provided by the 3GPP network function to the outside.

9. Network function (NF) repository function (NRF) entity: used to store the description information of the network function entity and the services it provides, and to support service discovery, network element entity discovery, and the like.

10. Policy control function (PCF) entity: a unified policy framework for guiding network behavior, providing policy rule information and the like for control plane function network elements (eg, AMF, SMF network elements, etc.).

11. Unified data management (unified data management, UDM) entity: used to process user identification, access authentication, registration, or mobility management, etc.

12. Application function (application function, AF) entity: used to perform data routing affected by applications, access network open function network elements, or interact with a policy framework to perform policy control, and the like.

In this network architecture, the N1 interface is the interface between the terminal and the AMF entity. The N2 interface is an interface between the AN and the AMF entity, and is used for sending non-access stratum (non-access stratum, NAS) messages and the like. The N3 interface is the interface between the (R)AN and the UPF entity, and is used to transmit data on the user plane. The N4 interface is an interface between the SMF entity and the UPF entity, and is used to transmit information such as the tunnel identification information of the N3 connection, the data buffer indication information, and the downlink data notification message. The N6 interface is the interface between the UPF entity and the DN, and is used to transmit data on the user plane.

It should be understood that the above-mentioned network architecture is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, which is not limited in this application.

It should also be understood that the AMF entity, the SMF entity, the UPF entity, the NSSF entity, the NEF entity, the AUSF entity, the NRF entity, the PCF entity, and the UDM entity shown in FIG. , for example, can be combined into network slices on demand. These core network elements may be independent devices, or may be integrated into the same device to implement different functions, which is not limited in this application.

It should be understood that the above names are only used to distinguish different functions, and do not mean that these network elements are independent physical devices, and this application does not limit the specific forms of the above network elements, for example, they can be integrated in the same physical device, They can also be different physical devices. In addition, the above naming is only for the convenience of distinguishing different functions, and should not constitute any limitation to the present application, and the present application does not exclude the possibility of adopting other nomenclature in the 5G network and other future networks. For example, in a 6G network, some or all of the above-mentioned network elements may use the terms in 5G, and may also use other names. A unified description is provided here, and details are not repeated below.

It should also be understood that the name of the interface between each network element in FIG. 1 is just an example, and the name of the interface in a specific implementation may be other names, which are not specifically limited in this application. In addition, the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.

The overall architecture of the NG-RAN is briefly described below with reference to FIG. 2 and FIG. 3 .

As shown in FIG. 2 , the core network device 103, such as the 5th generation core network (5GC), can be connected to either a complete access network device 101, such as a ^gNB , or a centralized unit (Centralized Unit). Unit, CU) 201 and an access network device 102 of a distributed unit (Distributed Unit, DU) 202 .

CU201 and DU202 can be softwareized or virtualized, and wireless access network functions that require flexible combinations will run in CU201, such as Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (Packet Data Convergence Protocol) , PDCP), radio resource control (Radio Resource Control, RRC) and other high-level functions; and RAN functions that are strongly related to hardware and require high real-time performance will run in DU202, such as radio link layer control protocol (Radio Link Control, RLC) ) layer, physical layer (physical layer, PHY), media access control layer (Media Access Control, MAC) and other underlying functions.

CU201 and DU202 are connected through a communication interface. The CU201 and the core network equipment are also connected through a communication interface. In this embodiment of the present application, the communication interface between the CU201 and the DU202 may be referred to as an F1 interface. The interface between the CU201 and the core network device may be called an N2 interface or an NG interface. As shown in FIG. 2 , one access network device 102 may include one CU201 and one or more DU202. The F1 interface is used to connect CU201 and DU202. One DU202 can only be connected to one CU201, and one CU201 can be connected to one or more DU202s.

For example, taking the access network device 102 as a gNB as an example, the gNB may include one or more gNB-DUs and one gNB-CU. One gNB-DU is connected to one gNB-CU, and one gNB-CU can be connected to multiple gNB-DUs. The gNB-CU and its connected gNB-DUs are viewed by other gNBs and 5GCs as a gNB.

Fig. 3 is based on the architecture of Fig. 2 and proposes a new architecture, that is, the CU includes a centralized unit-user plane (CU-UP) 301 and a centralized unit-control plane (Centralized Unit -control plane, CU-CP) 302. The CU-UP301 and CU-CP302 can be on different physical devices. There can be an open interface between CU-UP301 and CU-CP302, which can be called E1 interface. At the same time, CU-UP301, CU-CP302 and DU can have their own interfaces, for example, the interface between CU-CP302 and DU can be called F1-C interface, and the interface between CU-UP301 and DU is F1 -U interface.

The architecture of FIG. 3 may have the following characteristics: one access network device 102 may include one CU-CP 302 , one or more CU-UP 302 , and multiple DUs. One DU can be connected to one CU-CP302. Only one CU-CP302 can be connected to one CU-UP301. One DU can be connected to multiple CU-UP301s under the control of the same CU-CP302. One CU-UP301 can be connected to multiple DUs under the control of the same CU-CP302.

For example, taking the access network device 102 as a gNB as an example, both a gNB-DU and a gNB-CU-UP are only connected to one gNB-CU-CP. Under the control of the same gNB-CU-CP, one gNB-DU can be connected to multiple gNB-CU-UPs, and one gNB-CU-UP can be connected to multiple gNB-DUs.

FIG. 4 is a schematic diagram of the distribution of the air interface protocol stack in the case where the access network equipment includes CU and DU, and further, in the CU part, the CU includes CU-UP and CU-CP.

As can be seen from Figure 4, whether it is the user plane or the control plane, the air interface protocol stack is RLC, MAC, PHY running in the DU part (such as gNB-DU), PDCP and above protocol layers running in the CU part (such as gNB-CU) ). Among them, RRC can realize air interface radio resource and air interface connection control; SDAP can perform mapping between quality of service (QoS)-flow (QoS-flow) and data radio bearer (DRB) . QoS-flow is a service data flow with specific QoS requirements. The functions of other protocol layers will not be described again, and the 3GPP protocol specification can be referred to. This application does not limit this.

Industrial control in the Industrial Internet has some requirements such as end-to-end ultra-reliable and low latency communication (URLLC), low cost, and rapid deployment. The minimum end-to-end delay of the user plane required by industrial control is less than 2ms.

As can be seen from the 3GPP 5G network architecture shown in Figure 1, in the 3GPP 5G network, data transmission from terminal equipment A to terminal equipment B may need to pass through the following nodes and the transmission interface between them: terminal equipment A→gNB -DU→gNB-CU (or gNB-CU-UP)→UPF→DN→UPF→gNB-CU (or gNB-CU-UP)→gNB-DU→terminal device B.

Even if access network equipment, such as gNB, does not have CU/DU and CP/UP separation, the end-to-end transmission delay from terminal equipment to terminal equipment is much greater than 2ms, which cannot meet the low-latency requirements of industrial control. At the same time, the network nodes and functions in the current 3GPP 5G network are complex, resulting in high implementation costs.

In view of this, the present application provides a network unit and a network architecture, which can reduce time delay and save costs.

The various embodiments provided by the present application will be described in detail below with reference to the accompanying drawings.

FIG. 5 is a schematic interaction diagram of a communication system 500 provided by an embodiment of the present application. The communication system 500 may include a first network element 510 and a second network element 520 .

The communication system 500 provided in this embodiment of the present application may be called, for example, a minimalist network architecture, a minimalist network system, or a minimalist communication system. As shown in FIG. 5 , the network part may include a first network unit 510 and a second network unit 520, which can not only realize the corresponding network functions, but also meet the needs of low-latency, high-reliability, low-cost, and rapid deployment of communication networks in vertical industries such as industrial control.

In the communication system 500, the first network element 510 and the second network element 520 may communicate through a communication interface.

The following is a detailed introduction with reference to the embodiments of FIG. 8 and FIG. 9 .

In a possible design, the first network unit 510 is configured to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane processing function corresponding to UPF. The second network unit 520 is configured to implement: the first RRC function and the core network function, wherein the core network function includes one or more of the following: AMF, SMF, PCF, or AUSF.

In another possible design, the first network unit 510 is used to implement: the second RRC function; the second network unit 520 is used to implement: the first RRC function.

Optionally, the second RRC function includes: radio resource management RRM measurement configuration and/or radio bearer configuration.

Optionally, the first RRC function includes configuring one or more of the following: special cell configuration (special cell configuration, SpCellConfig), secondary cell configuration (SCell configuration, SCellConfig), radio link control configuration (RLC configuration, RLC- config), media intervention control layer cell group configuration (MAC-cellgroup configuration, MAC-cellGroupConfig), or physical cell group configuration (physical cell groupconfig, PhysicalCellGroupConfig). Among them, a special cell (SpCell, or may also be called a primary cell), if it is a primary base station or a primary node, the primary cell may refer to a primary cell (primary cell, PCell); if it is a secondary base station or secondary node, the primary cell may refer to Refers to a primary secondary cell (primary secondary cell, PSCell).

It should be understood that the first RRC function and the second RRC function are only named for distinction, and do not limit the protection scope of the embodiments of the present application.

It should also be understood that the first RRC function and the second RRC function may be partially the same, or may be completely different, and the functions may be flexibly deployed on the two network elements during specific implementation, which is not strictly limited.

It should also be understood that the above two possible designs can be used alone or in combination, which is not limited.

The above-mentioned first network unit 510 and second network unit 520 will be described in detail below.

The first network element 510 may be used to implement all user plane processing functions.

That is to say, the first network unit 510 can be used to implement all user plane processing functions, for example, the first network unit 510 can be used to implement the user plane processing functions in the 3GPP Rel-15 5G system, or, it can also be understood as, The user plane control in the 3GPP Rel-15 5G system is centralized into one network element, that is, the first network element 510 .

It should be understood that, in this embodiment of the present application, the first network unit 510 may be used to implement all user plane processing functions. In the process of data transmission, in the process of data transmission from one device to another device, the first network unit 510 performs the user plane processing function involved in the data transmission process, so as to avoid the need for data to pass through multiple network elements to achieve the purpose. Therefore, the user plane data transmission and processing delay can be reduced.

For example, take data transmission from one terminal device to another terminal device as an example.

An existing transmission process is as follows: data from a terminal device is first transmitted from the DU to the CU, then from the CU to the UPF, and then to another terminal device. In the embodiments of the present application, considering the transmission delay passing through network elements, such as the transmission delay from DU to CU and the transmission delay from CU to UPF, etc., the user plane control (or user plane processing) of these network elements may be ) is centralized to the first network unit 510, that is to say, the user plane processing function is performed by the first network unit 510. For example, data from a terminal device can be transmitted to the first network unit 510 first, and the first network unit 510 will then transfer the data to the first network unit 510. The data is transmitted to another terminal device, so that fast transmission between one terminal device and another terminal device can be realized through the first network unit 510, thereby saving the processing delay of the data passing through each network unit.

Optionally, the first network unit 510 is configured to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane processing function corresponding to the user plane function UPF.

Exemplarily, the user plane processing function (handling) corresponding to Layer 1 or Layer 2 may include, but is not limited to, one or more of the following: functions corresponding to SDAP, functions corresponding to PDCP, functions corresponding to RLC, functions corresponding to MAC function, or the function corresponding to the PHY.

For example, the first network unit 510 may be used to implement functions corresponding to SDAP, and the functions corresponding to SDAP may include, but are not limited to, mapping between QoS flows and data radio bearers, and/or, between downlink data packets and uplink data packets The QoS flow indicator (QoS flow indicator, QFI) is marked in the middle.

For another example, the first network unit 510 may be used to implement functions corresponding to PDCP, and the functions corresponding to PDCP may include, for example, one or more of the following: data transmission, encryption and decryption, integrity protection and verification, and robust header compression Robust header compression (ROHC) protocol header compression and decompression, timer-based service data unit (SDU) discard, split bearer routing, duplication, reordering and in-order delivery, Out-of-order delivery, or discarding of duplicate packets, etc. For detailed functions, please refer to 3GPP TS38.323v15.4.0. The functions of other protocol layers are similar and will not be described in detail later.

For another example, the first network unit 510 may be used to implement functions corresponding to RLC, and the functions corresponding to RLC may include, for example, one or more of the following: upper-layer PDU transmission, sequence numbering, automatic repeat request (ARQ) Error correction, RLC SDU segmentation and re-segmentation, reassembly of SDUs, duplicate detection, RLC SDU discarding, RLC reconstruction, or protocol error detection, etc.

For another example, the first network unit 510 may be configured to implement functions corresponding to MAC, and the functions corresponding to MAC may include, for example, one or more of the following: mapping between logical channels and transport channels, multiplexing and demultiplexing of MAC SDUs, Scheduling information reporting, error correction via HARQ, prioritization between end devices through dynamic scheduling, prioritization between logical channels of an end device through logical channel prioritization, or MAC PDU stuffing, etc.

For another example, the first network unit 510 may be configured to implement a function corresponding to the PHY, and the function corresponding to the PHY may include, for example, one or more of the following: transport block CRC attachment, channel coding, physical layer HARQ process, rate matching, scrambling ( scrambling), error detection on transmission channels, modulation and demodulation of physical channels, radio frequency processing, or multiple-input multiple-output antenna processing, etc.

It should be understood that the above exemplarily enumerates the functions corresponding to SDAP, the functions corresponding to PDCP, the functions corresponding to RLC, the functions corresponding to MAC, and the functions corresponding to PHY. The application embodiment is not limited to this.

Exemplarily, the user plane processing function corresponding to the UPF includes a routing function (routing). That is to say, the first network unit 510 may also be used to implement a routing function. Routing functions, including but not limited to one or more of the following: packet routing and forwarding, packet inspection, user plane part of policy rule enforcement, user plane QoS processing, data-to-QoS flow mapping function, or data-to-DRB mapping function (if SDAP is not configured or the SDAP layer is not configured with this function), etc.

It should be understood that the user plane processing functions corresponding to layer 1 or layer 2 and the user plane processing functions corresponding to UPF listed above are only exemplary descriptions, and the embodiments of the present application are not limited thereto.

In the prior art, during the transmission of downlink data from the UPF to the base station, the UPF will map the downlink data to the QoS flow, and implement differential processing by distinguishing the downlink data of different QoS flows by different scheduling priorities. Transport performance requirements for high-priority QoS flows.

Through this application, the first network unit 510 can implement the UPF function and the user plane processing function. In other words, there is no UPF to base station transmission process. Therefore, through the embodiments of the present application, the first network unit 510 can directly implement the mapping of downlink data to DRBs, that is, it can be understood that the mapping of downlink data to QoS flows is canceled or not available.

In addition, the first network unit 510 can realize the mapping of downlink data to DRB, and deliver the downlink data to the PDCP layer corresponding to the DRB. Therefore, the data may not be processed by the SDAP layer. That is, in this embodiment of the present application, the SDAP layer Layers may or may not be configured. It will be explained in detail below.

Optionally, the first network element 510 may be configured to configure one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig.

That is to say, the first network unit 510 may be used to perform one or more of the following processes, or in other words, the first network unit 510 may be used to perform one or more of the following operations: SpCellConfig, SCellConfig, RLC-config, MAC -cellGroupConfig, or PhysicalCellGroupConfig.

Optionally, the second RRC function includes: configuring parameters related to one or more of the following functions: power control, random access, beam management, hybrid automatic repeat request (HARQ), physical layer measurement, link adaptation, scheduling request , uplink and downlink scheduling, rate matching, automatic repeat request ARQ, or discontinuous reception DRX.

Optionally, SpCellConfig includes one or more of the following: cell or bandwidth part (BWP) related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

Optionally, the SCellConfig includes one or more of the following: cell or BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration.

Optionally, the cell or BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.

It should be understood that the above are only exemplary descriptions, and the embodiments of the present application are not limited thereto.

The second network unit 520 may be used to implement the first RRC function and the core network function.

The second network unit 520 is configured to implement the first RRC function, for example, the second network unit 520 is configured to implement the L3 control plane function; for another example, the second network unit 520 is configured to implement the RRC functions other than the second RRC function function; as another example, the second network unit 520 is configured to implement RRM measurement configuration and/or radio bearer configuration.

The radio bearer configuration includes, for example, SDAP and PDCP-related parameters for configuring the radio bearer, such as Radiobearerconfig and RRMmeasurementconfig in 3GPPTS 38.331v15.4.0.

In this case, by implementing the second RRC function by the first network unit 510 in the communication system 500, the second network unit 520 in the communication system 500 may no longer implement this part of the RRC function, that is, the second network unit 520 may implement the first RRC function. An RRC function such as responsible for configuration and reconfiguration of other functions. Therefore, the system can quickly adapt to changes in the state of the radio link of the air interface and ensure the transmission performance of the air interface.

The core network functions implemented by the second network unit 520 include one or more of the following: a function corresponding to AMF, a function corresponding to SMF, a function corresponding to PCF, or a function corresponding to AUSF.

For example, the second network unit 520 is used to implement the function corresponding to the AMF. The functions corresponding to AMF may include, for example, other functions except session management in the mobility management entity (mobility management entity, MME) function of 3GPP EPS, such as registration management, connection management, reachability management, mobility management, legal Monitoring, or access authorization (or authentication) and other functions.

For another example, the second network unit 520 is configured to implement a function corresponding to the SMF. The functions corresponding to SMF may include, for example, one or more of the following: session management, UE IP address allocation and management, selection and management of user plane functions, policy control, termination point of charging function interface, and downlink data notification, etc.

For another example, the second network unit 520 is configured to implement a function corresponding to the PCF. Functions corresponding to the PCF may include, for example, a unified policy framework for guiding network behavior, and/or providing policy rule information for control plane function network elements (eg, AMF, SMF network elements, etc.).

For another example, the second network unit 520 is configured to implement functions corresponding to the AUSF, such as user authentication and the like.

It should be understood that the above is only an exemplary description, and the embodiments of the present application are not limited thereto.

Optionally, the second network unit 520 may also be used to implement functions related to network capability opening and network data analysis. For example, it can provide the most simplified network management and control functions for vertical industry service providers or third-party application developers through standard API interfaces, simplifying network management and enabling network intelligence.

Exemplarily, the second network unit 520 may be used to implement a network capability opening function. Implementing the NEF function through the second network unit 520 can facilitate vertical industry service providers or third-party application developers to manage and control the network or obtain network information.

Exemplarily, the second network unit 520 is configured to implement functions related to network data analysis. A network data analytics function (NWDAF) is implemented through the second network unit 520, and data collection and big data analysis can be performed in the second network unit 520, thereby making the network intelligent.

Optionally, the second network unit 520 may also be used to implement a routing function.

Optionally, the first network unit 510 may be a local transmission unit (local transmission unit, LTU), and the second network unit 520 may be a remote control unit (remote control unit, RCU).

It should be understood that the above-mentioned first network unit 510 can be replaced by LTU, and the above-mentioned second network unit 520 can be replaced by RCU.

It should also be understood that the LTU and RCU are only a name, and do not limit the protection scope of the embodiments of the present application. The embodiments of the present application do not exclude the possibility of using other names in the 5G network and other future networks.

Based on the above technical solutions, with the communication system provided by the embodiments of the present application, the network part may include a first network unit and a second network unit, which not only implements corresponding network functions, but also simplifies network nodes and functions to avoid excessive There are many network nodes and overly complex interfaces, which can meet the needs of low-latency, high-reliability, low-cost, and rapid deployment of communication networks in vertical industries such as industrial control. In addition, the first network element implements: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane processing function corresponding to the user plane function UPF, so that when data is transmitted, such as data from a terminal device For transmission to another terminal device, through the first network unit, the data can be quickly transmitted to another terminal device, avoiding the need to pass through the core network and then sending it to another terminal device, so that low-latency transmission can be achieved, and it can support Ultra-low latency services.

For ease of understanding, the first network unit 510 is an LTU and the second network unit is an RCU as an example, and an exemplary description is given with reference to FIG. 6 .

FIG. 6 is a schematic interaction diagram of a communication system 600 provided by an embodiment of the present application. Communication system 600 may include LTUs and RCUs. For the configuration and parameters involved in FIG. 6 , reference may be made to the description of the embodiment in FIG. 5 , and details are not repeated here.

The LTU is equivalent to the first network unit 510 in the communication system 500 , and the RCU is equivalent to the second network unit 520 in the communication system 500 .

As shown in FIG. 6, in the communication system 600, the LTU and the RCU can communicate through an interface.

In a possible design, the LTU is used to implement: the user plane processing function corresponding to layer 1, the user plane processing function corresponding to layer 2, and the user plane processing function corresponding to the UPF; the RCU is used to implement: the first RRC function and the core network function.

For the LTU, the LTU can be used to implement: L1 and/or L2 user plane functions, for example, as shown in Figure 6: functions corresponding to SDAP, functions corresponding to PDCP, functions corresponding to RLC, functions corresponding to MAC, functions corresponding to PHY, The LTU can also be used to implement: the user plane processing function (ie, the routing function) corresponding to the UPF.

In another possible design, the LTU is used to configure one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig; the RCU is used to implement: in addition to the above SpCellConfig, SCellConfig, RLC- Functions other than config, MAC-cellGroupConfig, or PhysicalCellGroupConfig.

Regarding SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig, reference is made to the description in the embodiment of FIG. 5 , and details are not repeated here.

As shown in FIG. 6 , for the RCU, the RCU can be used to implement the connection control function, that is, the air interface layer 3 control plane function (such as the first RRC function), and the RCU can also include the core network function (or the necessary function of the core network), For example, the functions corresponding to AMF, the functions corresponding to SMF, the functions corresponding to PCF, the functions corresponding to AUSF and the like shown in FIG. 6 are shown.

As shown in FIG. 6 , the LTU can also be used to implement the second RRC function, for example, the LTU can be used to configure one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig, so as to implement the air interface Quick response to changes. In this case, the RCU no longer implements this part of the RRC function.

As shown in Figure 6, the RCU can also be used to implement one or more of the following functions: the routing function of the UPF, the NEF, or the NWDAF.

Exemplarily, when the RCU includes the routing function of the UPF, it can help the LTU to route data packets to the external network or another LTU without the LTU having a direct external user plane interface.

Exemplarily, in the case where the RCU includes the NEF function, it is convenient for vertical industry service providers or third-party application developers to manage, control or obtain network information on the network.

Exemplarily, when the RCU includes the NWDAF function, data information collection and big data analysis can be performed in the RCU to enable network intelligence.

Optionally, the mobile network is connected to the data network (DN) through the RCU, and the LTU may not be directly connected to the DN, or may implement operations such as data forwarding through an interface to the DN and/or the LTU.

Optionally, the RCU also has an interface with other network devices (eg gNB or gNB and access network nodes of other standard (eg eNB of LTE standard)). If other network devices are also of LTU and RCU architecture, the two RCUs can be connected through an interface.

Based on the above technical solutions, the network architecture provided by the embodiments of the present application can not only reduce the cost of network deployment and realize rapid network deployment, but also enable the LTU to implement the second RRC function, for example, the LTU can be responsible for the configuration and reconfiguration process of the radio bearer; Other functions of RRC (such as the first RRC function) are implemented by the RCU. For example, the RCU can be responsible for the configuration and reconfiguration process of other functions of the RRC, which not only enables the system to quickly adapt to changes in the state of the radio link of the air interface, but also ensures the transmission of the air interface. In addition, within the range of multiple LTUs managed by the RCU, a set of RRC configurations such as cell and RRM can be uniformly adopted, thereby avoiding frequent reconfiguration due to terminal equipment movement and reducing air interface signaling.

FIG. 7 is a schematic block diagram of a network device 700 provided by an embodiment of the present application. The network device 700 is equivalent to the first network unit 510 in the above-mentioned communication system 500 . The network device 700 may include a processing unit 710 and a communication unit 720 . The communication unit 720 may communicate with the outside, and the processing unit 710 may be used for data processing. The communication unit 710 may also be referred to as a communication interface or a transceiving unit.

It should be understood that each unit may be implemented in the form of hardware, and may also be implemented in the form of software function modules. It should also be understood that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division manners may be used in actual implementation. This is not limited.

It should also be understood that the division of modules or units in the embodiments of the present application is illustrative, and is only a logical function division, and other division manners may be used in actual implementation. The following description will be given by taking as an example that each function module or unit is divided corresponding to each function.

The processing unit 710 is configured to implement: the user plane processing function corresponding to layer 1, the user plane processing function corresponding to layer 2, and the user plane processing function corresponding to the user plane function UPF; the communication unit 720 is configured to communicate with the target device.

The target device, for example, may include terminal devices or other network devices.

Optionally, the processing unit 710 is further configured to configure one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig.

Optionally, the processing unit 710 is further configured to implement: downlink data to data radio bearer DRB mapping.

It should be understood that, for the network device 700, reference may be made to the description of the first network unit 510 in the embodiment of FIG. 5 and the description of the LTU in the embodiment of FIG. 6, and details are not repeated here.

It should also be understood that the configuration and parameters involved in FIG. 7 may refer to the description of the embodiment in FIG. 5 , which will not be repeated here.

Based on the above technical solutions, all user plane processing functions, such as L1/L2 data processing and data routing functions, are implemented through the network device 700, so that when the target address of the data to be transmitted is the local application of the network device 700 or other terminal devices (such as network devices 700), direct routing through the network device 700 can quickly route the data to the destination address, avoiding the need to first pass through the core network and then send it to the local application of the network device 700 or other terminal devices under the network device 700 , so that low-latency transmission between the terminal device and the application of the network device 700 or other terminal devices can be realized, and ultra-low-latency services can be supported.

FIG. 8 is a schematic block diagram of a network device 800 provided by an embodiment of the present application. The network device 800 is equivalent to the second network unit 520 in the above-mentioned communication system 500 . The network device 800 may include a processing unit 810 and a communication unit 820 . The communication unit 820 can communicate with the outside, and the processing unit 810 can be used for data processing. The communication unit 810 may also be referred to as a communication interface or a transceiving unit.

It should be understood that each unit may be implemented in the form of hardware, and may also be implemented in the form of software function modules. It should also be understood that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division manners may be used in actual implementation. This is not limited.

It should also be understood that the division of modules or units in the embodiments of the present application is illustrative, and is only a logical function division, and other division manners may be used in actual implementation. The following description will be given by taking as an example that each function module or unit is divided corresponding to each function.

The processing unit 810 is used to implement: the first RRC function and the core network function; the communication unit 820 is used to communicate with the target device.

The target device, for example, may include terminal devices or other network devices.

Optionally, the first RRC function includes: configuration: RRM measurement configuration and/or radio bearer configuration.

Optionally, the processing unit 810 is further configured to implement functions related to network capability opening and network data analysis.

Optionally, the core network functions include one or more of the following: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF.

It should be understood that, for the network device 800, reference may be made to the description of the second network unit 520 in the embodiment of FIG. 5 and the description of the RCU in the embodiment of FIG. 6, and details are not repeated here.

It should also be understood that the configuration and parameters involved in FIG. 8 may refer to the description of the embodiment in FIG. 5 , which will not be repeated here.

It should also be understood that, in the above-mentioned embodiments of FIG. 7 and FIG. 8 , the network device 700 and the network device 800 are divided into functional modules. For example, each functional module or unit may be divided corresponding to each function, or two or two The above functions are integrated in a processing module or unit. The above-mentioned integrated modules or units may be implemented in the form of hardware, or may be implemented in the form of software function modules. It should be noted that, the division of modules or units in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.

The network unit and network architecture proposed by the embodiments of the present application are described above with reference to FIGS. 5 to 8 , and the application of the network unit or the communication system is described with reference to the exemplary scenarios shown in FIGS. 9 to 12 .

FIG. 9 is a schematic interaction diagram of a terminal device access process applicable to an embodiment of the present application. FIG. 9 may include the following steps.

910. The first network element sends an interface establishment request message to the second network element.

The first network element may be an LTU, and the second network element may be an RCU.

It should be understood that the first network unit in the embodiment of the present application is equivalent to the first network unit 510 or the network device 700 in the above embodiment, and the second network unit is equivalent to the second network unit 520 or the network in the above embodiment. For the details of the device 800, reference may be made to the description of the above embodiments, and details are not repeated here. The following takes the first network unit and the second network unit as examples for exemplary description.

In this step, the first network element sends a setup request message to the second network element. For example, the interface establishment request message may include: the identifier of the first network element and the list information of the subordinate cells of the first network element.

The form of the first network element identification may be, for example, an identification (identity, ID) of the first network element, an index (index) of the first network element, or a name of the first network element, and the like.

The first network unit sends an interface establishment request message to the second network unit, and accordingly, the second network unit receives the interface establishment request message and feeds back to the first network unit.

920. The second network unit feeds back to the first network unit to establish a response message.

After receiving the interface establishment request message of the first network unit, the second network unit can learn some information related to the first network unit according to the parameters carried in the message, so as to make decisions such as the selection of the first network unit for subsequent communication Provide input.

For example, the interface establishment request message includes: the identification information of the first network element and the list information of the subordinate cells of the first network element. After receiving the interface establishment request message, the second network element can learn the identification of the first network element and the information to which it belongs. Cell list information.

The second network element feeds back an interface setup response (setup response) message to the first network element, and the content included in the setup response message is similar to the content included in the F1 setup response message. For example, the interface establishment response message may include the information of the activated cell list and system information. For another example, the interface establishment response message may further include information such as an available public land mobile network (public land mobile network, PLMN) list and a radio access network (radio access network, RAN) area code.

The RAN area code can be used to identify which RAN area the first network element or the subordinate cell of the first network element belongs to, so that the terminal equipment in the RRC inactive (RRC_INACTIVE) state can judge whether it needs to initiate RRC according to the RAN area code Connection recovery process.

After receiving the interface establishment response message, the first network unit may obtain information such as the list of activatable cells, the list of available PLMNs, and system information according to the interface establishment response message. After learning the information, the first network unit can broadcast the system information on the air interface.

930. The terminal device initiates a random access procedure to the first network unit.

After the terminal device is powered on, after completing downlink synchronization with the cells in the first network element and acquiring system information, it will initiate a random access procedure to the cells under the first network element to access the network.

It should be understood that the embodiments of this application do not limit the specific random access process. For example, the random access process can be completed through four-step random access, or the random access process can be completed through two-step random access. The example does not limit this.

940. The terminal device initiates an RRC connection establishment process to the first network element.

The RRC connection establishment procedure may include a three-way handshake.

First, the terminal device sends an RRC connection request (RRC connection request) message to the first network unit, the first network unit forwards the RRC connection request message to the second network unit, and informs the second network unit of the identity of the corresponding terminal device and cell ID.

Wherein, the identity of the terminal device and the identity of the cell may be carried in the RRC connection request message, or may also be sent to the second network unit through separate signaling.

Second, the second network element sends an RRC connection setup (RRC connection setup) message to the terminal device through the first network element.

That is, the second network element first sends the RRC connection establishment message to the first network element, and then the first network element sends the RRC connection establishment message to the terminal device.

Third, the terminal device completes the establishment of the RRC connection between the terminal device and the network by feeding back an RRC connection setup complete (RRC connection setup complete) message to the second network unit through the first network unit.

That is, the terminal device first sends an RRC connection establishment complete message to the first network element, and then the first network element forwards the RRC connection establishment complete message to the second network element.

Optionally, the terminal device may carry a non-access stratum (non access stratum, NAS) attach request (attach request) message in the RRC connection establishment complete message. The attach request message can be used to initiate the attachment of the terminal device at the NAS layer of the network, that is, authentication and registration.

950. The terminal device initiates an attach process to the second network element.

The attachment procedure may also include a three-way handshake procedure.

First, the terminal device sends an attach request message to the second network element through the first network element.

That is, the terminal device first sends the attach request message to the first network element, and then the first network element sends the attach request message to the second network element.

It should be understood that the attach request message may be sent through a separate signaling, or may be carried in the RRC connection establishment complete message in the previous steps.

Second, the second network element sends an attach accept message to the terminal device through the first network element.

That is, the second network element first sends the attach accept message to the first network element, and then the first network element sends the attach accept message to the terminal device.

Third, the terminal device completes the attachment of the terminal device in the second network element by feeding back an attach complete (attachcomplete) message to the second network element through the first network element.

That is, the terminal device first sends an attach complete message to the first network element, and then the first network element forwards the attach complete message to the second network element.

Optionally, in the attachment process of the three-way handshake, there may be authentication, key derivation, distribution and other processes between the terminal device and the second network unit.

Usually, the mobile network system performs user authentication based on a subscriber identification module (SIM) card or a universal mobile telecommunications system (UMTS) SIM (USIM) card, so as to avoid troubles such as manual input of a password by the user. In this embodiment of the present application, in order to facilitate rapid deployment of vertical services, user authentication may also be performed based on certificates. If the terminal device supports IP services, the network will assign an IP address to the terminal device, and can tell the terminal device through the attach process in this step.

960. The second network element initiates an access layer security activation process.

The second network unit derives the key used for air interface transmission according to the root key. The root key may be a preset root key, or may be a root key obtained according to the authentication process in step 950, which is not limited in this embodiment of the present application.

The second network unit may use the non-access stratum (AS) security activation process (AS security activation) to transmit the key used in the air interface or some input parameters for generating the key, for example, may include the next hop chain counter ( next-hop chaining counter, NCC), notify the terminal equipment.

It should be understood that this step and step 950 do not have a strict sequence, and may be performed in parallel or sequentially.

970. The second network unit initiates a radio bearer establishment process.

After obtaining the packet data unit (packet data unit, PDU) session (PDU session) information configured by the terminal device, the second network unit may initiate a radio bearer setup procedure (DRB setup procedure).

This embodiment of the present application does not limit when the second network unit obtains the PDU session information. For example, in the process of attaching the terminal device, the second network unit may obtain the PDU session information configured by the terminal device. For another example, the second network unit may obtain the PDU session information corresponding to the requested service in the subsequent service request process of the terminal device.

Step 970 may include the following steps.

9701. The second network element sends a PDU session resource setup request (PDU session resource setup request) message to the first network element.

After initiating the radio bearer establishment process, the second network element sends a PDU session resource establishment request message to the first network element. Through the radio bearer establishment process, an air interface bearer can be established for the terminal device, and related parameters can be configured. The relevant parameters may include, for example, the logical channel priority of the bearer and the like.

The PDU session resource establishment request message may include: PDU session ID, QoS parameters of each QoS flow corresponding to the PDU session, and other information.

The QoS parameters of the QoS flow may also be referred to as configuration parameters of the QoS flow. The QoS parameters of each QoS flow may include, for example, but are not limited to: PDU session aggregate maximum bit rate (AMBR), 5G QoS identifier (5G QoS Identifier, 5QI), or an allocation and retention priority (an allocation and retention priority). , ARP) parameters, etc.

9702. The first network element initiates RRC reconfiguration.

After receiving the PDU session resource establishment request message, the first network element can perform mapping of the QoS flow to the DRB according to the QoS flow included in the PDU session and the QoS parameters of each QoS flow corresponding to the PDU session, and establish a QoS flow for the PDU session. One or more air interface DRBs, and can generate an RRC reconfiguration (RRC reconfiguration) message including the configuration of the one or more air interface DRBs. The first network element may deliver the RRC reconfiguration message to the terminal device through the first network element.

The terminal device receives the RRC reconfiguration message and takes effect (that is, configures the corresponding DRB), and sends an RRC reconfiguration complete message to the first network element.

9703. The first network element sends a PDU session resource setup response (PDU session resource setup response) message to the second network element.

The first network element sends a PDU session resource establishment response message to the second network element to complete the DR establishment process.

There is no strict sequence requirement between the first network element sending the PDU session resource establishment response message to the second network element and the first network element sending the RRC reconfiguration message to the terminal device.

For example, the first network element may also first send a PDU session resource establishment response message to the second network element, and then send an RRC reconfiguration message to the terminal equipment. For another example, the first network element may also send an RRC reconfiguration message to the terminal device first, and then send a PDU session resource establishment response message to the second network element. For another example, the first network element may also simultaneously send an RRC reconfiguration message to the terminal device, and send a PDU session resource establishment response message to the second network element.

980. The first network element initiates an RRC reconfiguration process.

In this embodiment of the present application, the first network unit may process or execute or implement one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig. Therefore, the first network element may initiate reconfiguration of L1 or L2 (ie SDAP, PDCP, RLC, MAC and PHY) protocol layer parameters to quickly adapt to changes in the state of the air interface radio link.

For example, when the radio link of the air interface deteriorates, the first network unit may reconfigure one or more of the following parameters to ensure that the transmission performance is not affected: the number of HARQ retransmissions at the MAC layer, the number of ARQ retransmissions at the RLC layer The number of transmissions, or the reconfiguration of the PDCP layer to implement packet duplication, etc.

In the case of reconfiguration, the first network element sends an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message includes at least the radio bearer configuration. After successful reconfiguration, the terminal device returns an RRC reconfiguration complete (RRC reconfiguration complete) message to the first network element.

In this embodiment of the present application, the second network element may process or execute or implement: RRM measurement configuration and/or radio bearer configuration. Therefore, the second network element may also initiate an RRC reconfiguration process, for example, the second network element initiates a service RRC reconfiguration process related to cell and RRM measurement.

It should be understood that, in the foregoing embodiments, the names of the involved messages are only exemplary descriptions, and the embodiments of the present application are not limited thereto. For example, other names may also be used to represent similar meanings in future protocols.

Based on the above technical solutions, the first network unit can realize the reconfiguration of L1 or L2 (ie SDAP, PDCP, RLC, MAC and PHY) protocol layer parameters, and the second network unit can realize other functions of RRC, such as the second network The unit is responsible for the configuration and reconfiguration process of other functions of the RRC, so that the system can not only quickly adapt to changes in the state of the air interface radio link and ensure the transmission performance of the air interface, but also within the range of multiple first network units managed by the second network unit. , a set of RRC configurations such as cell and RRM can be uniformly adopted, thereby avoiding frequent reconfiguration due to terminal equipment movement and reducing air interface signaling. In addition, based on the above technical solution, the existing NR protocol can be reused as much as possible to reduce the impact on the terminal device, the first network unit and the second network unit.

FIG. 10 is a schematic interaction diagram of data transmission applicable to an embodiment of the present application. Figure 10 may include the following steps.

Optionally, 1010 may be included. 1010, uplink data arrives.

That is, the end device is going to send data. The following is an exemplary description as an example that the uplink data is the uplink data of accessing a web page.

For example, a PDU session is configured for the terminal device, wherein the QoS flow corresponding to the web page access service is mapped to the data radio bearer (DRB) configured by the network for the terminal device, such as DRB1. When a terminal device opens a web page or clicks a hyperlink on the web page, uplink data for accessing the web page will be generated, and the uplink data will reach the SDAP layer corresponding to the PDU session configured on the terminal device side.

Optionally, 1020 may be included. In 1020, the L2 of the terminal device processes the uplink data.

After receiving the above-mentioned uplink data, the SDAP layer maps the uplink data to DRB1 according to the configured mapping relationship between QoS flows and DRBs, and submits the uplink data to the PDCP layer corresponding to DRB1. The PDCP layer can first perform some processing on the uplink data, for example, including but not limited to: encryption, integrity protection and other processing, and then hand it over to the RLC layer corresponding to the DRB1. The RLC layer may first perform the acknowledgement mode processing or the unacknowledged mode processing on the uplink data, and the RLC layer may further segment the uplink data, and then hand it over to the MAC layer. The MAC layer encapsulates the processed uplink data into one or more MAC PDUs and delivers them to the PHY.

It should be understood that the foregoing steps 1010 and 1020 are only exemplary descriptions, which are not limited in this embodiment of the present application.

1030. The terminal device sends uplink data to the first network device. Correspondingly, the first network device receives the uplink data from the terminal device.

After the PHY receives the MAC PDUs submitted by the MAC layer, the PHY may first convert the MAC PDUs into transmission blocks (transmission blocks, TBs), and send the TBs to the first network device.

After the MAC layer of the terminal device receives the processed uplink data, if no available uplink resources are found to transmit the uplink data, the terminal device may initiate a scheduling request process and request the first network device to allocate uplink resources for transmitting the uplink data. upstream data.

The first network device may be an LTU.

It should be understood that the first network device in this embodiment of the present application is equivalent to the first network unit 510 or the network device 700 in the above embodiment, and details can be referred to the description of the above embodiment, which will not be repeated here. The following takes the first network device as an example for exemplary description.

Optionally, 1040 may be included. In 1040, the L2 of the first network device processes the received uplink data.

After receiving the TBs sent by the terminal device, the physical layer of the first network device delivers these TBs to the MAC layer, and the MAC layer can restore these TBs into MAC PDUs, and then deliver the MAC PDUs to the RLC layer. The RLC layer may perform post-segmentation data reassembly, and after restoring the uplink data, the uplink data is handed over to the PDCP layer. The PDCP layer may perform some processing on the uplink data, for example, including but not limited to: encryption, data integrity verification and other processing. The PDCP layer delivers the decrypted and integrity-verified (if integrity-protected) uplink data to the SDAP layer. The SDAP layer can hand over the uplink data to the routing function module.

It should be understood that, in this step, the process of processing the received data by the first network device is only illustrative, and the present application is not limited thereto.

1050. The first network device routes the uplink data to the destination address.

In this embodiment of the present application, the first network device may implement a user plane processing function. For example, in this embodiment of the present application, after receiving the uplink data, the routing function module in the first network device may route the uplink data to the destination address according to the destination IP address in the uplink data, and the destination address may be, for example, the corresponding data network. The uplink data will reach the server where the terminal device accesses the web page by means of IP address addressing. The server will respond to the uplink data, and feed back relevant content to the terminal device through the downlink data, such as feedback: the content of the accessed web page, the content of the accessed link, or prompt information and so on.

Optionally, the destination address corresponds to one or more of the following: a data network, other terminal devices, a network device where other terminal devices are located, a local application of the first network device, or a second network device.

Wherein, the network device where the other terminal device is located refers to the network device that has a communication connection with the terminal device, or in other words, the network device that controls the terminal device.

That is, the first network device may route uplink data to one or more of the following: a data network, other terminal devices, network devices where other terminal devices are located, local applications of the first network device, or second network devices.

If the first network device is not directly connected to the data network, the first network device routing function module can route the uplink data to the second network device or other network devices (that is, the network devices where other terminal devices are located), and then route the uplink data to the second network device or other network devices (that is, the network devices where other terminal devices are located). The second network device or other network device routes the upstream data to the data network.

The second network device may be an RCU.

It should be understood that the second network device in the embodiment of the present application is equivalent to the second network unit 520 or the network device 800 in the above embodiment, and details can be referred to the description of the above embodiment, which will not be repeated here. The following takes the second network device as an example for exemplary description.

It should be understood that, the above-mentioned embodiments are exemplified by taking the line data as IP data as an example, and the embodiments of the present application are not limited thereto. For example, the uplink data can also be Ethernet data. When the uplink data is Ethernet data, the first network device (ie, the routing function module of the first network device) may perform data routing according to the destination MAC address in the Ethernet data. For example, the first network device may route the uplink data directly to the destination address, or the first network device may also route the uplink data to the destination address through the second network device or other network devices.

Optionally, the destination address of the uplink data, such as IP service data or Ethernet service data, may be an application or other terminal device in the first network device in the mobile network.

In this case, for example, the first network device or the second network device may route data to the first network device where other terminal devices are located, and the first network device of the other terminal device transmits the data to the other terminal device. For another example, in the industrial Internet, the first network device itself implements a programmable logic control (programmable logic control, PLC) application, or the PLC and the first network device are deployed together. At this time, the first network device receives the uplink data. It can then be routed directly to the PLC.

Based on the above technical solutions, the first network device can implement all user plane functions, such as L1/L2 data processing and data routing functions, so that when the destination address is a local application of the first network device or other terminal devices (such as the other terminal devices), direct routing through the first network device can quickly route data to the destination address, avoiding the need to first pass through the core network and then send it to the local application of the first network device or other terminal devices under the first network device , so that low-latency transmission between the terminal device and the first network device application or other terminal devices can be implemented, and ultra-low-latency services can be supported.

As shown above, the first network unit (that is, the first network unit 510 or the network device 700 in the above embodiment or the first network device in FIG. 10 , can refer to the description in the above embodiment for details, which is not repeated here. Repeat the description. The first network element is taken as an example for illustrative description below.) The downlink data to DRS mapping can be directly implemented. 11 and FIG. 12 will be described below.

For ease of understanding, a brief introduction to QoS flow is given first.

QoS flow: 5G defines the packet processing mechanism on the air interface based on DRB. Data packets served by a DRB have the same packet processing mechanism in air interface transmission. A base station can establish multiple DRBs with a terminal device to meet QoS flows with different packet processing requirements. It should be noted that the same DRB may have a mapping relationship with one QoS flow, or may have a mapping relationship with multiple QoS flows.

Figure 11 shows a schematic diagram of the QoS framework defined by the existing 3GPP NR protocol.

Exemplarily, for downlink transmission: after the data of each service data flow (SDF) of a downlink PDU session reaches the UPF, the UPF will use the traffic filtering template (traffic filtering template, TFT) corresponding to the PDU session to perform QoS flow on the data. Classify, and carry a QoS flow indicator (QoS flow indicator, QFI) on the GTP-U encapsulation header that transmits the data to the access network device. After the access network device receives the data, it determines the QoS flow to which the data belongs according to the corresponding QFI, and then maps the data to the corresponding DRB at the SDAP layer corresponding to the PDU session according to the pre-configured QoS parameters corresponding to the QoS flow. , the data is handed over to the PDCP layer corresponding to the DRB.

That is to say, in the prior art, during the transmission of downlink data from the UPF to the base station, the UPF will map the downlink data to the QoS flow, and realize the difference by distinguishing the downlink data of different QoS flows by different scheduling priorities. processing, and preferentially meet the transmission performance requirements of high-priority QoS flows.

Provided by this application, the first network unit can implement the UPF function and the user plane processing function of the base station. In other words, there is no transmission process from the UPF to the base station. Therefore, through the embodiments of this application, the first network unit can directly implement downlink. Data to DRB mapping, that is, unmapping of downstream data to QoS flows.

In other words, the routing function module in the first network unit (such as the user plane processing function of the first network unit 510 ) can directly realize the mapping of downlink data to DRB, and deliver the downlink data to the PDCP layer corresponding to the DRB. Therefore, for PDU session, SDAP layer is configurable. That is, for a PDU session, the SDAP layer can be configured or not.

In addition, regardless of whether the SDAP layer is configured in the PDU session, the architecture provided by the present application can also adopt the QoS reflective mechanism similar to the existing 3GPPNR, so that the uplink data can be quickly responded and the signaling overhead can be saved.

Exemplarily, for uplink transmission, in the prior art, after the upper layer of the terminal device receives the data, it first performs the mapping of the uplink data to the QoS flow, and then hands the data to the SDAP layer (that is, the data needs to be processed by the SDAP layer), The SDAP layer continues to map the QoS flow to the DRB, and submits the uplink data to the PDCP layer corresponding to the DRB. The mapping of the uplink data to the QoS flow and the mapping of the QoS flow to the DRB usually require the network device to send signaling to the terminal device for configuration. Due to the unpredictability of data arrival, in order to quickly respond to the arrival of uplink data and save signaling overhead, the existing 3GPP NR protocol agrees with the QoS reflection mechanism, that is, by setting the QoS reflection function on in the SDAP header of the downlink data to enable the terminal Uplink data corresponding to the downlink data by the device. That is to say, the mapping of the data corresponding to the downlink data to the QoS flow and the mapping of the QoS flow to the DRB are adopted.

In this embodiment of the present application, regardless of whether the SDAP layer is configured, the QoS reflection mechanism can be used.

For example, for a PDU session, if the SDAP layer is not configured, it can be confirmed whether to enable the QoS reflection function through the indication of the PDCP layer.

As a possible implementation, the QoS reflective indication information can be carried in the PDCP header. For example, the first network unit turns on the QoS reflection function by setting the PDCP header, thereby instructing the terminal device to use the data corresponding to the downlink data to the DRB mapping for the uplink data corresponding to the downlink data. In this case, the uplink usually only needs to complete the "uplink data to DRB" mapping.

Exemplarily, if it is an IP service, the "correspondence" may be determined by the source and destination addresses in the TCP/UDP and IP headers being interchanged, and the contents of other fields being the same.

Exemplarily, if it is an Ethernet service, the "correspondence" can be confirmed by the source and destination addresses in the Ethernet header being interchanged, and the contents of other fields being the same.

Optionally, the QoS reflection indication information may be indicated by 1 bit in the PDCP header, or the QoS reflection indication information may be indicated by a reserve field in the PDCP header.

An exemplary description will be given below with reference to FIG. 12 .

As shown in the figure, the PDCP PDU format contains a 12-bit PDCP serial number (SN).

For example, whether the QoS reflection function is turned on may be indicated by any one of the R fields in the three reserved fields in the first byte. For example, when R=0, it means that the QoS reflection function is not enabled; when R=1, it means that the QoS reflection function is enabled.

Based on the above technical solutions, not only the delay caused by data transmission between the UPF and the base station can be avoided, but also by canceling the SDAP layer, SDAP data processing is reduced, data transmission delay is further reduced, and ultra-low delay transmission is realized. In addition, when the SDAP layer is cancelled, the QoS reflection function can be realized through the PDCP layer indicating whether to enable the QoS reflection function, thereby reducing signaling overhead.

The various embodiments described herein may be independent solutions, or may be combined according to internal logic, and these solutions all fall within the protection scope of the present application.

In the above, the communication system and the network device provided by the embodiments of the present application are described in detail with reference to FIG. 5 to FIG. 12 . Hereinafter, the communication apparatus provided by the embodiments of the present application will be described in detail with reference to FIG. 13 to FIG. 15 .

FIG. 13 is a schematic block diagram of a communication apparatus 1300 provided by an embodiment of the present application. As shown, the apparatus 1300 may include a communication unit 1310 and a processing unit 1320. The communication unit 1310 can communicate with the outside, and the processing unit 1320 is used for data processing. The communication unit 1310 may also be referred to as a communication interface or a transceiving unit.

In a possible design, the apparatus 1300 may implement steps or processes corresponding to those performed by the first network unit 510 (eg, LTU) in the above embodiments, for example, it may be the network device 700 or be configured in the network device 700 chip or circuit. At this time, the apparatus 1300 may be referred to as a network device. The communication unit 1310 is configured to perform the transceiving related operations on the side of the first network unit 510 (eg, the LTU) in the above embodiments, and the processing unit 1320 is configured to perform the processing of the first network unit 510 (eg, the LTU) in the above embodiments related operations.

In a possible implementation manner, the apparatus 1300 may implement the steps or processes performed by the first network device corresponding to the method 900 or 1000 according to the embodiment of the present application, and the apparatus 1300 may include a method for performing the method 900 in FIG. 9 . or a unit of the method performed by the first network device in the method 1000 in FIG. 10 . In addition, each unit in the apparatus 1300 and the above-mentioned other operations and/or functions are respectively to implement the corresponding flow of the method 900 in FIG. 9 or the method 1000 in FIG. 10 .

It should be understood that the specific process for each unit to perform the above-mentioned corresponding steps has been described in detail in the above-mentioned embodiment, and for brevity, it will not be repeated here.

In yet another possible design, the apparatus 1300 may implement steps or processes corresponding to the second network unit 520 (eg, RCU) in the above embodiments, for example, may be the network device 800 or be configured in the network device A chip or circuit in the 800. At this time, the apparatus 1300 may be referred to as a network device. The communication unit 1310 is configured to perform the transceiving related operations on the side of the second network unit 520 (eg, the RCU) in the above embodiments, and the processing unit 1320 is configured to perform the processing of the second network unit 520 (eg, the RCU) in the above embodiments related operations.

In a possible implementation manner, the apparatus 1300 may implement the steps or processes performed by the second network device corresponding to the method 900 or 1000 according to the embodiment of the present application, and the apparatus 1300 may include a method for performing the method 900 in FIG. 9 . or a unit of the method performed by the second network device in the method 1000 in FIG. 10 . In addition, each unit in the apparatus 1300 and the above-mentioned other operations and/or functions are respectively to implement the corresponding flow of the method 900 in FIG. 9 or the method 1000 in FIG. 10 .

It should be understood that the specific process for each unit to perform the above-mentioned corresponding steps has been described in detail in the above-mentioned embodiment, and for brevity, it will not be repeated here.

FIG. 14 is a schematic structural diagram of a communication apparatus 1400 provided by an embodiment of the present application. The apparatus may implement the function of the first network unit 510 (eg, LTU) in the above embodiments, or the actions performed by the first network device in the above method embodiments. For example, the method performed by the first network device in method 900 or method 1000 may be performed. The apparatus 1400 includes:

a memory 1410 for storing programs;

A communication interface 1420 for communicating with other devices;

The processor 1430 is used for executing the program in the memory 1410, when the program is executed,

The processor 1420 is configured to implement: a function corresponding to SDAP, a function corresponding to PDCP, a function corresponding to RLC, a function corresponding to MAC, a function corresponding to PHY, and the user plane processing function corresponding to UPF, or,

The processor 1420 is configured to configure one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalCellGroupConfig.

FIG. 15 is a schematic structural diagram of a communication apparatus 1500 provided by an embodiment of the present application. The apparatus may implement the function of the second network unit 520 (eg, the RCU) in the above embodiments, or the actions performed by the second network device in the above method embodiments. For example, the method performed by the second network device in method 900 or method 1000 may be performed. The apparatus 1500 includes:

a memory 1510 for storing programs;

A communication interface 1520 for communicating with other devices;

The processor 1530 is configured to execute the program in the memory 1510, when the program is executed,

The processor 1520 is configured to configure: radio resource management RRM measurement configuration and/or radio bearer configuration; and/or,

The processor 1520 is configured to implement one or more of the following functions: AMF, SMF, PCF, or AUSF.

Optionally, the above-mentioned communication interface (1420, 1520) may be a receiver or a transmitter, or may also be a transceiver.

In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.

It should be noted that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The aforementioned processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components . The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) And direct memory bus random access memory (directrambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute the method 900 and the method 1000. The method of any one of the illustrated embodiments.

According to the methods provided in the embodiments of the present application, the present application further provides a computer-readable medium, where program codes are stored in the computer-readable medium, and when the program codes are run on a computer, the computer is made to execute the methods of method 900 and method 1000. The method of any one of the illustrated embodiments.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (19)

1. A communication system, comprising: a first network unit and a second network unit, The first network element and the second network element communicate through a communication interface, wherein, The first network element is used to implement: a user plane processing function corresponding to layer 1, a user plane processing function corresponding to layer 2, and a user plane processing function corresponding to the user plane function UPF; The second network unit is used to implement: the first radio resource control RRC function and the core network function; Wherein, the core network function includes one or more of the following: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF. 2. The communication system according to claim 1, wherein the first network element is further configured to implement a second RRC function, and, The second RRC function includes: Configure one or more of the following: Special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig. 3. The communication system according to claim 2, wherein, The SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; The SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration. 4. The communication system according to claim 2 or 3, wherein the cell or BWP-related configuration includes configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization Signal block, or physical channel. 5. The communication system according to any one of claims 1 to 4, wherein the second network element is configured to implement the first RRC function, comprising: The first RRC function includes: Configuration: Radio resource management RRM measurement configuration and/or radio bearer configuration. 6. A communication system, comprising: a first network unit and a second network unit, the first network element and the second network element communicate through a communication interface, the second network element is used to implement the first radio resource control RRC function, the first network element is used to implement the second RRC function, Wherein, the first RRC function includes: Configuration: radio resource management RRM measurement configuration and/or radio bearer configuration; The second RRC function includes: One or more of the following are configured: special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig. 7. The communication system according to claim 6, wherein, The SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; The SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration. 8. The communication system according to claim 7, wherein, The cell or BWP-related configuration includes configuring one or more of the following parameters: Center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, sync block, or physical channel. 9. The communication system according to any one of claims 1 to 8, characterized in that, The first network element is further configured to implement the mapping of downlink data to the data radio bearer DRB. 10. The communication system according to any one of claims 1 to 9, characterized in that, The second network unit is further configured to implement a network capability opening function and/or a network data analysis function. 11. The communication system according to any one of claims 1 to 10, characterized in that, The layer 1 includes: a physical layer PHY; and/or, The layer 2 includes one or more of the following: a service data adaptation protocol SDAP layer, a packet data convergence protocol PDCP layer, a radio link layer control protocol RLC layer, and a media intervention control layer MAC layer. 12. The communication system according to any one of claims 1 to 11, characterized in that, The first network unit is a local transmission unit LTU, and the second network unit is a remote control unit RCU. 13. A network device, comprising: a processor and a communication interface, The processor is used to implement: the function corresponding to the service data adaptation protocol SDAP, the function corresponding to the packet data convergence protocol PDCP, the function corresponding to the radio link layer control protocol RLC, the function corresponding to the media intervention control layer MAC, and the physical layer PHY. function, and the user plane processing function corresponding to the user plane function UPF; The communication interface is used to communicate with the target device. 14. The network device according to claim 13, wherein the processor is further configured to implement a second radio resource control RRC function, and The second RRC function includes: One or more of the following are configured: special cell configuration SpCellConfig, secondary cell configuration SCellConfig, radio link control configuration RLC-config, media intervention control layer cell group configuration MAC-cellGroupConfig, or physical layer cell group configuration PhysicalCellGroupConfig. 15. The network device according to claim 14, wherein, The SpCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration; The SCellConfig includes one or more of the following: cell or bandwidth part BWP related configuration, channel state indication CSI measurement configuration, cross-carrier scheduling configuration, or rate matching configuration. 16. The network device according to claim 15, wherein, The cell or BWP-related configuration includes configuring one or more of the following parameters: Center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, sync block, or physical channel. 17. The network device according to any one of claims 13 to 16, wherein, The processor is further configured to implement: downlink data to data radio bearer DRB mapping. 18. A network device, comprising: a processor and a communication interface, The processor is configured to implement: a first radio resource control RRC function and a core network function, where the core network function includes one or more of the following: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or authentication service function AUSF; the communication interface is used to communicate with the target device; Wherein, the first RRC function includes: Configuration: Radio resource management RRM measurement configuration and/or radio bearer configuration. 19. The network device according to claim 18, wherein, The processor is also used to implement functions related to network capability opening and network data analysis.

Images