A communication method, apparatus and system

Abstract

Embodiments of the present application provide a communication method, apparatus and system. A first network function can send first information to one or more third network functions, wherein the first information indicates one or more capability items associated with one or more services, each of the one or more capability items being associated with one or more capabilities. The one or more third network functions can report their one or more capabilities based on the indicated one or more capability items. That is, the one or more third network functions can provide a report that the first network function can resolve. This makes interaction between various network functions possible, thereby enabling support for various services in a communication system.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 623,668, filed January 22, 2024, entitled "6G NETWORK CAPABILITY DESCRIPTION (LANGUAGE) - NCD(L)". The disclosure of the above application is incorporated herein by reference in its entirety. Technical Field

[0002] This application relates to the field of wireless technology, and more specifically, to a communication method, apparatus, and system. Background Technology

[0003] In communication systems, specific application programming interfaces (APIs) are defined based on the Hypertext Transfer Protocol (HTTP). Network functions can interact using this HTTP protocol.

[0004] As various services (such as artificial intelligence services and consortium network services) are gradually offered in communication systems, this specific API limits the development of communication systems. Summary of the Invention

[0005] This application provides a communication method, apparatus, and system that can support various services in a communication system.

[0006] According to a first aspect, one embodiment of this application provides a communication method, which can be executed by a first network function or a chip within the first network function. The method includes: sending first information, wherein the first information indicates one or more capability items associated with a service, each of the one or more capability items being associated with one or more capabilities; and receiving second information, wherein the second information indicates at least one capability reported based on the first information and associated with the one or more capability items.

[0007] According to the above scheme, a network function (such as a network capability (NC) provider) can report one or more of its own capabilities based on one or more indicated capability items. In other words, the NC provider can provide a report that is resolvable by the first network function. This enables interaction between various network functions, thereby supporting a variety of services within the communication system.

[0008] In conjunction with the first aspect, in some embodiments, each of the at least one capability is reported in a specific format.

[0009] According to the above scheme, NC providers can report one or more of their own capabilities in the indicated format. This enables the first network function to maintain service capabilities more efficiently.

[0010] In conjunction with the first aspect, in some embodiments, the first information also indicates the format.

[0011] According to the above scheme, the first network function can instruct one or more NC providers on the format, thereby ensuring that the reported capabilities can be correctly parsed by the first network function.

[0012] In conjunction with the first aspect, in some embodiments, each of the at least one capability is reported according to the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0013] According to the above scheme, in subsequent interactions, the index can be used to refer to the corresponding capability, thereby reducing subsequent transmission overhead. One or more conditions can be used to reliably activate the corresponding capability.

[0014] In conjunction with the first aspect, in some embodiments, each of the at least one capability is reported according to the format, the format further including information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

[0015] According to the above scheme, when determining whether to activate a capability, the reliability of activation can be improved by considering whether the corresponding capability is mandatory when one or more conditions are met.

[0016] In conjunction with the first aspect, in some embodiments, the first information also indicates one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any of the one or more capability items.

[0017] According to the above scheme, when the first information indicates an explanation and / or one or more examples of one or more capability items, the NC provider can more accurately understand one or more capability items.

[0018] In conjunction with the first aspect, in some embodiments, the method further includes: receiving third information from a second network function, wherein the third information requests the at least one capability associated with the service; and sending capability information to the second network function, wherein the capability information indicates the at least one capability.

[0019] According to the above scheme, the first network function collects one or more capabilities and can send capability information to other network functions.

[0020] In conjunction with the first aspect, in some embodiments, the method further includes: maintaining the second information.

[0021] According to the above scheme, the first network function can maintain one or more collected capabilities for use in subsequent processes (such as configuration processes).

[0022] In conjunction with the first aspect, in some embodiments, the method further includes: determining one or more first capabilities involved in a task among the at least one capability; sending a first message, wherein the first message indicates the one or more first capabilities described in the format.

[0023] According to the above scheme, the first network function learns one or more capabilities of one or more services, and uses the relevant one or more first capabilities to configure the relevant one or more first services to perform a task, thereby enabling the task to be performed.

[0024] According to a second aspect, one embodiment of this application provides a communication method, which can be executed by a second network function or a chip within the second network function. The method includes: acquiring capability information, wherein the capability information indicates one or more capabilities associated with a first service, and a task relating to the first service; determining one or more first capabilities among the one or more capabilities associated with the first service, the task relating to the first service; and sending a first message to a third network function corresponding to the first service, wherein the first message indicates the one or more first capabilities.

[0025] According to the above scheme, the second network function can acquire one or more capabilities of the first service and configure the first service to perform tasks using the relevant one or more first capabilities. One or more capabilities of the first service can be published to the second network function, enabling the second network function to configure the first service and thus support various services in the communication system.

[0026] In conjunction with the second aspect, in some embodiments, each of the one or more capabilities associated with the first service is described in a format, and each of the one or more first capabilities is described based on the format.

[0027] According to the above scheme, one or more first capabilities indicated by the first message are described based on a format, which enables the third network function to correctly parse the first message.

[0028] In conjunction with the second aspect, in some embodiments, each of the one or more capabilities associated with the first service is described in accordance with the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0029] According to the above scheme, in subsequent interactions (such as in the first message), the index can be used to refer to the corresponding capability, thereby reducing transmission overhead. Furthermore, the second network function can more reliably determine the first capability based on one or more conditions.

[0030] In conjunction with the second aspect, in some embodiments, each of the one or more capabilities associated with the first service is described in the format described, the format further including information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

[0031] According to the above scheme, when the second network function is based on one or more conditions, whether the corresponding capability is mandatory, and whether to activate one or more first capabilities, the reliability of activation can be improved.

[0032] In conjunction with the second aspect, in some embodiments, obtaining capability information includes: obtaining the task; determining the first service involved in the task; sending third information to a first network function, wherein the third information requests one or more capabilities associated with the first service; and receiving the capability information from the first network function.

[0033] According to the above scheme, the second network function can determine that the task involves the first service and obtain one or more capabilities of the first service from the first network function.

[0034] In conjunction with the second aspect, in some embodiments, sending a first message to a third network function corresponding to the first service includes: sending multiple first messages to multiple third network functions deployed in multiple first services, wherein the task relates to the multiple first services, and each first message in the first message indicates a first capability related to the task associated with the corresponding first service.

[0035] According to the above scheme, the second network function can determine that the task involves multiple first services, can learn the capabilities of various services, and can use one or more related first capabilities to configure one or more related first services to collaboratively execute the task, which makes the collaboration of multiple services possible.

[0036] In conjunction with the second aspect, in some embodiments, the method further includes sending a second message, wherein the second message indicates the configuration used for interaction between two third network functions.

[0037] According to the above scheme, even if the interfaces of the third network functions are incompatible, the second message can still enable interaction between them. Various services can collaboratively perform tasks.

[0038] In conjunction with the second aspect, in some embodiments, the configuration includes one or more of the following: the data format capabilities of the two third network functions, the data receiving network function of the two third network functions, the data sending network function of the two third network functions, and one or more data processing operations between the two third network functions.

[0039] In conjunction with the second aspect, in some embodiments, sending the second message includes: sending the second message to one or both of the two third network functions; or sending the second message to a fourth network function, wherein the fourth network function is responsible for the interaction between the two third network functions.

[0040] According to a third aspect, one embodiment of this application provides a communication method that can be executed by a third network function or a chip within the third network function. The method includes: receiving first information, wherein the first information indicates one or more capability items associated with a service, each of the one or more capability items being associated with one or more capabilities; and sending second information, wherein the second information indicates at least one capability reported based on the first information and associated with the one or more capability items.

[0041] The various implementations of the third aspect correspond to the various implementations of the first aspect. The beneficial technical effects of the various implementations of the third aspect can be found in the descriptions of the relevant implementations of the first aspect, and will not be repeated here.

[0042] In conjunction with the third aspect, in some embodiments, each of the at least one capability is reported in a specific format.

[0043] In conjunction with the third aspect, in some embodiments, the first information also indicates the format.

[0044] In conjunction with the third aspect, in some embodiments, each of the at least one capability is reported according to the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0045] In conjunction with the third aspect, in some embodiments, each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

[0046] In conjunction with the third aspect, in some embodiments, the first information further includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any of the one or more capability items.

[0047] In conjunction with the third aspect, in some embodiments, the task involves the third network function, the first information is received from the first network function, and the method further includes: receiving a first message from the first network function, wherein the first message indicates one or more first capabilities involved in the task among the at least one capability; or receiving a first message from a second network function, wherein the first message indicates one or more first capabilities involved in the task among the at least one capability.

[0048] According to a fourth aspect, one embodiment of this application provides a communication method, which can be executed by a third network function or a chip within the third network function. The method includes: receiving a first message, wherein the first message indicates one or more first capabilities involved in a task among one or more capabilities associated with a first service; and activating the one or more first capabilities based on the first message.

[0049] The various implementations of the fourth aspect correspond to the various implementations of the second aspect. The beneficial technical effects of the various implementations of the fourth aspect can be found in the descriptions of the relevant implementations in the second aspect, and will not be repeated here.

[0050] In conjunction with the fourth aspect, in some embodiments, the method further includes: receiving first information, wherein the first information indicates one or more capability items associated with the first service, each of the one or more capability items being associated with the one or more capabilities; and sending second information, wherein the second information indicates at least one capability reported based on the first information and associated with the one or more capability items.

[0051] In conjunction with the fourth aspect, in some embodiments, each of the at least one capability is reported according to a format, and the one or more first capabilities are described based on the format.

[0052] In conjunction with the fourth aspect, in some embodiments, the first information also indicates the format.

[0053] In conjunction with the fourth aspect, in some embodiments, each of the at least one capability is reported according to the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0054] In conjunction with the fourth aspect, in some embodiments, each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

[0055] In conjunction with the fourth aspect, in some embodiments, the first information further includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any one of the one or more capability items.

[0056] In conjunction with the fourth aspect, in some embodiments, the method further includes: receiving a second message, wherein the second message indicates the configuration used for interaction between the third network function and other network functions, the task relating to the interaction.

[0057] In conjunction with the fourth aspect, in some embodiments, the configuration includes one or more of the following: the data format capability of the third network function, the data format capability of the other network functions, the data receiving network function of the third network function and the other network functions, the data sending network function of the third network function and the other network functions, and one or more data processing operations between the third network function and the other network functions.

[0058] According to a fifth aspect, one embodiment of this application provides a communication method, which can be executed by a fourth network function or a chip within the fourth network function. The method includes: receiving a second message, wherein the second message indicates a configuration used for interaction between at least two third network functions corresponding to at least two services, the task relating to the interaction; and interacting with the two third network functions based on the second message.

[0059] According to the above scheme, even if the interfaces of the third network functions are incompatible, the second message can still enable interaction between them. Various services can collaboratively perform tasks.

[0060] In conjunction with the fifth aspect, in some embodiments, the configuration includes one or more of the following: data format capabilities of the at least two third network functions, data receiving network functions of the at least two third network functions, data sending network functions of the at least two third network functions, and one or more data processing operations between the at least two third network functions.

[0061] According to a sixth aspect, one embodiment of this application provides a communication method, the method comprising: a first network function sending first information to a third network function, wherein the first information indicates one or more capability items associated with a first service, each of the one or more capability items being associated with one or more capabilities; the third network function sending second information to the first network function, wherein the second information indicates at least one capability reported based on the first information and associated with the one or more capability items.

[0062] The various implementations of the sixth aspect correspond to the various implementations of the first and second aspects. The beneficial technical effects of the various implementations of the sixth aspect can be found in the descriptions of the relevant implementations of the first and second aspects, and will not be repeated here.

[0063] In conjunction with the sixth aspect, in some embodiments, the method further includes: the first network function sending capability information to the second network function, wherein the capability information indicates the at least one capability, and the task involves the first service; the second network function determining one or more first capabilities involved in the task among the at least one capability; the second network function sending a first message to the third network function, wherein the first message indicates the one or more first capabilities; and the third network function activating the one or more first capabilities based on the first message.

[0064] In conjunction with the sixth aspect, in some embodiments, the method further includes: the first network function determining one or more first capabilities involved in a task among the at least one capability; the first network function sending a first message to the third network function, wherein the first message indicates the one or more first capabilities; and the third network function activating the one or more first capabilities based on the first message.

[0065] In conjunction with the sixth aspect, in some embodiments, each of the at least one capability is reported according to a format, and each of the one or more first capabilities is described based on the format.

[0066] In conjunction with the sixth aspect, in some embodiments, the first information also indicates the format.

[0067] In conjunction with the sixth aspect, in some embodiments, each of the at least one capability is reported according to the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0068] In conjunction with the sixth aspect, in some embodiments, each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

[0069] In conjunction with the sixth aspect, in some embodiments, the first information further includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any one of the one or more capability items.

[0070] In conjunction with the sixth aspect, in some embodiments, sending a first message from the second network function or the first network function to the third network function corresponding to the first service includes: the second network function or the first network function sending multiple first messages to multiple third network functions deployed in multiple first services, wherein the task relates to the multiple first services, and each first message in the first message indicates a first capability related to the task associated with the corresponding first service.

[0071] In conjunction with the sixth aspect, in some embodiments, the method further includes: the second network function or the first network function sending a second message to one or both of the plurality of third network functions, wherein the second message indicates a configuration used for an interaction between the two third network functions, the task relating to the interaction; and the two third network functions interacting based on the second message; or the second network function or the first network function sending a second message to a fourth network function, wherein the second message indicates a configuration used for an interaction between at least two of the plurality of third network functions, the task relating to the interaction; and the at least two third network functions and the fourth network function interacting based on the second message.

[0072] In conjunction with the sixth aspect, in some embodiments, the configuration includes one or more of the following: the data format capabilities of the two third network functions, the data receiving network function of the two third network functions, the data sending network function of the two third network functions, and one or more data processing operations between the two third network functions.

[0073] According to a seventh aspect, a first network function is provided. The first network function includes a unit configured to perform the method according to the first aspect or any possible embodiment of the first aspect.

[0074] According to the eighth aspect, a second network function is provided. The second network function includes a unit for performing the method according to the second aspect or any possible embodiment of the second aspect.

[0075] According to the ninth aspect, a third network function is provided. The third network function includes a unit for performing the method according to the third aspect or any possible embodiment of the third aspect.

[0076] According to the tenth aspect, a third network function is provided. The third network function includes a unit for performing the method according to the fourth aspect or any possible embodiment of the fourth aspect.

[0077] According to the eleventh aspect, a fourth network function is provided. The fourth network function includes a unit for performing the method according to the fifth aspect or any possible embodiment of the fifth aspect.

[0078] According to a twelfth aspect, a system is provided. The system includes a first network function according to a seventh aspect and a third network function according to a ninth aspect.

[0079] According to a thirteenth aspect, a system is provided. The system includes a second network function according to an eighth aspect and a third network function according to a tenth aspect.

[0080] According to a fourteenth aspect, a communication device is provided. The communication device includes at least one processor coupled to at least one memory. The at least one memory is used to store a computer program or one or more instructions. The at least one processor is used to invoke the computer program or the one or more instructions from the at least one memory and to execute the computer program or the one or more instructions, such that: the communication device performs the method of the first aspect or any possible implementation thereof, or the communication device performs the method of the second aspect or any possible implementation thereof, or the communication device performs the method of the third aspect or any possible implementation thereof, or the communication device performs the method of the fourth aspect or any possible implementation thereof, or the communication device performs the method of the fifth aspect or any possible implementation thereof, or the communication device performs the method of the sixth aspect or any possible implementation thereof.

[0081] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, the communication device may be a first network function or a component (such as a chip or integrated circuit) installed in the first network function. For example, the communication device may be a second network function or a component (such as a chip or integrated circuit) installed in the second network function. For example, the communication device may be a third network function or a component (such as a chip or integrated circuit) installed in the third network function. For example, the communication device may be a fourth network function or a component (such as a chip or integrated circuit) installed in the fourth network function.

[0082] According to a fifteenth aspect, a communication apparatus is provided. The communication apparatus includes a processor and a communication interface. The processor is connected to the communication interface. The processor is configured to execute one or more instructions, and the communication interface is configured to communicate with other network elements under the control of the processor. The processor is capable of performing the methods described according to any possible embodiments of the first, second, third, fourth, fifth, sixth, or any of the foregoing aspects.

[0083] According to a sixteenth aspect, a computer storage medium is provided. The computer storage medium stores program code for executing one or more instructions to perform the method according to any possible embodiment of the first, second, third, fourth, fifth, sixth, or any of the foregoing aspects.

[0084] According to the seventeenth aspect, this application provides a computer program product comprising one or more instructions, wherein, when the computer program product is run on a computer, the computer performs the method according to any possible embodiment of the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, or any of the foregoing aspects.

[0085] According to the eighteenth aspect, this application provides a non-transitory computer-readable medium storing instructions that cause a processor in a device to implement the method according to any possible embodiment of the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, or any of the foregoing aspects.

[0086] According to the nineteenth aspect, this application provides an apparatus for performing the method described in any of the possible embodiments of the first, second, third, fourth, fifth, sixth aspects or any of the foregoing aspects.

[0087] According to the twentieth aspect, this application provides a processor for executing instructions to cause a device to perform the method according to any possible embodiment of the first, second, third, fourth, fifth, sixth aspects or any of the foregoing aspects.

[0088] According to the twenty-first aspect, this application provides an integrated circuit for performing the methods described in any of the possible embodiments of the first, second, third, fourth, fifth, sixth aspects or any of the foregoing aspects. Attached Figure Description

[0089] One or more embodiments have been described by way of example with reference to the accompanying drawings. These exemplary illustrations and drawings do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the scale of the drawings is not limited. In the drawings: Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0090] Figure 2 An example of a communication system is shown.

[0091] Figure 3 Another example of an electronic device (ED) and a base station is shown.

[0092] Figure 4 The unit or module in the device is shown.

[0093] Figure 5 This is an example of a 6G system conceptual architecture.

[0094] Figure 6 This is a schematic flowchart of a communication method according to an embodiment of this application.

[0095] Figure 7 An example of the format according to one embodiment of this application is shown.

[0096] Figure 8 This is a schematic flowchart illustrating a first implementation of the configuration process according to an embodiment of this application.

[0097] Figure 9 This is a schematic flowchart illustrating a second implementation of the configuration process according to an embodiment of this application.

[0098] Figure 10 This is a schematic flowchart of a communication method according to an embodiment of this application.

[0099] Figure 11 This is a schematic diagram of the LOMA task execution flow according to an embodiment of this application.

[0100] Figure 12 This is another schematic diagram of the LOMA task execution flow according to an embodiment of this application.

[0101] Figure 13 and Figure 14 This is a schematic block diagram of a possible device according to an embodiment of this application. Detailed Implementation

[0102] The technical solution of this application will now be described with reference to the accompanying drawings.

[0103] The technical solutions in this application embodiment can be applied to various communication systems, such as fifth-generation (5G) wireless communication systems, new radio (NR) wireless communication systems, sixth-generation (6G) wireless communication systems, or other evolved communication systems.

[0104] To facilitate understanding of the embodiments of this application, let's first take... Figures 1 to 3 Taking the communication system shown as an example, the communication system applicable to the embodiments of this application will be described in detail.

[0105] refer to Figure 1 , Figure 1 This is a non-limiting illustrative example providing a simplified schematic of a communication system. Communication system 100 includes a radio access network 120. Radio access network 120 can be a next-generation (e.g., sixth-generation, 6G or later) radio access network or a traditional (e.g., 5G) radio access network. One or more electronic devices (EDs) 110a to 110j (collectively referred to as 110) can be interconnected with each other or connected to one or more network nodes (170a, 170b, collectively referred to as 170) within radio access network 120. Core network 130 can be part of the communication system and can depend on or be independent of the radio access technology used in communication system 100. Furthermore, communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0106] Figure 2An exemplary communication system 100 is illustrated. Generally, the communication system 100 enables multiple wireless or wired units to transmit data and other content. The purpose of the communication system 100 may be to provide content such as voice, data, video, and / or text via broadcast, multicast, and unicast. The communication system 100 can operate by sharing resources such as carrier spectrum bandwidth among its constituent units. The communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. The communication system 100 can provide a wide variety of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, automated delivery, and mobility). The communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can form a multi-layered heterogeneous network. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

[0107] Terrestrial and non-terrestrial communication systems can be subsystems of a communication system. In the example shown, communication system 100 includes electronic devices (EDs) 110a to 110d (collectively referred to as ED 110), radio access networks (RANs) 120a and 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which are generally referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes access nodes 120c, which are generally referred to as non-terrestrial transmit and receive points (NT-TRPs) 172.

[0108] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with any other T-TRP 170a and 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can perform uplink and / or downlink transmissions with T-TRP 170a via interface 190a. In some examples, ED 110a, 110b, and 110d can also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d can perform uplink and / or downlink transmissions with NT-TRP 172 via interface 190c.

[0109] Air interfaces 190a and 190b can employ similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). Air interfaces 190a and 190b can utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0110] The 190c air interface enables communication between the ED 110d and one or more NT-TRP172s via a wireless link or simply via a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs and one or more NT-TRPs for multicast transmission.

[0111] RANs 120a and 120b communicate with the core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b, and / or the core network 130, can communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130, and may or may not use the same radio access technology as RANs 120a and / or RAN 120b. The core network 130 can also serve as a gateway access between (i) RANs 120a and 120b, or EDs 110a, 110b, and 110c, or both, and (ii) other networks (such as PSTN 140, Internet 150, and other networks 160). Additionally, some or all of the EDs in EDs 110a, 110b, and 110c may include functionality for communicating with different wireless networks via different radio links using different radio technologies and / or protocols. ED 110a, 110b, and 110c can communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150, rather than via wireless communication (or via wired communication in addition to wireless communication). PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a computer network and / or subnet (internal network) and employ protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and integrate multiple transceivers required to support such technologies.

[0112] Figure 3Another example of an ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, things, machines, etc. The ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0113] Each ED 110 represents any suitable end-user equipment for wireless operation and may include (or be referred to as) devices such as: user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train, or IoT device, industrial equipment, or devices within the aforementioned equipment (such as communication modules, modems, or chips), etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, referred to below as T-TRP 170. Similarly... Figure 3 As shown, NT-TRP is referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically started (i.e., established, activated, or enabled), shut down (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0114] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure. One, some, or all of the antennas may also be panels. The transmitter 201 and receiver 203 may be integrated, for example, integrated as a transceiver. The transceiver is used to modulate data or other content for transmission through at least one antenna 204 or a network interface controller (NIC). The transceiver may also be used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0115] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by one or more processing units 210. Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) card, and processor cache, etc.

[0116] ED 110 may also include one or more input / output devices (not shown) or interfaces (such as those connected to...). Figure 1 (Wired interface of Internet 150 in the network). Input / output devices support interaction with the user or other devices in the network. Each input / output device includes any suitable structure for providing or receiving information from the user (including for network interface communication), such as a speaker, microphone, keypad, keyboard, display, or touchscreen.

[0117] ED 110 also includes a processor 210 for performing the following operations: operations related to preparing to transmit uplink transmissions to NT-TRP 172 and / or T-TRP 170, operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and operations related to processing lateral link transmissions to and from other ED 110s. Processing operations related to preparing to transmit uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to a specific embodiment, the downlink transmission may be received by receiver 203 via receive beamforming, and processor 210 may extract signaling from the downlink transmission (e.g., by detecting and / or decoding signaling). For example, the signaling may be a reference signal transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction indications (such as beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (such as initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0118] Although not shown in the figures, processor 210 may be part of transmitter 201 and / or receiver 203. Although not shown in the figures, memory 208 may be part of processor 210.

[0119] The processing components in processor 210, transmitter 201, and receiver 203 may be implemented by the same or different processors, which execute instructions stored in memory (such as memory 208). Alternatively, some or all of the processing components in processor 210, transmitter 201, and receiver 203 may be implemented using special-purpose circuits such as a field-programmable gate array (FPGA), a graphics processing unit (GPU), or an application-specific integrated circuit (ASIC).

[0120] In some embodiments, the T-TRP 170 may have other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), or wireless router, relay station, ground node, ground network device, or ground base station, baseband unit (BBU), remote radio unit (RRU), radio unit (RU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 may be a macro BS, pico BS, relay node, or donor node, or a combination thereof. T-TRP 170 can refer to the aforementioned equipment or to a component within the aforementioned equipment (such as a communication module, modem, or chip).

[0121] In some embodiments, the CU (or CU control plane (CP) and CU user plane (UP)), DU, or RU may have other names. For example, in an open RAN (ORAN) system, the CU may also be called an open CU (open CU, O-CU), the DU may also be called an open DU (open DU, O-DU), the CU-CP may also be called an open CU-CP (open CU-CP, O-CU-CP), the CU-UP may also be called an open CU-UP (open CU-UP, O-CU-CP), and the RU may also be called an open RU (open RU, O-RU). Any of the CU (or CU-CP, CU-UP), DU, or RU can be implemented by a software module, a hardware module, or a combination of software and hardware modules.

[0122] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some modules in T-TRP 170 may be located remotely from the device housing the antenna of T-TRP 170 and may be coupled to the device housing the antenna via a communication link (not shown), sometimes referred to as a fronthaul, such as the Common Public Radio Interface (CPRI). Therefore, in some embodiments, the term "T-TRP 170" may also refer to network-side modules that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding; these modules are not necessarily part of the device housing the antenna of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs operating together to serve ED 110, such as through cooperative multicast.

[0123] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure. One, some, or all of the antennas may also be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing operations related to: preparing downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing backlink transmissions to NT-TRP 172, and processing transmissions received from NT-TRP 172 via backlink. Processing operations related to preparing downlink or backlink transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or backlink may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processor 260 can also perform operations related to network access (such as initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB), generating system information, etc. In some embodiments, processor 260 also generates beam direction indications, such as BAIs, that can be scheduled for transmission by scheduler 253. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the location for deploying NT-TRP 172, etc. In some embodiments, processor 260 can generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein can also be referred to as control signaling. Dynamic signaling can be transmitted in control channels such as the physical downlink control channel (PDCCH), while static or semi-static higher-layer signaling can be included in data packets that are transmitted in data channels such as the physical downlink shared channel (PDSCH).

[0124] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within T-TRP 170 or may operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, and / or backlink transmissions, including issuing scheduling grants and / or configuring schedule-free (“configuration grants”) resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by processor 260.

[0125] Although not shown in the figures, processor 260 may be part of transmitter 252 and / or receiver 254. Furthermore, although not shown in the figures, processor 260 may implement scheduler 253. Although not shown in the figures, memory 258 may be part of processor 260.

[0126] The processing components in processor 260, scheduler 253, transmitter 252, and receiver 254 can be implemented by the same or different processors, which execute instructions stored in memory (such as memory 258). Alternatively, some or all of the processing components in processor 260, scheduler 253, transmitter 252, and receiver 254 can be implemented using dedicated circuitry such as FPGA, GPU, or ASIC.

[0127] Although the NT-TRP 172 is only exemplified as a drone, it can be implemented in any suitable non-terrestrial form. Furthermore, in some embodiments, the NT-TRP 172 may have other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figure. One, some, or all of the antennas may also be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations related to: preparing downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing backhaul transmissions to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing receive transmissions in the uplink or backhaul may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as those in the medium access control (MAC) layer or radio link control (RLC) layer. Since this is only an example, NT-TRP 172 typically implements higher-layer functions in addition to physical layer processing.

[0128] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown in the figures, a processor 276 may be part of the transmitter 272 and / or the receiver 274. Although not shown in the figures, the memory 278 may be part of the processor 276.

[0129] The processing components in processor 276, transmitter 272, and receiver 274 may be implemented by the same or different processors for executing instructions stored in memory (such as memory 278). Alternatively, some or all of the processing components in processor 276, transmitter 272, and receiver 274 may be implemented using dedicated circuitry such as a programmed FPGA, GPU, or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs operating together to serve ED 110, such as through cooperative multicast.

[0130] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components are omitted.

[0131] To facilitate understanding of the embodiments of this application, the process of transmitting reference signals and measuring the channel based on these reference signals is briefly described below.

[0132] according to Figure 4 One or more steps of the exemplary methods provided herein may be performed by the corresponding unit or module. Figure 4 The diagram illustrates units or modules within a device (such as ED 110, T-TRP 170, or NT-TRP 172). For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented by hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be integrated circuits, such as a programmed FPGA, GPU, or ASIC. It should be understood that if these modules are implemented in software for execution by a processor, etc., these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, in one or more instances, and these modules themselves may include instructions for further deployment and instantiation.

[0133] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0134] The 6G system architecture proposed in this application aims to support 6G XaaS services by employing technologies such as network function virtualization and network slicing. The 6G system architecture adopts a service-oriented interaction mechanism between 6G services.

[0135] The 6G system adopts a service-oriented architecture and the XaaS concept. XaaS services in the 6G system are divided into three layers. The conceptual structure of the 6G system is as follows: Figure 5 As shown.

[0136] The services described in this application can be referred to as Web services running on a network. In some embodiments, the service may be a basic processing service, such as an artificial intelligence service, a data processing service, or a data storage service. In some embodiments, the service may be a control or management service, such as a resource management service, a task management service, or a connection management service. In some embodiments, the service may be a wireless network service, such as a RAN infrastructure service, a core network infrastructure service, or a satellite infrastructure service. This application does not limit the scope of the service.

[0137] Services can be provided by network functions or network entities. For ease of description, this application uses network functions as an example, but this does not exclude other implementation methods. This application does not limit the form of network functions. For example, one or more network functions can form a network slice according to needs, or they can be independent devices, or they can be integrated into a single device to support different services, or they can be one or more network components in one or more hardware devices, or one or more software functions running on dedicated hardware, or virtualization functions instantiated on a platform (such as a cloud platform), etc.

[0138] The service may also be referred to as X as a service (XaaS), network capability (NC), or other possible names. This application does not limit the terminology. For example, in a 6G system, the service may refer to a 6G XaaS service.

[0139] refer to Figure 5 The 6G system adopts a service-oriented architecture and the XaaS concept. XaaS services in a 6G system can be divided into three layers: the infrastructure layer, the control or management (C / M) layer, and the service layer. One or more services in the infrastructure layer can provide one or more wireless network services. One or more services in the C / M layer can provide one or more control or management services. One or more services in the service layer can provide one or more basic processing services. Examples of services in these three layers are given below for ease of understanding of the embodiments of this application.

[0140] The infrastructure layer includes the infrastructure that supports 6G services. For example, the infrastructure layer may include one or more of the following: wireless network (such as RAN, CN) infrastructure, data center infrastructure, cloud center infrastructure, satellite infrastructure (such as satellite networks), database infrastructure, storage infrastructure, and other possible infrastructure. The above-described infrastructure (i.e., services) is for illustrative purposes only and is not intended to limit the scope of the application. Although not shown in the figures, the infrastructure layer may include sensing networks, etc. This infrastructure may be provided by a single provider (such as a single device) or by multiple providers (such as multiple devices).

[0141] In some embodiments, each infrastructure may have its own control and management functions, represented as C / M functions, for infrastructure management. Each of these infrastructures is a type of infrastructure (i.e., service).

[0142] The C / M layer includes control and management services for 6G systems. These services can be developed and deployed using slicing technology and can utilize resources provided by the infrastructure layer. The C / M layer may include one or more of the following: Resource management (RM) as a service provides the ability to manage the lifecycle of various slices and allocate over-the-air resources to wireless devices. RM is a specific XaaS service, and can also be considered a specific NC. Mission management (MM) as a service provides the ability to program the provision of XaaS services at the service layer to deliver mission services. A mission can be a set of services (such as 6G XaaS services) provided by the system to one or more customers. A mission can be a class of services provided by a single 6G XaaS service, or it can be a class of services that requires multiple XaaS services to provide together. MM is an XaaS service, or it can be considered a specific NC (Network Capability), which can also be named Automatic Network Capability Programming (A-CAP).

[0143] Service provisioning management (SPM) is a service that provides the ability to control and manage customer access to 6G services and provide requested services. This capability is provided through unified mutual authentication, authorization and policies, key management, QoS guarantees, and billing between any pair of XaaS service providers and customers. These customers include not only end customers in the physical world but also digital representatives in the digital world. SPM is a specific XaaS service and can also be considered a specific NC.

[0144] Connectivity Management (CM) as a Service: Leveraging 5G connectivity management capabilities, but extending to include the digital world. CM is a specific XaaS service, and can also be viewed as a specific NC.

[0145] Confederation Network (CONET) as a Service: Provides the capability for multiple partners to jointly deliver 6G services. This capability is provided through consortium formation, mutual authentication and authorization among partners, and protocol negotiation regarding the recording and traceability of selected operations performed by partners, ensuring a trusted environment for the operation of 6G systems. CONET is a specific XaaS service and can also be considered a specific NC.

[0146] Protocol as a Service (PCS): Provides the ability to design customized protocol stacks for identified interfaces. These protocol stacks can be predefined for selection on demand, or designed on demand.

[0147] Cybersecurity Management as a Service: Provides infrastructure owners with the ability to detect potential security risks to their infrastructure.

[0148] It's important to note that XaaS services in the C / M layer not only support the control and management of the 6G system itself, but can also provide support to vertical industries as needed. For example, RM services can not only provide air resource management for the RAN, but also provide services to vertical industries to help them allocate air resources to their end customers. XaaS services in the C / M layer can be deployed using slicing technology.

[0149] The service layer includes 6G services that provide services to customers. For example, the service layer may include one or more of the following: The AI ​​service is referred to as NET4AI as a Service. It provides AI capabilities to support various AI applications. NET4AI is a specific XaaS service, but it can also be considered a specific NC (Computer-Aided Service).

[0150] The data storage and sharing service is represented as NET4Data as a Service. This service provides the ability to reliably store and share data under the control of the data owner and in accordance with authoritative regulations regarding the control of identified data. NET4Data is a specific XaaS service, and can also be considered a specific NC.

[0151] The service of data collection, data cleaning, data analysis, and data delivery is referred to as DAM as a Service. This service provides the ability to manage the lifecycle of statistical data, including data acquisition, de-identification, analysis, and delivery of information statistics from any type of sensor, device, and network function.

[0152] The 6G blockchain service is represented as NET4BC as a service. NET4BC is a specific XaaS service, and can also be considered a specific NC.

[0153] Providing services for the digital world is represented as NET4DW as a Service. Digital world services offer the ability to build, control, and manage the digital world. The digital world is defined as the digital implementation of the physical world. NET4DW is a specific XaaS service, and can also be considered a specific NC (Network Controller).

[0154] The 6G connectivity service is referred to as NET4Con as a service. This service provides the capability to support 6G blockchain services.

[0155] Enhanced connectivity services, such as network for connectivity (NET4CON) as a service, provide the ability to exchange messages and data between new 6G services. NET4CON is a specific XaaS service and can also be considered a specific NC.

[0156] It should be noted that all XaaS services in this service layer can be developed and deployed using resources provided in the infrastructure and employing network function virtualization and slicing technologies. The capabilities of each 6G service are provided by its control and management functions, as well as service-specific data processing functions.

[0157] In addition to supporting 6G XaaS services in the service layer, the 6G system also leverages the 5G system to provide vertical services. The difference between 6G XaaS services and other vertical industries is that vertical industries are purely customers who need other XaaS services to support their operation, and each XaaS service provides its capabilities to 6G customers.

[0158] Any pair of XaaS services in a 6G system can also act as customer and provider to each other. Some examples include an infrastructure owner providing its resources to XaaS services in the service layer and the client / main layer. One or more RM services may require the capabilities provided by NET4AI, DAM, and NET4DW to manage resources used for vertical slicing. The CONET service and NET4Data service may require the capabilities provided by NET4BC to support their operation. This application does not limit this.

[0159] In the embodiments of this application, the core concepts of the system (such as a 6G system) include one or more of the following: 6G systems can decouple various integrated services into basic XaaS services. Basic XaaS services provide unique capabilities to support specific types of services, such as NET4AI, NET4DW, DAM, NET4Data, blockchain services, task management services, etc.

[0160] The 6G system can support joint operation by multiple partners.

[0161] The data plane of a 6G system can include one or more processing functions of XaaS services. MM services can program the interconnection of these functions and support a variety of customized customer services.

[0162] The 6G system architecture can be simplified by classifying basic control and management services and combining these services into basic XaaS services in the C / M layer.

[0163] The C / M side of the 6G system includes C / M functionality in XaaS services and may include 5G CP (such as AMF) depending on the implementation options.

[0164] A basic architecture structure (BAS) can be a unified infrastructure with a minimal number of interfaces and is independent of the type of infrastructure.

[0165] The standardization, development, and deployment of 6G systems can be simplified using the BAS concept, while supporting various infrastructure deployment scenarios.

[0166] The aforementioned system can apply BAS or a subset thereof to the infrastructure based on the capabilities, capacity, and requirements of the infrastructure network, adapting to various deployment scenarios.

[0167] The aforementioned system can utilize the SBI interface concept and apply SBI interaction on both the 6G C / M plane and the 6G data plane.

[0168] The SBI interface can be simplified by introducing a trusted gateway (GW) on the data plane and C / M plane of a 6G system.

[0169] By introducing the CONET capabilities, NET4BC capabilities, and anonymity services provided by the Trusted Gateway (GW) into the C / M plane and data plane of the 6G system, the trustworthiness of the 6G system can be improved from the perspective of its operation.

[0170] Trustworthiness can be enhanced from the perspective of end-customer privacy protection by providing unified mutual authentication, IDM, and data cleansing through SPM service, DAM service, and 6G blockchain service.

[0171] Unified authentication, encompassing all participating partners and customers, can improve wireless device roaming management in both the physical and digital worlds.

[0172] By introducing the concept of BAS, 6G systems can define multiple architectural solutions without investing a lot of effort, supporting multiple development paths from 5G to 6G systems.

[0173] 6G systems can support backward compatibility by leveraging the advantages of SBA and its additional features. 5G users can access 5G services through 6G systems.

[0174] Because the concept of anonymous service provision is implemented in the trusted GW of the 6G C / M plane and 6G data plane, the 6G system can support future expansion by adding new XaaS services while minimizing the impact on standardization and deployment.

[0175] The proposed 6G system architecture can support 6GXaaS services by employing technologies such as network function virtualization and network slicing. The 6G system architecture adopts a service-oriented interaction mechanism between 6G services.

[0176] As mentioned above, systems (such as 6G systems) can support flexible and open service deployments, where one or more services can collaboratively perform tasks. For example, the proposed 6G network is based on SBA (XaaS service), which is based on network capability (NC). This network needs to utilize automatic network capability programming (A-CAP) to provide task services, which are based on the collaboration and interaction between multiple NCs (or services). To support this interaction, providing interfaces between the network functions of these NCs (or services) becomes a key factor. Therefore, the network system needs to specify and describe these interfaces.

[0177] Therefore, this application provides a communication method, apparatus, and system that can support various services in a communication system.

[0178] The solutions described in this application are applicable to next-generation networks (such as sixth-generation (6G) or higher) as well as traditional networks (such as 5G, 4G, 3G, or 2G). For example, the technical solutions proposed in the embodiments of this application can be applied to... Figure 5 The system shown includes one or more services.

[0179] Figure 6 This is a schematic flowchart of a communication method according to an embodiment of this application.

[0180] In S610, the first network function sends first information to one or more third network functions. Correspondingly, the one or more third network functions receive the first information from the first network function.

[0181] The first information indicates one or more capability items associated with a service, each of which is associated with one or more capabilities. The service can be any of the aforementioned XaaS services or the aforementioned NC. A third network function is deployed within this service. Therefore, one or more third network functions can report their capabilities based on one or more capability items. These one or more third network functions can report one or more capabilities that the first network function can resolve. This enables interaction between various network functions, thereby supporting a variety of services within the communication system.

[0182] The first network function can be any network function that publishes the first piece of information. For example, the first network function can be a network function deployed in CONET. For more details about CONET, please refer to [link / reference needed]. Figure 5 This application does not impose any limitations on this.

[0183] One or more third-party network functions can be various network functions that report their capabilities. For example, a third-party network function can be a function deployed in NET4AI, DAM, NET4DW, etc. For detailed information on the above services, please refer to [link / reference needed]. Figure 5 This application does not impose any limitations on this.

[0184] It is worth noting that, in the embodiments of this application, one or more third network functions may also be referred to as one or more NC providers, such as NET4AI provider, DAM provider, NET4DW provider, etc.

[0185] When a first network function sends first information to multiple third network functions, it can send corresponding first information to each of those third network functions. For example, the first network function sends first information #1 to a third network function deployed in NET4AI, where information #1 indicates one or more capability items associated with NET4AI. Similarly, the first network function sends first information #2 to a third network function deployed in DAM, where information #1 indicates one or more capability items associated with DAM. Therefore, multiple third network functions can report their own capabilities based on one or more corresponding capability items, while the first network function can uniformly maintain the capabilities of multiple third network functions.

[0186] Capabilities associated with a service can be referred to as various (or dimensional) capabilities associated with that service. For example, one or more capability dimensions may include one or more of the following: capability dimensions (such as the functions provided by the service), regional granularity dimensions (such as the available regional range), time window dimensions (such as the available time range), traffic granularity dimensions (such as the available traffic granularity), operational dimensions (such as processing collected data for output), output data type dimensions (such as the type of output data), output data format dimensions (such as the format of output data), and data destination dimensions (such as the destination to which the output data is sent). Capabilities associated with different services can vary.

[0187] The aforementioned capability dimensions are for illustrative purposes only. A first network function can determine one or more required capability items based on the types of various third network functions. Then, a third network function (such as NET4AI, DAM, NET4DW, etc.) can determine one or more capabilities for each of the one or more capability items. For example, for the output data format dimension, an NC provider can provide two capabilities: structured data and unstructured data.

[0188] For ease of description, one or more capability dimensions associated with a service may be named the capability dimension set of that service. Capability items associated with a service may be referred to as various (or different dimensions of) capabilities associated with that service. In some embodiments, the terms "capability item" and "capability dimension" are used interchangeably. A capability dimension set may include one or more capability dimensions, or a capability dimension set may include one or more capability items.

[0189] In some embodiments, the first information also indicates an explanation of one or more capability items. For example, the first information may include explanatory information (such as explanatory items, explanatory fields, etc.) for some or all of the capability items. For example, for a time window capability item, the explanatory information may indicate that the NC provider can report one or more capabilities regarding the available time range. Therefore, the NC provider can more accurately understand one or more capability items based on the explanation.

[0190] In some embodiments, the first information also indicates one or more examples of one or more capabilities associated with any of the one or more capability items. For example, for a time window capability item, the first information may include one or more examples of that capability item, such as a 1-second time window, an on-demand time window, etc. Therefore, these examples can help the NC provider understand one or more capability items.

[0191] It is worth noting that the first information may also include any other information used to describe one or more capability items. This application does not limit this.

[0192] In some embodiments, the first information may be presented in the form of natural language (such as at least one table) or formatted language. For example, the first information may be called a network capability description (language) (NCD(L)), which is a collection of information related to network capability description.

[0193] For example, for each NC (or service), the first network function defines a set of dimensions and publishes it along with guidelines for each NC provider, such as definitions of information elements, brief explanations of each dimension, and one or more examples of each dimension. The NC provider can then publish its capabilities according to these guidelines, for example, by filling out an NCD(L) form using the defined set of dimensions.

[0194] Descriptions of NCs (such as NET4AI, DAM, NET4DW, etc.) can simultaneously support descriptions of their capabilities by both 6G networks and third-party service providers. For each NC, basic service requirements can be defined for the NC provider to ensure the provision of that type of NC (or service). To this end, NC-specific basic requirements can be abstracted into independent description dimensions and exposed to the NC provider.

[0195] To facilitate understanding of the embodiments of this application, Table 1 shows the first information indicating the DAM data collection (DC) capability item. Table 2 shows the first information indicating the NET4AI capability item. Table 3 shows the first information indicating the NET4DW capability item.

[0196] Table 1:

[0197] As shown in Table 1, this table is an example of the set of network definition capability dimensions for DAM-DC, including a brief explanation and example for each dimension. This table provides guidance for DAM-DC providers to create their NCD(L)-based profiles. It defines several NC-specific basic service requirements (i.e., capability dimensions), such as area granularity, time window, traffic granularity, operation type, and data destination, which can be used for data collection services.

[0198] Table 2:

[0199] As shown in Table 2, this table is an example of the set of network-defined capability dimensions for NET4AI. NET4AI providers can report capabilities for AI applications based on Table 2. Detailed information is omitted here.

[0200] Table 3: Set of NET4DW Capabilities

[0201] As shown in Table 3, this table is an example of the set of network-defined capability dimensions for NETDW. NETDW providers can report capabilities for the digital world based on Table 3. Detailed information is omitted here.

[0202] It is worth noting that the capability dimension sets of DAM-DC, NET4AI, and NETDW described above are for illustrative purposes. Although not shown in the diagram, the first network function can define capability dimension sets for other NCs (or services) in a similar manner.

[0203] In some embodiments, the first information may also indicate a format that each of at least one capability can report according to. Therefore, one or more NC providers can report one or more of their capabilities according to the indicated format. This enables the first network function to maintain its service capabilities more efficiently.

[0204] For example, each of at least one capability is reported in a format that includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

[0205] In some embodiments, the first information indicates that one or more NC providers may further report one or more indexes of one or more of their capabilities. These indexes may be assigned by one or more NC providers and may be used to identify one or more capabilities. Thus, in subsequent interactions, the first network function and one or more NC providers may use one or more indexes to refer to one or more capabilities.

[0206] In some embodiments, the first information indicates that one or more NC providers may further report one or more conditions under which the corresponding capability is activated. For example, when activating a clustering method, the NC provider may activate the "data points for classification" capability, where "activating clustering method" may refer to the condition under which the NC provider activates the "data points for classification" capability. The NC provider may then report this condition based on the indicated format. Therefore, the first network function can maintain these one or more conditions and configure one or more NC providers based on these one or more conditions to achieve reliable configuration.

[0207] In some implementations of these embodiments, the condition for a capability to be activated can be another capability of the NC provider. Referring to the example above, the "clustering method" can be a capability of the NC provider, for which an index can be assigned. In other words, the condition can be presented as one or more indexes, since each capability can have a separate index.

[0208] In some implementations of these embodiments, the first information may also instruct one or more NC providers to report whether a corresponding capability is mandatory or optional when one or more conditions are met. For example, when the first information indicates that a corresponding capability is mandatory when a condition is met, that is, if the first network function has determined that the condition is a first capability to be activated, then that capability also needs to be a first capability to be activated. Alternatively, when the first information indicates that the corresponding capability is optional, if the condition is determined to be a first capability to be activated, the first network function can select the capability according to its own needs (it is not mandatory).

[0209] While the first network function can define one or more capability items (or one or more capability dimensions) for each service (e.g., as shown in Tables 1 through 3), the first information can be uniformly formatted. For example, the format can be presented as natural language (such as tables) or a formatted language.

[0210] For example, the first information instructs the second information to be reported according to a format that includes three information elements for each capability. The second information is sent by a third network function to indicate at least one capability associated with one or more capability items. The first information element includes an index of the capability, the second information element includes a description of the capability, and the third information element includes the conditions of the capability. For ease of understanding of the embodiments of this application, Figure 7 An example of the format is shown.

[0211] refer to Figure 7 The first row of the table includes multiple dimensions, such as Dimension 1, Dimension 2, etc. The second row indicates the format of each capability under each dimension, including the index, description, and conditions (presented as (preconditions, whether required)). Subsequent rows can list the dimension entries for NC providers (i.e., third-party network capabilities). In other words, NC providers can fill in the index, description, and condition elements for one or more of their capabilities. Figure 7 Two examples are shown: In the first example, the index of "Ability 1" under "Dimension 1" is filled in as "D1.1", and "N / A" indicates that the ability has no conditions. In the second example, the index of "Ability 2" under "Dimension 1" is filled in as "D1.2", and "(D2.1, True)" indicates that the condition for this ability to be activated is that Ability 1 (not shown) under Dimension 2 is activated, and when this condition is met, ability "D1.2" is required. Although not shown in the figure, if "True" is replaced with "False", it means that the ability is optional when the condition is met.

[0212] The first network function can indicate a format including these three elements. The NC provider can then generate a [database / configuration] based on the indicated capability items (dimensions) and the format. Figure 7 A table similar to the one in the example. Alternatively, the first network function can publish to... Figure 7 The form is similar to the one described above, and the NC provider can fill in the entries. Alternatively, the format can be predefined, and the initial information may not require instructions on the format. This application does not limit this.

[0213] In S620, one or more third network functions send second information to a first network function. Correspondingly, the first network function receives the second information from one or more third network functions.

[0214] The second information indicates at least one capability associated with one or more capability items reported based on the first information. One or more third network functions may generate the second information based on their associated one or more capability items. For example, when the first information indicates a set of capability dimensions (e.g., as shown in Tables 1 to 3), one or more third network functions may provide relevant information based on that set of capability dimensions.

[0215] As mentioned above, the information collected by each NC provider can be categorized into capability dimensions. The first network function defines one or more capability dimensions for each service (such as NET4AI, DAM, NET4DW, etc.) and exposes them to each NC provider. Under each capability dimension, the NC provider provides one or more capabilities to generate its second information (such as an NCDL-based configuration file). In other words, an NC provider's functionality is supported by one or more capabilities; its NCDL-based configuration file includes registration information for one or more capabilities and information on the coupling relationships between those capabilities.

[0216] For example, the second information includes a description element that indicates one or more capabilities under each dimension. This description element can define a brief description of each capability.

[0217] In some embodiments, each capability can be reported according to a format. This format can be indicated by first information or predefined; details can be found in S610, which is omitted here. For example, a capability can be reported according to a format that includes an index and / or conditions. Accordingly, the second information may include index elements, description elements, and condition elements.

[0218] An NC provider can identify one or more capabilities for each of its capability items (or dimensions). A single capability dimension can be associated with one or more capabilities. For example, for the output data format dimension, an NC provider can support two capabilities: structured data and unstructured data.

[0219] NC providers can assign an index to each capability. For example, this index can include a first part and a second part: the first part can refer to the corresponding capability dimension, and the second part can refer to the capability under that corresponding capability dimension. For instance, if an NC provider supports two capabilities under the output data format dimension: structured data and unstructured data, then the index for the structured data capability can be represented as "ODF.1", and the index for the unstructured data capability can be represented as "ODF.2", where "ODF" can be the first part, indicating the output data format dimension, and "1" and "2" can be the second parts, indicating these two capabilities. The index elements of the second information can define the index for that capability, and this index is unique within each NC provider.

[0220] The NC provider can also determine one or more conditions (if any) for each capability to be activated. Condition elements can be represented as value pairs, for example, Figure 7 The value shown is “(Preconditions, Required)”. The “Preconditions” value specifies which one or more capabilities must be activated before selecting the corresponding capability. The “Required” value indicates whether the capability is required (i.e., “Required” value = True) or optional (i.e., “Required” value = False) when the “Preconditions” are met. This value pair reflects the relationship between the current capability activation and other capability activations, which can further indicate the coupling relationship between multiple capabilities supported by various NCs (or services).

[0221] In some embodiments, the NC provider may also report one or more parameters related to one or more capabilities.

[0222] For example, when an NC provider reports on-demand time window capabilities under the time window capability dimension, this indicates that the NC provider can accept time windows specified by other network functions (or other devices). The NC provider can report one or more parameters indicating the acceptable range of time windows. For example, an on-demand time window can be represented as "T_min ≤ T ≤ T_max", where "T_min" represents the start time of the time window and "T_max" represents the end time of the time window. The NC provider can report T_min ≥ MIN, T_max ≤ MAX, where the parameter "MIN" represents the minimum acceptable value for the start time of the time window, and the parameter "MAX" represents the maximum acceptable value for the end time of the time window. In other words, the parameters "MIN" and "MAX" can be determined and reported by the NC provider reporting the time window, and other network functions (or devices) can specify the exact value of parameter "T_min" based on parameter "MIN" and specify parameter "T_max" based on parameter "MAX".

[0223] For example, one or more parameters can indicate multiple options associated with a corresponding capability. For instance, when an NC provider reports cell capabilities at the regional granularity level, it can further report its acceptable cell identifiers (IDs). That is, if the NC provider reports cell ID: option={ID1, ID2, ID3}, then the parameters “ID1”, “ID2”, and “ID3” represent its acceptable cell IDs.

[0224] For ease of description, parameters that can be specified by other network functions (or other devices), such as options for T_min, T_max, or cell ID, can be collectively referred to as variable parameters.

[0225] It is worth noting that NC providers may report one or more parameters related to one or more of their capabilities through the second information or any other information, and this application does not limit this. When the second information indicates one or more parameters, those parameters may be included in the description element.

[0226] In some embodiments, the second information may also indicate that the value of the variable parameter may be included in the index of the corresponding capability. For example, the index element may indicate an index following a given pattern, such as CapabilityID.{Parameter1}.{Parameter2}. The capabilityID may include a first part and a second part indicating the capability, while {Parameter1} and {Parameter2} represent the available parameters.

[0227] For example, the NC provider reports on-demand time window capabilities under the time window dimension, where the time window is represented as "T_min≤T≤T_max". The index element of the on-demand time window capability can be represented as "TW.3.{T_min}.{T_max}", where "TW.3" indicates the on-demand time window capability, and {T_min} and {T_max} indicate variable parameters. When the NC provider receives information indicating the index TW.3.{t1}.{t2}, it can activate the on-demand time window with start and end times from t1 to t2.

[0228] For example, when an NC provider reports cell capabilities at the regional granularity level, acceptable cell IDs are "ID1", "ID2", and "ID3". The index element for a cell capability can be represented as "AG.2.{1~3}" or "AG.2.{Cell ID}", where "AG.2" indicates the cell capability at the regional granularity level, and {1~3} or {Cell ID} indicates a variable parameter. When the NC provider receives information indicating the index AG.2.{1} or AG.2.{ID1}, it can activate the cell capability at the regional granularity level based on ID1.

[0229] It is worth noting that how an NC provider reports its capabilities in a specific format can be predefined or indicated by the first network function. For example, an NC provider can determine its capabilities based on capability items (e.g., Tables 1, 2, and 3) and based on the indicated format (e.g., ... Figure 7 Generate second information. For example, such as... Figure 7 As shown, the dimension set is a combination of capability dimensions determined by the first network function for one or more NC providers (such as a class of NC providers). Each NC provider describes its capabilities by filling in the values ​​of dimension entries. For each dimension entry, the NCD(L)-based configuration file includes three information elements (such as an index element, a description element, and a condition element).

[0230] As can be seen from the above description of the first information, different NC providers can receive different types of first information. Tables 1, 2, and 3 correspond to DAM-DC, NET4AI, and NET4DW, respectively. For ease of understanding this embodiment, the configuration files generated by DAM-DC, NET4AI, and NET4DW based on Tables 1, 2, and 3 are shown in Tables 4, 5, and 6, respectively.

[0231] Table 4: NCD(L)-based configuration files generated by DAM-DC providers

[0232] As shown in Table 4, this table is an example of a DAM-DC provider publishing its capabilities based on the set of dimensions in Table 1. The NCD(L)-based profile is presented in natural language (table). For each capability dimension (listed in the first column), the table contains one or more entries. For each entry, values ​​for three information elements (such as...) are given. Figure 7 (As shown).

[0233] For example, for the capability dimension, the DAM-DC provider supports the "Wireless Network Data Collection" capability. This capability is assigned an index "A.1", where "A" represents the capability dimension and "1" represents the capability. "N / A" in the "(Prerequisites, Required)" column indicates that there are no conditions for activating this capability. The meaning of "N / A" is similar in the various tables of this application.

[0234] For example, for the area granularity dimension, DAM-DC providers support two capabilities: "On-Demand" and "Cell ID". The "On-Demand" capability provides two options: "[center1, radium1]" and "[center2, radium2]". The "On-Demand" capability is assigned the index "AG.1.{1~2}", where "AG" represents the area granularity dimension, "1" represents the capability, and "{1~2}" indicates the variable parameters indicating these two options. The "Cell ID" capability provides three options: "ID1", "ID2", and "ID3". The "Cell ID" capability is assigned the index "AG.2.{1~3}", where "AG" represents the area granularity dimension, "2" represents the capability, and "{1~3}" indicates the variable parameters indicating these three options. The (preconditions, mandatory) elements for both capabilities are the same as (A.1, False), where "A.1" refers to the "Radio Network Data Collection" capability, indicating that the condition for these capabilities is that "Radio Network Data Collection" has been activated. “False” means that the activation of “AG.1.{1~2}” or “AG.2.{1~3}” is optional for the activation of “A.1”.

[0235] For the sake of brevity, other capabilities can be deduced by analogy with the above examples, and will not be elaborated here.

[0236] Table 5: NCD(L)-based configuration files generated by the NET4AI provider

[0237] It should be noted that the symbol "not index" (such as "not M.1" in the element (A.2¬ M.1, true) of the "Inference Result" capability) indicates that the condition is that the corresponding capability is not activated (e.g., the corresponding M.1 "Clustering" capability is not activated). The symbol "index#1&index#2" indicates that the condition is that the corresponding index#1 capability and the corresponding index#2 capability are activated simultaneously. If the symbol is presented as "index#1¬ index#2" (such as in the element (A.2¬ M.1, true)), it indicates that the condition is that the corresponding index#1 capability is activated and the corresponding index#2 capability is not activated. These symbols have similar meanings in other tables in this application.

[0238] In this embodiment, multiple capabilities can be requested in combination. For example, the NET4AI provider that generates Table 5 can request two RL-related capabilities in combination (such as RL model parameter updates with reward feedback as input, and RL action generation with action values ​​as output). The coupling relationship between these two capabilities is indicated by the configuration file. Specifically, "RL reward feedback" (IDT.3) is a required input to RL (M.2) because the value of its (precondition, required) element is (M.2, True). Similarly, "RL action {in progress, final state}" (ODT.3.{1,2}) is a required output to RL. Since reward feedback is the input to the RL model update capability, and actions are the output of the RL action generation capability, if a request involving (M.2, IDT.3, ODT.3.{1,2}) is received, these two capabilities must be requested in combination.

[0239] Table 6: NCD(L)-based configuration files generated by the NET4DW provider

[0240] The capabilities listed in the table above are for illustrative purposes only, and this application does not exclude other possible capabilities.

[0241] The second piece of information (such as NCDL-based configuration files) can be applied to the configuration and execution of task services. In one example, the NCDL-based configuration files of the relevant NC providers can be used to configure the individual NC providers and the data adaptation blocks required between them. In another example, the information in the configuration files can be used to indicate the processing operations required during task execution, such as the computational tasks performed by the individual NC providers and the data adaptation between them.

[0242] According to the above embodiments, one or more third network functions can report their capabilities based on one or more capability items. These one or more third network functions can report one or more capabilities that a first network function can resolve. This enables interaction between various network functions, thereby supporting various services in the communication system.

[0243] As can be seen from the above embodiments, the first network function receives the second information from the NC provider and can maintain the second information for use in subsequent processes (such as the task configuration process described below). In other words, the first network function can obtain these capabilities from one or more NC providers and maintain these capabilities for use in subsequent processes.

[0244] This section uses a task configuration process as an example to illustrate how the acquired second information is applied within the task configuration process. This application provides at least two implementation methods for the task configuration process. In the first implementation method, other network functions (i.e., non-first network functions) can configure one or more NC providers involved in the task. In the second implementation method, the first network function can configure one or more NC providers involved in the task.

[0245] First, in the first implementation, when other network functions (such as the second network function) configure one or more NC providers involved in the task, it can obtain the capabilities associated with these NC providers from the first network function.

[0246] Figure 8 This is a schematic flowchart illustrating a first implementation of the configuration process according to an embodiment of this application.

[0247] In step 810, the second network function acquires capability information.

[0248] This capability information indicates one or more capabilities associated with one or more services, where the task involves those services. The second network function can obtain capability information from the first network function. That is, the task can involve one or more NC providers. The capability information obtained from the first network function ensures interface matching between the involved NC providers when the task is executed.

[0249] The second network function can be a variety of network functions configured with multiple NC providers. For example, the first network function can interact with one or more other network functions and can provide organization, collaboration, or management services. For example, the second network function can be a function that provides MM services (or A-CAP services). As mentioned above, MM (or A-CAP) as a service can provide the ability to program the provision of XaaS services to manage task services.

[0250] In some embodiments, although not shown in the figures, step 810 may include: In step 811, the second network function acquires the task.

[0251] The task may be generated by a second network function, or the second network function may obtain the task from other network functions; this application does not limit this.

[0252] In step 812, the second network function determines one or more first services involved in the task.

[0253] The second network function can determine one or more services based on task requirements. For example, for a location-based RAN resource management and access (LOMA) task, the first network function can determine that the LOMA task involves DAM-DC, NET4AI, and NET4DW. Furthermore, the LOMA task involves network functions corresponding to DAM-DC, NET4AI, and NET4DW. This application does not limit this.

[0254] It is worth noting that detailed information about the above tasks can be found at [reference needed]. Figure 5 To facilitate understanding of the embodiments of this application, this application uses a LOMA task as an example for illustration. The task configuration process for other tasks can be deduced by referring to this example.

[0255] In step 813, the second network function sends third information to the first network function.

[0256] The third information request relates to one or more capabilities associated with one or more services involved in the task. For example, the third information indicates one or more identifiers of one or more first services, so the first network function can return information indicating one or more capabilities based on the indicated one or more identifiers.

[0257] In step 814, the first network function sends capability information to the second network function.

[0258] This capability information indicates one or more capabilities associated with one or more first services. First network functions can maintain information indicating capabilities associated with various types of services, which can be referenced in conjunction with... Figure 6 The description is as follows. Therefore, the first network function can respond to the third information by sending capability information to the second network function. For example, for a LOMA task, the capability information can indicate an NCD(L)-based profile generated by the DAM-DC, NET4AI, and NET4DW providers, as shown in Tables 4 through 6.

[0259] In some embodiments, each of one or more capabilities associated with the first service is described in a specific format. This format may be referenced in conjunction with... Figure 6 The description is omitted here. Generally speaking, the second network function can obtain the capabilities associated with various first services in a uniform format, which facilitates the configuration of these first services.

[0260] In step 820, the second network function determines one or more first capabilities involved in the task.

[0261] The second network function can identify the first service involved in the task, obtain the capability information of the first service, and determine the first capability involved in the task for each first service. For example, for DAM-DC, the second network function can obtain the NCD(L)-based configuration file (i.e., Table 4) generated by the DAM-DC provider, and select one or more suitable capabilities (i.e., one or more first capabilities) from it to enable multiple first services to collaboratively execute the task. The one or more capabilities can be determined according to the task requirements, and this application does not limit this.

[0262] In step 830, the second network function sends one or more first messages to one or more third network functions. Correspondingly, the one or more third network functions receive one or more first messages from the second network function.

[0263] The first message indicates one or more first capabilities. When a task involves multiple services, the second network function can send the first message to multiple third network functions corresponding to those services respectively.

[0264] In some embodiments, one or more first capabilities may be indicated based on a format. For example, capability information indicates an NCD(L)-based profile of a first service, wherein each capability is described according to a format that includes an index. Therefore, a first message may indicate one or more indexes of one or more first capabilities. Since the index of each capability can be assigned by the associated service provider, one or more third network functions can reliably parse the first message.

[0265] To facilitate understanding of the embodiments of this application, the LOMA task configurations for DAM-DC, NET4AI, and NET4DW generated based on Tables 4, 5, and 6 are shown in Tables 7, 8, and 9, respectively.

[0266] Table 7: Configuration of DAM-DC Providers Involved in LOMA Tasks

[0267] As shown in Table 7, the DAM-DC collects wireless network data under this configuration, including the data collection method, required data, and data transmission destination. There is a one-to-one relationship between the configured data types and data formats. If all data types require the same format, the data format configuration can be simplified to an index, as shown in Table 7.

[0268] As can be seen from Tables 4 and 7, the second network function selects at least one capability as the first capability for each capability dimension. When capability information indicates one or more parameters related to one or more capabilities (such as parameters that can be specified by the second network function, or multiple options that can be determined by the second network function), the second network function can determine the values ​​of these parameters. For example, for the time window dimension, the second network function determines "on-demand time window" as the first capability of the task and determines the start time of the time window as t1 and the end time as t2. As another example, for the regional granularity dimension, the capability can provide three options, and the second network function selects option 1, indicating that the regional granularity is cell ID1. Other examples are not elaborated further.

[0269] Table 8: Configuration of NET4AI Providers Involved in LOMA Tasks

[0270] As shown in Table 8, NET4AI participated in two steps of the LOMA task. One step was to apply a clustering algorithm to partition the RAN region into partitions. The other step was to apply an RL method to design the size of each RU type for a partition. In addition to the learning algorithm, Table 8 also provides some other parameters related to data interaction with the NC, such as the data types and formats of the requested inputs and provided outputs.

[0271] Table 9: Configuration of NET4DW Providers Involved in LOMA Tasks

[0272] As configured in Table 9, NET4DW simulates the wireless network and evaluates the LOMA scheme. Table 9 specifies the input data required for NET4DW to perform environment simulation and generate test scheme results. Additionally, the performance metrics to be evaluated are also configured, specifying the type and format of the output data.

[0273] It is worth noting that Tables 7 to 9 above are for illustrative purposes only, and this application does not exclude other methods of indicating the first capability. For example, a second network function may send a series of indices of the first capability to the corresponding network function.

[0274] To further improve collaboration efficiency, each NC provider can support a first message (such as a service request) by activating a combination of capabilities (or executing a combination of operations) based on the processing logic defined by the NC. Compared to requesting a single capability (or operation) each time, this can save data interaction overhead between multiple NC providers or between service consumers (such as second network functions) and NC providers. To support requests for capability combinations, a separate descriptive dimension can be introduced to cover the information required to determine the combination.

[0275] In step 840, one or more third network functions activate one or more first capabilities.

[0276] Each network function can activate one or more corresponding primary capabilities to perform a task. Details of the execution process will be provided in conjunction with... Figure 11 and Figure 12 The details will be elaborated upon here, but will be omitted.

[0277] In some embodiments, for a single task involving multiple third network functions, the task may involve one or more interactions between two NC providers. If the interfaces of the two NC providers are incompatible, the second network function can further configure the interaction between the two NC providers. For example, an NC provider may combine requests for multiple operations (i.e., capabilities), in which case an indicator of the combination may appear in the data interaction. The method described above may also include steps 850 or 860.

[0278] There are at least two ways to configure the interaction between the two third network functions. For ease of description, in the embodiments of this application, the two third network functions are referred to as third network function #1 and third network function #2, respectively.

[0279] In the first implementation, the second network function can be configured to interact with the third network function #1 and / or the third network function. Details are as follows.

[0280] Optionally, in step 850, the second network function sends a second message to one or more third network functions. Accordingly, the one or more third network functions receive the second message from the second network function.

[0281] The second message indicates the configuration used for interaction between the two third network functions. Therefore, third network function #1 and third network function #2 can interact based on these configurations.

[0282] In some embodiments, these configurations include one or more of the following: data format capability of third network function #1, data format capability of third network function #2, data receiving network function of third network function #1 and third network function #2, data sending network function of third network function #1 and third network function #2, and one or more data processing operations between third network function #1 and third network function #2.

[0283] It is worth noting that the content of these configurations is based on task requirements, and this application does not limit them.

[0284] In some embodiments, when the task involves only sending data from third network function #1 to third network function #2, the second network function can send a second message to third network function #1 because the third network function can convert the data format (which third network function #2 can parse) before sending data to third network function #2 based on the above configuration. Correspondingly, when the task involves only sending data from third network function #2 to third network function #1, the second network function can send a second message to third network function #2. When the task involves sending data from third network function #1 to third network function #2 and from third network function #2 to third network function #1 simultaneously, the second network function can send a second message to both third network function #1 and third network function #2 simultaneously.

[0285] For example, this task involves sending data #1 from the NET4AI provider to the NET4DW provider and data #2 from the NET4DW provider to the NET4AI provider. Therefore, a second network function can send a second message to both the NET4DW provider and the NET4AI provider. A third configuration can indicate the format of data #1 and specify that the sender of data #1 is the NET4AI provider and the receiver of data #1 is the NET4DW provider. Furthermore, the second message can indicate the format of data #2 and specify that the sender of data #2 is the NET4DW provider and the receiver of data #2 is the NET4AI provider.

[0286] It is worth noting that the second messages sent to the third network function #1 and the third network function #2 can be the same or different. For example, when the second network function sends a second message to the third network function #1, information known to the third network function #1 can be omitted, and vice versa.

[0287] In the second implementation, the second network function can be configured with other network functions to assist the third network function #1 and the third network function #2 in interacting. Details are as follows.

[0288] Optionally, in step 860, the second network function sends a second message to the fourth network function. Accordingly, the fourth network function receives the second message from the second network function.

[0289] The fourth network function can be any network function that can be used for interaction; for example, the fourth network function can be a processing service function (PSF). This application does not limit this.

[0290] For example, a PSF can provide services to enable data exchange between two third-party network functions. In some cases, a task involves one or more NC providers with misaligned interfaces (such as different indexes and formats of the exchanged data). In such cases, an application-specific (APP-specific) PSF can be set up between these providers. An APP-specific PSF can be used to enable data exchange between one or more NC providers with misaligned interfaces. This PSF can perform data adaptation, including one or more of the following: format conversion, data segmentation, application-defined calculations, etc.

[0291] When the second network function sends a second message to the PSF, the second message can indicate the format of the PSF's input data and the format of the PSF's output data. For example, when the PSF is located between the third network function #1 and the third network function #2, the output data of the third network function #1 is the input data of the PSF, and the output data of the PSF is the input data of the third network function #2. In this case, the second message can indicate the format of the output data of the third network function #1 and the format of the input data of the third network function #2.

[0292] In some embodiments, a task may involve interactions between multiple network function pairs. One or more PSFs can be responsible for these interactions. A second message can indicate the configuration used for the interactions involved in the task. For ease of understanding of the embodiments of this application, Table 10 provides illustrative configurations of one or more PSFs in a LOMA task.

[0293] Table 10: Configuration of App-Specific PSF for LOMA Tasks

[0294] Because of a mismatch between the output data from upstream NC providers (such as DAM) and the input data entering downstream NC providers (such as NET4AI), a dedicated PSF for the application (i.e., Figure 11 PSF#1 and PSF#2 in Table 10 are configured as per Table 10. This table configures the data forwarding rules (i.e., the receiving and sending locations for a given data type) and the data processing rules (i.e., calculation functions and related data). The data types and data formats in Table 10 are represented by an "index," which refers to the "index" value given in Tables 4 to 6.

[0295] In some embodiments, the fourth network function may report one or more of its own capabilities, similar to the third network function. For example, it may define a capability to convert one type of data format to another, and so on. In these cases, the fourth network function may activate one or more corresponding capabilities based on a second message. The second message may indicate one or more capabilities corresponding to the above configuration.

[0296] One or more third and fourth network functions can interact based on the indicated configuration to perform tasks.

[0297] As can be seen from the above embodiments, the second network function can learn the capabilities of various services and use one or more related first capabilities to configure one or more related first services to collaboratively perform tasks, which makes the collaboration of multiple services possible.

[0298] The second network function obtains capability information from the first network function and configures the services involved in the task. Figure 8 As described above, in the second implementation, the first network function can configure the multiple services involved in the task itself.

[0299] It's worth noting that the configuration logic for these two implementations is similar; the difference lies in the main configuration element. A further description of the configuration logic can be found by referring to... Figure 8 The description is omitted here. When the first network function is the configuration subject for determining one or more first capabilities involved in the task, the first network function can be combined as follows: Figure 6 As the description shows, capability reports for each service are obtained, so the first network function does not need to obtain capability information from elsewhere.

[0300] Figure 9 This is a schematic flowchart illustrating a second implementation of the configuration process according to an embodiment of this application.

[0301] In step 910, the first network function determines one or more first capabilities involved in the task.

[0302] This step can be referred to in the description of step 820, which is omitted here.

[0303] It is worth noting that before determining one or more first capabilities, the first network function can acquire a task and determine the first service involved in that task. This process can be referred to in the descriptions of steps 811 and 812, which are omitted here.

[0304] In step 920, the first network function sends a first message to one or more third network functions. Accordingly, the one or more third network functions receive the first message from the first network function.

[0305] This step can be referred to in the description of step 830, which is omitted here.

[0306] In step 930, one or more third network functions activate one or more first capabilities.

[0307] This step can be referred to in step 840, and is omitted here.

[0308] Similarly, for a single task involving multiple third network functions, the task may involve one or more interactions between two NC providers. If the interfaces of the two NC providers are incompatible, the first network function can further configure the interaction between the two NC providers. In a first implementation, the first network function can configure the interaction method between network function #1 and / or network function #2, and can perform step 940. In a second implementation, the first network function can configure other network functions to assist network function #1 and network function #2 in their interaction, and can perform step 950.

[0309] Optionally, in step 940, the first network function sends a second message to one or more third network functions. Correspondingly, the one or more third network functions receive the second message from the first network function.

[0310] This step can be referred to in the description of step 850, which is omitted here.

[0311] Optionally, in step 950, the first network function sends a second message to the fourth network function. Accordingly, the fourth network function receives the second message from the first network function.

[0312] This step can be referred to in the description of step 860, which is omitted here.

[0313] As can be seen from the above embodiments, the first network function can learn the capabilities of various services and configure one or more related first services using one or more related first capabilities to collaboratively execute tasks, making collaboration among multiple services possible. Furthermore, compared to... Figure 8 The method described above allows the first network function to maintain capability information for various services, thus eliminating the overhead of interaction between the first and second network functions.

[0314] The above Figures 6 to 9 The various methods mentioned include methods for reporting one or more capabilities and methods for configuring one or more services involved in the task. These methods can all be implemented individually, and some can also be combined. For example, Figure 6 The methods mentioned in Figure 8 The methods mentioned can be combined to achieve the same result. For example, Figure 6 The methods mentioned in Figure 9 The methods mentioned can be combined to achieve the desired results. To facilitate understanding of the embodiments of this application, a LOMA task is used as an example. Figure 10 The following is given Figure 6 The methods mentioned in Figure 8 This is one implementation of the method combination mentioned above. For details on some steps, please refer to the above text; they will not be repeated here.

[0315] In this illustrative implementation, the first network function is exemplified by the network function deployed in CONET, abbreviated as CONET. The second network function is exemplified by the network function deployed in MM, abbreviated as MM. The third network function includes network functions deployed in DAM, NET4AI, and NET4DW, abbreviated as DAM, NET4AI, and NET4DW, respectively. PSF can handle the interaction between DAM, NET4AI, and NET4DW.

[0316] Figure 10 This is a schematic flowchart of a communication method according to an embodiment of this application.

[0317] In step 1001, CONET sends the first message #1 to NET4AI.

[0318] This step can be referred to in the description of step 610, which is omitted here.

[0319] In step 1002, CONET sends the first message #2 to DAM.

[0320] This step can be referred to in the description of step 610, which is omitted here.

[0321] In step 1003, CONET sends the first message #3 to NET4DW.

[0322] This step can be referred to in the description of step 610, which is omitted here.

[0323] In step 1004, NET4AI sends the second message #1 to CONET.

[0324] This step can be referred to in the description of step 620, which is omitted here.

[0325] In step 1005, DAM sends the second message #2 to CONET.

[0326] This step can be referred to in the description of step 620, which is omitted here.

[0327] In step 1006, NET4DW sends the second message #3 to CONET.

[0328] This step can be referred to in the description of step 620, which is omitted here.

[0329] In step 1007, MM obtains the task.

[0330] This step can be referred to in the description of step 810 (e.g., 811), and is omitted here.

[0331] In step 1008, MM determines the NET4AI, DAM, and NET4DW involved in the task.

[0332] This step can be referred to in the description of step 810 (e.g., 812), and is omitted here.

[0333] In step 1009, MM sends a third message to CONET.

[0334] This step can be referred to in the description of step 810 (e.g., 813), and is omitted here.

[0335] In step 1010, CONET sends capability information to MM.

[0336] This step can be referred to in the description of step 810 (e.g., 814), and is omitted here.

[0337] In step 1011, MM determines the capabilities involved.

[0338] This step can be referred to in the description of step 820, which is omitted here.

[0339] In step 1012, MM sends the first message #1 to NET4AI.

[0340] This step can be referred to in the description of step 830, which is omitted here.

[0341] In step 1013, MM sends the first message #2 to DAM.

[0342] This step can be referred to in the description of step 830, which is omitted here.

[0343] In step 1014, MM sends the first message #3 to NET4DW.

[0344] This step can be referred to in the description of step 830, which is omitted here.

[0345] In step 1015, MM sends a second message to PSF.

[0346] This step can be referred to in the description of step 860, which is omitted here.

[0347] In step 1016, NET4AI, DAM, and NET4DW activate one or more of the involved capabilities.

[0348] This step can be referred to in step 840, and is omitted here.

[0349] As can be seen from the above embodiments, various services can report their capabilities based on the first information. CONET can maintain the reported capabilities. When the MM determines that a task involves NET4AI, DAM, and NET4DW, the MM can obtain the capability information of NET4AI, DAM, and NET4DW, and configure NET4AI, DAM, and NET4DW based on this capability information, which makes the collaboration of multiple services possible.

[0350] To facilitate understanding of the embodiments of this application, a LOMA task is used as an example. Figure 11 and Figure 12 An exemplary execution flow is provided.

[0351] Figure 11 This is a schematic diagram of a LOMA task execution flow according to an embodiment of this application. This diagram may be referred to as a LOMA task execution flow. Figure 11 This example illustrates a task supporting multiple services with misaligned interfaces. In this example, the goal of the LOMA task is to associate a set of radio resources and data transmission parameters (such as transmit power and MCS level) with geographic location. The task first divides the area into multiple partitions and then manages the resource units (RUs) of each partition. The LOMA task involves three NC providers: DAM, NET4AI, and NET4DW, with NET4AI providing services in two separate steps.

[0352] like Figure 11 As shown, DAM can activate one or more capabilities based on the corresponding configuration and operate based on the activated capabilities, subsequently generating data #1. DAM can send the generated data #1 to PSF #1, which can perform data adaptation on data #1 based on the indicated configuration to obtain data #2 and data #3. PSF #1 then sends the adapted data #2 to NET4AI and data #3 to NET4DW. NET4AI receives data #2 and processes it based on the corresponding configuration. Afterwards, NET4AI's NET4AI partition can generate data #4 and send it to NET4AI-RU, while simultaneously generating data #5 and sending it to PSF #2. Subsequently, NET4AI's NET4AI-RU can generate data #6 and send it to PSF #2. PSF #2 performs data adaptation on data #5 and data #6 to generate data #7. PSF #2 then sends data #7 to NET4DW. NET4DW processes data #3 and data #7 based on the corresponding configuration and generates data #8. Then, NET4DW sends data #8 back to NET4AI-RU via PSF #2. Therefore, the LOMA task can be completed.

[0353] exist Figure 11 In the examples shown, Tables 4 through 6 present the NCD(L)-based configuration files for the NC providers involved. Accordingly, MMs can configure individual NC providers by specifying the indexes of activated capabilities, where one or more indexes can be selected for each NC capability dimension. Tables 7 through 9 present the configurations for the DAM, NET4AI, and NET4DW providers, respectively, listing the indexes of activated capabilities and brief descriptions.

[0354] It should be noted that, for ease of understanding, PSF#1 and PSF#2 are drawn separately. In the embodiments of this application, one or more PSFs involved in the task service can be implemented by one function or by multiple functions, and this application does not limit this.

[0355] Figure 12 This is another schematic diagram of the LOMA task execution flow according to one embodiment of this application. All configurations of the involved (NC and APP specific) PSF need to be associated with the task, such as mapping the configuration table to the task ID. During task execution, this ID, along with data type information, is included in each data interaction. The PSF uses both to identify pre-configured operations. Figure 12 An example of LOMA task execution is shown, where the task ID is represented by "mission_id_loma" and the data type is represented by the index value given in Tables 4 to 6.

[0356] Numbered arrows indicate data interactions between the LOMA task client and the involved PSFs, with the numbers indicating the order of these interactions. Loops exist within the RL algorithm, requiring repeated data interactions, as shown by arrows 7 through 10. The content of the interacting data is represented by its NCD(L) defined data type index (e.g., ODT.1.{1~7}) or its keywords (e.g., “mission_id_loma” and “Designed LOMA map”). The operations performed by each PSF are given in the boxes, following the NC and APP-specific PSF configurations given in Tables 7 through 10. For detailed explanations, please refer to [reference needed]. Figure 12 This application does not impose any limitations on this.

[0357] Data interaction between multiple NC providers can be achieved using either HTTP or non-HTTP methods. Since the OpenAPI specification provides a standard for describing HTTP APIs, this application introduces a new description language to enable non-HTTP-based data interaction between multiple NC providers.

[0358] In the embodiments of this application, the 6G NC description may cover more information than that included in the OpenAPI description. For example, to ensure that the provider can support basic service requirements, NC-specific basic requirements can be abstracted into an independent description dimension. As another example, to improve the coordination efficiency between multiple NCs, the description may cover the information dimensions required by the NC provider to determine the operation combination.

[0359] The above text combined Figures 6 to 12 The method according to embodiments of this application is described in detail. The following will combine... Figure 13 and Figure 14 The apparatus provided in the embodiments of this application is described in detail. The description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the above method embodiments. For the sake of brevity, further details are omitted here.

[0360] refer to Figure 13 The diagram illustrates a schematic block diagram of a communication device according to an embodiment of this application. The communication device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can implement corresponding communication functions, and the processing unit 11 is used to perform data processing. The transceiver unit 11 can also be referred to as a communication interface or a communication unit.

[0361] In some embodiments, the communication device 10 may further include a storage unit. This storage unit can be used to store instructions and / or data. The processing unit 12 can read the instructions and / or data from the storage unit to enable the communication device to implement the method embodiments described above.

[0362] The communication device 10 can be used to perform operations executed by the first network function in the above method embodiments. In this case, the communication device 10 can be the first network function or a component configurable within the first network function. The transceiver unit 11 is used to perform communication-related (such as receive / transmit related) operations on the first network function side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the first network function side in the above method embodiments.

[0363] Communication device 10 can implement the embodiments of this application. Figures 6 to 12 The steps or processes executed by the first network function. The communication device 10 may include various units for performing... Figures 6 to 12 The method is executed by the first network function. Additionally, these units and the other operations and / or functions described above in the communication device 10 are respectively used to implement... Figures 6 to 12 The corresponding process in the text.

[0364] Alternatively, the communication device 10 can be used to perform operations performed by the second network function in the above method embodiments. In this case, the communication device 10 can be the second network function or a component configurable within the second network function. The transceiver unit 11 is used to perform communication-related (e.g., receive / transmit related) operations on the second network function side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the second network function side in the above method embodiments.

[0365] Communication device 10 can implement the embodiments of this application. Figures 6 to 12 The steps or processes executed by the second network function. The communication device 10 may include various units for performing... Figures 6 to 12 The method is executed by the second network function. Furthermore, these units and the other operations and / or functions described above in the communication device 10 are respectively used to implement... Figures 6 to 12 The corresponding process in the text.

[0366] The specific process by which the unit performs the corresponding steps described above is described in detail in the above method embodiments. For the sake of brevity, it will not be repeated here.

[0367] refer to Figure 14 The diagram illustrates a schematic block diagram of another communication device according to one embodiment of this application. The communication device 20 includes a processor 21. The processor 21 is coupled to a memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used to execute the computer programs or instructions and / or data stored in the memory 22 to perform the methods described in the above method embodiments.

[0368] In some embodiments, the communication device 20 includes one or more processors 21.

[0369] In one example, such as Figure 14 As shown, the communication device 20 may also include a memory 22.

[0370] In some embodiments, the communication device 20 may include one or more memories 22.

[0371] In one example, memory 22 may be integrated with processor 21 or may be set up separately from processor 21.

[0372] In one example, such as Figure 14 As shown, the communication device 20 may further include a transceiver 23 for receiving and / or transmitting signals. For example, the processor 21 may be used to control the transceiver 23 to receive and / or transmit signals.

[0373] In some embodiments, the communication device 20 may be a first network function or a component (such as a chip, circuit, or processing system) configurable in the first network function; or, the communication device 20 may be a second network function or a component (such as a chip, circuit, or processing system) configurable in the second network function.

[0374] In one embodiment, the communication device 20 is used to perform the operations performed by the first network function in the above method embodiments.

[0375] For example, processor 21 can be used to perform processing-related operations performed by the first network function in the above method embodiments, and transceiver 23 can be used to perform communication-related (such as receive / send related) operations performed by the first network function in the above method embodiments.

[0376] In another embodiment, the communication device 20 is used to perform the operations performed by the second network function in the above method embodiment.

[0377] For example, processor 21 can be used to perform processing-related operations performed by the second network function in the above method embodiments, and transceiver 23 can be used to perform communication-related (such as receive / send related) operations performed by the second network function in the above method embodiments.

[0378] In another embodiment, the communication device 20 is used to perform the operations performed by the third network function in the above method embodiments.

[0379] For example, processor 21 can be used to perform processing-related operations performed by the third network function in the above method embodiments, and transceiver 23 can be used to perform communication-related (such as receive / send related) operations performed by the third network function in the above method embodiments.

[0380] In another embodiment, the communication device 20 is used to perform the operations performed by the fourth network function in the above method embodiments.

[0381] For example, processor 21 can be used to perform processing-related operations performed by the fourth network function in the above method embodiments, and transceiver 23 can be used to perform communication-related (such as receive / send related) operations performed by the fourth network function in the above method embodiments.

[0382] One embodiment of this application also provides a computer-readable storage medium. This computer-readable storage medium stores computer instructions for implementing the methods described in the above-described method embodiments, which are executed by network functions (including a first network function, a second network function, a third network function, and / or a fourth network function).

[0383] For example, when a computer program is executed by a computer, the computer is able to implement the method described above, which is executed by network functions (including a first network function, a second network function, a third network function, and / or a fourth network function).

[0384] An embodiment of this application also provides a computer program product including instructions. When these instructions are executed by a computer, the computer is able to implement the methods described in the above method embodiments, which are executed by network functions (including a first network function, a second network function, a third network function, and / or a fourth network function).

[0385] One embodiment of this application also provides a communication system. This communication system includes the network functions described above (including a first network function, a second network function, a third network function, and / or a fourth network function).

[0386] For explanations and descriptions of the relevant content and beneficial effects of any communication device provided above, please refer to the corresponding method embodiments provided above. Further details will not be repeated herein.

[0387] The processor mentioned in the embodiments of this application can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gates, transistor logic devices, or discrete hardware components. The aforementioned general-purpose processor can be a microprocessor, or the aforementioned processor can be any conventional processor.

[0388] The memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. 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), or flash memory. The volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM can include a variety of forms, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0389] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, other programmable logic device, discrete gate or transistor logic device or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0390] It should also be noted that the memory described in this specification is intended to include, but is not limited to, these memories and any other suitable types of memory.

[0391] Those skilled in the art will recognize that, in conjunction with the various examples described in connection with the embodiments disclosed in this specification, the units and methods can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented through hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can employ different methods to implement the described functions for each specific application, but such implementations should not be considered to exceed the scope of protection of this application.

[0392] It should be noted that the term "receive / receiving" as used herein can refer to receiving or otherwise acquiring from a component / assembly within the same device or from another device separate from that device. Similarly, the term "transmit / transmitting" can refer to outputting or sending to a component / assembly within the same device or to another device separate from that device. For example, any method / process described herein can be performed by a chipset, in which case any transmitting or receiving step can be performed between components of the chipset.

[0393] Those skilled in the art will clearly understand that, for the sake of brevity, the specific working process of the above-described apparatus and units can be referred to the corresponding process in the above-described method embodiments. Further details are omitted here.

[0394] In the several embodiments provided in this application, the disclosed apparatus and methods can be implemented in other ways. For example, the described apparatus embodiments are merely examples. For example, dividing into units is only a logical functional division, and other division methods may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or described can be implemented through some interfaces. Indirect coupling or communication connection between devices or units can be implemented in electronic, mechanical or other forms.

[0395] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to implement the solution provided in this application, depending on actual needs.

[0396] In addition, the functional units in the embodiments of this application can be integrated into one unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0397] All or part of the above embodiments can be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments can be implemented in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of them generate the flow or function according to the embodiments of this application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. These computer instructions can be stored in a computer-readable storage medium or can be transmitted from one computer-readable storage medium to another. For example, these computer instructions can be transmitted from one website, computer, server, or data center to another via wired means (such as coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wireless means (such as infrared, radio, or microwave, etc.). The aforementioned computer-readable storage medium can be any available medium accessible to a computer, or a data storage device integrating one or more available media, such as a server or data center. The available medium can be a magnetic medium (such as a floppy disk, hard disk, or magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as an SSD), etc. For example, the available media may include, but are not limited to, various media that can store program code, such as USB flash drives, removable hard drives, ROM, RAM, disks, or optical discs.

[0398] The above description is merely one specific implementation of this application and is not intended to limit the scope of protection of this application. Any variations or substitutions that are readily conceived by those skilled in the art within the scope of the technology disclosed in this application are within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims and the specification.

Claims

1. A communication method executed by a first network function, characterized in that, include: Send (610) first information, wherein the first information indicates one or more capability items associated with the service, each of the one or more capability items being associated with one or more capabilities; Receive (620) second information, wherein the second information indicates at least one capability associated with the one or more capability items reported based on the first information.

2. The method according to claim 1, characterized in that, Each of the at least one capability is reported according to a specified format.

3. The method according to claim 2, characterized in that, The first information also indicates the format.

4. The method according to claim 2 or 3, characterized in that, Each of the at least one capability is reported in accordance with the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

5. The method according to claim 4, characterized in that, Each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

6. The method according to any one of claims 1 to 5, characterized in that, The first information also indicates one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any of the one or more capability items.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Receive third information from a second network function, wherein the third information requests at least one capability associated with the service; Send capability information to the second network function, wherein the capability information indicates the at least one capability.

8. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Maintain the second information.

9. The method according to any one of claims 2 to 8, characterized in that, The method further includes: Determine one or more first capabilities involved in the task of at least one of the capabilities (910); Send (920) a first message, wherein the first message indicates one or more first capabilities described in the format described.

10. A communication method performed by a second network function, characterized in that, include: Obtain (810) capability information, wherein the capability information indicates one or more capabilities associated with a first service, and the task involves the first service; Determine (820) one or more first capabilities involved in the task among the one or more capabilities associated with the first service; Send (830) a first message to a third network function corresponding to the first service, wherein the first message indicates the one or more first capabilities.

11. The method according to claim 10, characterized in that, Each of the one or more capabilities associated with the first service is described in a format, and each of the one or more first capabilities is described based on the format.

12. The method according to claim 11, characterized in that, Each of the one or more capabilities associated with the first service is described in the format described, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

13. The method according to claim 12, characterized in that, Each of the one or more capabilities associated with the first service is described in the format described, which also includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

14. The method according to any one of claims 10 to 13, characterized in that, The acquired capability information includes: Obtain the task; Identify one or more first services involved in the task; Send a third message to a first network function, wherein the third message requests one or more capabilities associated with the one or more first services; Receive the capability information from the first network function.

15. The method according to any one of claims 10 to 14, characterized in that, Sending the first message (830) to the third network function corresponding to the first service includes: Multiple first messages are sent to multiple third network functions deployed in multiple first services, wherein the task relates to the multiple first services, and each first message in the first message indicates a first capability related to the task associated with the corresponding first service.

16. The method according to claim 15, characterized in that, The method further includes: Send (850 or 860) a second message, wherein the second message indicates the configuration used for interaction between two of the plurality of third network functions.

17. The method according to claim 16, characterized in that, The configuration includes one or more of the following: the data format capabilities of the two third network functions, the data receiving network function of the two third network functions, the data sending network function of the two third network functions, and one or more data processing operations between the two third network functions.

18. The method according to claim 16 or 17, characterized in that, The sending of the second message (850 or 860) includes: Send (850) the second message to one or both of the two third network functions; or Send (860) the second message to the fourth network function, wherein the fourth network function is responsible for the interaction between the two third network functions.

19. A communication method performed by a third network function, characterized in that, include: Receive (610) first information, wherein the first information indicates one or more capability items associated with a service, each of the one or more capability items being associated with one or more capabilities; Send (620) a second message, wherein the second message indicates at least one capability associated with the one or more capability items reported based on the first message.

20. The method according to claim 19, characterized in that, Each of the at least one capability is reported according to a specified format.

21. The method according to claim 20, characterized in that, The first information also indicates the format.

22. The method according to claim 20 or 21, characterized in that, Each of the at least one capability is reported in accordance with the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

23. The method according to claim 22, characterized in that, Each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

24. The method according to any one of claims 19 to 23, characterized in that, The first information also includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any one of the one or more capability items.

25. The method according to any one of claims 19 to 24, characterized in that, The task involves the third network function, the first information is received from the first network function, and the method further includes: Receive (920) a first message from the first network function, wherein the first message indicates one or more first capabilities involved in the task of the at least one capability; or Receive (830) a first message from a second network function, wherein the first message indicates one or more first capabilities involved in the task of the at least one capability.

26. A communication method performed by a third network function, characterized in that, include: Receive (830 or 920) a first message, wherein the first message indicates one or more first capabilities involved in a task among one or more capabilities associated with a first service; Based on the first message, activate (840 or 930) one or more of the first capabilities.

27. The method according to claim 26, characterized in that, The method further includes: Receive (610) first information, wherein the first information indicates one or more capability items associated with the first service, each of the one or more capability items being associated with the one or more capabilities; Send (620) a second message, wherein the second message indicates at least one capability associated with the one or more capability items reported based on the first message.

28. The method according to claim 27, characterized in that, Each of the at least one capability is reported according to a format, and the one or more first capabilities are described based on the format.

29. The method according to claim 28, characterized in that, The first information also indicates the format.

30. The method according to claim 28 or 29, characterized in that, Each of the at least one capability is reported in accordance with the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

31. The method according to claim 30, characterized in that, Each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

32. The method according to any one of claims 27 to 31, characterized in that, The first information also includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any one of the one or more capability items.

33. The method according to any one of claims 26 to 32, characterized in that, The method further includes: Receive (850 or 940) a second message, wherein the second message indicates the configuration used for the interaction between the third network function and other network functions, the task relating to the interaction.

34. The method according to claim 33, characterized in that, The configuration includes one or more of the following: the data format capability of the third network function, the data format capability of the other network functions, the data receiving network function of the third network function and the other network functions, the data sending network function of the third network function and the other network functions, and one or more data processing operations between the third network function and the other network functions.

35. A communication method performed by a fourth network function, characterized in that, include: Receive (860 or 950) a second message, wherein the second message indicates the configuration used for interaction between at least two third network functions corresponding to at least two services, the task relating to said interaction; The second message is used to interact with the two third network functions.

36. The method according to claim 35, characterized in that, The configuration includes one or more of the following: the data format capabilities of the at least two third network functions, the data receiving network functions of the at least two third network functions, the data sending network functions of the at least two third network functions, and one or more data processing operations between the at least two third network functions.

37. A communication method, characterized in that, include: The first network function sends (610) first information to the third network function, wherein the first information indicates one or more capability items associated with the first service, each of the one or more capability items being associated with one or more capabilities; The third network function sends (620) second information to the first network function, wherein the second information indicates at least one capability associated with the one or more capability items reported based on the first information.

38. The method according to claim 37, characterized in that, The method further includes: The first network function sends capability information to the second network function, wherein the capability information indicates the at least one capability, and the task involves the first service; The second network function determines (820) one or more first capabilities involved in the task of the at least one capability; The second network function sends (830) a first message to the third network function, wherein the first message indicates the one or more first capabilities; The third network function activates (840) one or more of the first capabilities based on the first message.

39. The method according to claim 37, characterized in that, The method further includes: The first network function determines (910) one or more first capabilities involved in the task of the at least one capability; The first network function sends a (920) first message to the third network function, wherein the first message indicates the one or more first capabilities; The third network function activates (930) one or more of the first capabilities based on the first message.

40. The method according to any one of claims 37 to 39, characterized in that, Each of the at least one capability is reported according to a format, and each of the one or more first capabilities is described based on the format.

41. The method according to claim 40, characterized in that, The first information also indicates the format.

42. The method according to claim 40 or 41, characterized in that, Each of the at least one capability is reported in accordance with the format, which includes one or more of the following: an index of the corresponding capability, and one or more conditions under which the corresponding capability is activated.

43. The method according to claim 42, characterized in that, Each of the at least one capability is reported according to the format, which further includes information indicating whether the corresponding capability is mandatory or optional when the one or more conditions are met.

44. The method according to any one of claims 37 to 43, characterized in that, The first information also includes one or more of the following: an explanation of the one or more capability items, and one or more examples of one or more capabilities associated with any one of the one or more capability items.

45. The method according to any one of claims 38 to 44, characterized in that, Sending a first message from the second network function or the first network function to the third network function includes: The second network function or the first network function sends multiple first messages to multiple third network functions deployed in multiple first services, wherein the task relates to the multiple first services, and each first message in the first message indicates a first capability related to the task associated with the corresponding first service.

46. ​​The method according to claim 45, characterized in that, The method further includes: The second network function or the first network function sends a second message (850 or 940) to one or both of the plurality of third network functions, wherein the second message indicates the configuration used for the interaction between the two third network functions, the task relating to the interaction; and The two third network functions interact based on the second message; or The second network function or the first network function sends a second message (860 or 950) to the fourth network function, wherein the second message indicates the configuration used for an interaction between at least two of the plurality of third network functions, the task relating to the interaction; and The at least two third network functions and the fourth network function interact based on the second message.

47. The method according to claim 46, characterized in that, The configuration includes one or more of the following: the data format capabilities of the two third network functions, the data receiving network function of the two third network functions, the data sending network function of the two third network functions, and one or more data processing operations between the two third network functions.

48. An apparatus, characterized in that, The apparatus includes a processor and a memory, the memory storing one or more instructions executable on the processor, wherein when the one or more instructions are executed, the apparatus is capable of performing the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claims 35 or 36, or the method according to any one of claims 37 to 47.

49. An apparatus, characterized in that, The apparatus includes a function or unit for performing the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claim 35 or 36, or the method according to any one of claims 37 to 47.

50. A communication system, characterized in that, It includes a first network function and a third network function, wherein the first network function performs the method according to any one of claims 1 to 19, and the third network function performs the method according to any one of claims 19 to 25.

51. The system according to claim 50, characterized in that, The system further includes a second network function and / or a fourth network function, wherein the second network function performs the method according to any one of claims 10 to 18, and the fourth network function performs the method according to claim 35 or 36.

52. A communication system, characterized in that, It includes a second network function and a third network function, wherein the second network function performs the method according to any one of claims 10 to 18, and the third network function performs the method according to any one of claims 26 to 34.

53. The system according to claim 52, characterized in that, The system further includes a first network function and / or a fourth network function, wherein the first network function performs the method according to any one of claims 1 to 9, and the fourth network function performs the method according to claim 35 or 36.

54. A computer-readable storage medium, characterized in that, It includes one or more instructions, wherein when the one or more instructions are executed on a computer, the computer performs the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claim 35 or 36, or the method according to any one of claims 37 to 47.

55. A non-transitory computer-readable medium for storing instructions, characterized in that, The instructions cause a processor in the device to implement the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claim 35 or 36, or the method according to any one of claims 37 to 47.

56. A device, characterized in that, For performing the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claim 35 or 36, or the method according to any one of claims 37 to 47.

57. A processor, characterized in that, For executing instructions to cause the device to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claims 35 or 36, or the method according to any one of claims 37 to 47.

58. An integrated circuit, characterized in that, For performing the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 25, or the method according to any one of claims 26 to 34, or the method according to claim 35 or 36, or the method according to any one of claims 37 to 47.

Images