Intelligent c-plane packet filter

Abstract

Embodiments of the present disclosure relate to intelligent C-plane packet filters. According to aspects of the present disclosure, a method includes determining, by a first network node having an interface with a second network node, how to map a network node related process or service to one or more flows; receiving, by the network node, an indication from a user equipment (UE) indicating how to map the network node related process or service to the one or more flows, wherein the indication is sent in an application protocol; and configuring, by the second network node, the network node related process or service to be streamed.

Description

Cross-reference to related applications

[0001] The following applications are relevant: U.S. Patent Application No. 335833-US-PSP (44665-593) filed by the attorney; and U.S. Patent Application No. 336828-US-PSP (44665-604) filed by the attorney. Technical Field

[0002] The various example implementations generally involve apparatus, methods, and computer program products that support control plane grouped filters. Background Technology

[0003] Wireless networks offer significant advantages to user mobility. The ability to maintain connectivity while on the move not only benefits the user but also contributes to greater efficiency and productivity across society. As expectations for connection reliability, data speed, and low power consumption become more demanding, the technologies used in wireless networks must keep pace. Therefore, continuous focus on improving wireless networking technologies is essential. Summary of the Invention

[0004] According to various aspects of this disclosure, a method includes: a first network node having an interface with a second network node determining how to map a network node-related process or service to one or more streams; the network node receiving from a user equipment (UE) an instruction indicating how to map the network node-related process or service to one or more streams, wherein the instruction is sent in an application protocol; and the second network node configuring the network node-related process or service to be streamed.

[0005] In one aspect, the first network node can support distributed units (DUs), and the second network node can support central units (CUs).

[0006] In one aspect, the first network node can be the first gNB, and the second network node is the second gNB.

[0007] In one aspect, the first network node can be a gNB, and the second network node can be an AMF.

[0008] In one aspect, network node-related processes may include at least one of the following: call setup, handover, session modification request, or measurement results from the UE.

[0009] In one aspect, the instruction may be based on Operations Management and Maintenance (OAM) functions or a set of rules.

[0010] In one aspect, the method may further include: sending a set of rules from a second network node to a first network node; and configuring computing units required by the first network node to understand the set of rules.

[0011] In one aspect, the method may further include: sending a message from the second network node to the first network node acknowledging receipt of the request; and defining a procedure mapping for the UE by the first network node.

[0012] In one aspect, the method may further include: sending a set of rules from a second network node to a first network node; and configuring all computing units required by the first network node to understand the set of rules.

[0013] In one aspect, the method may further include: defining a network node-related process mapping for the UE by the first network node.

[0014] In one aspect, the stream identifier can be carried in the N2, NG, E1, F1 or Xn interface.

[0015] In one aspect, the control plane functions of the core network can map critical message exchanges according to at least two levels of flow identifier priority, including mappings between distributed units (DUs) and centralized units (CUs) or mappings from gNBs to access and mobility management functions (AMFs).

[0016] In one aspect, the stream identifier may be included in the SCTP protocol, UDP protocol, or QUIC protocol.

[0017] In one aspect, the method may also include reducing the message flow from the message exchange based on the priority of the flow identifier.

[0018] In one aspect, a stream identifier may be mapped to at least one of the following: SCTP data block header stream identifier, SCTP source port, QUIC UDP source port packet connection identifier, QUIC packet connection identifier, QUIC packet frame stream identifier, UDP source port, QUIC packet source connection identifier, QUIC packet destination connection identifier, or packet frame stream identifier.

[0019] In one aspect, a flow identifier may be added to at least one of the following: a new RRC header, a low-level protocol, or a network layer or application layer protocol (including, but not limited to, SCTP, QUIC, UDP, F1, E1, Xn, NG, or N2).

[0020] In one aspect, a network device may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform at least any of the aforementioned methods.

[0021] In one aspect, a processor-readable medium storing instructions that, when executed by at least one processor of a network device, cause the network device to perform at least any of the aforementioned methods.

[0022] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

[0023] Some example implementation schemes will now be described with reference to the accompanying drawings.

[0024] Figure 1 This is a diagram illustrating an example embodiment of a wireless networking between a network system and a user equipment (UE) according to an aspect of this disclosure; Figure 2 This is a diagram illustrating an example component of a network system according to an aspect of this disclosure; Figure 3 This is a diagram illustrating an example of an operation for signaling UE capability information to a network device according to one aspect of this disclosure; and Figure 4 This is an illustration of an example of a component of a user equipment or network device according to one aspect of this disclosure. Detailed Implementation

[0025] This disclosure relates to a mapping process that can be used to control plane packet filters and / or have differentiated QoS processing for each flow or separate routing for each flow.

[0026] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the art will recognize that the aspects can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring the description of the aspects.

[0027] Throughout this specification, the reference to "an aspect" or "aspect" means that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Therefore, the phrases "in an aspect" or "in one respect" appearing in various places throughout this specification do not necessarily refer to the same aspect. Furthermore, a particular feature, structure, or characteristic may be combined in one or more aspects in any suitable manner.

[0028] The embodiments described in this disclosure can be implemented in wireless networking devices, such as, but not limited to, devices utilizing Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5GNR), 5G Advanced, 6G (and above), and 802.11ax (Wi-Fi 6), and other wireless networking systems. The term "eLTE" here refers to LTE evolution connected to a 5G core. LTE is also referred to as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0029] This disclosure may use the term "serving network device" to refer to a network node or network device (or part thereof) serving a UE. As used herein, the terms "send to," "transmit to," "receive from," and "cooperate with" (and variations thereof) include communication that may or may not involve communication through one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes acquiring in a first instance or re-acquiring after a first instance. The term "connection" may refer to a physical connection or a logical connection.

[0030] This disclosure uses 5G NR as an example of a wireless network, and may use smartphones and / or extended reality headsets as examples of UEs. It is intended and should be understood that such examples are merely illustrative, and this disclosure applies to other wireless networks and user equipment.

[0031] Figure 1 This is a diagram illustrating an example of wireless networking between network system 100 and user equipment (UE) 150. Network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). Network node 120 will be described in more detail below. As used herein, the term "network apparatus" may refer to any component of network system 100, such as server 110, network node 120, network device 130, any of the foregoing components, and / or any other component of network system 100. Examples of network apparatus include, but are not limited to, apparatuses for implementing various aspects of 5G NR. This disclosure describes implementations related to 5G NR and implementations relating to aspects defined by the 3rd Generation Partnership Project (3GPP). However, it is contemplated that implementations related to other wireless network technologies are included within the scope of this disclosure.

[0032] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, a node that provides New Radio (NR) user plane and control plane protocol terminals toward the UE and is connected to the 5G core (5GC) via an NG interface, for example, according to Section 3.2 of 3GPP TS 38.300 V 16.6.0 (2021-6), which is incorporated herein by reference.

[0033] gNB supports various protocol layers, such as Layer 1 (L1) - the physical layer, Layer 2 (L2) and Layer 3 (L3).

[0034] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which, for example: The physical layer provides a transmission channel to the MAC sublayer; The MAC sublayer provides logical channels to the RLC sublayer; The RLC sublayer provides RLC channels to the PDCP sublayer; The PDCP sublayer provides radio bearers to the SDAP sublayer; The SDAP sublayer provides Quality of Service (QoS) flows to 5GC; The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0035] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) according to Section 6 of 3GPP TS 38.300 V 16.6.0 (2021-6), which is incorporated herein by reference.

[0036] The gNB Central Unit (gNB-CU) includes, for example, logical nodes that host, the gNB's Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols, or the gNB's RRC and PDCP protocols, and controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0037] A gNB Distributed Unit (gNB-DU) comprises, for example, a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0038] The gNB-CU-Control Plane (gNB-CU-CP) includes, for example, logical nodes that host the RRC and control plane portion of the PDCP protocol for the gNB-CU, such as for the en-gNB or gNB. The gNB-CU-CP terminates the E1 interface connected to the gNB-CU-User Plane (gNB-CU-UP) and the F1-C interface connected to the gNB-DU.

[0039] The gNB-CU-User Plane (gNB-CU-UP) includes, for example, a logical node that hosts, for example, the user plane portion of the PDCP protocol for the gNB-CU of the en-gNB, and the user plane portions of the PDCP and SDAP protocols for the gNB-CU of the gNB. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU, for example, according to Section 3.1 of 3GPP TS 38.401 V 16.6.0 (2021-7), which is incorporated herein by reference.

[0040] As used herein, the term "network node" may refer to any one or any combination of gNB, gNB-CU, gNB-DU, gNB-CU-CP, or gNB-CU-UP.

[0041] RAN (Radio Access Network) nodes or network nodes (such as, for example, gNB, gNB-CU, or gNB-DU, or portions thereof) can be implemented using means, for example, having at least one processor and / or at least one memory, which has processor-readable instructions (“programs”) configured to support and / or provision and / or process CU and / or DU-related functionalities and / or features, and / or at least one protocol (sub)layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network). Different functional divisions between central and distributed units are possible. The following will combine... Figure 4 Examples describing such devices and components.

[0042] The gNB-CU and gNB-DU portions can be co-located or physically separated, for example. The gNB-DU can even be further divided into, for example, two parts, one including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud-RAN / Virtual-RAN (BBU / REC / C-RAN / V-RAN), Open-RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Headend / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various example embodiments of this disclosure, a network node supporting at least one of the Central Unit functions or Layer 3 protocols of a radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Distributed Unit functions or Layer 2 protocols of a radio access network can be, for example, a gNB-DU.

[0043] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support serving cells for user equipment (UE), or candidate cells for handover, dual connectivity and / or carrier aggregation and other procedures.

[0044] User equipment (UE) 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, IoT devices, or M2M devices, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least certain operations, such as, for example, an RRC connection to the RAN. Figure 4 Examples of components of the UE are described below. In an implementation, UE 150 may be configured to generate messages to be transmitted to the RAN via radio (e.g., including a cell ID) (e.g., to reach and communicate with the serving cell). In an implementation, UE 150 may generate, transmit, and receive RRC messages containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0045] Continue to refer to Figure 1In an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cell. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In an implementation, network node 120 may be referred to as a base station.

[0046] Figure 1 Examples are provided, and only network system 100 and UE 150 are shown. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user equipment can communicate with network system 100.

[0047] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below should also be applicable to other types of network systems. The network system can be configured according to... Figure 1 The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network (RAN) 225. Additionally, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein and can refer to instructions executed by and implemented by one or more processors.

[0048] The following describes example functionality of the components. This example functionality is merely illustrative, and it should be understood that additional operations and functions can be performed by the components described herein. Furthermore, connections between components can be virtual connections based on service interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" for any other component acting as a service "consumer," providing services for network functions.

[0049] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an Authentication Server Function (AUSF) 211, an Access and Mobility Management Function (AMF) 212, and a Session Management Function (SMF) 213. The core network 210 may also include a Network Slice Selection Function (NSSF) 214, a Network Open Function (NEF) 215, a Network Repository Function (NRF) 216, and a Unified Data Management Function (UDM) 217, which may include a Unified Data Repository (UDR) 224.

[0050] Additional components and functions of the core network 210 may include application functions (AF) 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analytical data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0051] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted through the RAN 225. For example, the UPF 226 identifies services from service providers, internet access, and third-party services.

[0052] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs Packet Data Unit (PDU) session management and manages session context with UPF 226.

[0053] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Auxiliary Information (NSSAI). This selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create private network services. NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

[0054] UDM 217 generates authentication vectors for use by AUSF 211 and AMF 212 and provides user identity processing. UDM 217 can connect to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, as well as provide Quality of Service (QoS) and accounting functions.

[0055] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analytics and provide insights into the capabilities that leverage analytics when providing services. ADRF 221 allows consumers to store, retrieve, remove, and analyze data. MDAF 222 provides additional data analytics services for network functions. OAM 223 provides provisioning and management processing capabilities to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0056] Figure 2 This is merely an example of a component of a network system, and variations are expected within the scope of this disclosure. In implementations, the network system may include... Figure 2 Other components not shown. In an implementation, the network system may not include... Figure 2 Each component is shown. In the implementation, the components and connections can be used with... Figure 2 The connections shown are implemented using different connections. These and other implementations are considered to be within the scope of this disclosure.

[0057] Figure 3 This is a diagram illustrating example operations used to signal user equipment (UE) capability information to network devices. These operations are performed by... Figure 3 The components shown at the top perform the functions, including the UE, one or more network devices (e.g., network nodes, gNBs), and core network functions. Such components can be, for example, a combination of... Figure 1 and Figure 2 The same component described above or otherwise.

[0058] exist Figure 3The operation of the transport layer presents several technical challenges in providing solutions. Transport layer mechanisms (firewalls and rate limiting) are coarse-grained. Both operate at the flow level and do not distinguish which control plane processes and / or message exchanges are critical, tolerating poor packet drop. An example is an emergency call, but instead of servicing existing calls, new call establishment is restricted. The network node (gNB) cannot effectively identify which level of service is meaningful for UE messages. Control plane applications operate based on CPU load, which is detected, for example, by sending and observing latency in sent and received messages. When latency increases, it begins to reject new calls. Part of the CPU load may be caused by the influx of messages that may have already been dropped at the transport layer, which saves CPU time for control plane computational tasks, resulting in higher performance. However, in this scenario, the transport should not blindly drop any packets exceeding the rate limit, but only remove those packets that have the least impact on the call or high-priority (UE) service. Another problem is that the control plane is unaware of the cause of the failure process when packets are dropped at the transport layer. This complicates finding the cause of critical performance indicator (KPI) degradation.

[0059] This disclosure defines a system-level framework relating to how to dynamically configure packet filtering procedures from the UE to the desired network functionality. Packet Filtering Procedures ( Figure 3 The operation defines how signaling packet labeling begins at the UE and how network nodes (gNBs) and core network functions can configure and use packet filters. Packet filters help mitigate high-load situations where the network must drop some packets to maintain system stability or alternatively prioritize flow. Furthermore, the technical issues discussed above can be further improved by having control plane functions label the most critical messages / procedures, making them detectable by transport layer firewalls / packet filters / rate limiting functions. Transport layer functions then selectively reduce packet inflow and control plane CPU load by removing packets that have the least impact on the session / call. The transport plane indicates the affected process. This information is further logged as the reason for the failed process and can be provided to the network operator via the management plane.

[0060] At Operation 301, User Equipment (UE), gNB1, gNB2, and core network functions perform signaling services.

[0061] At operation 302, CU-1 determines which flows are available. Specifically, gNB-CU receives messages, for example via OAM or based on gNB internal algorithm rules, instructing how to map gNB procedures (e.g., network node-related procedures) or services to flows. These procedures may include, for example, call setup, handover, measurements from the UE, and / or services such as emergency services.

[0062] At operation 303, CU-1 sends a configuration, including the procedures for streaming information elements (IEs), to DU-1. DU-1 receives the configuration from CU-1. More specifically, gNB-CU configures each possible and / or required procedure to a stream and sends the rules to the DU. gNB-DU configures all the computational units it needs to understand the rules. Whenever gNB-DU sends a message to gNB-CU, it uses the procedure mapping defined in the stream and defines the message header accordingly.

[0063] At operation 304, DU-1 sends a configuration confirmation to CU-1, including the process of streaming the IE. CU-1 receives the configuration confirmation from DU-1. That is, gNB-DU confirms the request and may also request gNB-CU to perform process mapping for gNB-CU.

[0064] At operation 305, CU-1 sends configuration to the core network functions, including the process of streaming IE. The core network functions receive configuration from CU-1.

[0065] At operation 306, the core network function sends a configuration confirmation to CU-1, including the process of streaming the IE. CU-1 receives the configuration confirmation from the core network function.

[0066] At operation 307, CU-1 sends the configuration to CU-2, including the process of streaming the IE. CU-2 receives the configuration from CU-1.

[0067] At operation 308, CU-2 sends a configuration confirmation to CU-1, including the process of streaming the IE. CU-1 receives the configuration confirmation from CU-2.

[0068] At operation 309, CU-1 sends the configuration to CU-2, including the process of streaming the IE. CU-2 receives the configuration from CU-1.

[0069] At operation 310, CU-2 sends a configuration confirmation to CU-1, including the process of streaming the IE. CU-1 receives the configuration confirmation from CU-2.

[0070] At operation 311, CU-1 sends an RRC reconfiguration to the UE, including the procedure for streaming the IE. The UE receives the reconfiguration from CU-1. Specifically, gNB-DU defines the UE's network node-related procedure mapping.

[0071] At operation 312, the UE sends an RRC reconfiguration to the CU-1, including the procedure for streaming the IE. The CU-1 receives the reconfiguration from the UE. The UE adds a Stream ID to at least one of the following: a layer lower than the RRC layer (e.g., a MAC layer header) or an RRC layer header. Once the gNB-DU receives the procedure-related message from the UE, the gNB-DU knows how to populate and process the message internally within the gNB based on the Stream ID, without opening the actual RRC message.

[0072] At operation 313, signaling services are mapped to flows across UE, gNB1, gNB2, and core network functions.

[0073] Figure 3 The operations described are merely examples, and variations are expected within the scope of this disclosure. In implementations, the operations may include... Figure 3 Other operations not shown. In the implementation, operations may not include... Figure 3 Each operation is shown. In the implementation, the operation can be correlated with... Figure 3 The different sequences shown are implemented. These and other implementations are considered to be within the scope of this disclosure.

[0074] The operation is described below from the UE's perspective. From this perspective, a method may include: a first network node having an interface with a second network node determining how to map a network node-related process or service to one or more streams; the network node receiving from the user equipment (UE) an instruction indicating how to map the network node-related process or service to one or more streams, wherein the instruction is sent in an application protocol; and the second network node configuring the network node-related process or service to be streamed.

[0075] Now for reference Figure 4 This diagram illustrates a block diagram of example components of a UE or network device. The device includes an electronic storage device 410, a processor 420, a memory 450, and a network interface 440. The various components can be communicatively coupled to each other. The processor 420 can be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system-on-a-chip (SoC), or any other type of processor. The memory 450 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 450 includes processor-readable instructions executable by the processor 420 to cause the device to perform various operations, including those mentioned herein, such as... Figure 3 The operation.

[0076] Electronic storage device 410 can be and includes any type of electronic storage device for storing data, such as hard disk drives, solid-state drives, and / or optical disks, as well as other types of electronic storage devices. Electronic storage device 410 stores processor-readable instructions for causing the device to perform its operations, and stores data associated with such operations, such as data related to the 5G NR standard and other data. Network interface 440 enables wireless networking technologies, such as 5G NR and / or other wireless networking technologies.

[0077] Figure 4 The components shown are merely examples, and those skilled in the art will understand that the apparatus includes other components not shown, and may include multiples of any of the components shown. These and other embodiments are considered to be within the scope of this disclosure.

[0078] Other implementations of this disclosure include the following examples.

[0079] Example 1.1 A method comprising: The first network node, which has an interface with the second network node, determines how to map the processes or services associated with the network node to one or more flows; The network node receives from the user equipment (UE) an indication of how to map network node-related processes or services to the one or more flows, wherein the indication is sent in an application protocol; and The second network node configures the network node-related processes or services to be streamed.

[0080] Example 1.2 The method described in Example 1.1, wherein the first network node supports a distributed unit (DU) and the second network node supports a central unit (CU).

[0081] Example 1.3 The method according to any one of the foregoing examples, wherein the first network node is a first gNB and the second network node is a second gNB.

[0082] Example 1.4 The method according to any one of the foregoing examples, wherein the first network node is a gNB and the second network node is an AMF.

[0083] Example 1.5 The method according to any one of the foregoing examples, wherein the network node-related process includes at least one of the following: call establishment, handover, session modification request, or measurement results from the UE.

[0084] Example 1.6 The method according to any one of the foregoing examples, wherein the instruction is based on an Operations Management and Maintenance (OAM) function or a set of rules.

[0085] Example 1.7 The method described in Example 1.6 further includes: The second network node sends the set of rules to the first network node; and The first network node is configured with the computing units required to understand the set of rules.

[0086] Example 1.8 The method described in Example 1.7 further includes: Sending a message confirming the request from the first network node to the second network node; and The process mapping for the UE is defined by the first network node.

[0087] Example 1.9 The method described in Example 1.8 further includes: The second network node sends the set of rules to the first network node; and The first network node configures all the computing units it needs to understand the set of rules.

[0088] Example 1.10 The method described in Example 1.9 further includes: The first network node defines the process mapping related to the network node for the UE.

[0089] Example 1.11 The method described in Example 1.1, wherein the stream identifier is carried in an interface of N2, NG, E1, F1 or Xn.

[0090] Example 1.12 According to the method described in Example 1.1, the control plane functions of the core network map critical message exchanges according to at least two levels of flow identifier priority, the at least two levels of flow identifier priority including mapping between distributed units (DU) and centralized units (CU) or mapping from gNB to access and mobility management functions (AMF).

[0091] Example 1.13 The method described in Example 1.11, wherein the stream identifier is included in the SCTP protocol, UDP protocol, or QUIC protocol.

[0092] Example 1.14 The method described in Example 1.12 further includes: The message flow from message exchange is reduced based on the priority of the flow identifier.

[0093] Example 1.15 The method according to Example 1.11, wherein the stream identifier is mapped to at least one of the following: SCTP data block header stream identifier, SCTP source port, QUIC UDP source port packet connection identifier, QUIC packet connection identifier, QUIC packet frame stream identifier, UDP source port, QUIC packet source connection identifier, QUIC packet destination connection identifier, or packet frame stream identifier.

[0094] Example 1.16 The method according to Example 1.11, wherein the flow identifier is added to at least one of the following: a new RRC header, a low-level protocol, or a network layer or application layer protocol, including but not limited to SCTP, QUIC, UDP, F1, E1, Xn, NG, or N2.

[0095] Example 2.1 A network device comprising: The first network node, which has an interface with the second network node, determines how to map the processes or services associated with the network node to one or more stream components; A component comprising receiving from the user equipment (UE) by the network node an instruction indicating how to map network node-related processes or services to the one or more flows, wherein the instruction is sent in an application protocol; and The components of the processes or services associated with the network node to be streamed are configured by the second network node.

[0096] Example 2.2 A network device according to Example 2.1, wherein the first network node supports a distributed unit (DU) and the second network node supports a central unit (CU).

[0097] Example 2.3 A network device according to any one of the foregoing examples, wherein the first network node is a first gNB and the second network node is a second gNB.

[0098] Example 2.4 A network device according to any one of the foregoing examples, wherein the first network node is a gNB and the second network node is an AMF.

[0099] Example 2.5 A network apparatus according to any one of the foregoing examples, wherein the network node-related process includes at least one of the following: call establishment, handover, session modification request, or measurement results from the UE.

[0100] Example 2.6 A network device according to any one of the foregoing examples, wherein the instruction is based on operation management and maintenance OAM functions or a set of rules.

[0101] Example 2.7 The network device according to Example 2.6 further includes: The component that sends the set of rules from the second network node to the first network node; and The first network node is configured with the components of the computing unit required to understand the set of rules.

[0102] Example 2.8 The network device according to Example 2.7 further includes: A component that sends a message confirming the request from the first network node to the second network node; and The first network node defines the components for the process mapping of the UE.

[0103] Example 2.9 The network device according to Example 2.8 further includes: The component that sends the set of rules from the second network node to the first network node; and The first network node configures all the computing units it needs to understand the set of rules.

[0104] Example 2.10 The network apparatus according to Example 2.9 further includes: The first network node defines the components for process mapping related to the network node for the UE.

[0105] Example 2.11 A network device according to Example 2.1, wherein a flow identifier is carried in an N2, NG, E1, F1 or Xn interface.

[0106] Example 2.12 A network apparatus according to Example 2.1, wherein the control plane functions of the core network map critical message exchanges according to at least two levels of flow identifier priority, the at least two levels of flow identifier priority including a mapping between distributed units (DU) and centralized units (CU) or a mapping from gNB to access and mobility management functions (AMF).

[0107] Example 2.13 A network apparatus according to Example 2.11, wherein the flow identifier is included in the SCTP protocol, UDP protocol, or QUIC protocol.

[0108] Example 2.14 The network device according to Example 2.12 further includes: The number of components in the message stream from the message exchange is reduced based on the priority of the stream identifier.

[0109] Example 2.15 The network apparatus according to Example 2.11, wherein the flow identifier is mapped to at least one of the following: SCTP data block header flow identifier, SCTP source port, QUIC UDP source port packet connection identifier, QUIC packet connection identifier, QUIC packet frame stream identifier, UDP source port, QUIC packet source connection identifier, QUIC packet destination connection identifier, or packet frame stream identifier.

[0110] Example 2.16 A network apparatus according to Example 2.11, wherein the flow identifier is added to at least one of the following: a new RRC header, a low-level protocol, or a network layer or application layer protocol, including but not limited to SCTP, QUIC, UDP, F1, E1, Xn, NG, or N2.

[0111] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to apply this disclosure differently with virtually any suitable detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0112] The phrases “in one aspect,” “in all aspects,” “in all dimensions,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects under this disclosure. The phrase “multiple” may refer to two or more.

[0113] The phrases “in the implementation,” “in the implementation,” “in various implementations,” “in some implementations,” or “in other implementations” can each refer to one or more of the same or different implementations according to this disclosure. The phrase “A or B” means “(A), (B), or (A and B)”, and the phrase “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C)”. Any method, program, algorithm, or code described herein can be translated into or expressed in a programming language or computer program. As used herein, the terms “programming language” and “computer program” each include any language used to specify instructions to a computer, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages ​​that specify their own programs, and all first-, second-, third-, fourth-, fifth-, and more generation computer languages. Databases and other data schemas, and any other meta-languages, are also included. There is no distinction between languages ​​that are interpreted, compiled, or use compilation and interpretation methods. There is no distinction between compiled and source versions of a program. Therefore, a reference to a program in which a programming language can exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. A reference to a program can encompass the actual instructions and / or the intent of those instructions.

[0114] While various aspects of this disclosure have been shown in the accompanying drawings, they are not intended to be limited thereto, as the scope of this disclosure is intended to be as broad as will be permitted in the art, and similarly, when reading the specification. Therefore, the above description should not be construed as restrictive, but merely as an example of particular aspects. Other modifications within the scope and spirit of the appended claims will be contemplated by those skilled in the art.

[0115] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0116] Clause 1. A method comprising: The first network node, which has an interface with the second network node, determines how to map the processes or services associated with the network node to one or more flows; The network node receives from the user equipment (UE) an indication of how to map network node-related processes or services to the one or more flows, wherein the indication is sent in an application protocol; and The second network node configures the processes or services associated with the network node to be streamed.

[0117] Clause 2. The method according to Clause 1, wherein the first network node supports a distributed unit (DU) and the second network node supports a central unit (CU).

[0118] Clause 3. The method according to any one of the preceding clauses, wherein the first network node is a first gNB and the second network node is a second gNB.

[0119] Clause 4. The method according to any one of the preceding clauses, wherein the first network node is a gNB and the second network node is an AMF.

[0120] Clause 5. The method described in Clause 1, wherein the network node-related process includes at least one of the following: call establishment, handover, session modification request, or measurement results from the UE.

[0121] Clause 6. The method according to any one of the preceding clauses, wherein the instructions are based on the operation management and maintenance of OAM functions or a set of rules.

[0122] Clause 7. The method described pursuant to Clause 6 further includes: The second network node sends the set of rules to the first network node; and The first network node is configured with the computing units required to understand the set of rules.

[0123] Clause 8. The method described pursuant to Clause 7 further includes: Sending a message confirming the request from the first network node to the second network node; and The process mapping for the UE is defined by the first network node.

[0124] Clause 9. The method described pursuant to Clause 8 further includes: The second network node sends the set of rules to the first network node; and The first network node configures all the computing units it needs to understand the set of rules.

[0125] Clause 10. The method described pursuant to Clause 9 further includes: The first network node defines the process mapping related to the network node for the UE.

[0126] Clause 11. The method according to any one of the preceding clauses, wherein the stream identifier is carried in an N2, NG, E1, F1 or Xn interface.

[0127] Clause 12. The method according to any one of the preceding clauses, wherein the control plane functions of the core network map critical message exchanges according to at least two levels of flow identifier priority, said at least two levels of flow identifier priority including mapping between distributed unit (DU) and centralized unit (CU) or mapping from gNB to access and mobility management function (AMF).

[0128] Clause 13. The method described in Clause 11, wherein the stream identifier is included in the SCTP protocol, UDP protocol, or QUIC protocol.

[0129] Clause 14. The method described pursuant to Clause 12 further includes: The message flow from message exchange is reduced based on the priority of the flow identifier.

[0130] Clause 15. The method according to Clause 11, wherein the stream identifier is mapped to at least one of the following: SCTP data block header stream identifier, SCTP source port, QUIC UDP source port packet connection identifier, QUIC packet connection identifier, QUIC packet frame stream identifier, UDP source port, QUIC packet source connection identifier, QUIC packet destination connection identifier, or packet frame stream identifier.

[0131] Clause 16. The method of Clause 11, wherein the flow identifier is added to at least one of the following: a new RRC header, a low-level protocol, or a network layer or application layer protocol, including but not limited to SCTP, QUIC, UDP, F1, E1, Xn, NG, or N2.

[0132] Clause 17. A network device comprising: At least one processor; and At least one memory storing instructions that, when executed by the at least one processor, cause the network device to perform at least the method according to any one of clauses 1 to 16.

[0133] Clause 18. A processor-readable medium storing instructions that, when executed by at least one processor of a network device, cause the network device to perform at least the method according to any one of Clauses 1 to 16.

Claims

1. A method for communication, comprising: The first network node, which has an interface with the second network node, determines how to map the processes or services associated with the network node to one or more flows; The first network node receives from the user equipment (UE) an indication of how to map network node-related processes or services to the one or more flows, wherein the indication is sent in an application protocol; as well as The second network node configures the processes or services associated with the network node to be streamed.

2. The method according to claim 1, wherein the first network node supports a distributed unit (DU) and the second network node supports a central unit (CU).

3. The method according to claim 1, wherein the first network node is a first gNB and the second network node is a second gNB.

4. The method according to any one of claims 1 to 3, wherein the first network node is a gNB and the second network node is an AMF.

5. The method of claim 1, wherein the network node-related process includes at least one of the following: call setup, handover, session modification request, or measurement results from the UE.

6. The method according to any one of claims 1 to 3, wherein the instruction is based on operation management and maintenance OAM functions or a set of rules.

7. The method of claim 6, further comprising: The second network node sends the set of rules to the first network node; as well as The first network node is configured with the computing units required to understand the set of rules.

8. The method of claim 7, further comprising: Send a message confirming the request from the first network node to the second network node; as well as The process mapping for the UE is defined by the first network node.

9. The method of claim 8, further comprising: The second network node sends the set of rules to the first network node; as well as The first network node configures all the computing units it needs to understand the set of rules.

10. The method of claim 9, further comprising: The first network node defines the process mapping related to the network node for the UE.

Images