Method and system for designing signaling radio bearers and handling control plane data transmission and reception

Abstract

In embodiments, methods of signaling radio bearers and handling control plane data transmission and reception for a 6G network architecture are disclosed. The method includes flexible and simple network functions for providing a degree of freedom for network function placement due to clouding and virtualization of the network functions. The method also includes a 6G network architecture in which any network node communicates with any other network node located in the RAN or core network function, thereby enabling a single anchor of the UE to exchange control signaling with the network. The method also enables the new network architecture of the 6G to design signaling radio bearers required for communication between the network and the UE. The method also defines procedures for handling control plane messages for transmission and reception between the UE and the network entity.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communications. For example, the present disclosure relates to designing signaling radio bearers and processing control plane data transmission and reception for 6G network architecture. Background Art

[0002] In recent years, some broadband wireless technologies have been developed to meet the growing number of broadband users by providing better applications and services. The second generation (2G) wireless communication system has been developed to provide voice services while ensuring user mobility. The third generation wireless communication system supports not only voice services but also data services. In recent years, the fourth generation wireless communication system has been developed to provide high-speed data services. However, currently, the fourth generation (4G) wireless communication system cannot meet the growing demand for high-speed data services due to lack of resources. In order to meet the growing demand for high-speed data services, the fifth generation wireless communication system is deployed to solve this problem. In addition, the fifth generation (5G) wireless communication system provides ultra-reliability and supports low-latency applications.

[0003] The 5G system architecture is based on a service-based architecture (SBA). According to TS 23.501, the 5G system architecture is defined as service-based, and the interactions between network functions are represented in the following two ways.

[0004] A service-based representation where network functions within the control plane (e.g. AMF) enable other authorized network functions to access their services. This representation also includes point-to-point reference points where necessary.

[0005] The reference point representation shows that there is interaction between NF services in network functions described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0006] Figure 1 FIG. 1 is a diagram illustrating a core network architecture 100 depicting a 5G service-based core network architecture 100 using a service-based interface within a control plane (CP) according to a prior art solution. Figure 1, considering conventional methods and systems, the 5G service-based core network architecture brings more scalability and flexibility because any network function (NF) node can interact with any other node in the 5G service-based system architecture. The 5G service-based system architecture should balance the service-based interaction between CP (control plane) network functions. In this case, the NF set provides services to other authorized NFs to access their services through SBI (service-based interface). NF service is a capability exposed by NF (NF service generator) to other authorized NFs (NF service consumers) through service-based interfaces. NF service can support one or more NF service operations. Network functions can provide different functions and therefore provide different NF services. Each NF service provided by a network function should be independent, operated and managed independently of other NF services (e.g., extensions) provided by the same network function.

[0007] The service-based interface represents how a set of services are provided or exposed through a given NF. This is the interface where NF service operations are invoked. The following control plane interfaces within the 5G service-based system architecture are specified in 3GPP TS 23.501 and are defined as service-based interfaces: - Namf, Nsmf, Nudm, Nnrf, Nnssf, Nausf, Nnef, Nsmsf, Nudr, Npcf, N5g-eir, Nlmf. The 5G system architecture includes the following network functions (NFs).

[0008] Authentication Server Function (AUSF).

[0009] Access and mobility management function (AMF).

[0010] Data Network (DN), for example, operator service, Internet access or third-party service.

[0011] Unstructured Data Storage Function (UDSF).

[0012] Network Exposure Function (NEF).

[0013] Network Repository Function (NRF).

[0014] Network Slice Specific Authentication and Authorization Function (NSSAAF).

[0015] Network Slice Selection Function (NSSF).

[0016] Policy Control Function (PCF).

[0017] Session Management Function (SMF).

[0018] Unified Data Management (UDM).

[0019] Unified Data Repository (UDR).

[0020] User Plane Function (UPF).

[0021] UE Radio Capability Management Function (UCMF).

[0022] Application Function (AF).

[0023] User Equipment (UE).

[0024] (Radio) Access Network ((R)AN).

[0025] 5G Equipment Identity Register (5G-EIR).

[0026] Network Data Analysis Function (NWDAF).

[0027] Billing function (CHF).

[0028] The system architecture based on 5G services is based on service-based interfaces, but RAN 106 to CN (core network) is still a point-to-point interaction. Due to network function virtualization, RAN 106 and core network 104 can be in the same location, but it is still RAN 106 that can interact only with a single core network function entity (e.g., AMF 102). RAN 106 and AMF 102 become anchor points for all UE 108 control messages, and each message must pass through these network entities, which is inefficient because it affects the overall control plane latency. This also leads to an increased number of hops and ultimately increases the control plane latency. Therefore, due to the involvement of multiple nodes, it leads to increased overhead and control process completion time at the network node. This point-to-point communication also leads to redundant functions in RAN 106 and core network 104, and uses complex protocols such as NGAP (NG Application Protocol) to communicate between any two nodes.

[0029] Therefore, there is a need to design a more flexible and simple network architecture that can overcome various of the above-mentioned problems. Summary of the invention

[0030]

[0031] According to an example embodiment, a method for processing control plane data transmission in a 6G network is provided. The method includes: deploying a packet data convergence protocol (PDCP) entity at a radio access network (RAN) module, a plurality of network function (NF) modules, or at least one of the plurality of NF modules. The method also includes: determining whether the PDCP entity interacts with each of the plurality of NF modules and the RAN module based on the deployment of the PDCP entity. The method also includes: determining whether synchronization is required between the plurality of NF modules based on the result of the determination. The method also includes: sending a message to the RAN module, a plurality of network function (NF) modules, or at least one of the plurality of NF modules based on the result of the determination of the synchronization requirement.

[0032] According to an example embodiment, a system for processing control plane data transmission in a 6G network is provided. The system includes one or more processors, and the one or more processors are configured to: deploy a packet data convergence protocol (PDCP) entity at a radio access network (RAN) module, a plurality of network function (NF) modules, or one of at least one of the plurality of NF modules. The system is also configured to: determine whether the PDCP entity interacts with each of the plurality of NF modules and the RAN module based on the deployment of the PDCP entity. The system is also configured to: determine whether synchronization is required between the plurality of NF modules based on the result of the determination. The system is also configured to: send a message to the RAN module, a plurality of network function (NF) modules, or one of at least one of the plurality of NF modules based on the result of the determination of the synchronization requirement.

[0033] According to various example embodiments, the present disclosure discloses a more flexible and simple network architecture, a 6G architecture, which can provide freedom for network function deployment due to cloudification and virtualization of network functions. In the 6G network architecture, any network function module can communicate with any other network function module located in the RAN module or in the control plane network function module. This will also enable a single anchor point for the UE to exchange control signaling with the control plane network function module.

[0034] In order to further illustrate the example advantages and features of the present disclosure, a more detailed description will be presented by reference to the various example embodiments thereof shown in the accompanying drawings. It should be understood that these drawings depict example embodiments of the present disclosure and are therefore not to be considered as limiting the scope thereof. The present disclosure will be described and illustrated with respect to additional specificity and detail. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals refer to like elements.

[0036] Figure 1 is a diagram showing a 5G system architecture diagram depicting the use of a service-based interface within a control plane (CP) according to the prior art.

[0037] Figure 2 is a diagram illustrating an example 6G network architecture according to various embodiments.

[0038] Figure 3 is a flow chart illustrating an example method for handling control plane data transmission in a 6G network according to various embodiments.

[0039] Figure 4A and Figure 4B It is an example PDCP entity deployed on a HUB module according to various embodiments and can interact with an NF module.

[0040] Figure 5A and Figure 5B The present invention is a diagram showing that the HUB module can be deployed with all different NFs according to various embodiments. n Figure 2 is a diagram of an example PDCP entity with which the modules interact.

[0041] Fig. 6A and Figure 6B is a diagram illustrating an example PDCP entity deployed on a single NF module that may interact with a DU according to various embodiments.

[0042] Fig. 7A and Figure 7B is a diagram illustrating an example PDCP entity as part of different NF modules of a network or controlling network function modules that may interact with a DU according to various embodiments.

[0043] Fig. 8A and Figure 8B is a diagram showing that an example PDCP entity according to various embodiments is part of a DU module and can interact with an NF module.

[0044] Fig. 9A and Fig. 9B The example PDCP entity according to various embodiments is a part of the DU module and can be connected to different NFs. n A diagram of how modules interact.

[0045] Fig.10is a flow chart illustrating example message generation based on the arrangement of PDCP entities and the interaction between the RAN module and the NF module according to various embodiments.

[0046] Fig.11 is a diagram showing various example design options for a common SRB through which a RAN module (DU or HUB module) may interact with a NF module according to various embodiments.

[0047] Fig. 12A and Fig. 12B is a diagram showing an example design of a single common SRB for a specific logical channel associated with each of different NF modules according to various embodiments.

[0048] Fig.13 is a flow chart illustrating an example process of transmission operations between a UE and a network according to various embodiments.

[0049] Fig.14A and Fig. 14B is a diagram showing different NFs according to various embodiments. n Diagram of an example design of a common SRB associated with modules.

[0050] Fig.15 is a flow chart illustrating an example process of a transmission operation between a UE and a network according to various embodiments.

[0051] Fig.16 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments.

[0052] Fig.17A and Fig. 17B is a diagram showing an example design of a common SRB associated with a specific NF according to various embodiments.

[0053] Fig.18 is a flow chart illustrating an example process of a transmission operation between a UE and a network according to various embodiments.

[0054] Fig.19 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments.

[0055] Fig. 20A and Fig. 20B is a diagram showing different NFs according to various embodiments. n Diagram of an example design of multiple SRBs associated with each of the modules.

[0056] Fig.21 is a flow chart illustrating an example process of a transmission operation between a UE and a network according to various embodiments.

[0057] Fig. 22 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments.

[0058] Fig.23A and Fig. 23B is a diagram showing different NFs according to various embodiments. n Diagram of an example design of a separate SRB associated with each of the modules.

[0059] Fig.24 is a flow chart illustrating an example process of a transmission operation between a UE and a network according to various embodiments.

[0060] Fig.25 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments.

[0061] Fig.26 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments.

[0062] Fig. 27 is a block diagram illustrating an example configuration of a network according to various embodiments.

[0063] Fig.28 is a block diagram illustrating an example configuration of a user equipment (UE) in a wireless network according to various embodiments.

[0064] Furthermore, those skilled in the art will appreciate that elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. For example, a flow chart illustrates a method to help improve understanding of aspects of the present disclosure. Furthermore, with respect to the construction of the device, one or more components of the device may have been represented in the drawings with conventional symbols, and the drawings may illustrate various details useful for understanding the various exemplary embodiments of the present disclosure, so as not to obscure the drawings with details that may be apparent to those of ordinary skill in the art having the benefit of the description herein. DETAILED DESCRIPTION

[0065] It should be understood from the outset that although example implementations of various example embodiments of the present disclosure are shown below, the present disclosure may be implemented using any number of techniques, whether currently known or existing. The present disclosure should not be limited in any way to the illustrative implementations, drawings, and techniques shown below, including the example designs and implementations shown and described herein, but may be modified within the scope of the present disclosure, including the full scope of the appended claims and their equivalents.

[0066] As used herein, the term “some” may mean “none, or one, or more than one, or all”. Accordingly, the terms “none”, “one”, “more than one”, “more than one but not all”, or “all” may all mean “some”. The term “some embodiments” may mean no embodiments, or one embodiment, or several embodiments, or all embodiments. Accordingly, the term “some embodiments” may mean “no embodiments, or one embodiment, or more than one embodiment, or all embodiments”.

[0067] The terms and structures employed herein are used to describe, teach, and illustrate the various embodiments and their specific features and elements, and are not intended to limit, reduce or diminish the spirit and scope of the claims or their equivalents.

[0068] For example, any terms used herein and grammatical variations thereof, such as but not limited to “includes,” “comprising,” “having,” “consisting of,” etc., do not specify precise limitations or restrictions, and certainly do not exclude the possible addition of one or more features or elements (unless otherwise stated), and further should not be considered to exclude the removal of one or more listed features and elements (unless otherwise stated with the restrictive language “must include” or “required to include”).

[0069] Regardless of whether a feature or element is limited to only one use, in any case, it can still be referred to as "one or more features" or "one or more elements" or "at least one feature" or "at least one element". In addition, the use of the term "one or more" or "at least one" feature or element does not exclude the absence of the feature or element, unless otherwise specified by limiting language such as "requires the presence of one or more..." or (requires one or more elements).

[0070] Unless defined otherwise, all terms used herein, especially technical and / or scientific terms, have the same meanings as commonly understood by one of ordinary skill in the art.

[0071] Hereinafter, embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings.

[0072] Figure 2 200 is a diagram illustrating a 6G network architecture according to various embodiments. Figure 2 In the 6G architecture, the RAN module and the network or control plane network function module interact with each other through a common control interface. The RAN module may include a HUB module, a DU module, a switch, a CMD, a UE (user equipment), etc. However, the network or control plane network function module 208 may include different network function (NF) modules. For example, different NF modules may include but are not limited to NF1, NF2, NF3...NF n, other NFs, fused AI, etc. In other words, until the HUB module, it is a RAN module, and other than that, it is a control plane network function module. In an embodiment, different NF modules may belong to different services such as connection management, session management, switching, service request, etc. In an embodiment, throughout this disclosure (including the drawings), the terms "RAN module" and "RAN" are used interchangeably.

[0073] In such Figure 2 In the 6G network architecture shown in , the RAN acts as a service-based RAN. Therefore, the RAN can interact with any NF module present in the network or control plane network function module. All different NF modules can be controlled by a Hub module or a switch or a CMD. In that case, the Hub module or the switch or the CMD becomes a single anchor point for all UE control messages from the UE. The Hub module can be an independent module or can be located at a specific NF, or can be located together with the DU module, or can be maintained at different NF modules. All control message transmissions between the UE and the HUB module are managed by a single layer. For example, in the case where the UE wants to send a control message to the NF1 module of the network. Then, in this case, the control message of the UE is first parsed in the HUB module, and then further, the HUB module transmits the UE control message directly to the NF1 module. In an embodiment, the SBI (service-based interface) is located between the HUB module and the NF module. The SBI interface can use the HTTP / 2 type or equivalent protocol for establishing a connection between the HUB module and the NF module. In an embodiment, the terms "network" and "control plane network function module" and "NF module" and "NF" are used interchangeably throughout this disclosure (including the accompanying drawings). In an embodiment, the terms "network" and "control plane network function module" and "NF module" and "NF" are used interchangeably throughout this disclosure (including the accompanying drawings).

[0074] In an embodiment, the present disclosure discloses that the 6G architecture can implement an end-to-end architecture to a service-based architecture to make the 6G architecture more efficient, flexible and simple. In order to make the 6G architecture more efficient, flexible and simple, the 6G architecture and process are redesigned as follows.

[0075] Design split network functions between RAN and core network function modules.

[0076] Signaling Radio Bearer (SRB) designed for interaction between RAN module and NF module.

[0077] In an embodiment, the design of split network functions between RAN and core network function modules can be obtained as follows.

[0078] Defines the deployment of PDCP entities.

[0079] Define the interactions between different NF modules.

[0080] The generation of messages is handled based on the deployment of the PDCP entity and the interaction between various modules (e.g., RAN module, DU module, HUB module, and NF module).

[0081] In an embodiment, a signaling radio bearer (SRB) designed for interaction between a RAN module and a NF module may be obtained as follows.

[0082] SRB is designed based on the deployment of PDCP entities and the interaction between different NF modules.

[0083] Process the control plane data transmission operation between UE and NW.

[0084] Process the control plane data reception operation between UE and NW.

[0085] In an embodiment, a design of a split network function between a RAN and a core network function module is disclosed. For designing a split network function between a RAN and a control plane network function module, it is necessary to define the arrangement of a packet data convergence protocol (PDCP) entity. The PDCP entity for the control plane network function module is used to deliver and receive control plane data. The control plane data is sent or received via a signaling radio bearer (SRB) terminated at the PDCP entity. In the current 6G architecture, the PDCP terminates at a central unit located at the RAN and interacts with the RRC for control plane data because it is a common anchor point. However, in the proposed 6G architecture, the UE can interact with any NF module. For the interaction, it is necessary to define the arrangement of the PDCP entity that can handle the control plane process, and it is necessary to define the corresponding process that can handle the sending and receiving of messages for the UE. In addition, since any NF module can directly send or receive messages, it is necessary to define options for interaction between the RAN module and the NF module, depending on the deployment of the PDCP entity independently or in a specific NF module.

[0086] The following will explain in more detail the detailed description of designing the split network functions between the RAN and core network function modules and designing the signaling radio bearer (SRB) for the interaction between the RAN module and the NF module.

[0087] Figure 3 3 is a flow chart 300 illustrating an example method for processing control plane data transmission in a 6G network according to various embodiments. Figure 3In 302, a packet data convergence protocol (PDCP) entity / module is deployed on a radio access network (RAN) module, or a PDCP entity can be deployed in different network functions (NFs). n ) module, or the PDCP entity can be deployed at any NF module present in the 6G architecture. At 304, the method determines whether the PDCP entity interacts with each of the different NF modules or interacts with the RAN module. This determination is made based on the deployment of the PDCP entity on the RAN module or on different NF modules. In an embodiment, the interaction between the RAN module and different NF modules will be described in the following paragraphs.

[0088] At 306, the method determines whether synchronization is required between different NF modules. At 308, based on the result of the determination of the synchronization requirement, a message is sent to the RAN module or to different NF modules or to a single NF module. A detailed description of the deployment of the PDCP entity, the interaction between the RAN module and the NF module, and the transmission of the message will be provided in the following paragraphs.

[0089] In the embodiment, the design of the split option between the RAN module and the control network function module is disclosed. When designing, first, decide on the deployment of the PDCP entity on the RAN module or the control network function module. Then, decide on different NF n The interaction between the NF module and the RAN module. Afterwards, the generation of messages is processed based on the deployment of the PDCP entity and the interaction between different NF modules and the RAN module.

[0090] refer to Figure 3 , wherein at 302, it is determined that the deployment of the PDCP entity is located on the RAN module or on different NF modules. In an embodiment, the RAN module may include a HUB module, a DU module, a switch, and a CMD. n After the module is connected, at 304, it is determined whether the PDCP entity is connected to different NF n Each of the modules may interact with the RAN module. Therefore, it is determined whether the PDCP entity is deployed on the RAN module or deployed on different NF n module and determine whether the PDCP entity is associated with different NFs n Each of the modules or both interacting with the RAN module will be discussed in the following paragraphs with the help of Figures 4 to 9.

[0091] Figure 4A and Figure 4B FIG. 400 is a diagram illustrating an example PDCP entity deployed on a HUB module 404 and capable of interacting with an NF module according to various embodiments. Figure 4A and Figure 4B In the 404, the PDCP entity is a separate module and is deployed on the HUB module 404. The Radio Link Control (RLC), Medium Access Control (MAC), Physical Layer and Radio Frequency (RF) exist in the DU (Distributed Unit) 406. The Radio Frequency (RF) and Transceiver Point (TRP) can be a separate unit 408.

[0092] After deployment, according to the disclosed design, the PDCP entity can communicate with different NFs. n Only one NF module among the NF modules interacts, such as Figure 4A and Figure 4B As shown in . For example, one of the NF modules may be, but is not limited to, NF1402, which may interact with the HUB module 404. The HUB module 404 may interact with only one of the NF modules through a service-based interface, which may run through HTTP through a TCP / SCTP interface. In an embodiment, the HUB module 404 may also be a part of the DU module 406 itself, where all modules such as PDCP, RLC, MAC, and PHY may be arranged together. In an embodiment, if the HUB module 404 and the switch are separate, they may interact with each other through an F1-AP or point-to-point interface or a service-based interface. All other NF n Modules can interact with NF1 which can be used to send and receive messages.

[0093] In an embodiment, the Service Data Adaptation Protocol (SDAP) may be a part of the DU module 406 or associated with the module handling the Control Unit User Plane (CU-UP). Any new data layer module may be a part of the DU module 406 or any other equivalent module and handle the control messages such as the PDCP entity or anything equivalent is a part of the HUB module 404. In case any other NF module wants to send a message to the HUB module 404, then in that case the message has to be parsed only by NF1 402.

[0094] In an example implementation, consider that the PDCP entity is located on the HUB module 404 and the PDCP entity can only communicate with different NFs of the network. n Example of NF1 402 or control plane network function module interaction among modules. For example, different NFs existing in the network n The modules can be NF2, NF3, NF4, etc. nThe interaction between the HUB module 404 and the NF1 402 is implemented through a service-based interface, which can be run through HTTP through a TCP / SCTP interface. The HUB module 404 needs to be enabled together with the PDCP entity and should support all defined functions.

[0095] Figure 5A and Figure 5B FIG. 1 is a diagram showing a HUB module 404 deployed on the HUB module 404 and capable of being connected to different NFs according to various embodiments. n FIG500 is a diagram of an example PDCP entity with which the modules interact. Figure 5A and Figure 5B In the embodiment, the PDCP entity is deployed on the HUB module 404. The PDCP entity is a separate entity and is deployed on the HUB module 404. The RLC, MAC, physical layer and radio frequency (RF) are located in the DU module 406. In an embodiment, the RF and the transmit / receive point (TRP) can be separate units 408.

[0096] After deployment, according to the disclosed design, the PDCP entity can communicate with all the different NFs of the network such as, for example but not limited to, NF1 402, NF2 502, NF3 506, and NF4 508. n Modules or control plane network function modules interact, such as Figure 5A and Figure 5B In the example scenario, consider that the PDCP entity is deployed on the HUB module 404. Thereafter, the PDCP entity may interact with the NF1 402, NF2 502, NF3 506, and NF4 508 or control plane network function modules of the network. Now, consider that the UE 410 wants to send packets for different NF n Modules, such as NF1 402, NF2 502, NF3 506, and NF4 508, are provided as examples of messages to each of the UE 410 modules, in which case the UE 410 message is first sent to the DU module 406, and then further sent to the HUB module 404. The sending of the message can be implemented through an interface such as an F1-C interface or an F1-U type or an SBI interface between the HUB module 404 and the DU module 406. The HUB module 404 needs to be enabled with the PDCP entity and should support all defined functions. Thereafter, the UE 410 message is sent from the HUB module 404 to NF1 402, NF2 502, NF3 506, and NF4 508. In an embodiment, the Service Data Adaptation Protocol (SDAP) may be part of the DU module 406 or associated with a module that handles CU-UP.

[0097] Fig. 6A and Figure 6B600 is a diagram illustrating an example PDCP entity deployed on a single NF module and that can interact with the DU module 406 according to various embodiments. Fig. 6A and Figure 6B In the example, the PDCP entity is deployed on a single NF module. In a non-limiting example, consider that the PDCP entity is deployed only on a single NF1 module 602 or control plane network function module of the network. RLC, MAC, physical layer and RF are located in the DU module 406. In an embodiment, RF and TRP can be separate units 408.

[0098] After deployment, according to the disclosed design, the PDCP entity can interact with the DU module 406, such as Fig. 6A and Figure 6B In all different NF n Modules or different NFs n In the case that some NF modules in the module want to send messages, they can directly send messages to the DU module 406 or to the UE 410 through the NF1 module 602 (in which the PDCP entity is arranged). In this case, NF1 602 can maintain all other different NF n In an embodiment, the sending of messages between NF1 602 and DU module 406 is implemented through F1-C interface or F1-U type or SBI interface. NF1 602 needs to be enabled with PDCP function and should support all defined functions.

[0099] In an example implementation, consider that UE 410 wants to send a request to any different NF n In the case where the UE 410 sends a message to the DU module 406 directly through the NF1 module 602, the UE 410 may send a message directly to the DU module 406 only through the NF1 module 602. In an embodiment, the SDAP may be a part of the DU module 406 or associated with a module that processes CU-UP.

[0100] Fig. 7A and Figure 7B FIG. 1 is a diagram showing different NFs as a network according to various embodiments. n FIG. 700 is a diagram of an example PDCP entity that may be a part of a module or control network functional module and may interact with the DU module 406. Fig. 7A and Figure 7B In the PDCP entity, different NF n In other words, the PDCP entity can be deployed in different NF nFor example, the PDCP entity may be deployed on NF1 602, NF2 704, NF3 706, and NF4 702. In an embodiment, RLC, MAC, physical layer, and RF are located in DU module 406. RF and TRP may be separate units 408.

[0101] After the deployment of the PDCP entity, according to the disclosed design of the present disclosure, the PDCP entity can interact with the DU module 406, such as Fig. 7A and Figure 7B Therefore, in this case, all the different NF n The module can directly interact with the DU module 406. Consider all the different NF n An example of a module (when each NF module has a PDCP module) wanting to send a message to the DU module 406 or to the UE 410. In this case, all different NF n The module can send messages directly to the DU module 406. In an embodiment, all different NF n The message transmission between the module and the DU module 406 is realized through the F1-C interface or the F1-U type or SBI interface. These interfaces exist in all different NF n module and the DU module 406. In an embodiment, the SDAP may be a part of the DU module 406 or associated with a module that processes CU-UP.

[0102] Fig. 8A and Figure 8B 800 is a diagram illustrating an example PDCP entity that is part of a DU module 802 and that may interact with only one NF module according to various embodiments. Fig. 8A and Figure 8B In the embodiment, the PDCP entity is deployed on the DU module 802. In an embodiment, the RLC, MAC, physical layer and RF are located in the DU module 802. The RF and TRP can be separate units 408.

[0103] After deployment, according to the disclosed design, the PDCP entity may interact with only one of the NF modules or the control plane network function modules present in the network, such as Fig. 8A and Figure 8B As shown in . In a non-limiting example, it is considered that the PDCP entity can interact only with the NF1 module 402. The interaction between the NF1 module 402 and the DU module 802 is implemented through an F1-C interface or an F1-U type or SBI interface.

[0104] In an example implementation, consider the case where UE 410 wants to send a message, then the UE 410 message must be delivered only through NF1 module 410. In an embodiment, DU module 802 needs to be enabled with PDCP functionality and should support all defined functions. In an embodiment, SDAP can be part of DU module 802 or associated with a module that handles CU-UP.

[0105] In an embodiment, any new data layer module can be a part of DU module 802 or any other equivalent module. In this case, the processing of the message will be a part of DU module 802. For example, if any other NF module wants to send a message to DU module 802, the message of any other NF module must go through NF1 402 only.

[0106] Fig. 9A and Fig. 9B 802 and can be used with different NFs according to various embodiments. n FIG900 is a diagram of an example PDCP entity with which the modules interact. Fig. 9A In the embodiment, the PDCP entity may be deployed on the DU module 802. In an embodiment, the PDCP entity may be deployed on a module equivalent to the DU module 802.

[0107] After deployment, according to the disclosed design, the PDCP entity can communicate with different NFs of the network. n Modules or control network function modules to interact, such as Fig. 9A and Fig. 9B In other words, the PDCP entity can interact with each NF module. In an embodiment, the PDCP entity interacts with different NF n The interaction between modules is realized through interfaces such as F1-C interface or F1-U type or SBI interface, which are implemented in different NF n The interface between the module or multiple network function modules and the DU module 802.

[0108] In an embodiment, the DU module 802 needs to be enabled with the PDCP function and should support all defined functions. The SDAP can be part of the DU module 802 or associated with the module that handles CU-UP. In an embodiment, the RLC, MAC, physical layer and RF are located in the DU module 802, and the TRP can be a separate unit 408.

[0109] Now, back to the reference Figure 3 , in deciding whether the PDCP entity is in the RAN module or in different NF nAfter the deployment on the modules (302) and the interaction with each NF module or RAN module based on the deployment decision of the PDCP entity (304), the process moves to 306 and 308. At 306, it is determined that the different NF n Whether synchronization is required between modules, and then refer to Fig.10 The sending of a message to the RAN module or to the NF module based on the result of the determination of the synchronization requirement in step 308 is described in more detail.

[0110] Fig.10 FIG. 100 is a flowchart 1000 showing exemplary message generation based on the arrangement of PDCP entities and the interaction between the RAN module and the NF module according to various embodiments. Fig.10 In the method 1002a, the method 1000 includes the PDCP entity as an independent module, or in other words, the PDCP can be deployed on the HUB module 404. In addition, in 1004b, the method 1000 includes that the PDCP entity can be deployed on the DU module 406. In addition, in 1006c, the method 1000 includes that the PDCP entity can be deployed on different NF modules.

[0111] Continuing with 1002a, when the PDCP entity may be deployed on the HUB module 404, at 1008, the method 1000 may include determining whether the PDCP entity may communicate with all different NFs. n Similarly, continuing to 1004b, when the PDCP entity is deployed on the DU module 406, at 1008, the method 1000 may include determining whether the PDCP entity can interact with all different NF modules. n Similarly, continuing with 1006c, at 1012, method 1000 may include determining different NF n Each or in other words all different NFs in a module n Whether the module has a PDCP entity. The different possibilities at 1002a, 1004b and 1006c are described in more detail below.

[0112] Now, consider the case where the PDCP entity can be deployed on the HUB module 404. After determining that the PDCP entity is deployed on the HUB module 404, moving to 1008. At 1008, the method 1000 can include determining whether the PDCP entity can communicate with all different NFs. n In other words, it determines whether PDCP can interact with different NFs. n At 1016, method 1000 may include determining that among all the different NF nWhether synchronization is required between modules. At 1018, if it is determined that n If synchronization is not required between modules, different NFs are sent directly to the common signaling radio bearer (SRB) module. n Thereafter, the message is sent from the common SRB module to the HUB module 404 in which the PDCP entity is deployed. In an embodiment, throughout the present disclosure and the accompanying drawings, "each NF module" and "each of the different NF modules" are used interchangeably.

[0113] In an example implementation, consider Figure 5A The PDCP entity shown in FIG. 4 is deployed on the HUB module 404. In addition, considering the existence of different NF n Modules, such as NF1 402, NF2 502, NF3 506, and NF4 508 modules. The PDCP entity may interact with NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the method includes determining that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the method 1000 may include, when it is determined that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508, directly sending a message of each NF module, such as NF1 402, NF2 502, NF3 506, and NF4 508, to a common signaling radio bearer (SRB) module. Thereafter, a message is directly sent from the common SRB module to the HUB module 404 in which the PDCP entity is deployed.

[0114] Return to reference Fig.10 1018, wherein the PDCP entity can be deployed on the HUB module 404, and determine the n The method 1000 may include sharing a message of each NF module with one or more NF modules requiring synchronization at 1014. Thereafter, at 1014, the method 1000 may include generating a final message by the one or more NF modules requiring synchronization. The generation of the final message is based on the message of each NF module. Thereafter, the final message of the one or more NF modules requiring synchronization is sent to the HUB module 404 in which the PDCP entity is deployed.

[0115] In an example implementation, consider Figure 5AThe PDCP entity shown in is deployed on the HUB module 404 and the PDCP entity can interact with NF1 402, NF2 502, NF3 506 and NF4 508 or control plane network function modules of the network. Thereafter, the method includes determining that synchronization is required between NF1 402 and NF2 502. Thereafter, NF1 402 and NF2 502 can generate a final message according to the synchronization requirement. Thereafter, the final message is directly sent to the HUB module 404 in which the PDCP entity is deployed.

[0116] Return to reference Fig.10 1008, wherein the PDCP entity can be deployed on the HUB module 404, and determine all NF n The module may not interact with the PDCP entity. n After the module may not interact with the PDCP entity, move to 1010. At step, the method 1000 includes all NF n The module generates a message. NF n The module may generate a message and send the final message to the NF module which may interact with the HUB module 404 in which the PDCP entity is deployed.

[0117] In an example implementation, it is considered that the NF1 402, NF2 502, NF3 506, and NF4 508 modules may not interact with the PDCP entity. After determining that the NF1 402, NF2 502, NF3 506, and NF4 508 modules may not interact with the PDCP entity, the method 1000 includes: n Thereafter, the NF3506 module may generate a message and send a final message to a NF module (which may be any one of NF1 402, NF2 502, NF3 506 and NF4 508) that may interact with the HUB module 404 in which the PDCP entity is deployed.

[0118] Return to reference Fig.10 1002a, wherein the PDCP entity may be deployed on the HUB module 404. After determining that the PDCP entity is being deployed on the HUB module 404, moving to 1008. At 1008, the method 1000 may include determining that the PDCP entity may interact with a single NF module. Thereafter, at 1016, the method 1000 may include, based on the determination that the PDCP entity may interact with a single NF module, determining to nWhether synchronization is required or needed between modules. Thereafter, at 1018, if it is determined that synchronization is not required between all different NF modules, a message of a single NF module is directly sent to a common signaling radio bearer (SRB) module. Thereafter, the message is sent from the common SRB module to the HUB module 404 in which the PDCP entity is deployed.

[0119] In an example implementation, consider Figure 4A The PDCP entity shown in is deployed on the HUB module 404. In addition, it is considered that the PDCP entity can interact with only one of the NF modules, such as NF1 402. Thereafter, the method includes determining that synchronization is not required between NF1 402, NF2, NF3, and NF4. Thereafter, the method 1000 may include, when it is determined that synchronization is not required between NF1 402, NF2, NF3, and NF4, then directly sending a message of NF1 402 to a common signaling radio bearer (SRB) module. Thereafter, the message is sent from the common SRB module to the HUB module 404 in which the PDCP entity is deployed.

[0120] Return to reference Fig.10 1018, wherein the PDCP entity may be deployed on the HUB module 404, and the PDCP entity may interact with only a single NF module. Thereafter, at 1008, it is determined that n The method 1000 may include sharing a message of a single NF module with one or more NF modules requiring synchronization. Thereafter, the method 1000 may include generating a final message by the one or more NF modules requiring synchronization. The generation of the final message is based on the different NF modules. n Thereafter, a final message of one or more NF modules requiring synchronization is sent to the first NF module. Thereafter, the final message is sent by the first NF module to the common signaling radio bearer (SRB) module.

[0121] In an example implementation, it is considered that the PDCP entity is deployed on the HUB module 404, and the PDCP entity can interact with NF1402 (the first NF module), such as Figure 4A As shown in . Thereafter, the method includes determining that synchronization is required between NF1 402, NF2, NF3 and NF4. Thereafter, the NF1 402 message is shared with, for example, NF2, NF3 and NF4 requiring synchronization. Thereafter, a final message is generated by NF2, NF3 and NF4 requiring synchronization. Thereafter, the final message is sent to NF1 402. Then, the final message is sent to a common SRB. Thereafter, the final message is sent to a HUB module 404 in which the PDCP entity is deployed.

[0122] Return to reference Fig.10 1004b, wherein the PDCP may be deployed on the DU module 802. Continuing with 1004b, consider the case where the PDCP entity is being deployed on the DU module 802. After determining that the PDCP entity is being deployed on the DU module 802, moving to 1008. At 1008, the method 1000 may include determining whether the PDCP entity can communicate with all different NFs. n In other words, it determines whether PDCP can interact with different NFs. n Thereafter, at 1016, method 1000 may include determining that n Modules require or do not require synchronization. Thereafter, at 1018, if it is determined that n If synchronization is not required between modules, different NFs are sent directly to the common signaling radio bearer (SRB) module. n Thereafter, the message is sent from the common SRB module to the DU module 802 in which the PDCP entity is deployed.

[0123] In an example implementation, consider that the PDCP entity is deployed on the DU module 802, such as Fig. 9A In addition, considering all NF n The module includes NF1 402, NF2 502, NF3 506, and NF4 508. Then, in this case, the PDCP entity may interact with NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the method includes determining that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the method 1000 may include, when it is determined that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508, directly sending a message to each NF module, such as NF1 402, NF2 502, NF3 506, and NF4 508, to a common signaling radio bearer (SRB) module. Thereafter, a message is directly sent from the common SRB module to the DU module 802 in which the PDCP entity is deployed.

[0124] Return to reference Fig.10 1018, wherein the PDCP entity can be deployed on the DU module 802, and determine the different NF n Then, at 1014, the method 1000 may include sharing different NFs with one or more different NF modules requiring synchronization. nThereafter, at 1014, method 1000 may include generating a final message by one or more different NF modules requiring synchronization. The generation of the final message is based on the different NF n Thereafter, the final message requiring synchronization of one or more different NF modules is sent to the DU module 802 in which the PDCP entity is deployed.

[0125] In an example implementation, it is considered that the PDCP entity is deployed on the DU module 802, and the PDCP entity can interact with NF1 402, NF2 502, NF3 506, and NF4 508, such as Fig. 9A As shown in . Thereafter, the method includes determining that synchronization is required between NF1 402 and NF2 502. Thereafter, NF1 402 and NF2 502 may generate a final message according to the synchronization requirement. Thereafter, the final message is directly sent to the DU module 802 in which the PDCP entity is deployed.

[0126] Return to reference Fig.10 1008, wherein the PDCP entity can be deployed on the DU module 802, and determine all different NF n The module may not interact with the PDCP entity. n After the module may not interact with the PDCP entity, the method 1000 moves to 1010. At 1010, the method 1000 includes, by the NF n The module generates a message. NF n The module may generate a message and send it to the NF module which may interact with the DU module 802 in which the PDCP entity is deployed.

[0127] In an example implementation, it is considered that the NF1 402, NF2 502, NF3 506, and NF4 508 modules may not interact with the PDCP entity. After determining that the NF1 402, NF2 502, NF3 506, and NF4 508 modules may not interact with the PDCP entity, the method 1000 includes: n Thereafter, the NF3 506 module may generate a message and send the final message to the NF module (which may be any NF module among NF1 402, NF2 502, NF3 506 and NF4 508) that may interact with the DU module 802 in which the PDCP entity is deployed.

[0128] Return to reference Fig.101004b, wherein the PDCP entity may be deployed on the DU module 802. After determining that the PDCP entity is deployed on the DU module 802, move to 1008. At 1008, the method 1000 may include determining that the PDCP entity may interact with a single NF module. Thereafter, at 1016, the method 1000 may include determining that the PDCP entity may interact with a single NF module. n Modules require or do not require synchronization. Thereafter, at 1018, if it is determined that n If synchronization is not required between modules, the message of a single NF module is directly sent to a common signaling radio bearer (SRB) module. Thereafter, the message is sent from the common SRB module to the DU module 802 in which the PDCP entity is deployed.

[0129] In an example implementation, consider that the PDCP entity is deployed on the DU module 802, such as Fig. 8A As shown in . In addition, consider that the PDCP entity may interact only with NF1 402. Thereafter, the method includes determining that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the method 1000 may include, when it is determined that synchronization is not required between NF1 402, NF2 502, NF3 506, and NF4 508, then directly sending a message of NF1 402 to the common SRB module. Thereafter, a message is sent from the common SRB module to the DU module 802 in which the PDCP entity is deployed.

[0130] Return to reference Fig.10 1018, wherein the PDCP entity may be deployed on the DU module 802, and the PDCP entity may interact with only a single NF module. Thereafter, at 1008, it is determined that n The method 1000 may include synchronizing one or more different NFs with the modules. n The modules share messages of a single NF module. Thereafter, the method 1000 includes generating a final message by one or more NF modules requiring synchronization. The generation of the final message is based on the different NF n Module. Then, one or more different NFs that require synchronization n The final message of the module is sent to the first NF module. Thereafter, the first NF module sends the final message to the common SRB module.

[0131] In an example implementation, consider that the PDCP entity is deployed on the DU module 802, and the PDCP entity can interact with the NF1402, such as Fig. 8AAs shown in . Thereafter, the method includes determining that synchronization is required between NF1 402, NF2 502, NF3 506, and NF4 508. Thereafter, the NF1 402 message is shared with, for example, NF2 502, NF3 506, and NF4 508 requiring synchronization. Thereafter, a final message is generated by NF2 502, NF3 506, and NF4 508 requiring synchronization. Thereafter, the final message is sent to NF1 402. Then, the final message is sent to a common SRB. Thereafter, the final message is sent to a DU module 802 in which the PDCP entity is deployed.

[0132] Return to reference Fig.10 1006c, wherein the PDCP may be deployed on a NF module, and determining that the PDCP entity interacts with a RAN module corresponding to the DU module 802. After the determination, the method 1000 may include, at 1012, determining whether each NF module has a PDCP entity. After determining that each NF module does not have a PDCP entity, move to 1010. In other words, the PDCP entity may be only on a single NF module. Thereafter, at 1010, the method 1000 may include generating a message for each NF module other than the second NF module. The message is generated by each NF module other than the second NF module. Thereafter, the method 1000 may include sending the generated message of each NF module to the NF module interacting with the DU module 802.

[0133] In an example implementation, consider that the PDCP entity is deployed on a single NF module NF1 602, such as Fig. 6A As shown in , and determining that the PDCP entity interacts with the RAN module corresponding to the DU module. Thereafter, the method includes: n The module generates a message. NF n The modules may include, but are not limited to, NF1 402, NF2 502, NF3 506, and NF4 508. For example, in addition to NF1 having a PDCP entity, NF3 506 and NF4 508 may generate a message. Thereafter, the generated message is sent to NF1 having a PDCP entity 602 interacting with the DU module 802.

[0134] Return to reference Fig.10 1012, wherein the PDCP entity is deployed in the NF n The method 1000 may include determining that each NF module has a PDCP entity in the case of the RAN module corresponding to the DU module 802, and determining that the PDCP entity interacts with the RAN module corresponding to the DU module 802. Thereafter, at 1016, the method 1000 may include determining that each NF module has a PDCP entity in the case of the RAN module corresponding to the DU module 802. n Whether synchronization is required between modules. Determine whether synchronization is required between modules in different NF nAfter synchronization is required between modules, method 1000 includes, at 1014, determining n Modules require synchronization, and different NFs require synchronization n One or more of the modules share messages of each of the different NF modules. Thereafter, the method 1000 includes different NFs requiring synchronization. n One or more of the modules generates a final message. The message is generated based on the shared message. Thereafter, the method includes sending a message to different NFs. n Each of the modules sends a final message. Thereafter, the method includes sending a final message by each of the different NF modules to the common SRB module.

[0135] In the example implementation, consider that the PDCP entity is deployed in different NFs. n On each of the modules, for example, NF1 having PDCP entity 602, NF2 having PDCP entity 704, NF3 having PDCP entity 706, and NF4 having PDCP entity 702, as shown in FIG. Fig. 7A As shown in FIG. 4 , the PDCP entity may interact with the DU module 802. Thereafter, the method includes determining that synchronization is required between the NF1 402, NF2 502, NF3 506, and NF4 508 modules. In addition, considering that the NF1 402, NF2 502, NF3 506, and NF4 508 module messages are to be synchronized with different NFs that require synchronization. n The modules (e.g., NF3 506 and NF4 508) are shared. Thereafter, the final message is generated by NF3 506 and NF4 508 that require synchronization. Thereafter, the final message is sent to NF1 402, NF2 502, NF3 506, and NF4 508. Then, the final message is sent by NF1 402, NF2 502, NF3 506, and NF4 508 to the common SRB.

[0136] Return to reference Fig.10 1012, wherein it is determined that each of the different NF modules has a PDCP entity, and it is determined that the PDCP entity interacts with the RAN module corresponding to the DU module 802, and then moves to 1016. At 1016, the method 1000 includes determining that each of the different NF modules has a PDCP entity, and determining that the PDCP entity interacts with the RAN module corresponding to the DU module 802, and then moves to 1016. n Whether synchronization is required between modules. n After synchronization is not required between modules, method 1000 includes sending different NFs to the common SRB module at 1018. n Messages for each of the modules.

[0137] Now, back to the reference Figure 3, wherein at 304, it is determined that the PDCP entity (deployed on the RAN module) can communicate with different NF n Modules interact with each other. n The interaction between modules is completed through the common SRB. In an embodiment, the RAN module (for example, HUB 404 and DU 406 modules) on which the PDCP entity is deployed can communicate with different NFs through it. n Modules interact with each other using common SRBs to define various design options. Fig.11 to illustrate various design options.

[0138] Fig.11 The RAN module (DU or HUB module) according to various embodiments can communicate with different NFs through n Diagram of various example design options for common SRBs with which modules can interact. Fig.11 In the RAN module (DU or HUB module), it can be connected to different NF n The common SRBs that modules interact with define various design options. Fig.25 These designs are further described in more detail.

[0139] Fig. 12A and Fig. 12B 1200a and 1200b are diagrams showing example designs of a single common SRB for a specific logical channel associated with each of the different NF modules according to various embodiments. Fig. 12A In the embodiment, the case where the PDCP entity is deployed on the RAN module is considered. The PDCP entity in the RAN module may refer to the PDCP entity being deployed on the HUB module 404, which is an independent module, or may be deployed on the DU module 406. Now, the design further illustrates that there are different NFs with different logical channels. n Each of the modules is configured with a single common SRB. In other words, different NFs are configured in the network. n The number of modules can be such that a common SRB can be split across different logical channels. For example, a single common SRB is SRB1 1202. There can be NF1 402, NF2 502, and NF3 1208 with logical channels LC1 1204, LC2 1206, and LC3 1208, respectively. n 1200n configures SRB1 1202.

[0140] In an example implementation, it is considered that the PDCP entity may be deployed on the RAN module and is associated with NF1 402, NF2 502, and NF n1200n associated LC1 1204, LC2 1206 and LC3 1208 configure a single common SRB1 1202. In addition, consider NF1 and NF2 sending messages. These messages are sent through SRB1 1202. Thereafter, mapping of the messages received through SRB1 1202 is performed on a specific logical channel. The specific logical channel can be LC1 1204, LC21206, LC3 1208. The mapping of SRB messages can be performed by the PDCP entity because the PDCP entity knows which NF module it received the message from. Therefore, the PDCP entity only sends the message to a specific logical channel. Therefore, here, in the given example, the PDCP entity knows that NF1 402, NF2 502 have sent the message, and therefore the mapping of the SRB message will be completed using the logical channels LC1 1204, LC2 1206. Therefore, the NF1 402 , NF2 502 messages will be sent to logical channels LC1 1204 and LC2 1206 .

[0141] In an embodiment, there may be a single common SRB configured between the UE and the network, but different NF n Each of the modules may be mapped to a different logical channel with different priorities. In an embodiment, there may be messages of different priorities on multiple RLC or logical channels.

[0142] In the embodiments discussed, no identifier is needed, as the LC will reflect which NF module the message is intended for. Identification of the NF module can be done through the logical channel ID, as the network can provide multiple NF modules for different NF modules. n Each of the modules configures a separate logical channel. The network can share this information with the UE 410 based on RRC or any equivalent message. These logical channels can also be pre-configured between the UE 410 and the network.

[0143] exist Fig. 12B In the above example, the PDCP entity is deployed in different NFs. n Now, the design further illustrates that there are different NFs with different logical channels. n In other words, depending on the number of NF modules configured in the network, the common SRB can be split across different logical channels. For example, the single common SRB is SRB1 1202. There can be NF1402, NF2 502, and NF3 1208 with logical channels LC1 1204, LC2 1206, and LC3 1208, respectively. n1200n configures SRB1 1202. Thereafter, mapping of the message received through SRB1 1202 is performed on a specific logical channel. The specific logical channel may be LC1 1204, LC2 1206, LC3 1208. The mapping of the SRB message may be performed by the PDCP entity because the PDCP entity knows from which NF module it received the message. Therefore, the PDCP entity sends the message only to a specific logical channel. Therefore, here, in the given example, the PDCP entity knows that NF1 402, NF2 502 has sent the message, and therefore the mapping of the SRB message will be done using the logical channels LC1 1204, LC2 1206. Therefore, the NF1 402, NF2 502 message will be sent to the logical channels LC1 1204 and LC2 1206.

[0144] In an example embodiment, consider that UE 410 wants to send messages to different NFs. n 1202. Then, in this case, the UE 410 sends a message to the SRB1 1202. Thereafter, mapping of the message received through the SRB1 1202 is performed on a specific logical channel. Thereafter, the SRB 1202 message is sent to the NF module for which the UE 410 has sent the message. The same process applies when sending a message from the UE 410 to the network function side.

[0145] After associating a single common SRB with a specific logical channel associated with each NF module, the following reference Fig.13 The process of the transmission operation between the UE 410 and the network is described in more detail.

[0146] Fig.13 1300 is a flowchart illustrating an example process of transmission operations between a UE and a network according to various embodiments. Fig.13 In this paper, the PDCP entity is considered to be deployed on the RAN module, and the interaction between the PDCP entity and each NF module is determined, and the PDCP entity is determined in different NF modules. n No synchronization is required between modules. Consider NF1 402, NF2 502, and up to NF n1200n exists in the network. Therefore, at 1302, a single common SRB is configured for each NF module having different logical channels. Different logical channels are configured for each NF module. Thereafter, at 1304, it is determined whether the first NF module among the multiple NF modules wants to send the message. For example, consider that NF1 402 wants to send a message to. Thereafter, at 1306, it is determined whether synchronization is required between the multiple NF modules. In the case where synchronization is not required between the multiple NF modules, then move to 1308. At 1308, the message of the first NF module is sent to a single common SRB module, for example, the message of NF1 402 is sent to SRB1 1202. Thereafter, at 1314, the message received on the common SRB module is mapped relative to a specific logical channel (LC), wherein the message is sent to the RAN module through each LC. Thereafter, the RAN module can send the message to UE 410.

[0147] Returning to reference 1306, if it is determined that different NF n The modules require synchronization, and then move to 1310. At 1310, a message of the first NF module (e.g., NF1 402) is shared with any NF module requiring synchronization except the first NF module (e.g., NF1 402). Thereafter, at 1312, a final message is created by any NF module requiring synchronization except the first NF module and sent to a single common SRB module. Thereafter, at 1314, a message received on the single common SRB module is mapped with respect to a specific LC among a plurality of logical channels (LCs), wherein the SRB message is sent to the RAN module through each LC.

[0148] In an embodiment, the mapping of SRB messages on specific logical channels is disclosed. The mapping of SRB messages on specific logical channels is performed by the PDCP entity because the PDCP entity knows which NF module the message is received from. Therefore, the PDCP entity will only send messages to specific logical channels. Thereafter, the PDCP entity can notify the lower layer of the NF module that has sent the message. In this case, the PDCP entity or any other layer notifies the lower layer such as RLC, MAC, etc. of which NF module the specific message comes from, or it can notify the lower layer of the logical channel carrying the NF module message. This is based on a table maintained in the PDCP entity. The table is made based on the message and the corresponding logical channel. In other words, the table includes the message and the corresponding logical channel. Thereafter, the RAN module can map the message to a specific logical channel. In an embodiment, the DU module 406 processes the message for a specific logical channel based on a conventional scheme based on information from the upper layer and sends it to the UE 410.

[0149] In an embodiment, the process of mapping the SRB message on a specific logical channel is performed by the network. The network can map each NF module to a specific logical channel. The number of logical channels depends on the number of configured NF modules. Each NF module corresponds only to a specific logical channel. This configuration can be sent to the DU module 406 and the UE 410.

[0150] Fig.26 2600 is a flowchart illustrating an example process of receiving operations between a UE and a network according to various embodiments. Consider that a PDCP entity is deployed on a RAN module. After the PDCP entity is deployed, at 2602, different NF n Each of the modules configures a single common SRB module. Thereafter, at 2604, mapping of each NF module relative to a specific logical channel (LC) is completed. Here, the UE maintains the LC and the NF mapping is configured by the network. Thereafter, at 2606, the UE 410 sends a message on a specific LC for the NF module. Thereafter, at 2608, identification of the NF module mapped with a specific LC among the multiple LCs is completed. At 2608, the RAN module or the DU module 406 identifies the NF module based on the specific LC. Thereafter, at 2610, a message is sent to the identified NF module.

[0151] Fig.14A and Fig. 14B is a diagram showing different NFs according to various embodiments. n Figures 1400a and 1400b show example designs of common SRBs associated with modules. Fig.14A In the present invention, the case where the PDCP entity is deployed on the RAN module corresponding to the switch is considered. The RAN module may include a HUB module 404, a CMD, or a DU module 406. In this design, different NF n Each of the modules configures a single common SRB. For example, with respect to NF1 402, NF2 502, and NF n The 1200n module is configured with a single common SRB 1202. The single common SRB is used to n Modules (e.g. from NF1 402, NF2 502 and NF n 1200n module) to transmit and send messages to the HUB module 404 or CMD or switch. Once the CMD or HUB module 404 or switch receives any different NF nModule (e.g., from NF1 402 module), the CMD or HUB module 404 or switch must identify the NF module that can process the message. There may be multiple possibilities by which this can be done, for example, this can be done based on the header of the message indicating which NF module the message is for. It may have an NF header field. This may be based on an L1 header or a layer 2 header such as SDAP, PDCP, RLC, MAC, etc., or based on a layer 3 message header such as RRC or a core network message header. The NW may configure different header fields associated with different NFs, or may pre-configure, for example, NF1 corresponds to 000, NF2 corresponds to 001, etc.

[0152] exist Fig. 14B In the design, consider the case when the PDCP entities are deployed on different NF modules. In this design, a single common SRB terminates at different NF modules. For example, a single common SRB 1202 terminates at NF1 402, NF2 502, and NF n 1200n module termination. In this case, consider that UE 410 sends a message to the NF module. The message will be sent to DU module 406 through the common SRB. Then, based on the message received at DU module 406, DU module 406 identifies which NF module the message sent by UE 410 is for. DU entity 406 can be identified based on L1 header or layer 2 header such as SDAP, PDCP, RLC, MAC, etc. UE 410 or the network will add this information when forming the packet.

[0153] In making a single common SRB with multiple different NF n After the modules are associated, the following references Fig.15 The process of the transmission operation between the UE 410 and the network is described in more detail.

[0154] Fig.15 1500 is a flowchart illustrating an example process of sending operations between a UE and a network according to various embodiments. Considering NF1 402, NF2 502, and NF n 1200n exists in the network. Therefore, at 1502, different NF n Each of the modules (e.g., NF1 402, NF2 502, and NF n 1200n) configures a common single SRB 1202. The common single SRB 1202 is configured by the network. This refers to NF1 402, NF2 502, and NF n1200n can send messages only through a single public SRB 1202. In an embodiment, the network provides the same configuration at the UE 410, and configures the public SRB for transmitting and receiving all messages. Thereafter, at 1504, it is determined whether the first NF module (e.g., NF1 402) wants to send a message. Thereafter, at 1506, before sending the message of the first NF module, it is determined whether synchronization is required between all NF modules. If synchronization is not required between NF modules, move to 1508. At 1508, the message of the first NF module is sent to the configured public SRB module.

[0155] Referring back to 1506, if it is determined that synchronization is required between different NF modules, then the process moves to 1510. At 1510, the different NF modules that require synchronization n The modules share the message of the first NF module. Thereafter, at 1512, a final message is created by any one of the different NF modules requiring synchronization, and then the final message is sent to the common SRB.

[0156] In an example implementation, consider NF1, NF2, ..., up to NF n Existing in the network, such as Fig.14A In the first step, NF1, NF1, NF2, ... until NF n A common SRB is configured. In addition, in the next step, consider that NF1 402 wants to send a message to UE 410. Then, in the next step, before sending the message, consider the case where it is determined whether synchronization is required between NF1 402 and NF2 502. In an embodiment, the method of synchronizing different NFs is disclosed. n Synchronization required between modules. There may be synchronization between NF1402, NF2502 and NF n A small number of messages requiring synchronization between NF1 400n and then the messages need to be sent only by a specific NF. As an example, the DRB configuration message is about NF1 402, and the PHY and MAC configuration is about another NF (assuming NF2 502). Therefore, before sending the message to UE 410, coordination is required between the two NFs (e.g., NF1 402 and NF2 502). The NF module also sends the synchronization required by NF2 through a certain content of the message or through a separate message.

[0157] Thereafter, in the next step, NF1 402 sends the message on the common SRB 1202. In the case that synchronization is not required between the NF1 402 and NF2 502 modules, then the message is sent by either NF1 402 or NF2 502 (the module that generates the message). In the case that it is determined that synchronization is required between the NF1 402 and NF2 502 modules, then NF1 402 shares the message with NF2 502 (with respect to NF2 502, synchronization is required). In this case, NF1 402 shares all information elements and other required information that needs to be sent to the UE, and makes a decision at other NF modules. As an example, it can indicate that there is a handover process, in which case other NF modules need to take actions accordingly. Thereafter, in the next step, NF2 502 creates a final message and sends the final message on the common SRB. In an embodiment, NF2 502 can be a module that has generated a message, or a module that has generated a final message, or a module that can only send a message on a common SRB.

[0158] In an example implementation, consider that the PDCP entity is deployed on the NF module and the common SRB is terminated at the NF module 1202, such as Fig. 14B In this case, the UE 410 wants to send a message to the NF1 402. Then, in this case, based on the information received at the DU module 406, the DU module 406 identifies that the UE 410 message is for the NF1 402 module. The identification is based on the L1 header or the layer 2 header of the PDCP entity.

[0159] Fig.16 1600 is a flowchart illustrating an example process of receiving operations between a UE and a network according to various embodiments. Consider that a PDCP entity is deployed on a RAN module corresponding to a switch. After the PDCP entity is deployed, at 1602, a common SRB is configured for each NF module. For example, a common SRB1 1202 is configured for the NF1 402 module. Similarly, a common SRB1 1202 is configured for NF2 502, and so on until NF n 1200n configures the public SRB1 1202. Thereafter, at 1604, the UE 410 sends a message on the configured public SRB. Thereafter, at 1606, the mapping of the message with respect to the corresponding NF module is completed. The switch maintains the mapping of the message with the corresponding NF module. The switch may have a function that can determine the message type. Thereafter, at 1608, the message is sent to the mapped NF module.

[0160] Fig.17A and Fig. 17B 1400a and 1400b are diagrams showing example designs of common SRBs associated with specific NFs according to various embodiments. Fig.17AIn the embodiment, the case when the PDCP entity is deployed on the RAN module is considered. In this design, the common SRB can be configured to access only a single NF. In this case, all messages will only pass through a single NF, such as NF1 402. In the case of sending and receiving messages between multiple NFs and UE 410, a single SRB can be used to send and receive messages between multiple NFs and UE 410. In other words, only one NF module (such as NF1) can access the common SRB 1702, and all other different NFs can access the common SRB 1702. n The module can send and receive data via NF1 402.

[0161] exist Fig. 17B In the example, consider the case where the PDCP entity is deployed in different NFs. n Module. In this design, the public SRB can be configured to access only a single NF. In this case, consider that UE 410 sends a message to the NF module. The message will be sent to DU module 406 through NF1 (where a single public SRB 1702 is arranged). Then, based on the message received at DU module 406, DU module 406 identifies which NF module the message sent by UE 410 is for.

[0162] After associating a single common SRB with a single NF module, the following reference Fig.18 The process of the transmission operation between the UE 410 and the network is described in more detail.

[0163] Fig.18 1800 is a flowchart illustrating an example process of a transmission operation between a UE and a network according to various embodiments. Consider a case where PDCP is deployed on a RAN module. Here, in this case, the PDCP entity is deployed on a DU module 802. In an embodiment, PDCP may be deployed on a HUB module 404, a switch, and a CMD. Fig.18 In the embodiment, at 1802, the network configures a single common SRB 1702 for a single NF module. Therefore, a single NF module can send messages only through this SRB 1702. In an embodiment, the network provides the same configuration at the UE and configures a common SRB for transmitting and receiving all messages. Thereafter, at 1804, sending a message from the first NF module is performed. For example, consider that the first NF module is NF1 402, which wants to send a message. The message can be a message associated with UE 410. Thereafter, at 1804, before sending the NF1 message, it is determined whether synchronization is required between different NF modules. There are n A small number of messages between modules require synchronization. nAfter the synchronization between modules is completed, the message needs to be sent through a specific NF module. As an example, if the DRB configuration message is about the NF1 module, and the PHY and MAC configuration is about another NF, such as NF2, then coordination is required between these two NF modules before sending the message to the UE. The NF1 402 module also sends the synchronization required by NF2 502 through a certain content of the message or through a separate message.

[0164] Thereafter, at 1806, it is determined that n No synchronization is required between modules, then move to 1810. At 1810, determine whether it is the first module (eg, NF1 402) or a different NF n The module includes SRB termination. If it is determined that the first NF module (eg, NF1 402) includes SRB termination, then at 1814 a message may be sent to NF1 402. Thereafter, at 1814, a final message may be created by NF1 402 and sent over a single common SRB module.

[0165] In an example implementation, consider the case when the PDCP entity is deployed on the NF module. In this design, consider that the common SRB can be configured to access only a single NF1, such as Fig. 17B As shown. In this case, consider that UE 410 sends a message to NF1 402 module. The message will be sent to DU module 406 through NF1 (where a single common SRB is arranged). Then, based on the message received at DU module 406, DU module 406 identifies which NF module the message sent by UE 410 is for.

[0166] Fig.19 1900 is a flow chart illustrating an example process of receiving operations between a UE and a network according to various embodiments. Consider that a PDCP entity is deployed on a RAN module. After deployment, at 1902, a single SRB is configured on at least one of the different NF modules. For example, consider that a single SRB is configured on NF1. Thereafter, at 1904, the UE 410 sends a message to the single SRB. Thereafter, at 1906, the message is sent from the single SRB to a specific NF module. The specific NF module may be a different NF. n Any NF module in the module. Consider that a specific module can be different NF n Any different NF modules among the modules. Thereafter, at 1908, the message from the specific module is sent to other different modules outside the specific module.

[0167] Fig. 20A and Fig. 20B is a diagram showing different NFs according to various embodiments. nFigures 2000a and 2000b show an example design of multiple SRBs associated with each of the modules. Fig. 20A In the design, consider the case when the PDCP entity is deployed on the RAN module. In this design, multiple SRBs are configured for each NF module, for example, each NF module can access multiple SRBs. In addition, in this design, messages with priority are sent through high SRBs or low SRBs. Messages with high priority can be sent to high priority SRBs, and messages with low priority can be sent to low priority SRBs. In addition, in this design, an identifier is required at the RAN module because multiple or all NF modules use the same SRB. The method of identifying NF modules defined above also applies in this case.

[0168] exist Fig. 20B In the example, consider the case where the PDCP entity is deployed in different NFs. n In this design, multiple SRBs are configured for each NF module. SRBs can be high priority SRBs or low priority SRBs. NF can generate high priority or low priority messages, and accordingly they can be mapped to SRBs that can carry high or low priority messages.

[0169] In enabling multiple public SRBs with different NF n After each of the modules is associated, in the following paragraphs with the help of Fig.21 The process of the transmission operation between UE 410 and the network is described.

[0170] Fig.21 21 is a flowchart 2100 illustrating an example process of transmission operations between a UE and a network according to various embodiments. Fig.21 In the present invention, the PDCP entity is deployed on the RAN module. After the PDCP entity is deployed, at 2102, different NF n Each of the modules is configured with multiple SRBs. The multiple SRBs have different priorities. Thereafter, at 2104, consider that the first NF module wants to send a message. For example, the first NF module is the NF1 402 module that wants to send a message. Thereafter, at 2106, determine the different NFs. n Whether synchronization is required between modules. If it is determined that different NF n No synchronization is required between modules, and then move to 2108. At 2108, determine whether the NF1 402 message is a high priority. The determination of whether the NF1 402 message is a high priority depends on the different NF nNo synchronization determination is required between modules. Therefore, if it is determined at 2108 that the NF1 402 message is not a high priority, then move to 2114. At 2114, the NF1 402 message is sent on a low priority SRB. Further, referring back to step 2108, if it is determined that the NF1 402 message is a high priority, then move to 2116. At 2116, the NF1 402 message is sent on a high priority SRB.

[0171] Now, referring back to step 2106, if it is determined that synchronization is required between different NF modules, then move to step 2110. At 2110, the message of the first NF module (e.g., the NF1 402 module message) is shared with any NF module that requires synchronization except the first NF module (e.g., the NF1 402 module). Any NF module may be NF2, NF3, ... until NF n . Thereafter, at 2112, a final message is created by any NF module that requires synchronization except the first NF module (e.g., NF1 402). Thereafter, at 2108, it is determined whether the final message is a high priority. If it is determined that the final message is not a high priority, then move to 2114. At 2114, NF1 402 sends the final message on a low priority SRB. Further, returning to reference 1208, it is determined that the final message is a high priority, and then move to 2116. At 2116, NF1 402 sends the final message on a high priority SRB.

[0172] In the example implementation, consider the scenario where the PDCP entity is deployed on the RAN module. After the PDCP entity is deployed, consider NF1 402 and NF n The 1200n module is configured with SRB1 2002 and SRB2 2004, as Fig. 20A and Fig. 20B As shown in . Assume that SRB1 2002 is of high priority and SRB2 2004 is of low priority. Thereafter, take the case where the NF1 402 module wants to send a message. Before sending the NF1 402 message, determine whether synchronization is required between the NF2 502 module and the NF3 504 module. If it is determined that synchronization is not required between the NF2 502 module and the NF3 504 module, then determine whether the NF1 402 message is of high priority. In the case that the NF1 402 message is of high priority, then the NF1 402 message is sent on the high priority SRB1 2002. In the case that it is determined that the NF1 402 message is not of high priority, then the NF1 402 message is sent on the low priority SRB 2004.

[0173] In an example implementation, consider that synchronization is required between the NF2 502 module and the NF3 504 module, then the message of the NF1 402 module is shared with either the NF2 502 module or the NF3 504 module. Sharing the message with the NF2 502 module or the NF3 504 depends on synchronization. Consider sharing the message of the NF1 402 module with the NF2 502 module based on synchronization. Thereafter, a final message is created by the NF2 502 module. In the case that the final message is high priority, then NF1 402 sends the final message on the high priority SRB1 2002. In the case that the final message is not high priority, then NF1 402 sends the final message on the low priority SRB 2004.

[0174] Fig. 22 2200 is a flowchart illustrating an example process of receiving operations between a UE and a network according to various embodiments. Consider that a PDCP entity is deployed on a RAN module, and multiple SRBs are configured for each of different NF modules at 2202. Thereafter, at 2204, the UE sends a message on multiple SRBs based on priority. In an embodiment, the message may be a high priority message or a low priority message. Multiple SRBs have different priorities. For example, different priorities may be high priority SRBs or may be low priority SRBs. This priority may be determined based on the message type or layer or NF module. Thereafter, at 2206, the RAN module (DU) maintains a mapping table of high priority and low priority messages. Thereafter, at 2208, it is determined whether the message is received on a high priority SRB. If it is determined that the message is not received on a high priority SRB, move to 2210. At 2210, the message is sent to a NF module having a low priority SRB or having a low priority message. At 2212, the control entity may have a function that can determine the message type.

[0175] Referring back to 2208, it is determined that a message is received on a high priority SRB. Thereafter, at 2214, the message is sent to a NF module with a high priority SRB or with a high priority message. In an embodiment, at 2216, the RAN module may have a function that may determine the message type.

[0176] Fig.23A and Fig. 23B is a diagram showing different NFs according to various embodiments. n Figures 2300a and 2300b show example designs of separate SRBs associated with each of the modules. Fig.23AIn the embodiment of the present invention, the case when the PDCP entity is deployed on the RAN module corresponding to the switch is considered. In this design, a separate SRB can be configured for each of the different NF modules. Each of the separate SRBs has a different priority. The priority of these separate SRBs depends on the message type or UE layer. Each SRB is responsible for carrying messages from a specific NF only. Similarly, UE 410 also sends specific messages through specific SRBs.

[0177] exist Fig. 23B In the example, consider the case where the PDCP entity is deployed in different NFs. n In this design, different NF n Each of the modules configures a separate SRB. Each of the separate SRBs has a different priority. The priority of these separate SRBs depends on the message type or UE layer.

[0178] In making separate SRBs with different NF n After each of the modules is associated, in the following paragraphs, with the help of Fig.24 Describes the processing of sending operations between the UE and the network.

[0179] Fig.24 2400 is a flowchart illustrating an example process of a transmission operation between a UE and a network according to various embodiments. Consider the case where a PDCP entity is deployed on a RAN module corresponding to a switch. Fig.24 In the embodiment, the PDCP entity is deployed on the DU module 802. In the embodiment, the PDCP can be deployed on the HUB module 404, the switch and the CMD. Fig.18 In the example, at 2402, the network configures a separate SRB for each of the different NF modules. For example, the network may configure SRB1 2302 for NF1 402, SRB2 2304 for NF2 502, and SRB3 2305 for NF n 1200n configures SRBn 2300n. Thereafter, at 2404, a message is sent from the first NF module. Consider that the first NF module is NF1 402. Thereafter, at 2406, before sending the NF1 402 message, it is determined whether synchronization is required between different NF modules. If it is determined that synchronization is required between different NF modules, n If synchronization is not required between modules, move to 2408. At 2408, the message of the first NF module (eg, NF1 402) is sent to the SRB supported by NF1. For example, the message of the NF1 402 module is sent to the SRB1 2302 supported by the NF1 module 402.

[0180] Now, returning to reference 2406, where, if it is determined that in different NF nThe modules require synchronization, and then move to 2410. At 2410, different NFs other than the first module that require synchronization n The modules share the messages of the first NF module (e.g., NF1 402 messages). Therefore, assume that in this case, synchronization is required between NF2 502 and NF3 504. Then, in this case, the NF1 module 402 messages are shared with NF2 502 and NF3 504. Thereafter, at 2412, the NF1 modules are sent by different NFs. n The module creates the final message, and the final message is sent to different NFs n SRBs supported by the module.

[0181] Fig.25 2500 is a flowchart illustrating an example process of receiving operations between a UE and a network according to various embodiments. Consider that a PDCP entity is deployed on a RAN module corresponding to a switch. After deployment, at 2502, a separate SRB may be configured for each NF module. Thereafter, at 2504, the UE 410 sends a message on an SRB specific to the NF module. Thereafter, at 2506, the RAN module (DU module) identifies a specific NF module based on the SRB. Thereafter, at step 2508, the message is sent to the specific NF module.

[0182] Fig. 27 2700 is a block diagram illustrating an example configuration of a network according to various embodiments. The network 2700 may correspond to a 3GPP PLMN-A and / or an N3GPP PLMN-A, as discussed throughout this disclosure. The network 2700 may include at least one processor (e.g., including a processing circuit) 2702, a storage unit (e.g., a memory) 2706 (e.g., a storage device), and a communication unit (e.g., including a communication circuit) 2704 (e.g., a communicator or a communication interface). In addition, the network 2700 may also include a cloud RAN (C-RAN), a central unit (CU), a core network (NW), a distributed unit (DU), or any other possible network (NW) entity. The communication unit 2704 may include various communication circuits and perform one or more functions for sending and receiving signals via a wireless channel.

[0183] As an example, the processor 2702 may include various processing circuits and may be a single processing unit or may all include many units of multiple computing units. The processor 2702 may be implemented as one or more of a microprocessor, a microcomputer, a microcontroller, a digital signal processor, a central processing unit, a state machine, a logic circuit, and / or any device that manipulates a signal based on an operation instruction. Among other capabilities, the processor 2702 is configured to fetch and run computer-readable instructions and data stored in a memory. The processor 2702 may include one or more processors. At this point, the one or more processors 2702 may be general-purpose processors such as a central processing unit (CPU), an application processor (AP), etc., such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-specific processor such as a neural processing unit (NPU). The one or more processors 2702 may control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (e.g., memory unit 2706). Predefined operating rules or artificial intelligence models are provided by training or learning.

[0184] Memory 2706 can include any non-transitory computer-readable medium known in the art, including, for example, volatile memory such as static random access memory (SRAM) and dynamic random access memory (DRAM), and / or non-volatile memory such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disks, optical disks, and magnetic tapes.

[0185] Fig.28 is a block diagram illustrating an example configuration of a user equipment (UE) in a wireless network according to various embodiments. Fig.28 The configuration of the UE 2800 may be understood as a part of the configuration of the UE 2800. Hereinafter, it should be understood that the terms including "unit" or "module" at the end may refer to a unit (for example, including various circuits) for processing at least one function or operation, and may be implemented in hardware, software, or a combination of hardware and software.

[0186] refer to Fig.28, UE 2800 may include at least one processor (e.g., including processing circuitry) 2802, a communication unit (e.g., including communication circuitry) 2804 (e.g., a communicator or communication interface), and a storage unit (e.g., memory) 2806 (e.g., a storage device). As an example, UE 2800 may be a user equipment 410, such as a cellular phone or other device that communicates through multiple cellular networks (such as 3G, 4G, 5G or quasi-5G, 6G networks, or any future wireless communication networks). The communication unit 2804 may include various communication circuits and perform functions for sending and receiving signals via wireless channels.

[0187] As an example, the processor 2802 may include various processing circuits and may be a single processing unit or may all include many units of multiple computing units. The processor 2802 may be implemented as one or more of a microprocessor, a microcomputer, a microcontroller, a digital signal processor, a central processing unit, a state machine, a logic circuit, and / or any device that manipulates a signal based on an operation instruction. Among other capabilities, the processor 2802 is configured to fetch and run computer-readable instructions and data stored in a memory. The processor 2802 may include one or more processors. At this point, the one or more processors 2802 may be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU). The one or more processors 2802 may control the processing of input data according to predefined operating rules or AI models stored in non-volatile memory and volatile memory (e.g., memory unit 2806). Predefined operating rules or artificial intelligence models are provided by training or learning.

[0188] Memory 2806 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory such as static random access memory (SRAM) and dynamic random access memory (DRAM), and / or non-volatile memory such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk, and magnetic tape.

[0189] Reference is now made to various exemplary advantages of the methods and systems disclosed herein. Technical advantages of conventional and prior art states are provided by the methods and systems disclosed herein. Technical advantages include, for example and not as limitation.

[0190] 6G networks provide freedom in network function deployment due to cloudification and virtualization of network functions.

[0191] Reduce overall network latency.

[0192] Although the present disclosure has been shown and described with reference to various exemplary embodiments, it will be understood that the various exemplary embodiments are intended to be illustrative, rather than restrictive. Those skilled in the art will further appreciate that various work modifications may be made to the method in order to implement the present disclosure. The accompanying drawings and the above description provide examples of embodiments. Those skilled in the art will appreciate that one or more of the elements described may be well combined into a single functional element. Alternatively, some elements may be segmented into multiple functional elements. Elements in one embodiment may be added to another embodiment.

Claims

1. A method for processing control plane data transmission in a 6G network, the method include: Deploying (302) a packet data convergence protocol PDCP entity at one of a plurality of radio access network RAN ​​modules, a plurality of network function NF modules, or at least one NF module of the plurality of NF modules; Based on the deployment of the PDCP entity, determining (304) whether the PDCP entity interacts with each of the plurality of NF modules and with the RAN module; Based on the result of the determination, determining (306) whether synchronization is required between the plurality of NF modules; as well as Based on the result of determining that the synchronization is required, a message is sent (308) to one of the RAN module, the plurality of NF modules, or the at least one NF module among the plurality of NF modules.

2. The method according to claim 1, in: Based on the PDCP entity being deployed at the RAN module, determining that the PDCP entity interacts with each of the plurality of NF modules, and determining that synchronization is not required between the plurality of NF modules, the method further includes: A message for each of the multiple NF modules is sent to a common signaling radio bearer (SRB) module.

3. The method according to claim 1, in: Based on the PDCP entity being deployed at the RAN module, determining that the PDCP entity interacts with each of the plurality of NF modules, and determining that synchronization is required between the plurality of NF modules, the method further includes: sharing a message of each of the plurality of NF modules with one or more NF modules requiring synchronization; The one or more NF modules requiring synchronization generate a final message based on the shared message, sending the final message of the one or more NF modules requiring synchronization to each of the plurality of NF modules; and The final message is sent by each of the multiple NF modules to a common signaling radio bearer SRB module.

4. The method according to claim 1, in: Based on the PDCP entity being deployed at the RAN module, determining that the PDCP entity interacts with a first NF module among the multiple NF modules, and determining that synchronization is not required between the multiple NF modules, the method further includes: Sending the message of the first NF module to a common signaling radio bearer SRB module, wherein NF modules other than the first NF module interact with the first NF module, and The NF modules other than the first NF module send messages of the NF modules other than the first NF module to the first NF module.

5. The method according to claim 1, in: Based on the PDCP entity being deployed at the RAN module, determining that the PDCP entity interacts with a first NF module among the multiple NF modules, and determining that synchronization is required between the multiple NF modules, the method further includes: Sharing the message of the first NF module with the one or more NF modules requiring synchronization; The one or more NF modules requiring synchronization generate a final message based on the shared message, and sending the final message of the one or more NF modules to the first NF module; and The final message is sent by the first NF module to the common signaling radio bearer SRB module.

6. The method according to claim 1, in: Based on the PDCP entity being deployed on at least one NF module among the multiple NF modules, determining that the PDCP entity interacts with the RAN module corresponding to the distributed unit DU, the method further includes: Determine whether each NF module has the PDCP entity; Based on determining that each of the NF modules does not have the PDCP entity, generating a message for each of the plurality of NF modules except the second NF module, wherein the message is generated by each of the plurality of NF modules except the second NF module; and sending the message generated by each of the plurality of NF modules to at least one NF module among the plurality of NF modules, wherein the at least one NF module among the plurality of NF modules interacts with the RAN module corresponding to the DU, Wherein, based on determining that each of the NF modules has the PDCP entity, the method further includes: Determining that synchronization is required between the plurality of NF modules; Based on determining that synchronization is required between the plurality of NF modules, sharing a message of each of the plurality of NF modules with the one or more NF modules requiring synchronization; The one or more NF modules requiring synchronization generate a final message based on the shared message, Sending the final message to each of the NF modules; and Each of the NF modules sends the final message to the common signaling radio bearer SRB module, or Determining that synchronization is not required between the plurality of NF modules; and Based on determining that synchronization is not required between the multiple NF modules, a message for each of the multiple NF modules is sent to a common signaling radio bearer (SRB) module.

7. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module, the method further includes: configuring a common SRB module for each of the plurality of NF modules; determining whether a first NF module among the plurality of NF modules wants to send the message; Determining that synchronization is not required between the plurality of NF modules; Based on determining that synchronization is not required between the plurality of NF modules, sending the message of the first NF module to the common SRB module; mapping the message received on the common SRB module relative to each of a plurality of logical channels LC, wherein the message is sent to the RAN module via each of the LCs; Determining that synchronization is required between the plurality of NF modules; Sharing the message of the first NF module with any one of the NF modules requiring synchronization except the first NF module; A final message is created by any of the NF modules requiring synchronization except the first NF module; and The final message is sent to the common signaling radio bearer SRB module by any one of the NF modules requiring synchronization.

8. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module corresponding to the switch, the method further includes: configuring a plurality of SRBs for each of the plurality of NF modules, wherein each of the plurality of SRBs has a different priority; determining whether a first NF module among the plurality of NF modules wants to send the message; Determining that synchronization is not required between the plurality of NF modules; Based on determining that synchronization is not required between the plurality of NF modules, determining whether the message is of high priority; Based on determining that the message is not a high priority, sending the message on a low priority SRB; Based on determining that the message is of high priority, sending the message on the high priority SRB; Determining that synchronization is required between the plurality of NF modules; Sharing the message of the first NF module with any one of the NF modules requiring synchronization except the first NF module; A final message is created by any of the NF modules requiring synchronization except the first NF module; determining whether the final message is a high priority message; Based on determining that the message is not a high priority, sending the final message on a low priority SRB; and Based on determining that the message is of high priority, the final message is sent on a high priority SRB.

9. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module corresponding to the switch, the method further includes: configuring a plurality of common SRBs for each of the plurality of NF modules; determining whether a first NF module among the plurality of NF modules wants to send the message; Determining that synchronization is not required between the plurality of NF modules; Based on determining that synchronization is not required between the plurality of NF modules, sending the message of the first NF module to the common SRB module; Determining that synchronization is required between the plurality of NF modules; Sharing the message of the first NF module with any one of the NF modules requiring synchronization; The final message is created by any of the NF modules that require synchronization; and Based on determining that synchronization is required between the plurality of NF modules, the final message is sent to the common SRB.

10. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module corresponding to the switch, the method further includes: Configuring a separate SRB for each of the plurality of NF modules, wherein the separate SRB is configured for each of the NF modules; Sending the message from a first NF module among the plurality of NF modules; Determining that synchronization is not required between the plurality of NF modules; Sending the message to the separate SRB supported by the first NF module; Determining that synchronization is required between the plurality of NF modules; Sharing the message of the first NF module with any one of the NF modules requiring synchronization except the first module; The first NF module requiring synchronization creates a final message; and The final message is sent to the SRB supported by any one of the NF modules requiring synchronization except the first module.

11. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module, the method further includes: configuring a single SRB for the at least one NF module among the plurality of NF modules; Sending the message from a first NF module among the plurality of NF modules; Determining that synchronization is not required between the plurality of NF modules; determining whether the first NF module or the plurality of NF modules include SRB termination; Based on determining that the first NF module or the plurality of NF modules do not include the SRB termination, sending the message to the single SRB, wherein the message is sent by at least one NF module among the plurality of NF modules; Determining that synchronization is required between the plurality of NF modules; Determining that the first NF module or the plurality of NF modules include SRB termination; Based on determining that the first NF module includes the SRB termination, sharing the message of the first NF module with any one of the NF modules requiring synchronization other than the first module; The first NF module requiring synchronization creates a final message; and The final message is sent to the single SRB.

12. The method according to claim 1, in, Based on that the PDCP entity is deployed at the RAN module corresponding to the switch, the method further includes: configuring a different SRB for each of the plurality of NF modules; Sending the message from a first NF module among the plurality of NF modules; Determining that synchronization is not required between the plurality of NF modules; Send the message of the first NF module using the SRB supported by the NF1 module; Determining that synchronization is required between the plurality of NF modules; Sharing the message of the first module with the plurality of NF modules requiring synchronization except the first module; The multiple NF modules requiring synchronization create a final message; Sending the final message to the SRB supported by the plurality of NF modules, or configuring a plurality of SRBs for each of the plurality of NF modules, wherein each of the plurality of SRBs has a different priority; Sending a message of a user equipment UE on the multiple SRBs; determining whether the message was received on a high priority SRB; Based on determining that the message is received on the high priority SRB, sending the message as a high priority to each of the NF modules; and Based on determining that the message is received on a low priority SRB, the low priority message is sent to each of the NF modules.

13. The method according to claim 1, in, Based on that the PDCP entity is deployed at the multiple NF modules, the method further includes: configuring a different SRB for each of the plurality of NF modules; Sending the message from a first NF module among the plurality of NF modules; Determining that synchronization is not required between the plurality of NF modules; and The message of the first NF module is sent with the SRB supported by the first NF module.

14. The method according to claim 1, in: Based on that the PDCP entity is deployed at the RAN module, the method further includes: configuring a common SRB module for each of the plurality of NF modules; mapping each of the NF modules relative to a specific LC among a plurality of logical channels LC; Sending a message for the UE on a specific LC among the plurality of LCs; identifying the NF module mapped with a specific LC among the plurality of LCs; and Send the message to the identified NF module, or configuring a single SRB for the at least one NF module among the plurality of NF modules; sending the message from the UE on the single SRB; Sending the message from the single SRB to a specific NF module among the plurality of NF modules; and sending the message from the specific NF module to the plurality of NF modules other than the specific NF module, or configuring a plurality of SRBs for each of the plurality of NF modules, wherein each of the plurality of SRBs has a different priority; determining whether the UE wants to send the message on the plurality of SRBs, wherein the message is a high priority message and a low priority message; Creating, by the RAN module, a table of high priority messages and low priority messages; determining whether the message was received on a high priority SRB; Based on determining that the message is received on the high priority SRB, sending the message to the NF module having the high priority SRB; and Based on determining that the message was not received on the high priority SRB, sending the message to the NF module having a low priority SRB, or configuring a separate SRB for each of the plurality of NF modules; Sending the message from the UE on an SRB specific to a NF module among the plurality of NF modules; Identifying a specific NF module from among the plurality of NF modules based on the SRB; and The message is sent to the specific NF module based on the identification.

15. A system (2700) configured to process control plane data transmission in a 6G network, the system include: One or more processors (2702), the one or more processors configured to: A packet data convergence protocol PDCP entity is deployed at one of a plurality of radio access network RAN ​​modules, a plurality of network function NF modules, or at least one NF module among the plurality of NF modules; Based on the deployment of the PDCP entity, determining whether the PDCP entity interacts with each of the plurality of NF modules and with the RAN module; Based on the result of the determination, determining whether synchronization is required between the plurality of NF modules; as well as Based on the result of determining that the synchronization is required, a message is sent to one of the RAN module, the plurality of NF modules, or the at least one NF module among the plurality of NF modules.

Images