6G network system based on protocol component displacement migration and bypass

Abstract

The invention provides a 6G network system based on protocol component displacement migration and bypass, which comprises a core network, an access network and a terminal, the core network, the access network and the terminal are all provided with protocol stacks for communication, each protocol stack comprises a plurality of protocol layers, each protocol layer is composed of a plurality of network function components, and the network function components are connected with the core network. Wherein at least part of the network function components are set as bit replacement units, and the bit replacement units interact with the network function components of other protocol layers to realize function equivalent replacement across the protocol layers; the system further comprises an arrangement center which is an entity used for managing and controlling arrangement and dynamic scheduling of the network function components in a centralized mode, and the arrangement center receives registration information of the network function components and formulates an arrangement scheme of the function components based on service types, service chains and / or QoS (Quality of Service) requirements. And the core network and the access network formulate an arrangement scheme and then notify the terminal to cooperatively execute the operation of functional component replacement, vertical migration or protocol bypass.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and in particular relates to a 6G network system based on protocol component replacement migration and bypass. Background Art

[0002] With the development of 6G networks, future wireless communication systems need to support higher data rates, lower latency, higher reliability, and larger-scale terminal connections to meet the needs of diverse application scenarios such as immersive communications, ultra-reliable low-latency communications (URLLC), large-scale Internet of Things (IoT), smart cities, and industrial automation. To this end, the network architecture must have greater elasticity, flexibility, and scalability to adapt to changing business needs and network environments.

[0003] Although the existing 5G network has introduced technologies such as network slicing, software-defined networking (SDN), and network function virtualization (NFV), which have improved the flexibility and resource utilization of the network, there are still many limitations in practical applications. For example, the slice management and resource scheduling of 5G networks are complex, making it difficult to achieve dynamic adaptation to diversified business scenarios; the protocol stack structure is relatively fixed, making it difficult to flexibly adjust the protocol processing flow according to business needs, resulting in difficulty in further optimizing network latency and energy efficiency; the network's self-healing ability is limited, and it is difficult to ensure the continuous operation of key businesses in the face of large-scale failures or extreme scenarios. In addition, the existing network architecture also has deficiencies in supporting multi-domain collaboration, intelligent orchestration, and automated operation and maintenance, making it difficult to meet the higher requirements of future 6G networks for intelligence, automation, and ubiquitous connectivity. Summary of the invention

[0004] In order to overcome the above problems, the present invention proposes a 6G network system based on protocol component substitution migration and bypass, including a core network side and an access network side, wherein both the core network side and the access network side are provided with a protocol stack for communication, wherein the protocol stack comprises a plurality of protocol layers, each of which is composed of a plurality of network function components, and the network function components are used to implement the basic communication functions of the protocol layers to which they belong, wherein at least some of the network function components are configured as substitution units, and the substitution units interact with the network function components of other protocol layers through standardized interfaces to implement functional equivalent replacement across protocol layers;

[0005] The system also includes an orchestration center, which is an entity used to centrally manage and control the orchestration and dynamic scheduling of network functional components. The orchestration center receives information about each network functional component and dynamically performs functional component replacement, vertical migration or protocol bypass operations based on business type, service chain and / or QoS (quality of service) requirements.

[0006] Furthermore, the system is a distributed, centralized or hybrid component orchestration architecture, wherein:

[0007] Distributed architecture: The orchestration center consists of several orchestration nodes distributed on the core network side and the access network side. Each of the several orchestration nodes has a certain degree of autonomous decision-making and management capabilities, and can control and schedule local network resources and functional components. The orchestration nodes cooperate with each other to achieve the overall network function component orchestration task;

[0008] Centralized architecture: The orchestration center is set on the core network side to centrally manage all functional components in the network. The network function components in the network need to report information to the orchestration center and at the same time receive instructions and configurations issued by the orchestration center, so as to achieve unified orchestration, scheduling and decision-making of component orchestration;

[0009] Hybrid architecture: That is, a centralized orchestration center is set up, and several orchestration nodes are also set up in each network autonomous domain. The centralized orchestration center is responsible for global network component planning, policy formulation and macro allocation of resources. The distributed orchestration nodes are responsible for the orchestration, real-time scheduling and data processing of network function components within the autonomous domain. The two cooperate to achieve the component orchestration management of the entire network.

[0010] Furthermore, the component orchestration management process is as follows:

[0011] The network function component registers with its affiliated orchestration center or orchestration node. The orchestration center or orchestration node performs component orchestration management based on the ID of each network function component;

[0012] When the UE accesses the network and registers, it reports its component capability information, that is, the component IDs of each layer of the UE, to the network (orchestration center or orchestration node) as the access side;

[0013] The orchestration center and / or the orchestration node negotiate an orchestration plan according to the service requirements or UE type in combination with the UE component capability information. The orchestration plan at least includes the composition of the network function component set and the activation / effective time of the orchestration;

[0014] After the component orchestration is triggered, the orchestration center and / or the orchestration node execute the component orchestration on the core network side and cooperate with the relevant protocol layers to execute the component orchestration on the core network side.

[0015] The relevant protocol layer notifies the UE of the network side component orchestration plan through RRC signaling or MAC CE, so that both parties can activate a new component combination at a common time to support specific services.

[0016] Furthermore, the function component replacement operation is to temporarily replace the components with similar and equivalent functions between different protocol layers, so that the function of at least one protocol layer is realized by the substitution unit of another protocol layer.

[0017] Furthermore, according to the real-time service scenario, the vertical migration operation migrates the high-layer protocol function components to the low-layer protocol layer, and the substitution unit at the low layer implements the aforementioned high-layer functions to support the sinking of protocol functions.

[0018] Furthermore, according to the service requirements, the protocol bypass operation performs bypass processing on one or more protocol layers in the protocol stack, and the substitution unit of the adjacent protocol layer takes over the required functions to optimize the protocol processing flow and reduce latency.

[0019] Advantages of the present invention:

[0020] The 6G network architecture provided by the present invention can be flexibly adjusted and expanded according to different service requirements and scenarios through elastic design. Based on the component-based / modular design of network functions, the network can quickly adapt to new technologies and services to meet diverse user needs.

[0021] The elastic migration design proposed by the present invention allows the network to optimize resource utilization according to real-time service requirements and network conditions. For example, through flexible service offloading and local endogenous computing power, the network can quickly process sensing data, reduce dependence on the central data center, and improve resource utilization efficiency.

[0022] The elastic architecture proposed by the present invention can support multiple service types, including high rate, low latency, and a large number of device connections. Through service-oriented components and open protocols, this architecture enables the network to better adapt to different types of device and service requirements.

[0023] The 6G network architecture design proposed by the present invention takes into account compatibility with existing networks, supports smooth evolution from 5G to 6G, and reduces interference and impact on existing networks.

[0024] The 6G network architecture introduces AI and digital twin technologies. Through the component substitution migration and bypass mechanism proposed by the present invention, it is easier to achieve network self-configuration, self-recovery, self-optimization, and self-operation, reducing the difficulty and cost of operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0026] Figure 1 For the 6G componentized network architecture model

[0027] Figure 2For the 6G network and component orchestration and slice scheduling architecture

[0028] Figure 3 For the distributed / hybrid architecture component orchestration process

[0029] Figure 4 For the centralized network component orchestration process

[0030] Figure 5 For the control plane component orchestration application example

[0031] Figure 6 For the user plane component orchestration application example

[0032] Figure 7 For the component replacement operation process and interface

[0033] Figure 8 For the 6G bypassable user plane protocol stack architecture - UL bypass processing

[0034] Figure 9 For the 6G bypassable user plane protocol stack architecture - UL bypass processing

[0035] Figure 10 For the process example of user plane protocol layer bypass

[0036] Figure 11 For the DL MAC PDU example

[0037] Figure 12 For the UL MAC PDU example

[0038] Figure 13 For the component vertical migration process example Specific implementation manners

[0039] The present application will be described below in conjunction with specific embodiments:

[0040] Embodiment 1:

[0041] A 6G network system based on protocol component replacement migration and bypass provided by the present invention is a component-based network system, including an access network protocol layer and a core network protocol layer, as well as a function entity and a network management entity for semi-static and dynamic real-time orchestration and scheduling of components. Its structural model is as Figure 1 shown, and its overall architecture in the 6G network is as Figure 2 shown.

[0042] The component orchestration and slice scheduling entity is responsible for real-time dynamic component orchestration and real-time resource optimization scheduling of the slice model based on factors such as business QoS requirements or terminal device types, so as to ensure the network's elasticity and scalability and dynamically adapt to the changing needs of the business. The 6G network adopts a two-dimensional elastic processing mechanism of network function component orchestration + resource slice scheduling. Among them, the resource slice is the management unit of the network resource set dynamically allocated to ensure the specific services of the UE. The network resource set includes core network resources, access network resources, etc., mainly covering computing, storage, spectrum, etc. Slice management needs to uniformly manage and coordinately schedule multi-dimensional resources such as computing, storage, spectrum / bandwidth, etc. based on the complexity of multi-dimensional resource management. These resources are interrelated and affected by various factors. For example, spectrum resources are affected by geographical environment, user density, etc. At the same time, the slice needs to be dynamically managed and adjusted in real time, that is, it changes from slice management to slice scheduling: as the business changes, it is necessary to monitor the slice status in real time and dynamically adjust the resource scheduling and allocation. The specific operations and settings of the resource slice are the same as those of the prior art and will not be elaborated in this embodiment.

[0043] Component orchestration relies on the network system provided in this embodiment. Through network function components as the basic composition units of the protocol layer, during the network service process, they can be instantiated as needed to become component instances to provide protocol processing services for different UEs. The component orchestration entity (i.e., the orchestration center) performs real-time orchestration of network function components according to different UE types, different business QoS, and changes in business service quality during orchestration. Specifically:

[0044] (1) Dynamic orchestration of functional components based on business requirements

[0045] Identify business requirements: First, identify the UE business type, and distinguish whether the UE is of the eMBB, URLLC, or mMTC business type. eMBB type UEs have high bandwidth requirements, such as high-definition video playback terminals; URLLC type UEs have strict latency requirements, such as autonomous driving vehicles; mMTC type UEs have frequent signaling interactions but small single data volumes, such as Internet of Things sensors.

[0046] Dynamic orchestration of functional components: Based on the business requirements of the UE, dynamically allocate network function component resources. For eMBB type UEs, a complete protocol stack layer and the functional components it contains can be equipped. For URLLC type UEs, mechanisms such as protocol layer bypass need to be adopted to reduce unnecessary protocol layer processing and ensure low-latency communication.

[0047] (2) Orchestration based on the service chain

[0048] Create service chains: According to the QoS requirements of different services, create corresponding service chains, and connect network function components in a specific order. For example, for an eMBB service that requires security protection, a service chain can be created that includes network function components such as firewalls, intrusion detection systems, and cache servers to ensure the security and efficiency of data transmission.

[0049] Flexibly adjust service chains: When the QoS requirements or service quality of a service change, flexibly adjust the service chain. If the business's requirement for security decreases, the intrusion detection system component can be temporarily removed from the service chain to reduce the latency of data transmission; if the complexity of data processing in the business increases, corresponding processing function components can be added to the service chain, such as adding data encryption components.

[0050] Optimize the performance of service chains: Optimize the overall performance of service chains, including reducing the data transmission latency between network function components in the service chain and improving the processing efficiency of components. For example, by optimizing the deployment locations of components in the service chain, the data transmission path between them can be made shorter.

[0051] (3) Intelligent Orchestration Based on QoS Awareness

[0052] Obtain and analyze QoS parameters: Obtain QoS parameters of different services, such as maximum bit rate (MBR), guaranteed bit rate (GBR), allocation and retention priority (ARP), etc., and analyze these parameters to determine the QoS requirements and priorities of the services. For example, video call services usually require higher bandwidth and lower latency, and their GBR and ARP values are relatively high; while file download services focus more on transmission speed and have relatively lower requirements for latency, and their MBR values are high.

[0053] Make decisions with intelligent algorithms: Use intelligent algorithms, such as machine learning algorithms, deep reinforcement learning algorithms, or large AI models, to perform dynamic intelligent orchestration of network function components according to the QoS parameters of services and the real-time network status. These algorithms can learn the historical data of the network and business traffic patterns, predict the future state of the network and the demand changes of services, and thus allocate resources and adjust network function components in advance. For example, by analyzing historical data, it is predicted that the traffic of video call services will increase significantly during a certain period, and more resources are allocated to relevant network function components in advance to meet the QoS requirements of the services.

[0054] Real-time feedback and adjustment: Establish a real-time feedback mechanism, and evaluate and adjust the orchestration results of network function components according to the real-time QoS metrics and service quality feedback of services. If it is found that the QoS metrics of a service do not meet the expected requirements, timely adjust the resource allocation, location, or configuration of network function components to optimize service quality.

[0055] 4) Orchestration Based on Automation and Closed-Loop Management

[0056] Automated Configuration and Deployment: Achieve the automated configuration and deployment of network function components. According to predefined policies and business requirements, automatically complete the creation, activation, or destruction of network function components.

[0057] Real-Time Monitoring and Fault Recovery: Monitor the running status and service quality of network function components in real time. When a fault or anomaly occurs, automatically perform fault recovery and resource adjustment. For example, when a network function component fails, automatically start the backup component and reallocate the service traffic to ensure business continuity and service quality.

[0058] Closed-Loop Optimization and Adjustment: Establish a closed-loop optimization and adjustment mechanism. Based on the network performance metrics and business service quality feedback, continuously optimize the orchestration strategy and resource configuration of network function components. Through continuous monitoring, evaluation, and adjustment, achieve the adaptive optimization and performance improvement of the network.

[0059] 5) Orchestration Based on Multi-Domain Collaboration

[0060] Cross-Domain Resource Collaborative Management: In a multi-domain network environment, establish a unified resource management platform to achieve the collaborative management and orchestration of network function component resources in different domains. The 6G network architecture includes terrestrial networks and various non-terrestrial networks, such as satellite networks, drone networks, etc. It is necessary to achieve cross-domain collaborative orchestration to ensure seamless connection between different networks and efficient utilization of resources, and provide users with convenient network services.

[0061] Example 2:

[0062] The implementation of component orchestration relies on the deployment mode of the component center and component architecture in the network system. The network system provided in this example is divided into distributed, centralized, or hybrid component orchestration architectures.

[0063] The orchestration center of the distributed architecture consists of several orchestration nodes distributed on the core network side and the access network side. Each orchestration node has a certain degree of autonomous decision-making and management capabilities, and can control and schedule local network resources and function components. Each orchestration node collaborates to complete the overall network function component orchestration task.

[0064] The orchestration center of the centralized architecture is set on the core network side, centrally managing all function components in the network. The network function components in the network need to report information to the orchestration center and receive instructions and configurations issued by the orchestration center, so as to achieve unified orchestration, scheduling, and decision-making of component orchestration.

[0065] The hybrid architecture sets up a centralized orchestration center and also sets up several orchestration nodes in each network autonomous domain. The centralized orchestration center is responsible for global network component planning, policy formulation, and macro-allocation of resources. The distributed orchestration nodes are responsible for the orchestration, real-time scheduling, and data processing of network function components within the autonomous domain. The two cooperate to achieve the orchestration and management of components throughout the network.

[0066] For the orchestration and management processes of different architectures, such as Figure 3 As shown, this embodiment provides a distributed / hybrid network component orchestration process:

[0067] S1. Inside the 6G network, each functional component needs to register with the component orchestration function entity, and the component orchestration function entity performs component orchestration management based on the IDs of each component.

[0068] S2. When the UE accesses the network and registers, it reports its component capability information to the network, that is, the component IDs of each layer of the UE. Here, the understanding of functional components by the network and the UE is unified, that is, through a standardized method, the component ID can achieve an unambiguous understanding of the component by both parties.

[0069] S3. After the UE accesses the network, the 6GC component orchestration function entity (6GC Orchestrator) and the RAN component orchestration function entity (RAN Orchestrator) on the network side negotiate the orchestration plan based on factors such as service requirements or UE type, combined with the UE component capability information. The orchestration plan at least includes: the composition of the component set, the activation / effective time of the orchestration, etc.

[0070] S4. After the component orchestration is triggered, 6GC Orchestrator cooperates with the 6GC protocol function entity (6GC Function) to execute the component orchestration on the core network side.

[0071] S5. After the component orchestration is triggered, RAN Orchestrator cooperates with the RAN protocol layer to execute the component orchestration on the access network side.

[0072] S6. The component orchestration plan on the network side needs to be notified to the UE through RRC signaling or MAC CE so that both parties can activate a new component combination at a common time to support specific services. The information carried includes the component combination Index and the associated DRB ID, etc.

[0073] For the hybrid architecture, after the orchestration sub-center realizes the component orchestration within the access network it manages, it notifies the orchestration center on the network side, and then the orchestration center organizes and coordinates to realize the interaction between the network side and the access network side.

[0074] For the centralized component orchestration architecture, such as Figure 4As shown in the figure, steps such as component registration, resource preparation, and component orchestration notification are all uniformly managed by the 6GC component orchestration function entity (6GC Orchestrator) on the network side, so as to achieve vertical migration of components or protocol layer bypass.

[0075] Embodiment 3:

[0076] The component orchestration process is based on the collaborative work of network function components between different protocol layers. In this process, there are cases where a network function component in the original protocol layer is replaced by a network function component in another protocol layer. The units between such upper and lower protocol layers that have approximately equivalent functions and can replace and interact with each other are substitution units. Substitution units can interact with network function components in other protocol layers through standardized interfaces, and can perform temporary unit replacement operations according to the needs of service slices, and perform real-time component combination to meet the QoS requirements of service slices. As Figure 5 and 6 shown in the figure, in the control plane and user plane, when the service slice requires it, the green unit can migrate its processing from the core network / NAS layer to the RAN layer for processing, and then omit other function processing processes in the core network / NAS layer to simplify the network processing flow or achieve goals such as improving energy efficiency. For the blue unit, the RLC layer is entirely replaced, playing the role of protocol layer bypass to achieve purposes such as reducing communication latency.

[0077] Specifically, the component substitution operation process is as Figure 7 shown in the figure. Component substitution orchestration can be initiated by the core network / access network, or the UE can initiate component orchestration suggestions or requests to the orchestration center according to changes in service QoS. The final orchestration plan is determined by the decision of the orchestration center.

[0078] In the combination of network function components, there are default conventional configurations, and other combinations outside the conventional combination configurations are customized combination configurations, that is, configurations orchestrated according to needs.

[0079] After the orchestration center formulates and issues the orchestration plan, each protocol layer and the UE start and disable corresponding components according to the orchestration plan, and construct new component combinations (distinguished based on the combination Index). It should be noted that in the combination of network function components, there are missing conventional configurations, and other combinations outside the conventional combination configurations are customized combination configurations, that is, configurations orchestrated according to needs. The interaction between components between different protocol layers is processed in a standardized interface manner, and the interaction between components within the same protocol layer is not standardized.

[0080] According to the component customization combination scheme, the radio interface PDU data packets transmitted between the network side and the UE side carry relevant information such as component IDs or component combination indexes. There are two ways to carry this information: 1) Each protocol layer component indicates the target component ID to be passed in its component's PDU header. 2) The component combination index of the receiving side is indicated in the PDU header of the MAC layer. Based on this index, the receiving party determines the component IDs associated with each layer.

[0081] When the network function component performs substitution migration or bypass, it can distinguish and process according to each service of the UE, or perform a unified component substitution operation with the UE as a unit.

[0082] Embodiment 4:

[0083] This embodiment provides an adaptive bypass method implemented by the network system disclosed in Embodiments 1-3. The scenario adaptability of the protocol stack system adopted in this method changes, that is, a variable protocol stack structure. Some protocol layers can be bypassed. For example, the RAN RLC layer bypass technology can bypass multiple protocol layers simultaneously according to service types and QoS requirements, dynamically streamline the protocol stack levels, reduce the network end-to-end delay, and meet the industrial ultra-real-time control requirements. Through the dynamic perception of service types, the network protocol system adaptively adjusts or negotiates and adjusts between the network and the terminal.

[0084] Figure 8 and Figure 9 respectively show the downlink and uplink processing examples of the 6G bypassable user plane protocol stack architecture provided by the present invention. According to the UE's service QoS requirements, the high-level protocol layer can bypass the low-level protocol layer. For example, PDCP can bypass RLC and directly connect to the MAC layer through its internal logical channel Logical Channel component. At the same time, some necessary function processing of the RLC layer can be substituted by substitution components in the upper layer (PDCP) or the lower layer (MAC), so as to achieve complete or partial bypass of RLC. Similarly, PDCP can bypass RLC and MAC and directly connect to the PHY physical layer through the transport channel Transport Channel component. If some necessary function processing of the RLC layer and MAC can be substituted by substitution components in the upper layer (PDCP) or the lower layer (PHY), complete or partial bypass can be achieved. The protocol layers in 6GC can also be bypassed, and several function components in 6GC can be bypassed according to the UE service type or the characteristics of the autonomous domain network.

[0085] This embodiment also gives a process example of bypassing the user plane protocol layer with a distributed architecture, such as Figure 10As shown in the figure, the 6GC component orchestrator and the RAN component orchestrator on the network side negotiate and formulate a bypass solution for the RLC protocol layer according to the QoS Flow requirements, and notify the PDCP layer and the MAC layer of the UE and the RAN. After the bypass is started, the PDCP takes over the logical channel processing, directly interfaces with the MAC data processing, and sends the PDU down to the MAC layer. At this time, the PDU is specially processed, and a MAC header is added to indicate that the data packet needs to bypass the protocol layer, and is sent by the MAC layer to the UE. After receiving the data packet, the UE parses the MAC header and performs the same processing on the uplink PDU, so that the uplink PDU also bypasses the PLC layer and is directly sent to the DPCP layer by the MAC layer.

[0086] In the bypass process example provided in this embodiment, the protocol layer bypass (simplification) triggered by QoS requirements can bypass any network protocol layer or multiple protocol layers as needed. In the case where the RLC is bypassed, the replacement components of the PDCP and the MAC need to take over the necessary functional processing after the RLC is bypassed, such as the data packet segmentation and reassembly functional components.

[0087] The functional replacement between components can refer to Figure 6 , specifically:

[0088] The network function components of the SDAP layer involve functions such as the mapping of QoS flows and radio bearers, data packet marking and processing, user data transmission, etc., and their corresponding several components, and also include service interface adaptation components between protocol layers.

[0089] The network function components of the PDCP layer involve functions such as header compression and decompression, encryption and integrity protection, reordering and data replication transmission, control plane signaling bearer, etc., and their corresponding several components, and also include service interface adaptation components between protocol layers.

[0090] The network function components of the RLC layer involve functions such as data segmentation and reassembly, three data transmission modes, ARQ, RLC PDU packetization / depacketization, etc., and their corresponding several components, and also include service interface adaptation components between protocol layers.

[0091] The network function components of the MAC layer involve functions such as random access control, logical channel and transport channel mapping, scheduling and transmission scheme selection, data multiplexing and demultiplexing, power control, etc., and their corresponding several components, and also include service interface adaptation components between protocol layers.

[0092] In the case where the bypass solution is not triggered, in the user plane process, the protocol layers related to user service processing are sequentially sent through the functional components of each layer of SDAP, PDCP, RLC, MAC, and PHY, and received in the reverse direction.

[0093] In the case where component substitution is triggered, for the user plane process, RLC is bypassed. The protocol layers related to user service processing sequentially pass through the functional components of each layer of SDAP, PDCP, MAC, and PHY for transmission processing and perform reception processing in reverse. Since the RLC layer is bypassed, the PDCP layer substitution unit component needs to assume the logical channel missing due to RLC bypass, that is, the PDCP layer substitution unit has a logical channel as a service interface to dock with the MAC layer substitution unit. The substitution unit of the MAC layer needs to have functions such as packet segmentation / reassembly caused by RLC bypass. The selection of the substitution units in the PDCP and MAC layers in the UE and RAN depends on the component orchestration scheme.

[0094] In the above example, the MAC PDU header indicates the bypassed protocol layer, such as RLC, through the assemblyIndex component to combine the Index field. Moreover, the same MAC PDU can accommodate bypassed PDUs (such as PDCP PDUs) or non-bypassed PDUs (such as RLC PDUs). DL and UL MAC PDU examples are as Figure 11 , 12 shown.

[0095] Example 5:

[0096] This embodiment presents an adaptive vertical migration process for full-stack functional components of the network system based on Embodiments 1-3. For example, Figure 13 it presents the vertical migration process of components in a distributed architecture. During the component substitution migration process, RAN Orchestrator plays a central role in coordinating protocol layers such as RRC and the link layer for component substitution migration processing. RRC uses substitution components to replace the 6GC NAS components and execute the streamlined control plane signaling process. When the 6GC functional components for user plane data transmission vertically migrate downward to the RAN side, 6GC no longer participates in the processing of this user plane process.

[0097] For the interaction between components during vertical migration, reference can be made to Figure 5 . In the figure, some functional components of the NAS layer are replaced by the substitution units in the MAC layer. For example, the authentication function vertically migrates downward and realizes fast authentication synchronously during the random access or RRC connection establishment process. Through component orchestration and substitution operations, authentication preposition is achieved, which can effectively implement illegal interception and reduce signaling overhead.

[0098] The network functional components of the NAS layer involve functions such as access and security management, session management, mobility management, etc., and their corresponding several, and also include service interface adaptation components between protocol layers.

[0099] The network function components of the RRC layer involve functions such as system message broadcasting, connection management, mobility management, radio resource configuration and management, security management, power control, etc., and several corresponding components for each function. Additionally, it includes a service interface adaptation component between protocol layers.

[0100] The network function components of the PDCP layer involve functions such as header compression and decompression, encryption and integrity protection, reordering and data replication transmission, control plane signaling bearer, etc., and several corresponding components for each function. Additionally, it includes a service interface adaptation component between protocol layers.

[0101] The network function components of the RLC layer involve functions such as data segmentation and reassembly, three data transfer modes, ARQ, RLC PDU packetization / depacketization, etc., and several corresponding components for each function. Additionally, it includes a service interface adaptation component between protocol layers.

[0102] The network function components of the MAC layer involve functions such as random access control, logical channel and transport channel mapping, scheduling and transmission scheme selection, data multiplexing and demultiplexing, power control, etc., and several corresponding components for each function. Additionally, it includes a service interface adaptation component between protocol layers.

[0103] In the case where component substitution is not triggered, control plane processes, such as authentication, are initiated and processed by the 6GC and the UE NAS layer. The lower protocol layers sequentially pass through the function components of the RRC, PDCP, RLC, MAC, and PHY layers for transmission processing and reverse for reception processing.

[0104] In the case where component substitution is triggered, control plane processes, such as authentication, are initiated by the RAN and the UE RRC layer and processed in cooperation with the MAC layer. The authentication component of the NAS layer is substituted and migrated downward to the RRC layer and the MAC layer. The orchestration scheme requires the substitution unit of the RRC layer to have the function of constructing equivalent authentication messages due to the substitution of the NAS layer authentication component. The MAC needs to construct MSGA / B based on the messages provided by the RRC substitution unit during the random access process. The selection of the substitution units in the RRC and MAC layers in the UE and the RAN depends on the component orchestration scheme.

Claims

1. A 6G network system based on protocol component substitution migration and bypass, including a core network, an access network, and terminals. The core network, access network, and terminals are all equipped with protocol stacks for communication. The protocol stack includes multiple protocol layers, and is characterized in that: Each protocol layer is composed of several network function components. The network function components are used to implement the basic functions of the protocol layer to which they belong. At least some of the network function components are set as substitution units. The substitution units interact with the network function components of other protocol layers to achieve cross-protocol layer function equivalent substitution; The system also includes an orchestration center, which is an entity for centralized management and control of network function component orchestration and dynamic scheduling. The orchestration center receives the registration information of each network function component, and formulates an orchestration plan for function component substitution, vertical migration, or protocol bypass based on service type, service chain, and / or QoS (Quality of Service) requirements; After formulating the orchestration plan, the core network and the access network notify the terminals to cooperate in performing the operations of function component substitution, vertical migration, or protocol bypass. The operations can be located on all layers of the full stack, including the control plane and the user plane.

2. The 6G network system based on protocol component substitution migration and bypass according to claim 1, characterized in that The system is a distributed, centralized, or hybrid component orchestration architecture, where: Distributed architecture: The orchestration center is composed of multiple orchestration nodes distributed in each network node on the core network side and the access network side. The orchestration nodes orchestrate the network function components of the protocol stack within their respective network nodes, and the orchestration nodes cooperate to achieve the overall network function component orchestration task; Centralized architecture: The orchestration center is set as an independent entity on the core network side, centrally orchestrating all function components in the network. The network function components in the network need to report service requirements and device category information to the orchestration center, and at the same time receive instructions and configurations issued by the orchestration center, so as to achieve unified component orchestration management; Hybrid architecture: Set up an orchestration center on the core network side and an orchestration sub-center on the access network side. The orchestration sub-center centrally orchestrates each network function component within its affiliated access network side. In addition to orchestrating the network function components within the core network side, the orchestration center on the core network side also cooperates with each orchestration sub-center on the access network side to formulate an overall orchestration plan.

3. The 6G network system based on protocol component substitution migration and bypass according to claim 2, characterized in that: In the centralized architecture, the network function components of the access network directly interact with the orchestration center or transit through the network function components on the core network side.

4. The 6G network system based on protocol component substitution migration and bypass according to claim 3, characterized in that, The component orchestration management process is as follows: The network function components register with their affiliated orchestration center or orchestration node. The orchestration center or orchestration node performs component orchestration management based on the IDs of each network function component; When the UE accesses the network and registers, it reports its component capability information and component ID to the orchestration center or orchestration node; The orchestration center and / or the orchestration node negotiate the orchestration plan according to the service requirements or UE type, combined with the UE component capability information. The orchestration plan at least includes the composition of the network function component set and the activation / effective timing of the orchestration; After the component orchestration is triggered, the orchestration center cooperates with the network function components on the core network side to execute the component orchestration on the core network side; The orchestration center cooperates with the orchestration sub-center or the orchestration node cooperates with the network function components on the access network side to execute the component orchestration on the access network side; The access network notifies the UE of the component orchestration scheme via RRC signaling or MAC CE, so that both sides can activate a new component combination at a common time to support specific services.

5. The 6G network system based on protocol component substitution migration and bypass according to claim 1, characterized in that: The functional component replacement operation is to temporarily replace components with approximately equivalent functions between different protocol layers, so that the functions of at least one protocol layer are implemented by the replacement unit of another protocol layer.

6. The 6G network system based on protocol component substitution migration and bypass according to claim 1, characterized in that: The vertical migration operation migrates the functions of the high-layer protocol layer to the low-layer protocol layer according to the real-time service scenario, and the replacement unit of the low layer implements the functions of the high-layer protocol layer to support the sinking of protocol functions.

7. The 6G network system based on protocol component substitution migration and bypass according to claim 1, characterized in that: The protocol bypass operation performs bypass processing on one or more protocol layers in the protocol stack according to service requirements, and the replacement unit of the adjacent protocol layer takes over the required functions to optimize the protocol processing flow and reduce latency.

8. The 6G network system based on protocol component substitution migration and bypass according to claim 1, characterized in that: The network function components and replacement units between different protocol layers interact through standardized interfaces.

9. The 6G network system based on protocol component replacement migration and bypass according to claim 1, characterized in that: After the core network and the access network formulate the orchestration scheme, the access network notifies the terminal of the orchestration scheme via the control plane signaling; the PDU data packet is transmitted between the access network and the terminal through the air interface, and the PDU data packet carries component ID or component combination index information.

10. The 6G network system based on protocol component substitution migration and bypass according to claim 9, characterized in that , The ways in which the PDU data packet carries component ID or component combination index information include: Each protocol layer component indicates the transfer target component ID in the PDU header of its component; The component combination index of the receiving side is indicated in the PDU header of the MAC layer, and based on this index, the receiving party determines the component IDs associated with each layer.

Images