WO2024197896A1 - 用于实现业务的方法和通信装置 - Google Patents

用于实现业务的方法和通信装置 Download PDF

Info

Publication number
WO2024197896A1
WO2024197896A1 PCT/CN2023/085700 CN2023085700W WO2024197896A1 WO 2024197896 A1 WO2024197896 A1 WO 2024197896A1 CN 2023085700 W CN2023085700 W CN 2023085700W WO 2024197896 A1 WO2024197896 A1 WO 2024197896A1
Authority
WO
WIPO (PCT)
Prior art keywords
function network
execution function
plane
network element
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/085700
Other languages
English (en)
French (fr)
Inventor
姚琦
武绍芸
邢玮俊
吴建军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2023/085700 priority Critical patent/WO2024197896A1/zh
Priority to CN202380096248.XA priority patent/CN120982151A/zh
Priority to EP23929479.6A priority patent/EP4683380A4/en
Publication of WO2024197896A1 publication Critical patent/WO2024197896A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Definitions

  • the present application relates to the field of wireless communications, and in particular to a method and a communication device for implementing a service.
  • the fifth generation (5G) network can be viewed as a single connection model, maintaining a user plane transmission channel from user equipment (UE) to data network (DN), thereby enabling UE to access DN data services.
  • UE user equipment
  • DN data network
  • 6G networks will add data plane and computing plane functions, and will no longer be just a connection model.
  • 6G networks will add data plane and computing plane functions, and will no longer be just a connection model.
  • 6G services based on the data plane and computing plane.
  • the present application provides a method and a communication device for implementing a service, which can implement a service with data plane functional requirements and/or computing plane functional requirements.
  • a method for implementing a service is provided.
  • the method can be executed by a service plane control function network element, or by a component of the service plane control function network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the service plane control function network element.
  • the method comprises: receiving a service request, the service request comprising a data plane function requirement and/or a computing plane function requirement; determining M target service plane execution function network elements, a forwarding path between the M target service plane execution function network elements and a processing rule for each of the target service plane execution function network elements according to the service request, 2 ⁇ M; establishing a forwarding path between the M target service plane execution function network elements, and sending the processing rule to each of the target service plane execution function network elements, the processing rule indicating the service operation performed by the target service plane execution function network element.
  • a data plane and a computing plane are introduced.
  • the business plane execution function network element that executes the business and the forwarding path of the business plane execution function network element that executes the business and the corresponding processing rules respectively based on the business request with data plane function requirements and/or computing plane function requirements it is possible to implement the business with data plane function requirements and/or computing plane function requirements.
  • the service plane control function network element can be implemented by a session management function (SMF).
  • SMS session management function
  • the data plane and computing plane control functions can be enhanced in the current SMF to realize the functions of the service plane control function network element.
  • This solution makes little change to the existing network architecture and is suitable for various demands of various user planes, data planes and computing planes in the future.
  • M target service plane execution function network elements are determined based on the service request, including determining the M target service plane execution function network elements based on the service request and capability information of each service plane execution function network element in the N service plane execution function network elements, the capability information including data plane capabilities and/or computing plane capabilities supported by the service plane execution function network element, the M target service plane execution function network elements belong to the N service plane execution function network elements, M ⁇ N.
  • the data plane capability may include one or more of the following capabilities: data feature extraction, data analysis, data compression, or data decompression.
  • computing surface capabilities may include one or more of the following: the capacity of the central processing unit (CPU)/graphics processing unit (GPU), the margin of the CPU/GPU, or what computing algorithms are supported.
  • the M target service plane execution function network elements include one or more of the following: at least one access network device, at least one user plane function network element, or at least one network data analysis function network element.
  • the functions of the service plane execution function network element can be realized by enhancing the data plane and computing plane functions in the access network equipment, user plane function network element, or network data analysis function network element. This solution makes little change to the existing network architecture and is easy to implement.
  • the M target service plane execution function network elements include a first access network device in the at least one access network device.
  • the sending of the processing rule to each of the target service plane execution function network elements includes: sending the processing rule to the first access network device through an interface between the service plane control function network element and the first access network device.
  • the service plane control function network element and the access network device can communicate directly without forwarding by other network elements.
  • the first access network device executes the data plane and/or computing plane functions based on the processing rules.
  • receiving the service request includes: receiving the service request from a first network element; or receiving the service request from the first network element via a network open function network element.
  • the first network element is one of the following: a terminal device, an application function network element, a task anchor point, or an operation maintenance management function network element.
  • terminal equipment, application function network elements, task anchor points, or operation and maintenance management function network elements can send service requests when there is a service demand.
  • M target service plane execution function network elements are determined, including: according to the service request, a first request is sent to a network storage function network element, the first request includes the data plane function requirement and/or the computing plane function requirement, the first request is used for the network storage function network element to determine P candidate service plane execution function network elements, and the M target service plane execution function network elements belong to the P candidate service plane execution function network elements; receiving a first response from the network storage function network element, the first response indicating the P candidate service plane execution function network elements; determining the M target service plane execution function network elements from the P candidate service plane execution function network elements.
  • the service plane execution function network element can register its capability information with the network storage function network element, and the service plane control function network element can request the network storage function network element to determine P candidate service plane execution function network elements according to the data plane function requirements and/or the computing plane function requirements of the service request, and then determine the M target service plane execution function network elements from the P candidate service plane execution function network elements. It should be understood that P can be equal to M or greater than M.
  • the method before determining M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each of the target network elements based on the service request, the method also includes: receiving registration information from some or all of the N service plane execution function network elements, and the registration information includes capability information of the service plane execution function network elements.
  • the service plane execution function network element can register its capability information with the service plane control function network element.
  • the method before determining M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each of the target network elements based on the service request, the method also includes: receiving configuration information, which includes capability information of some or all of the N service plane execution function network elements.
  • the capability information of the service plane execution function network element can be registered and configured on the service plane control function network element, saving the cost caused by the service plane control function network element inquiring other network elements.
  • a communication system which includes a service plane control function network element and M target service plane execution function network elements.
  • the service plane control function network element is used to: receive a service request, which includes a data plane function requirement and/or a computing plane function requirement; determine the M target service plane execution function network elements, the forwarding path between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element according to the service request, 2 ⁇ M ⁇ N; establish a forwarding path between the M target service plane execution function network elements, and send the processing rule to each target service plane execution function network element, the processing rule indicating the service operation performed by the target service plane execution function network element.
  • the target service plane execution function network element is used to: receive the processing rule from the service plane control function network element.
  • a data plane and a computing plane are introduced.
  • the business request can realize the business with data plane function requirements and/or computing plane function requirements.
  • the target service plane execution function network element is further used to: send registration information to the network storage function network element or the service plane control function network element, and the registration information includes data plane capabilities and/or computing plane capabilities supported by the target service plane execution function network element.
  • the target service plane execution function network element is a network device, and the target service plane execution function network element is specifically used to receive the processing rule through an interface between the network device and the service plane control function network element.
  • a communication device comprising a module or a unit for executing the method in the first aspect or any possible implementation manner of the first aspect.
  • a communication device comprising a processor, the processor being coupled to a memory, the memory being used to store computer programs or instructions, and the processor being used to execute the computer programs or instructions stored in the memory to implement the method in the first aspect or any possible implementation of the first aspect.
  • the device further includes a memory coupled to the processor.
  • processors there are one or more processors and/or one or more memories.
  • the memory may be integrated with the processor, or the memory may be separately provided with the processor.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the device is a service plane control function network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip in a service plane control function network element.
  • the communication interface may be an input/output interface.
  • a processor comprising: an input circuit, an output circuit, and a processing circuit.
  • the circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.
  • the above-mentioned processor can be a chip
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits.
  • the input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver
  • the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter
  • the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • This application does not limit the specific implementation methods of the processor and various circuits.
  • a computer program product which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute the method in the first aspect or any possible implementation of the first aspect.
  • a computer program also referred to as code, or instruction
  • a computer-readable storage medium which stores a computer program (also referred to as code or instructions).
  • a computer program also referred to as code or instructions.
  • the computer program runs on a computer, the computer executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.
  • a chip comprising a processor for calling and running a computer program from a memory, so that a communication device equipped with the chip executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.
  • a communication device comprising an interface and a processor, wherein the interface is used to send and/or receive signals, so that the processor executes the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.
  • FIG1 is a schematic diagram of a 5G network architecture
  • FIG2 is a schematic diagram of a network architecture provided in an embodiment of the present application.
  • FIG3 is a schematic flow chart of a method for implementing a service provided in an embodiment of the present application.
  • FIG4 is a schematic flow chart of a method for implementing a service provided in an embodiment of the present application.
  • FIG5 is a schematic flow chart of a method for implementing a service provided in an embodiment of the present application.
  • FIG6 is a schematic flow chart of a method for implementing a service provided in an embodiment of the present application.
  • FIG7 is a schematic flow chart of a method for implementing a service provided in an embodiment of the present application.
  • FIG8 is a schematic block diagram of a communication device provided in an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of another communication device provided in an embodiment of the present application.
  • A/B can represent A or B.
  • the "and/or” in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships.
  • a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • multiple means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.
  • the words “first”, “second” and the like are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like do not necessarily limit the difference.
  • network elements, network functions, devices, apparatuses, etc. can be replaced with each other; network elements, network functions, devices, apparatuses, etc. can also be replaced with "entities”, and “functional network elements” can also be replaced with “functions”.
  • FIG1 shows a schematic diagram of a 5G network architecture.
  • the 5G network includes a user plane and a control plane.
  • the user plane is used to transmit data, including a (radio) access network ((R)AN) 101 and a user plane function (UPF) 102.
  • the UPF can be divided into an intermediate user plane function (I-UPF) and an anchor user plane function (A-UPF).
  • the control plane can adopt a service-based interface.
  • the control plane can include: access and mobility management function (AMF) 104, session management function (SMF) 105, network repository function (NRF) 106, network exposure function (NEF) 107, policy control function (PCF) 108, etc.
  • AMF access and mobility management function
  • SMF session management function
  • NRF network repository function
  • PCF policy control function
  • the 5G network may also include a network data analysis function (NWDAF) 110.
  • NWDAF network data analysis function
  • FIG1 also shows a UE 111 accessing the network, a data network (DN) 103 connected to the 5G network, an application function (AF) 109, and operation, administration and maintenance (OAM) 112.
  • DN data network
  • AF application function
  • OAM operation, administration and maintenance
  • RAN101 It is used to provide network access functions for authorized user equipment (UE) in a specific area (for example, UE 111 in Figure 1). It is responsible for wireless resource management, uplink and downlink data classification and quality of service (QoS) application, as well as completing signaling processing with control plane network elements and data forwarding with user plane functional network elements.
  • UE authorized user equipment
  • QoS quality of service
  • UPF 102 used for packet routing and forwarding, QoS processing of user plane data, etc.
  • DN 103 A network used to provide data transmission.
  • the UE after the UE accesses the network, it can establish a protocol data unit (PDU) session, access the DN through the PDU session, and interact with the AF deployed in the DN.
  • PDU protocol data unit
  • the network can select the UPF accessing the DN as the PDU session anchor (PSA) according to the network policy, and access the AF through the N6 interface of the PSA.
  • PSA PDU session anchor
  • AMF 104 Mainly used for mobility management and access management, etc. It can be used to implement other functions of the mobility management entity (MME) except session management, such as lawful monitoring and access authorization/authentication.
  • MME mobility management entity
  • SMF 105 Mainly responsible for establishing and managing sessions for users, configuring packet forwarding rules and QoS processing rules for user name functions, etc.
  • NRF 106 Responsible for network function service registration, status monitoring, etc., to achieve automated management, selection and scalability of network function services, and allow each network function to discover services provided by other network functions.
  • NEF 107 Used to provide customized functions for network opening. NEF network elements can also be used to provide external applications Functional network elements open up capabilities supported by 5GC, such as providing small data transmission capabilities.
  • PCF 108 A unified policy framework used to guide network behavior and provide policy rule information to control plane functional network elements (such as AMF, SMF network elements, etc.).
  • Application function network elements can interact with the 5G system through application function network elements to access NEF or interact with the policy framework for policy control, etc.
  • NWDAF 110 can provide network analysis services based on the network service's request data. For example, a network service may request specific analysis information on the load level of a particular network slice. Alternatively, a network service may subscribe to a service that notifies the NWDAF when a network slice changes or reaches a certain threshold.
  • OAM112 Mainly used for daily network and service analysis, prediction, planning and configuration; daily operational activities such as network and service testing and fault management.
  • the 5G network shown in Figure 1 can be regarded as a single connection model, maintaining a user plane transmission channel from UE to DN (UE—RAN—I-UPF—A-UPF--DN), thereby enabling UE to access DN data services.
  • UE RAN—I-UPF—A-UPF--DN
  • the present application provides a method for implementing a service, introducing a data plane and a computing plane.
  • determining the service plane execution function network element that executes the service and the forwarding path of the service plane execution function network element that executes the service and the corresponding processing rules based on the service request with data plane functional requirements and/or computing plane functional requirements and the capability information of the service plane execution function network element it is possible to implement services with data plane functional requirements and/or computing plane functional requirements.
  • the business plane in this application may also be referred to as the function plane, user plane, data plane, or computing plane, and this application does not limit the name.
  • this article uses the term business plane to explain.
  • FIG2 is a schematic diagram of a network architecture provided by the present application.
  • the network architecture includes a service plane control function network element 201 and a service plane execution function network element.
  • the network architecture may also include one or more of the following: a network open function network element 202, a network storage function network element 203, an application function network element 204, or a network management function network element 205.
  • the network architecture also shows a terminal device 207 that communicates with an access network device 206. Each device or network element is described below.
  • Business plane control function network element 201 has computing plane and data plane control functions, used to manage (or call network storage function 203 service query) connection resources, computing resources and data resources, and realize connection, computing and data collaboration.
  • the function of the service plane control function network element 201 can be implemented by enhancing the data plane and computing plane control functions in the session management function network element.
  • the session management function network element may be an SMF.
  • the session management function network element may be an SMF, or may have other names, which are not limited in this application.
  • Business plane execution function network element a network element that has or supports certain data plane and/or computing plane functions.
  • the service plane execution function network element may be composed of the access network device 206, the user
  • the service plane execution function network element may be implemented by the network plane function network element 208 or the network data analysis function network element 209.
  • the service plane execution function network element may be implemented by adding a new network element (eg, the new network element 210 shown in FIG. 2 ) to the current network architecture.
  • Access network equipment It can be a base station (Base Station), an evolved base station (Evolved NodeB, eNodeB), a transmission reception point (Transmission Reception Point, TRP), the next generation base station (Next Generation NodeB, gNB) in a 5G mobile communication system, the next generation base station in a sixth generation (6th Generation, 6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it can also be a module or unit that completes some of the functions of a base station, for example, it can be a centralized unit (Central Unit, CU) or a distributed unit (Distributed Unit, DU).
  • Base Station Base Station
  • Evolved NodeB, eNodeB evolved base station
  • TRP Transmission Reception Point
  • the CU completes the functions of the radio resource control protocol and the packet data convergence layer protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP);
  • the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer.
  • 3GPP 3rd Generation Partnership Project
  • the access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.
  • the access network device and the terminal device can be fixed or movable.
  • the access network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and artificial satellites in the air.
  • the embodiments of the present application do not limit the application scenarios of access network devices and terminal devices.
  • the user plane function network element may be a UPF.
  • the user plane function network element may still be a UPF, or may have other names, which are not limited in this application.
  • the network data analysis function network element may be NWDAF.
  • the network data analysis function network element may still be NWDAF, or may have other names, which are not limited in this application.
  • Network open function network element 202 In the 5G communication system, the network open function network element may be NEF. In future communication systems, the network open function network element may still be NEF, or may have other names, which are not limited in this application.
  • Network storage function network element 203 In the 5G communication system, the network storage function network element may be an NRF. In future communication systems, the network storage function network element may still be an NRF, or may have other names, which are not limited in this application.
  • Application function network element 204 In the 5G communication system, the application function network element may be AF. In future communication systems, the application function network element may still be AF, or may have other names, which are not limited in this application.
  • Network management function element 205 In the 5G communication system, the network management function element may be OAM. In the future communication system, the network management function element may still be OAM, or may have other names, which are not limited in this application.
  • Terminal equipment 207 The terminal equipment may refer to user equipment (UE), station, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • the terminal equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLAN) phone, or a wireless cellular phone.
  • SIP session initiation protocol
  • WLAN wireless local loop
  • WLL local loop
  • PDA personal digital assistant
  • WLL wireless local loop
  • PDA personal digital assistant
  • WLL wireless local loop
  • computing device or other processing device connected to a wireless modem, large screen, vehicle-mounted device, wearable device, terminal device in a 5G network or terminal device in a future evolved public land mobile communication network (public land mobile network, PLMN), etc.
  • PLMN public land mobile network
  • signals can be directly exchanged between the service plane control function network element 201 and the access network device 206 without being transferred through other network elements (eg, AMF).
  • the service plane control function network element 201 and the service plane execution function network element may exchange signals based on a service-oriented interface or an N4 interface or other interfaces.
  • the user plane function network element 208 and the network data analysis function network element 209 can directly exchange signals without being transferred through other network elements (such as AMF).
  • the user plane function network element 208 and the network data analysis function network element 209 can exchange signals based on the N9 interface or the service interface or other interfaces.
  • network elements, network elements or functions involved in this application can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the network element or device in the accompanying drawings may also be a chip, a chip system, or a processor that supports the network element or device to implement the method, or a logic module or software that can implement all or part of the functions of the network element or device.
  • Fig. 3 is a schematic flow chart of a method for implementing a service provided by the present application.
  • the method 300 may include S301 to S303, and each step is described below.
  • S301 The service plane control function network element receives a service request.
  • the service request comes directly or indirectly from the first network element. That is, the first network element can directly send the service request to the service plane control function network element, or the first network element can first send the service request to the intermediate network element, and then the intermediate network element sends the service request to the service plane control function network element.
  • the first network element can be a terminal device, an application function network element, a task anchor point, or an operation and maintenance management function network element.
  • the intermediate network element can be a network open function network element.
  • the service request includes data plane functional requirements and/or computing plane functional requirements.
  • the service request includes data plane functional requirements.
  • the service request is a request to collect (e.g., aggregate, deduplicate, etc.), anonymize, and/or compress specific data.
  • the service request includes computing plane functional requirements.
  • the service request is a request to locally unload a specific service or extract a specific service flow.
  • some services may belong to the data plane or the computing plane, or some services may belong to both the data plane and the user plane. For example, preprocessing of video data streams.
  • the service plane control function network element determines M target service plane execution function network elements, forwarding paths between the M target service plane execution function network elements, and processing rules of each target service plane execution function network element according to the service request.
  • the M target service plane execution function network elements may be determined according to the service request and the capability information of each service plane execution function network element in the N service plane execution function network elements.
  • the M target service plane execution function network elements belong to the N service plane execution function network elements, that is, the M target service plane execution function network elements are the M service plane execution function network elements in the N service plane execution function network elements, 2 ⁇ M ⁇ N.
  • the capability information of any service plane execution function network element includes the data plane capability and/or computing plane capability supported by the service plane execution function network element.
  • the data plane capabilities may include one or more of the following capabilities: data feature extraction, data analysis, data compression, and data decompression.
  • the computing surface capability may include one or more of the following capabilities: CPU/GPU capacity, CPU/GPU margin, and supported computing algorithms.
  • the capability information of the service plane execution function network element may be the capability information of the service plane execution function network element registered with the service plane control function network element.
  • the service plane execution function network element may send registration information to the service plane control function network element, and the registration information may include capability information of the service plane execution function network element. That is, the service plane execution function network element may register its capability information to the service plane control function network element through the registration information.
  • This method may be applicable to simple networking or local networking scenarios.
  • the capability information of the service plane execution function network element may be the service plane execution function network element registered with the network storage function network element, such as NRF.
  • the service plane execution function network element may send registration information to the network storage function network element, and the registration information may include the capability information of the service plane execution function network element. That is, the service plane execution function network element may register its capability information to the network storage function network element through the registration information.
  • This method may be applicable to complex networking or distributed networking scenarios.
  • the service plane execution function network element may send the data plane function requirements and/or computing plane function requirements contained in the service request to the network storage function network element.
  • the network storage function network element may determine P (M ⁇ P ⁇ N) candidate service plane execution function network elements based on the data plane function requirements and/or computing plane function requirements and the capability information of the service plane execution function network element registered with the network storage function network element, and return the information of the P candidate service plane execution function network elements (for example, the identifiers of the P candidate service plane execution function network elements) to the service plane execution function network element.
  • the service plane execution function network element may determine the M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element based on the P candidate service plane execution function network elements.
  • the M target service plane execution function network elements are the M candidate service plane execution function network elements among the P candidate service plane execution function network elements.
  • the capability information of the service plane execution function network element may be configured in the service plane control On the functional network element.
  • the management system/operation and maintenance system may configure the capability information of the service plane execution functional network element on the service plane control functional network element.
  • the service plane execution function network element does not need to register the capability information, and the capability information of the service plane execution function network element is directly configured on the service plane control function network element.
  • all service plane execution function network elements register capability information using the first implementation method or the second implementation method.
  • the capability information of all service plane execution function network elements is implemented using the third implementation method.
  • the registration or configuration method of capability information of different service plane execution function network elements may be different. For example, some service plane control function network elements register capability information using the first implementation method, and other service plane control function network elements register capability information using the second implementation method.
  • each service plane execution function network element may be different or the same, and this application does not limit this.
  • access network device #1 supports data feature extraction
  • access network device #2 supports data compression and data decompression
  • user plane function network element #1 supports data feature extraction, data compression, and data decompression at the same time.
  • the service plane control function network element may register its own service scope, and/or the supported data plane and/or computing plane capabilities, with the network storage function network element.
  • the data plane and/or computing plane capabilities supported by the service plane control function network element may be identified by the data plane and/or computing plane capabilities supported by the service plane execution function network element managed by the service plane control function network element.
  • the intermediate network element can request the network storage function network element to select a service plane control function network element that meets the requirements based on the service scope of the service plane control function network element itself, and/or the supported data plane and/or computing plane capabilities, and then send the service request to the selected service plane control function network element.
  • the processing rules indicate the service operations performed by the target service plane execution function network element. That is, the processing rules of a target service plane execution function network element refer to what operations the target service plane execution function network element needs to perform, such as data processing/data analysis, data compression/decompression, preprocessing/fusion processing, federated processing (distributed), etc.
  • the service request is to collect, anonymize, and compress specific data.
  • the service plane control function network element can determine that compression is performed by access network device #1 and access network device #2, collection is performed by user plane function network element #1, and anonymization is performed by network data analysis function network element.
  • the service plane control function network element determines to establish a connection between access network device #1 and user plane function network element #1, a connection between access network device #2 and user plane function network element #1, and a connection between user plane function network element #1 and network data analysis function network element.
  • the processing rule of access network device #1 is compression
  • the processing rule of access network device #2 is also compression
  • the processing rule of user plane function network element #1 is collection and transmission to network data analysis function network element
  • the processing rule of network data analysis function network element is anonymization.
  • the service request is to first unload a specific service flow locally, extract key features, and then upload it to the data center.
  • the service plane control function network element can determine that the user plane function network element #2 will perform data diversion and extract key features, and then the network data analysis function network element will perform further analysis and processing.
  • the service plane control function network element determines to establish a connection between the user plane function network element #2 and the network data analysis function network element.
  • the processing rule of the user plane function network element #2 is to split the data and transmit it to the network data analysis function network element, and the processing rule of the network data analysis function network element is to further process and analyze the received data.
  • the service plane control function network element establishes a forwarding path between M target service plane execution function network elements, and sends a processing rule to each target service plane execution function network element.
  • the service plane control function network element establishes a connection between the access network device #1 and the user plane function network element #1, a connection between the access network device #2 and the user plane function network element #1, and a connection between the user plane function network element #1 and the network data analysis function network element.
  • the service plane control function network element sends the corresponding processing rules to the access network device #1, the access network device #2, the user plane function network element #1, and the network data analysis function network element, respectively.
  • a data plane and a computing plane are introduced.
  • the business plane execution function network element that executes the business and the forwarding path of the business plane execution function network element that executes the business and the corresponding processing rules respectively based on the business request with data plane function requirements and/or computing plane function requirements it is possible to implement the business with data plane function requirements and/or computing plane function requirements.
  • the functions of the service plane control function network element can be realized by enhancing the data plane and computing plane control functions in the SMF. This solution makes little change to the existing network architecture (including user plane functions and session management functions) and is suitable for various demands of various user planes, data planes and computing planes in the future.
  • the functions of the service plane execution function network element can be realized by enhancing the data plane and computing plane functions in the RAN, UPF or NWDAF. This solution makes little change to the existing network architecture and is easy to implement.
  • SMF, RAN, UE, UPF, AF, NRF, NEF, and NWDAF correspond to the service plane control function network element, access network equipment, terminal equipment, user plane function network element, application function network element, network storage function network element, network open function network element, and network data analysis function network element in method 300, respectively.
  • FIG4 shows a schematic flow chart of a method for implementing a service provided by the present application.
  • the SMF may directly receive a service request, and at the same time, the service plane execution function network element registers its capability information with the NRF.
  • the method 400 may include S401 to S408. Each step is described below.
  • S401 The service plane execution function network element registers its capability information with the NRF.
  • multiple network elements such as RAN#1, RAN#2, UPF#1 and NWDAF register their capability information with NRF.
  • the first network element sends a service request to the SMF.
  • the SMF receives the service request.
  • the UE or AF when there is a data plane function requirement and/or a computing plane function requirement, the UE or AF sends a service request to the SMF, wherein the service request may include the data plane function requirement and/or the computing plane function requirement.
  • S403 SMF sends a first request to NRF according to the service request.
  • NRF receives the first request from SMF.
  • the first request may include a data plane function requirement and/or a computing plane function requirement in the service request.
  • S404 The NRF determines P candidate service plane execution function network elements according to the first request.
  • the P candidate service plane execution function network elements are part or all of the N service plane execution function network elements that have registered capability information with the NRF, and M ⁇ P ⁇ N.
  • NRF sends a first response to SMF in response to the first request. response.
  • the first response is used to indicate the P candidate service plane execution function network elements, for example, the first response may include the identifiers of the P candidate service plane execution function network elements.
  • the P candidate service plane execution function network elements may be RAN#1, RAN#2, UPF#1, and NWDAF.
  • SMF determines M target service plane execution function network elements, forwarding paths between the M target service plane execution function network elements, and processing rules for each target service plane execution function network element based on the first response.
  • the SMF can determine the M target service plane execution function network elements based on the topological relationship between the P candidate service plane execution function network elements and/or the load information of the P candidate service plane execution function network elements.
  • the M target service plane execution function network elements are the M candidate service plane execution function network elements among the P candidate service plane execution function network elements.
  • the SMF can also determine the forwarding path between the M target service plane execution function network elements and the processing rules of each target service plane execution function network element.
  • the P candidate service plane execution function network elements are the M target service plane execution function network elements.
  • the service request is to collect, anonymize, and compress specific data.
  • SMF can determine that compression is performed by RAN#1 and RAN#2, collection is performed by UPF#1, and anonymization is performed by NWDAF.
  • SMF determines to establish a connection between RAN#1 and UPF#1, a connection between RAN#2 and UPF#1, and a connection between UPF#1 and NWDAF.
  • the processing rule of RAN#1 is compression
  • the processing rule of RAN#2 is also compression
  • the processing rule of UPF#1 is collection and transmission to NWDAF
  • the processing rule of NWDAF is anonymization.
  • SMF establishes a forwarding path between the M target service plane execution function network elements.
  • SMF establishes the connection between RAN#1 and UPF#1, the connection between RAN#2 and UPF#1, and the connection between UPF#1 and NWDAF.
  • SMF sends the corresponding processing rules to each target service plane execution function network element.
  • each target service plane execution function network element receives the processing rules from SMF.
  • SMF sends processing rule #1 to RAN#1, which is compression; sends processing rule #2 to RAN#2, which is also compression; sends processing rule #3 to UPF#1, which is collection and transmission to NWDAF; sends processing rule #4 to NWDAF, which is anonymization.
  • RAN#1 and RAN#2 will compress the service respectively and then transmit it to UPF#1.
  • UPF#1 collects the received service and transmits it to NWDAF.
  • NWDAF anonymizes the received service.
  • the method for implementing a service introduces a data plane and a computing plane.
  • determining the service plane execution function network element that executes the service and the forwarding path of the service plane execution function network element that executes the service and the corresponding processing rules based on the service request with data plane function requirements and/or computing plane function requirements and the capability information of the service plane execution function network element it is possible to implement services with data plane function requirements and/or computing plane function requirements.
  • FIG5 shows a schematic flow chart of a method for implementing a service provided by the present application.
  • the SMF may indirectly receive a service request, and at the same time, the service plane execution function network element registers its capability information with the NRF.
  • the method 500 may include S501 to S512. Each step is described below.
  • S501 The service plane execution function network element registers its capability information with the NRF.
  • This step is the same as S401, and reference may be made to S401.
  • S502 The first network element sends a service request to the NEF.
  • the NEF receives the service request.
  • the UE or AF when it has data plane function requirements and/or computing plane function requirements, it can send a request to the NEF.
  • the NEF sends a second request to the NRF.
  • the NRF receives the second request.
  • the second request may include the data plane function requirement and/or the computing plane function requirement in the service request.
  • NRF determines SMF according to the second request.
  • SMF may register its service scope, and/or the supported data plane and/or computing plane capabilities, with NRF.
  • the data plane and/or computing plane capabilities supported by SMF may be identified by the data plane and/or computing plane capabilities supported by the service plane execution function network element of the SMF.
  • the NRF may determine a suitable SMF based on data plane functional requirements and/or computing plane functional requirements, and/or information of the SMF registered with the NRF.
  • S505 The NRF sends a second response to the NEF in response to the second request.
  • the MEF receives the second response.
  • the second response may include information of the SMF determined by the NRF, such as an identifier of the SMF.
  • NEF sends the service request to SMF.
  • SMF requests NRF to determine the candidate service plane execution function network element according to the service request. After NRF determines the candidate service plane execution function network element, it returns it to SMF. SMF further determines M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element. In addition, SMF determines the forwarding paths between the M target service plane execution function network elements, and sends the corresponding processing rules to each target service plane execution function network element.
  • the method for implementing a service introduces a data plane and a computing plane.
  • determining the service plane execution function network element that executes the service and the forwarding path of the service plane execution function network element that executes the service and the corresponding processing rules based on the service request with data plane function requirements and/or computing plane function requirements and the capability information of the service plane execution function network element it is possible to implement services with data plane function requirements and/or computing plane function requirements.
  • FIG6 shows a schematic flow chart of a method for implementing a service provided by the present application.
  • the SMF can directly receive a service request, and at the same time, the service plane execution function network element registers its capability information with the SMF.
  • the method 600 may include S601 to S605. Each step is described below.
  • S601 The service plane execution function network element registers its capability information with the SMF.
  • multiple network elements such as RAN#1, RAN#2, UPF#1 and NWDAF register their capability information with NRF.
  • S601 can also be replaced by configuring the capability information of the service plane execution function network element on the SMF.
  • the first network element sends a service request to the SMF.
  • the SMF receives the service request.
  • the UE or AF when there is a data plane function requirement and/or a computing plane function requirement, the UE or AF sends a service request to the SMF, wherein the service request may include the data plane function requirement and/or the computing plane function requirement.
  • SMF determines M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element based on the service request and the capability information of the N service plane execution function network elements.
  • N service plane execution function network elements are service plane execution function network elements whose capability information is registered in S601.
  • the service request is to collect, anonymize, and compress specific data.
  • SMF can The service request and the capability information of N service plane execution function network elements determine that RAN#1 and RAN#2 are compressed, collected by UPF#1, and anonymized by NWDAF. SMF determines to establish the connection between RAN#1 and UPF#1, the connection between RAN#2 and UPF#1, and the connection between UPF#1 and NWDAF.
  • the processing rule of RAN#1 is compression
  • the processing rule of RAN#2 is also compression
  • the processing rule of UPF#1 is collection and transmission to NWDAF
  • the processing rule of NWDAF is anonymization.
  • SMF establishes a forwarding path between the M target service plane execution function network elements.
  • SMF executes the processing rules of the functional network element to each target service plane.
  • SMF establishes the connection between RAN#1 and UPF#1, the connection between RAN#2 and UPF#1, and the connection between UPF#1 and NWDAF.
  • SMF sends processing rule #1 to RAN#1, which is compression, sends processing rule #2 to RAN#2, which is also compression, sends processing rule #3 to UPF#1, which is collection and transmission to NWDAF, and sends processing rule #4 to NWDAF, which is anonymization.
  • RAN#1 and RAN#2 will compress the service respectively and then transmit it to UPF#1.
  • UPF#1 collects the received service and transmits it to NWDAF.
  • NWDAF anonymizes the received service.
  • the method for implementing a service introduces a data plane and a computing plane.
  • determining the service plane execution function network element that executes the service and the forwarding path of the service plane execution function network element that executes the service and the corresponding processing rules based on the service request with data plane function requirements and/or computing plane function requirements and the capability information of the service plane execution function network element it is possible to implement services with data plane function requirements and/or computing plane function requirements.
  • FIG7 shows a schematic flow chart of a method for implementing a service provided by the present application.
  • the SMF may indirectly receive a service request, and at the same time, the service plane execution function network element registers its capability information with the SMF.
  • the method 700 may include S701 to S709. Each step is described below.
  • the service plane execution function network element registers its capability information to the SMF.
  • This step is the same as S601, and reference may be made to S601.
  • S702 The first network element sends a service request to the NEF.
  • the NEF receives the service request.
  • the UE or AF when there is a data plane function requirement and/or a computing plane function requirement, the UE or AF sends a service request to the NEF, wherein the service request may include the data plane function requirement and/or the computing plane function requirement.
  • the NEF sends a second request to the NRF.
  • the NRF receives the second request.
  • the second request may include the data plane function requirement and/or the computing plane function requirement in the service request.
  • NRF determines SMF according to the second request.
  • S705 The NRF sends a second response to the NEF in response to the second request.
  • the MEF receives the second response.
  • the second response may include information of the SMF determined by the NRF, such as an identifier of the SMF.
  • S703-S705 are the same as S503-S505, and specific reference may be made to S503-S505.
  • NEF sends the service request to SMF.
  • SMF determines M target business plane execution function network elements, the forwarding paths between the M target business plane execution function network elements, and the processing rules of each target business plane execution function network element based on the service request and the capability information of N business plane execution function network elements. Further, SMF establishes the forwarding paths between the M target business plane execution function network elements and sends the processing rules to each target business plane execution function network element.
  • the method for implementing a service introduces a data plane and a computing plane.
  • determining the service plane execution function network element that executes the service and the forwarding path of the service plane execution function network element that executes the service and the corresponding processing rules based on the service request with data plane function requirements and/or computing plane function requirements and the capability information of the service plane execution function network element it is possible to implement services with data plane function requirements and/or computing plane function requirements.
  • the candidate service plane execution function network elements are determined by the NRF, and the forwarding paths between the M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element are determined by the SMF.
  • the forwarding paths between the M target service plane execution function network elements, the forwarding paths between the M target service plane execution function network elements, and the processing rules of each target service plane execution function network element may also be determined by the NRF. Then, the NRF may return the above information to the SMF.
  • FIG 8 is a schematic block diagram of a communication device provided in an embodiment of the present application.
  • the communication device 2000 may include a communication unit 2100 and a processing unit 2200.
  • the communication unit 2100 can implement corresponding communication functions, and the communication can be internal communication of the communication device 2000 or communication between the communication device 2000 and other devices; the processing unit 2200 can implement corresponding processing functions.
  • the communication unit 2100 can also be referred to as a communication interface or a transceiver unit.
  • the communication device 2000 may also include a storage unit, which can be used to store instructions and/or data, and the processing unit 2200 can read the instructions and/or data in the storage unit so that the device implements the aforementioned method embodiment.
  • the communication device 2000 may be a service plane control function network element in the above method embodiments, such as an SMF, or a module or chip applied to the service plane control function network element.
  • the communication device 2000 may be used to execute the steps or processes executed by the service plane control function network element in the above method embodiments.
  • the communication unit 2100 is used to receive a service request, which includes a data plane function requirement and/or a computing plane function requirement; the processing unit 2200 is used to determine M target service plane execution function network elements, the forwarding path between the M target service plane execution function network elements, and the processing rules of each of the target service plane execution function network elements according to the service request, 2 ⁇ M; the processing unit 2200 is also used to establish a forwarding path between the M target service plane execution function network elements; the communication unit 2100 is also used to send the processing rule to each of the target service plane execution function network elements, and the processing rule indicates the service operation performed by the target service plane execution function network element.
  • the processing unit 2200 is specifically used to determine the M target business plane execution function network elements based on the service request and capability information of each business plane execution function network element in the N business plane execution function network elements, the capability information including data plane capabilities and/or computing plane capabilities supported by the business plane execution function network elements, and the M target business plane execution function network elements belong to the N business plane execution function network elements.
  • the M target service plane execution function network elements include one or more of the following: at least one access network device, at least one user plane function network element, or at least one network data analysis function network element.
  • the M target service plane execution function network elements include a first access network device in the at least one access network device.
  • the communication unit 2100 is specifically configured to: send the processing rule to the first access network device through an interface between the communication device and the first access network device.
  • the communication unit 2100 is specifically configured to: receive the service request from the first network element; or The service request from the first network element is received by the network open function network element, wherein the first network element is one of the following: terminal equipment, application function network element, task anchor point, or operation maintenance management function network element.
  • the communication unit 2100 is further used to: send a first request to the network storage function network element according to the service request, the first request including the data plane function requirement and/or the computing plane function requirement, the first request is used for the network storage function network element to determine P candidate service plane execution function network elements, the M target service plane execution function network elements belong to the P candidate service plane execution function network elements; receive a first response from the network storage function network element, the first response indicates the P candidate service plane execution function network elements.
  • the processing unit 2200 is specifically used to: determine the M target service plane execution function network elements from the P candidate service plane execution function network elements.
  • the communication unit 2100 is further used to: receive registration information from some or all of the N service plane execution function network elements, where the registration information includes capability information of the service plane execution function network elements.
  • the communication unit 2100 is further used to: receive configuration information, where the configuration information includes capability information of some or all of the N service plane execution function network elements.
  • the communication device 2000 can also be used to execute the steps or processes performed by any other network element (for example, the service plane execution function network element) in the above method embodiment.
  • any other network element for example, the service plane execution function network element
  • the "unit" in the communication device 2000 can be implemented by hardware, can be implemented by software, and can also be implemented by hardware executing the corresponding software implementation.
  • the "unit” can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and/or other suitable components that support the described functions.
  • the communication unit 2100 can be replaced by a transceiver transceiver circuit (for example, it can include a receiving circuit and a transmitting circuit), and the processing unit 2200 can be replaced by a processor or a processing circuit.
  • FIG9 shows a schematic block diagram of another communication device 3000 provided in an embodiment of the present application.
  • the device 3000 may be a service plane control function network element, or may be a chip, a chip system, or a processor that supports the service plane control function network element to implement the above method.
  • the device may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the device 3000 may include one or more processors 3100, which may also be referred to as processing units, and may implement certain control functions.
  • the processor 3100 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process communication protocols and communication data
  • the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a user chip, a DU or a CU, etc.), execute a software program, and process the data of the software program.
  • the processor 3100 may also store instructions and/or data, which can be executed by the processor 3100 so that the device 3000 executes the method described in the above method embodiment.
  • the apparatus 3000 may include a communication interface 3200 for implementing receiving and sending functions.
  • the communication interface 3200 may be a transceiver circuit, an interface, an interface circuit or a transceiver.
  • the transceiver circuit, interface, interface circuit or transceiver that realizes the receiving and sending functions can be separate or integrated.
  • the above-mentioned transceiver circuit, interface, interface circuit or transceiver can be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, interface circuit or transceiver can be used for transmitting or delivering signals.
  • the device 3000 may include one or more memories 3300, on which instructions may be stored, and the instructions may be executed on the processor 3100, so that the device 3000 performs the method described in the above method embodiment.
  • data may also be stored in the memory 3300.
  • instructions and/or data may also be stored in the processor 3100.
  • the processor 3100 and the memory 3300 may be provided separately or integrated together.
  • the device 3000 may also be any other network element involved in the above method embodiment (such as a service plane execution function network element), or may be a chip, a chip system, or a processor that supports the implementation of the above method.
  • the device may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • each step in the method embodiment provided by the present application can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor executing, or a combination of hardware and software modules in a processor executing.
  • the software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.
  • the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined and performed.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synchronous link dynamic random access memory
  • DR RAM direct rambus RAM
  • the present application also provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, the computer executes each step or process executed by any network element in any of the above method embodiments.
  • the present application also provides a computer-readable storage medium, which stores program code.
  • the program code runs on a computer, the computer executes each step or process executed by any network element in any of the above method embodiments.
  • the present application also provides a communication device, including a processor and an interface, wherein the interface is used to send and/or receive signals, so that the processor executes each step or process executed by any network element in any of the above method embodiments.
  • the present application also provides a communication system, which includes at least one of a service plane execution function network element and a service plane control function network element.
  • the above-mentioned device embodiments and method embodiments completely correspond to each other, and the corresponding steps are executed by the corresponding modules or units.
  • the communication unit or communication interface executes the receiving or sending steps in the method embodiment, and the other steps except sending and receiving can be executed by the processing unit or processor.
  • a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and/or a computer.
  • applications running on a computing device and a computing device can be components.
  • One or more components may reside in a process and/or an execution thread, and a component may be located on a computer and/or distributed between two or more computers.
  • these components may be executed from various computer-readable storage media having various data structures stored thereon.
  • Components may, for example, communicate through local and/or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
  • signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a DVD
  • a semiconductor medium e.g., a solid state disk (SSD)
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种用于实现业务的方法和通信装置，应用于通信领域。该方法包括：业务面控制功能网元接收包括数据面功能需求和/或计算面功能需求的业务请求，并根据该业务请求确定目标业务面执行功能网元、目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则，以及，建立目标业务面执行功能网元之间的转发路径，向各目标业务面执行功能网元发送该处理规则。该方法引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。

Description

用于实现业务的方法和通信装置 技术领域
本申请涉及无线通信领域，尤其涉及一种用于实现业务的方法和通信装置。
背景技术
第五代(5th generation，5G)网络可以视为单一的连接模型，维护一条用户设备(userequipment，UE)到数据网络(datanetwork，DN)的用户面传输通道，从而使能UE访问DN数据业务。
目前，对于第六代(6th generation，6G)网络架构业界仍在探索中。6G网络将新增数据面和计算面功能，不再仅仅是连接模型。然而，具体如何基于数据面和计算面实现未来6G各种新业务目前尚未有相关方案。
发明内容
本申请提供了一种用于实现业务的方法和通信装置，能够实现具有数据面功能需求和/或计算面功能需求的业务。
第一方面，提供了一种用于实现业务的方法，该方法可以由业务面控制功能网元执行，也可以由业务面控制功能网元的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分业务面控制功能网元的功能的逻辑模块或软件实现。
该方法包括：接收业务请求，该业务请求包括数据面功能需求和/或计算面功能需求；根据该业务请求确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各该目标业务面执行功能网元的处理规则，2≤M；建立该M个目标业务面执行功能网元之间的转发路径，并向各该目标业务面执行功能网元发送该处理规则，该处理规则指示在该目标业务面执行功能网元所执行的业务操作。
根据本申请提供的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
在一种可能的实现方式中，业务面控制功能网元可以由会话管理功能(session management function，SMF)实现。
具体地，可以在当前的SMF中增强数据面和计算面控制功能，实现业务面控制功能网元的功能。该方案对已有网络架构改动较小，适用于未来各种用户面、数据面和计算面的各种诉求。
在一种可能的实现方式中，根据该业务请求确定M个目标业务面执行功能网元，包括，根据该业务请求和N个业务面执行功能网元中各业务面执行功能网元的能力信息确定该M个目标业务面执行功能网元，该能力信息包括该业务面执行功能网元支持的数据面能力和/或计算面能力，该M个目标业务面执行功能网元属于该N个业务面执行功能网元，M≤N。
示例性的，数据面能力可以包括下述中的一项或多项能力：数据特征提取、数据 分析、数据压缩、或者数据解压缩。
示例性的，计算面能力可以包括下述中的一项或多项能力：中央处理器(central processing unit，CPU)/图形处理器(graphics processing unit，GPU)的容量、CPU/GPU的余量、或者支持何种计算算法。
在一种可能的实现方式中，该M个目标业务面执行功能网元包括下述中的一项或多项：至少一个接入网设备、至少一个用户面功能网元、或者至少一个网络数据分析功能网元。
即，可以通过在接入网设备、用户面功能网元、或者网络数据分析功能网元中增强数据面和计算面功能，实现业务面执行功能网元的功能。该方案对已有网络架构改动较小，易于实现。
在一种可能的实现方式中，该M个目标业务面执行功能网元包括该至少一个接入网设备中的第一接入网设备。其中，向各该目标业务面执行功能网元发送该处理规则，包括：通过该业务面控制功能网元与该第一接入网设备之间的接口，向该第一接入网设备发送该处理规则。
基于该方案，业务面控制功能网元与接入网设备之间可以直接通信，不需要其他网元的转发。第一接入网设备基于处理规则执行数据面和/或计算面功能。
在一种可能的实现方式中，接收业务请求，包括：接收来自第一网元的该业务请求；或者，经由网络开放功能网元接收来自该第一网元的该业务请求。其中，该第一网元为下述之一：终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元。
也就是说，终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元都可以在有业务需求时，发送业务请求。
在一种可能的实现方式中，根据所述业务请求，确定M个目标业务面执行功能网元，包括：根据该业务请求，向网络存储功能网元发送第一请求，该第一请求包括该数据面功能需求和/或该计算面功能需求，该第一请求用于该网络存储功能网元确定P个候选业务面执行功能网元，该M个目标业务面执行功能网元属于该P个候选业务面执行功能网元；接收来自该网络存储功能网元的第一响应，该第一响应指示该P个候选业务面执行功能网元；从该P个候选业务面执行功能网元中确定该M个目标业务面执行功能网元。
在该方案中，业务面执行功能网元可以将其能力信息注册到网络存储功能网元，业务面控制功能网元可以根据业务请求的数据面功能需求和/或该计算面功能需求，请求网络存储功能网元确定P个候选业务面执行功能网元，进而从该P个候选业务面执行功能网元中确定该M个目标业务面执行功能网元。应理解，P可以等于M，也可以大于M。
在一种可能的实现方式中，在根据该业务请求，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各该目标网元的处理规则之前，该方法还包括：接收来自该N个业务面执行功能网元中部分或全部业务面执行功能网元的注册信息，该注册信息包括该业务面执行功能网元的能力信息。
在该方案中，业务面执行功能网元可以将其能力信息注册到业务面控制功能网元上。
在一种可能的实现方式中，在根据该业务请求，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各该目标网元的处理规则之前，该方法还包括：接收配置信息，该配置信息包括该N个业务面执行功能网元中部分或全部业务面执行功能网元的能力信息。
在该方案中，可以将业务面执行功能网元的能力信息注册配置在业务面控制功能网元上，节约业务面控制功能网元向其它网元查询带来的成本。
第二方面，提供了一种通信系统，该通信系统包括业务面控制功能网元和M个目标业务面执行功能网元。该业务面控制功能网元用于：接收业务请求，该业务请求包括数据面功能需求和/或计算面功能需求；根据该业务请求，确定该M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各该目标业务面执行功能网元的处理规则，2≤M≤N；建立该M个目标业务面执行功能网元之间的转发路径，并向各该目标业务面执行功能网元发送该处理规则，该处理规则指示在该目标业务面执行功能网元所执行的业务操作。该目标业务面执行功能网元用于：接收来自业务面控制功能网元的该处理规则。
根据本申请提供的通信系统，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
在一种可能的实现方式中，该目标业务面执行功能网元还用于：向网络存储功能网元或者该业务面控制功能网元发送注册信息，该注册信息包括该目标业务面执行功能网元支持的数据面能力和/或计算面能力。
在一种可能的实现方式中，该目标业务面执行功能网元为网络设备，该目标业务面执行功能网元具体用于：通过该网络设备和该业务面控制功能网元之间的接口，接收该处理规则。
第三方面，提供了一种通信装置，包括用于执行第一方面或第一方面中任一种可能实现方式中的方法的模块或单元。
第四方面，提供了一种通信装置，包括处理器，处理器与存储器耦合，存储器用于存储计算机程序或指令，处理器用于执行存储器存储的计算机程序或指令，以实现第一方面或第一方面中任一种可能实现方式中的方法。
在一种可能的实现方式中，该装置还包括与处理器耦合的存储器。
在一种可能的实现方式中，处理器为一个或多个，和/或，存储器为一个或多个。
在一种可能的实现方式中，存储器可以与处理器集成在一起，或者存储器与处理器分离设置。
在一种可能的实现方式中，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为业务面控制功能网元。示例性的，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为业务面控制功能网元中的芯片。示例性的，该通信接口可以是输入/输出接口。
第五方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。该处理 电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行上述第一方面或第一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请对处理器及各种电路的具体实现方式不做限定。
第六方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)，当计算机程序在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法。
第八方面，提供了一种芯片，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的通信装置执行上述第一方面或第一方面中任一种可能实现方式中的方法。
第九方面，提供了一种通信装置，该通信装置包括接口和处理器，该接口用于发送和/或接收信号，使得所该处理器执行上述第一方面或第一方面中任一种可能实现方式中的方法。
附图说明
图1是一种5G网络架构示意图；
图2是本申请实施例提供的一种网络架构示意图；
图3是本申请实施例提供的一种用于实现业务的方法的示意性流程图；
图4是本申请实施例提供的一种用于实现业务的方法的示意性流程图；
图5是本申请实施例提供的一种用于实现业务的方法的示意性流程图；
图6是本申请实施例提供的一种用于实现业务的方法的示意性流程图；
图7是本申请实施例提供的一种用于实现业务的方法的示意性流程图；
图8是本申请实施例提供的一种通信装置的示意性框图；
图9是本申请实施例提供的另一种通信装置的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或 a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。本申请中，“在……情况下”、“如果……”、“当……时”、“若……”等类似的描述可以替换使用。另外，网元、网络功能、设备、装置等可以相互替换；网元、网络功能、设备、装置等也可以替换为“实体”，“功能网元”也可以替换为“功能”。
图1示出了一种5G网络架构示意图。参见图1，5G网络包括用户面和控制面。其中，用户面用于传输数据，包括(无线)接入网(radio access network，(R)AN)101和用户面功能(user plane function，UPF)102。UPF可以分为中间用户面功能(intermediate user plane function，I-UPF)和锚点用户面功能(anchor user plane function，A-UPF)。控制面可以采用服务化接口(service based interface)。控制面可以包括：接入与移动性管理功能(access and mobility management function，AMF)104、会话管理功能(session management function，SMF)105、网络存储功能(network repository function，NRF)106、网络开放功能(network exposure function，NEF)107、策略控制功能(policy control function，PCF)108、等。该5G网络还可以包括网络数据分析功能(network data analytics function，NWDAF)110。另外，图1还示出了接入网络的UE 111，以及与5G网络连接的数据网络(data network，DN)103、应用功能(application function，AF)109、以及操作、管理和维护(operation，administration and maintenance，OAM)112。下面对图1所示的各网元、设备或功能进行说明。
(R)AN101：用于为特定区域的授权用户设备(userequipment，UE)(比如，图1中的UE 111)提供入网功能，负责无线资源管理，上下行数据分类和服务质量(quality of service，QoS)应用，以及与控制面网元完成信令处理，与用户面功能网元完成数据转发等功能。
UPF 102：用于分组路由和转发以及用户面数据的QoS处理等。
DN 103：用于提供传输数据的网络。
在5G通信系统中，UE接入网络后可以建立协议数据单元(protocol data unit，PDU)会话，并通过PDU会话访问DN，可以与部署在DN中的AF交互。根据用户访问的DN不同，网络可以根据网络策略选择接入DN的UPF作为为PDU会话锚点(PDU session anchor，PSA)，并通过PSA的N6接口访问AF。
AMF 104：主要用于移动性管理和接入管理等，可以用于实现移动性管理网元(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
SMF 105：主要是为用户建立并管理会话，配置用户名功能的数据包转发规则和QoS处理规则等。
NRF 106：负责对网络功能服务注册登记、状态监测等，实现网络功能服务自动化管理、选择和可扩展，并允许每个网络功能发现其它网络功能提供的服务。
NEF 107：用于提供网络开放的定制功能。还可以通过NEF网元，向外部的应用 功能网元开放5GC支持的能力，譬如提供小数据传递能力等。
PCF 108：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
AF 109：应用功能网元可以通过应用功能网元与5G系统交互，用于接入NEF或与策略框架交互进行策略控制等。
NWDAF 110：可以根据网络服务的请求数据提供网络分析服务。比如，一个网络服务请求专门的分析信息在一个特定网络切片的负载级别上。或者，网络服务可以订阅某一种服务，在网络切片变换或者到了一定的阈值时，NWDAF进行通知。
OAM112：主要用于日常网络和业务的分析、预测、规划和配置工作；对网络及其业务的测试和故障管理等的日常操作活动。
应理解，图1所示的各网元、设备或功能之间的通信接口或者服务化接口仅是示例，本申请并不排除各网元、设备或功能之间的采用其他的接口进行通信。
图1所示的5G网络可以视为单一的连接模型，维护一条UE到DN的用户面传输通道(UE—RAN—I-UPF—A-UPF--DN)，从而使能UE访问DN数据业务。
目前，对于6G网络架构业界仍在探索中，多个公司/标准组织都提出了各自的构想，但6G网络将新增数据面和计算面功能，网络不再仅仅是连接模型，已经成为业界共识。然而，具体如何定义数据面和计算面，以及如何基于数据面和计算面实现未来6G各种新业务，目前尚未有相关方案。
有鉴于此，本申请提供一种实现业务的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求和业务面执行功能网元的能力信息，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
本申请中的业务面，也可以称为功能面、用户面、数据面、或者计算面，本申请对名称不做限定。为便于理解，本文均采用业务面这一称谓来阐述。
图2是本申请提供的一种网络架构示意图。参见图2，该网络架构包括业务面控制功能网元201和业务面执行功能网元。可选地，该网络架构还可以包括下述中的一项或多项：网络开放功能网元202、网络存储功能网元203、应用功能网元204、或者网络管理功能网元205。另外，该网络架构中还示出了与接入网设备206通信的终端设备207。下面对各设备或网元进行说明。
1、业务面控制功能网元201：具有计算面和数据面控制功能，用于管理(或者调用网络存储功能203服务查询)连接资源、计算资源和数据资源，实现连接与计算、数据协同。
在一些实施例中，可以通过在会话管理功能网元中增强数据面和计算面控制功能，实现业务面控制功能网元201的功能。
在5G通信系统中，该会话管理功能网元可以是SMF。在未来通信系统中，会话管理功能网元可以是SMF，或者，还可以有其它的名称，本申请不做限定。
2、业务面执行功能网元：具有或支持一定的数据面和/或计算面功能的网元。
在一些实施例中，业务面执行功能网元可以由图2所示的接入网设备206、用户 面功能网元208或者网络数据分析功能网元209实现。或者，业务面执行功能网元可以通过在当前网络架构中新增网元(例如，图2中所示的新增网元210)来实现。
接入网设备：可以是基站(Base Station)、演进型基站(Evolved NodeB，eNodeB)、发送接收点(Transmission Reception Point，TRP)、5G移动通信系统中的下一代基站(Next Generation NodeB，gNB)、第六代(6th Generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或WiFi系统中的接入节点等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(Central Unit，CU)，也可以是分布式单元(Distributed Unit，DU)。这里的CU完成基站的无线资源控制协议和分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)的功能，还可以完成业务数据适配协议(Service Data Adaptation Protocol，SDAP)的功能；DU完成基站的无线链路控制层和介质访问控制(Medium Access Control，MAC)层的功能，还可以完成部分物理层或全部物理层的功能，有关上述各个协议层的具体描述，可以参考第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的相关技术规范。接入网设备可以是宏基站，也可以是微基站或室内站，还可以是中继节点或施主节点等。本申请的实施例对接入网设备所采用的具体技术和具体设备形态不做限定。接入网设备和终端设备可以是固定位置的，也可以是可移动的。接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和终端设备的应用场景不做限定。
在5G通信系统中，用户面功能网元可以是UPF。在未来通信系统中，用户面功能网元仍可以是UPF，或者，还可以有其它的名称，本申请不做限定。
在5G通信系统中，网络数据分析功能网元可以是NWDAF。未来通信系统中，网络数据分析功能网元仍可以是NWDAF，或者，还可以有其它的名称，本申请不做限定。
3、网络开放功能网元202：在5G通信系统中，网络开放功能网元可以是NEF。来通信系统中，网络开放功能网元仍可以是NEF，或者，还可以有其它的名称，本申请不做限定。
4、网络存储功能网元203：在5G通信系统中，网络存储功能网元可以是NRF。来通信系统中，网络存储功能网元仍可以是NRF，或者，还可以有其它的名称，本申请不做限定。
5、应用功能网元204：在5G通信系统中，应用功能网元可以是AF。来通信系统中，应用功能网元仍可以是AF，或者，还可以有其它的名称，本申请不做限定。
6、网络管理功能网元205：在5G通信系统中，网络管理功能网元可以是OAM。来通信系统中，网络管理功能网元仍可以是OAM，或者，还可以有其它的名称，本申请不做限定。
7、终端设备207：终端设备可以指(user equipment，UE)、站点(station)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless  local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、大屏、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
在一些实施例中，业务面控制功能网元201和接入网设备206之间可以直接交互信号，而不再经过其他网元(比如，AMF)的中转。
在一些实施例中，业务面控制功能网元201与业务面执行功能网元可基于服务化接口或者N4接口或者其他接口交互信号。
在一些实施例中，用户面功能网元208与网络数据分析功能网元209之间可以直接交互信号，而不再经过其他网元(比如，AMF)的中转。例如，用户面功能网元208与网络数据分析功能网元209之间可以基于N9接口或者服务化接口或者其他接口交互信号。
应理解，图2所示的各网元、设备或功能之间的通信接口或者服务化接口仅是示例，本申请并不排除各网元、设备或功能之间的采用其他的接口进行通信。
可以理解的是，本申请所涉及网元、网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
下面结合附图，对本申请提供的方法进行详细说明。可以理解，本申请提供的一些附图中主要以网元或设备作为执行主体为例来示意该方法，但本申请并不限制执行主体。例如，附图中的网元或设备也可以是支持该网元或设备实现该方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分该网元或设备的功能的逻辑模块或软件。
图3是本申请提供的一种用于实现业务的方法的示意性流程图。该方法300可以包括S301至S303，下面对各步骤进行说明。
S301，业务面控制功能网元接收业务请求。
该业务请求直接或间接的来自于第一网元。即，第一网元可以直接向业务面控制功能网元发送业务请求，或者，第一网元可以先向中间网元发送业务请求，然后中间网元再向业务面控制功能网元发送业务请求。比如，第一网元可以是终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元等。比如，中间网元可以是网络开放功能网元。
其中，该业务请求包括数据面功能需求和/或计算面功能需求。一种可能的场景，该业务请求包括数据面功能需求。例如，该业务请求是请求对特定数据进行收集(比如，汇总、去重等)、匿名化、和/或压缩。在另一种可能的场景中，该业务请求包括计算面功能需求。例如，该业务请求是请求对特定业务进行本地卸载，或者对特定业务流进行提取。
需要说明的是，一些业务可能属于数据面，也可能属于计算面，或者，一些业务可能既属于数据面又属于用户面。例如，对视频数据流进行预处理。
另外，应理解，不同的计算面需求对业务面执行功能网元的计算面能力要求可能不同，同理，不同的数据面需求对业务面执行功能网元的数据面能力要求可能不同。
S302，业务面控制功能网元根据该业务请求，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径、以及各目标业务面执行功能网元的处理规则。
在一些实施例中，可以根据该业务请求和N个业务面执行功能网元中各业务面执行功能网元的能力信息确定该M个目标业务面执行功能网元。该M个目标业务面执行功能网元属于该N个业务面执行功能网元，即，该M个目标业务面执行功能网元为该N个业务面执行功能网元中的M个业务面执行功能网元，2≤M≤N。
任一业务面执行功能网元的能力信息包括该业务面执行功能网元支持的数据面能力和/或计算面能力。
示例性的，数据面能力可以包括下述中的一项或多项能力：数据特征提取、数据分析、数据压缩、数据解压缩。
示例性的，计算面能力可以包括下述中的一项或多项能力：CPU/GPU的容量、CPU/GPU的余量、支持何种计算算法。
应理解，本申请并不排除数据面能力和/或计算面能力还包括这里未列举的其他能力，也不排除数据面能力和/或计算面能力不是这里所列举的能力的可能性。
在第一种实现方式中，业务面执行功能网元的能力信息可以是业务面执行功能网元注册到业务面控制功能网元的。
具体地，业务面执行功能网元可以向业务面控制功能网元发送注册信息，该注册信息可以包括该业务面执行功能网元的能力信息。即，业务面执行功能网元可以通过该注册信息，将其能力信息注册到业务面控制功能网元。该方式可以适用于简单组网或本地组网场景。
在第二种实现方式中，业务面执行功能网元的能力信息可以是业务面执行功能网元注册到网络存储功能网元上的，例如NRF。
具体地，业务面执行功能网元可以向网络存储功能网元发送注册信息，该注册信息可以包括该业务面执行功能网元的能力信息。即，业务面执行功能网元可以通过该注册信息，将其能力信息注册到网络存储功能网元。该方式可以适用于复杂组网或者分布式组网场景。
示例性的，在任意一个业务面执行功能网元的能力信息都是注册到网络存储功能网元的情况下，业务面执行功能网元在接收到第一网元发送的业务请求后，可以将该业务请求所包含的数据面功能需求和/或计算面功能需求发给网络存储功能网元。网络存储功能网元可以根据该数据面功能需求和/或计算面功能需求以及注册到网络存储功能网元的业务面执行功能网元的能力信息，确定P(M≤P≤N)个候选业务面执行功能网元，并将该P个候选业务面执行功能网元的信息(比如，该P个候选业务面执行功能网元的标识)返回给业务面执行功能网元。业务面执行功能网元可以根据该P个候选业务面执行功能网元，确定该M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则。其中，该M个目标业务面执行功能网元为该P个候选业务面执行功能网元中的M个候选业务面执行功能网元。
在第三种实现方式中，业务面执行功能网元的能力信息可以是配置在业务面控制 功能网元上的。例如，可以由管理系统/运维系统将业务面执行功能网元的能力信息配置在业务面控制功能网元上。
即，无需业务面执行功能网元去注册能力信息，而在业务面控制功能网元上直接配置业务面执行功能网元的能力信息。
需要说明的是，在一些实施例种，所有业务面执行功能网元都采用上述第一种实现方式或者都采用上述第二种实现方式注册能力信息。或者，所有业务面执行功能网元的能力信息都是采用上述第三种实现方式实现的。在另一些实施例中，不同业务面执行功能网元的能力信息的注册或者配置方式可能不同，比如，一些业务面控制功能网元采用上述第一种实现方式注册能力信息，另一些业务面控制功能网元采用上述第二种实现方式注册能力信息。
另外，各业务面执行功能网元支持的数据面和/或计算面能力可以不同，也可以相同，本申请对此不作限定。比如，在一种场景中，接入网设备#1支持数据特征提取、接入网设备#2支持数据压缩和数据解压缩，用户面功能网元#1同时支持数据特征提取、数据压缩和数据解压缩。
在一些实施例中，考虑到业务面控制功能网元可能有特定的服务范围，业务面控制功能网元可将自身的服务范围，和/或，支持的数据面和/或计算面能力，注册到网络存储功能网元。示例性的，业务面控制功能网元支持的数据面和/或计算面能力可以通过该业务面控制功能网元管理的业务面执行功能网元支持的数据面和/或计算面能力来标识。
对于此实施例，如果第一网元通过中间网元发送业务请求，则中间网元可以请求网络存储功能网元根据业务面控制功能网元自身的服务范围，和/或，支持的数据面和/或计算面能力，选择符合要求的业务面控制功能网元，然后再向所选择的业务面控制功能网元发送业务请求。
所述处理规则指示在目标业务面执行功能网元所执行的业务操作。即，某一目标业务面执行功能网元的处理规则是指该目标业务面执行功能网元需要执行何种操作，例如数据处理/数据分析、数据压缩/解压缩、预处理/融合处理、联邦处理(分布式)等。
举例来说，在第一种可能的场景中，该业务请求是对特定数据进行收集、匿名化、压缩。业务面控制功能网元可以确定由接入网设备#1和接入网设备#2进行压缩，由用户面功能网元#1进行收集、由网络数据分析功能网元进行匿名化。业务面控制功能网元确定建立接入网设备#1和用户面功能网元#1之间的连接、接入网设备#2和用户面功能网元#1之间的连接、以及用户面功能网元#1和网络数据分析功能网元之间的连接。接入网设备#1的处理规则是压缩、接入网设备#2的处理规则也是压缩，用户面功能网元#1的处理规则是收集以及传输到网络数据分析功能网元，网络数据分析功能网元的处理规则是匿名化。
举例来说，在第二种可能的场景中，该业务请求是对特定业务流先在本地卸载，提取出关键特征后再上传到数据中心。业务面控制功能网元可以确定由用户面功能网元#2进行数据分流并提取出关键特征、再由网络数据分析功能网元进行进一步分析处理。业务面控制功能网元确定建立用户面功能网元#2与网络数据分析功能网元之间的 连接。用户面功能网元#2的处理规则是数据分流以及传输到网络数据分析功能网元，网络数据分析功能网元的处理规则是对接收到的数据进一步处理分析。
S303，业务面控制功能网元建立M个目标业务面执行功能网元之间的转发路径，并向各目标业务面执行功能网元发送处理规则。
比如，对于上述第一种可能的场景，业务面控制功能网元建立接入网设备#1和用户面功能网元#1之间的连接、接入网设备#2和用户面功能网元#1之间的连接、以及用户面功能网元#1和网络数据分析功能网元之间的连接。并且，业务面控制功能网元分别向接入网设备#1、接入网设备#2、用户面功能网元#1和网络数据分析功能网元发送各自对应的处理规则。
根据本申请提供的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
在一些实施例中，可以通过在SMF中增强数据面和计算面控制功能，实现业务面控制功能网元的功能。该方案对已有网络架构(包括用户面功能、会话管理功能)改动较小，适用于未来各种用户面、数据面和计算面的各种诉求。
在一些实施例中，可以通过在RAN、UPF或者NWDAF中增强数据面和计算面功能，实现业务面执行功能网元的功能。该方案对已有网络架构改动较小，易于实现。
下面以在5G架构上通过增强数据面功能和计算面功能来实现本申请提供的方法为例，介绍本申请提供的方法的几个具体示例。其中，下文中的SMF、RAN、UE、UPF、AF、NRF、NEF、NWDAF依次对应方法300中的业务面控制功能网元、接入网设备、终端设备、用户面功能网元、应用功能网元、网络存储功能网元、网络开放功能网元、网络数据分析功能网元。
图4示出了本申请提供的用于实现业务的方法的一个示意性流程图。该方法400中，SMF可以直接接收业务请求，同时，业务面执行功能网元将其能力信息注册到NRF。该方法400可以包括S401至S408。下面对各步骤进行说明。
S401，业务面执行功能网元将其能力信息注册到NRF。
比如，RAN#1、RAN#2、UPF#1以及NWDAF等多个网元将其能力信息注册到NRF。
S402，第一网元向SMF发送业务请求。相应地，SMF接收该业务请求。
比如，UE或者AF在有数据面功能需求和/或计算面功能需求的情况下，向SMF发送业务请求。其中，该业务请求可以包括数据面功能需求和/或计算面功能需求。
S403，SMF根据该业务请求，向NRF发送第一请求。相应地，NRF接收来自SMF的第一请求。
第一请求可以包括业务请求中的数据面功能需求和/或计算面功能需求。
S404，NRF根据第一请求，确定P个候选业务面执行功能网元。
其中，该P个候选业务面执行功能网元为将能力信息注册到NRF的N个业务面执行功能网元中的部分或全部业务面执行功能网元，M≤P≤N。
S405，NRF向SMF发送响应于第一请求的第一响应。相应地，SMF接收该第一 响应。
其中，第一响应用于指示该P个候选业务面执行功能网元，比如，第一响应可以包括该P个候选业务面执行功能网元的标识。举例来说，该P个候选业务面执行功能网元可以是RAN#1、RAN#2、UPF#1和NWDAF。
S406，SMF根据第一响应，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径及各目标业务面执行功能网元的处理规则。
比如，SMF可以根据该P个候选业务面执行功能网元之间的拓扑关系和/或该P个候选业务面执行功能网元的负载信息等，确定该M个目标业务面执行功能网元。其中，该M个目标业务面执行功能网元为该P个候选业务面执行功能网元中的M个候选业务面执行功能网元。进一步地，SMF还可以确定该M个目标业务面执行功能网元之间的转发路径及各目标业务面执行功能网元的处理规则。
应理解，如果P＝M，则该P个候选业务面执行功能网元为该M个目标业务面执行功能网元。
举例来说，该业务请求是对特定数据进行收集、匿名化、压缩。SMF可以确定由RAN#1和RAN#2进行压缩，由UPF#1进行收集、由NWDAF进行匿名化。SMF确定建立RAN#1和UPF#1之间的连接、RAN#2和UPF#1之间的连接、以及UPF#1和NWDAF之间的连接。RAN#1的处理规则是压缩、RAN#2的处理规则也是压缩，UPF#1的处理规则是收集以及传输到NWDAF，NWDAF的处理规则是匿名化。
S407，SMF建立该M个目标业务面执行功能网元之间的转发路径。
比如，SMF建立RAN#1和UPF#1之间的连接、RAN#2和UPF#1之间的连接、以及UPF#1和NWDAF之间的连接。
S408，SMF向各目标业务面执行功能网元发送对应的处理规则。相应地，各目标业务面执行功能网元接收来自SMF的处理规则。
比如，SMF向RAN#1发送处理规则#1，处理规则#1为压缩，向RAN#2发送处理规则#2，处理规则#2也是压缩，向UPF#1发送处理规则#3，处理规则#3是收集以及传输到NWDAF，向NWDAF发送处理规则#4，处理规则#4是匿名化。相应地，RAN#1和RAN#2接收到业务后，将分别对该业务进行压缩，然后传输给UPF#1。UPF#1对接收到的业务进行收集，并传输给NWDAF。NWDAF对接收到的业务进行匿名化。
本申请提供的用于实现业务的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求和业务面执行功能网元的能力信息，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
图5示出了本申请提供的用于实现业务的方法的一个示意性流程图。该方法500中，SMF可以间接接收业务请求，同时，业务面执行功能网元将其能力信息注册到NRF。该方法500可以包括S501至S512。下面对各步骤进行说明。
S501，业务面执行功能网元将其能力信息注册到NRF。
该步骤与S401相同，可以参考S401。
S502，第一网元向NEF发送业务请求。相应地，NEF接收该业务请求。
比如，UE或者AF在有数据面功能需求和/或计算面功能需求的情况下，向NEF 发送业务请求。其中，该业务请求可以包括数据面功能需求和/或计算面功能需求。
S503，NEF向NRF发送第二请求。相应地，NRF接收第二请求。
其中，第二请求可以包括业务请求中的数据面功能需求和/或计算面功能需求。
S504，NRF根据第二请求，确定SMF。
考虑到SMF可能有特定的服务范围，SMF可将自身的服务范围，和/或，支持的数据面和/或计算面能力，注册到NRF。其中，SMF支持的数据面和/或计算面能力可以通过该SMF的业务面执行功能网元支持的数据面和/或计算面能力来标识。
在NRF接收到第二请求后，NRF可以根据数据面功能需求和/或计算面功能需求，和/或，SMF注册到NRF的信息，确定合适的SMF。
S505，NRF向NEF发送响应于第二请求的第二响应。相应地，MEF接收第二响应。
其中，第二响应可以包括NRF确定的SMF的信息，比如包括该SMF的标识。
S506，NEF向SMF发送该业务请求。
S507-S512，与S403-S408相同。
即，SMF根据该业务请求，请求NRF确定候选业务面执行功能网元。NRF确定候选业务面执行功能网元后，返回给SMF。SMF再进一步确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径及各目标业务面执行功能网元的处理规则。并且，SMF该M个目标业务面执行功能网元之间的转发路径，以及向各目标业务面执行功能网元发送对应的处理规则。
本申请提供的用于实现业务的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求和业务面执行功能网元的能力信息，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
图6示出了本申请提供的实现业务的方法的一个示意性流程图。该方法600中，SMF可以直接接收业务请求，同时，业务面执行功能网元将其能力信息注册到SMF。该方法600可以包括S601至S605。下面对各步骤进行说明。
S601，业务面执行功能网元将其能力信息注册到SMF。
比如，RAN#1、RAN#2、UPF#1以及NWDAF等多个网元将其能力信息注册到NRF。
应理解，S601也可以替换为在SMF上配置业务面执行功能网元的能力信息。
S602，第一网元向SMF发送业务请求。相应地，SMF接收该业务请求。
比如，UE或者AF在有数据面功能需求和/或计算面功能需求的情况下，向SMF发送业务请求。其中，该业务请求可以包括数据面功能需求和/或计算面功能需求。
S603，SMF根据该业务请求和N个业务面执行功能网元能力信息，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则。
应理解，该N个业务面执行功能网元为在S601中注册了能力信息的业务面执行功能网元。
举例来说，该业务请求是对特定数据进行收集、匿名化、压缩。SMF可以根据该 业务请求和N个业务面执行功能网元的能力信息，确定RAN#1和RAN#2进行压缩，由UPF#1进行收集、由NWDAF进行匿名化。SMF确定建立RAN#1和UPF#1之间的连接、RAN#2和UPF#1之间的连接、以及UPF#1和NWDAF之间的连接。RAN#1的处理规则是压缩、RAN#2的处理规则也是压缩，UPF#1的处理规则是收集以及传输到NWDAF，网NWDAF的处理规则是匿名化。
S604，SMF建立该M个目标业务面执行功能网元之间的转发路径。
S605，SMF向各目标业务面执行功能网元的处理规则。
比如，SMF建立RAN#1和UPF#1之间的连接、RAN#2和UPF#1之间的连接、以及UPF#1和NWDAF之间的连接。并且，SMF向RAN#1发送处理规则#1，处理规则#1为压缩，向RAN#2发送处理规则#2，处理规则#2也是压缩，向UPF#1发送处理规则#3，处理规则#3是收集以及传输到NWDAF，向NWDAF发送处理规则#4，处理规则#4是匿名化。相应地，RAN#1和RAN#2接收到业务后，将分别对该业务进行压缩，然后传输给UPF#1。UPF#1对接收到的业务进行收集，并传输给NWDAF。NWDAF对接收到的业务进行匿名化。
本申请提供的用于实现业务的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求和业务面执行功能网元的能力信息，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
图7示出了本申请提供的实现业务的方法的一个示意性流程图。该方法700中，SMF可以间接接收业务请求，同时，业务面执行功能网元将其能力信息注册到SMF。该方法700可以包括S701至S709。下面对各步骤进行说明。
S701，业务面执行功能网元将其能力信息注册到SMF。
该步骤与S601相同，可以参考S601。
S702，第一网元向NEF发送业务请求。相应地，NEF接收该业务请求。
比如，UE或者AF在有数据面功能需求和/或计算面功能需求的情况下，向NEF发送业务请求。其中，该业务请求可以包括数据面功能需求和/或计算面功能需求。
S703，NEF向NRF发送第二请求。相应地，NRF接收第二请求。
其中，第二请求可以包括业务请求中的数据面功能需求和/或计算面功能需求。
S704，NRF根据第二请求，确定SMF。
S705，NRF向NEF发送响应于第二请求的第二响应。相应地，MEF接收第二响应。
其中，第二响应可以包括NRF确定的SMF的信息，比如包括该SMF的标识。
应理解，S703-S705与S503-S505相同，具体可以参考S503-S505。
S706，NEF向SMF发送该业务请求。
S707-S709，与S603-S605相同。
即，SMF根据该业务请求和N个业务面执行功能网元能力信息，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则。进一步地，SMF建立该M个目标业务面执行功能网元之间的转发路径，并向各目标业务面执行功能网元的处理规则。
本申请提供的用于实现业务的方法，引入了数据面和计算面，通过根据具有数据面功能需求和/或计算面功能需求的业务请求和业务面执行功能网元的能力信息，可以确定执行业务的业务面执行功能网元、执行业务的业务面执行功能网元的转发路径和分别对应的处理规则，从而能够实现具有数据面功能需求和/或计算面功能需求的业务。
需要说明的是，上文描述的方法400和方法500中，由NRF确定候选业务面执行功能网元，由SMF确定M个目标业务面执行功能网元之间的转发路径、该M个目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则。然而，在一些实施例中，也可以由NRF确定M个目标业务面执行功能网元之间的转发路径、该M个目标业务面执行功能网元之间的转发路径以及各目标业务面执行功能网元的处理规则。然后，NRF可以将上述信息返回给SMF。
上文描述了本申请提供的方法实施例，下文将描述本申请提供的装置实施例。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图8是本申请实施例提供的通信装置的示意性框图。如图8所示，该通信装置2000可以包括通信单元2100和处理单元2200。通信单元2100可以实现相应的通信功能，该通信可以是该通信装置2000的内部通信也可以是该通信装置2000与其他装置的通信；处理单元2200可以实现相应的处理功能。通信单元2100还可以称为通信接口或收发单元。可选地，该通信装置2000还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元2200可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
在一种可能的设计中，该通信装置2000可以是上文方法实施例中的业务面控制功能网元，比如SMF，还可以是应用于业务面控制功能网元的模块或芯片。该通信装置2000可以用于执行上述各方法实施例中业务面控制功能网元所执行的步骤或流程。
具体地，通信单元2100，用于接收业务请求，该业务请求包括数据面功能需求和/或计算面功能需求；处理单元2200，用于根据该业务请求，确定M个目标业务面执行功能网元、该M个目标业务面执行功能网元之间的转发路径以及各该目标业务面执行功能网元的处理规则，2≤M；该处理单元2200还用于，建立该M个目标业务面执行功能网元之间的转发路径；该通信单元2100还用于，向各该目标业务面执行功能网元发送该处理规则，该处理规则指示在该目标业务面执行功能网元所执行的业务操作。
可选地，该处理单元2200具体用于：根据该业务请求和N个业务面执行功能网元中各业务面执行功能网元的能力信息，确定该M个目标业务面执行功能网元，该能力信息包括该业务面执行功能网元支持的数据面能力和/或计算面能力，该M个目标业务面执行功能网元属于该N个业务面执行功能网元。
可选地，该M个目标业务面执行功能网元包括下述中的一项或多项：至少一个接入网设备、至少一个用户面功能网元、或者至少一个网络数据分析功能网元。
可选地，该M个目标业务面执行功能网元包括该至少一个接入网设备中的第一接入网设备。其中，该通信单元2100具体用于：通过该通信装置与该第一接入网设备之间的接口，向该第一接入网设备发送该处理规则。
可选地，该通信单元2100具体用于：接收来自第一网元的该业务请求；或者，经 由网络开放功能网元接收来自该第一网元的该业务请求。其中，该第一网元为下述之一：终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元。
可选地，该通信单元2100还用于：根据该业务请求，向网络存储功能网元发送第一请求，该第一请求包括该数据面功能需求和/或该计算面功能需求，该第一请求用于该网络存储功能网元确定P个候选业务面执行功能网元，该M个目标业务面执行功能网元属于该P个候选业务面执行功能网元；接收来自该网络存储功能网元的第一响应，该第一响应指示该P个候选业务面执行功能网元。该处理单元2200具体用于：从该P个候选业务面执行功能网元中确定该M个目标业务面执行功能网元。
可选地，该通信单元2100还用于：接收来自该N个业务面执行功能网元中部分或全部业务面执行功能网元的注册信息，该注册信息包括该业务面执行功能网元的能力信息。
可选地，该通信单元2100还用于：接收配置信息，该配置信息包括该N个业务面执行功能网元中部分或全部业务面执行功能网元的能力信息。
关于通信装置2000中各单元所执行的步骤或流程，具体可以参考上文方法实施例，这里不再详述。
应理解，通信装置2000还可以用于执行上述方法实施例中由其他任一网元(比如，业务面执行功能网元)所执行的步骤或流程，具体可以参考上文方法实施例，这里不再详述。
应理解，通信装置2000中的“单元”可以通过硬件实现，也可以通过软件实现，还可以通过硬件执行相应的软件实现。比如，所述“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。又如，通信单元2100可以由收发机收发电路(例如可以包括接收电路和发送电路)替代，处理单元2200可以由处理器或处理电路替代。
图9示出了本申请实施例提供的另一通信装置3000的示意性框图。该装置3000可以是业务面控制功能网元，也可以是支持业务面控制功能网元实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
该装置3000可以包括一个或多个处理器3100，所述处理器3100也可以称为处理单元，可以实现一定的控制功能。所述处理器3100可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，用于、用户芯片，DU或CU等)进行控制，执行软件程序，处理软件程序的数据。
在一种可选的设计中，处理器3100也可以存有指令和/或数据，所述指令和/或数据可以被所述处理器3100运行，使得所述装置3000执行上述方法实施例中描述的方法。
在另一种可选的设计中，该装置3000可以包括用于实现接收和发送功能的通信接口3200。例如该通信接口3200可以是收发电路、接口、接口电路或收发器等。用于 实现接收和发送功能的收发电路、接口、接口电路或收发器可以是分开的，也可以集成在一起。上述收发电路、接口、接口电路或收发器可以用于代码/数据的读写，或者，上述收发电路、接口、接口电路或收发器可以用于信号的传输或传递。
可选地，该装置3000中可以包括一个或多个存储器3300，其上可以存有指令，该指令可在处理器3100上被运行，使得该装置3000执行上述方法实施例中描述的方法。可选的，存储器3300中还可以存储有数据。可选的，处理器3100中也可以存储指令和/或数据。处理器3100和存储器3300可以单独设置，也可以集成在一起。
应理解，该装置3000还可以是上述方法实施例中涉及的其他任一网元(比如业务面执行功能网元)，也可以是支持该实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
应理解，在一种可能的设计中，本申请提供的方法实施例中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、 同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中任一网元所执行的各个步骤或流程。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中任一网元所执行的各个步骤或流程。
本申请还提供一种通信装置，包括处理器和接口，该接口用于发送和/或接收信号，使得该处理器执行上述任一方法实施例中任一网元所执行的各个步骤或流程。
本申请还提供一种通信系统，其包括业务面执行功能网元和业务面控制功能网元中的至少一项。
上述各个装置实施例和方法实施例完全对应，由相应的模块或单元执行相应的步骤，例如通信单元或通信接口执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元或处理器执行。
在本申请的实施例中，各术语及英文缩略语均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读存储介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以基于前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执 行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (23)

  1. 一种用于实现业务的方法，其特征在于，应用于业务面控制功能网元，所述方法包括：
    接收业务请求，所述业务请求包括数据面功能需求和/或计算面功能需求；
    根据所述业务请求确定M个目标业务面执行功能网元、所述M个目标业务面执行功能网元之间的转发路径以及各所述目标业务面执行功能网元的处理规则，2≤M；
    建立所述M个目标业务面执行功能网元之间的转发路径，并向各所述目标业务面执行功能网元发送所述处理规则，所述处理规则指示在所述目标业务面执行功能网元所执行的业务操作。
  2. 如权利要求1所述的方法，其特征在于，所述根据所述业务请求确定M个目标业务面执行功能网元，包括：
    根据所述业务请求和N个业务面执行功能网元中各业务面执行功能网元的能力信息，确定所述M个目标业务面执行功能网元，所述能力信息包括所述业务面执行功能网元支持的数据面能力和/或计算面能力，所述M个目标业务面执行功能网元属于所述N个业务面执行功能网元。
  3. 如权利要求1或2所述的方法，其特征在于，所述M个目标业务面执行功能网元包括下述中的一项或多项：至少一个接入网设备、至少一个用户面功能网元、或者至少一个网络数据分析功能网元。
  4. 如权利要求3所述的方法，其特征在于，所述M个目标业务面执行功能网元包括所述至少一个接入网设备中的第一接入网设备；
    其中，所述向各所述目标业务面执行功能网元发送所述处理规则，包括：
    通过所述业务面控制功能网元与所述第一接入网设备之间的接口，向所述第一接入网设备发送所述处理规则。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述接收业务请求，包括：
    接收来自第一网元的所述业务请求；或者，
    经由网络开放功能网元接收来自所述第一网元的所述业务请求；
    其中，所述第一网元为下述之一：终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元。
  6. 如权利要求1-5中任一项所述的方法，其特征在于，所述根据所述业务请求，确定M个目标业务面执行功能网元，包括：
    根据所述业务请求，向网络存储功能网元发送第一请求，所述第一请求包括所述数据面功能需求和/或所述计算面功能需求，所述第一请求用于所述网络存储功能网元确定P个候选业务面执行功能网元，所述M个目标业务面执行功能网元属于所述P个候选业务面执行功能网元；
    接收来自所述网络存储功能网元的第一响应，所述第一响应指示所述P个候选业务面执行功能网元；
    从所述P个候选业务面执行功能网元中确定所述M个目标业务面执行功能网元。
  7. 如权利要求2所述的方法，其特征在于，在所述根据所述业务请求，确定M个目标业务面执行功能网元、所述M个目标业务面执行功能网元之间的转发路径以及各 所述目标网元的处理规则之前，所述方法还包括：
    接收来自所述N个业务面执行功能网元中部分或全部业务面执行功能网元的注册信息，所述注册信息包括所述业务面执行功能网元的能力信息。
  8. 如权利要求2所述的方法，其特征在于，在所述根据所述业务请求，确定M个目标业务面执行功能网元、所述M个目标业务面执行功能网元之间的转发路径以及各所述目标网元的处理规则之前，所述方法还包括：
    接收配置信息，所述配置信息包括所述N个业务面执行功能网元中部分或全部业务面执行功能网元的能力信息。
  9. 一种通信系统，其特征在于，包括：
    业务面控制功能网元和M个目标业务面执行功能网元；
    所述业务面控制功能网元用于：
    接收业务请求，所述业务请求包括数据面功能需求和/或计算面功能需求；
    根据所述业务请求，确定所述M个目标业务面执行功能网元、所述M个目标业务面执行功能网元之间的转发路径以及各所述目标业务面执行功能网元的处理规则，2≤M≤N；
    建立所述M个目标业务面执行功能网元之间的转发路径，并向各所述目标业务面执行功能网元发送所述处理规则，所述处理规则指示在所述目标业务面执行功能网元所执行的业务操作；
    所述目标业务面执行功能网元用于：
    接收来自业务面控制功能网元的所述处理规则。
  10. 如权利要求9所述的通信系统，其特征在于，所述目标业务面执行功能网元还用于：
    向网络存储功能网元或者所述业务面控制功能网元发送注册信息，所述注册信息包括所述目标业务面执行功能网元支持的数据面能力和/或计算面能力。
  11. 如权利要求9或10所述的通信系统，其特征在于，所述目标业务面执行功能网元为网络设备，所述目标业务面执行功能网元具体用于：
    通过所述网络设备和所述业务面控制功能网元之间的接口，接收所述处理规则。
  12. 一种通信装置，其特征在于，包括：
    通信单元，用于接收业务请求，所述业务请求包括数据面功能需求和/或计算面功能需求；
    处理单元，用于根据所述业务请求，确定M个目标业务面执行功能网元、所述M个目标业务面执行功能网元之间的转发路径以及各所述目标业务面执行功能网元的处理规则，2≤M；
    所述处理单元还用于，建立所述M个目标业务面执行功能网元之间的转发路径；
    所述通信单元还用于，向各所述目标业务面执行功能网元发送所述处理规则，所述处理规则指示在所述目标业务面执行功能网元所执行的业务操作。
  13. 如权利要求12所述的通信装置，其特征在于，所述处理单元具体用于：
    根据所述业务请求和N个业务面执行功能网元中各业务面执行功能网元的能力信息，确定所述M个目标业务面执行功能网元，所述能力信息包括所述业务面执行功能 网元支持的数据面能力和/或计算面能力，所述M个目标业务面执行功能网元属于所述N个业务面执行功能网元。
  14. 如权利要求12或13所述的通信装置，其特征在于，所述M个目标业务面执行功能网元包括下述中的一项或多项：至少一个接入网设备、至少一个用户面功能网元、或者至少一个网络数据分析功能网元。
  15. 如权利要求14所述的通信装置，其特征在于，所述M个目标业务面执行功能网元包括所述至少一个接入网设备中的第一接入网设备；
    其中，所述通信单元具体用于：
    通过所述通信装置与所述第一接入网设备之间的接口，向所述第一接入网设备发送所述处理规则。
  16. 如权利要求12-15中任一项所述的通信装置，其特征在于，所述通信单元具体用于：
    接收来自第一网元的所述业务请求；或者，
    经由网络开放功能网元接收来自所述第一网元的所述业务请求；
    其中，所述第一网元为下述之一：终端设备、应用功能网元、任务锚点、或者操作维护管理功能网元。
  17. 如权利要求12-16中任一项所述的通信装置，其特征在于，所述通信单元还用于：
    根据所述业务请求，向网络存储功能网元发送第一请求，所述第一请求包括所述数据面功能需求和/或所述计算面功能需求，所述第一请求用于所述网络存储功能网元确定P个候选业务面执行功能网元，所述M个目标业务面执行功能网元属于所述P个候选业务面执行功能网元；
    接收来自所述网络存储功能网元的第一响应，所述第一响应指示所述P个候选业务面执行功能网元；
    所述处理单元具体用于：
    从所述P个候选业务面执行功能网元中确定所述M个目标业务面执行功能网元。
  18. 如权利要求13所述的通信装置，其特征在于，所述通信单元还用于：
    接收来自所述N个业务面执行功能网元中部分或全部业务面执行功能网元的注册信息，所述注册信息包括所述业务面执行功能网元的能力信息。
  19. 如权利要求13所述的通信装置，其特征在于，所述通信单元还用于：
    接收配置信息，所述配置信息包括所述N个业务面执行功能网元中部分或全部业务面执行功能网元的能力信息。
  20. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1-8中任一项所述方法。
  21. 一种通信装置，其特征在于，包括处理器和接口，所述接口用于发送和/或接收信号，使得所述处理器执行如权利要求1-8中任一项所述方法。
  22. 一种可读存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时，使得所述计算机执行如权利要求1-8中任一项所述方法。
  23. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得所述计算机执行如权利要求1-8中任一项所述方法。
PCT/CN2023/085700 2023-03-31 2023-03-31 用于实现业务的方法和通信装置 Ceased WO2024197896A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2023/085700 WO2024197896A1 (zh) 2023-03-31 2023-03-31 用于实现业务的方法和通信装置
CN202380096248.XA CN120982151A (zh) 2023-03-31 2023-03-31 用于实现业务的方法和通信装置
EP23929479.6A EP4683380A4 (en) 2023-03-31 2023-03-31 METHOD FOR IMPLEMENTING A COMMUNICATION SERVICE AND DEVICE

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/085700 WO2024197896A1 (zh) 2023-03-31 2023-03-31 用于实现业务的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2024197896A1 true WO2024197896A1 (zh) 2024-10-03

Family

ID=92903180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/085700 Ceased WO2024197896A1 (zh) 2023-03-31 2023-03-31 用于实现业务的方法和通信装置

Country Status (3)

Country Link
EP (1) EP4683380A4 (zh)
CN (1) CN120982151A (zh)
WO (1) WO2024197896A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113573367A (zh) * 2021-07-05 2021-10-29 中国联合网络通信集团有限公司 无线资源的分配方法及装置
WO2022031553A1 (en) * 2020-08-04 2022-02-10 Intel Corporation Data plane for big data and data as a service in next generation cellular networks
CN114698025A (zh) * 2020-12-28 2022-07-01 华为技术有限公司 一种通信方法及节点
CN115226163A (zh) * 2021-04-20 2022-10-21 华为技术有限公司 一种通信方法及装置
CN115484620A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 一种算力资源调度的方法以及相关装置
WO2023046012A1 (zh) * 2021-09-24 2023-03-30 维沃移动通信有限公司 感知业务处理方法、终端及网络侧设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10601932B2 (en) * 2017-06-09 2020-03-24 At&T Intellectual Property I, L.P. Next generation mobility core network controller for service delivery
WO2022235690A1 (en) * 2021-05-04 2022-11-10 Intel Corporation Enhanced service function chaining in next generation cellular networks

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031553A1 (en) * 2020-08-04 2022-02-10 Intel Corporation Data plane for big data and data as a service in next generation cellular networks
CN114698025A (zh) * 2020-12-28 2022-07-01 华为技术有限公司 一种通信方法及节点
CN115226163A (zh) * 2021-04-20 2022-10-21 华为技术有限公司 一种通信方法及装置
CN115484620A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 一种算力资源调度的方法以及相关装置
CN113573367A (zh) * 2021-07-05 2021-10-29 中国联合网络通信集团有限公司 无线资源的分配方法及装置
WO2023046012A1 (zh) * 2021-09-24 2023-03-30 维沃移动通信有限公司 感知业务处理方法、终端及网络侧设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4683380A4 *

Also Published As

Publication number Publication date
CN120982151A (zh) 2025-11-18
EP4683380A4 (en) 2026-04-29
EP4683380A1 (en) 2026-01-21

Similar Documents

Publication Publication Date Title
US11051192B2 (en) Network data analytics in a communications network
US20210274418A1 (en) Information Transmission Method and Apparatus
US20240056496A1 (en) Method and Apparatus for Selecting Edge Application Server
US10321381B2 (en) Device, system, and method for customizing user-defined mobile network
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
JP7717700B2 (ja) ネットワーク機能登録方法、発見方法、装置、デバイス及び媒体
EP4436112A1 (en) Communication method and apparatus
CN116074807A (zh) 一种数据收集方法及通信装置
CN116846445A (zh) 小区信息的配置方法、装置、可读存储介质及芯片系统
US9439169B2 (en) Reducing paging delays using location analytics in communications networks
WO2024197896A1 (zh) 用于实现业务的方法和通信装置
WO2024033833A1 (en) Apparatus, method, and computer program
US20250300907A1 (en) Network service method, communication apparatus, and communication system
WO2025139787A1 (zh) 通信方法和通信装置
WO2025160971A1 (zh) 无线通信的方法及设备
WO2025092843A1 (zh) 通信方法及相关装置
WO2025015561A1 (zh) 无线通信的方法和通信装置
WO2025209416A1 (zh) 通信方法及通信装置
WO2025208506A1 (zh) 无线通信的方法、终端设备和网络设备
WO2025107300A1 (zh) 数据传输方法、终端设备及网络设备
WO2025025996A1 (zh) 服务质量监测方法、装置、系统及存储介质
WO2025097379A1 (zh) 无线通信的方法及通信设备
WO2024197587A1 (zh) 通信方法及通信装置
WO2025098105A1 (zh) 一种边缘应用服务器发现方法及装置
WO2025086050A1 (zh) 一种提供网络服务的方法、装置以及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23929479

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023929479

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023929479

Country of ref document: EP

Effective date: 20251017

ENP Entry into the national phase

Ref document number: 2023929479

Country of ref document: EP

Effective date: 20251017

ENP Entry into the national phase

Ref document number: 2023929479

Country of ref document: EP

Effective date: 20251017

ENP Entry into the national phase

Ref document number: 2023929479

Country of ref document: EP

Effective date: 20251017

ENP Entry into the national phase

Ref document number: 2023929479

Country of ref document: EP

Effective date: 20251017