CN111866908B - Communication system and network equipment - Google Patents

Communication system and network equipment Download PDF

Info

Publication number
CN111866908B
CN111866908B CN201910360430.7A CN201910360430A CN111866908B CN 111866908 B CN111866908 B CN 111866908B CN 201910360430 A CN201910360430 A CN 201910360430A CN 111866908 B CN111866908 B CN 111866908B
Authority
CN
China
Prior art keywords
network
configuration
function
network element
layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910360430.7A
Other languages
Chinese (zh)
Other versions
CN111866908A (en
Inventor
曾清海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910360430.7A priority Critical patent/CN111866908B/en
Priority to PCT/CN2020/083516 priority patent/WO2020220943A1/en
Publication of CN111866908A publication Critical patent/CN111866908A/en
Application granted granted Critical
Publication of CN111866908B publication Critical patent/CN111866908B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Abstract

The application provides a communication system and network equipment, so that the transmission delay of transmission data can be reduced, and the cost is saved. The communication system may include: a first network element and a second network element, the first network element and the second network element communicating through a communication interface, wherein the first network element is configured to implement: a user plane processing function corresponding to the layer 1, a user plane processing function corresponding to the layer 2, and a user plane processing function corresponding to the user plane function UPF; the second network element is configured to implement: part of the radio resource control RRC functions and core network functions, wherein the core network functions include one or more of: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF.

Description

Communication system and network equipment
Technical Field
The present application relates to the field of communications, and more particularly, to a communication system and a network device.
Background
In the industrial internet, there are some demands for industrial control, such as ultra-reliable and low latency communication (URLLC) from end to end, low cost, and rapid deployment. Taking the transmission delay as an example, the minimum end-to-end transmission delay of the user plane required by the industrial control is less than 2 milliseconds (ms).
In the fifth Generation (5th Generation, 5G) network of the third Generation Partnership Project (3 GPP), the transmission delay of data from one terminal device to another terminal device is much longer than 2ms, and the low-delay requirement of industrial control cannot be satisfied.
In addition, network nodes and functions in current 3GPP 5G networks are complex, resulting in high implementation cost.
How to reduce the delay as much as possible is a problem to be solved urgently.
Disclosure of Invention
The application provides a communication system and a network device, which can reduce the transmission delay of transmission data.
In a first aspect, a communication system is provided, which may include: a first network element and a second network element, the first network element and the second network element communicating through a communication interface, wherein the first network element is configured to implement: a user plane processing function corresponding to the layer 1, a user plane processing function corresponding to the layer 2, and a user plane processing function corresponding to the user plane function UPF; the second network element is configured to implement: a first radio resource control, RRC, function and a core network function; wherein the core network functions include one or more of: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF.
Based on the technical scheme, according to the communication system provided by the embodiment of the application, the network part can comprise the first network unit and the second network unit, so that not only can corresponding network functions be realized, but also the requirements of industry control and other vertical industries on low delay, high reliability, low cost and rapid deployment of the communication network can be met. Furthermore, the first network element implements: the user plane processing function corresponding to the layer 1, the user plane processing function corresponding to the layer 2 and the user plane processing function corresponding to the user plane function UPF, so that when data is transmitted, if the data is transmitted from one terminal device to another terminal device, the data can be quickly transmitted to the another terminal device through the first network unit, the situation that the data needs to be transmitted to the another terminal device through a core network firstly is avoided, low-delay transmission can be realized, and ultra-low-delay service can be supported.
Optionally, the user plane handling function (handling) corresponding to layer 1 or layer 2 may include, for example and without limitation, one or more of the following: a function corresponding to a Service Data Attachment Protocol (SDAP), a function corresponding to a Packet Data Convergence Protocol (PDCP), a function corresponding to a Radio Link Control Protocol (RLC), a function corresponding to a Media Access Control (MAC), or a function corresponding to a physical layer (PHY).
Optionally, the user plane processing function corresponding to the user plane function UPF may include, for example and without limitation, one or more of the following: data to QoS flows, QoS flow to DRB mapping function, or data to DRB mapping function directly, etc.
With reference to the first aspect, in some implementations of the first aspect, the first network unit is further configured to implement a second RRC function, and the second RRC function includes: configuring one or more of: a special cell configuration (scellconfiguration), a secondary cell configuration (scellconfiguration), a radio link control configuration (RLC-configuration), a medium access control layer cell group configuration (MAC-cell group configuration ), or a physical cell group configuration (physical cell group configuration). Specific contents of these configurations can be referred to 3GPP ts38.331v15.4.0.
The first network element may perform (or process, or execute, or configure) one or more of the following configurations: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig.
Optionally, a special cell (SpCell, or may also be referred to as a primary cell), if it is a primary base station or a primary node (MN), the primary cell may be referred to as a primary cell (PCell); in the case of a secondary base station or a Secondary Node (SN), the primary cell may be referred to as a primary secondary cell (PSCell).
Optionally, the second RRC function may be used to configure one or more of the following function related parameters: power control, random access, beam management, hybrid automatic repeat request, HARQ, physical layer measurements, link adaptation, scheduling request, uplink and downlink scheduling, rate matching, automatic repeat request, ARQ, discontinuous reception, DRX.
Based on the above technical solution, the first network element may be configured to configure any one or more parameters.
With reference to the first aspect, in certain implementations of the first aspect, the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
The first network element may perform (or process, or execute) one or more of the following configurations: a cell or BWP related configuration, a CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the first aspect, in certain 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 configure one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.
Optionally, the physical channel includes: a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Broadcast Channel (PBCH), a Physical Random Access Channel (PRACH), a Physical Uplink Shared Channel (PUSCH), and a 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 unit may implement (or process, or perform): RRM measurement configuration and/or radio bearer configuration.
Based on the technical scheme, the first network unit executes part of the RRC function, and the second network unit executes the other part of the RRC function, so that the system can be quickly adapted to the state change of the air interface wireless link, and the air interface transmission performance is ensured.
Optionally, the first RRC function and the second RRC function may be completely different or partially the same, and in specific implementation, the functions may be flexibly deployed on the two units according to needs without being strictly limited.
Optionally, the radio bearer configuration includes, for example, configuring the SDAP and PDCP related parameters of the radio bearer, such as radio bearer configuration and RRMmeasurementconfig in 3GPP ts38.331v15.4.0.
The second network element may configure terminal equipment specific (UE-specific) RRC procedure related parameters including, but not limited to: RRM measurements, and/or, the SDAP and PDCP related parameters of the radio bearer, such as Radiobearerconfig and RRMmeasurementconfig in 3GPP ts38.331v15.4.0.
With reference to the first aspect, in certain implementations of the first aspect, the layer 1 includes: a physical layer (PHY); and/or, the layer 2 comprises: 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 access control layer MAC layer.
With reference to the first aspect, in certain implementation manners of the first aspect, the first network unit is further configured to implement mapping of downlink data to a data radio bearer DRB.
With reference to the first aspect, in certain implementations of the first aspect, the second network unit is further configured to implement a network capability opening and/or a network data analysis function.
Based on the technical scheme, the network capacity opening function is realized through the second network unit, and management, control or network information acquisition of a vertical industry service provider or a third-party application developer on a network can be facilitated. In addition, a network data analysis function (NWDAF) is realized by the second network element, and data acquisition and big data analysis can be performed in the second network element, so that the network can be intelligentized.
With reference to the first aspect, in certain 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, which may include: the first network unit and the second network unit communicate via a communication interface, the second network unit is configured to implement a first radio resource control, RRC, function, and the first network unit is configured to implement a second RRC function, where the second RRC function includes: configuring one or more of: the method comprises the following steps that SpCellConfig is configured in a special cell, SCellConfig is configured in an auxiliary cell, RLC-config is configured in wireless link control, MAC-cellGroupConfig is configured in a cell group of a media intervention control layer, or PhysicalcCellGroupConfig is configured in a cell group of a physical layer; 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 of the above listed items by the first network unit, the second network unit may not implement the part of the RRC function (i.e. the second RRC function), that is, the RCU may implement the first RRC function. Therefore, the system can be quickly adapted to the state change of the air interface wireless link, and the air interface transmission performance is ensured.
With reference to the second aspect, in certain implementations of the second aspect, the first network unit is further configured to implement mapping of downlink data to a data radio bearer DRB.
With reference to the second aspect, in certain implementations of the second aspect, the second network element is further configured to implement a network capability opening and/or a network data analysis related function.
With reference to the second aspect, in certain implementations of the second aspect, the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
The first network element may perform (or process, or execute) one or more of the following configurations: a cell or BWP related configuration, a CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the second aspect, in certain 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 channel includes: PDSCH, PDCCH, PBCH, PRACH, PUSCH, PUCCH.
With reference to the second aspect, in certain implementations of the second aspect, the layer 1 includes: a physical layer (PHY); and/or, the layer 2 comprises: 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 access control layer MAC layer.
With reference to the second aspect, in certain 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, which may include: a processor and a communication interface, the processor to implement: a function corresponding to a service data adaptation protocol SDAP, a function corresponding to a packet data convergence protocol PDCP, a function corresponding to a radio link layer control protocol RLC, a function corresponding to a media access control layer MAC, a function corresponding to a physical layer PHY, and a user plane processing function corresponding to a user plane function UPF; the communication interface is used for communicating with a target device.
Based on the above technical solution, the network device can implement: user plane processing function corresponding to layer 1 (i.e. function corresponding to physical layer PHY), user plane processing function corresponding to layer 2 (i.e. function corresponding to service data adaptation protocol SDAP, function corresponding to packet data convergence protocol PDCP, function corresponding to radio link layer control protocol RLC, function corresponding to media access control layer MAC), and user plane processing function corresponding to user plane function UPF, so that when data is transmitted, if data is transmitted from one terminal device to another terminal device, rapid transmission of data to another terminal device can be achieved through the first network unit, it is avoided that data needs to be transmitted to another terminal device through the core network first, low-delay transmission can be achieved, ultra-low-delay service can be supported
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 special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
With reference to the third aspect, in certain implementations of the third aspect, the SpCellConfig includes at least one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the third aspect, in certain 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 channel includes: PDSCH, PDCCH, PBCH, PRACH, PUSCH, PUCCH.
With reference to the third aspect, in certain implementations of the third aspect, the processor is further configured to: mapping of downlink data to data radio bearers DRBs.
In a fourth aspect, a network device is provided, which may include: a processor and a communication interface, the processor to implement: a first RRC function and a core network function, the core network function comprising one or more of: an access and mobility management function, AMF, a session management function, SMF, a policy control function, PCF, or an authentication service function, AUSF, wherein the first RRC function comprises: configuration: a radio resource management, RRM, measurement configuration and/or a radio bearer configuration; the communication interface is used for communicating with a target device.
With reference to the fourth aspect, in some implementations of the fourth aspect, the processor is further configured to implement network capability opening and network data analysis related functions.
In a fifth aspect, a method for data transmission is provided, where the method may be performed by a network device, or may also be performed by a chip or a circuit configured in the network device, and this application is not limited thereto.
The method can comprise the following steps: the first network equipment receives a data packet from the first terminal equipment; and the first network equipment routes the data packet to a destination address corresponding to the data packet.
Based on the above technical solution, the data can be routed to the destination address quickly by the direct routing of the first network device, and the need of routing to the destination address corresponding to the data packet through the core network is avoided, so that the low-delay transmission between the terminal device (for example, referred to as the first terminal device) and other devices can be realized, and the ultra-low-delay service can be supported.
With reference to the fifth aspect, in certain implementations of the fifth aspect, the destination address corresponds to one or more of: the system comprises a data network, a second terminal device, a network device where the second terminal device is located, a local application of the first network device, or the second network device.
Based on the above technical solution, through the direct routing of the first network device, the data can be quickly routed to one or more of 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, and the like, thereby avoiding the need to send the data to these devices through the core network, and thus achieving the low-latency transmission between the terminal device (for example, denoted as the first terminal device) and the network device application or other terminal devices (for example, denoted as the second terminal device), and supporting the ultra-low-latency service. The first network device may route the packet to the second network device, and the second network device may route the packet to the data network.
Optionally, the second terminal device may include: the terminal device under the first network device, and/or the terminal device under other network devices.
The first network device may route the data packet to another network device, and then route the data packet to the data network by the other network device, and further transmit the data packet 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 processing function corresponding to a user plane function UPF.
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: a function corresponding to SDAP, a function corresponding to PDCP, a function corresponding to RLC, a function corresponding to MAC, or a 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 special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
With reference to the fifth aspect, in certain implementations of the fifth aspect, the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the fifth aspect, in certain 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 certain implementations of the fifth aspect, the data packet is not processed by a service data adaptation protocol, SDAP, entity.
With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further comprises: and the first network equipment sets a service quality QoS reflection function in a PDCP layer of a radio bearer RB corresponding to the data packet.
In a sixth aspect, a method of data transmission is provided, which may include: the first network equipment receives a data packet from the terminal equipment; the first network device routes the data packet to a second network device; the second network device routes the data packet to a data network.
Based on the above technical solution, when the first network device is not directly connected to the data network, the first network device routing function module may forward the uplink data to the second network device in a routing manner, and then the second network device routes the uplink data 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 processing function corresponding to a user plane function UPF.
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: a function corresponding to SDAP, a function corresponding to PDCP, a function corresponding to RLC, a function corresponding to MAC, or a 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 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 sixth aspect, in some implementations of the sixth 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 special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
With reference to the sixth aspect, in certain implementations of the sixth aspect, the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the sixth aspect, in certain 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 certain implementations of the sixth aspect, the data packet is not processed by a service data adaptation protocol, SDAP, entity.
With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further comprises: and the first network equipment sets a service quality QoS reflection function in a PDCP layer of a radio bearer RB corresponding to the data packet.
In a seventh aspect, a communication apparatus is provided, which includes a processing unit and a communication unit, wherein the communication unit is configured to receive a data packet from a first terminal device; the processing unit is configured to: and routing the data packet to a destination address corresponding to the data packet.
With reference to the seventh aspect, in some implementations of the seventh aspect, the destination address corresponds to one or more of: the system comprises a data network, a second terminal device, a network device where the second terminal device is located, a local application of the first network device, or the 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 processing function corresponding to a user plane function UPF.
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: a function corresponding to SDAP, a function corresponding to PDCP, a function corresponding to RLC, a function corresponding to MAC, or a 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 comprises: configuring one or more of: the special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
With reference to the seventh aspect, in certain implementations of the seventh aspect, the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration; the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
With reference to the seventh aspect, in certain implementations of the seventh aspect, the configuring 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 a service data adaptation protocol, SDAP, entity.
With reference to the seventh aspect, in certain implementations of the seventh aspect, the method further includes: and the processing unit sets a service quality QoS reflection function in a PDCP layer of a radio bearer RB corresponding to the data packet.
In an eighth aspect, a communication apparatus is provided, which has the function of implementing the first network unit of the first aspect or the second aspect. These functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.
In a ninth aspect, there is provided a communication apparatus having a function of the second network unit implementing the first or second aspect. These functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.
A tenth aspect provides a communication apparatus having a function of implementing the network device of the third aspect. These functions may be implemented by hardware, or by hardware executing corresponding software. 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 may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.
In a twelfth aspect, a communication device is provided, which comprises a memory for storing a computer program or instructions, a communication interface, and a processor, wherein the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the device is caused to perform the functions of the first network unit of the first or second aspect.
In a thirteenth aspect, a communication device is provided, the device comprising a memory for storing a computer program or instructions, a communication interface, and a processor, the processor being coupled to the memory and the communication interface, and the computer program or instructions, when executed by the processor, causing the device to perform the functions of the second network element of the first or second aspect.
In a fourteenth aspect, there is provided a communication apparatus comprising a memory for storing a computer program or instructions, a communication interface, and a processor coupled to the memory and the communication interface, wherein the processor, when executing the computer program or instructions, causes the apparatus to perform the functions of the network device of the third aspect.
In a fifteenth aspect, a communication apparatus is provided, which comprises a memory for storing a computer program or instructions, a communication interface, and a processor, wherein the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the apparatus is caused to perform the functions of the network device of the fourth aspect.
In a sixteenth aspect, a communication apparatus is provided, which comprises a memory for storing a computer program or instructions, a communication interface, and a processor, wherein the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the apparatus is caused to perform the functions of the first network device of the fifth aspect.
In a seventeenth aspect, a computer program product is provided, the computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the functions of the first network element of the first or second aspect described above.
In an eighteenth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the functions of the second network element of the first or second aspect described above.
In a nineteenth aspect, there is provided a computer program product, the computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the functions of the network device of the third aspect.
In a twentieth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the functions of the network device of the fourth aspect described above.
In a twenty-first aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the functions of the first network device of the above fifth aspect.
A twenty-second aspect provides a computer-readable storage medium storing a computer program which, when executed, implements the functionality of the first network element of the above-mentioned first or second aspect.
A twenty-third aspect provides a computer-readable storage medium storing a computer program which, when executed, implements the functionality of the second network element of the first or second aspect.
A twenty-fourth aspect provides a computer-readable storage medium storing a computer program that, when executed, implements the functions of the network device of the above-described third aspect.
A twenty-fifth aspect provides a computer-readable storage medium storing a computer program that, when executed, implements the functions of the network device of the fourth aspect.
A twenty-sixth aspect provides a computer-readable storage medium storing a computer program which, when executed, implements the functions of the first network device of the above-described fifth aspect.
In a twenty-seventh aspect, a communication system is provided, the communication system comprising a first network device and a second network device as described above.
Drawings
FIG. 1 is a schematic diagram of a 3GPP 5G system architecture;
fig. 2 and 3 are schematic diagrams of a NG-RAN architecture;
FIG. 4 is a schematic diagram of the distribution of air interface protocol stacks in the case that CUs are divided into CU-UP and CU-CP;
FIG. 5 is a schematic block diagram of a communication system provided in accordance with an embodiment of the present application;
fig. 6 is a schematic block diagram of yet another communication system provided in accordance with an embodiment of the present application;
FIG. 7 is a schematic block diagram of a network device provided in accordance with embodiments of the present application;
FIG. 8 is a schematic block diagram of yet another network device provided in accordance with an embodiment of the present application;
FIG. 9 is a schematic interaction diagram of a terminal device access procedure suitable for use with embodiments of the present application;
FIG. 10 is a schematic interaction diagram of data transfer suitable for use with embodiments of the present application;
FIG. 11 is a schematic diagram of a QoS framework defined by the 3GPP NR existing protocol;
FIG. 12 is a diagram illustrating a PDCP PDU format suitable for use in an embodiment of the present application;
FIG. 13 is a schematic block diagram of a communications device provided in accordance with an embodiment of the present application;
fig. 14 is a schematic structural diagram of a communication device provided in accordance with an embodiment of the present application;
fig. 15 is a schematic structural diagram of a communication device provided in an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a 5th Generation (5G) system, a New Radio (NR) or future communication system, etc.
It should be understood that the embodiment of the present application does not particularly limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the method provided by the embodiment of the present application can be executed, or the program recorded with the code of the method provided by the embodiment of the present application is executed, so as to perform communication according to the method provided by the embodiment of the present application. For example, an execution main body of the method provided by the embodiment of the present application may be a terminal or a network device, or a functional module capable of calling a program and executing the program in the terminal or the network device.
For the purpose of understanding the embodiments of the present application, a schematic diagram of a 3rd Generation Partnership Project (3 GPP)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 (non-roaming) architecture. The network architecture may specifically include the following network elements:
1. user Equipment (UE): may refer to a terminal device, access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. 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 handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.
2. Access Network (AN): the method provides a network access function for authorized users in a specific area, and can use transmission tunnels with different qualities according to the level of the users, the requirements of services and the like. The access network may be an access network employing different access technologies. There are two types of current radio access technologies: third Generation Partnership Project (3 GPP) access technologies such as the radio access technologies employed in 3G, 4G or 5G systems and non-third Generation Partnership Project (non-3GPP) access technologies. The 3GPP Access technology refers to an Access technology meeting 3GPP standard specifications, and an Access Network adopting the 3GPP Access technology is referred to as a Radio Access Network (RAN), where an Access Network device in a 5G system is referred to as a next generation Base station (gNB). The non-3GPP access technology refers to an access technology that does not conform to the 3GPP standard specification, for example, an air interface technology represented by an Access Point (AP) in wifi.
An access network that implements an access network function based on a wireless communication technology may be referred to as a Radio Access Network (RAN), and a 5G radio access network of 3GPP may become a next generation radio access network (NG-RAN). The radio access network can manage radio resources, provide access service for the terminal, and further complete the forwarding of control signals and user data between the terminal and the core network.
The Radio Access Network may be, for example, a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, an evolved node b (eNB, eNodeB) in an LTE System, a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the Network device may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network device in a future 5G Network, or a Network device in a future evolved PLMN Network. The embodiments of the present application do not limit the specific technologies and the specific device forms adopted by the radio access network device.
3. Access and mobility management function (AMF) entity: the method is mainly used for mobility management, access management and the like.
4. Session Management Function (SMF) entity: the method is mainly used for session management, Internet Protocol (IP) address allocation and management of the UE and the like.
5. User Plane Function (UPF) entity: i.e. a user plane gateway. The method can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, and the like. The user data can be accessed to a Data Network (DN) through the network element.
6. Data Network (DN): for providing a network for transmitting data. Such as a network of carrier services, an Internet network, a third party's service network, etc.
7. Authentication service function (AUSF) entity: the method is mainly used for user authentication and the like.
8. Network open function (NEF) entity: for securely opening services and capabilities, etc. provided by the 3GPP network functions to the outside.
9. The network storage function (NF) entity is used to store the network function entity and the description information of the service provided by the network function entity, and support service discovery, network element entity discovery, etc.
10. Policy Control Function (PCF) entity: the unified policy framework is used for guiding network behaviors, providing policy rule information for control plane function network elements (such as AMF and SMF network elements) and the like.
11. Unified Data Management (UDM) entity: for handling subscriber identification, access authentication, registration, or mobility management, etc.
12. Application Function (AF) entity: the method is used for carrying out data routing of application influence, accessing network open function network elements, or carrying out strategy control by interacting with a strategy framework 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 (NAS) messages, and the like. The N3 interface is AN interface between (R) AN and UPF entities for transmitting user plane data and the like. The N4 interface is an interface between the SMF entity and the UPF entity, and is used to transmit information such as tunnel identification information, data cache indication information, and downlink data notification message of the N3 connection. The N6 interface is an interface between the UPF entity and the DN, and is used for transmitting user plane data and the like.
It should be understood that the above network architectures are merely illustrative of network architectures described from the perspective of conventional point-to-point architectures and service architectures, and are not intended to be limiting in this application.
It should also be understood that the AMF entity, SMF entity, UPF entity, NSSF entity, NEF entity, AUSF entity, NRF entity, PCF entity, UDM entity shown in fig. 1 may be understood as network elements in the core network for implementing different functions, e.g. may be combined into network slices as needed. The core network elements may be independent devices, or may be integrated in the same device to implement different functions, which is not limited in this application.
It should be understood that the above-mentioned names are only used for distinguishing different functions, and do not represent that these network elements are respectively independent physical devices, and the present application is not limited to the specific form of the above-mentioned network elements, for example, they may be integrated in the same physical device, or they may be different physical devices. Furthermore, the above nomenclature is only used to distinguish between different functions, and should not be construed as limiting the application in any way, and this application does not exclude the possibility of other nomenclature being used in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may follow the terminology in 5G, and may also adopt other names, etc. The description is unified here, and will not be repeated below.
It should also be understood that the name of the interface between each network element in fig. 1 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this application. In addition, the name of the transmitted message (or signaling) between the network elements is only an example, and the function of the message itself is not limited in any way.
The general architecture of the NG-RAN is briefly described below in connection with fig. 2 and 3.
As shown in FIG. 2, a core network device 103, such as a fifth generation core network (the 5)thgeneration core network, 5GC), either the complete access network device 101, such as the gNB, or the access network device 102 including a Centralized Unit (CU) 201 and a Distributed Unit (DU) 202 may be connected.
CU201 and DU202 may be software-based or virtualized, and Radio access network functions that need to be flexibly combined may be operated in CU201, for example, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and other high layer functions; the RAN function that is strongly related to hardware and has a high real-time requirement is executed in the DU202, for example, the Radio Link Control (RLC) layer, the physical layer (PHY), the Media Access Control (MAC) layer, and other underlying functions.
CU201 and DU202 are connected via a communication interface. CU201 is also connected to core network devices via a communication interface. In the embodiment of the present application, the communication interface between CU201 and DU202 may be referred to as an F1 interface. The interface between CU201 and the core network devices may be referred to as the N2 interface or the NG interface. As shown in fig. 2, an access network device 102 may include a CU201, one or more DUs 202. CU201 is connected to DU202 using F1 interface. One DU202 can only be connected to one CU201, and one CU201 can be connected to one or more DUs 202.
For example, taking the access network device 102 as a gNB, 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 may be connected to a plurality of gNB-DUs. The gNB-CU and its connected gNB-DUs appear to other gNBs and 5 GCs as a gNB.
Fig. 3 is a diagram illustrating a new architecture based on the architecture of fig. 2, in which a CU includes a Centralized Unit-user plane (CU-UP) 301 and a Centralized Unit-control plane (CU-CP) 302. Where CU-UP301 and CU-CP302 may be on different physical devices. There may be an open interface between CU-UP301 and CU-CP302, which may be referred to as an E1 interface. Meanwhile, each of the CU-UP301 and CU-CP302 and DU may have its own interface, for example, the interface between CU-CP302 and DU may be referred to as F1-C interface, and the interface between CU-UP301 and DU may be referred to as F1-U interface.
For the architecture of fig. 3, the following characteristics may be present: an access network device 102 may include one CU-CP302, one or more CU-UPs 302, and a plurality of DUs. One DU may connect one CU-CP 302. One CU-UP301 can be connected to only one CU-CP 302. One DU may be connected to a plurality of CU-UPs 301 under the control of the same CU-CP 302. One CU-UP301 may be connected to multiple DUs under the control of the same CU-CP 302.
For example, taking the access network device 102 as the gNB for example, one gNB-DU and one gNB-CU-UP are both connected to only one gNB-CU-CP. One gNB-DU may be connected to multiple gNB-CU-UP and one gNB-CU-UP may be connected to multiple gNB-DUs under the control of the same gNB-CU-CP.
Fig. 4 is a schematic diagram of the distribution of an air interface protocol stack in the case that the access network device includes a CU and a DU, and further, in the CU portion, the CU includes a CU-UP and a CU-CP.
As can be seen from fig. 4, the air interface protocol stack, whether it is the user plane or the control plane, is that the RLC, MAC, PHY operate in the DU part (e.g., gNB-DU), and the PDCP and the above protocol layers operate in the CU part (e.g., gNB-CU). The RRC can realize the connection control of air interface wireless resources and air interfaces; the SDAP may perform mapping between quality of service (QoS) -flow (QoS-flow) and Data Radio Bearer (DRB). QoS-flow is a traffic data flow with specific QoS requirements. The functions of other protocol layers are not described in detail, and reference may be made to the 3GPP protocol specification. This is not limited in this application.
Industrial control in the industrial internet has some requirements of end-to-end ultra-reliable and low latency communication (URLLC), low cost, and rapid deployment. The end-to-end user plane delay required by industrial control is at least less than 2 ms.
As can be seen from the 3GPP 5G network architecture shown in fig. 1, in a 3GPP 5G network, data may need to pass through the following nodes and transmission interfaces between them, when data is transmitted from terminal device a to terminal device B: terminal device 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 the access network device, such as the gNB, has no CU/DU and CP/UP separation, the end-to-end transmission delay from the terminal device to the terminal device is much longer than 2ms, and the low-delay requirement of industrial control cannot be met. Meanwhile, network nodes and functions in the current 3GPP 5G network are complex, resulting in high implementation cost.
In view of this, the present application provides a network unit and a network architecture, which can reduce the time delay and save the cost.
Various embodiments provided herein 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 in an embodiment of the present application. The communication system 500 may comprise a first network element 510 and a second network element 520.
The communication system 500 provided in the embodiment of the present application may be referred to as a very simple network architecture, a very simple network system, a very simple communication system, or the like, for example, as shown in fig. 5, a network part may include a first network unit 510 and a second network unit 520, which may not only implement corresponding network functions, but also meet the requirements of the industry vertical industries such as industrial control and the like on low-latency, high-reliability, low-cost, and fast deployment of a communication network.
In the communication system 500, the first network element 510 and the second network element 520 may communicate via a communication interface.
This is described in more detail below in connection with the embodiments of fig. 8 and 9.
In one possible design, the first network element 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 element 520 is configured to implement: a first RRC function and a core network function, wherein the core network function includes one or more of: AMF, SMF, PCF, or AUSF.
In yet another possible design, the first network unit 510 is configured to implement: a second RRC function; the second network element 520 is configured to implement: a 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: a special cell configuration (scellconfiguration), a secondary cell configuration (scellconfiguration), a radio link control configuration (RLC-configuration), a medium access control layer cell group configuration (MAC-cell group configuration ), or a physical cell group configuration (physical cell group configuration). Wherein, a special cell (SpCell, or may also be referred to as a primary cell), if it is a primary base station or a primary node, the primary cell may refer to a primary cell (PCell); in case of a secondary base station or a secondary node, the primary cell may be referred to as a primary secondary cell (PSCell).
It should be understood that the first RRC function and the second RRC function are only named for differentiation and do not limit the 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 completely different, and the functions may be flexibly deployed on the two network elements according to needs in specific implementation, which is not strictly limited.
It should also be understood that the two possible designs described above can be used alone or in combination, without limitation.
The first network unit 510 and the second network unit 520 described above are described in detail below.
The first network element 510 may be used to implement all user plane processing functions.
That is, the first network element 510 may be configured to implement all user plane processing functions, for example, the first network element 510 may be configured to implement user plane processing functions in a 3GPP Rel-155G system, or it may also be understood that user plane control in a 3GPP Rel-155G system is centralized in one network element, i.e., the first network element 510.
It should be understood that in the embodiment of the present application, the first network unit 510 may be used to implement all the user plane processing functions. In the data transmission process, in the process of transmitting data 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 that the data can reach the destination only by passing through multiple network elements, thereby reducing the user plane data transmission and processing delay.
For example, data transmission from one terminal device to another terminal device is taken as an example.
One existing transmission process is: data from one terminal device is transmitted from the DU to the CU, then from the CU to the UPF, and then to the other terminal device. In the embodiment of the present application, in consideration of the transmission delay through the network units, such as the transmission delay from DU to CU and the transmission delay from CU to UPF, the user plane control (or user plane processing) of these network units may be centralized to the first network unit 510, that is, the first network unit 510 performs the user plane processing function, for example, data from a terminal device may be transmitted to the first network unit 510 first, and then the first network unit 510 transmits the data to another terminal device, so that the first network unit 510 may implement fast transmission from one terminal device to another terminal device, and further, the processing delay of data through each network unit may be saved.
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 a user plane function UPF.
Illustratively, the user plane handling function (handling) corresponding to layer 1 or layer 2, for example, may include, but is not limited to, one or more of the following: a function corresponding to SDAP, a function corresponding to PDCP, a function corresponding to RLC, a function corresponding to MAC, or a function corresponding to PHY.
For example, the first network element 510 may be used to implement the functionality corresponding to the SDAP, which may include, but is not limited to: mapping between QoS flow and data radio bearer, and/or marking QoS Flow Indicator (QFI) in downlink data packet and uplink data packet.
As another example, the first network unit 510 may be configured to implement PDCP corresponding functionality, which may include, for example, one or more of the following: data transmission, encryption and decryption, integrity protection and verification, header compression and decompression using a robust header compression (ROHC) protocol, timer-based Service Data Unit (SDU) discard, split bearer (split bearer) routing, duplication (duplication), reordering and in-order delivery, out-of-order delivery, or duplicate packet discard, among others. The detailed functions can be referred to 3GPP ts38.323v15.4.0. The other protocol layers are similar in function and will not be described in detail later.
As another example, the first network element 510 may be configured to implement RLC corresponding functionality, which may include, for example, one or more of the following: upper layer PDU transmission, sequence numbering, error correction by automatic repeat request (ARQ), RLC SDU segmentation and re-segmentation, SDU reassembly, duplicate detection, RLC SDU discard, RLC re-establishment, or protocol error detection, etc.
As another example, the first network element 510 may be configured to implement MAC corresponding functionality, which 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 by HARQ, priority handling between terminal devices by dynamic scheduling, priority handling between logical channels of one terminal device by logical channel priority ordering, or MAC PDU padding, etc.
As another example, the first network element 510 may be configured to implement PHY-corresponding functionality, which may include, for example, one or more of: transport block CRC attachment, channel coding, physical layer HARQ processes, rate matching, scrambling (scrambling), error detection on transport channels, modulation and demodulation of physical channels, radio frequency processing, or multiple input multiple output antenna processing, etc.
It should be understood that the foregoing exemplarily lists a function corresponding to the SDAP, a function corresponding to the PDCP, a function corresponding to the RLC, a function corresponding to the MAC, and a function corresponding to the PHY, and specifically, reference may be made to the existing description of 3GPP TS38.300V15.4.0, and the embodiment of the present application is not limited thereto.
Illustratively, the UPF corresponds to a user plane processing function, including a routing function (routing). That is, the first network element 510 may also be used to implement routing functions. Routing functions, for example including but not limited to one or more of the following: packet routing and forwarding, packet detection, user plane policy rule enforcement, user plane QoS processing, mapping of data to QoS flows, or mapping of data directly to DRBs (if SDAP is not configured or if the SDAP layer is not configured), etc.
It should be understood that the above-listed user plane processing functions corresponding to layer 1 or layer 2 and the user plane processing functions corresponding to UPF are only exemplary, and the embodiments of the present application are not limited thereto.
In the prior art, in the transmission process of downlink data from a UPF to a base station, the UPF performs mapping from the downlink data to QoS streams, and performs differential processing by performing different scheduling priorities on the downlink data of different QoS streams, so as to preferentially meet the transmission performance requirement of high-priority QoS streams.
With the present application, the first network unit 510 can implement a UPF function and a user plane processing function. In other words, there is no transmission process of the UPF to the base station. Therefore, with the embodiment of the present application, the mapping of the downlink data to the DRB can be directly implemented in the first network unit 510, that is, it can be understood that the mapping of the downlink data to the QoS flow is cancelled or not.
In addition, the first network unit 510 may implement mapping from downlink data to a DRB, and deliver the downlink data to a PDCP layer corresponding to the DRB, so that the data may not be processed by the SDAP layer, that is, in this embodiment, the SDAP layer may or may not be configured. As will be described in detail below.
Optionally, the first network element 510 may be configured to configure one or more of: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig.
That is, the first network element 510 may be configured to perform one or more of the following, or the first network element 510 may be configured to perform one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig.
Optionally, the second RRC function includes: configuring one or more of the following functionally related parameters: power control, random access, beam management, hybrid automatic repeat request, HARQ, physical layer measurements, link adaptation, scheduling request, uplink and downlink scheduling, rate matching, automatic repeat request, ARQ, or discontinuous reception, DRX.
Optionally, the SpCellConfig comprises one or more of: a cell or bandwidth part (BWP) related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
Optionally, the SCellConfig includes one or more of: a cell or BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
Optionally, the cell or BWP related configuration comprises 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 description is only exemplary, and the embodiments of the present application are not limited thereto.
The second network element 520 may be configured to implement the first RRC function as well as the core network function.
The second network element 520 is configured to implement the first RRC function, e.g., the second network element 520 is configured to implement the L3 control plane function; for another example, the second network element 520 is configured to implement a function of the RRC functions other than the second RRC function; as another example, the second network element 520 is configured to implement RRM measurement configurations and/or radio bearer configurations.
The radio bearer configuration includes, for example, configuring parameters related to the SDAP and PDCP of the radio bearer, such as radio bearer configuration and RRMmeasurementconfig in 3GPP ts38.331v15.4.0.
In this case, the first network element 510 in the communication system 500 may not implement the second RRC function by implementing the second RRC function, and the second network element 520 in the communication system 500 may not implement the part of the RRC function, that is, the second network element 520 may implement the first RRC function, such as being responsible for configuration and reconfiguration of other functions. Therefore, the system can be quickly adapted to the state change of the air interface wireless link, and the air interface transmission performance is ensured.
The core network functions that the second network element 520 uses for implementation include one or more of the following: a function corresponding to an AMF, a function corresponding to an SMF, a function corresponding to a PCF, or a function corresponding to an AUSF.
For example, the second network element 520 is used to implement the corresponding functionality of the AMF. The function corresponding to the AMF may include, for example, functions other than session management, such as functions of registration management, connection management, reachability management, mobility management, lawful interception, or access authorization (or authentication), among Mobility Management Entity (MME) functions of the 3GPP EPS.
As another example, the second network element 520 is configured to implement a corresponding function of the SMF. The corresponding functionality of the SMF may include, for example, one or more of: session management, UE IP address assignment and management, selection and management of user plane functions, policy control, or termination of charging function interfaces, and downstream data notification, etc.
As another example, second network element 520 is configured to implement a function corresponding to the PCF. The corresponding functions of the PCF may include, for example: a unified policy framework that guides network behavior, and/or policy rule information for control plane functional network elements (e.g., AMFs, SMF network elements, etc.), etc.
As 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 description is only exemplary, and the embodiments of the present application are not limited thereto.
Optionally, the second network element 520 may also be used to implement network capability opening and network data analysis related functions. For example, the simplest network management and control functions can be provided for vertical industry service providers or third party application developers through standard API interfaces, network management is simplified, and network intelligence is enabled.
Exemplarily, the second network element 520 may be configured to implement a network capability opening function. The NEF function is implemented by the second network unit 520, which may facilitate management, control or network information acquisition of the vertical industry service provider or third party application developer.
Illustratively, the second network element 520 is configured to implement network data analysis related functions. The second network unit 520 realizes a network data analysis function (NWDAF), and data acquisition and big data analysis can be performed in the second network unit 520, so that the network can be intelligentized.
Optionally, the second network element 520 may also be used to implement a routing function.
Alternatively, the first network element 510 may be a Local Transmission Unit (LTU) and the second network element 520 may be a Remote Control Unit (RCU).
It should be understood that the first network unit 510 may be replaced by an LTU and the second network unit 520 may be replaced by an RCU.
It should also be understood that the LTU and RCU are only names, and do not limit the scope of the embodiments of the present application. Embodiments of the present application do not preclude the possibility of using other nomenclature in 5G networks as well as other networks in the future.
Based on the technical scheme, according to the communication system provided by the embodiment of the application, the network part can comprise the first network unit and the second network unit, so that the corresponding network function can be realized, and excessive network nodes and excessively complex interfaces are avoided by simplifying the network nodes and the functions, so that the requirements of the vertical industries such as industrial control and the like on low delay, high reliability, low cost and rapid deployment of the communication network can be met. Furthermore, the first network element implements: the user plane processing function corresponding to the layer 1, the user plane processing function corresponding to the layer 2 and the user plane processing function corresponding to the user plane function UPF, so that when data is transmitted, if the data is transmitted from one terminal device to another terminal device, the data can be quickly transmitted to another terminal device through the first network unit, the situation that the data needs to be transmitted to another terminal device through a core network firstly is avoided, low-delay transmission can be realized, and ultra-low-delay service can be supported.
For ease of understanding, the first network unit 510 is an LTU, and the second network unit is an RCU, which are exemplarily described with reference to fig. 6.
Fig. 6 is a schematic interaction diagram of a communication system 600 provided in an embodiment of the present application. Communication system 600 may include LTUs and RCUs. The configuration and parameters related to fig. 6 can refer to the description of the embodiment of fig. 5, and are not repeated here.
The LTU corresponds to a first network element 510 in the communication system 500 and the RCU corresponds to a second network element 520 in the communication system 500.
As shown in fig. 6, in a communication system 600, LTUs and RCUs may communicate over an interface.
In one possible design, the LTU is used to implement: a user plane processing function corresponding to the layer 1, a user plane processing function corresponding to the layer 2 and a user plane processing function corresponding to the UPF; the RCU is used to implement: a first RRC function and a core network function.
For LTUs, the LTUs may be used to implement: l1 and/or L2 user plane functions, such as shown in FIG. 6: the function corresponding to the SDAP, the function corresponding to the PDCP, the function corresponding to the RLC, the function corresponding to the MAC, and the function corresponding to the PHY may also be used to implement: the UPF corresponds to a user plane processing function (i.e., routing function).
In yet another possible design, the LTU is configured to configure one or more of: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig; the RCU is used to implement: the RRC function is a function other than SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcCellGroupConfig described above.
With respect to SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcCellGroupConfig, reference is made to the description in the embodiment of FIG. 5, and the details are not repeated herein.
As shown in fig. 6, for the RCU, the RCU may be configured to implement a connection control function, that is, an air interface layer 3 control plane function (e.g., a first RRC function), and the RCU may further include a core network function (or a necessary function of the core network), for example, a function corresponding to the AMF, a function corresponding to the SMF, a function corresponding to the PCF, a function corresponding to the AUSF, and the like shown in fig. 6.
As shown in fig. 6, the LTU may also be used to implement a second RRC function, including for example that the LTU may be used to configure one or more of: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig to achieve a fast response to an interface change. In this case, the RCU no longer implements this part of the RRC function.
As shown in fig. 6, the RCU may also be used to implement one or more of the following functions: routing function of UPF, NEF, or NWDAF.
Illustratively, where the RCU includes the routing functionality of the UPF, the LTU may be assisted in routing the packet to the foreign network or to another LTU without the LTU having a direct external interface to the user.
Illustratively, where the RCU includes NEF functionality, it may facilitate management, control, or network information acquisition of the network by a vertical industry service provider or a third party application developer.
Illustratively, where the RCU includes NWDAF functionality, data information gathering and big data analysis may be performed within the RCU, enabling network intelligence.
Alternatively, the mobile network is connected to a Data Network (DN) through the RCU, and the LTU may not be directly connected to the DN, or data forwarding and the like may be implemented through an interface to the DN and/or the LTU.
Optionally, the RCU also has an interface with other network devices (e.g., the gNB or the gNB and other standard access network nodes (e.g., LTE standard enbs)). If other network devices are also LTU and RCU architectures, the two RCUs may be connected through an interface.
Based on the above technical solution, the network architecture provided by the embodiment of the present application can not only reduce the network deployment cost and implement the fast 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; the RCU implements other functions of the RRC (e.g., a first RRC function), for example, the RCU may be responsible for configuration and reconfiguration processes of other functions of the RRC, so that the system can adapt to changes in the state of an air interface wireless link quickly, and ensure transmission performance of the air interface, and within a plurality of LTUs managed by the RCU, a set of cell and RRC configuration such as RRM may be uniformly employed, thereby avoiding frequent reconfiguration due to movement of the terminal device, and reducing signaling of the air interface.
Fig. 7 is a schematic block diagram of a network device 700 according to an embodiment of the present application. The network device 700 corresponds to the first network unit 510 in the communication system 500 described above. 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 can be implemented in the form of hardware, and also can be implemented in the form of a software functional module. It should also be understood that the division of the units in the embodiments of the present application is illustrative, and is only one logical function division, and there may be other division manners in actual implementation. This is not limitative.
It should also be understood that the division of the modules or units in the embodiments of the present application is illustrative, and is only one division of logical functions, and there may be other divisions when the actual implementation is performed. The following description will be given taking the example of dividing each functional module or unit into corresponding functions.
The processing unit 710 is configured to implement: a user plane processing function corresponding to the layer 1, a user plane processing function corresponding to the layer 2, and a user plane processing function corresponding to the user plane function UPF; the communication unit 720 is used for communicating with the target device.
The target device may include, for example, a terminal device or other network device.
Optionally, the processing unit 710 is further configured to configure one or more of: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig.
Optionally, the processing unit 710 is further configured to implement: mapping of downlink data to data radio bearers DRBs.
It should be understood that reference may be made to the description of the LTU in the embodiment of fig. 5 with respect to the first network unit 510 and in the embodiment of fig. 6 with respect to the network device 700, which are not described herein again.
It should also be understood that the configurations and parameters referred to in fig. 7 can refer to the description of the embodiment in fig. 5, and are not repeated here.
Based on the above technical solution, all user plane processing functions, such as L1/L2 data processing and data routing functions, are implemented by the network device 700, so that when a target address of data to be transmitted is a local application of the network device 700 or other terminal devices (such as other terminal devices under the network device 700), the data can be routed to the target address quickly by the direct routing of the network device 700, and the data is prevented from being sent to the local application of the network device 700 or other terminal devices under the network device 700 through the core network, so that low-latency transmission between the terminal device and the application of the network device 700 or other terminal devices can be implemented, and an ultra-low-latency service can be supported.
Fig. 8 is a schematic block diagram of a network device 800 according to an embodiment of the present application. The network device 800 corresponds to the second network unit 520 in the communication system 500 described above. Network device 800 may include a processing unit 810 and a communication unit 820. The communication unit 820 may communicate with the outside, and the processing unit 810 may 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 can be implemented in the form of hardware, and also can be implemented in the form of a software functional module. It should also be understood that the division of the units in the embodiments of the present application is illustrative, and is only one logical function division, and there may be other division manners in actual implementation. This is not limitative.
It should also be understood that the division of the modules or units in the embodiments of the present application is illustrative, and is only one division of logical functions, and there may be other divisions when the actual implementation is performed. The following description will be given taking the example of dividing each functional module or unit into corresponding functions.
The processing unit 810 is configured to implement: a first RRC function and a core network function; the communication unit 820 is used for communicating with a target device.
The target device may include, for example, a terminal device or other network device.
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 network capability opening and network data analysis related functions.
Optionally, the core network functions include one or more of: 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 reference may be made to the description of the second network unit 520 in the embodiment of fig. 5 and the RCU in the embodiment of fig. 6 for the network device 800, which are not described herein again.
It should also be understood that the configuration and parameters referred to in fig. 8 can refer to the description of the embodiment in fig. 5, and are not repeated here.
It should be further understood that in the above embodiments of fig. 7 and 8, the network device 700 and the network device 800 are divided into functional modules, for example, the functional modules or units may be divided corresponding to the functions, or two or more functions may be integrated into one processing module or unit. The integrated modules or units may be implemented in the form of hardware, or may be implemented in the form of software functional modules. It should be noted that, in the embodiment of the present application, the division of the module or the unit is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
The network element and the network architecture proposed in the embodiments of the present application are described above with reference to fig. 5 to 8, and applications of the network element or the communication system are described with reference to the exemplary scenarios shown in fig. 9 to 12.
Fig. 9 is a schematic interaction diagram of a terminal device access procedure suitable for use in an embodiment of the application. Fig. 9 may include the following steps.
The first network element sends 910 an interface setup request message to the second network element.
The first network unit may be an LTU and the second network unit may be an RCU.
It should be understood that, in the embodiment of the present application, the first network unit 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 device 800 in the above embodiment, which may be specifically described with reference to the above embodiment and is not described herein again. The following is an exemplary description of the first network element and the second network element.
In this step, the first network element sends a setup request (setup request) message to the second network element. For example, the interface establishment request message may include: a first network element identification and first network element subordinate cell list information.
The first network element identification may be in the form of, for example: an Identity (ID) of the first network element, an index (index) of the first network element, or a name of the first network element, etc.
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 the interface establishment request message to the first network unit.
The second network element feeds back to the first network element 920, i.e. a response message can be established.
After receiving the interface establishment request message of the first network element, the second network element can acquire some information related to the first network element according to the parameters carried by the message, thereby providing input for decisions such as selection of the first network element for subsequent communication.
For example, the interface establishment request message includes: the identifier information of the first network element and the list information of the cell to which the first network element belongs can be obtained after the second network element receives the interface establishment request message.
The second network element feeds back to the first network element a setup response (setup response) message containing similar content as contained in the F1 setup response message. For example, the interface setup response message may include: information of the active cell list and system information. For another example, the interface setup response message may further include information such as a Public Land Mobile Network (PLMN) list and a Radio Access Network (RAN) area code that are available.
The RAN area code may be used to identify a RAN area to which the first network unit or the first network unit subordinate cell belongs, so that the terminal device in an RRC INACTIVE (RRC _ INACTIVE) state may determine whether to initiate an RRC connection recovery procedure according to the RAN area code.
After receiving the interface establishment response message, the first network element may obtain information such as an activated cell list, an available PLMN list, and system information according to the interface establishment response message. After obtaining the information, the first network element may broadcast the system information over the air interface.
930, the terminal device initiates a random access procedure to the first network element.
After the terminal equipment is powered on, downlink synchronization with a cell in the first network unit is completed, and system information is acquired, a random access process is initiated to the cell under the first network unit to access the network.
It should be understood that, in the embodiment of the present application, a specific random access process is not limited, for example, the random access process may be completed through four-step random access, or the random access process may be completed through two-step random access, which is not limited in the embodiment of the present application.
940, the terminal device initiates an RRC connection setup procedure to the first network element.
The RRC connection establishment procedure may include a three-way handshake.
First, a terminal device sends an RRC connection request (RRC connection request) message to a first network unit, and the first network unit forwards the RRC connection request message to a second network unit and informs the second network unit of an identifier and a cell identifier of the corresponding terminal device.
The identifier of the terminal device and the cell identifier may be carried in the RRC connection request message, or may be sent to the second network element through separate signaling.
Second, the second network element sends an RRC connection setup (RRC connection setup) message to the terminal device via the first network element.
That is, the second network element first sends an RRC connection setup message to the first network element, and then the first network element sends the RRC connection setup message to the terminal device.
Third, the terminal device completes RRC connection establishment between the terminal device and the network by the first network unit feeding back an RRC connection setup complete (RRC connection setup complete) message to the second network unit.
That is, the terminal device first sends an RRC connection setup complete message to the first network element, and then the first network element forwards the RRC connection setup complete message to the second network element.
Optionally, the terminal device may carry an attach request (attach request) message of a Non Access Stratum (NAS) in the RRC connection setup complete message. The attach request message may be used to initiate the attachment, i.e. authentication and registration, of the terminal device at the network NAS layer.
950, the terminal device initiates an attach procedure to the second network element.
The attach procedure (attachment procedure) may also include a three-way handshake procedure.
First, a terminal device sends an attach request message to a second network element through a first network element.
That is, the terminal device first sends an 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 single signaling, or may be carried in the RRC connection setup complete message in the previous step.
Second, the second network element sends an attach accept (attach accept) message to the terminal device via the first network element.
That is, the second network element first sends an attach accept message to the first network element, and then the first network element sends the attach accept message to the terminal device.
Thirdly, the terminal device feeds back an attach complete (attach complete) message to the second network unit through the first network unit to complete the attachment of the terminal device to the second network unit.
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 attach procedure of the three-way handshake, there may be also authentication, key derivation, distribution, etc. procedures between the terminal device and the second network element.
Generally, a mobile network system performs user authentication based on a Subscriber Identity Module (SIM) card or a Universal Mobile Telecommunications System (UMTS) SIM (usim) card to avoid the trouble of inputting a password manually by a user. In the embodiment of the application, in order to facilitate rapid deployment of vertical services, user authentication may also be performed based on a certificate. 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 procedure in this step.
960, the second network element initiates an access stratum security activation procedure.
And the second network unit derives the key used by 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.
The second network element may notify the terminal device of a key used for over-the-air transmission or some input parameters for generating the key, which may include a next-hop-chain counter (NCC), for example, through an Access Stratum (AS) security activation procedure (AS security activation).
It should be understood that this step is not strictly sequential to step 950, and may be performed in parallel or sequentially.
970, the second network element initiates a radio bearer establishment procedure.
After obtaining Packet Data Unit (PDU) session information configured by the terminal device, the second network element may initiate a radio bearer setup procedure (DRB setup procedure).
The embodiment of the present application does not limit when the second network unit obtains the PDU session information. For example, during the terminal device attach procedure, the second network element may obtain the PDU session information configured by the terminal device. For another example, the second network element may obtain the PDU session information corresponding to the requested service in a 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 procedure, the second network element sends a PDU session resource establishment request message to the first network element. The air interface bearer can be established for the terminal equipment through the radio bearer establishing process, and relevant parameters are configured. The relevant parameters may include, for example, logical channel priority of the bearer, etc.
The PDU session resource setup request message may include: PDU session ID, QoS parameter of each QoS flow corresponding to the PDU session, and the like.
The QoS parameters of a QoS flow may also be referred to as configuration parameters of the QoS flow. The QoS parameters for each QoS flow may include, for example, but are not limited to: PDU session Aggregation Maximum Bit Rate (AMBR), 5G QoS Identifier (5G QoS Identifier,5QI), or an Allocation and Retention Priority (ARP) parameter, etc.
9702, the first network element initiates an RRC reconfiguration.
After receiving the PDU session resource establishment request message, the first network element may perform mapping from QoS flow to DRB according to the QoS flow included in the PDU session and QoS parameters of each QoS flow corresponding to the PDU session, establish one or more air interface DRBs for the PDU session, and generate an RRC reconfiguration (RRC reconfiguration) message including configuration of the one or more air interface DRBs. The first network unit may issue the RRC reconfiguration message to the terminal device through the first network unit.
The terminal device receives the RRC reconfiguration message and applies the RRC reconfiguration message to take effect (i.e., configures the corresponding DRB), and sends an RRC reconfiguration complete message to the first network unit.
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.
The first network unit sends the PDU session resource establishment response message to the second network unit, and the first network unit sends the RRC reconfiguration message to the terminal equipment, wherein the requirements on the sequence are not strict.
For example, the first network element may also send the PDU session resource establishment response message to the second network element, and then send the RRC reconfiguration message to the terminal device. For another example, the first network element may also send the RRC reconfiguration message to the terminal device first, and then send the PDU session resource establishment response message to the second network element. For another example, the first network element may also send an RRC reconfiguration message to the terminal device and send a PDU session resource establishment response message to the second network element at the same time.
980, the first network element initiates an RRC reconfiguration procedure.
In embodiments of the application, the first network element may process or execute or implement one or more of the following: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig. Thus, the first network element may initiate a reconfiguration of L1 or L2 (i.e., SDAP, PDCP, RLC, MAC, and PHY) protocol layer parameters to quickly adapt to changes in air interface radio link status.
For example, in the case that the air interface wireless link becomes poor, the first network unit may reassert one or more of the following parameters to ensure that the transmission performance is not affected: the number of HARQ retransmissions of the MAC layer, the number of ARQ retransmissions of the RLC layer, or the reconfiguration of the PDCP layer to achieve packet repetition (packet repetition), etc.
And under the reconfiguration condition, the first network unit sends an RRC reconfiguration message to the terminal equipment, wherein the RRC reconfiguration message at least comprises radio bearer configuration. After the reconfiguration is successful, the terminal device returns an RRC reconfiguration complete message to the first network element.
In embodiments 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 procedure, for example, the second network element initiates related RRC reconfiguration procedures such as serving cell and RRM measurement.
It should be understood that the names of the messages referred to in the above embodiments are only exemplary, and the embodiments of the present application are not limited thereto, for example, other names may be used in future protocols to indicate similar meanings.
Based on the above technical solution, the first network unit may implement reconfiguration of protocol layer parameters of L1 or L2 (i.e., SDAP, PDCP, RLC, MAC, and PHY), and the second network unit may implement other functions of the RRC, for example, the second network unit may be responsible for configuration and reconfiguration processes of other functions of the RRC, so that the system may not only adapt to changes in the state of an air interface radio link quickly and ensure transmission performance of the air interface, but also may uniformly adopt RRC configurations such as a set of cell and RRM within a range of a plurality of first network units managed by the second network unit, thereby avoiding frequent reconfiguration due to movement of the terminal device and reducing air interface signaling. In addition, based on the above technical solution, the NR existing protocol may be reused as much as possible, reducing the influence on the terminal device, the first network unit, and the second network unit.
Fig. 10 is a schematic interaction diagram of data transmission suitable for use in embodiments of the present application. Fig. 10 may include the following steps.
Optionally, 1010 may be included. At 1010, upstream data arrives.
That is, the terminal device is to transmit data. The following description takes the uplink data as an example for accessing the web page.
For example, a PDU session is configured for a terminal device, where a QoS flow corresponding to a web page access service is mapped to a Data Radio Bearer (DRB) configured for the terminal device by a network, for example, denoted as DRB 1. When the terminal equipment opens the web page or clicks a certain hyperlink of the web page, uplink data for accessing the web page is generated and reaches the SDAP layer corresponding to the PDU session configured on the terminal equipment side.
Optionally, 1020 may be included. 1020, the L2 of the terminal device processes the uplink data.
After receiving the uplink data, the SDAP layer maps the uplink data to the DRB1 according to the configured mapping relationship from the QoS flow to the DRB, and delivers the uplink data to the PDCP layer corresponding to the DRB 1. The PDCP layer may first perform some processing on the uplink data, including but not limited to: ciphering, integrity protection, etc., and then handed to the RLC layer corresponding to the DRB 1. The RLC layer may perform acknowledged mode processing or unacknowledged mode processing on the uplink data first, and may also segment the uplink data and then give it to the MAC layer. And the MAC layer encapsulates the processed uplink data into one or more MAC PDUs and delivers the MAC PDUs to the PHY.
It should be understood that the above steps 1010 and 1020 are only exemplary, and the embodiment of the present application is not limited thereto.
And 1030, the terminal equipment sends uplink data to the first network equipment. Accordingly, the first network device receives the uplink data from the terminal device.
Upon receiving the MAC PDUs delivered by the MAC layer, the PHY may convert the MAC PDUs into Transport Blocks (TBs) and transmit the TBs to the first network device.
After receiving the processed uplink data, if no available uplink resource is found to transmit the uplink data, the MAC layer of the terminal device may initiate a scheduling request process to request the first network device to allocate an uplink resource for transmitting the uplink data.
The first network device may be an LTU.
It should be understood that the first network device 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 may specifically refer to the description of the above embodiment, which is not described herein again. The following takes the first network device as an example for illustration.
Optionally 1040 may be included. 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 gives the TBs to the MAC layer, and the MAC layer may restore the TBs into MAC PDUs and then give the MAC PDUs to the RLC layer. The RLC layer may perform data reassembly after segmentation, and after restoring the uplink data, deliver the uplink data to the PDCP layer. The PDCP layer may perform some processing on the uplink data, including but not limited to: encryption, data integrity verification and the like. The PDCP layer gives the decrypted and integrity-verified (if integrity-protected) uplink data to the SDAP layer. The SDAP layer may hand the upstream data to the routing function.
It should be understood that, in this step, the processing procedure of the received data by the first network device is only an exemplary illustration, and the application is not limited thereto.
1050, the first network device routes the upstream data to the destination address.
In this embodiment, 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 a destination address according to a destination IP address in the uplink data, where the destination address may be a corresponding data network, for example. The uplink data reaches a server of the terminal equipment for accessing the web page in an IP address addressing mode. The server will respond to the uplink data and feed back related content to the terminal device through the downlink data, such as: content of the accessed web page, content of the accessed link, or hints information, and the like.
Optionally, the destination address corresponds to one or more of: the data network, the other terminal device, the network device where the other terminal device is located, the local application of the first network device, or the second network device.
The network device where the other terminal device is located means a network device in communication connection with the terminal device, or a network device controlling the terminal device.
That is, the first network device may route upstream data to one or more of: the data network, the other terminal device, the network device where the other terminal device is located, the local application of the first network device, or the second network device.
If the first network device is not directly connected to the data network, the first network device routing function module may route the uplink data to the second network device or another network device (i.e., the network device where the other terminal device is located) in a routing manner, and then the second network device or another network device routes the uplink 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 may specifically refer to the description of the above embodiment, which is not described herein again. The following takes the second network device as an example for illustration.
It should be understood that the above embodiments are exemplified by taking the uplink data as the IP data, and the embodiments of the present application are not limited thereto. For example, the upstream data may also be ethernet data. When the uplink data is ethernet data, the first network device (i.e. 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 upstream data directly to the destination address, or the first network device may route the upstream data to the destination address through the second network device or other network devices.
Alternatively, the destination address of the upstream data, e.g. data of IP traffic or data of ethernet traffic, 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 the data to the first network device where the other terminal device is 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 is implemented with a Programmable Logic Control (PLC) application, or the PLC is deployed together with the first network device, and at this time, the first network device may directly route to the PLC after receiving the uplink data.
Based on the above technical solution, the first network device may 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 (e.g., other terminal devices under the first network device), the data may be routed to the destination address quickly by the direct routing of the first network device, thereby avoiding the need to send the data to the local application of the first network device or other terminal devices under the first network device through the core network, and thus implementing low-latency transmission between the terminal device and the local application of the first network device or other terminal devices, and supporting ultra-low-latency services.
As shown above, the first network unit (i.e., the first network unit 510 or the network device 700 in the above embodiment or the first network device in fig. 10, which may specifically refer to the above embodiment and is not described herein again. This is explained below with reference to fig. 11 and 12.
For ease of understanding, the QoS flow will be briefly described.
QoS flow: the 5G defines the packet handling mechanism over the air interface based on DRB. Data packets served by one DRB have the same packet handling mechanism in the air interface transmission. The base station may establish multiple DRBs with the terminal device to satisfy 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.
Fig. 11 shows a schematic diagram of the QoS framework defined by the 3GPP NR existing protocol.
Illustratively, for downlink transmission: after Service Data Flow (SDF) data of one downlink PDU session reaches the UPF, the UPF performs QoS flow classification on the data using a Traffic Filtering Template (TFT) corresponding to the PDU session, and carries a QoS Flow Indicator (QFI) on a GTP-U encapsulation header that transmits the data to the access network device. After receiving the data, the access network device determines the QoS flow to which the data belongs according to the corresponding QFI, then maps the data to the corresponding DRB on the SDAP layer corresponding to the PDU session according to the pre-configured QoS parameter corresponding to the QoS flow, and delivers the data to the PDCP layer corresponding to the DRB.
That is to say, in the prior art, in the transmission process of the downlink data from the UPF to the base station, the UPF performs mapping from the downlink data to the QoS stream, and performs different scheduling priorities on the downlink data of different QoS streams to implement differential processing, so as to preferentially meet the transmission performance requirement of the high-priority QoS stream.
By the embodiments of the present application, the first network unit can implement a UPF function and a user plane processing function of the base station, in other words, there is no transmission process from the UPF to the base station, so that the mapping from the downlink data to the DRB, that is, the mapping from the downlink data to the QoS stream, can be directly implemented in the first network unit.
In other words, the routing function module in the first network element (e.g. the user plane processing function of the first network element 510) may directly implement mapping of the downlink data to the DRB, and deliver the downlink data to the PDCP layer corresponding to the DRB, so that the SDAP layer is configurable for the PDU session. That is, for a PDU session, the SDAP layer may or may not be configured.
In addition, no matter the PDU session is not configured with the SDAP layer, the architecture provided by the present application may also adopt a QoS reflection (QoS reflection) mechanism similar to the existing 3GPP NR, so as to quickly respond to uplink data and save signaling overhead.
For example, for uplink transmission, in the prior art, after receiving data, an upper layer of a terminal device performs mapping from the uplink data to a QoS flow, and then delivers the data to an SDAP layer (that is, the data needs to be processed by the SDAP layer), and the SDAP layer continues to perform mapping from the QoS flow to a DRB and delivers the uplink data to a PDCP layer corresponding to the DRB. Mapping of uplink data to QoS flows and mapping of QoS flows to DRBs both generally require the network device to send signaling to the terminal device for configuration. Since data arrival is unpredictable, in order to quickly respond to the arrival of uplink data and to save signaling overhead, the 3GPP NR prior protocol agrees with a QoS reflection mechanism, that is, a QoS reflection function is set in the SDAP header of downlink data to open up the uplink data corresponding to the downlink data for the terminal device. That is, a mapping of data corresponding to downlink data to QoS flows and a mapping of QoS flows to DRBs are employed.
In the embodiments of the present application, the QoS reflection mechanism may be used regardless of whether the SDAP layer is configured.
For example, for the PDU session, in case that the SDAP layer is not configured, whether to turn on the QoS reflection function can be confirmed by an indication of the PDCP layer.
In one possible implementation, the QoS reflective indication information may be carried in a PDCP header. For example, the first network unit turns on by setting the QoS reflection function in the PDCP header, thereby instructing the terminal device to adopt mapping of data corresponding to the downlink data to the DRB for uplink data corresponding to the downlink data. In this case, the uplink typically only needs to complete the mapping of "uplink data to DRB".
Illustratively, if it is IP traffic, the "correspondence" may be determined by exchanging the source and destination addresses, other fields contents in the TCP/UDP and IP headers.
Illustratively, if it is ethernet traffic, the "correspondence" can be confirmed by exchanging the source and destination addresses in the ethernet header, and the other fields having the same content.
Alternatively, the QoS reflection indication information may be indicated by 1 bit (bit) in the PDCP header, or the QoS reflection indication information may be indicated by a reserved (reserve) field in the PDCP header.
This is exemplified below with reference to fig. 12.
As shown, the PDCP PDU format includes 12-bit PDCP Sequence Number (SN).
For example, whether the QoS reflection function is turned on may be indicated by any one R field of three reserved fields in the first byte. For example, when R is 0, it indicates that the QoS reflection function is not turned on; when R is 1, it indicates that the QoS reflection function is turned on.
Based on the technical scheme, the time delay generated by data transmission between the UPF and the base station can be avoided, and the SDAP layer is cancelled, so that the data processing of the SDAP is reduced, the data transmission time delay is further reduced, and the ultra-low time delay transmission is realized. In addition, when the SDAP layer is cancelled, the PDCP layer can indicate whether the QoS reflection function is opened or not to realize the QoS reflection function, so that the signaling overhead is reduced.
The various embodiments described herein may be implemented as stand-alone solutions or combined in accordance with inherent logic and are intended to fall within the scope of the present application.
The communication system and the network device provided in the embodiment of the present application are described in detail above with reference to fig. 5 to 12. Hereinafter, a communication device according to an embodiment of the present application will be described in detail with reference to fig. 13 to 15.
Fig. 13 is a schematic block diagram of a communication apparatus 1300 according to 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 may communicate with the outside, and the processing unit 1320 may perform data processing. The communication unit 1310 may also be referred to as a communication interface or a transceiving unit.
In one possible design, the apparatus 1300 may implement the steps or processes performed by the first network unit 510 (e.g., LTU) corresponding to the above embodiments, for example, the network device 700, or a chip or circuit configured in the network device 700. At this point, the apparatus 1300 may be referred to as a network device. The communication unit 1310 is configured to perform transceiving related operations on the first network unit 510 (e.g., LTU) side in the above embodiments, and the processing unit 1320 is configured to perform processing related operations of the first network unit 510 (e.g., LTU) in the above embodiments.
In a possible implementation manner, the apparatus 1300 may implement steps or flows corresponding to those performed by the first network device in the method 900 or 1000 according to the embodiment of the present application, and the apparatus 1300 may include a unit for performing the method performed by the first network device in the method 900 in fig. 9 or the method 1000 in fig. 10. Also, the units and other operations and/or functions described above in the apparatus 1300 are respectively for implementing the corresponding flows of the method 900 in fig. 9 or the method 1000 in fig. 10.
It should be understood that the specific processes of the units for executing the corresponding steps are described in detail in the above embodiments, and therefore, for brevity, are not described herein again.
In yet another possible design, the apparatus 1300 may implement the steps or the flow executed by the second network unit 520 (e.g., RCU) corresponding to the above embodiments, for example, it may be the network device 800, or a chip or a circuit configured in the network device 800. At this point, the apparatus 1300 may be referred to as a network device. The communication unit 1310 is configured to perform transceiving related operations on the side of the second network unit 520 (e.g., RCU) in the above embodiments, and the processing unit 1320 is configured to perform processing related operations of the second network unit 520 (e.g., RCU) in the above embodiments.
In a possible implementation manner, the apparatus 1300 may implement steps or flows corresponding to those executed by the second network device in the method 900 or 1000 according to the embodiment of the present application, and the apparatus 1300 may include a unit for executing the method executed by the second network device in the method 900 in fig. 9 or the method 1000 in fig. 10. Also, the units and other operations and/or functions described above in the apparatus 1300 are respectively for implementing the corresponding flows of the method 900 in fig. 9 or the method 1000 in fig. 10.
It should be understood that the specific processes of the units for executing the corresponding steps are described in detail in the above embodiments, and therefore, for brevity, are not described herein again.
Fig. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present disclosure. The apparatus may implement the functionality of the first network unit 510 (e.g., 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 comprises:
a memory 1410 for storing programs;
a communication interface 1420 for communicating with other devices;
a processor 1430 for executing programs in memory 1410 that, when 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 a user plane processing function corresponding to UPF, or,
the processor 1420 is configured to configure one or more of: SpCellConfig, SCellConfig, RLC-config, MAC-cellGroupConfig, or PhysicalcellCellGroupConfig.
Fig. 15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present application. The apparatus may implement the functionality of the second network element 520 (e.g., 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 a program;
a communication interface 1520 for communicating with other devices;
a processor 1530 that executes programs in memory 1510 that, when executed,
the processor 1520 is to configure: a radio resource management, RRM, measurement configuration and/or a radio bearer configuration; and/or the presence of a gas in the gas,
the processor 1520 is configured to implement: one or more of the following functions: AMF, SMF, PCF, or AUSF.
Alternatively, the communication interface (1420, 1520) may be a receiver or a transmitter, or may be a transceiver.
In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.
It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being 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 further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of any of the embodiments shown in methods 900 and 1000.
According to the method provided by the embodiment of the present application, a computer-readable medium is further provided, which stores program code, and when the program code runs on a computer, the computer is caused to execute the method of any one of the embodiments shown in the method 900 and the method 1000.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on 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 can be a component. One or more components can 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. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (18)

1. A communication system, comprising: a first network element and a second network element,
the first network element and the second network element communicate via a communication interface, wherein,
the first network element is configured to implement: a user plane processing function corresponding to the layer 1, a user plane processing function corresponding to the layer 2, and a user plane processing function corresponding to the user plane function UPF;
the second network element is configured to implement: a first radio resource control, RRC, function and a core network function;
wherein the core network functions include one or more of: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF,
the first RRC function includes: configuration: radio resource management RRM measurement configuration and/or radio bearer configuration.
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:
configuring one or more of:
the special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
3. The communication system of claim 2,
the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration;
the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
4. A communication system according to claim 2 or 3, wherein said cell or BWP related configuration comprises configuring one or more of the following parameters: center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.
5. A communication system, comprising: a first network element and a second network element,
the first network element and the second network element communicating over a communication interface, the second network element being configured to implement a first radio resource control, RRC, function, the first network element being configured to implement a second RRC function,
wherein the first RRC function comprises:
configuration: a radio resource management, RRM, measurement configuration and/or a radio bearer configuration;
the second RRC function includes:
configuring one or more of: the special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
6. The communication system of claim 5,
the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration;
the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
7. The communication system of claim 6,
the cell or BWP related configuration comprises configuring one or more of the following parameters:
center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.
8. The communication system according to any one of claims 1 to 3, 5 to 7,
the first network unit is further configured to implement mapping of downlink data to a data radio bearer DRB.
9. The communication system according to any one of claims 1 to 3, 5 to 7,
the second network unit is further configured to implement a network capability opening function and/or a network data analysis function.
10. The communication system according to any one of claims 1 to 3, 5 to 7,
the layer 1 comprises: a physical layer (PHY); and/or the presence of a gas in the gas,
the layer 2 comprises 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 access control layer MAC layer.
11. The communication system according to any one of claims 1 to 3, 5 to 7,
the first network unit is a local transmission unit LTU and the second network unit is a remote control unit RCU.
12. A network device, comprising: a processor and a communication interface, wherein the processor is connected with the communication interface,
the processor is configured to implement: a function corresponding to a service data adaptation protocol SDAP, a function corresponding to a packet data convergence protocol PDCP, a function corresponding to a radio link layer control protocol RLC, a function corresponding to a media access control layer MAC, a function corresponding to a physical layer PHY, and a user plane processing function corresponding to a user plane function UPF;
the communication interface is used for communicating with a target device.
13. The network device of claim 12, wherein the processor is further configured to implement a second Radio Resource Control (RRC) function, and wherein
The second RRC function includes:
configuring one or more of: the special cell configuration SpCellConfig, the auxiliary cell configuration SCellConfig, the radio link control configuration RLC-config, the media access control layer cell group configuration MAC-cellGroupConfig, or the physical layer cell group configuration PhysicalcellGroupConfig.
14. The network device of claim 13,
the SpCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration;
the SCellConfig includes one or more of: a cell or bandwidth part BWP related configuration, a channel state indication CSI measurement configuration, a cross-carrier scheduling configuration, or a rate matching configuration.
15. The network device of claim 14,
the cell or BWP related configuration comprises configuring one or more of the following parameters:
center frequency, bandwidth, waveform, subcarrier bandwidth, frame structure, synchronization signal block, or physical channel.
16. The network device of any of claims 12 to 15,
the processor is further configured to implement: mapping of downlink data to data radio bearers DRBs.
17. A network device, comprising: a processor and a communication interface, wherein the processor is connected with the communication interface,
the processor is configured to implement: a first radio resource control, RRC, function and a core network function, the core network function comprising one or more of: an access and mobility management function AMF, a session management function SMF, a policy control function PCF, or an authentication service function AUSF;
the communication interface is used for communicating with a target device;
wherein the first RRC function comprises:
configuration: radio resource management RRM measurement configuration and/or radio bearer configuration.
18. The network device of claim 17,
the processor is also used for realizing the functions related to network capability opening and network data analysis.
CN201910360430.7A 2019-04-30 2019-04-30 Communication system and network equipment Active CN111866908B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910360430.7A CN111866908B (en) 2019-04-30 2019-04-30 Communication system and network equipment
PCT/CN2020/083516 WO2020220943A1 (en) 2019-04-30 2020-04-07 Communication system and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910360430.7A CN111866908B (en) 2019-04-30 2019-04-30 Communication system and network equipment

Publications (2)

Publication Number Publication Date
CN111866908A CN111866908A (en) 2020-10-30
CN111866908B true CN111866908B (en) 2021-12-14

Family

ID=72965700

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910360430.7A Active CN111866908B (en) 2019-04-30 2019-04-30 Communication system and network equipment

Country Status (2)

Country Link
CN (1) CN111866908B (en)
WO (1) WO2020220943A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220074872A (en) * 2019-09-26 2022-06-03 지티이 코포레이션 Service-based access network architecture and communication
CN113422694A (en) * 2021-06-08 2021-09-21 腾讯科技（深圳）有限公司 Communication method, communication apparatus, communication medium, and electronic device
CN114143229B (en) * 2021-12-01 2023-04-07 中国联合网络通信集团有限公司 Communication method, device, equipment and storage medium
CN116801263A (en) * 2022-03-18 2023-09-22 中兴通讯股份有限公司 Network node, method and storage medium
CN114466332A (en) * 2022-04-07 2022-05-10 阿里巴巴达摩院(杭州)科技有限公司 Data communication system and method, and live data transmission method, device and equipment

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1996913A (en) * 2005-12-31 2007-07-11 华为技术有限公司 A network interconnection system and method for separated control and load
EP2850748A1 (en) * 2012-05-14 2015-03-25 Samsung Electronics Co., Ltd. Method and apparatus for processing state information in communication system
CN108400997A (en) * 2017-02-06 2018-08-14 电信科学技术研究院 Conversation managing method, terminal, management function entity and access network node
CN108650125A (en) * 2018-05-09 2018-10-12 清华大学 A kind of core network system based on non-stack agreement towards B5G
CN108738138A (en) * 2017-04-17 2018-11-02 上海诺基亚贝尔股份有限公司 Method for wireless communications, the network equipment and terminal device
CN109121162A (en) * 2017-06-26 2019-01-01 中国移动通信有限公司研究院 A kind of processing method of cell information, the network equipment and terminal
CN109246850A (en) * 2017-05-05 2019-01-18 华为技术有限公司 Wireless connection control method, distributed unit, centralized unit and base station system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132548B (en) * 2006-08-22 2011-08-03 上海贝尔阿尔卡特股份有限公司 Wireless resource dynamic assignment system and method aiming at MBMS business
ES2820853T3 (en) * 2016-08-12 2021-04-22 Ericsson Telefon Ab L M Two-level MRS configuration
CN108738038B (en) * 2017-04-18 2023-03-24 中兴通讯股份有限公司 Message processing method and device and first radio access network equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1996913A (en) * 2005-12-31 2007-07-11 华为技术有限公司 A network interconnection system and method for separated control and load
EP2850748A1 (en) * 2012-05-14 2015-03-25 Samsung Electronics Co., Ltd. Method and apparatus for processing state information in communication system
CN108400997A (en) * 2017-02-06 2018-08-14 电信科学技术研究院 Conversation managing method, terminal, management function entity and access network node
CN108738138A (en) * 2017-04-17 2018-11-02 上海诺基亚贝尔股份有限公司 Method for wireless communications, the network equipment and terminal device
CN109246850A (en) * 2017-05-05 2019-01-18 华为技术有限公司 Wireless connection control method, distributed unit, centralized unit and base station system
CN109121162A (en) * 2017-06-26 2019-01-01 中国移动通信有限公司研究院 A kind of processing method of cell information, the network equipment and terminal
CN108650125A (en) * 2018-05-09 2018-10-12 清华大学 A kind of core network system based on non-stack agreement towards B5G

Also Published As

Publication number Publication date
WO2020220943A1 (en) 2020-11-05
CN111866908A (en) 2020-10-30

Similar Documents

Publication Publication Date Title
US10972956B2 (en) Enhanced handling on QoS flow description
US10462700B2 (en) Method for performing reflective quality of service (QOS) in wireless communication system and a device therefor
US10966222B2 (en) Method, device, and system for processing reflective QoS characteristics
US11229067B2 (en) Relay communication method and relay communications apparatus and system
CN111866908B (en) Communication system and network equipment
CN110249597B (en) Communication processing method and device
US11350305B2 (en) Method and apparatus for processing data in wireless communication system
US11115855B2 (en) Method for transmitting UL packet based on quality of service (QoS) flow in wireless communication system and a device therefor
US9883441B2 (en) Method and apparatus to route packet flows over two transport radios
EP3048845B1 (en) Device and method for data transmission
EP3603168B1 (en) Method for transmitting lossless data packet based on quality of service (qos) framework in wireless communication system and a device therefor
US11019527B2 (en) Method for transmitting TCP ACK packet in wireless communication system and a device therefor
RU2767778C2 (en) Method and device for protecting data integrity
CN111148163B (en) Communication method and device
EP3836598B1 (en) Data transmission apparatuses and system
JP7378569B2 (en) Lossless transmission for Unaware Response Mode (UM) data radio bearer (DRB)
KR20200018577A (en) Terminal device, base station device, communication method, and integrated circuit
CN113873582B (en) Mobile edge calculation processing method and related equipment
US10455472B2 (en) Device and method of handling data transmissions in a wireless communication system
CN112690037A (en) Terminal device, base station device, and method
CN115150910A (en) Communication method and communication device
KR20200117356A (en) Method and apparatus for transmitting signal based on quality of service in mobile communication network

Legal Events

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