Collaborative request processing method, communication network element and communication system

Abstract

The invention provides a collaborative request processing method, a communication network element and a communication system, and relates to the technical field of 6G communication. The collaboration request processing method comprises the following steps: receiving a collaboration request from user equipment, wherein the collaboration request comprises a data service request and a connection service request; determining a connection service management function network element and a data service management function network element according to the cooperation request; a first request is sent to the service management function network element, a second request is sent to the data service management function network element, the first request comprises the connection service request, and the second request comprises the data service request. The embodiment of the invention can support the core network to process cooperation requests including connection, perception, AI service and the like.

Description

Background Art

[0002] Traditional network services mainly focus on connection services, that is, providing users with network access and data transmission functions. However, in new 6G business scenarios such as perception and AI, users often need to obtain diversified perception / AI data services such as data collection, data analysis, and AI reasoning on the basis of connection services. Therefore, how to support the coordinated processing of connection, perception, and AI services has become an urgent problem to be solved in existing networks.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The purpose of the present disclosure is to provide a collaborative request processing method, a communication network element and a communication system to solve the problem of collaborative request processing in a 6G network architecture.

[0005] According to a first aspect of an embodiment of the present disclosure, a collaborative request processing method is provided, which is executed by an access and mobility management function network element, including: receiving a collaborative request from a user equipment, the collaborative request including a data service request and a connection service request; determining a connection service management function network element and a data service management function network element according to the collaborative request; sending a first request to the service management function network element, and sending a second request to the data service management function network element, the first request including the connection service request, and the second request including the data service request.

[0006] According to the second aspect of an embodiment of the present disclosure, a collaborative request processing method is provided, which is executed by a connection service management function network element, including: receiving a collaborative request from an access and mobility management function network element; extracting a connection service request in the collaborative request; and establishing a network connection for a user device according to the connection service request.

[0007] According to the third aspect of an embodiment of the present disclosure, a collaborative request processing method is provided, which is executed by a data service management function network element, including: receiving a collaborative request from an access and mobility management function network element; extracting a data service request in the collaborative request; and selecting a data service execution node to execute a data service task according to the data service request.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a communication network element is provided, including: a first collaborative request receiving module, configured to receive a collaborative request from a user device, the collaborative request including a data service request and a connection service request; a collaborative request matching module, configured to determine a connection service management function network element and a data service management function network element according to the collaborative request; a request sending module, configured to send a first request to the service management function network element, and send a second request to the data service management function network element, the first request including the connection service request, and the second request including the data service request.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication network element is provided, including: a second collaborative request receiving module, configured to receive a collaborative request from an access and mobility management function network element; a connection service request extraction module, configured to extract the connection service request in the collaborative request; and a network connection establishment module, configured to establish a network connection for a user device according to the connection service request.

[0010] According to the sixth aspect of an embodiment of the present disclosure, a communication network element is provided, including: a third collaborative request receiving module, configured to receive a collaborative request from an access and mobility management function network element; a data service request extraction module, configured to extract the data service request in the collaborative request; and a data service request execution module, configured to select a data service execution node to execute a data service task according to the data service request.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a communication system is provided, including: an access and mobility management function network element, used to execute the collaborative request processing method as described in any one of the above items; a connection service management function network element, used to execute the collaborative request processing method as described above; and a data service management function network element, used to execute the collaborative request processing method as described above.

[0012] According to an eighth aspect of the present disclosure, there is provided an electronic device, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute any one of the methods described above based on instructions stored in the memory.

[0013] According to a ninth aspect of the present disclosure, there is provided a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the collaborative request processing method as described in any one of the above items is implemented.

[0014] According to a ninth aspect of the present disclosure, a computer program product is provided, comprising a computer program, which implements the steps of any of the above methods when executed by a processor.

[0015] The disclosed embodiment receives collaborative requests including data service requests such as connection service requests, perception service requests and AI service requests sent by user equipment (UE), and selects appropriate network function entities (such as CSMF and DSMF) to process these requests respectively, thereby supporting the core network to simultaneously process multi-factor collaborative requests for connection + perception + AI services initiated by UE, thereby realizing collaborative processing of multi-factor services by the core network.

[0016] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0018] Figure 1A and Figure 1B It is a schematic diagram of the architecture of a communication system to which an embodiment of the present disclosure is applied.

[0019] Figure 2 is a flowchart of a collaborative request processing method performed by eAMF in an exemplary embodiment of the present disclosure.

[0020] Figure 3 It is a functional diagram of a network element in the communication system 100 in the exemplary embodiment of the present disclosure during processing of a collaborative request.

[0021] Figure 4 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0022] Figure 5 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0023] Figure 6 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0024] Figure 7 is a flowchart of a collaborative service processing method executed by a CSMF in an exemplary embodiment of the present disclosure.

[0025] Figure 8 is a flowchart of a collaborative service processing method executed by DSMF in an exemplary embodiment of the present disclosure.

[0026] Fig. 9 It is a flowchart of a collaborative request processing method executed by a UE according to an embodiment of the present disclosure.

[0027] Fig.10 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0028] Fig.11 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0029] Fig.12 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0030] Fig.13 is a block diagram of a communication network element in an exemplary embodiment of the present disclosure Fig.14 is a block diagram of an electronic device in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0032] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0033] In addition, the accompanying drawings are only schematic diagrams of the present disclosure, and the same reference numerals and texts (including Chinese and English) in the drawings represent the same or similar parts, so their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities, which do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0034] The exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0035] Figure 1Aand Figure 1B It is a schematic diagram of the architecture of a communication system to which an embodiment of the present disclosure is applied.

[0036] refer to Figure 1A , the communication system 100 is a 6G network system that supports data services and can be expressed in the form of a service-oriented interface.

[0037] From the perspective of the service-oriented interface architecture of the core network, the communication system 100 includes a data bus and a control bus.

[0038] The data bus is used to transmit information related to data processing and service management between various network functional entities. For example, the data bus can transmit collected data, intermediate processing data, or final data service results related to AI and perception, including structured data with topological information, gradient data of AI models, inference data, and other large data volumes, thereby separating data transmission aggregation from business logic and improving data exchange efficiency.

[0039] The control bus is used to transmit control signaling and management information between various network function entities.

[0040] The network function entities mainly involved in the communication system 100 include: SEF (Service Exposure Function): It is used to open up 6G network services to the outside world, securely open network capabilities and services to third-party applications or other network functions, and provide a unified interface and security mechanism so that external entities can access 6G network services.

[0041] AF (Application Function): Mainly responsible for application layer related functions, interacting with network functions, and providing business requirements to the network side, such as business requests related to policy control.

[0042] eNRF (Evolved Network Repository Function): used to store network-related data and configuration information, provide data retrieval and storage services for other network elements, and support the normal operation of network functions. In the embodiments of the present disclosure, it is used to provide data service function registration, update and subscription services, and can be called a registration center.

[0043] Control plane NF (Control-plane Network Function): refers to various network functions of the control plane, responsible for processing control plane related services such as signaling, session management, and mobility management.

[0044] eAMF (Evolved Access and Mobility Management Function): mainly responsible for access control, mobility management, session management and other functions, ensuring that the user equipment (UE) can correctly access the network and maintain connection during mobility, also referred to as eAMF. In the embodiment of the present disclosure, eAMF is used to execute the collaborative request processing method 200.

[0045] CSMF (Connection Service Management Function): responsible for managing connection-related services, including operations such as establishment, maintenance, and release of a connection between a UE and a data network DN. In the embodiment of the present disclosure, the CSMF is used to execute the collaborative request processing method 700 .

[0046] DSMF (Data Service Management Function): Mainly manages data services, including registration, discovery, authorization and other operations of data services. In the disclosed embodiment, DSMF is used to execute the collaborative request processing method 800, and selects specific DPF, DSF and other NFs with different data capabilities according to the data service request to form an executable UE, RAN, DPF, DSF logical topology, and control the work chain to implement specific data service functions. DSMF also supports the data service capability reporting function of DPF.

[0047] DSF (Data Storage Function) network element: used to store data, provide data storage and retrieval services for the network, and can store user data, business data, etc. In the disclosed embodiment, DSF is a data service execution node that stores collected data and data service results, etc., to meet the storage requirements of new data such as perception, AI, and data with undefined structures.

[0048] DPF (Data Plane Function) network element: mainly responsible for the forwarding and processing of user plane data, such as data packet routing, QoS guarantee, etc. In the disclosed embodiment, DPF is a data service execution node, which can realize data collection, transmission, preprocessing, analysis and other functions, support perception data processing, AI model training and reasoning, and thus support extensive and diverse data collection and processing capabilities.

[0049] UE (User Equipment): User equipment used by users, such as mobile phones, tablet computers, etc., is the initiator and receiver of communication. In the embodiment of the present disclosure, it is the initiator of the collaborative request, has collaborative request generation function and collaborative request sending function, and is used to execute the collaborative request processing method 900.

[0050] (R)AN (Radio) Access Network: also referred to as RAN, is responsible for providing services such as wireless access control and data transmission for UEs in a specific area. In the embodiments of the present disclosure, (R)AN can serve as the task executor of the perception task, supporting wireless perception of a specific area or target and obtaining perception measurement data.

[0051] UPF (User Plane Function): Mainly responsible for forwarding and processing user plane data, including encapsulation, decapsulation, and routing of data packets.

[0052] DN (Data Network): The external network that the user ultimately wants to access, such as the Internet.

[0053] Among them, the control plane NF, eNRF, SEF, AF, eAMF, CSMF, DSMF, DSF, and DPF are connected through their respective corresponding first interfaces (such as Figure 1A As shown) such as Nnf, Nnrf, Nsef, Naf, NeAMF, Nsmf, etc. are connected to the control bus to realize control signaling and management information transmission between each other.

[0054] At the same time, the control planes NF, eNRF, SEF, AF, eAMF, CSMF, DSMF, DSF, and DPF are connected through their respective corresponding second interfaces (such as Figure 1A as shown) are connected to the data bus to achieve data transmission between them.

[0055] In addition, the UE is connected to the eAMF through the N1 interface to implement functions such as access control and mobility management to transmit collaborative requests and receive processing results of collaborative requests.

[0056] (R)AN is connected to the eAMF through the N2 interface and to the UPF through the N3 interface. It is responsible for connecting the UE to the network and transmitting data.

[0057] UPF is connected to CSMF through the N4 interface to receive connection service management from CSMF; it is connected to DN through the N6 interface to realize forwarding of user plane data to the data network, and can be connected to other UPFs through the N9 interface (for scenarios such as data forwarding).

[0058] As a data service execution node, DPF is connected to (R)AN and can obtain and process the perception data collected by (R)AN.

[0059] refer to Figure 1B , the communication system 100 can also be expressed as a point-to-point interface.

[0060] exist Figure 1B Performance in Figure 1A The functions of the network functional entities shown in the figure include: UE, RAN, UPF, DPF, and DSF can all serve as data service execution nodes. Data service tasks may include: Data collection (DC): Obtaining data from data sources, including user data, network data, AI data, perception data, etc.

[0061] Data Storage (DS): stores collected data and data service results, etc.

[0062] Data Processing (DP): data preprocessing, analysis, etc.

[0063] Among them, UE, RAN, UPF, DPF and DSF all have DC function, DPF has DP function, and DSF has DS function.

[0064] exist Figure 1B Performance in Figure 1A The connections shown in the table include: AF calls network services such as CSMF and DSMF through SEF to meet business needs such as connection and data services.

[0065] The eAFM is connected to the CSMF and the DSMF to send a first request to the CSMF and a second request to the DSMF according to the coordination request received from the UE.

[0066] DSMF is connected to RAN, DPF, and DSF to select data service execution nodes, namely UE, RAN, DPF, and DSF, according to the second request. Among them, RAN, as a data service execution node, is connected to DSMF in addition to eAMF and DPF to receive perception tasks from DSMF and collect data.

[0067] DPF is connected to DSF for data exchange. DPF can read data from DSF or store data to DSF.

[0068] In addition, Figure 1AThe eNRF appears as a registration center, which can provide the capability registration, query, and subscription functions of multiple network function entities; the control plane NF can provide other control functions. Since it is not the main improvement object of the collaborative request processing in the embodiment of the present disclosure, it will not be described in detail here.

[0069] In the disclosed embodiment, in addition to being responsible for UE access and mobility management related signaling, the eAMF also enhances the collaborative processing capability of multi-factor collaborative requests such as data services and connection services for data services. Specifically, the eAMF executes the collaborative request processing method 200, receives a collaborative request from the UE, selects the CSMF and the DSMF according to the collaborative request, and sends a first request and a second request to the CSMF and the DSMF, respectively.

[0070] CSMF receives the first request from eAMF, identifies the connection service request therein, and controls the establishment, modification, and release of the connection from UE to the data network DN. In some embodiments, the first request is a connection service request extracted by eAMF from the collaborative request; in other embodiments, the first request is a collaborative request, and CSMF parses the collaborative request and extracts the connection service request. For details, please see the subsequent embodiments.

[0071] DSMF receives the second request from eAMF, identifies the data service request therein, selects specific NFs with different data capabilities such as DPF and DSF, forms an executable UE, RAN, DPF, and DSF logical topology, and controls the work chain to implement specific data service functions. DSMF also supports the data service capability reporting function of DPF. In some embodiments, the second request is a data service request extracted by eAMF from the collaborative request; in other embodiments, the second request is a collaborative request, and DSMF parses the collaborative request and extracts the data service request. For details, please see the subsequent embodiments.

[0072] By enhancing the functions of UE, eAMF, DSMF, and CSMF, the communication system 100 can support the simultaneous processing of multi-factor collaborative requests for connection + perception + AI services initiated by the UE, and realize collaborative processing of multi-factor services in the core network.

[0073] Figure 2 is a flowchart of a collaborative request processing method performed by eAMF in an exemplary embodiment of the present disclosure.

[0074] refer to Figure 2 The collaborative request processing method 200 is executed by the functionally enhanced eAMF having collaborative request parsing capability, and may include: Step S21, receiving a collaboration request from a user equipment, wherein the collaboration request includes a data service request and a connection service request; Step S22, determining a connection service management function network element and a data service management function network element according to the collaboration request; Step S23: Send a first request to the service management function network element, and send a second request to the data service management function network element, wherein the first request includes the connection service request, and the second request includes the data service request.

[0075] The disclosed embodiment receives collaborative requests including data service requests such as connection service requests, perception service requests and AI service requests sent by user equipment (UE), and selects appropriate network function entities (such as CSMF and DSMF) to process these requests respectively, thereby supporting the core network to simultaneously process multi-factor collaborative requests for connection + perception + AI services initiated by UE, thereby realizing collaborative processing of multi-factor services by the core network.

[0076] Next, each step of the collaborative request processing method 200 is described in detail.

[0077] In step S1, a cooperation request is received from a user equipment, where the cooperation request includes a data service request and a connection service request.

[0078] A collaborative request may be a request initiated when a user simultaneously requests a connection service, data services such as a perception service, and an AI service. A collaborative request is not a number of independent requests sent separately, but a request containing multiple information. A collaborative request is used to request the core network to provide the UE with connection services and data-related services such as perception services and AI services, including a connection service request and a data service request, wherein the connection service request is a PDU session establishment request for the UE, and the data service request may include types such as a perception service request and an AI service request.

[0079] Exemplarily, the format of the data service request includes, for example: business type, data service demander type, data service demander identifier, data service application type, data service application identifier, data service indication information, etc.

[0080] Taking data service requests including perception service requests as an example, data service requests can carry business types (such as high-precision positioning, imaging mapping, drone flight supervision, environmental monitoring, etc.), business requirements (such as perception mode, perception area, perception QoS requirements, perception data update frequency, etc.), as well as perception-related parameters, such as perception accuracy, perception distance, perception speed range, perception service quality (QoS) requirements, etc.

[0081] Taking data service requests including AI service requests as an example, data service requests can carry business types (such as image recognition, speech recognition, natural language processing, intelligent prediction, personalized recommendation, reasoning tasks, etc.), business requirements (such as model accuracy requirements, response time, amount of data processed, service call frequency, etc.), required computing power resource types (such as CPU, GPU, storage, etc.), specific QoS requirements of AI tasks (such as training accuracy, etc.), and AI-related parameters, such as data set type, model parameters, model preset thresholds, training accuracy requirements, etc.

[0082] The above description of the content of the collaborative request is only an example. In some embodiments of the present disclosure, in addition to the connection service request and the data service request, the collaborative request may also include other types of service requests; or include the connection service request and other types of service requests; or include the data service request and other types of service requests. Those skilled in the art can set the types and quantities of service requests included in the collaborative request according to actual needs. As long as the service request includes different types of service requests, it belongs to the collaborative request referred to in the embodiments of the present disclosure.

[0083] In an exemplary embodiment, the eAMF obtains a coordination request through a NAS message from the UE, that is, the UE sends an uplink NAS message to the eAMF to simultaneously request a connection service and a data service, and the data service includes but is not limited to a perception service and an AI service. NAS (Non-Access Stratum) messages refer to messages used in mobile communication systems to transmit signaling information unrelated to the access layer between user equipment (UE) and core network control plane entities (such as eAMF, etc.), mainly involving mobility management, session management, security management and other functions.

[0084] In some embodiments, the eAMF can obtain the coordination request through the PCO field in the NAS message from the UE. The PCO field (Packet Core Network-Connected Optimisation) is a field in the NAS message that is used to carry information related to packet core network connection optimization. By setting the coordination request in the PCO field, specific coordination service related information can be flexibly transmitted without changing the existing NA message body structure, thereby improving the efficiency and pertinence of information transmission and facilitating the core network to quickly identify and process the UE's coordination service requirements.

[0085] In other embodiments, the eAMF may obtain the collaborative request through a newly added dedicated multi-factor collaborative request NAS message from the UE. By adding a new NAS message to achieve the transmission of collaborative requests, a dedicated and standardized transmission channel can be provided for collaborative requests, reducing interference with other business messages, and more clearly and accurately expressing the multi-factor requirements of collaborative services, facilitating efficient analysis and processing by the core network, and improving the response speed and service quality of collaborative services.

[0086] In step S2, a connection service management function network element and a data service management function network element are determined according to the collaboration request.

[0087] In the embodiments of the present disclosure, multiple DSMFs with different capabilities and multiple CSMFs with different connection management capabilities and resource configurations may be deployed in the network.

[0088] In some embodiments, the eAMF may identify a coordination request from the UE according to a preset method, and determine the CSMF and DSMF corresponding to the coordination request according to the service area corresponding to the coordination request.

[0089] When obtaining a collaborative request through a NAS message, the information of the service area corresponding to the collaborative request can be obtained from the relevant fields in the NAS message (such as the extended field containing location information, the specific service area identification field); it can also be obtained from the positioning information reported by the UE (if the NAS message is associated with UE positioning related content); it can also be derived based on the tracking area (TA, Tracking Area) information currently registered by the UE combined with the network configuration.

[0090] In some embodiments, a special field may be defined in the collaborative request to define the service area corresponding to the collaborative request.

[0091] Whether defining the service area in a NAS message or defining a dedicated field in a collaborative request to define the service area, the first service area corresponding to the connection service request and the second service area corresponding to the data service request can be defined separately.

[0092] The connection service request mainly focuses on the access and connection management of user equipment. The definition of its service area is usually related to factors such as network coverage and mobility management. For example, it can be divided according to the tracking area (TA). The purpose is to ensure that the user equipment can maintain a stable connection within a certain range and achieve seamless mobile switching.

[0093] Data service requests focus on meeting users' needs for data access and processing. The definition of the service area can be determined based on the source and distribution of the data and the needs of business applications. For example, for a specific IoT application, the data service area may be the range of all sensor devices in an industrial park, so as to obtain and process the data in the area in a targeted manner.

[0094] Therefore, defining service areas for unconnected service requests and data service requests respectively can enable more accurate allocation and utilization of network resources, better meet the needs of different types of services, and improve service quality and user experience.

[0095] In addition to selecting the corresponding CSMF and DSMF for the collaborative request according to the service area, the CSMF and DSMF may also be selected according to the service type and the traffic load.

[0096] For example, when eAMF is responsible for extracting connection service requests and data service requests from collaborative requests, CSMF can be selected based on the complexity of the connection service requests (such as high mobility requirements, high reliability requirements, etc.) and specific requirements for session management. For connection service requests that require high reliability and low latency, CSMF with strong processing capabilities, abundant resources and a location closer to the access side in the network topology is given priority to quickly process tasks such as connection establishment and session management to ensure the quality of connection services.

[0097] For another example, you can select a DSMF based on the data size, type (such as AI or perception services), and processing requirements of the data service request. If the data service request is a real-time analysis task with a large amount of data, select a DSMF with powerful data storage and high-speed computing capabilities to efficiently process and store relevant data and meet the business requirements for data processing speed and accuracy. If the data service request is a perception service, select a DSMF that has registered perception service capabilities.

[0098] When the eAMF is not responsible for extracting the connection service request and the data service request in the collaborative request, the eAMF may also select the CSMF and DSMF according to the preset rules (such as information such as service type and business load) recorded in the specific fields in the NAS message and according to the data service capabilities of the pre-configured CSMF and DSMF. Alternatively, the eAMF may select the CSMF and DSMF according to the information recorded in the special fields defined in the collaborative request and according to the data service capabilities of the pre-configured CSMF and DSMF.

[0099] The specific field in the NAS message or the special field defined in the collaborative request can record a variety of information used to assist the eAMF in selecting the CSMF and DSMF. Those skilled in the art can configure according to actual conditions, and the present disclosure does not impose any special restrictions on this.

[0100] After determining the CSMF and DSMF corresponding to the collaborative service information, proceed to step S3.

[0101] In step S3, a first request is sent to the service management function network element, and a second request is sent to the data service management function network element, wherein the first request includes the connection service request, and the second request includes the data service request.

[0102] CSMF establishes the PDU session of the UE according to the first request; DSMF selects the data service execution node according to the second request to execute the data service request. eAMF can cooperate with CSMF to establish a network connection of the user equipment; receive the data service execution result from DSMF, and send the data service execution result to the user equipment.

[0103] Figure 3 It is a functional diagram of a network element in the communication system 100 in the exemplary embodiment of the present disclosure during processing of a collaborative request.

[0104] refer to Figure 3 , at event 301, the UE initiates a connection, perception and AI coordination request to the core network eAMF. Among them, the UE can send a connection, perception and AI service coordination request to the eAMF through an enhanced NAS message.

[0105] At event 302, the eAMF, CSMF, and DSMF participate in multi-factor collaborative request processing, wherein the enhanced eAMF may disassemble and translate the multi-factor collaborative request into separate connection service requests, perception service requests, and AI service requests (see Figure 4 and Figure 5 The embodiment shown in the figure), selects the appropriate CSMF and DSMF, and sends the corresponding request to the corresponding CSMF and DSMF. The eAMF can also select the appropriate CSMF and DSMF according to the collaborative request, and forward the multi-factor collaborative request to the selected CSMF and DSMF (see Figure 6 ).

[0106] Specifically, AFM sends a first request to CSMF and sends a second request to DSMF.

[0107] At event 303, the CSMF controls the establishment of a PDU session connection from the UE to the network according to the first request.

[0108] At event 304, the DSMF identifies the data service requirement according to the second request, and selects a suitable data service execution node according to the data service requirement (eg, the requested service type, location area, etc.).

[0109] At event 305, the DSMF sends the specific perception / AI data service task to the selected data service execution node.

[0110] At event 306, the various data service execution nodes collaborate to perform the perception / AI task.

[0111] At event 307 , the data service execution node returns the data service task execution result to the UE.

[0112] The data service task execution result includes, for example, a storage address of the data service result, allowing the UE to access and obtain the data service result through the address.

[0113] In some embodiments, the first request is a connection service request, and the second request is a data service request, that is, the eAMF locally parses the collaborative request and extracts the connection service request and the data service request, and sends them to the selected CSMF and DSMF respectively. Step S3 may include: parsing the collaborative request to extract the connection service request and the data service request; sending the connection service request to the connection service management function network element; sending the data service request to the data service management function network element.

[0114] In these embodiments, the eAMF may first parse the collaborative request and extract the connection service request and the data service request, and then determine the appropriate CSMF and DSMF; or it may first select the appropriate CSMF and DSMF, and then parse the collaborative request and extract the connection service request and the data service request.

[0115] In some embodiments, the eAMF may parse the collaborative request to extract a connection service request and two or more types of data service requests, where the two or more types of data service requests include at least one of an AI service request and a perception service request. That is, a collaborative request may include multiple different types of data service requests, and the eAMF may extract different data service requests separately.

[0116] In some embodiments, two or more types of data service requests correspond to at least one data service management function network element, and sending the data service request to the data service management function network element includes: sending two or more types of data service requests to their corresponding data service management function network elements respectively.

[0117] eAMF can determine the DSMF corresponding to each data service request (of course, the DSMF corresponding to each data service request can also be determined through the preset field in the NAS message or the collaborative service message before extraction), and send each data service request to its corresponding DSMF. For example, eAMF extracts one or more perception service requests and one or more AI service requests from the collaborative request, and determines the DSMF corresponding to each perception service request and each AI service request.

[0118] Figure 4 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0119] refer to Figure 4 ,eAMF is not only responsible for extracting data service requests from collaborative requests, but also for extracting different data service requests.

[0120] At event 401, the UE sends a NAS message to the eAMF to request connection service, perception service and AI data service at the same time. There are two options: implementation based on the PCO field of the PDU session NAS message and implementation based on the newly added dedicated multi-factor service request NAS message. The collaborative request carries connection, perception and AI data service requests at the same time, including a PDU session establishment request for connection service, as well as a data service request for perception service and a data service request for AI service. The collaborative request includes the requested AI data service business type (such as statistical analysis of registration or session, AI model training, AI reasoning, etc.), the requested data service area, the specific QoS requirements of the requested service and other information.

[0121] At event 402, the eAMF processes the multi-factor collaborative request, including extracting the fields related to connection, perception, and AI data service requests from the NAS message, and breaking it into independent connection service requests, perception service requests, and AI data service requests. The eAMF selects the appropriate CSMF and DSMF in the network based on the service area, etc.

[0122] At event 403, the eAMF sends a connection service request to the CSMF.

[0123] At event 404, the eAMF sends a perception and AI data service request to the DSMF. In this step, different perception service requests may correspond to the same or different DSMFs, different AI service requests may correspond to the same or different DSMFs, and perception service requests and AI service requests may correspond to the same or different DSMFs. To simplify the representation, DSMF is used in the figure.

[0124] At event 405, after receiving the connection service request message, the CSMF controls the establishment of a PDU session connection from the UE to the network.

[0125] In event 406, after receiving the perception, AI and other data service request messages, DSMF arranges and selects the appropriate data service execution node, namely UE\RAN\DPF\DSF, according to the perception / AI data service requirements (such as the requested service type, area, etc.) (in some embodiments, UE can also be used as a data service execution node, and the UE that executes the data service may be different from the UE that requests the service). Assuming that this data service request includes both an AI service request and a perception service request, DSMF selects the appropriate RAN, DSF and DPF to perform the perception task and AI task respectively. The basis for "appropriate" includes but is not limited to service area matching, load compliance, registered capability type compliance, etc.

[0126] At event 407, the DSMF sends the sensing task to the selected RAN.

[0127] At event 408, the DSMF sends AI-related tasks such as data analysis, processing or storage to the selected DPF and DSF respectively.

[0128] The process of DSMF issuing data service tasks includes interacting with each service execution node.

[0129] At event 409, RAN performs a sensing task and collects data.

[0130] At event 410, the RAN sends the collected data to the DPF.

[0131] At event 411, the DPF performs data analysis and processing and executes AI tasks (including AI model training or reasoning). The AI ​​tasks here may or may not utilize the perception data transmitted by the RAN. When utilizing the perception data transmitted by the RAN, the AI ​​tasks may be executed after receiving the perception data.

[0132] At event 412, the DPF sends the task execution result to the DSF.

[0133] At event 413, the DSF performs data storage.

[0134] At event 414, the DPF sends a message to the DSMF that the task execution result has been stored, including the storage address of the task execution result. The DSMF sends the storage address to the eAMF. The eAMF sends the storage address of the task execution result to the service requester UE via a downlink NAS message.

[0135] In some embodiments, the eAMF is only responsible for extracting the data service request from the collaborative request, and does not further split the data service request. However, if the data service request consists of multiple requests, the eAMF may still determine which DSFM or DSFMs to send the data service request to based on the information carried by the data service request, or the information carried by the collaborative request, or the information carried by the uplink NAS message sent by the UE. At this time, the data service request received by each DSFM is the same, and it is necessary to parse the data service request locally and identify the data service request for its own processing.

[0136] Figure 5 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0137] refer to Figure 5 At event 501, the UE sends a NAS message to the eAMF to request connection services, awareness services, and AI data services at the same time. Figure 3 The embodiment shown.

[0138] At event 502, the eAMF processes the multi-factor collaborative request. This includes extracting the connection, perception, and AI data service request related fields from the NAS message, and breaking them into independent connection service requests and data service requests, where the data service request may include two or more data service requests. The eAMF selects the appropriate CSMF in the network based on the service area, etc., and determines which DSFM or DSFMs to send the data service request to based on the information carried in the data service request, or the information carried in the collaborative request, or the information carried in the uplink NAS message sent by the UE.

[0139] At event 503, the eAMF sends a connection service request to the CSMF.

[0140] At event 504, the eAMF sends a data service request to the DSMF. In this step, there may be one or more DSMFs, and the data service request (i.e., data service request packet) received by each DSMF is the same. To simplify the representation, DSMF is used in the figure.

[0141] At event 505, after receiving the connection service request message, the CSMF controls the establishment of a PDU session connection from the UE to the network.

[0142] At event 506, after receiving the data service request message, the DSMF extracts the data service request executed by itself from the data service request.

[0143] At event 507, the DSMF selects a suitable data service execution node, ie, UE\RAN\DPF\DSF, according to the data service request to be executed by the DSMF. Assume that the RAN, DSF and DPF are selected this time.

[0144] At event 508, the DSMF issues a sensing task to the selected RAN.

[0145] At event 509, the DSMF sends AI-related tasks such as data analysis, processing or storage to the selected DPF and DSF respectively.

[0146] The process of DSMF issuing data service tasks includes interacting with each service execution node.

[0147] At event 510, the RAN performs a sensing task and performs data collection.

[0148] At event 511, the RAN sends the collected data to the DPF.

[0149] At event 512, the DPF performs data analysis and processing and executes AI tasks (including AI model training or reasoning). The AI ​​tasks here may or may not utilize the perception data transmitted by the RAN. When utilizing the perception data transmitted by the RAN, the AI ​​tasks may be executed after receiving the perception data.

[0150] At event 513, the DPF sends the task execution result to the DSF.

[0151] At event 514, the DSF performs data storage.

[0152] At event 515, the DPF sends a message to the DSMF that the task execution result has been stored, including the storage address of the task execution result. The DSMF sends the storage address to the eAMF. The eAMF sends the storage address of the task execution result to the service requester UE via a downlink NAS message.

[0153] By extracting the connection service request and data service request from the collaborative request by eAMF, distributing the data service request to DSMF, and having DSMF extract the data service request for execution locally, the load on eAMF can be reduced and the information processing efficiency of eAMF can be improved.

[0154] Furthermore, in order to further reduce the load of eAMF, the tasks of connection service requests and data service requests can be directly extracted from the collaborative request and distributed to specific CSFM and DSMF, so as to further improve the information processing efficiency of eAMF, realize distributed processing, and help achieve load balancing within the system.

[0155] In some other embodiments, the first request and the second request are both collaborative requests, that is, the eAMF forwards the collaborative request to the selected CSMF and DSMF. Step S3 may include: sending the collaborative request to the connection service management function network element so that the connection service management function network element extracts the connection service request from the collaborative request; sending the collaborative request to the data service management function network element so that the data service management function network element extracts the data service request from the collaborative request.

[0156] Figure 6 It is a process diagram of a collaborative request in an exemplary embodiment of the present disclosure.

[0157] refer to Figure 6 , eAMF is only responsible for forwarding the collaborative request to the selected CSMF and DSMF, and CSMF and DSMF extract the connection service request and data service request from the collaborative request.

[0158] At event 601, the UE sends a NAS message to the eAMF to request connection service, perception service and AI data service at the same time. There are two optional methods: implementation based on the PCO field of the PDU session NAS message and implementation based on the newly added dedicated multi-factor service request NAS message. It carries connection, perception and AI data service requests at the same time, for example, including a PDU session establishment request for connection service, and a data service request for perception and AI services, including the requested data service business type (such as registration or session statistical analysis, AI model training, AI reasoning, etc.), the requested data service area, the specific QoS requirements of the requested service, etc.

[0159] At event 602, the eAMF processes the multi-factor service request, parses the connection, perception and AI data service coordination request, and selects the appropriate CSMF and DSMF in the network based on the service area, etc.

[0160] At event 603, the eAMF sends a connection, perception and AI service collaboration request to the CSMF.

[0161] At event 604, the eAMF sends a connection, perception and AI service collaboration request to the DSMF.

[0162] In event 605, after receiving the connection, perception and AI service collaboration request message, CSMF extracts the relevant information of the connection service, that is, the connection service request.

[0163] At event 606, the CSMF controls the establishment of a PDU session connection from the UE to the network.

[0164] At event 607, after receiving the connection, perception and AI service collaboration request message, DSMF extracts the information related to perception and AI services, namely the data service request. DSMF selects the appropriate data service execution node, namely UE\RAN\DPF\DSF, based on the specific data service requirements contained in the data service request (such as the requested data service business type, area, etc.). Assuming that the data service request extracted this time includes both AI service requests and perception service requests, DSMF selects the appropriate RAN, DSF and DPF to perform perception tasks and AI tasks respectively. The basis for "appropriate" includes but is not limited to service area matching, load compliance, registered capability type compliance, etc.

[0165] At event 608, the DSMF issues a sensing task to the selected RAN.

[0166] At event 609, the DSMF sends AI-related tasks such as data analysis, processing or storage to the selected DPF and DSF respectively.

[0167] At event 610, the RAN performs a sensing task and collects data.

[0168] At event 611, the RAN sends the collected data to the DPF.

[0169] At event 612, the DPF performs data analysis and processing to execute AI tasks (AI model training or inference).

[0170] At event 613, the DPF sends the task execution result to the DSF.

[0171] At event 614, the DSF performs data storage.

[0172] At event 615, the DPF sends a message to the DSMF that the task execution result has been stored, including the storage address of the task execution result. The DSMF sends the storage address to the eAMF. The eAMF sends the storage address of the task execution result to the service requester UE via a downlink NAS message.

[0173] exist Figure 6 In the illustrated embodiment, the CSMF and the DSMF may extract the connection service request and the data service request from the collaborative request through preset rules. For example, the CSMF may extract the connection service request through a preset field related to the connection service in the collaborative request, or extract the relevant information of the connection service according to a preset keyword in the collaborative request. The DSMF may also extract the connection service request through a preset field related to the data service in the collaborative request, or extract the relevant information of the data service (such as the perception service, AI service) according to a preset keyword.

[0174] In the process of DSMF extracting data service requests from collaborative requests, if the data service requests include multiple data service requests corresponding to two or more DSMFs, DSMF can first extract the set of data service requests, then identify and extract the data service requests that match itself from the set of data service requests; or directly identify and extract the data service requests that match itself from the collaborative request. At this time, eAMF can simultaneously distribute the collaborative request to all CSMFs and all DSMFs involved in the collaborative request. Each CSMF and DSMF receives the same collaborative request and needs to extract the service request for which it is responsible locally.

[0175] By enhancing CSMF and DSMF, they are equipped with the ability to parse collaborative requests. The task of parsing collaborative requests can be distributed to CSMF and DSMF, thereby improving data processing efficiency and reducing eAMF load.

[0176] Based on this, the embodiments of the present disclosure provide a collaborative service processing method performed by CSMF and a collaborative service processing method performed by DSMF.

[0177] Figure 7 is a flowchart of a collaborative service processing method executed by a CSMF in an exemplary embodiment of the present disclosure.

[0178] refer to Figure 7 , the collaborative service processing method 700 may include: Step S71, receiving a coordination request from an access and mobility management function network element; Step S72, extracting the connection service request in the collaborative request; Step S73: Establishing a network connection of the user equipment according to the connection service request.

[0179] Method 700 is performed by a CSMF with enhanced functionality and the ability to parse collaborative requests. The CSMF can receive collaborative requests from the eAMF, parse the collaborative requests, and extract relevant information about the connection service, i.e., the connection service request. The PDU session connection from the UE to the network is established according to the connection service request. Please refer to the aforementioned embodiment for the detailed interaction process, which will not be repeated here.

[0180] Figure 8 is a flowchart of a collaborative service processing method executed by DSMF in an exemplary embodiment of the present disclosure.

[0181] refer to Figure 8 , the collaborative service processing method 800 may include: Step S81, receiving a coordination request from an access and mobility management function network element; Step S82, extracting the data service request in the collaborative request; Step S83: Select a data service execution node to execute the data service task according to the data service request.

[0182] Method 800 is executed by a DSMF with enhanced functionality and collaborative request parsing capability. DSMF can receive collaborative requests from eAMF, parse collaborative requests, and extract relevant information of data services (such as AI services, perception services), i.e., data service requests. According to the data service request, a suitable data service execution node is selected to perform the data service task. For the detailed interaction process, please refer to the aforementioned embodiment, which will not be repeated here.

[0183] In an exemplary embodiment, step S82 includes: extracting two or more types of data service requests in the collaborative request, and the two or more types of data service requests include at least one of an AI service request and a perception service request.

[0184] That is, the DSMF may first extract a set of data service requests from the collaborative request, and then identify and extract the data service request that matches itself from the set of data service requests. In addition, the DSMF may also directly extract the data service request that matches itself from the collaborative request.

[0185] The data service request matching the DSMF may be one, two or more. When there are two or more data service requests, they may be of the same type (for example, all are perception service requests) or of different types (for example, including both perception service requests and AI service requests).

[0186] In an exemplary embodiment, two or more types of data service requests correspond to at least one service execution node, and step S83 includes: generating two or more data service tasks according to two or more types of data service requests; Send two or more data service tasks to their corresponding service execution nodes respectively.

[0187] DSMF can select different service execution nodes for two or more data service requests, or send two or more data service requests of the same type to the same service execution node, or send two or more data service requests of different types to the same service execution node. Each service execution node can execute only one type of data service task or multiple types of data service tasks; it can execute one data service task or multiple data service tasks in parallel or sequentially.

[0188] Corresponding to the above-mentioned collaborative request processing method executed by the network element of the core network, the embodiment of the present disclosure also provides a collaborative request processing method executed by the UE.

[0189] Fig. 9 It is a flowchart of a collaborative request processing method executed by a UE according to an embodiment of the present disclosure.

[0190] Fig. 9 The method 900 may be performed by a UE having the capability of generating a cooperation request.

[0191] refer to Fig. 9 , the collaborative request processing method 900 may include: Step S91, generating a collaborative request according to a preset format, where the collaborative request is used to request a connection service and a data service; Step S92: Send a collaboration request to the access and mobility management function network element.

[0192] Among them, when the UE determines to request multiple services from the core network, including requesting connection services and data services at the same time, it can generate a collaborative request according to a preset format. In addition to including a connection service request and one or more data service requests, the collaborative request can also record relevant information for eAMF to select CSMF and DSMF in a preset field, such as the service area and other information mentioned in the aforementioned embodiment, or it can be used by DSMF to identify and extract relevant information for the data service request for which it is responsible. In addition, the collaborative request can also include information such as the number and type of data service requests.

[0193] A person skilled in the art may add information to the collaborative request as required so that the core network can process the collaborative request, but the present disclosure is not limited thereto.

[0194] In an exemplary embodiment, in step S82, the UE may send a coordination request to the eAMF via a NAS message. In some embodiments, the UE may carry the coordination request via the PCO field in the NAS message, and may also carry relevant information of the coordination request in the PCO field or other preset fields, such as information that helps the eAMF select CSMF and DSMF.

[0195] In other embodiments, the UE may send a collaboration request via a dedicated multi-factor collaboration request NAS message, and may also carry relevant information of the collaboration request in a preset field of the dedicated multi-factor collaboration request NAS message, such as information that helps the eAMF select CSMF and DSMF.

[0196] During the complete processing of the collaborative request, Figure 8The UE shown needs to have matching collaborative request generation function and collaborative request identification function with the eAMF in the core network. When the UE needs to send a collaborative request, it can select an eAMF with a collaborative request processing capability that matches itself (for example, the UE and the eAMF have synchronous cognition of the preset format of the collaborative request) to send the collaborative request.

[0197] As a result, the communication system 100 can have the ability to process collaborative requests and meet the needs of diversified service requests faced by 6G network deployment.

[0198] The collaborative service processing method provided in the embodiment of the present disclosure aims to solve the problem that users in the next-generation network simultaneously request connection services, perception services and AI services. A core network connection, perception and AI service collaboration method and process are proposed to support the core network to simultaneously process multi-factor collaborative requests for connection + perception + AI services initiated by UE, thereby realizing collaborative processing of multi-factor collaborative requests by the core network.

[0199] In the disclosed embodiment, the core network can receive a multi-factor service request including connection service, perception service and AI service request sent by a user equipment (UE), and decompose it into independent connection service request, perception service request and AI service request. By selecting appropriate network function entities (such as CSMF and DSMF) to process these requests respectively, the coordinated processing of connection service, perception service and AI service is realized.

[0200] In addition, by introducing network functional entities such as DSMF, unified management and coordination of network resources can be achieved. DSMF can select appropriate RAN, DPF and DSF according to data service requirements to collect, analyze, process and store data related to perception / AI tasks, thereby realizing dynamic allocation and optimization of network resources.

[0201] Corresponding to the above method embodiments, the present disclosure also provides several communication network elements that can be used to execute the above method embodiments.

[0202] Fig.10 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0203] refer to Fig.10 , the communication network element 1000 may include: A first collaborative request receiving module 101, configured to receive a collaborative request from a user equipment, wherein the collaborative request includes a data service request and a connection service request; A collaborative request matching module 102, configured to determine a connection service management function network element and a data service management function network element according to the collaborative request; The request sending module 103 is configured to send a first request to the service management function network element and a second request to the data service management function network element, wherein the first request includes the connection service request and the second request includes the data service request.

[0204] Since the functions of the communication network element 1000 have been described in detail in its corresponding method embodiment (method 200), the present disclosure will not repeat them here.

[0205] Fig.11 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0206] refer to Fig.11 , the communication network element 1100 may include: A second coordination request receiving module 111, configured to receive a coordination request from an access and mobility management function network element; A connection service request extraction module 112, configured to extract the connection service request in the collaborative request; The network connection establishing module 113 is configured to establish a network connection for the user equipment according to the connection service request.

[0207] Since the functions of the communication network element 1100 have been described in detail in the corresponding method embodiment (method 700), the present disclosure will not repeat them here.

[0208] Fig.12 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0209] refer to Fig.12 , the communication network element 1200 may include: A third coordination request receiving module 121, configured to receive a coordination request from an access and mobility management function network element; A data service request extraction module 122, configured to extract the data service request in the collaborative request; The data service request execution module 123 is configured to select a data service execution node to execute a data service task according to the data service request.

[0210] Since the functions of the communication network element 1200 have been described in detail in its corresponding method embodiment (method 800), the present disclosure will not repeat them here.

[0211] Fig.13 It is a block diagram of a communication network element in an exemplary embodiment of the present disclosure.

[0212] refer to Fig.13 , the communication network element 1300 may include: A collaborative request generating module 131, configured to generate a collaborative request according to a preset format, wherein the collaborative request is used to request a connection service and a data service; The coordination request sending module 132 is configured to send a coordination request to the access and mobility management function network element.

[0213] Since the functions of the communication network element 1300 have been described in detail in the corresponding method embodiment (method 900), the present disclosure will not repeat them here.

[0214] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0215] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0216] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0217] Refer to the following Fig.14 14 to 15. The electronic device 1400 according to this embodiment of the present invention is described. Fig.14 The electronic device 1400 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0218] like Fig.14 As shown, the electronic device 1400 is in the form of a general computing device. The electronic device 1400 can be used for any one or more functions of eAMF, CSMF, and DSMF, or the electronic device 1400 can be a UE.

[0219] The components of the electronic device 1400 may include, but are not limited to: the at least one processing unit 1410 described above, the at least one storage unit 1420 described above, and a bus 1430 connecting different system components (including the storage unit 1420 and the processing unit 1410).

[0220] The storage unit stores program codes, which can be executed by the processing unit 1410, so that the processing unit 1410 performs the steps according to various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 1410 can perform the method shown in the embodiment of the present disclosure.

[0221] The storage unit 1420 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 14201 and / or a cache storage unit 14202 , and may further include a read-only storage unit (ROM) 14203 .

[0222] The storage unit 1420 may also include a program / utility 14204 having a set (at least one) of program modules 14205, such program modules 14205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0223] Bus 1430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0224] The electronic device 1400 may also communicate with one or more external devices 1500 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1400, and / or may communicate with any device that enables the electronic device 1400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1450. In addition, the electronic device 1400 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1460. As shown, the network adapter 1460 communicates with other modules of the electronic device 1400 via a bus 1430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0225] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0226] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present invention may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a user device, the program code is used to enable the user device to perform the steps according to various exemplary implementations of the present invention described in the above "Exemplary Method" section of the present specification.

[0227] The program product for implementing the above method according to an embodiment of the present invention can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a user device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0228] The program product may be any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0229] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0230] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0231] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0232] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0233] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are to be considered exemplary only, and the true scope and concept of the present disclosure are indicated by the claims.

Claims

1. A collaborative request processing method, characterized in that: Executed by the access and mobility management function network element, including: receiving a coordination request from a user equipment, the coordination request including a data service request and a connection service request; Determine a connection service management function network element and a data service management function network element according to the coordination request; A first request is sent to the service management function network element, and a second request is sent to the data service management function network element, wherein the first request includes the connection service request, and the second request includes the data service request.

2. The collaborative request processing method according to claim 1, characterized in that: The first request and the second request are both the collaborative requests, and sending the first request to the service management function network element and sending the second request to the data service management function network element comprises: sending the collaboration request to the connection service management function network element so that the connection service management function network element extracts the connection service request from the collaboration request; The coordination request is sent to the data service management function network element, so that the data service management function network element extracts the data service request from the coordination request.

3. The collaborative request processing method according to claim 1, characterized in that: The first request is a connection service request, the second request is a data service request, and sending the first request to the service management function network element and sending the second request to the data service management function network element comprises: Parsing the collaboration request to extract the connection service request and the data service request; Sending the connection service request to the connection service management function network element; The data service request is sent to the data service management function network element.

4. The collaborative request processing method according to claim 3, characterized in that: Parsing the collaboration request to extract the connection service request and the data service request includes: The collaborative request is parsed to extract a connection service request and two or more types of data service requests, wherein the two or more types of data service requests include at least one of an AI service request and a perception service request.

5. The collaborative request processing method according to claim 4, characterized in that: The two or more types of data service requests correspond to at least one data service management function network element, and sending the data service request to the data service management function network element includes: The two or more types of data service requests are respectively sent to their corresponding data service management function network elements.

6. The collaborative request processing method according to claim 1, characterized in that: Receiving a collaboration request from a user device includes: The cooperation request is obtained through a NAS message from the user equipment.

7. The collaborative request processing method according to claim 6, characterized in that: Acquiring the collaboration request through the NAS message includes: The cooperation request is obtained through the PCO field in the NAS message.

8. The collaborative request processing method according to claim 6, characterized in that: Acquiring the collaboration request through the NAS message includes: The collaboration request is obtained through a dedicated multi-element collaboration request NAS message.

9. The collaborative request processing method according to claim 1, characterized in that: Determining the connection service management function network element and the data service management function network element according to the coordination request includes: The connection service management function network element and the data service management function network element are determined according to the service area corresponding to the collaboration request.

10. A collaborative request processing method, characterized in that: Executed by the connection service management function network element, including: receiving a coordination request from an access and mobility management function network element; Extracting a connection service request from the collaborative request; A network connection of the user equipment is established according to the connection service request.

11. A collaborative request processing method, characterized in that: Executed by the data service management function network element, including: receiving a coordination request from an access and mobility management function network element; extracting a data service request in the collaborative request; A data service execution node is selected according to the data service request to execute the data service task.

12. The collaborative request processing method according to claim 11, characterized in that: Extracting the data service request in the collaborative request includes: Extract two or more types of data service requests from the collaborative request, where the two or more types of data service requests include at least one of an AI service request and a perception service request.

13. The collaborative request processing method according to claim 12, characterized in that: The two or more types of data service requests correspond to at least one service execution node, and selecting a data service execution node to perform a data service task according to the data service request includes: generating two or more data service tasks according to the two or more types of data service requests; The two or more data service tasks are respectively sent to their corresponding service execution nodes.

14. A collaborative request processing method, characterized in that: Executed by the user device, including: generating a collaborative request according to a preset format, wherein the collaborative request is used to request a connection service and a data service; Send a coordination request to the access and mobility management function network element.

15. The collaborative request processing method according to claim 14, characterized in that: Sending a coordination request to the access and mobility management function network element includes: The collaboration request is sent to the access and mobility management function network element through a NAS message.

16. A communication network element, characterized in that: include: A first collaborative request receiving module, configured to receive a collaborative request from a user equipment, wherein the collaborative request includes a data service request and a connection service request; A collaborative request matching module, configured to determine a connection service management function network element and a data service management function network element according to the collaborative request; The request sending module is configured to send a first request to the service management function network element and a second request to the data service management function network element, wherein the first request includes the connection service request and the second request includes the data service request.

17. A communication network element, characterized in that: include: A second coordination request receiving module, configured to receive a coordination request from an access and mobility management function network element; A connection service request extraction module, configured to extract the connection service request in the collaborative request; The network connection establishing module is configured to establish a network connection of the user equipment according to the connection service request.

18. A communication network element, characterized in that: include: A third coordination request receiving module, configured to receive a coordination request from an access and mobility management function network element; A data service request extraction module, configured to extract the data service request in the collaborative request; The data service request execution module is configured to select a data service execution node to execute a data service task according to the data service request.

19. A communication system, characterized in that: include: An access and mobility management function network element, configured to execute the collaborative request processing method according to any one of claims 1 to 9; A connection service management function network element, configured to execute the collaborative request processing method as claimed in claim 10; A data service management function network element, configured to execute the collaborative request processing method according to any one of claims 11 to 13; User equipment, used to execute the collaborative request processing method as described in any one of claims 14 and 15.

20. An electronic device, characterized in that: include: Memory; as well as A processor coupled to the memory, the processor being configured to execute the method according to any one of claims 1 to 15 based on instructions stored in the memory.

21. A computer-readable storage medium having a program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 15 is implemented.

22. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 15 are implemented.

Images