Method, service system, functional entity, storage medium and computer program product for establishing a service

Abstract

The embodiment of the application provides a method for establishing a service, a service system, a device for establishing a service, a functional entity, a storage medium and a computer program product, wherein the method comprises the following steps: a first functional entity receives a first service request, the first service request is used for requesting to execute a first service, the first service represents a service which needs to dispatch one or more capabilities to execute; based on the first service request, configuration information about the first service is sent to one second functional entity in a plurality of second functional entities, and the plurality of second functional entities are used for providing the one or more capabilities for executing the first service.

Description

Technical Field

[0001] This application relates to the field of wireless technology, and in particular to a method for establishing a service, a service system, a device for establishing a service, a functional entity, a storage medium, and a computer program product. Background Technology

[0002] Currently, there is a need for the network side to provide end-to-end support for emerging services such as image classification, speech recognition, and cloud gaming, encompassing multiple capabilities throughout their entire lifecycle. However, in related technologies, the service establishment process is primarily triggered by the core network, and the access network cannot perceive service requirements, thus hindering the effective invocation of multi-dimensional services. Summary of the Invention

[0003] To address the related technical issues, embodiments of this application provide a method for establishing a business, a business system, an apparatus for establishing a business, a functional entity, a storage medium, and a computer program product.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for establishing a business function, applied to a first functional entity, the method comprising:

[0006] Receive a first service request, the first service request is used to request the execution of a first service, the first service represents a service that requires scheduling one or more capabilities to be executed;

[0007] Based on the first service request, configuration information about the first service is sent to one of a plurality of second functional entities, wherein the plurality of second functional entities are used to provide one or more of the capabilities for executing the first service.

[0008] In the above scheme, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0009] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0010] In the above scheme, receiving the first service request includes:

[0011] Receive the first service request sent by the base station and / or terminal and / or core network side; or,

[0012] The system receives the first service request sent by a third functional entity, which is used to forward the first service request sent by the base station and / or terminal and / or core network side to the first functional entity.

[0013] In the above scheme, the first service request carries first information, which is used to indicate one or more capabilities; and / or,

[0014] The method further includes:

[0015] The system receives first information sent by the base station and / or the core network side, wherein the first information is used to indicate one or more capabilities, and the first information is determined by the base station and / or the core network side based on the service policy of the first service.

[0016] In the above scheme, the configuration information includes one or more of the following:

[0017] The business type of the first service;

[0018] The identifier of the first service;

[0019] The identifier of the service flow carrying the first service;

[0020] The second information is used to indicate the plurality of second functional entities;

[0021] The third information is used to indicate the initiator of the first service request.

[0022] In the above scheme, one of the plurality of second functional entities is determined based on one or more of the following:

[0023] The load of the second functional entity;

[0024] The capabilities of the second functional entity;

[0025] The business type of the first service;

[0026] The coverage area of ​​the second functional entity.

[0027] In the above scheme, the configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0028] This application embodiment also provides a method for establishing a business, applied to a second functional entity, the method comprising:

[0029] Receive configuration information regarding the first service; among which,

[0030] The first service characterizes a service that requires scheduling one or more capabilities to execute; the configuration information is used to be sent to multiple second functional entities, which are used to provide the one or more capabilities for executing the first service.

[0031] In the above scheme, receiving configuration information about the first service includes:

[0032] Receive the configuration information about the first service sent by the first functional entity; or,

[0033] Receive configuration information about the first service from one of the plurality of second functional entities.

[0034] In the above scheme, one of the other second functional entities among the plurality of second functional entities is determined based on one or more of the following:

[0035] The load of the second functional entity;

[0036] The capabilities of the second functional entity;

[0037] The business type of the first service;

[0038] The coverage area of ​​the second functional entity.

[0039] In the above scheme, after receiving the configuration information about the first service sent by the first functional entity, the method further includes:

[0040] Send configuration information about the first service to each of the other second functional entities among the plurality of functional entities.

[0041] In the above scheme, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0042] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0043] In the above scheme, the configuration information includes one or more of the following:

[0044] The business type of the first service;

[0045] The service identifier of the first service;

[0046] The identifier of the service flow carrying the first service;

[0047] The second information is used to indicate the plurality of second functional entities;

[0048] The third information is used to indicate the initiator of the first service request.

[0049] In the above scheme, the configuration information is sent through the Xn interface, F1 interface, or SBI interface.

[0050] This application embodiment also provides a business system, including: a first functional entity and a plurality of second functional entities; wherein,

[0051] The first functional entity is used to implement any of the methods for establishing services on the first functional entity side; and / or, the second functional entity is used to implement any of the methods for establishing services on the second functional entity side.

[0052] Among the above schemes,

[0053] The first functional entity is deployed at a core network node, and the plurality of second functional entities are deployed at different access network nodes; or,

[0054] The first functional entity and one of the plurality of second functional entities are deployed at the first access network node, and the other second functional entities, excluding the first one, are deployed at different second access network nodes; or,

[0055] In the above scheme, the third functional entity is deployed on the same node as the first functional entity, or the first functional entity is deployed on the first access network node and the third functional entity is deployed on the core network node.

[0056] In the above scheme, the first functional entity and the plurality of second functional entities are all deployed at the first base station; wherein,

[0057] The first base station adopts a CU-DU separation architecture, and the first functional entity and one of the multiple second functional entities are jointly deployed in the CU of the first base station. The other second functional entities among the multiple second functional entities, except for the first second functional entity, are respectively deployed in different DUs of the first base station.

[0058] In the above scheme, the first functional entity and one of the plurality of second functional entities are jointly deployed in the CU of the first base station, and the other second functional entities, excluding the first one, are deployed in the DU of one or more second base stations; wherein,

[0059] The first base station and the plurality of second base stations all adopt a CU-DU separation architecture.

[0060] This application also provides an apparatus for establishing a business, comprising:

[0061] The first receiving unit is configured to receive a first service request, the first service request being used to request the execution of a first service, the first service representing a service that requires scheduling one or more capabilities to be executed.

[0062] The first sending unit is configured to send configuration information about the first service to one of a plurality of second functional entities based on the first service request, wherein the plurality of second functional entities are configured to provide one or more capabilities for executing the first service.

[0063] This application also provides an apparatus for establishing a business, comprising:

[0064] The second receiving unit is used to receive configuration information about the first service; wherein,

[0065] The first service characterizes a service that requires scheduling one or more capabilities to execute; the configuration information is used to be sent to multiple second functional entities, which are used to provide the one or more capabilities for executing the first service.

[0066] This application embodiment also provides a first functional entity, including: a first processor and a first communication interface; wherein,

[0067] The first communication interface is used for:

[0068] Receive a first service request, the first service request is used to request the execution of a first service, the first service represents a service that requires scheduling one or more capabilities to be executed;

[0069] Based on the first service request, configuration information about the first service is sent to one of a plurality of second functional entities, wherein the plurality of second functional entities are used to provide one or more of the capabilities for executing the first service.

[0070] This application embodiment also provides a second functional entity, including: a second processor and a second communication interface; wherein,

[0071] The second communication interface is used for:

[0072] Receive configuration information regarding the first service; among which,

[0073] The first service characterizes a service that requires scheduling one or more capabilities to execute; the configuration information is used to be sent to multiple second functional entities, which are used to provide the one or more capabilities for executing the first service.

[0074] This application embodiment also provides a first functional entity, including: a first processor and a first memory for storing computer programs capable of running on the processor.

[0075] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the methods for establishing services on the first functional entity side.

[0076] This application embodiment also provides a second functional entity, including: a second processor and a second memory for storing computer programs capable of running on the processor.

[0077] Wherein, when the second processor runs the computer program, it executes the steps of any of the methods for establishing a service on the second functional entity side.

[0078] This application embodiment also provides a storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the steps of the method for establishing any of the above-mentioned first functional entity side services, or the steps of the method for establishing any of the above-mentioned second functional entity side services.

[0079] This application also provides a computer program product, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the method for establishing any of the first functional entities or the steps of the method for establishing any of the second functional entities.

[0080] In the method, system, apparatus, functional entity, storage medium, and computer program product for establishing a service provided in this application embodiment, for a service that requires scheduling one or more capabilities to execute, the first functional entity sends configuration information about the service to one of the multiple second functional entities used to execute the aforementioned one or more capabilities based on the corresponding service request. In this way, all of these second functional entities can execute the corresponding capabilities based on the configuration information of the service, thereby realizing the effective invocation of multi-dimensional services and supporting the service requirements of various multi-dimensional services. Attached Figure Description

[0081] Figure 1 This is a schematic diagram illustrating the implementation process of a method for establishing a business according to an embodiment of this application;

[0082] Figure 2 This is a schematic diagram illustrating the implementation process of another method for establishing a business according to an embodiment of this application;

[0083] Figure 3 A schematic diagram illustrating the implementation principle of the method for establishing services based on related technologies and embodiments of this application;

[0084] Figure 4 This is a schematic diagram of the architecture of a business system according to an embodiment of this application;

[0085] Figure 5 This is a schematic diagram of the architecture of another business system according to an embodiment of this application;

[0086] Figure 6 This is a schematic diagram of the architecture of a third type of business system according to an embodiment of this application;

[0087] Figure 7 This is a schematic diagram of the architecture of the fourth type of business system in this application embodiment;

[0088] Figure 8 This is a schematic diagram of the architecture of the fifth type of business system in this application;

[0089] Figure 9 This is a schematic diagram illustrating a scenario for an application embodiment of this application;

[0090] Figure 10 A schematic diagram of the interaction flow of a method for establishing a business according to an application embodiment of this application;

[0091] Figure 11 This is a schematic diagram of the structure of an apparatus for establishing a service according to an embodiment of this application;

[0092] Figure 12 This is a schematic diagram of the structure of an apparatus for establishing a service according to another embodiment of this application;

[0093] Figure 13 This is a schematic diagram of the structure of the first functional entity in an embodiment of this application;

[0094] Figure 14 This is a schematic diagram of the structure of the second functional entity in an embodiment of this application. Detailed Implementation

[0095] Currently, the emergence of new services such as image classification, speech recognition, and cloud gaming not only places higher demands on communication capabilities but also requires the assistance of AI, computing, and sensing capabilities. Therefore, the network side needs to provide end-to-end support for the entire lifecycle of these new services, offering multi-dimensional capabilities. The access network side, with its proximity to users and distributed characteristics, may deploy multi-dimensional capabilities there in the future. However, current technologies primarily involve the core network triggering PDU sessions and instructing the access network to establish corresponding radio bearers to achieve the service establishment process. However, in this process, the access network cannot perceive the service requirements, thus hindering the effective invocation of multi-dimensional services.

[0096] Based on this, in various embodiments of this application, for services that require scheduling one or more capabilities to be executed, the first functional entity sends configuration information about the service to multiple second functional entities used to execute the aforementioned one or more capabilities based on the corresponding service request. In this way, these second functional entities can execute the corresponding capabilities based on the configuration information of the service, thereby realizing the effective invocation of multi-dimensional services and supporting the service requirements of various multi-dimensional services.

[0097] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0098] This application provides a method for establishing a business function, applied to a first functional entity, which can also be described as a business management function. (Refer to...) Figure 1 The method includes:

[0099] Step 101: Receive the first service request.

[0100] The first service request is used to request the execution of a first service, which represents a service that requires scheduling one or more capabilities to be executed.

[0101] Step 102: Based on the first service request, send configuration information about the first service to one of the multiple second functional entities. These multiple second functional entities are used to provide one or more capabilities for executing the first service.

[0102] Here, the second functional entity can also be described as a capability execution function, which is used to execute different capabilities to provide corresponding services.

[0103] When the first functional entity receives a service request for a corresponding service, based on one or more capabilities that need to be scheduled when the service is executed, in this embodiment of the application, the first functional entity selects only one second functional entity from among the multiple second functional entities that execute these one or more capabilities to establish a control signaling connection, and sends the configuration information of the service to the selected second functional entity, so that the configuration information of the service can be transmitted to other second functional entities through the selected second functional entity. In this way, the corresponding second functional entity can execute the corresponding capability based on the configuration information of the service, thereby supporting the scheduling requirements of the multi-dimensional capabilities of the service.

[0104] During the service establishment process, the second functional entity selected by the first functional entity establishes a connection with one or more other second functional entities to issue control signaling to the other second functional entities, instructing them to perform corresponding capabilities. Here, when there are multiple other second functional entities, the second functional entity selected by the first functional entity can issue control signaling to these multiple other second functional entities in parallel based on the established connection.

[0105] For example, the first service is a service that integrates communication, sensing, and AI capabilities. The second functional entity selected by the first functional entity has AI inference capabilities. In addition, two other second functional entities have communication capabilities and sensing capabilities, respectively. Then, the second functional entity selected by the first functional entity performs AI inference. At the same time, based on the sensing requirements of the first service, the second functional entity instructs the second functional entity with sensing capabilities to provide sensing data, and based on the communication QoS requirements of the first service, it instructs the second functional entity with communication capabilities to establish an air interface bearer to transmit the service data of the first service.

[0106] In one embodiment, one of the plurality of second functional entities is determined based on one or more of the following:

[0107] The load of the second functional entity;

[0108] The capabilities of the second functional entity;

[0109] The business type of the first business;

[0110] The coverage area of ​​the second functional entity.

[0111] In one embodiment, the first service needs to schedule one or more capabilities, including but not limited to any one or more of the following:

[0112] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0113] Corresponding to the above capabilities, the main functions of the second functional entity used to perform computing capabilities include: sensing computing nodes and providing computing services; the main functions of the second functional entity used to perform AI capabilities include: training, inference, downloading, monitoring, and exposing AI models; the main functions of the second functional entity used to perform communication capabilities include: establishing signaling bearers and establishing data bearers that meet the QoS requirements of various multi-dimensional capabilities; the main functions of the second functional entity used to perform sensing capabilities include: providing sensing data; and the main functions of the second functional entity used to perform data capabilities include: collecting data measured by base stations and terminals, providing data required for AI tasks, and providing data to external users.

[0114] In practical applications, the first functional entity can determine, based on the received service request, what capabilities need to be scheduled for service execution. For example, based on the indication information for multi-dimensional capabilities in the service request, it can determine the capabilities required for the service execution. Therefore, in one embodiment, the first service request carries first information, which indicates one or more capabilities.

[0115] And / or, the base station and / or core network side may also determine the scheduling capabilities required for the execution of the first service based on the service policy of the first service, such as the QoS policy. In this way, the first functional entity can confirm, based on the instructions from the base station and / or core network side, what scheduling capabilities are required for the execution of the service. Based on this, in another embodiment, the method for establishing a service further includes:

[0116] The system receives first information sent by the base station and / or the core network side, wherein the first information is used to indicate one or more capabilities, and the first information is determined by the base station and / or the core network side based on the service policy of the first service.

[0117] In one embodiment, receiving a first service request includes:

[0118] Receive the first service request sent by the base station and / or terminal and / or core network side; or

[0119] Receive the first service request sent by the third functional entity.

[0120] The third functional entity is used to forward the first service request sent by the base station and / or terminal and / or core network side to the first functional entity.

[0121] Here, the first service request can be initiated by the access network side, i.e., the base station, or by the core network side, or by the terminal. In addition, a third functional entity can be defined, which can also be understood as an interface function, used to receive service requests initiated by the base station and / or the terminal and / or the core network, and forward the service request to the first functional entity.

[0122] Specifically, the interface function is responsible for receiving service requests initiated by base stations and / or terminals and / or the core network, determining whether a communication, computing, and AI capability fusion process needs to be established, and forwarding it to the service management function to determine the specific service type. During implementation, the interface function and the service management function can be deployed independently or jointly. For example, the air interface function can be merged with the service management function triggered by air interface messages; the core network interface function can be merged with the service management function triggered by core network messages.

[0123] In one embodiment, the configuration information includes one or more of the following:

[0124] The business type of the first business;

[0125] The identifier of the first business;

[0126] The identifier of the business flow that carries the primary business;

[0127] The second information is used to indicate multiple second functional entities;

[0128] The third piece of information is used to indicate the initiator of the first business request.

[0129] The identifier of the service flow carrying the first service can be marked by the access network node. All data mapped to the same service flow identifier will be mapped to the same radio bearer on the access network side for the same processing.

[0130] In one embodiment, the configuration information is sent via the Xn interface, the F1 interface, or the (SBI, ServiceBasedInterface) interface.

[0131] Among them, the Xn interface is the downlink interface between gNBs, the F1 interface is the interface between the gNB and various functions in the Evolved Packet Core (EPC), and the SBI is the interface between nodes in the core network. In practical applications, the interface functions can be used to select the appropriate interface for transmitting configuration information based on the location of the communicating parties in the network.

[0132] Corresponding to the method for establishing services on the first functional entity side of the above embodiments, this application embodiment also provides a method for establishing services, applied to a second functional entity. (Refer to...) Figure 2 The method includes:

[0133] Step 201: Receive configuration information for the first service.

[0134] The first service represents a service that requires scheduling one or more capabilities to execute. Configuration information is sent to multiple second functional entities, which provide one or more capabilities for executing the first service.

[0135] Here, the second functional entity can also be described as a capability execution function, used to execute different capabilities. When the first functional entity receives a service request for a corresponding service, based on one or more capabilities that need to be scheduled when the service is executed, in this embodiment, the first functional entity selects only one second functional entity from among the multiple second functional entities executing these one or more capabilities to establish a control signaling connection, and sends the configuration information of the service to that one second functional entity, so that the configuration information of the service can be transmitted to other second functional entities through that one second functional entity. In this way, the corresponding second functional entity can execute the corresponding capability based on the configuration information of the service, thereby supporting the scheduling requirements of the multi-dimensional capabilities of the service.

[0136] During the service establishment process, the second functional entity selected by the first functional entity establishes a connection with one or more other second functional entities to issue control signaling to the other second functional entities, instructing them to perform corresponding capabilities. Here, when there are multiple other second functional entities, the second functional entity selected by the first functional entity can issue control signaling to these multiple other second functional entities in parallel based on the established connection.

[0137] For example, the first service is a service that integrates communication, sensing, and AI capabilities. The second functional entity selected by the first functional entity has AI inference capabilities. In addition, two other second functional entities have communication capabilities and sensing capabilities, respectively. Then, the second functional entity selected by the first functional entity performs AI inference. At the same time, based on the sensing requirements of the first service, the second functional entity instructs the second functional entity with sensing capabilities to provide sensing data, and based on the communication QoS requirements of the first service, it instructs the second functional entity with communication capabilities to establish an air interface bearer to transmit the service data of the first service.

[0138] In one embodiment, one of the plurality of second functional entities is determined based on one or more of the following:

[0139] The load of the second functional entity;

[0140] The capabilities of the second functional entity;

[0141] The business type of the first business;

[0142] The coverage area of ​​the second functional entity.

[0143] Therefore, in practical applications, a single second functional entity can be selected by a first functional entity. Correspondingly, in one embodiment, receiving configuration information about the first service includes receiving configuration information about the first service sent by the first functional entity. Alternatively, if a single second functional entity is not selected by the first functional entity, it needs to receive configuration information about the first service from a second functional entity selected by the first functional entity. That is, in one embodiment, receiving configuration information about the first service includes receiving configuration information about the first service sent by one of the multiple second functional entities.

[0144] In one embodiment, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0145] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0146] Corresponding to the above capabilities, the main functions of the second functional entity used to perform computing capabilities include: sensing computing nodes and providing computing services; the main functions of the second functional entity used to perform AI capabilities include: training, inference, downloading, monitoring, and exposing AI models; the main functions of the second functional entity used to perform communication capabilities include: establishing signaling bearers and establishing data bearers that meet the QoS requirements of various multi-dimensional capabilities; the main functions of the second functional entity used to perform sensing capabilities include: providing sensing data; and the main functions of the second functional entity used to perform data capabilities include: collecting data measured by base stations and terminals, providing data required for AI tasks, and providing data to external users.

[0147] In one embodiment, one of the plurality of second functional entities is determined based on one or more of the following:

[0148] The load of the second functional entity;

[0149] The capabilities of the second functional entity;

[0150] The business type of the first service;

[0151] The coverage area of ​​the second functional entity.

[0152] In one embodiment, after receiving configuration information about a first service sent by a first functional entity, the method for establishing the service further includes:

[0153] Send configuration information about the first service to each of the other second functional entities among the multiple functional entities.

[0154] In one embodiment, the configuration information includes one or more of the following:

[0155] The business type of the first business;

[0156] The business identifier of the first business;

[0157] The identifier of the business flow that carries the primary business;

[0158] The second information is used to indicate multiple second functional entities;

[0159] The third piece of information is used to indicate the initiator of the first business request.

[0160] The identifier of the service flow carrying the first service can be marked by the access network node. All data mapped to the same service flow identifier will be mapped to the same radio bearer on the access network side for the same processing.

[0161] In one embodiment, the configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0162] Among them, the Xn interface is the downlink interface between gNBs, the F1 interface is the interface between the gNB and various functions in the EPC, and the SBI is the interface between nodes in the core network. In practical applications, the appropriate interface is selected for transmitting configuration information based on the location of the communicating parties in the network.

[0163] Combination Figure 3 From the traditional business establishment process and the business establishment process provided in this application embodiment, it is easy to see that in the traditional solution, the business request is sent to the core network, and the business establishment process is triggered by the core network. The access network side does not directly perceive the business needs. Thus, when multi-dimensional capabilities are invoked, certain business delays may occur during the capability invocation process, and resource utilization may be reduced. In contrast, the method provided in this application embodiment allows the first functional entity to be deployed on the access network side. In this way, the business request can be sent to the access network, and the access network side has the ability to perceive business needs. Therefore, it can flexibly select capability execution entities for capability invocation according to the capabilities required for business execution, realizing unified scheduling of multiple nodes, improving resource utilization. At the same time, each capability execution entity focuses on the capabilities it is responsible for, which can improve service efficiency.

[0164] The above sections introduced the relevant implementation principles of the first, second, and third functional entities in the method of establishing services in the embodiments of this application. The following section describes the networking methods that the above functional entities may involve in actual deployment.

[0165] Based on this, embodiments of this application provide a business system, including: a first functional entity and a plurality of second functional entities; wherein, the first functional entity is used to implement any of the methods for establishing a business on the side of the first functional entity; and / or, the second functional entities are used to implement any of the methods for establishing a business on the side of the second functional entity.

[0166] In one embodiment, the third functional entity is deployed on the same node as the first functional entity, or the first functional entity is deployed on the first access network node and the third functional entity is deployed on the core network node.

[0167] Figure 4 The diagram illustrates the architecture of a business system according to an embodiment of this application, wherein a first functional entity is deployed at a core network node, and multiple second functional entities are deployed at different access network nodes.

[0168] For example, refer to Figure 4The service management function, i.e., the first functional entity, and the interface function, i.e., the third functional entity, are both deployed in the Access and Mobility Management Function (AMF). The two capability execution functions, i.e., the second functional entities, are deployed in two gNBs respectively. The service management function and the capability execution function selected by the service management function, i.e., the first capability execution function, interact through the NG interface. The capability execution function selected by the service management function interacts with the other capability execution function based on the Xn interface.

[0169] based on Figure 4 In practical applications, the AMF receives service requests from third-party applications or other core network elements. The AMF determines the corresponding service type and selects a capability execution function. Then, the AMF initiates a service establishment request to the capability execution function selected by the AMF (i.e., gNB 1), which means sending the service configuration information to the capability execution function selected by the AMF. This configuration information includes at least the service type, service identifier, service flow identifier, and node information of other capability execution functions, and may also include the identifier of the service requester.

[0170] Among them, other capability execution functions are capability execution functions other than those selected by AMF that are used to provide capabilities for services. The node information of other capability execution functions includes node address information, capability type, etc.

[0171] The AMF sends service configuration information to the capability execution function selected by the AMF. This configuration information can be carried by PDU session management messages, paging messages, or other new types of NG interface messages.

[0172] After the capability execution function selected by the AMF receives the service configuration information, the capability execution function selected by the AMF initiates a service establishment request to other capability execution functions, that is, sends the service configuration information to other capability execution functions. This configuration information includes at least the service type, service identifier, service flow identifier, and node information of other capability execution functions, and may also include the identifier of the service requester.

[0173] Among them, the capability execution function selected by the AMF sends service configuration information to other capability execution functions. This configuration information can be carried by Xn Setup, NG-RAN node Configuration Update, RAN Paging or other new Xn interface messages.

[0174] Next, the other capability execution functions send a service establishment request response to the capability execution function selected by the AMF. After receiving the service establishment request response, the capability execution function selected by the AMF sends a service establishment request response to the AMF, thereby completing the service establishment process.

[0175] Figure 5 This paper illustrates the architecture of another business system according to an embodiment of this application. (Refer to...) Figure 5 The first functional entity (service management function) and one second functional entity (first capability execution function) are deployed on the first access network node (gNB1), another second functional entity (capability execution function) is deployed on a different second access network node (gNB2), and the third functional entity (interface function) is deployed on the core network node. The two capability execution functions interact with each other through the Xn interface.

[0176] based on Figure 5 In practical applications, the AMF receives service requests from the Session Management Function (SMF), Network Data Analytics Function (NWDAF), Location Management Function (LMF), Application Function (AF), other core network elements, or terminals. The AMF determines if a new radio-side service needs to be established and sends the service request to gNB 1 (the node for the service management function and the first capability execution function). This service request includes the identifier of the requesting party. The service request sent by the AMF can be carried using a new type of NG interface message.

[0177] Next, gNB 1 determines the service type and selects the capability execution function to be deployed on gNB 2. Then, gNB 1 sends a service establishment request to gNB 2, that is, sends the service configuration information to gNB 2. This configuration information includes at least the service type, service identifier, service flow identifier, and other node information of capability execution functions, and may also include the identifier of the service requester.

[0178] Among them, gNB 1 sends service configuration information to gNB 2, which can be carried by Xn Setup, NG-RANnode Configuration Update, RAN Paging or other new types of Xn interface messages.

[0179] Then, gNB 2 sends a service establishment request response to gNB 1, thereby completing the service establishment process.

[0180] Figure 6The diagram shows the architecture of a third type of business system according to an embodiment of this application, wherein a first functional entity, a second functional entity, and a third functional entity are deployed on a first access network node, and another second functional entity is deployed on a different second access network node.

[0181] For example, refer to Figure 6 The interface function, namely the third functional entity, is deployed in AMF. The business management function is deployed in business management function and one capability execution function (first capability execution function) are both deployed in gNB 1. Another capability execution function is deployed in gNB 2. The two capability execution functions interact with each other through the Xn interface.

[0182] based on Figure 6 In practical applications, gNB 1 receives service requests from other core network elements, other gNBs, or terminals. gNB 1 determines whether a new radio service needs to be established, identifies the corresponding service type, and selects a capability to execute the function.

[0183] Subsequently, gNB 1 initiates a service establishment request to gNB 2, that is, sends the service configuration information to the capability execution function selected by gNB 1. This configuration information includes at least the service type, service identifier, service flow identifier, and node information of other capability execution functions, and may also include the identifier of the service requester.

[0184] gNB 1 sends service configuration information to gNB 2. This configuration information can be carried by Xn Setup, NG-RAN nodeConfiguration Update, RAN Paging, or other new types of Xn interface messages.

[0185] Then, gNB 2 sends a service establishment request response to gNB 1, thereby completing the service establishment process.

[0186] Figure 7 The diagram illustrates the architecture of a fourth service system according to an embodiment of this application. In this system, a first functional entity and multiple second functional entities are deployed in a first base station. The first base station adopts a CU-DU separation architecture, and the first functional entity (service management function) and one of the multiple second functional entities (first capability execution function) are jointly deployed in the CU of the first base station. The other second functional entities among the multiple second functional entities are deployed in different DUs of the first base station.

[0187] based on Figure 7In practical applications, the CU in the first base station receives service requests from other core network elements, other gNBs, or terminals. The CU determines whether a new radio service needs to be established, identifies the corresponding service type, and selects the capability in the CU to execute the function.

[0188] Subsequently, the CU initiates a service establishment request to the two capability execution functions deployed on DU 1 and DU 2 respectively. That is, it sends the service configuration information to the two capability execution functions on DU 1 and DU 2. The configuration information includes at least the service type, service identifier, service flow identifier and other node information of the capability execution functions, and may also include the identifier of the service requester.

[0189] The CU sends service configuration information to the DU, which can be carried by F1Setup, gNB-DUConfiguration Update, gNB-CU Configuration Update, gNB-DUResourceCoordination, or other new F1 interface messages.

[0190] Afterwards, DU 1 and DU 2 send service establishment request responses to CU respectively, thereby completing the service establishment process.

[0191] Figure 8 This paper illustrates the architecture diagram of a fifth type of business system according to an embodiment of this application. (Refer to...) Figure 8 The first functional entity (service management function) and one of the multiple second functional entities (first capability execution function) are both deployed in the CU 1 of the first base station. The other second functional entities among the multiple second functional entities, except for the aforementioned second functional entity, are deployed in the DU of one or more second base stations. The first base station and the multiple second base stations all adopt a CU-DU separation architecture.

[0192] based on Figure 8 In practical applications, the CU in the first base station receives service requests from other core network elements, other gNBs, or terminals. The CU determines whether a new radio service needs to be established, identifies the corresponding service type, and selects the capability in the CU to execute the function.

[0193] Subsequently, CU 1 initiates a service establishment request to CU 2, that is, sends the service configuration information to the capability execution function deployed on DU 2 in the second base station. The configuration information includes at least the service type, service identifier, service flow identifier and other node information of capability execution functions, and may also include the identifier of the service requester.

[0194] Specifically, CU1 sends service configuration information to CU2, which can be carried by Xn Setup, NG-RAN nodeConfiguration Update, RAN Paging, or other new Xn interface messages.

[0195] Subsequently, CU 2 sends the service configuration information to DU 2, instructing the capability execution function on DU 2 to provide the corresponding capability. This configuration information includes at least the service type, service identifier, service flow identifier, and other node information of the capability execution function, and may also include the identifier of the service requester.

[0196] Specifically, CU 2 sends service configuration information to DU 2. This configuration information can be carried by F1Setup, gNB-DUConfiguration Update, gNB-CU Configuration Update, gNB-DU ResourceCoordination, or other new F1 interface messages.

[0197] Subsequently, DU 2 sends a service establishment request response to CU 2. After receiving the service establishment request response, CU 2 sends a service establishment request response to CU 1, thereby completing the service establishment process.

[0198] It should be noted that, Figure 7 In this context, the business management functions deployed on CU 2 are mainly used for transparent transmission between the business management functions on CU 1 and the capability execution functions on DU 2.

[0199] Based on the business system architecture shown above, it can be seen that in the embodiments of this application, the first, second, and third functional entities can be flexibly deployed in core network nodes or access network nodes according to networking requirements. Furthermore, for CU-DU separated base station architectures, these functional entities can also be flexibly deployed. Based on different system architectures, configuration information regarding service capability calls can be carried through Xn Setup, NG-RAN node Configuration Update, RAN Paging, or a new Xn interface message type; it may also be carried through F1Setup, gNB-DUConfiguration Update, gNB-CU Configuration Update, gNB-DU Resource Coordination, or a new F1 interface message type; this configuration information may be interacted through a new SBI interface. In addition, corresponding to specific capabilities, the configuration information may also include specific configurations. For example, for AI capabilities, the configuration information may include AI model parameters; for computing capabilities, the configuration information may include computing power level requirements; and for sensing capabilities, the configuration information may include sensing accuracy requirements.

[0200] The following application examples further illustrate the method for establishing services in this application.

[0201] Reference Figure 9 The illustrated scenario illustrates intelligent path planning for drones, which requires the integration of scheduling communication capabilities and AI capabilities to plan flight paths for the drones. Specifically, business management and interface functions are deployed in the AMF (Advanced Management Function), while the primary capability execution function and AI capability execution function are deployed in gNB 1. The AI ​​capability execution function performs the drone's path reasoning task. Furthermore, communication capability execution functions are deployed in gNB 2 and gNB 3 respectively, used to collect the drone's location information, channel information, etc., in real time, and to feed back the AI ​​reasoning results to the drone.

[0202] In the above scenarios, combined Figure 10 The illustrated business setup interaction flow includes:

[0203] 1. The AMF receives service requests, determines the service type, selects the first capability to perform the function as the first base station, and selects the other capabilities to perform the functions as the second and third base stations.

[0204] 2. The AMF issues a service establishment request, which includes at least the following: service type, service identifier, service flow identifier, address information and capability type of the second and third base stations, and may also include the identifier of the service request initiator.

[0205] 3. The first base station initiates a service establishment request to the second base station. The service establishment request shall at least carry: service type, service identifier, service flow identifier, and may also include the identifier of the service request initiator.

[0206] 4. The second base station sends a service establishment request response, which includes dedicated random access resources and radio bearer configuration.

[0207] 5. The first base station sends a service establishment request response, which includes a service identifier, a service flow identifier, and node information for the capability execution function.

[0208] 6. The AMF sends a service request response to the drone. This service establishment request response includes the service identifier, the service flow identifier, and the relevant configuration of the second base station.

[0209] Here, the first base station uses AI capabilities to perform drone path reasoning and instructs the drone to move to the coverage area of ​​the third base station. This instruction can be sent directly to the drone by the first base station or by the second base station.

[0210] 7. The first base station initiates a service establishment request to the third base station, which includes the requested capability type, service identifier, service flow identifier, and may also include the node information of the source node, the second base station, and the identifier of the service request initiator.

[0211] 8. The second base station sends a service establishment request response, which includes dedicated random access resources and radio bearer configuration.

[0212] 9. The first base station issues a service update configuration, which includes the service identifier, the service flow identifier, and the relevant configuration of the third base station.

[0213] To implement the method for establishing services on the first functional entity side of this application embodiment, this application embodiment also provides a service establishment apparatus, which is disposed on the first functional entity, such as... Figure 11 As shown, the device includes:

[0214] The first receiving unit 1101 is used to receive a first service request, which is used to request the execution of a first service. The first service represents a service that requires scheduling one or more capabilities to be executed.

[0215] The first sending unit 1102 is used to send configuration information about the first service to one of a plurality of second functional entities based on the first service request. The plurality of second functional entities are used to provide one or more capabilities for executing the first service.

[0216] In one embodiment, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0217] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0218] In one embodiment, the first receiving unit 1101 is used for:

[0219] Receive the first service request sent by the base station and / or terminal and / or core network side; or

[0220] The system receives a first service request sent by a third functional entity, which is used to forward the first service request sent by the base station and / or terminal and / or core network side to the first functional entity.

[0221] In one embodiment, the first service request carries first information, which is used to indicate one or more capabilities; and / or,

[0222] The apparatus for establishing the business also includes:

[0223] The third receiving unit is configured to receive first information sent by the base station and / or the core network side, wherein the first information is used to indicate one or more capabilities, and the first information is determined by the base station and / or the core network side based on the service policy of the first service.

[0224] In one embodiment, the configuration information includes one or more of the following:

[0225] The business type of the first business;

[0226] The identifier of the first business;

[0227] The identifier of the business flow that carries the primary business;

[0228] The second information is used to indicate multiple second functional entities;

[0229] The third piece of information is used to indicate the initiator of the first business request.

[0230] One of the plurality of second functional entities is determined based on one or more of the following:

[0231] The load of the second functional entity;

[0232] The capabilities of the second functional entity;

[0233] The business type of the first business;

[0234] The coverage area of ​​the second functional entity.

[0235] This configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0236] In practical applications, the first receiving unit 1101, the first sending unit 1102, and the third receiving unit can be implemented by the communication interface in the device for establishing the service.

[0237] To implement the method for establishing services on the second functional entity side of this application embodiment, this application embodiment also provides a service establishment apparatus, which is disposed on the second functional entity, such as... Figure 12 As shown, the device includes:

[0238] The second receiving unit 1201 is used to receive configuration information about the first service.

[0239] The first service represents a service that requires scheduling one or more capabilities to execute. This configuration information is used to be sent to multiple second functional entities, which provide the one or more capabilities for executing the first service.

[0240] In one embodiment, the second receiving unit 1201 is used for:

[0241] Receive configuration information about the first service sent by the first functional entity; or,

[0242] Receive configuration information about the first service from one of the multiple second functional entities.

[0243] In one embodiment, one of the plurality of second functional entities is determined based on one or more of the following:

[0244] The load of the second functional entity;

[0245] The capabilities of the second functional entity;

[0246] The business type of the first business;

[0247] The coverage area of ​​the second functional entity.

[0248] In one embodiment, the means for establishing a service further includes:

[0249] The second sending unit is configured to send configuration information about the first service to each of the other second functional entities among the plurality of functional entities after receiving configuration information about the first service sent by the first functional entity.

[0250] In one embodiment, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0251] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0252] In one embodiment, the configuration information includes one or more of the following:

[0253] The business type of the first business;

[0254] The business identifier of the first business;

[0255] The identifier of the business flow that carries the primary business;

[0256] The second information is used to indicate multiple second functional entities;

[0257] The third piece of information is used to indicate the initiator of the first business request.

[0258] In one embodiment, the configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0259] In practical applications, the first receiving unit 1201 and the second sending unit can be implemented by the communication interface in the device for establishing the service.

[0260] It should be noted that the above embodiments of the apparatus for establishing services are only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the apparatus can be divided into different program modules to complete all or part of the processing described above. Furthermore, the apparatus for establishing services and the method embodiments for establishing services provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0261] Based on the hardware implementation of the above program modules, and in order to implement the method of the first functional entity side of the embodiments of this application, the embodiments of this application also provide a first functional entity, such as... Figure 13 As shown, the first functional entity 1300 includes:

[0262] The first communication interface 1301 is capable of exchanging information with other network nodes;

[0263] The first processor 1302 is connected to the first communication interface 1301 to enable information interaction with other network nodes. When running a computer program, it executes the methods provided by one or more technical solutions on the first functional entity side. The computer program is stored in the first memory 1303.

[0264] Specifically, the first communication interface 1301 is used to receive a first service request, which requests the execution of a first service, wherein the first service represents a service that requires scheduling one or more capabilities to be executed; and is used to send configuration information about the first service to one of a plurality of second functional entities based on the first service request, wherein the plurality of second functional entities are used to provide one or more capabilities for the execution of the first service.

[0265] In one embodiment, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0266] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0267] In one embodiment, the first communication interface 1301 is used for:

[0268] Receive the first service request sent by the base station and / or terminal and / or core network side; or

[0269] The system receives a first service request sent by a third functional entity, which is used to forward the first service request sent by the base station and / or terminal and / or core network side to the first functional entity.

[0270] In one embodiment, the first service request carries first information, which is used to indicate one or more capabilities; and / or,

[0271] The first communication interface 1301 is also used for:

[0272] The system receives first information sent by the base station and / or the core network side, wherein the first information is used to indicate one or more capabilities, and the first information is determined by the base station and / or the core network side based on the service policy of the first service.

[0273] In one embodiment, the configuration information includes one or more of the following:

[0274] The business type of the first business;

[0275] The identifier of the first business;

[0276] The identifier of the business flow that carries the primary business;

[0277] The second information is used to indicate multiple second functional entities;

[0278] The third piece of information is used to indicate the initiator of the first business request.

[0279] One of the plurality of second functional entities is determined based on one or more of the following:

[0280] The load of the second functional entity;

[0281] The capabilities of the second functional entity;

[0282] The business type of the first business;

[0283] The coverage area of ​​the second functional entity.

[0284] This configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0285] It should be noted that the specific processing procedures of the first processor 1302 and the first communication interface 1301 can be understood by referring to the above method.

[0286] Of course, in practical applications, the various components in the first functional entity 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to implement communication between these components. In addition to a data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 13 The general designated all buses as Bus System 1304.

[0287] The first memory 1303 in this embodiment is used to store various types of data to support the operation of the first functional entity 1300. Examples of such data include any computer program used to operate on the first functional entity 1300.

[0288] The methods disclosed in the above embodiments of this application can be applied to the first processor 1302, or implemented by the first processor 1302. The first processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 1302. The first processor 1302 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1302 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 1303. The first processor 1302 reads the information in the first memory 1303 and completes the steps of the aforementioned method in combination with its hardware.

[0289] In an exemplary embodiment, the first functional entity 1300 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0290] Based on the hardware implementation of the above program modules, and in order to implement the method on the second functional entity side of the embodiments of this application, the embodiments of this application also provide a second functional entity, such as... Figure 14 As shown, the second functional entity 1400 includes:

[0291] The second communication interface 1401 is capable of exchanging information with other network nodes;

[0292] The second processor 1402 is connected to the second communication interface 1401 to enable information interaction with other network nodes. When running a computer program, it executes the methods provided by one or more technical solutions on the second functional entity side. The computer program is stored on the second memory 1403.

[0293] Specifically, the second communication interface 1401 is used to receive configuration information about the first service.

[0294] The first service represents a service that requires scheduling one or more capabilities to execute. This configuration information is used to be sent to multiple second functional entities, which provide the one or more capabilities for executing the first service.

[0295] In one embodiment, the second communication interface 1401 is used for:

[0296] Receive configuration information about the first service sent by the first functional entity; or,

[0297] Receive configuration information about the first service from one of the multiple second functional entities.

[0298] In one embodiment, one of the plurality of second functional entities is determined based on one or more of the following:

[0299] The load of the second functional entity;

[0300] The capabilities of the second functional entity;

[0301] The business type of the first business;

[0302] The coverage area of ​​the second functional entity.

[0303] In one embodiment, the second communication interface 1401 is further used for:

[0304] After receiving the configuration information about the first service from the first functional entity, the configuration information about the first service is sent to each of the other second functional entities among the multiple functional entities.

[0305] In one embodiment, the first service needs to schedule one or more capabilities, including any one or more of the following:

[0306] Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

[0307] In one embodiment, the configuration information includes one or more of the following:

[0308] The business type of the first business;

[0309] The business identifier of the first business;

[0310] The identifier of the business flow that carries the primary business;

[0311] The second information is used to indicate multiple second functional entities;

[0312] The third piece of information is used to indicate the initiator of the first business request.

[0313] In one embodiment, the configuration information is sent via the Xn interface, F1 interface, or SBI interface.

[0314] It should be noted that the specific processing procedures of the second processor 1402 and the second communication interface 1401 can be understood by referring to the above method.

[0315] Of course, in practical applications, the various components in the second functional entity 1400 are coupled together via a bus system 1404. It can be understood that the bus system 1404 is used to implement communication between these components. In addition to a data bus, the bus system 1404 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 14 The general designated all buses as Bus System 1404.

[0316] The second memory 1403 in this embodiment is used to store various types of data to support the operation of the second functional entity 1400. Examples of such data include any computer program used to operate on the second functional entity 1400.

[0317] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 1402. The second processor 1402 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 1402. The second processor 1402 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1402 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 1403. The second processor 1402 reads information from the second memory 1403 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0318] In an exemplary embodiment, the second functional entity 1400 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0319] It is understood that the memories (first memory 1203, second memory 1403) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Specifically, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be disk storage or magnetic tape storage. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0320] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 1203 storing a computer program, which can be executed by a first processor 1202 of a first functional entity 1200 to complete the steps described in the method of the first functional entity. Another example is a second memory 1403 storing a computer program, which can be executed by a second processor 1402 of a second functional entity 1400 to complete the steps described in the method of the second functional entity. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0321] For example, this application also provides a computer program product, including a computer program that can be executed by a first processor 1302 of a first functional entity 1300 to complete the steps described in the aforementioned first functional entity-side method. Alternatively, the computer program can be executed by a second processor 1402 of a second functional entity 1400 to complete the steps described in the aforementioned second functional entity-side method.

[0322] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0323] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Additionally, the term "one or more" in this document means any one of a set of multiple objects, or any combination of at least two of a set of multiple objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0324] In the embodiments of this application, the functional entity may also be referred to as a network element, an entity, a network device, or a network-side device, etc.

[0325] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0326] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for establishing a business, characterized in that, Applied to a first functional entity, the method includes: Receive a first service request, the first service request is used to request the execution of a first service, the first service represents a service that requires scheduling one or more capabilities to be executed; Based on the first service request, configuration information about the first service is sent to one of a plurality of second functional entities, wherein the plurality of second functional entities are used to provide one or more of the capabilities for executing the first service.

2. The method according to claim 1, characterized in that, The first service requires scheduling one or more capabilities, including any one or more of the following: Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

3. The method according to claim 1, characterized in that, Receiving the first service request includes: Receive the first service request sent by the base station and / or terminal and / or core network side; or, The system receives the first service request sent by a third functional entity, which is used to forward the first service request sent by the base station and / or terminal and / or core network side to the first functional entity.

4. The method according to claim 1 or 3, characterized in that, The first service request carries first information, which is used to indicate one or more capabilities; And / or, The method further includes: The system receives first information sent by the base station and / or the core network side, wherein the first information is used to indicate one or more capabilities, and the first information is determined by the base station and / or the core network side based on the service policy of the first service.

5. The method according to claim 1, characterized in that, The configuration information includes one or more of the following: The business type of the first service; The identifier of the first service; The identifier of the service flow carrying the first service; The second information is used to indicate the plurality of second functional entities; The third information is used to indicate the initiator of the first service request.

6. The method according to claim 1, characterized in that, One of the plurality of second functional entities is determined based on one or more of the following: The load of the second functional entity; The capabilities of the second functional entity; The business type of the first service; The coverage area of ​​the second functional entity.

7. The method according to claim 1, characterized in that, The configuration information is sent via the Xn interface, F1 interface, or SBI interface.

8. A method for establishing a business, characterized in that, Applied to a second functional entity, the method includes: Receive configuration information regarding the first service; among which, The first service characterizes a service that requires scheduling one or more capabilities to execute; the configuration information is used to be sent to multiple second functional entities, which are used to provide the one or more capabilities for executing the first service.

9. The method according to claim 8, characterized in that, The receiving of configuration information regarding the first service includes: Receive the configuration information about the first service sent by the first functional entity; or, Receive configuration information about the first service from one of the plurality of second functional entities.

10. The method according to claim 9, characterized in that, One of the plurality of second functional entities is determined based on one or more of the following: The load of the second functional entity; The capabilities of the second functional entity; The business type of the first service; The coverage area of ​​the second functional entity.

11. The method according to claim 9, characterized in that, After receiving the configuration information about the first service sent by the first functional entity, the method further includes: Send configuration information about the first service to each of the other second functional entities among the plurality of functional entities.

12. The method according to claim 8, characterized in that, The first service requires scheduling one or more capabilities, including any one or more of the following: Computing power, artificial intelligence capabilities, communication capabilities, sensing capabilities, and data capabilities.

13. The method according to claim 8, characterized in that, The configuration information includes one or more of the following: The business type of the first service; The service identifier of the first service; The identifier of the service flow carrying the first service; The second information is used to indicate the plurality of second functional entities; The third information is used to indicate the initiator of the first service request.

14. The method according to claim 8, characterized in that, The configuration information is sent via the Xn interface, F1 interface, or SBI interface.

15. A business system, characterized in that, include: A first functional entity and multiple second functional entities; among which... The first functional entity is used to implement the method for establishing a business as described in any one of claims 1 to 7; And / or, the second functional entity is used to implement the method for establishing a business as described in any one of claims 8 to 14.

16. The business system according to claim 15, characterized in that, The first functional entity is deployed at a core network node, and the plurality of second functional entities are deployed at different access network nodes; or, The first functional entity and one of the plurality of second functional entities are deployed at the first access network node, and the other second functional entities, excluding the first second functional entity, are deployed at different second access network nodes.

17. The business system according to claim 16, characterized in that, The third functional entity is deployed on the same node as the first functional entity, or the first functional entity is deployed on the first access network node and the third functional entity is deployed on the core network node.

18. The business system according to claim 15, characterized in that, The first functional entity and the plurality of second functional entities are all deployed at the first base station; wherein, The first base station adopts a CU-DU separation architecture, and the first functional entity and one of the multiple second functional entities are jointly deployed in the CU of the first base station. The other second functional entities among the multiple second functional entities, except for the first second functional entity, are respectively deployed in different DUs of the first base station.

19. The business system according to claim 15, characterized in that, The first functional entity and one of the plurality of second functional entities are jointly deployed in the CU of the first base station, and the other second functional entities, excluding the first one, are deployed in the DU of one or more second base stations; wherein, The first base station and the plurality of second base stations all adopt a CU-DU separation architecture.

20. An apparatus for establishing a business, characterized in that, include: The first receiving unit is configured to receive a first service request, the first service request being used to request the execution of a first service, the first service representing a service that requires scheduling one or more capabilities to be executed. The first sending unit is configured to send configuration information about the first service to one of a plurality of second functional entities based on the first service request, wherein the plurality of second functional entities are configured to provide one or more capabilities for executing the first service.

21. An apparatus for establishing a business, characterized in that, include: The second receiving unit is used to receive configuration information about the first service; wherein, The first service characterization represents a service that requires scheduling one or more capabilities to execute; The configuration information is used to be sent to multiple second functional entities, which are used to provide one or more capabilities for performing the first service.

22. A first functional entity, characterized in that, include: A first processor and a first communication interface; wherein... The first communication interface is used for: Receive a first service request, the first service request is used to request the execution of a first service, the first service represents a service that requires scheduling one or more capabilities to be executed; Based on the first service request, configuration information about the first service is sent to one of a plurality of second functional entities, wherein the plurality of second functional entities are used to provide one or more of the capabilities for executing the first service.

23. A second functional entity, characterized in that, include: A second processor and a second communication interface; wherein... The second communication interface is used for: Receive configuration information regarding the first service; among which, The first service characterizes a service that requires scheduling one or more capabilities to execute; the configuration information is used to be sent to multiple second functional entities, which are used to provide the one or more capabilities for executing the first service.

24. A first functional entity, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 7.

25. A second functional entity, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 8 to 14.

26. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7, or the steps of the method according to any one of claims 8 to 14.

27. A computer program product having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7, or the steps of the method according to any one of claims 8 to 14.

Images