Object-oriented 6G network service support system and method

Abstract

The invention belongs to the technical field of communication, and particularly relates to an object-oriented 6G network service support system, which comprises a service encapsulation layer SOP, a function protocol layer FOP, a resource modeling layer ROM, an object orchestration and scheduling O-ORCH and a network virtual entity management N-VEM. According to the support system provided by the invention, network components are abstracted to form different forms of multi-object cooperation of different service objects such as network Object, network encapsulation, object inheritance and aggregation and polymorphism, and a basis is provided for each function of a flexible network. The supporting system supports a cross-entity inter-object multi-level object service calling mode, communication between UE and a network, communication between UE and UE and communication between network elements are instantiated as inter-object communication, two communication parties construct a communication object two-tuple, communication is divided into peer-to-peer layer communication and non-peer-to-peer layer communication based on a calling hierarchy, and the communication object two-tuple is divided into peer-to-peer layer communication and non-peer-to-peer layer communication. And flexible resource management, scheduling and service cooperation are realized.

Description

Technical Field

[0001] The present invention belongs to the field of communication technologies, and particularly relates to an object-oriented 6G network service support system and method. Background Art

[0002] The goal of 6G is to empower the ubiquitous intelligent information society, and to establish a ubiquitous mobile communication network covering the sky, land, sea and air by integrating communication, computing, sensing, intelligence, etc., so as to achieve high-speed broadband communication with global ubiquitous coverage. At the same time, factors such as the diversification of data sources, applications, communication means, and computing require 6G to have capabilities in aspects such as intelligence and service / business support liberalization. It can be seen that 6G is not only the product of the combination of technologies such as mobile communication, computer, big data, and artificial intelligence (ICDT), but is also evolving towards DOICT to build a new network foundation, that is, simplifying the on-site network networking through CT; through OT, deeply collaborating with industrial protocols to achieve high reliability; realizing intelligence through DT and ensuring low-latency experience in a closed loop; using IT for more industrial applications to reduce construction costs and achieve flexible networking.

[0003] Many emerging scenarios require the network to achieve seamless coverage, extreme connection, "communication-sensing-computation" integration, digital twin parallel interaction, endogenous intelligence, etc., which 5G cannot fully match; therefore, on the basis of 5G typical scenarios (eMBB, ULRRC, and mMTC), 6G needs to support three enhanced technologies:

[0004] (ubiquitous mobile broadband) ubiquitous mobile broadband, ULBC (ultra-reliable low-latency broadband communication) ultra-reliable low-latency broadband communication, mULC (massive ultra-reliable low-latency communication) massive ultra-reliable low-latency communication.

[0005] The main feature that the future network needs to possess is flexibility, while existing technologies such as 5G have problems such as a rigid network architecture, a rigid protocol stack layer, a coarse network resource management granularity, and limited cooperation scope between network function components. The flexibility requirements of 6G networks are mainly reflected in the following three aspects:

[0006] Flexible service and service support: At the application and service layer, a user-centric network is realized. The network serves users, so the design of the network must fully consider the needs of users, activate the network service support function as needed, and make the network "move" with the user and the service ability "migrate" with the service scenario.

[0007] Flexible Resource Management and Scheduling: At the resource layer, the network should have the ability to schedule distributed network resources on demand. To meet the requirements of new scenarios and applications for data traffic and transmission latency, resources such as computing, storage, and transmission will also be distributed across every node of the end-to-end network. And realize the on-demand allocation and flexible scheduling of resources between the cloud, network, and edge, so as to achieve network flexibility in the resource dimension.

[0008] Flexible Adaptive Network Architecture: In the 5G network, the air interface protocol adopts a hierarchical model, including the physical layer, media access control (MAC) layer, radio link control (RLC) layer, and packet data convergence protocol (PDCP) layer. All service data must be processed through these layers. The processing of each layer will introduce specific latency, resulting in latency becoming a bottleneck. In addition, at the network function layer, the network should be able to flexibly and independently expand the capabilities of network elements and quickly iterate and evolve software functions. Specifically, the 6G network should be end-to-end SBA. Therefore, compared with the SBA CN that has been basically completed in the 5G network, 6G needs to focus on the serviceification of the RAN. Summary of the Invention

[0009] To solve the above problems, the present invention provides an object-oriented network service support system, which is characterized by including: a service encapsulation layer SOP, a function protocol layer FOP, a resource modeling layer ROM, an object orchestration and scheduling O-ORCH, and a network virtual entity management N-VEM;

[0010] Service Object Encapsulation Layer SOP: The control plane is based on service objects to perform real-time control of service data streams to support various application services and manage user registration, authentication, and mobility; the user plane is based on service objects to process service data stream transmission; the information plane is based on service objects to provide necessary auxiliary information for the control plane and the user plane;

[0011] The service objects are divided into user plane service objects, control plane service objects, and information plane service objects. Among them, the user plane service objects include sub-module level objects such as QoS profile of service data, data flow control, packet routing and forwarding management, etc., as well as UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of module-level objects. The control plane service objects include service control-related objects such as UE access management, mobility management, session management, security management, and slice management, as well as their capability management, and UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of module-level objects. The information plane service objects include sub-module level objects such as information analysis related to user services, as well as UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of module-level objects.

[0012] Functional Object Protocol Layer FOP: The control plane is based on functional objects and is used for configuration and control between objects. The user plane is based on functional objects and is used for carrying user service information flows. The information plane is based on functional objects and is used to provide necessary auxiliary information for the control plane and the user plane;

[0013] The functional objects are divided into user plane functional objects, control plane functional objects, and information plane functional objects. Among them, the user plane functional objects include sub-module level objects such as the mapping of service data and QoS flow, the mapping of QoS flow and DRB, PDU data encapsulation and decapsulation, the multiplexing and demultiplexing of transport blocks TB, the processing of physical signals, and the QoS guarantee for latency and determinacy-sensitive data, as well as UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of module-level objects. The control plane functional objects include sub-module level objects related to functional control such as the control of the radio configuration signaling process of the UE, resource allocation and UE scheduling control, link adaptation, power control, and logical channel priority mapping management, as well as UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of sub-module level objects. The information plane functional objects include sub-module level objects such as channel / environment measurement and reference signal-related information, as well as UE-level aggregation objects and service-level aggregation objects, where the aggregation objects are implemented through the derivation and inheritance of module-level objects.

[0014] Resource Object Modeling Layer ROM: The control plane is based on resource objects and is used for the real-time control of resource objects, responsible for resource model creation and management; The execution plane is based on resource objects and is the carrier of signal processing. As an execution object entity, it performs specific business operations; The information plane is based on resource objects and is used to monitor the status of resource objects, etc., to assist the control plane and the execution plane in making dynamic adjustments;

[0015] The resource objects are divided into execution plane resource objects, control plane resource objects, and information plane resource objects. Among them, the execution plane resource objects include resource unit level objects such as RF Chain, spectrum, computing power, etc., and service-level aggregation objects constructed by the aggregation of multiple objects, where the aggregation objects are implemented through the derivation and inheritance of unit level objects. The control plane functional objects include sub-module level objects related to resource control such as computing resource configuration and management control, as well as aggregation objects formed by the combination of multiple objects due to business processing needs, where the aggregation objects are implemented through the derivation and inheritance of sub-module level objects. The information plane functional objects include sub-module level objects such as object status monitoring, as well as aggregation objects formed by the combination of multiple objects due to business processing needs, where the aggregation objects are implemented through the derivation and inheritance of sub-module level objects.

[0016] The Object Orchestration and Scheduling O-ORCH regularly updates the service status reported by the Service Encapsulation Layer SOP of multiple network entities (the service status of each object in each layer). Multiple network entities within an autonomous domain share one Object Orchestration and Scheduling O-ORCH. The Object Orchestration and Scheduling O-ORCH performs object management and scheduling for one or more network entities according to business / service requirements;

[0017] The Network Virtual / Entity Management N-VEM undertakes the function of managing network element nodes in the network, including the management of physical network elements and virtual network element nodes. The physical network elements are user equipment UEs and network equipment nodes, and the virtual network element nodes are digital twins based on physical network elements. Multiple autonomous domains share one Network Virtual / Entity Management N-VEM.

[0018] Furthermore, the Service Encapsulation Layer SOP includes an Authentication Server Function module AUSF, an Access and Mobility Management Function module AMF, a Network Service Exposure Function module NEF, a Network Repository Function module NRF, a Network Slice Admission Control Function module NSACF, a Network Slice Authentication and Authorization Function module NSSAAF, a Network Slice Selection Function module NSSF (NetworkSlice Selection Function), a Policy Control Function module PCF, a Session Management Function module SMF, a Non-Seamless WLAN Offload Function NSWOF module, an Edge Application Service Discovery Function module EASDF, an Object Service Capability Management module OSCM, a User Plane Function module UPF, and a Data Analysis Function module DAF.

[0019] Furthermore, the Functional Protocol Layer FOP includes

[0020] The L1 Physical Sublayer PHY is used to utilize the resource objects (radio resources, AI model resources, etc.) provided by the Resource Object Modeling Layer to perform multiple access, provide physical channels, modulation and demodulation, channel encoding and decoding, physical layer processes, physical layer measurements, and anti-interference processing;

[0021] The L2 Link Sublayer includes a Media Access Control Sublayer MAC, which is used for segmentation and recombination of Service Data Units SDUs, realization of the mapping between logical channels and transport channels, multiplexing and demultiplexing of several logical channel SDUs and one Transport Block TB, user equipment scheduling, resource allocation, link adaptation, and power control, HARQ error correction, logical channel priority sorting and processing, and user equipment data priority processing;

[0022] The L3 logical sublayer includes a service data adaptation sublayer SDA, a packet data convergence protocol sublayer PDCP, and a radio link control sublayer RLC; the wireless data adaptation sublayer SDA includes a time-sensitive control TSC functional unit and a QoS Flowhandlding QFH functional unit. The TSC is used to implement deterministic transmission control of services, and the QFH is used to implement the mapping between Qos Flow and DRB, and mark the QoS Flow ID of UL and DL data packets.

[0023] The control plane of the L3 logical sublayer is responsible for the signaling process function of the wireless configuration of the UE; the user plane is responsible for the mapping of service data and QoS, the mapping of QoS and data radio bearer or signaling radio bearer DRB / SRB, the control and transmission of service data streams, deterministic transmission control, unified packet processing of network control signaling and user data, and the interaction with the L2 link sublayer.

[0024] Furthermore, during the process of service data transmission, the functional protocol layer FOP can dynamically bypass one or more sublayers of PDCP, RLC, and MAC or partial functional units of the SDA based on the QoS requirements of the service data.

[0025] Furthermore, the resource modeling layer ROM includes an RMOM functional unit responsible for the management and maintenance of resource model objects, an RORM functional unit responsible for the establishment, association, modification, and maintenance of resource object relationships, a ROSCH functional unit responsible for the real-time scheduling of resource objects, a resource object routing RORU, and an OSMON functional unit responsible for monitoring the status of resource objects.

[0026] Furthermore, the ROSCH functional unit implements internal object scheduling for the control plane, execution plane, and information plane based on the instructions of object orchestration and scheduling of O-ORCH.

[0027] Furthermore, the object orchestration and scheduling O-ORCH includes an object service authorization management OSAU module responsible for configuring the external service permissions of managed objects; a processing object allocation and recycling OARE module that allocates and recycles each layer of objects of entities according to object status and service demand information; an object status management OSM module responsible for collecting, updating, and recording object status and capability information.

[0028] Furthermore, the network virtual / entity management N-VEM includes an unstructured data storage function module UDSF, a UE wireless management function UCMF, a charging function module CHF, a unified data management function UDM module, a message framework adapter function module MFAF, and a digital virtual / twin network management DVNM.

[0029] Furthermore, the service object encapsulation layer SOP, the functional object protocol layer FOP, the object orchestration and scheduling O-ORCH and the network virtual / entity management N-VEM are all provided with an endogenous intelligent body AI Agent, and the resource object modeling layer ROM is provided with an intelligent engine AI Engine. The endogenous intelligent body AI Agent and the intelligent engine AI Engine collaborate through object calls at each layer to support AI type business / services.

[0030] The present invention also provides a business support method based on the above object-oriented network business support system:

[0031] It includes network entity A and network entity B existing in the same autonomous domain, the service requirements of a certain functional layer (SOP or FOP) of entity A that processes a certain service and the service processing capabilities of each functional layer of entity A, determines the service support that needs to initiate a specific functional layer call to other entities and initiates the request to the object orchestration and scheduling module O-ORCH;

[0032] After receiving the business support request, the object orchestration and scheduling makes object allocation and scheduling decisions based on the updated service status of entities A and B, and returns the allocation result to entity A;

[0033] After receiving the object allocation and scheduling decision, entity A updates and stores the capabilities of each functional layer of entity B, and at the same time initiates a request to call a specific functional layer to entity B; after receiving the scheduling request from entity A, the specific functional layer of entity B returns the call confirmation information to entity A and establishes a service function connection with entity A, thereby completing the business support for the specific functional layer call.

[0034] Furthermore, the way in which network entity A schedules the functional layer objects of network entity B includes peer layer calls and non-peer layer calls; the peer layer call refers to the SOP or FOP of network entity A scheduling the SOP or FOP resources corresponding to network entity B; the non-peer layer call refers to the SOP of network entity A scheduling the FOP resources of network entity B or the FOP of network entity A scheduling the ROM resources of network entity B.

[0035] Furthermore, the present invention also provides a third-party service authorization and guarantee credit granting method based on the above object-oriented network business support system:

[0036] When an entity needs to initiate a service / business authorization request that O-ORCH cannot decide on its own, the object orchestration and scheduling entity sends the service / business authorization request to the network virtual entity management entity; when the network virtual entity management entity cannot decide on its own, it sends a credit query to a trusted third party, and the trusted third party returns the query result based on its credit information;

[0037] The network virtual entity management determines whether to authorize according to the query result and sends the result to the object orchestration and scheduling entity. The object orchestration and scheduling network element issues instructions on whether to permit services / businesses to each functional layer according to the judgment result.

[0038] In summary, the present invention includes at least one of the following beneficial effects:

[0039] 1. The network system provided by the present invention abstracts network components, including resources, protocol layers, devices, network elements, etc., to form operations of different forms of different service objects such as network Object (resource object, function object, service object, object creation and destruction according to resource type and scenario application requirements), network encapsulation (programmable slices, network programming APIs), object inheritance and aggregation (extension of object attributes and methods through inheritance), polymorphism (autonomous domain objects (space-air-ground, private network, etc.), physical world, digital world, biological consciousness world), etc., providing a basis for each function of the flexible network.

[0040] 2. An object-oriented network service support system provided by the present invention supports a multi-level object service call mode between objects across entities, exemplifies the communication between UE and network, UE and UE, and network element and network element as the communication between objects, constructs a communication object binary group for both sides of the communication (e.g., UE1 object <---> UE2 object), and is divided into peer-to-peer communication and non-peer-to-peer communication based on the call level, realizing flexible resource management, scheduling, and service collaboration.

[0041] 3. The network system provided by the present invention has a bypassable network design, which can adapt to the network hierarchy changes in business scenarios, including the scenario adaptability changes of the protocol stack system, that is, a dynamically variable protocol stack structure, and some protocol layers can be bypassed (such as the RLC layer bypass technology). Through the dynamic perception of service types, the network protocol system adaptively adjusts or the network negotiates with the terminal to adjust, constructing a flexible and adaptive network architecture.

[0042] 4. The present invention designs a multi-faceted integrated wireless protocol stack, which includes a control plane, a user plane, and an information plane. Due to the need for concurrent service processing, the network supports multi-plane aggregation processing, that is, the control plane process, the user plane process, and the information plane process are pipelined and concurrent. When the control plane process reaches a certain node, the user plane process can start. The information plane process and the user plane process are aggregated at an appropriate node, and this aggregation point is at the upper layer of the functional protocol layer, that is, it can be aggregated to the user plane of the logic layer for unified service layer docking processing according to service needs. If there is no aggregation need, the user plane and the information plane are processed independently, further strengthening the management and scheduling of flexible resources.

[0043] 5. The present invention also provides a service call guarantee credit granting system architecture between services and objects. By introducing a third-party or public credit granting center, it supports the security permission for cross-entity object service calls and can also support the credit granting permission for user services. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] Figure 1 It is the overall network architecture of the present invention;

[0046] Figure 2 It is the overall framework of business collaboration of the network support system of the present invention;

[0047] Figure 3 It is an example of the network autonomous domain deployment architecture;

[0048] Figure 4 It is the network logical entity architecture;

[0049] Figure 5 It is the mapping ratio relationship diagram between network components;

[0050] Figure 6 It is the function and architecture of the SOP service object encapsulation layer;

[0051] Figure 7 It is the control process of the QoS policy of the SOP control plane in the service encapsulation layer;

[0052] Figure 8 It is the processing process of the service data flow of the SOP user plane in the service encapsulation layer;

[0053] Figure 9 It is the business type decomposition diagram of the QoS profile;

[0054] Figure 10 It is the definition of the perceived QoS profile object;

[0055] Figure 11 It is the definition of the computing power QoS profile object;

[0056] Figure 12 It is the definition of the digital twin QoS profile object;

[0057] Figure 13 It is the definition of the AI QoS profile object;

[0058] Figure 14 Functional Protocol Layer FOP Framework Structure;

[0059] Figure 15 Functional Protocol Layer FOP Control Plane Protocol Stack;

[0060] Figure 16 Functional Protocol Layer FOP User Plane Protocol Stack;

[0061] Figure 17 Functional Protocol Layer FOP Information Plane Protocol Stack;

[0062] Figure 18 Functional Protocol Layer FOP Channel Structure Diagram;

[0063] Figure 19 Example of AI-Assisted Functional Protocol Layer FOP Physical Sublayer Signal Processing Process;

[0064] Figure 20 Functional Protocol Layer FOP Downlink Protocol Stack Architecture;

[0065] Figure 21 Functional Protocol Layer FOP Uplink Protocol Stack Architecture;

[0066] Figure 22 Bypassable Protocol Stack Architecture – Downlink;

[0067] Figure 23 Bypassable Protocol Stack Architecture – Uplink;

[0068] Figure 24 Example of RLC Bypass Process;

[0069] Figure 25 DL MAC PDU Example;

[0070] Figure 26 UL MAC PDU Example;

[0071] Figure 27 ROM Resource Object Modeling Layer Framework Structure;

[0072] Figure 28 Resource Object Collaboration Relationship;

[0073] Figure 29 ROM Three-Side Collaboration Framework Process;

[0074] Figure 30 Object Orchestration and Scheduling O-ORCH Network Function Framework;

[0075] Figure 31 Schematic of O-ORCH Functional Modules and Their Collaboration Process with SOP / FOP / ROM;

[0076] Figure 32 N-VEM function framework;

[0077] Figure 33 Overall processing flow of services such as communication perception and intelligent computing;

[0078] Figure 34 Peer-layer object call service process (A.SOP - B.SOP);

[0079] Figure 35 Cross-layer object call service process (A.SOP calls B.FOP layer object);

[0080] Figure 36 Cross-layer object call service process (A.FOP calls B.ROM layer object);

[0081] Figure 37 Service security credit framework process;

[0082] Figure 38 Example of AI service processing flow. Detailed implementation manners

[0083] The present invention will be further described in detail below with reference to the accompanying drawings.

[0084] Embodiment 1:

[0085] The invention provides an object-oriented network service support system, and its network architecture is as Figure 1 shown, including a service encapsulation layer SOP, a function protocol layer FOP, a resource modeling layer ROM, an object orchestration and scheduling O-ORCH, and a network virtual entity management N-VEM. The service processing framework of this network framework is as Figure 2 shown.

[0086] This network architecture is applied to one or more autonomous domains. There are multiple entities / network entities in each autonomous domain. An example of the deployment of the network autonomous domain is as Figure 3 shown. Figure 4 , 5 shown, which is the network logical entity architecture within the autonomous domain, the interaction interfaces adopted among each functional layer, functional unit and entity, and the mapping ratio among network components. The interaction interfaces include:

[0087] Vm: Interface between operation and maintenance and management, the global data center node N-VEM and the network nodes it manages / serves;

[0088] Vo: Interface between the object orchestration and scheduling functional entity O-ORCH and the functional protocol layer entity FOP and service encapsulation layer entity SOP nodes it controls;

[0089] Hn: Interface between the SOP control plane entity in the service encapsulation layer and the user plane function entity;

[0090] Vx: Interface between the FOP and SOP units;

[0091] Uu: Radio air interface;

[0092] Nx: Interface between the SOP in the service encapsulation layer and the service node.

[0093] Service Encapsulation Layer SOP:

[0094] The Service Encapsulation Layer SOP has multiple functional units, including the Authentication Server Function Module AUSF, the Access and Mobility Management Function Module AMF, the Network Service Exposure Function Module NEF, the Network Repository Function Module NRF, the Network Slice Admission Control Function Module NSACF, the Network Slice Authentication and Authorization Function Module NSSAAF, the Network Slice Selection Module NSSF (Network Slice Selection Function), the Policy Control Function Module PCF, the Session Management Function Module SMF, the Non-Seamless WLAN Offloading Function NSWOF Module, the Edge Application Service Discovery Function Module EASDF, the Object Service Capability Management Module OSCM, the User Plane Function Module UPF, and the Data Analysis Function Module DAF.

[0095] The participation of each functional unit in the SOP service encapsulation layer functions and architecture is as Figure 6 shown, and the names and functions of each functional unit are as follows:

[0096] Authentication Server Function (AUSF) Authentication Server Function:

[0097] Verify the UE for the requester network function;

[0098] Provide key material to the requester network function;

[0099] Protect the list of guidance information for the requester network function.

[0100] Access and Mobility Management Function (AMF) Access and Mobility Management Function:

[0101] Registration, connection, reachability, and mobility management;

[0102] Provide a session management message transmission channel for the UE and SMF;

[0103] Provide authentication and authorization functions when the user accesses;

[0104] Access point for the terminal and the core network control plane of the radio.

[0105] Network Exposure Function (NEF): Network Service Exposure Function

[0106] Store information in the NDR and retrieve relevant information from the NDR as well;

[0107] Provide corresponding security guarantees to ensure the security of external applications accessing the 6G network;

[0108] Conversion of relevant information inside and outside 6G;

[0109] Retrieve relevant information of other network elements.

[0110] Network Repository Function (NRF): Network Storage Function

[0111] Service discovery function;

[0112] Maintain the characteristics of available network element instances and the service capabilities they support;

[0113] Store the characteristic parameters of network elements.

[0114] Network Slice Admission Control Function (NSACF):

[0115] Monitor and control the number of registered UEs on each network slice;

[0116] Monitor and control the number of PDU sessions established on each network slice;

[0117] Event-based network slice status notification and report to the consumer network function.

[0118] Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF):

[0119] Authentication and authorization for specific network slices

[0120] Network Slice Selection Function (NSSF):

[0121] Determine the network slice instances that the UE is allowed to access based on the UE's slice selection assistance information, subscription information, etc.;

[0122] Determine the allowed NSSAI and map it to the subscribed S-NSSAI if necessary;

[0123] Determine the configured NSSAI and, if necessary, map it to the subscribed S-NSSAI;

[0124] Determine the set of AMFs for serving the UE.

[0125] Policy Control Function (PCF):

[0126] Support a unified policy framework and manage network behavior;

[0127] Provide policy rules to network entities;

[0128] Access the subscription information of the unified data repository (UDR).

[0129] Session Management Function (SMF):

[0130] Session management: responsible for tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement;

[0131] Control in QoS, charging data collection, roaming, etc.;

[0132] Lawful interception;

[0133] Downlink data notification.

[0134] Non-Seamless WLAN Offload Function (NSWOF):

[0135] Authentication of NSWO;

[0136] Edge Application Server Discovery Function (EASDF);

[0137] Process DNS messages according to the instructions of the SMF, including exchanging DNS messages with the UE; forward DNS messages to C-DNS or L-DNS for DNS queries, etc.

[0138] Object Service Capabilty Management (OSCM):

[0139] Object service capability configuration, query, and maintenance.

[0140] User Plane Function (UPF):

[0141] Anchor point for intra-RAT mobility

[0142] Data packet routing, forwarding, monitoring, and QoS processing

[0143] Traffic statistics and reporting

[0144] Data Analytics Function (DAF) data analysis function:

[0145] Responsible for collecting and analyzing data, and providing the generated analysis results for users

[0146] Based on the above functional units, the control plane of the Service Encapsulation Layer (SOP) can perform real-time control of service data flows to support various application services and manage user registration, authentication, and mobility; the user plane can perform service data flow transmission processing; and the information plane provides necessary auxiliary information for the control plane and the user plane

[0147] Among them, the control plane of the Service Encapsulation Layer (SOP) provides network service programmable APIs and exists as an interface layer. It is divided into internal and external API interfaces. The internal API is mainly used for network programmable control and service authorization management. Externally, it mainly provides external API interface services for service users, including user registration, authentication, mobility management, QoS policy control, PDU session management, etc. Its control process for QoS policies is as Figure 7 shown, and a specific control example is given:

[0148] 1. The APP provides the service requirements of the application layer to the PCF. The service requirements of the application layer include flow description information for service data flow detection, QoS-related requirements, such as bandwidth requirements, service types, etc

[0149] 2. The PCF formulates PCC rules based on the information collected from various channels such as the SMF, AMF, NWDAF, UDR, etc., and the pre-configured information on the PCF

[0150] 3. The PCF sends the PCC rules to the SMF, where the PCC rules are at the service data flow (SDF) level

[0151] 4. The SMF determines appropriate QoS flows based on the received PCC rules, the SMF's own configuration information, UE subscription information obtained from the UDM, etc., to transmit the service data flows corresponding to the PCC rules

[0152] Step 5. The SMF determines the following information for each QoS flow:

[0153] (1) QoS profile, sent to the base station for mapping of QoS Flow to DRB

[0154] (2) QoS rule, which is sent to the UE for use and is mainly used for the mapping of uplink data SDF to QoS Flow.

[0155] (3) PDR packet detection rule, which is mainly used for the mapping of downlink data SDF to QoS Flow, and for further detection and control of uplink data on the network

[0156] side.

[0157] (4) QoS enforcement rule, which is sent to the UPF for traffic control and threshold control on the data plane.

[0158] The service encapsulation layer SOP user plane is used for the transmission and processing of user service data flows, including data packet routing, forwarding, monitoring, and QoS processing, traffic statistics, and reporting, etc. Its service data flow processing process is as Figure 8 shown:

[0159] When processing downlink data:

[0160] 1. The UPF matches the downlink data according to the packet detection rule PDR received from the SMF, completes the mapping of SDF to QoS flow, and discards the data packet if the match fails.

[0161] 2. The UPF adds the QoS flow identifier QFI to the matched data packet header according to the corresponding QoS enforcement rule.

[0162] 3. The UPF performs bitrate control and threshold control on the downlink data packet according to the corresponding QoS enforcement rule.

[0163] When processing uplink data:

[0164] 1. The UE matches the data packet to be sent with the flow description information of the QoS rule, thereby determining the QoS flow to which the service data belongs according to the matched QoS rule, and completing the mapping of SDF to QoS Flow. If the match fails, the data packet is discarded.

[0165] 2. The UE adds the QoS flow identifier QFI to the matched data packet header according to the QoS rule.

[0166] 3. The UE performs bitrate control on the uplink data packet according to the QoS rule

[0167] 4. The UPF uses the PDR packet detection rule received from the SMF to verify the received uplink data, verify whether the uplink data carries the correct QFI, and perform bitrate control on the received uplink data packet.

[0168] The SOP information plane of the service encapsulation layer is used to provide necessary information assistance for the control plane and the user plane. It mainly performs the mapping of the auxiliary service data flow (SDF) to the QoS Flow, PDU session management, and determines the QoSProfile, PDR (Packet Detection Rule), QoS Rule, etc. It includes:

[0169] The QoS status information used

[0170] The candidate QoS configuration status information

[0171] The requirement information of the service flow data

[0172] The information plane transmits information to the control plane and the user plane. This information can be used by the control plane as a reference for QoS policy control, and by the user plane as a reference for mapping the service data flow to the QoS flow and bit rate control, etc. Taking the implementation of the QoS control policy in the control plane as an example:

[0173] 1. The DAF module in the information plane reports the QoS status, subsequent QoS configuration status, SDF requirement information, etc. to the PCF module in the control plane

[0174] 2. The PCF module comprehensively generates PCC rules based on the information received from the information plane and the application layer service requirement information

[0175] 3. Based on the generated PCC rules, it guides the SMF to determine the corresponding QoS control rules.

[0176] Based on the above functions of each layer, the SOP of the service encapsulation layer can decompose the QoS profile according to different service types according to the QoS requirements. For example Figure 9 As shown, each QoS profile can be combined into a hybrid QoS profile to support hybrid service types, such as the QoS profile for communication perception services, the QoS profile for intelligent computing services, the QoS profile for communication perception and intelligent computing services, etc. In addition to paying attention to network efficiency and network value as a whole, it can also keep a high cohesion and low coupling relationship in each business field.

[0177] Each type of service has its specific QoS profile definition. Taking some service models as examples, such as Figures 10 - 13 As shown:

[0178] The perception service model pays attention to perception ability indicators such as accuracy and resolution in the perception field according to its characteristics. In some scenarios, the requirement for real-time performance is not high, and it can be divided into two categories: target positioning and environmental detection. Among them:

[0179] Target location perception focuses on the state changes of specific targets. Common QoS profile metrics include:

[0180] (1) Detection performance: measured by false alarms, missed alarms, and detection probability;

[0181] (2) Accuracy: commonly using absolute deviation or mean-square error (MSE)

[0182] (3) Resolution: often characterized by the ambiguity function to depict the trade-off between system parameters and range and velocity resolutions.

[0183] Environmental detection perception focuses on the overall information of the surrounding environment rather than individual targets, and the perception results are often richer information such as images. Common QoS profile metrics include:

[0184] (1) Spatial resolution, including three dimensions: range resolution, azimuth resolution, and elevation resolution.

[0185] (2) Sidelobe performance: in radar imaging, the total energy of a single pixel should come from a single spatially resolved unit.

[0186] (3) Image entropy: describes the average amount of information in an image. The entropy value indicates the focusing of each point in the image, thereby characterizing the image quality; (4) Perception range: describes the distance of the coverage area under the premise of specifying the perception performance.

[0187] (5) Perception probability: describes the reliability of the specified perception.

[0188] The computing power service model focuses on computing power metrics such as operation speed and cache size in its computing field and requires efficient utilization of computing power. The definition of its computing power QoS profile object is as Figure 11 shown, including computing resource utilization rate, operation speed, cache size, throughput, CPU utilization rate, MIPS, and computing response time, etc.

[0189] The QoS profile object definition of the digital twin service model is as Figure 12 shown, which can be divided into three categories: network parameters, user perception, and object status. Specifically:

[0190] Network parameters include the delay, throughput, connection success rate, coverage rate, packet loss rate, handover success rate, delay jitter, and acceptable bit error rate of each network unit;

[0191] User perception includes user experience model parameters (timeliness, session quality, accessibility, maintainability, integrity, content quality, ease of use), the five senses of users (hearing, vision, touch, smell, taste), emotional model parameters (joy, trust, fear, surprise, sadness, disgust, anger, and expectation), etc.;

[0192] User / object status knowledge includes human vital sign model parameters (heart rate, pulse, blood pressure, respiration, pain, blood oxygen, pupil, and corneal reflex), 3D object model parameters, etc.

[0193] The AI service QoS of the AI business model refers to the quality indicators in aspects such as the performance, availability, and security provided by the AI service, including inference speed, energy consumption, computing security, data privacy, model controllability, etc. Its QoS profile object definition is as Figure 13 shown, divided into AI models and AI data. The indicators of AI models include inference accuracy, training or inference latency, training or inference data density, and training or inference energy efficiency; the AI data indicators include data integrity, data redundancy, data timeliness, and data distribution.

[0194] Function protocol layer FOP:

[0195] The control plane of the function protocol layer FOP is used for the configuration and control between objects, the user plane is used for the transmission and bearing of the user service information flow, and the information plane is used to provide necessary auxiliary information for the control plane and the user plane. The framework structure of the function protocol layer FOP is as Figure 14 shown, and the protocol stacks of each plane are as Figures 15 - 17 shown.

[0196] The function protocol layer FOP includes the L1 physical sublayer PHY, the L2 link sublayer, and the L3 logical sublayer. Among them, the L1 physical sublayer PHY is used for multiple access, providing physical channels, modulation and demodulation, channel encoding and decoding, physical layer processes, physical layer measurements, and anti-interference processing. As Figure 18 shown, the physical channels include dynamic variable physical dedicated channels PxDCH (x: UL / DL / SL), physical broadcast channel PBCH, physical random access channel PRACH, physical shared channels PxSCH (x: UL / DL / SL), and physical control channels PxCCH (x: UL / DL / SL).

[0197] Among them, PxDCH is a variable self-contained dedicated physical channel used for the exclusive transmission of resources for services or UEs, and can carry multi-mode information such as the AI signal processing wireless transmission mode and the delay deterministic and reliability-sensitive wireless transmission mode at the same time.

[0198] PxDCH is a self - contained physical channel that simultaneously transmits control information CCE (Control Channel Element), demodulation reference signal DMRS, and model / data information. The CCE carries information such as the distribution change information of DMRS (Demodulation Reference Signal), the change information of data PRB / RE resources, and MCS adjustment. If the relevant information does not change, the CCE only carries the "no update indication" information. PxDCH is a physical channel with variable structure, which can adapt to the requirements of transmission scenarios such as ULBC (ultra - reliable low - latency broadband communication) and mULC (massive ultra - reliable low - latency communication) through the dynamic matching of the channel structure and the wireless transmission mode.

[0199] The PxDCH channel supports wireless resource partitioned transmission for wireless transmission mode differentiation: For the signal processing of the AI mode, PxDCH can carry AI / neural network model update information or neuron information for assisting data signal processing, and this information is transmitted simultaneously with the data signal in PxDCH. In the case of more than one wireless transmission mode <CCE, RS, AI model (optional) / data> combination, the channel adopts a wireless resource partitioned channel structure according to different wireless transmission mode combinations; in the {<CCE, RSx, AI model>; <CCE, RSy, data>} combination, if the AI model information exists, this part can adopt a different MCS coding and modulation scheme from the data part according to the requirements of reliability guarantee. The <CCE, RSx, AI model> and <CCE, RSy, data> transmitted in PxDCH have independent wireless resource partitions and their respective CCE configurations, RS time - frequency resource density configurations, and the AI model and data have different MCS coding and modulation schemes.

[0200] For the wireless transmission mode <CCE, RS, data> that is sensitive to delay determinacy and reliability, PxDCH can enable DSSS spread - spectrum signal processing, and its corresponding DMRS demodulation reference signal can dynamically support high - density time - frequency resource configuration.

[0201] The physical shared channel PxSCH is used for the channel - shared transmission of multi - service and multi - UE data.

[0202] For a certain service, one or two combined channels of PxSCH and PxDCH can be used for the wireless transmission of service data.

[0203] The enabling rules for the PxDCH dedicated physical channel are as follows:

[0204] Step1: Based on the QoS profile of the QoS flow in the logical sublayer and the service data transmission status monitoring information, determine the logical priority and map it to the LCID;

[0205] Step2: The link sublayer determines the link priority according to the LCID priority (UL / DL / SL) and the link monitoring information, and maps it to the corresponding transport channel TCID;

[0206] Step3: The physical sublayer determines the corresponding physical channel according to the TCID selected by the link sublayer, based on the mapping relationship between the TCID and the physical channel. The TCIDs in the specified range are mapped to the PxDCH dedicated physical channel for data transmission.

[0207] During service processing, the built-in intelligent agent AI Agent and the intelligent engine AI Engine of the ROM in the physical sublayer can achieve auxiliary processing based on their functions and service requirements. The specific process is as Figure 19 shown. The intelligent engine AI Engine of the ROM can obtain the corresponding AI inference model through training. When the FOP physical sublayer processes services, it extracts the relevant data and computing requirements of the AI / god network, sends this data to the training module of the intelligent engine AI Engine for training, and sends the new AI inference model to the inference module. The FOP physical sublayer sends the data and parameters to be processed to the inference module of the intelligent engine AI Engine to obtain the result, and returns it to the FOP physical sublayer for subsequent processing. The above method can be regarded as a manifestation form of object invocation between entities. The FOP physical sublayer realizes the relevant computing services of the AI / neural network by invoking the resource of the intelligent engine AI Engine module in the ROM layer, assisting the processing speed and accuracy of the digital signal processing algorithm in the physical sublayer.

[0208] The L2 link sublayer includes the media access control sublayer MAC, which is used for segmentation and recombination of service data units SDUs, realization of the mapping between logical channels and transport channels, multiplexing and demultiplexing of several logical channel SDUs and one transport block TB, user equipment scheduling, resource allocation, link adaptation, power control, HARQ error correction, logical channel priority sorting and processing, and user equipment data priority processing.

[0209] The L3 logical sublayer includes the Radio Resource Control (RRC) sublayer for wireless control, the Service Data Adaptation (SDA) sublayer, the Packet Data Convergence Protocol (PDCP) sublayer, and the Radio Link Control (RLC) sublayer. The control plane of the L3 logical sublayer is responsible for the signaling process functions of the UE's radio configuration. The user plane is responsible for the mapping of service data and QoS, the mapping of QoS and data radio bearers or signaling radio bearers (DRB / SRB), the control and transmission of service data flows, deterministic transmission control, unified packet processing of network control signaling and user data, and data interaction with the L2 link sublayer through logical channels. The logical sublayer calculates a corresponding logical sublayer priority score through priority weighted scoring based on each dimension of the service QoS Profile and the QoS flow transmission status information. This logical sublayer priority score is mapped to a corresponding LCID value. The logical channel ID (LCID) is used as the input information for the link sublayer to determine the scheduling priority.

[0210] The Service Data Adaptator (SDA) sublayer includes the following two functional units:

[0211] Time Sensitive Controller (TSC): It has a time-sensitive control function. By monitoring the QoS flow transmission status and its QoS Profile in real time, it determines the logical sublayer priority of the service for mapping with the LCID, and further the link layer uses it to determine the service scheduling priority. Thus, it provides low-latency, low-jitter, and highly reliable communication services for service data transmission. Through the TSC time-sensitive control of the logical sublayer, combined with the real-time guarantee of wireless scheduling in the link sublayer and the low-latency frame structure waveform design in the physical sublayer, a three-dimensional and fully endogenous low-latency and jitter deterministic support system is formed.

[0212] QoS Flow handling (QFH): It realizes the mapping between QoS Flow and DRB and marks the QoS Flow ID of UL and DL data packets.

[0213] The functional entities / instances of the Functional Protocol Layer FOP (including UL / DL / SL, etc.) mainly process services through interfaces such as QoS flow, Radio Bearer (DRB), RLC Channel, and Logical Channel (QoS specific). The data plane data is aggregated at the logical layer or provides auxiliary information for scheduling decisions at the link layer according to actual needs. In protocol processing, it is distinguished based on the logical channel ID and type. Taking positioning awareness as an example, UE-specific positioning is mapped to the UE-level LCID. Public positioning information is mapped to the public LCID. UE group shared positioning information is mapped to the UE group LCID. As an example, the uplink and downlink protocol stack architecture of the Functional Protocol Layer FOP is as Figure 20 , 21 shown.

[0214] Under the network system of this embodiment, it is possible to realize the function object call of heterogeneous entities / networks. For example, the service object of network element A calls the function object of network element B. For the AI service case, the AI service object of network element A can call the Sidelink AI entity / instance object of B through its DL functional protocol layer to provide functional protocol layer services for others.

[0215] During the business data transmission process of the Functional Protocol Layer FOP, one or more sub-layers of PDCP, RLC, and MAC or some functional units of SDA can be bypassed based on the dynamic requirements of the QoS of the business data, as Figure 22 , 23 shown. Based on the business requirements, the RLC sub-layer of the FOP layer is bypassed in the uplink and downlink processes.

[0216] Taking the bypass of the RLC sub-layer as an example, the specific bypass process is as Figure 24 shown. The UPF functional unit of the SOP service encapsulation layer notifies the service data adaptation sub-layer SDA in the logical sub-layer of the FOP functional protocol layer of the service flow type indication and transmission status information. Its TSC functional unit triggers the delay-sensitive Qos Flow monitoring and control mechanism according to the business requirements, and formulates the Qos Flow that needs to bypass the protocol layer and the sub-layers to be bypassed. At this time, the bypass effective time of the protocol layer can be notified to the UE through the RRC message or MAC CE according to the pre-set communication mechanism.

[0217] When the RRC message notification is selected, the SDA triggers the configuration of the UE protocol layer bypass and returns it to the RRC. The RRC notifies the UE of the protocol layer bypass activation timing through the RRC message according to the configuration. At the same time, the SDA conveys the protocol layer bypass trigger indication to the PDCP. The PDCP indicates that the RLC is bypassed and exchanges relevant logical channel information with the RLC. After the PDCP takes over the logical channel, it directly processes the MAC data.

[0218] When the MAC CE notification is selected, the SDA first conveys the protocol layer bypass trigger indication to the PDCP. The PDCP indicates that the RLC is bypassed and exchanges relevant logical channel information with the RLC. After the PDCP takes over the logical channel, it interfaces with the MAC, and the MAC notifies the UE of the protocol layer bypass activation timing through the MAC CE.

[0219] After the bypass mechanism is triggered, the DL PDU is directly transmitted from the PDCP to the MAC, and a MAC header is added to indicate the protocol layer that the data packet needs to bypass. After being sent to the UE through the MAC PDU, the UE parses the MAC header, bypasses the RLC and delivers the PDU to the PDCP for PDU UL processing, and the process is the same as that of the PDU DL.

[0220] It should be noted that as Figure 25 、 26 shown, in the case where the RLC is bypassed, the MAC needs to take over its data packet segmentation and reassembly functions, and the same MAC PDU can accommodate bypassed PDUs (such as PDCP PDUs) or non-bypassed PDUs (such as RLC PDUs).

[0221] Resource Modeling Layer ROM:

[0222] The Resource Modeling Layer ROM includes a control plane, an execution plane, and an information plane. The control plane is used for the real-time control of resource objects and is responsible for resource model creation and management; the execution plane is the carrier of signal processing, as an execution object entity, to perform specific service operations, such as computing processing (CPU / DSP / ASIC HWA / GPU, etc. performing computing tasks), signal channels (including signal or data transmission carriers such as fronthaul, midhaul, and backhaul), data storage (temporary storage such as TCM, disk / Flash / array storage of data, etc.), AI model inference (AI models, inference / training execution based on AI hardware platforms), perception detection (association and cooperation based on sensor computing bodies, wireless spectra, etc. to perform environmental (including electromagnetic environment) perception detection), etc.; the information plane is used to monitor the status of resource objects, etc., to assist the control plane and the execution plane in dynamic adjustment.

[0223] As Figure 27As shown in the figure, the resource modeling layer ROM functional unit includes the RMOM functional unit responsible for the management and maintenance of resource model objects, the RORM functional unit responsible for the establishment, association, modification and maintenance of resource object relationships, the ROSCH functional unit responsible for the real-time scheduling of resource objects, the resource object router RORU, and the OSMON functional unit responsible for monitoring the status of resource objects.

[0224] The ROSCH functional unit schedules each resource in the resource modeling layer ROM based on business requirements, and exchanges object status with O-ORCH through the control plane via the service encapsulation layer FOP to update the information of each object in O-ORCH, realizing the scheduling of various resources in the service model, channel model and computing model. The cooperation relationships of each resource object are as Figure 28 shown, and the scheduling process is as Figure 29 shown.

[0225] The control plane RMOM performs initial object creation management and creates an object relationship network, then pushes the object relationships to the execution plane and the information plane, and at the same time sends the object information to O-ORCH via FOP for update. Based on business requirements, O-ORCH sends object orchestration and scheduling instructions to FOP, and FOP conveys them layer by layer to ROM. ROSCH performs internal object scheduling of ROM, reports service objects to FOP through the control plane, and FOP assists in the object call cooperation of the ROM control plane. RORU is the resource object router in ROM, and the information plane reports object status information to the control plane through OSMON.

[0226] Object Orchestration and Scheduling O-ORCH:

[0227] The object orchestration and scheduling O-ORCH regularly updates the service status reported by multiple network entity service encapsulation layers SOP (the service status of each object in each layer). Multiple network entities within an autonomous domain share one object orchestration and scheduling O-ORCH. The object orchestration and scheduling O-ORCH performs object management and scheduling on one or more network entities according to business / service requirements; the object orchestration and scheduling O-ORCH refers to the orderly arrangement and organization of the service encapsulation layer SOP, the functional protocol layer FOP, and the resource modeling layer ROM under the drive of business requirements. Through the scheduling and control of object orchestration and scheduling, a network service that can meet business requirements is finally formed. O-ORCH realizes the decoupling of business and logical networks, and logical networks and physical networks through abstraction. Users define business requirements through the abstract language provided by object orchestration, and object orchestration automatically constructs the user's logical network according to the business definition. Through object orchestration and scheduling, the complexity of the network can be effectively shielded from users, and the time for service design and deployment can be reduced.

[0228] Figure 30 and 31respectively show the end-to-end network orchestration instantiation process of object orchestration and scheduling O-ORCH and the collaboration process with each functional layer. After receiving the deployed service request, object orchestration and scheduling decompose it according to the type requirements of the service to each layer, and mobilize and coordinate various related sub-service objects, functional objects, and resource object managers to perform service object orchestration and instantiation for each sub-layer. The openness achieved through the API interface in the object management orchestration entity O-ORCH decouples the user entry, end-to-end cross-layer orchestration and service management, and the underlying network and infrastructure.

[0229] Network Virtual / Entity Management (N-VEM):

[0230] Network Virtual / Entity Management (N-VEM) undertakes the function of network element node management in the network, including the management of physical network elements and virtual network element nodes. The physical network elements are user equipment (UE) and network device nodes, and the virtual network element nodes are digital twins based on physical network elements. Multiple autonomous domains share one Network Virtual / Entity Management (N-VEM).

[0231] As Figure 32 shown, Network Virtual / Entity Management (N-VEM) includes an Unstructured Data Storage Function Module (UDSF), a UE Radio Management Function (UCMF), a Charging Function Module (CHF), a Unified Data Management (UDM) Module, and a Message Framework Adapter Function Module (MFAF).

[0232] The specific functions of each module are as follows:

[0233] Unstructured Data Storage Function (UDSF): Stores specific unstructured data, such as session IDs used by AMF and SMF, status data, etc.

[0234] Unified Data Repository (UDR). Unified data repository function;

[0235] UDM stores and retrieves subscription data;

[0236] PCF stores and retrieves policy data, storage and retrieval of structured services;

[0237] Application data of NEF (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs)

[0238] UEradio Capability Management Function (UCMF): The UE radio management function is used to store field entries corresponding to UE radio function IDs assigned by the PLMN or the manufacturer. Equipment Identity Register (EIR): The device identity registration device.

[0239] CHarging Function (CHF): Responsible for accurately calculating and allocating the costs of various services and resources used by users.

[0240] Data Collection Coordination Function (DCCF): Used to coordinate data collected from one or more NFs according to data collection requests from one or more consumer NFs.

[0241] Network Node Management (NNM): Used to manage network nodes.

[0242] Digital Twin Network Management (DTNM): Used to manage digital twin network nodes.

[0243] Unified Data Management (UDM): Generation of 6G AKA authentication credentials, user identity processing (such as storage and management of the SUPI of each user in the 5G system), support for unhiding privacy-protected user identifiers (SUCI), access authentication based on subscription data (such as roaming restrictions), NF registration management for UE services (for example, storing the serving AMF for the UE and the serving SMF for the UE PDU session), support for service / session continuity (by maintaining the ongoing session allocation of the SMF / DNN), MT-SMS delivery support, lawful interception function (especially in the case of outbound roaming, where the UDM is the only contact point for LI), subscription management, SMS management;

[0244] Messaging Framework Adaptor Function (MFAF): The service interacts with the messaging framework.

[0245] Based on the object-oriented network service support system provided above, Figure 33 A general processing flow for services such as communication sensing and intelligent computing is given. After the connections between all levels, modules, and units within the support system are established and activated, the UE and the DN establish a service connection. After the object scheduling and command within each functional layer are realized by the O-ORCH, the data flow is transmitted between layers.

[0246] The system provided in this embodiment adopts an object - oriented network design, integrating the concepts of service - enablement and programmability into all levels of network design, enabling full decoupling and flexible allocation of software and hardware resources. This design not only enhances the flexibility of the network, reduces the cost of network upgrading, but also provides a "plug - and - play" base network interface for various emerging application scenarios and vertical industries, greatly improving the adaptability and scalability of the network.

[0247] Embodiment 2:

[0248] The present invention also provides a support method for an object - oriented network service support system as described above, including network entity A and network entity B existing in the same autonomous domain. For a certain function layer (SOP or FOP) of entity A that processes a certain service, its service requirements and the service - processing capabilities of each function layer of entity A are processed, and it is determined that a service support for initiating a specific function - layer call to other entities is required and a request is sent to the object orchestration and scheduling O - ORCH.

[0249] After receiving the service support request, the object orchestration and scheduling performs object allocation and scheduling judgment according to the updated service states of entity A and B, and returns the allocation result to entity A.

[0250] After receiving the object allocation and scheduling judgment, entity A updates and stores the capabilities of each function layer of entity B, and at the same time sends a request for a specific function - layer call to entity B; after receiving the scheduling request from entity A, the specific function layer of entity B returns a call confirmation message to entity A and establishes a service - function connection with entity A, thus completing the service support for the specific function - layer call.

[0251] The ways for network entity A to schedule the function layer of network entity B include peer - layer call and non - peer - layer call; peer - layer call means that the SOP or FOP of network entity A schedules the corresponding SOP or FOP resources of network entity B; non - peer - layer call means that the SOP of network entity A schedules the FOP resources of network entity B or the FOP of network entity A schedules the ROM resources of network entity B. Figure 34 The service process of peer - layer call is given, Figure 35 、 36 The service process of non - peer - layer call is shown.

[0252] The peer - layer and non - peer - layer calls initiated for the above - mentioned service support satisfy certain rule conditions, where:

[0253] For service calls between peer - layers, the basic principles include:

[0254] 1. Between network element entities A and B, service rules and service scopes are negotiated through peer - layer communication.

[0255] 2. For each peer layer, including the resource modeling layer, the functional protocol layer, and the service encapsulation layer, service calls can be negotiated between the peer layers of entities A and B.

[0256] 3. For service calls between each peer layer, services can be provided layer by layer for service calls, or the network element entity can be used as a whole for unified service calls. In this case, when entity A calls an object of B, it does not care how B provides services internally, but only needs to make a service request. A does not need to care about how B processes the service request.

[0257] The basic principles of service calls for non-peer layers include:

[0258] (1) Between network element entities A and B, through non-peer layer communication (communication between objects), service rules and service scopes are negotiated.

[0259] (2) Service calls provided by the lower layer for the higher layer can be negotiated between the non-peer layers of entities A and B.

[0260] (3) For service calls between each peer layer, services can be provided layer by layer for service calls, or the network element entity can be used as a whole for unified service calls. In this case, when entity A calls an object of B, it does not care how B provides services internally, but only needs to make a service request. A does not need to care about how B processes the service request.

[0261] The support for multi-level object service call modes between different entities instantiates the communication between UE and network, UE and UE, and network element and network element into communication between objects. The two communication parties construct a communication object binary tuple (e.g., UE1 object <---> UE2 object). Based on the call hierarchy, it is divided into peer layer communication and non-peer layer communication, realizing flexible resource management and scheduling.

[0262] Embodiment 3:

[0263] In the existing 5G network services, there is no such mechanism as credit granting. It is statically pre-configured in advance by the management end, and users need to complete the entire service activation process when opening a service. This embodiment proposes a dynamic credit granting mechanism, that is, real-time activation of user services or real-time authorization of object calls.

[0264] A method for third-party service authorization and guarantee credit granting based on the above object-oriented network service support system, as Figure 37 shown, the specific method is:

[0265] When an entity needs to initiate a service / business authorization request that O-ORCH cannot decide on its own, the object orchestration and scheduling entity sends the service / business authorization request to the network virtual entity management entity; when the network virtual entity management entity cannot decide on its own, it sends a credit query to a trusted third party, and the trusted third party returns the query result based on its credit information; the network virtual entity management determines whether to authorize based on the query result, and sends the result to the object orchestration and scheduling entity, and the object orchestration and scheduling network element enables services / businesses at each functional layer based on the judgment result.

[0266] The service authorization and guarantee credit mechanism in this embodiment is applicable to: the opening of new user services, the management and permission of object calls between heterogeneous entities. The security engine is not only a computing resource, but also includes the role of a credible third party, which is used for security guarantees by a credible third party when a terminal UE and a base station XNB or a core network element cannot pass the authentication process such as security authentication. Through the security guarantee mechanism, the UE can quickly access or the UE can quickly authenticate the network. When the UE needs to enable a new function or improve the QoS service level, and the network fails to open the corresponding service license for the UE in time, the UE can be temporarily admitted through the credible security guarantee mechanism. The so-called third-party guarantee mechanism requires the use of blockchain and AI big models, and the network nodes or external third parties with this capability guarantee the UE (or its service slice) or network element.

[0267] The security parameters on the UE side include user credit score or level, root key, etc.

[0268] The third-party service authorization and guarantee credit granting method provided in this embodiment has the ability to perceive and intervene in associated security and network layer risks:

[0269] The network needs to comprehensively monitor changes in the security status of all terminal devices in the network, predict in advance which terminals are facing security risks, the level of security protection mechanisms that may need to be enabled, and the impact on the business collaboration of the entire network, and then start the backup business nodes in advance.

[0270] In addition, the security situation information of the UE terminal can be disseminated in whole or in part within or outside the autonomous domain as needed, so that the devices in the network can take proactive security precautions.

[0271] Embodiment 4:

[0272] This embodiment provides an example of an AI business / service processing flow based on an endogenous intelligent agent AI Agent or an intelligent engine AI Engine. The AI Agent and the AI Engine collaborate through object calls at each layer to support AI-type businesses / services. The AI Engine is divided into two parts: training and inference. The training part is not responsible for object management and creation. The function of providing object services to the upper layer is the responsibility of the ROM inference part, and object creation is the responsibility of the inference AI Engine for creation and maintenance.

[0273] As Figure 38 shown, the service encapsulation layer SOP endogenous intelligent agent AI Agent initiates an object call. The function protocol layer FOP makes an object call to the ROM intelligent engine AI Engine in the resource layer based on AI business / service requirements, realizes the functions of model modeling and AI calculation, and sends the results to the function protocol layer FOP to form the AI business data processing results, which are returned to the function protocol layer FOP to complete the business / service process.

[0274] The above are all preferred embodiments of the present invention. The protection scope of the present invention is not limited by this. Therefore, all equivalent changes made according to the structure, shape, and principle of the present invention should be covered within the protection scope of the present invention.

Claims

1. An object-oriented network business support system, characterized in that: include: Service encapsulation layer SOP, functional protocol layer FOP, resource modeling layer ROM, object orchestration and scheduling O-ORCH, network virtual entity management N-VEM; The service object encapsulation layer SOP includes the control plane, user plane and information plane. The control plane is based on the service object to achieve real-time control of service data flow to support various application services and the management of user registration, authentication and mobility. The user plane implements service data flow transmission and processing based on service objects; the information plane provides necessary auxiliary information for the control plane and user plane based on service objects; The functional object protocol layer FOP includes the control plane, user plane and information plane; the control plane is based on functional objects to realize the configuration and control between objects; the user plane is based on functional objects to realize the transmission and bearing of user service information flow; the information plane is based on functional objects to provide necessary auxiliary information for the control plane and user plane; The resource object modeling layer ROM includes the control plane, execution plane and information plane. The control plane is based on resource objects, realizes real-time control of resource objects and is responsible for resource model creation and management. The execution plane is based on resource objects, undertakes the carrier of signal processing, and performs specific business operations as the execution object entity. The information plane is based on resource objects, realizes monitoring the status of resource objects, and assists the control plane and execution plane in dynamic adjustment. Object orchestration and scheduling O-ORCH regularly updates the service status reported by the service encapsulation layer SOP of multiple network entities (the service status of each object at each layer). Multiple network entities in an autonomous domain share one object orchestration and scheduling O-ORCH. Object orchestration and scheduling O-ORCH manages and schedules objects for one or more network entities according to business / service requirements. The network virtual / physical management N-VEM is responsible for the management of network element nodes in the network, including the management of physical network elements and virtual network element nodes. The physical network elements are user equipment UE and network device nodes, and the virtual network element nodes are digital twins based on physical network elements. Multiple autonomous domains share one network virtual / physical management N-VEM.

2. The object-oriented network business support system according to claim 1, characterized in that: The service encapsulation layer SOP includes an authentication server function module AUSF, an access and mobility management function module AMF, a network service presentation function module NEF, a network storage function module NRF, a network slice admission control function module NSACF, a network slice identity authentication and authorization function module NSSAAF, a network slice selection module NSSF (Network Slice Selection Function), a policy control function module PCF, a session management function module SMF, a non-seamless WLAN offload function NSWOF module, an edge application service discovery function module EASDF, an object service capability management module OSCM, a user plane function module UPF and a data analysis function module DAF.

3. The object-oriented network business support system according to claim 1, characterized in that: The functional protocol layer FOP includes L1 physical sublayer PHY is used to use the resource objects (radio resources, AI model resources) provided by the resource object modeling layer to perform multiple access, provide physical channels, modulation and demodulation, channel encoding and decoding, physical layer processes, physical layer measurements and anti-interference processing; L2 link sublayer, including the media access control sublayer MAC, is used for segmentation and reassembly of service data units SDUs, mapping of logical channels to transport channels, multiplexing and demultiplexing of several logical channel SDUs and a transport block TB, user equipment scheduling, resource allocation, link adaptation and power control, HARQ error correction, logical channel priority sorting and processing, and user equipment data priority processing; L3 logical sublayer, including radio resource control sublayer RRC, service data adaptation sublayer SDA, packet data convergence protocol sublayer PDCP and radio link control sublayer RLC; The L3 logical sublayer control plane is responsible for the signaling process function of the UE's wireless configuration; the user plane is responsible for the mapping of service data and QoS, the mapping of QoS and data radio bearer or signaling radio bearer DRB / SRB, service data flow control and transmission, deterministic transmission control, unified packet processing of network control signaling and user data, and interaction with the L2 link sublayer.

4. The object-oriented network business support system according to claim 3, characterized in that: During the service data transmission process, the functional protocol layer FOP can dynamically bypass one or more sublayers in PDCP, RLC and MAC or bypass some functional units of SDA based on the QoS requirements of the service data.

5. The object-oriented network business support system according to claim 3, characterized in that: The physical channels of the functional protocol layer FOP include dynamically variable physical dedicated channels PxDCH (x: UL / DL / SL), physical broadcast channels PBCH, physical random access channels PRACH, physical shared channels PxSCH (x: UL / DL / SL), and physical control channels PxCCH (x: UL / DL / SL).

6. The object-oriented network business support system according to claim 5, characterized in that: The variable physical dedicated channel PxDCH is a self-contained dedicated physical channel with a variable structure, which is used for resource-exclusive transmission of services or UEs; the variable physical dedicated channel PxDCH simultaneously transmits control information CCE, demodulation reference signal DMRS, and model / data information.

7. An object-oriented network business support system according to claim 1, characterized in that: The resource modeling layer ROM includes the RMOM functional unit responsible for the management and maintenance of resource model objects, the RORM functional unit responsible for the establishment, association, modification and maintenance of resource object relationships, the ROSCH functional unit responsible for real-time scheduling of resource objects, the resource object routing RORU and the OSMON functional unit responsible for resource object status monitoring.

8. The object-oriented network business support system according to claim 7, characterized in that: The ROSCH functional unit implements internal object scheduling of the control plane, execution plane and information plane based on the object orchestration and scheduling instructions of O-ORCH.

9. The object-oriented network business support system according to claim 1, characterized in that: The object orchestration and scheduling O-ORCH includes an object service authorization management OSAU module that manages the configuration related to the external service license of the object; an object allocation and recovery OARE module that allocates and recovers objects at each layer of the entity according to the object status and service demand information; and an object status management OSM module that is responsible for the collection, update and recording of object status and capability information.

10. The object-oriented network business support system according to claim 1, characterized in that: The network virtual / entity management N-VEM includes an unstructured data storage function module UDSF, a UE wireless management function UCMF, a billing function module CHF, a unified data management function UDM module, a message framework adapter function module MFAF, and a digital virtual / twin network management DVNM.

11. The object-oriented network business support system according to claim 1, characterized in that: The service object encapsulation layer SOP, functional object protocol layer FOP, object orchestration and scheduling O-ORCH and network virtual / entity management N-VEM are all equipped with endogenous intelligent body AI Agent, which is responsible for the process and logic control of AI business and its own network intelligence; the resource object modeling layer ROM is equipped with an intelligent engine AI Engine, which is responsible for providing AI model resources and reasoning / training computing resources; the endogenous intelligent body AI Agent and the intelligent engine AI Engine collaborate through object calls at each layer to support AI type business / services.

12. A business support method based on the object-oriented network business support system according to claims 1-11, characterized in that: It includes network entity A and network entity B existing in the same autonomous domain, the service requirements of a certain functional layer (SOP or FOP) of entity A that processes a certain service and the service processing capabilities of each functional layer of entity A, determines the service support that needs to initiate a specific functional layer call to other entities and initiates the request to the object orchestration and scheduling module O-ORCH; After receiving the business support request, the object orchestration and scheduling makes object allocation and scheduling decisions based on the updated service status of entities A and B, and returns the allocation result to entity A; After receiving the object allocation and scheduling decision, entity A updates and stores the capabilities of each functional layer of entity B, and at the same time initiates a request to call a specific functional layer to entity B; after receiving the scheduling request from entity A, the specific functional layer of entity B returns the call confirmation information to entity A and establishes a service function connection with entity A, thereby completing the business support for the specific functional layer call.

13. The business support method according to claim 12, characterized in that: The way in which network entity A schedules the functional layer objects of network entity B includes peer layer calls and non-peer layer calls; the peer layer call refers to the SOP or FOP of network entity A scheduling the SOP or FOP resources corresponding to network entity B; the non-peer layer call refers to the SOP of network entity A scheduling the FOP resources of network entity B or the FOP of network entity A scheduling the ROM resources of network entity B.

14. A third-party service authorization and guarantee credit granting method based on the object-oriented network business support system of claims 1-11, characterized in that: When an entity needs to initiate a service / business authorization request that O-ORCH cannot decide on its own, the object orchestration and scheduling entity sends the service / business authorization request to the network virtual entity management entity; when the network virtual entity management entity cannot decide on its own, it sends a credit query to a trusted third party, and the trusted third party returns the query result based on its credit information; The network virtual entity management determines whether to authorize based on the query results and sends the results to the object orchestration and scheduling entity. The object orchestration and scheduling network element issues instructions to each functional layer on whether to allow the service / business based on the judgment results.

Images