Collaborative service method and apparatus, and ran, network function, terminal and storage medium

Abstract

The present disclosure relates to a collaborative service method and apparatus, and an RAN, a network function, a terminal and a storage medium. The method comprises: a first RAN acquiring a terminal capability identifier of at least one terminal that accesses the first RAN, the terminal capability identifier comprising a capability field and a collaboration field, wherein the capability field is used for indicating whether the terminal supports a target capability, and the collaboration field is used for indicating whether the terminal supports exposing the target capability externally, and when the terminal supports exposing the target capability externally, the terminal is capable of providing a collaborative service for the target capability.

Description

Collaborative service methods, devices, RAN, network functions, terminals, and storage media

[0001] Related applications

[0002] This disclosure claims priority to Chinese patent application filed on July 9, 2024, with application number 2024109163756, entitled "Cooperative Service Method, Apparatus, RAN, Network Function, Terminal and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of mobile communication technology, and in particular to a collaborative service method, apparatus, RAN, network function, terminal and storage medium. Background Technology

[0004] In the vision of 6G (6th Generation mobile networks), the 6G network will be a huge distributed intelligent network. In addition to basic communication capabilities, the 6G network may add new capabilities such as sensing, intelligence, computing, and security. Terminals will not only be end users using connectivity services, but also diverse users using new services such as intelligent services, sensing services, and computing services.

[0005] There is currently no solution on how to fully utilize these new capabilities to reduce network deployment costs. Summary of the Invention

[0006] In a first aspect, some embodiments of this disclosure provide a cooperative service method. The cooperative service method is used in a first RAN, and the method includes:

[0007] Obtain the terminal capability identifier of at least one terminal accessing the first RAN;

[0008] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0009] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0010] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0011] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0012] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0013] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0014] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0015] In some embodiments, obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes:

[0016] Receive a registration request sent by the terminal, the registration request carrying at least one of the following:

[0017] The terminal capability identifier;

[0018] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0019] In some embodiments, the method further includes:

[0020] The registration request is sent to the first network function.

[0021] In some embodiments, the first network function is AMF.

[0022] In some embodiments, the registration request carries the terminal capability identifier and the terminal type, and the method further includes:

[0023] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0024] In some embodiments, the registration request carries the terminal type, and the method further includes:

[0025] Based on the terminal type, obtain the terminal capability identifier.

[0026] In some embodiments, obtaining the terminal capability identifier based on the terminal type includes:

[0027] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

[0028] In some embodiments, the method further includes:

[0029] The terminal capability identifier is carried in the registration request and sent to the first network function.

[0030] In some embodiments, the method further includes:

[0031] The system receives a terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table based on the terminal type and verifying the terminal capability identifier based on the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[0032] If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

[0033] In some embodiments, the second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

[0034] In some embodiments, receiving the terminal capability verification notification sent by the first network function includes:

[0035] Receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

[0036] In some embodiments, obtaining the terminal capability identifier based on the terminal type includes:

[0037] The registration request is sent to the first network function;

[0038] The terminal capability identifier returned by the first network function is received. The terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

[0039] In some embodiments, receiving the terminal capability identifier returned by the first network function includes:

[0040] The system receives a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

[0041] In some embodiments, obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes:

[0042] Under the condition that the preset conditions are met, a terminal capability request is sent to the terminal;

[0043] The terminal capability response sent by the terminal is received, and the terminal capability response carries the terminal capability identifier.

[0044] In some embodiments, the preset conditions include at least one of the following:

[0045] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0046] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0047] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0048] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0049] In some embodiments, when the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0050] In some embodiments, the method further includes:

[0051] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0052] In some embodiments, after receiving the terminal capability response sent by the terminal, the method further includes:

[0053] Send the terminal type and the terminal capability identifier to the first network function.

[0054] In some embodiments, before sending the terminal capability request to the terminal, the method further includes:

[0055] Receive the terminal capability request sent by the first network function.

[0056] In some embodiments, the method further includes:

[0057] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0058] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0059] In some embodiments, the cooperating terminal is a terminal that accesses the first RAN.

[0060] In some embodiments, the method further includes:

[0061] Send the service request to the collaborative terminal;

[0062] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[0063] In some embodiments, the method further includes:

[0064] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0065] In some embodiments, determining the collaborative terminal matching the service type and the service requirements based on the service request includes:

[0066] The service request is sent to the first network node;

[0067] The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

[0068] In some embodiments, the method further includes:

[0069] The system receives terminal service provider information of the collaborative terminal sent by the first network node and sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

[0070] In some embodiments, the service request is further used for the first network node to send the service request to a second network node or a central network node if the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0071] In some embodiments, the method further includes:

[0072] The system receives terminal servicer information of the collaborative terminal sent by the first network node, wherein the terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service.

[0073] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0074] Secondly, some embodiments of this disclosure provide a collaborative service method. The collaborative service method is used for a first network function, and the method includes:

[0075] Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function;

[0076] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0077] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0078] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0079] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0080] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0081] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0082] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0083] In some embodiments, obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes:

[0084] Receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following:

[0085] The terminal capability identifier;

[0086] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0087] In some embodiments, the registration request carries the terminal capability identifier and the terminal type, and the method further includes:

[0088] The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

[0089] In some embodiments, the registration request carries the terminal type of the terminal, and the method further includes:

[0090] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

[0091] In some embodiments, the method further includes:

[0092] The terminal capability identifier is sent to the first RAN in the context establishment response.

[0093] In some embodiments, the registration request further carries the terminal capability identifier, and the method further includes:

[0094] A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type.

[0095] The terminal capability verification notification is sent to the first RAN.

[0096] In some embodiments, the method further includes:

[0097] If the query result is different from the terminal capability identifier, then delete the entry in the second capability mapping table that corresponds to the terminal type.

[0098] In some embodiments, sending the terminal capability verification notification to the first RAN includes:

[0099] The terminal capability verification notification is sent to the first RAN along with the context establishment response.

[0100] In some embodiments, obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes:

[0101] Under preset conditions, the terminal capability identifier sent by the first RAN is received. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

[0102] In some embodiments, before receiving the terminal capability identifier sent by the first RAN, the method further includes:

[0103] Send the terminal capability request to the first RAN;

[0104] The step of receiving the terminal capability identifier sent by the first RAN includes:

[0105] The terminal capability response of the terminal is received from the first RAN, and the terminal capability response carries the terminal capability identifier.

[0106] In some embodiments, the preset conditions include at least one of the following:

[0107] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0108] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0109] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0110] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0111] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0112] In some embodiments, the method further includes:

[0113] The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

[0114] In some embodiments, the method further includes:

[0115] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0116] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0117] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access the same network node.

[0118] In some embodiments, the method further includes:

[0119] Send the service request to the collaborative terminal;

[0120] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[0121] In some embodiments, the method further includes:

[0122] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0123] In some embodiments, determining the collaborative terminal matching the service type and the service requirements based on the service request includes:

[0124] If no matching collaborative terminal is found according to the service request, the service request is sent to a second network node or a central network node so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0125] In some embodiments, the method further includes:

[0126] Receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[0127] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0128] In some embodiments, when the terminal service provider information is sent by the central network node, before sending the terminal service provider information to the target terminal, the method further includes:

[0129] Send a collaborative service request to the second network node;

[0130] Sending the terminal service provider information to the target terminal includes:

[0131] If a confirmation and collaboration response is received from the second network node, the terminal service provider information is sent to the target terminal.

[0132] In some embodiments, the first network function is AMF.

[0133] Thirdly, some embodiments of this disclosure provide a collaborative service method. The collaborative service method is used on a terminal, and the method includes:

[0134] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal.

[0135] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0136] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0137] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0138] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0139] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0140] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0141] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0142] In some embodiments, reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes:

[0143] Send a registration request to the first RAN, the registration request carrying at least one of the following:

[0144] The terminal capability identifier;

[0145] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0146] In some embodiments, before reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal, the method further includes:

[0147] Receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under the condition of meeting preset conditions;

[0148] The step of reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes:

[0149] A terminal capability response is sent to the first RAN, the terminal capability response carrying the terminal capability identifier.

[0150] In some embodiments, the preset conditions include at least one of the following:

[0151] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0152] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0153] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0154] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0155] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0156] In some embodiments, the method further includes:

[0157] A service request is sent to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

[0158] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[0159] The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or,

[0160] The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0161] In some embodiments, the method further includes:

[0162] Receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function;

[0163] A business session is established with the collaborating terminal based on the terminal service provider information.

[0164] In some embodiments, the method further includes:

[0165] During the collaborative service process between the terminal and the collaborating terminal, a first service processing result is sent to the network node;

[0166] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

[0167] In some embodiments, before sending the service request to the first RAN or the first network function, the method further includes:

[0168] The business to be processed is divided into business segments to obtain collaborative sub-businesses;

[0169] The business request is generated based on the business type and business requirements of the collaborative sub-business.

[0170] Fourthly, some embodiments of this disclosure provide a collaborative service apparatus. The collaborative service apparatus is located in a first RAN, and the apparatus includes:

[0171] The acquisition module is used to acquire the terminal capability identifier of at least one terminal accessing the first RAN;

[0172] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0173] Fifthly, some embodiments of this disclosure provide a collaborative service device. The collaborative service device is configured within a first network function, and the device includes:

[0174] The acquisition module is used to acquire the terminal capability identifier of at least one terminal accessing the first RAN, wherein the first RAN is the RAN that accesses the first network function;

[0175] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0176] Sixthly, some embodiments of this disclosure provide a collaborative service device. The collaborative service device is located on a terminal, and the device includes:

[0177] The sending module is used to report the terminal capability identifier of the terminal to the first RAN accessed by the terminal, and / or to report the terminal capability identifier to the first network function accessed by the terminal;

[0178] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0179] In a seventh aspect, some embodiments of this disclosure provide a RAN. The RAN includes a memory, a transceiver, and a processor.

[0180] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0181] Obtain the terminal capability identifier of at least one terminal accessing the first RAN;

[0182] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0183] Eighthly, some embodiments of this disclosure provide a network function. The network function includes a memory, a transceiver, and a processor.

[0184] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0185] Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function;

[0186] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0187] Ninthly, some embodiments of this disclosure provide a terminal. The terminal includes a memory, a transceiver, and a processor.

[0188] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0189] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal.

[0190] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0191] In a tenth aspect, some embodiments of this disclosure provide a computer-readable storage medium. The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the methods described in the first, second, or third aspects above.

[0192] Eleventhly, some embodiments of this disclosure provide a chip. The chip includes programmable logic circuitry and / or program instructions that, when the chip is executed, implement the steps of the methods described in the first, second, or third aspects above.

[0193] In a twelfth aspect, some embodiments of this disclosure provide a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the methods described in the first, second, or third aspect.

[0194] The aforementioned collaborative service method, apparatus, RAN, network function, terminal, and storage medium involve the first RAN acquiring a terminal capability identifier of at least one terminal accessing the first RAN. This terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports a target capability, and the collaboration field indicates whether the terminal supports externally accessible target capabilities. Thus, based on the acquired terminal capability identifier, the first RAN can determine whether the terminal supports externally accessible target capabilities. Target capabilities include, for example, intelligent capabilities such as intelligent training and intelligent inference capabilities, as well as intelligent capabilities such as signal sensing, temperature sensing, and humidity sensing capabilities, and computing capabilities such as computing processing capabilities and computing task segmentation capabilities, etc. When the terminal supports externally accessible target capabilities, the terminal can provide collaborative services for the target capabilities. For example, the terminal can utilize the aforementioned intelligent capabilities, sensing capabilities, computing capabilities, and other target capabilities to provide intelligent services, sensing services, computing services, etc., thereby fully utilizing the terminal's target capabilities and enhancing the network capabilities at the edge through the terminal's capabilities, thereby reducing network deployment costs. Attached Figure Description

[0195] To more clearly illustrate the technical solutions in some embodiments or related technologies of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on the disclosed drawings without creative effort.

[0196] Figure 1 is a schematic diagram of the implementation environment of a collaborative service method provided by some embodiments of this disclosure;

[0197] Figure 2 is a flowchart illustrating the collaborative service method in some embodiments;

[0198] Figure 3 is a schematic diagram of terminal capability identification in some embodiments;

[0199] Figure 4 is a flowchart illustrating the collaborative service method in some other embodiments;

[0200] Figure 5 is a flowchart illustrating the collaborative service method in some other embodiments;

[0201] Figure 6 is a flowchart illustrating the relevant initial registration process for terminals;

[0202] Figure 7 is a flowchart illustrating the collaborative service method in some other embodiments;

[0203] Figure 8 is a flowchart illustrating the collaborative service method in some other embodiments;

[0204] Figure 9 is a flowchart illustrating the collaborative service method in some other embodiments;

[0205] Figure 10 is a flowchart illustrating the collaborative service method in some other embodiments;

[0206] Figure 11 is a flowchart illustrating the collaborative service method in some other embodiments;

[0207] Figure 12 is a flowchart illustrating the collaborative service method in some other embodiments;

[0208] Figure 13 is a flowchart illustrating the collaborative service method in some other embodiments;

[0209] Figure 14 is a flowchart illustrating the relevant session establishment process;

[0210] Figure 15 is a flowchart illustrating the collaborative service method in some other embodiments;

[0211] Figure 16 is a flowchart illustrating the collaborative service method in some other embodiments;

[0212] Figure 17 is a flowchart illustrating the collaborative service method in some other embodiments;

[0213] Figure 18 is a flowchart illustrating the collaborative service method in some other embodiments;

[0214] Figure 19 is a structural block diagram of the collaborative service device in some embodiments;

[0215] Figure 20 is a structural block diagram of the collaborative service device in some other embodiments;

[0216] Figure 21 is a structural block diagram of the collaborative service device in some other embodiments;

[0217] Figure 22 is a schematic diagram of the RAN structure in some embodiments;

[0218] Figure 23 is a schematic diagram of the network function in some embodiments;

[0219] Figure 24 is a schematic diagram of the terminal structure in some embodiments;

[0220] Figure 25 is a schematic structural diagram of the chip in some embodiments. Detailed Implementation

[0221] The technical solutions of some embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0222] In some embodiments of this disclosure, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0223] In some embodiments of this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0224] In 5G (5th Generation mobile networks) networks, terminals are mainly designed for three application scenarios: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (uRLLC), and massive machine-type communications (mMTC), primarily to meet communication needs.

[0225] In the vision of 6G (6th Generation mobile networks), the 6G network will no longer be merely a communication network, but a vast distributed intelligent network. Besides basic communication capabilities, 6G networks may add new capabilities such as sensing, intelligence, computing, and security. Future 6G networks are expected to provide various high-precision sensing services and support a wide range of complex sensing application scenarios. With the introduction of new services, the service targets within the 6G network will expand. The widespread application of digitalization and the formulation of global digital strategies have created an urgent need for new capabilities for terminals in 6G networks.

[0226] In the vision of 6G terminals: 1) Terminals will generate more and more information at an increasingly faster speed. As the source of information, terminals will generate massive amounts of information in real time. Terminals will support 3D (Three Dimensions) audio (spatial audio), 3D video (spatial video), smart assistants, and digital world information during the information generation process. 2) Terminals will acquire user input more efficiently. Terminals can obtain user information input in real time through diverse and intelligent human-computer interaction methods. These methods will support holographic interaction and even brain-computer input. During the information input process, the terminal's input sensors will support the input and collection of tactile, olfactory, and gustatory information. 3) Terminals will have more powerful local storage capabilities, enabling real-time local storage of acquired information. The storage capacity will be increased by a thousandfold, reaching the petabyte (PB) level. The stored information will include not only physical world information but also digital world information. 4) Terminals will have increasingly powerful processing capabilities, enabling real-time information processing. In the information processing stage, the terminal will expand from image and voice data processing to support 3D and virtual data processing. This will require the use of more efficient new processors, and the terminal's computing power will increase from TTOPS (one trillion operations per second) to PTOPS (ten quadrillion operations per second). 5) The terminal will have higher transmission rates and lower latency, enabling real-time transmission (including sending and receiving) of massive amounts of information. 6G terminals will support the transmission of 3D multimedia information, with peak rates increasing a thousandfold to Tbps (terabits per second). They will also support AI (Artificial Intelligence) communication, communication sensing fusion, and space-air-ground communication. 6) The terminal will have richer presentation capabilities, enabling real-time presentation of complex, multi-dimensional information. Breaking away from the current 2D (Two Dimensions) information presentation, the terminal will support 3D video, holographic images, and 3D audio, further supporting the presentation of tactile, olfactory, and gustatory information.

[0227] In 6G networks, terminals will not only be end users using connectivity services, but also diverse users utilizing new services such as computing, data, sensing, and intelligent services. In other words, 6G terminals, in addition to enhanced communication capabilities, will need to possess sensing, intelligent, computing (or computational power), and security capabilities to meet specific needs. In the vision of 6G networks, terminals can be both consumers and producers of functions / services. Therefore, there are currently no solutions on how to fully utilize these new capabilities to reduce network deployment costs.

[0228] In view of this, some embodiments of this disclosure provide a collaborative service method, apparatus, RAN (Radio Access Network), network function, terminal, and storage medium, which can fully utilize terminal capabilities and reduce network deployment costs.

[0229] Figure 1 is a schematic diagram of the implementation environment of a collaborative service method provided by some embodiments of this disclosure.

[0230] As shown in Figure 1, the first RAN 200 communicates with at least one terminal 100 within its network coverage area (Figure 1 only shows one terminal 100 as an example). The first RAN 200 also communicates with a first network function 300 via the network, and the terminal 100 also communicates with the first network function 300 via the network.

[0231] The first network function could be, for example, AMF (Access and Mobility Management Function).

[0232] The following description, using the implementation environment shown in Figure 1 as an example and in conjunction with the accompanying drawings of some embodiments of this disclosure, clearly and completely describes the technical solutions in some embodiments of this disclosure. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0233] The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0234] In some embodiments, as shown in FIG2, a cooperative service method is provided. Taking the application of this method to the first RAN in FIG1 as an example, the method includes the following steps:

[0235] Step 201: The first RAN obtains the terminal capability identifier of at least one terminal accessing the first RAN.

[0236] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports the externally exposed target capability. When the terminal supports the externally exposed target capability, the terminal can provide collaborative services for the target capability.

[0237] For example, the terminal capability identifier may be obtained by the first RAN during the initial registration of the terminal, or it may be obtained by the first RAN during the terminal registration update / periodic registration update process. The first RAN may also obtain the terminal capability identifier at other times. For example, the first RAN may obtain the terminal capability identifier periodically, or it may obtain the terminal capability identifier when a preset trigger time arrives. There is no limitation on the timing of the first RAN obtaining the terminal capability identifier.

[0238] After the first RAN obtains the terminal capability identifier of the terminal, it identifies the capability fields included in the terminal capability identifier to determine whether the terminal supports the target capability. For example, if the capability field is configured with a first value, it indicates that the terminal supports the target capability; if the capability field is configured with a second value, it indicates that the terminal does not support the target capability. The first value can be, for example, 1, and the second value can be, for example, 0. The first and second values ​​can also be other values, for example, the first value can be Y, the second value can be N, and so on.

[0239] The first RAN can also identify the cooperation field included in the terminal capability identifier, thereby determining whether the terminal supports the externally exposed target capability. For example, if the cooperation field is configured with a first value, it indicates that the terminal supports the externally exposed target capability; if the cooperation field is configured with a second value, it indicates that the terminal does not support the externally exposed target capability. Similar to the above, the first value can be, for example, 1, and the second value can be, for example, 0, etc.

[0240] In this way, after the first RAN obtains the terminal capability identifier of one or more terminals accessing the first RAN, for each terminal, the first RAN can determine whether the terminal supports the target capability based on the terminal capability identifier. For terminals that support the target capability, it can also determine whether the terminal supports exposing its target capability to the outside world. If the terminal supports exposing its own target capability to the outside world, then when there is a high-load task in the network that targets the target capability, in addition to network capabilities, the target capability of the terminal can also be considered. If the terminal is acceptable, the target capability of the terminal can be coordinated as needed to process the task and extend support. The method of coordinated service will be described by example in the following embodiments.

[0241] In some embodiments, the target capability may include one or more of intelligent capabilities, perception capabilities, and computing capabilities; in some embodiments, the target capability may include other capabilities in addition to one or more of the above-mentioned intelligent capabilities, perception capabilities, and computing capabilities, such as security capabilities, etc. There is no limitation on the specific capability type indicated by the target capability.

[0242] For example, in some embodiments of this disclosure, the capability field may include at least one of intelligent capability field, perception capability field, and computing capability field, that is, the capability field may have the following possible combinations: the capability field includes an intelligent capability field; the capability field includes a perception capability field; the capability field includes a computing capability field; the capability field includes an intelligent capability field and a perception capability field; the capability field includes an intelligent capability field and a computing capability field; the capability field includes an intelligent capability field, a perception capability field, and a computing capability field.

[0243] Among them, the intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0244] In some implementations, in addition to any of the above combinations, the capability field may further include fields for indicating other capabilities. For example, the capability field may also include a custom field for indicating whether the terminal supports capabilities other than intelligent capabilities, sensing capabilities, and computing capabilities.

[0245] Taking the capability fields, including intelligent capability fields, perception capability fields, and computing capability fields, as an example, see Figure 3. In the terminal capability identifier shown in Figure 3, the "intelligent" field represents the intelligent capability field, the "perception" field represents the perception capability field, the "computation" field represents the computing capability field, the "custom" field represents the custom field, and the "collaboration" field represents the collaboration field.

[0246] In this diagram, if the "Intelligence Capability" field is configured with a first value (e.g., "1" as shown in Figure 3), it indicates that the terminal supports intelligence capabilities; if the "Intelligence Capability" field is configured with a second value (e.g., "0"), it indicates that the terminal does not support intelligence capabilities. Similarly, if the "Perception Capability" field is configured with a first value (e.g., "1" as shown in Figure 3), it indicates that the terminal supports perception capabilities; if the "Perception Capability" field is configured with a second value (e.g., "0"), it indicates that the terminal does not support perception capabilities. If the "Computation Capability" field is configured with a first value (e.g., "1" as shown in Figure 3), it indicates that the terminal supports computation capabilities; if the "Computation Capability" field is configured with a second value (e.g., "0"), it indicates that the terminal does not support computation capabilities. Custom fields can be defined based on the terminal's subsequent capabilities during implementation. The terminal capability identifier shown in Figure 3 indicates that the terminal supports intelligence capabilities, perception capabilities, and computation capabilities, and that the terminal supports exposing its own intelligence capabilities, perception capabilities, and computation capabilities.

[0247] It should be noted that in some embodiments of this disclosure, the number of collaborative fields can be one or more. In some embodiments, when the number of collaborative fields is one, the collaborative field is used to indicate whether the terminal supports simultaneously opening one or more capabilities indicated by the capability field. Taking Figure 3 as an example, the terminal supports intelligent capabilities, sensing capabilities, and computing capabilities, and the number of collaborative fields is one. If the one collaborative field is configured as 1, it indicates that the terminal supports simultaneously opening its intelligent capabilities, sensing capabilities, and computing capabilities.

[0248] In some embodiments, when there are multiple collaborative fields, the capability fields, including intelligent capability fields and perception capability fields, can each correspond to a collaborative field. Each collaborative field is used to indicate whether the terminal supports opening up the capability indicated by the capability field corresponding to the collaborative field. For example, if the collaborative field corresponding to the intelligent capability field is configured as 1, it indicates that the terminal supports opening up its intelligent capability. If the collaborative field corresponding to the perception capability field is configured as 0, it indicates that the terminal does not support opening up its perception capability, and so on. The design method of the terminal capability identifier is not specifically limited here.

[0249] In some embodiments of this disclosure, intelligent capabilities may include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. Intelligent training capability refers to the terminal's ability to train an artificial intelligence model; intelligent reasoning capability refers to the terminal's ability to perform reasoning (or prediction) using the trained artificial intelligence model; and intelligent monitoring capability refers to the terminal's ability to perform monitoring (e.g., environmental monitoring) based on the artificial intelligence model. Perception capabilities include at least one of signal perception capabilities, temperature perception capabilities, humidity perception capabilities, image perception capabilities, location perception capabilities, and speed perception capabilities. These capabilities, in turn, refer to the terminal's ability to perceive signals, temperature, humidity, images, location, and speed, respectively. Temperature and humidity may be, for example, ambient temperature and ambient humidity. Computational capabilities include at least one of computational processing capabilities, computational task segmentation capabilities, and computational aggregation capabilities, etc.

[0250] Faced with diverse terminal forms and complex human-machine-object interaction scenarios, the 6G network concept requires terminals to support various new capabilities. However, due to limitations in terminal size, power consumption, and portability, terminals cannot add unlimited new capabilities. Terminals need to possess flexible, on-demand expandable and configurable capabilities, allowing them to use and expose their capabilities as needed. Therefore, some embodiments of this disclosure use terminal capability identifiers to indicate the capabilities the terminal possesses and whether it can expose its capabilities.

[0251] Overall, in the above embodiments, the first RAN obtains the terminal capability identifier of at least one terminal accessing the first RAN. The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports the externally exposed target capability. Thus, the first RAN can determine whether the terminal supports the externally exposed target capability based on the obtained terminal capability identifier. Target capabilities include intelligent capabilities such as intelligent training capabilities and intelligent inference capabilities, as well as intelligent capabilities such as signal sensing capabilities, temperature sensing capabilities, and humidity sensing capabilities, and computing capabilities such as computing processing capabilities and computing task segmentation capabilities, etc. When the terminal supports the externally exposed target capability, the terminal can provide collaborative services for the target capability. For example, the terminal can use the above-mentioned intelligent capabilities, sensing capabilities, computing capabilities, etc., to provide intelligent services, sensing services, computing services, etc., thereby making full use of the terminal's target capability, enhancing the edge network capability through the terminal's capability, and thus reducing network deployment costs.

[0252] The above embodiments briefly describe the design of the terminal capability identifier. Below, through several possible implementation methods, the process of the first RAN obtaining the terminal capability identifier of at least one terminal accessing the first RAN will be illustrated by way of example.

[0253] Referring to Figure 4, the first RAN can execute step 401 shown in Figure 4 to obtain the terminal capability identifier of at least one terminal accessing the first RAN:

[0254] Step 401: The first RAN receives a registration request sent by the terminal. The registration request carries at least one of the following: terminal capability identifier; terminal type, which is used to obtain the terminal capability identifier.

[0255] That is, the terminal sends a registration request to the first RAN. This registration request can be sent when the terminal initially registers, or it can be sent by the terminal during the registration update / periodic registration update process. This registration request can be an RRC (Radio Resource Control) message.

[0256] In a first possible implementation, the registration request includes the terminal's terminal capability identifier, that is, the terminal reports the terminal's terminal capability identifier to the first RAN that the terminal accesses.

[0257] In a second possible implementation, the registration request includes not only the terminal capability identifier but also the terminal type. That is, in addition to reporting its terminal capability identifier to the first RAN, the terminal also reports its terminal type. When the registration request carries both the terminal capability identifier and the terminal type, the first RAN can store the mapping relationship between the terminal type and the terminal capability identifier in a first capability mapping table. This first capability mapping table can be stored locally within the first RAN or in other devices. The storage format of the mapping relationship between the terminal type and the terminal capability identifier in the first capability mapping table will be exemplified in the following embodiments.

[0258] For example, the terminal type may include personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices may include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc., while portable wearable devices may include smartwatches, smart bracelets, head-mounted devices, etc. Head-mounted devices may include virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, and so on.

[0259] In both of the above implementation methods, the terminal reports its terminal capability identifier to the first RAN via a registration request. After receiving the registration request from the terminal, the first RAN selects a first network function and sends the registration request to the first network function, which can be an AMF (Authentication Management Function). It is understood that if the registration request sent by the terminal includes the terminal's terminal capability identifier, then the registration request received by the first network function from the first RAN will also include the terminal's terminal capability identifier. In some embodiments, if the registration request sent by the terminal includes not only the terminal capability identifier but also the terminal type, then the registration request received by the first network function from the first RAN will also include both the terminal's terminal capability identifier and the terminal type.

[0260] For example, referring to Figure 5, the process of a terminal reporting its capabilities is illustrated using the initial registration process of a terminal as an example.

[0261] 1. During the initial registration process, the terminal sends a registration request to the first RAN it accesses. In addition to carrying relevant registration parameters, the AN message also includes the terminal capability identifier and terminal type (optional).

[0262] Please refer to Figure 6, which is a schematic diagram of the relevant initial registration process. In step 1 shown in Figure 6, the UE (User Equipment), i.e. the terminal, sends a registration request to the first RAN to which the terminal is connected. The terminal sends the terminal capability identifier and terminal type (optional) in the registration request to the first RAN.

[0263] 2. After receiving the registration request sent by the terminal, the first RAN performs AMF selection, which is the same as step 2 in the relevant initial registration process shown in Figure 6.

[0264] 3. The first RAN sends the registration request to the AMF (i.e., the first network function mentioned above). In addition to carrying the relevant registration parameters, the N2 message also includes the terminal capability identifier and terminal type (optional).

[0265] Next, the subsequent registration process after step 3 is the same as steps 4 to 24 in the initial registration process of the relevant terminal shown in Figure 6, and will not be described again here.

[0266] It should be noted that the above embodiments involve the terminal reporting its terminal capability identifier to the first RAN it accesses (the terminal sends a registration request to the first RAN, the registration request carrying the terminal capability identifier and / or terminal type), and the first RAN obtains the terminal capability identifier based on the registration request. In some embodiments, the terminal may also directly report its terminal capability identifier to the first network function (such as AMF) it accesses (the terminal sends a registration request to the first network function, the registration request carrying the terminal capability identifier and / or terminal type), for example, through NAS (Non-access stratum) messages. In this way, the first network function can obtain the terminal capability identifier of the terminal accessing the first RAN based on the registration request, and then the first network function can synchronize the obtained terminal capability to the first RAN. In some embodiments, the terminal may also report its terminal capability identifier to both the first RAN it accesses and the first network function it accesses. The specific method of terminal capability reporting is not limited here.

[0267] The above text introduced two implementation methods: registration request carrying terminal capability identifier and registration request carrying terminal capability identifier and terminal type.

[0268] In a third possible implementation, the registration request carries the terminal type. After receiving the registration request from the terminal, the first RAN obtains the terminal capability identifier based on the terminal type. That is, if the registration request sent by the terminal to the first RAN does not carry the terminal capability identifier, but only carries the terminal type in addition to the relevant registration parameters, then the first RAN obtains the terminal capability identifier based on the terminal type.

[0269] The following describes, through several possible implementation methods, the process by which the first RAN obtains the terminal capability identifier based on the terminal type.

[0270] First, the capability mapping table is introduced. In some embodiments of this disclosure, the capability mapping table includes the mapping relationship between the terminal type and the terminal capability identifier. For example, taking the terminal capability identifier as shown in Figure 3, see Table 1, which is an exemplary capability mapping table:

[0271] Table 1

[0272] The terminal type field in the capability mapping table can store the identifier of the terminal type. For example, terminal type "1" in Table 1 represents one type of terminal, terminal type "2" in Table 1 represents another type of terminal, and so on. It can be understood that the terminal type field can also be stored in other formats. The terminal capability identifier field stores the field values ​​of each field in the terminal capability identifier. For example, the terminal capability identifier "11101" in Table 1 indicates that the terminal corresponding to terminal type "1" supports intelligent capabilities, sensing capabilities, and computing capabilities, and supports exposing its intelligent capabilities, sensing capabilities, and computing capabilities to the outside world.

[0273] In some embodiments of this disclosure, the capability mapping table can be stored in the RAN, such as the first capability mapping table stored in the first RAN in the above embodiments. It can also be stored in the core network (here referred to as the second capability mapping table for distinction). The second capability mapping table can be stored in the AMF (such as the first network function mentioned above, or other AMFs) or UDM (User Data Management). The capability mapping table can be pre-configured by the operator or collected and saved based on historical information.

[0274] The following section introduces several possible implementation methods for the first RAN to obtain the terminal capability identifier based on the terminal type.

[0275] 1) The capability mapping table is stored in the first RAN.

[0276] In this way, the first RAN can query the terminal capability identifier associated with the terminal type in the first capability mapping table based on the terminal type sent by the terminal.

[0277] In this embodiment, the capability mapping table can be stored in the first RAN. Here, the capability mapping table stored in the first RAN is referred to as the first capability mapping table for distinction.

[0278] In this way, after the first RAN receives the registration request sent by the terminal, if the registration request does not carry the terminal capability identifier of the terminal, but only carries the terminal type of the terminal in addition to the relevant registration parameters, then the first RAN can obtain the terminal capability identifier by querying the terminal capability identifier associated with the terminal type in the first capability mapping table according to the terminal type.

[0279] For example, since the registration request carries the terminal type, the first RAN may also carry the terminal capability identifier in the registration request and send it to the first network function, such as the AMF mentioned above.

[0280] For example, referring to Figure 7, the process of the first RAN querying the first capability mapping table to obtain the terminal's capabilities is illustrated using the initial registration process of the terminal as an example.

[0281] 1. During the initial registration process, the terminal sends a registration request to the first RAN it accesses. In addition to the relevant registration parameters, the AN message also carries the terminal type.

[0282] Referring to Figure 6, in step 1 shown in Figure 6, the terminal sends a registration request to the first RAN it accesses, and the terminal sends the terminal type in the registration request to the first RAN.

[0283] 2. After receiving the registration request sent by the terminal, the first RAN queries the terminal capability identifier associated with the terminal type in the first capability mapping table according to the terminal type. The first RAN also performs AMF selection.

[0284] 3. The first RAN sends the terminal capability identifier in the registration request to the AMF (i.e., the first network function mentioned above). That is, in addition to carrying the relevant registration parameters, the N2 message also includes the terminal capability identifier and terminal type.

[0285] In some embodiments, the first RAN may also only carry the terminal capability identifier in the registration request sent to the first network function, that is, the terminal type is the content carried in the registration request in some embodiments.

[0286] Next, the subsequent registration process after step 3 is the same as steps 4 to 24 in the initial registration process of the relevant terminal shown in Figure 6, and will not be described again here.

[0287] In one implementation, after the first network function receives a terminal registration request sent by the first RAN, if the registration request carries a terminal capability identifier and a terminal type, the first network function may also store the mapping relationship between the terminal type and the terminal capability identifier locally in a second capability mapping table and / or in a second capability mapping table of the second network function. The second network function includes at least a UDM. That is, the second capability mapping table may be stored locally in the first network function, or in other network functions (e.g., UDM), or both locally in the first network function and in the UDM. The storage location of the second capability mapping table is not limited here.

[0288] 2) The capability mapping table is stored in the first RAN and the core network.

[0289] In this embodiment, the capability mapping table can be stored in the first RAN or in the core network. Here, the capability mapping table stored in the first RAN is referred to as the first capability mapping table, and the capability mapping table stored in the core network is referred to as the second capability mapping table, for distinction.

[0290] After receiving a registration request from a terminal, if the registration request does not carry the terminal capability identifier of the terminal, but only carries the terminal type in addition to the relevant registration parameters, then the first RAN will look up the terminal capability identifier associated with the terminal type in the first capability mapping table according to the terminal type to obtain the terminal capability identifier.

[0291] To verify the accuracy of the terminal capability identifier queried by the first RAN, in some embodiments of this disclosure, the terminal type is already carried in the registration request sent by the terminal to the first RAN. The first RAN may also carry the terminal capability identifier queried by it in the registration request to the first network function, such as the AMF mentioned above.

[0292] After receiving a registration request from the first RAN, the first network function queries the second capability mapping table for the terminal capability identifier associated with the terminal type according to the terminal type carried in the registration request, and obtains the query result. As mentioned above, the second capability mapping table is stored in the first network function and / or the second network function, and the second network function includes at least UDM.

[0293] Then, based on the query results and the terminal capability identifier carried in the registration request sent by the first RAN, the first network function generates a terminal capability verification notification and sends the terminal capability verification notification to the first RAN.

[0294] As mentioned above, the query result is obtained by the first network function from the second capability mapping table based on the terminal type carried in the registration request sent by the first RAN. It is understood that the query result may be the same as the terminal capability identifier carried in the registration request sent by the first RAN, or it may be different from the terminal capability identifier carried in the registration request sent by the first RAN. The terminal capability verification notification is used to indicate whether the query result is the same as the terminal capability identifier carried in the registration request sent by the first RAN.

[0295] The first RAN receives a terminal capability verification notification sent by the first network function. As mentioned above, the terminal capability verification notification is generated by the first network function after querying the second capability mapping table according to the terminal type and verifying the terminal capability identifier according to the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[0296] If the terminal capability verification notification indicates that the query result obtained by the first network function from querying the second capability mapping table according to the terminal type is different from the terminal capability identifier carried in the registration request sent by the first RAN (i.e., the first RAN queries the first capability mapping table according to the terminal type carried in the registration request sent by the terminal), it indicates that the mapping relationship corresponding to the terminal type stored in the first capability mapping table and / or the second capability mapping table is incorrect, and the first RAN deletes the table entries corresponding to the terminal type in the first capability mapping table and the second capability mapping table.

[0297] In some embodiments, if the first network function determines that the query result is different from the terminal capability identifier carried in the registration request sent by the first RAN, the first network function may also delete the entry content corresponding to the terminal type in the second capability mapping table.

[0298] In some embodiments, the terminal capability verification notification may be sent separately; in some embodiments, the terminal capability verification notification may also be carried in the subsequent context establishment response, that is, the first network function sends the terminal capability verification notification to the first RAN along with the context establishment response, so as to realize the process of the first network function sending the terminal capability verification notification to the first RAN. In this way, the first RAN receives the context establishment response sent by the first network function, which carries the terminal capability verification notification, so as to realize the process of the first RAN receiving the terminal capability verification notification sent by the first network function. Here, the method by which the first network function sends the terminal capability verification notification to the first RAN is not limited.

[0299] For example, referring to Figure 8, taking the initial registration process of a terminal as an example, the process of the first RAN obtaining the terminal's capabilities is illustrated by storing the capability mapping table in the first RAN and the core network (here, it is stored in the first network function, such as AMF).

[0300] 1. During the initial registration process, the terminal sends a registration request to the first RAN it accesses. In addition to the relevant registration parameters, the AN message also carries the terminal type.

[0301] Referring to Figure 6, in step 1 shown in Figure 6, the terminal sends a registration request to the first RAN it accesses, and the terminal sends the terminal type in the registration request to the first RAN.

[0302] 2. After receiving the registration request sent by the terminal, the first RAN queries the terminal capability identifier associated with the terminal type in the first capability mapping table according to the terminal type, and the first RAN also performs AMF selection.

[0303] 3. The first RAN sends the terminal capability identifier in the registration request to the AMF (i.e., the first network function mentioned above). That is, in addition to carrying the relevant registration parameters, the N2 message also includes the terminal capability identifier and terminal type.

[0304] 4. After receiving the registration request, the AMF queries the second capability mapping table based on the terminal type carried in the registration request, obtains the query result, and verifies the terminal capability based on the query result.

[0305] 5. Based on the above query results and the terminal capability identifier carried in the registration request sent by the first RAN, the AMF generates a terminal capability verification notification and sends the terminal capability verification notification to the first RAN.

[0306] The query result may be the same as the terminal capability identifier carried in the registration request sent by the first RAN, or it may be different from the terminal capability identifier carried in the registration request sent by the first RAN. The terminal capability verification notification is used to indicate whether the query result is the same as the terminal capability identifier carried in the registration request sent by the first RAN.

[0307] If the AMF verifies that the query result is the same as the terminal capability identifier carried in the registration request sent by the first RAN, the AMF sends a terminal capability verification notification to the first RAN confirming the verification. If the query result is different from the terminal capability identifier carried in the registration request sent by the first RAN, the AMF deletes the entry corresponding to the terminal type in the second capability mapping table locally or in the UDM, and sends a terminal capability verification notification that the verification failed to the first RAN, notifying the first RAN to delete the entry corresponding to the terminal type in the first capability mapping table.

[0308] The subsequent registration process is the same as steps 4 to 24 in the initial registration process of the relevant terminal shown in Figure 6, and will not be repeated here. It should be noted that the aforementioned terminal capability verification notification can be sent separately or included in the subsequent context establishment response.

[0309] 3) The capability mapping table is stored in the core network.

[0310] After receiving the registration request sent by the terminal, the first RAN does not carry the terminal capability identifier of the terminal. In addition to carrying the relevant registration parameters, the registration request only carries the terminal type of the terminal. When the first RAN obtains the terminal capability identifier of the terminal based on the terminal type, since the first RAN does not store the first capability mapping table, the first RAN sends the registration request to the first network function.

[0311] After receiving the terminal registration request sent by the first RAN, the first network function carries the terminal type of the terminal. The first network function then queries the second capability mapping table for the terminal capability identifier associated with the terminal type based on the terminal type. As mentioned above, the second capability mapping table can be stored in the first network function (such as AMF) or UDM.

[0312] Then, the first network function will send the terminal capability identifier obtained from the second capability mapping table according to the terminal type to the first RAN, and the first RAN will receive the terminal capability identifier returned by the first network function.

[0313] For example, the first network function may send a capability notification to the first RAN, carrying the terminal capability identifier obtained by the first network function from the second capability mapping table according to the terminal type in the capability notification. In some embodiments, the first network function may also carry the terminal type in the capability notification and send it to the first RAN.

[0314] It should be noted that the aforementioned capability notification may be sent by the first network function to the first RAN alone, or the first network function may send the terminal capability identifier to the first RAN by including it in the context establishment response.

[0315] The first RAN then receives a context establishment response sent by the first network function. This context establishment response carries the terminal capability identifier and the terminal type, thereby enabling the first RAN to receive the terminal capability identifier returned by the first network function.

[0316] For example, referring to Figure 9, taking the initial registration process of a terminal as an example, the process of the first RAN obtaining the terminal's capabilities is illustrated by storing the capability mapping table in the core network (here, it is stored in the first network function, such as AMF).

[0317] 1. During the initial registration process, the terminal sends a registration request to the first RAN it accesses. In addition to the relevant registration parameters, the AN message also carries the terminal type.

[0318] Referring to Figure 6, in step 1 shown in Figure 6, the terminal sends a registration request to the first RAN it accesses, and the terminal sends the terminal type in the registration request to the first RAN.

[0319] 2. After receiving the registration request sent by the terminal, the first RAN performs AMF selection, which is the same as step 2 in the relevant initial registration process shown in Figure 6.

[0320] 3. The first RAN sends the registration request to the AMF (i.e., the first network function mentioned above). In addition to carrying the relevant registration parameters, the N2 message also includes the terminal type of the terminal.

[0321] 4. After receiving the registration request, AMF queries the second capability mapping table based on the terminal type carried in the registration request to obtain the terminal capability identifier associated with the terminal type.

[0322] 5. The AMF sends the terminal capability identifier and terminal type (optional) to the first RAN via capability notification.

[0323] The subsequent registration process is the same as steps 4 to 24 in the initial registration process of the relevant terminal shown in Figure 6, and will not be repeated here. It should be noted that the above-mentioned capability notification can be sent to the first RAN by the first network function alone, or the first network function can send the terminal capability identifier to the first RAN by including it in the context establishment response.

[0324] In this way, after the first RAN receives the registration request sent by the terminal, if the registration request does not carry the terminal capability identifier of the terminal, but only carries the terminal type of the terminal in addition to the relevant registration parameters, then the first RAN can obtain the terminal capability identifier according to the terminal type through any of the above implementation methods. The implementation methods are flexible and diverse, and can be flexibly selected in actual application.

[0325] The above embodiment exemplifies how the first RAN obtains the terminal capability identifier of at least one terminal accessing the first RAN by taking the terminal type and / or terminal capability identifier carried in the registration request sent by the terminal to the first RAN as an example.

[0326] However, it is understandable that the following situations may occur, causing the first RAN to fail to successfully obtain the terminal capability identifier of the terminal through the above implementation method, for example:

[0327] 1) In order to complete network access as soon as possible, the terminal may only report its basic information during the initial registration. The registration request sent by the terminal to the first RAN does not carry the terminal capability identifier and the terminal type. At this time, the first RAN cannot parse the terminal capability identifier from the registration request, nor can it obtain the terminal capability identifier based on the terminal type.

[0328] 2) In the embodiment shown in Figure 7 above (the capability mapping table is stored in the first RAN), the registration request carries the terminal type. However, the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type. At this time, the first RAN cannot successfully obtain the terminal capability identifier.

[0329] 3) In the embodiment shown in Figure 9 above (the capability mapping table is stored in the core network), the registration request carries the terminal type. However, after the first RAN sends the terminal type to the first network function, the first network function does not find the terminal capability identifier in the second capability mapping table. Thus, the first RAN does not receive the terminal capability identifier returned by the first network function, and the first RAN cannot successfully obtain the terminal capability identifier.

[0330] 4) In the embodiment shown in Figure 8 above (the capability mapping table is stored in the first RAN and the core network), the first RAN deletes the entry content corresponding to the terminal type in the first capability mapping table according to the terminal capability verification notification sent by the first network function. The first network function also deletes the entry content corresponding to the terminal type in the second capability mapping table. At this time, the first RAN is also unable to successfully obtain the terminal capability identifier.

[0331] Therefore, in order to successfully obtain the terminal capability identifier of at least one terminal accessing the first RAN, the first RAN can send a terminal capability request to the terminal if preset conditions are met. That is, it obtains the terminal capability identifier of the terminal through the terminal capability request process, and then performs specific service processing.

[0332] The preset conditions may include at least one of the four situations mentioned above, namely at least one of the following:

[0333] The registration request sent by the terminal to the first RAN does not carry the terminal capability identifier or the terminal type; the registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table based on the terminal type; the registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function; the first RAN deletes the entry in the first capability mapping table corresponding to the terminal type according to the instruction of the terminal capability verification notification sent by the first network function.

[0334] The terminal receives a terminal capability request sent by the first RAN, as described above. The terminal capability request is sent by the first RAN under preset conditions. The terminal responds to the terminal capability request by sending a terminal capability response to the first RAN. The terminal capability response carries a terminal capability identifier. In this way, the terminal reports its terminal capability identifier to the first RAN it accesses.

[0335] The first RAN receives a terminal capability response sent by the terminal, which carries a terminal capability identifier.

[0336] It should be noted that when the registration request sent by the terminal to the first RAN carries the terminal type, the terminal capability request sent by the first RAN to the terminal can also carry the terminal type. In this way, the terminal capability response sent by the terminal to the first RAN can also carry the terminal type.

[0337] After receiving the terminal capability response, the first RAN can store the mapping relationship between the terminal type and the terminal capability identifier in the first capability mapping table.

[0338] After receiving the terminal capability response sent by the terminal, the first RAN can also send the terminal type and terminal capability identifier to the first network function. From the perspective of the first network function, the first network function receives the terminal capability identifier sent by the first RAN under the above-mentioned preset conditions. The first network function can then obtain the terminal capability identifier of at least one terminal accessing the first RAN. This terminal capability identifier is sent by the terminal to the first RAN in response to the terminal capability request sent by the first RAN.

[0339] For example, the first RAN sends the terminal type and terminal capability identifier to the first network function via a terminal capability synchronization message.

[0340] In some embodiments, the first network function may store the mapping relationship between terminal type and terminal capability identifier in a second capability mapping table, which may be stored in the first network function (such as AMF) or UDM.

[0341] For example, referring to Figure 10, the process of a terminal initiating a terminal capability request to the first RAN to obtain terminal capabilities is illustrated using the initial registration process of a terminal as an example.

[0342] 1. Under the above-mentioned preset conditions, the first RAN sends a terminal capability request to the terminal. If the terminal type is carried in the registration request when the terminal is registered, the terminal capability request can also carry the terminal type.

[0343] 2. The terminal sends a terminal capability response to the first RAN. The terminal capability response carries the terminal capability identifier. If the terminal capability request carries the terminal type, the terminal capability response can also carry the terminal type.

[0344] 3. After receiving the terminal capability response, the first RAN stores the mapping relationship between the terminal type and the terminal capability identifier in the first capability mapping table.

[0345] 4. The first RAN synchronizes terminal capabilities with the AMF (first network function). The first RAN sends the terminal type and terminal capability identifier to the first network function through the terminal capability synchronization message.

[0346] 5. The first network function stores the mapping relationship between terminal type and terminal capability identifier in the second capability mapping table, which can be stored in the first network function (such as AMF) or UDM.

[0347] The embodiment shown in Figure 10 is an example of a terminal capability request initiated by the first RAN. In other possible implementations, the terminal capability request can also be initiated by the first network function to obtain terminal capabilities.

[0348] In this way, before the first RAN sends a terminal capability request to the terminal, the first network function sends a terminal capability request to the first RAN, the first RAN receives the terminal capability request sent by the first network function, and then the first RAN forwards the terminal capability request to the terminal.

[0349] For example, referring to Figure 11, the process of a terminal initiating a terminal capability request to obtain terminal capabilities is illustrated using the initial registration process of a terminal as an example.

[0350] 1. Under the above-mentioned preset conditions, the AMF (first network function) sends a terminal capability request to the first RAN. If the terminal type is carried in the registration request when the terminal is registered, the terminal capability request can also carry the terminal type.

[0351] 2. The first RAN sends a terminal capability request to the terminal, which may include the terminal type (if applicable).

[0352] 3. The terminal sends a terminal capability response to the first RAN. The terminal capability response carries the terminal capability identifier. If the terminal capability request carries the terminal type, the terminal capability response can also carry the terminal type.

[0353] 4. After receiving the terminal capability response, the first RAN stores the mapping relationship between the terminal type and the terminal capability identifier in the first capability mapping table.

[0354] 5. The first RAN responds to the AMF (first network function) terminal capability response, which carries the terminal capability identifier and terminal type.

[0355] 6. After receiving the terminal capability identifier and terminal type sent by the first RAN, the first network function stores the mapping relationship between the terminal type and the terminal capability identifier in the second capability mapping table. The second capability mapping table can be stored in the first network function (such as AMF) or UDM.

[0356] In the above embodiments, after the first RAN receives the registration request sent by the terminal, if the registration request carries the terminal capability identifier and / or the terminal type of the terminal, the first RAN can directly obtain the terminal capability identifier of the terminal or obtain the terminal capability identifier according to the terminal type. If the terminal capability identifier cannot be obtained successfully or is not obtained in the above way, the terminal capability identifier can also be obtained by sending a terminal capability request to the terminal, thereby improving the reliability of terminal capability acquisition.

[0357] Based on the acquired terminal capability identifier, the first RAN can determine whether the terminal supports externally exposed intelligent capabilities, sensing capabilities, computing capabilities, and other target capabilities. If the terminal supports externally exposed target capabilities, it can provide collaborative services targeting those capabilities. For example, the terminal can utilize its aforementioned intelligent capabilities, sensing capabilities, computing capabilities, and other target capabilities to provide intelligent services, sensing services, computing services, etc., thereby fully utilizing the terminal's target capabilities, enhancing edge network capabilities through the terminal's capabilities, and thus reducing network deployment costs.

[0358] Once the network understands the capabilities of a terminal, it can collaborate with the terminal to provide services. Simultaneously, based on a terminal's service request, the network can select collaborating terminals to provide relevant services. For example, the following scenarios may exist:

[0359] (1) When the terminal itself does not support the target capability, the terminal’s services need to be processed by the network, and the service processing process is the same as the service processing flow of the relevant terminal.

[0360] (2) If the terminal itself supports the target capabilities, such as intelligent capabilities, then the terminal can handle intelligent services.

[0361] In related technologies, most artificial intelligence models run on servers. However, because terminals are closer to the data source, running AI models on terminals allows for timely information processing while ensuring that data does not leave the terminal, greatly protecting user privacy. When the terminal's battery power, energy consumption, computing power, and data availability meet the requirements, business processing can be prioritized on the terminal itself.

[0362] (3) The terminal itself supports the target capabilities, but the business is processed entirely on the terminal, which places high demands on the terminal's computing power, algorithms, battery life, etc. The terminal cannot fully bear the load, so it can work in collaboration with the network.

[0363] For example, the terminal may collaborate with other compliant terminals to provide services, and / or the terminal may collaborate with a network to provide services.

[0364] It should be noted that in some embodiments of this disclosure, the business data processed collaboratively is non-privacy data, and there is a default protocol for large-scale data transmission between terminals and between terminals and the network.

[0365] The following illustrations illustrate the process of collaborative services.

[0366] In some embodiments, based on the embodiment shown in FIG2, and referring to FIG12, the collaborative service method of some embodiments of this disclosure further includes steps 1201 and 1202 shown in FIG12:

[0367] Step 1201: The first RAN receives a service request sent by the target terminal. The service request carries the service type and service requirements.

[0368] The target terminal itself supports the target capabilities, but processing the service entirely on the target terminal places high demands on its computing power, algorithms, and battery life, which the target terminal cannot fully handle. Therefore, it can provide collaborative services with other terminals or the network. For example, when the processing latency requirements of the service are high, or when other terminals need to jointly perceive global information, inter-terminal collaborative services can be implemented.

[0369] When a target terminal has a need for collaborative services, it can send a service request. This service request carries the service type and service requirements. The service type can be, for example, intelligent services, computing services, or sensing services. The service requirements can be, for example, low-latency services, etc.

[0370] In some embodiments of this disclosure, the target terminal may send a service request to the first RAN, or the target terminal may send a service request to the first network function (such as AMF). Here, we will first take the example of the target terminal sending a service request to the first RAN.

[0371] In this way, the first RAN receives the service request sent by the target terminal.

[0372] Step 1202: The first RAN determines a cooperating terminal that matches the service type and service requirements based on the service request, and / or determines a network node that matches the service type and service requirements based on the service request, wherein the cooperating terminal and the network node are respectively used to provide cooperative services.

[0373] First, taking the collaborative service between the target terminal and the collaborating terminal as an example, we will introduce how the first RAN determines the collaborating terminal that matches the service type and service requirements based on the service request.

[0374] For example, both the target terminal and the cooperating terminal are terminals that are connected to the first RAN. The first RAN has obtained the terminal capability identifiers of each terminal connected to the first RAN through the implementation of the above embodiments. That is, the first RAN has determined the capabilities of each terminal, and then the first RAN selects a cooperating terminal for the target terminal.

[0375] After receiving the service request sent by the target terminal, the first RAN determines the candidate terminals that support the service type based on the terminal capability identifier of each terminal. Then, the first RAN selects the candidate terminals that meet the service requirements (such as latency requirements) as the cooperating terminals.

[0376] Next, the first RAN sends a service request to the cooperating terminal. The cooperating terminal can accept or reject the request. If it rejects the request, the first RAN needs to make a new selection. If it accepts the request, the cooperating terminal returns a cooperation confirmation message to the first RAN. This cooperation confirmation message can carry information about the cooperating terminal's own capabilities that can be shared externally, such as the availability of computing resources, algorithms, and data.

[0377] If the first RAN receives a collaboration confirmation message from the collaborating terminal, the first RAN determines that the collaborating terminal accepts the collaboration service. The first RAN then sends the terminal service provider information of the collaborating terminal, such as the identifier of the collaborating terminal, to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0378] If the first RAN receives a rejection message from a cooperating terminal, the first RAN will re-identify other cooperating terminals that match the service type and service requirements, until a cooperating terminal that can provide cooperating services is found or until the exit conditions are met, and then exit the current cooperating service process.

[0379] Please refer to Figure 13 below for an explanation of the process by which the first RAN selects a cooperating terminal for the target terminal when the target terminal and the cooperating terminal are connected to the same RAN (first RAN).

[0380] 1. The target terminal initiates a service request to the first RAN. The service request carries the service type (such as intelligent service, computing service or sensing service, etc.) and the service requirements (such as low latency service, etc.).

[0381] 2. The first RAN determines the collaborative terminal that matches the service type and service requirements based on the service request, that is, the first RAN selects a collaborative terminal that meets the service capabilities.

[0382] 3. The first RAN sends a service request to the selected cooperating terminal.

[0383] 4. The cooperating terminal can accept or reject the request independently. If it accepts the request, the cooperating terminal will return a cooperation confirmation message to the first RAN. This cooperation confirmation message can carry information about the cooperating terminal's own capabilities that can be shared externally, such as the availability of computing resources, algorithms, and data.

[0384] If the cooperating terminal refuses, the first RAN needs to select another cooperating terminal.

[0385] 5. The first RAN returns the terminal servicer information of the cooperating terminal to the target terminal.

[0386] The subsequent process involves establishing an end-to-end session between the target terminal and the collaborating terminal. This process is the same as the related end-to-end session establishment process, as shown in Figure 14, and will not be repeated here. After the target terminal and the collaborating terminal establish an end-to-end session, the end-to-end service processing flow is then carried out.

[0387] In this way, the first RAN determines the cooperating terminal that matches the service type and service requirements based on the service request.

[0388] In some cases, processing services entirely on the target terminal places high demands on the target terminal's computing power, algorithms, and battery life, which the target terminal cannot fully handle. In such cases, the target terminal can collaborate with the network to provide services. The first RAN determines the network node that matches the service type and requirements based on the service request. That is, it determines the network node that supports the service type, whose service capabilities match the service requirements, and that accepts collaborative services. This network node then collaborates with the target terminal to provide services.

[0389] In other cases, the target terminal can also provide collaborative services with the cooperating terminal and the network.

[0390] For example, the target terminal's service processing requires data support from the cooperating terminal, such as global environment awareness. This service can be perceived collaboratively by the target terminal and at least one cooperating terminal, and the network can process the service. In this scenario, the first RAN determines the cooperating terminal and network node to provide the collaborative service based on the service request. That is, the cooperating terminal and network node support the above-mentioned service type, and the service capabilities of the cooperating terminal and network node match the service requirements. The cooperating terminal and network node accept the collaborative service.

[0391] In this way, during the collaborative service process between the target terminal and the collaborating terminal, the target terminal sends its first service processing result to the network node, and the collaborating terminal sends its second service processing result to the network node. The service identifiers carried by the first and second service processing results are the same. Thus, the network node determines that the first and second service processing results are the processing results of the same service based on the service identifiers. The network node then jointly performs service processing based on the first service processing result and the second service processing result sent by the collaborating terminal. For example, if the target terminal and the collaborating terminal are co-perceiving, the network will jointly perform service processing based on the content of the co-perceived information.

[0392] For example, in some scenarios, before the target terminal sends a service request to the first RAN or the first network function, the target terminal can also perform service segmentation processing on the service to be processed to obtain collaborative sub-services. That is, the target terminal can segment the service to be processed to obtain latency-sensitive services and other services. Then, the terminal generates a service request based on the service type and service requirements of the collaborative sub-services. In this way, the first RAN determines the collaborative terminal and network nodes based on the service request. The collaborative terminal is deployed close to the target terminal and can handle some latency-sensitive services, while other services can be handled by the network nodes, thereby realizing collaborative services between the target terminal, the collaborative terminal, and the network.

[0393] The above embodiments illustrate the example of a target terminal sending a service request to a first RAN, and the first RAN selecting a cooperating terminal and / or network node for the target terminal based on the service request. In some embodiments, as described above, the target terminal may also send a service request to a first network function (such as an AMF), whereby the first network function performs service coordination. Both the target terminal and the cooperating terminal are terminals accessed by the first RAN. The first RAN is accessed by the first network function, which has determined the capabilities of each terminal, and thus selects a cooperating terminal for the target terminal.

[0394] The target terminal sends a service request (carrying the service type and service requirements) to the first network function (such as AMF). After receiving the service request sent by the target terminal, the first network function determines a cooperating terminal that matches the service type and service requirements based on the service request, and / or determines a network node that matches the service type and service requirements based on the service request. The cooperating terminal and the network node are used to provide cooperative services.

[0395] The method by which the first network function selects a cooperating terminal and / or network node is similar to the method by which the first RAN selects a cooperating terminal and / or network node. Taking the selection of a cooperating terminal by the first network function as an example, after receiving a service request sent by the target terminal, the first network function determines candidate terminals that support the corresponding service type based on the terminal capability identifier of each terminal. Then, the first network function selects the candidate terminal that meets the service requirements (e.g., latency requirements) from among the candidate terminals as the cooperating terminal.

[0396] Next, the first network function sends a service request to the collaborating terminal. The collaborating terminal can accept or reject the request. If it rejects the request, the first network function needs to select another collaborating terminal. If it accepts the request, the collaborating terminal returns a collaborating confirmation message to the first network function. This collaborating confirmation message can carry information about the collaborating terminal's own capabilities that can be shared externally, such as the availability of computing resources, algorithms, and data.

[0397] If the first network function receives a collaboration confirmation message from the collaboration terminal, the first network function determines that the collaboration terminal accepts the collaboration service. The first network function then sends the terminal service provider information of the collaboration terminal to the target terminal. The terminal service provider information is used by the target terminal and the collaboration terminal to establish a business session.

[0398] If the first network function receives a rejection message from a collaborating terminal, it will re-identify other collaborating terminals that match the service type and service requirements until a collaborating terminal that can provide collaborative services is found or until the exit conditions are met, at which point it will exit the current collaborative service process.

[0399] For example, referring to Figure 15, the process of the core network selecting a collaborative terminal for the target terminal when the target terminal and the collaborative terminal access the same distributed node is described in conjunction with the illustration.

[0400] 1. The target terminal initiates a service request to the AMF. The service request carries the service type (such as intelligent service, computing service or sensing service, etc.) and the service requirements (such as low latency service, etc.).

[0401] 2. The AMF determines the collaborative terminal that matches the business type and business requirements based on the business request, that is, the AMF selects a collaborative terminal that meets the business capabilities.

[0402] 3. AMF sends a service request to the selected cooperating terminal.

[0403] 4. The collaborative terminal can accept or reject the request independently. If it accepts the request, the collaborative terminal will return a collaborative confirmation message to the AMF. This collaborative confirmation message can carry information about the collaborative terminal's own capabilities that can be shared externally, such as the availability of computing resources, algorithms, and data.

[0404] 5. AMF returns the terminal service provider information of the collaborating terminal to the target terminal.

[0405] If the collaborating terminal refuses, the AMF needs to select another collaborating terminal.

[0406] Thus, regardless of which method the target terminal uses (sending a service request to the first RAN or the first network function), after receiving the terminal servicer information of the cooperating terminal sent by the first RAN or the first network function, the target terminal establishes a service session with the cooperating terminal based on the terminal servicer information. This initiates the end-to-end session establishment process from the target terminal to the cooperating terminal, which is similar to the related end-to-end session establishment process, as shown in Figure 14, and will not be elaborated further here. After the target terminal and the cooperating terminal establish an end-to-end session, the end-to-end service processing flow begins.

[0407] In the above embodiments, the process of providing collaborative services between the target terminal and the collaborating terminal is described assuming that both the target terminal and the collaborating terminal are connected to the first RAN. In some embodiments, the target terminal and the collaborating terminal may also be connected to different networks.

[0408] In one possible implementation, the target terminal is a terminal accessing the first RAN, and the cooperating terminal is a terminal accessing the second RAN. Both the first RAN and the second RAN are accessed by the first network node (accessing the first network function in the first network node). In this case, the core network can select the cooperating terminal for the target terminal.

[0409] Based on the embodiment shown in Figure 12, after the first RAN receives the service request sent by the target terminal, the first RAN can send the service request to the first network node (exemplarily, the first RAN sends the service request to the first network function in the first network node). The service request is used by the first network node to determine the cooperating terminal according to the service request, so as to realize the process of the first RAN determining the cooperating terminal that matches the service type and service requirements according to the service request.

[0410] The first network node receives the service request sent by the first RAN (or the target terminal can directly send the service request to the first network node). The first network node then determines the cooperating terminal that matches the service type and service requirements based on the service request. The selection process is similar to that in the above embodiments and will not be described again here.

[0411] After the first network node selects a cooperating terminal, it sends the terminal service provider information of the cooperating terminal to the first RAN. The first RAN receives the terminal service provider information of the cooperating terminal sent by the first network node and sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal and the cooperating terminal to establish a service session. After the target terminal and the cooperating terminal establish an end-to-end session, they perform the end-to-end service processing flow.

[0412] In another possible implementation, the target terminal is a terminal connected to the first RAN, and the cooperating terminal is a terminal connected to the second RAN. The first RAN and the second RAN are connected to different network nodes. In this case, the neighboring distributed nodes / central nodes can discover the cooperating terminals that meet the requirements, thereby selecting a cooperating terminal for the target terminal.

[0413] In this scenario, after the first RAN sends the service request to the first network node (or the target terminal can also directly send the service request to the first network node), the service request is also used by the first network node to send the service request to the second network node or the central network node if no matching cooperative terminal is found based on the service request. In other words, during the process of determining a cooperative terminal that matches the service type and requirements based on the service request, if no matching cooperative terminal is found based on the service request, the first network node sends the service request to the second network node or the central network node, so that the second network node or the central network node can determine the cooperative terminal.

[0414] After receiving a service request from the first network node, the second network node or the central network node matches a suitable collaborative terminal according to the service request and sends the terminal service provider information of the collaborative terminal to the first network node.

[0415] After receiving the terminal servicer information of the collaborative terminal from the second network node or the central network node, the first network node sends the terminal servicer information to the target terminal. The terminal servicer information is used by the target terminal to establish a business session with the collaborative terminal.

[0416] In some embodiments, after the first network node receives the terminal service provider information sent by the central network node, that is, when the terminal service provider information is sent by the central network node, before the first network node sends the terminal service provider information to the target terminal, the first network node also sends a collaborative service request to the second network node.

[0417] If the second network node confirms the collaboration, it will return a confirmation collaboration response. If the first network node receives the confirmation collaboration response sent by the second network node, the first network node will then send the terminal service provider information to the target terminal.

[0418] It should be noted that the aforementioned first network node can directly send terminal service provider information to the target terminal, or the first network node can send terminal service provider information to the target terminal through the first RAN. In this way, after the first RAN receives the terminal service provider information of the cooperating terminal sent by the first network node (it can be understood that the terminal service provider information is sent by the first network node after confirming the cooperating service by the second network node), the first RAN sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal and the cooperating terminal to establish a service session.

[0419] For example, referring to Figure 16, the process of neighboring distributed nodes / central nodes discovering a suitable cooperative terminal when the target terminal and the cooperating terminal are connected to different RANs and the two RANs are connected to different distributed nodes is described in conjunction with the illustration.

[0420] 1. The target terminal initiates a service request to the first network node (distributed node 1). The service request carries the service type and service requirements. The service type is such as intelligent service, computing service or sensing service, etc., and the service requirements are such as low latency service, etc.

[0421] 2. The first network node attempts to select a cooperating terminal within the range of terminals accessed by this node, but no suitable cooperating terminal is found.

[0422] 3. The first network node sends a service request to the second network node (neighbor distributed node 2) based on the maintained neighbor node information. The second network node returns a response carrying the terminal service provider information.

[0423] 4. The first network node returns terminal service provider information to the target terminal.

[0424] or,

[0425] 3. The first network node sends a service request to the central network node, and the central network node returns a response carrying the terminal service provider information.

[0426] 4. The first network node sends a collaborative service request to the second network node. If the second network node confirms the collaboration, it will return a confirmation collaboration response.

[0427] 5. The first network node returns the terminal service provider information to the target terminal.

[0428] If the second network node refuses to cooperate in step 4, the central network node needs to select a new cooperating terminal.

[0429] The collaborative service method provided in some embodiments of this disclosure enhances the network capabilities at the edge by leveraging the capabilities of the terminal, fully utilizes the target capabilities of the terminal, uses the terminal as an edge node of the network for collaborative service processing, improves the network's operating efficiency, realizes the collaboration of multilateral capability resources between terminals and / or the network, and reduces network deployment costs.

[0430] In some embodiments, as shown in FIG17, a collaborative service method is provided, which is illustrated by taking the application of the method to the first network function in FIG1 as an example. The method includes the following steps:

[0431] Step 1701: The first network function obtains the terminal capability identifier of at least one terminal accessing the first RAN. The first RAN is the RAN accessing the first network function. The terminal capability identifier includes a capability field and a coordination field. The capability field is used to indicate whether the terminal supports the target capability, and the coordination field is used to indicate whether the terminal supports the externally exposed target capability. If the terminal supports the externally exposed target capability, the terminal can provide coordination services for the target capability.

[0432] In some embodiments, the capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field;

[0433] Among them, the intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0434] In some embodiments, intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities;

[0435] The sensing capabilities include at least one of the following: signal sensing capability, temperature sensing capability, humidity sensing capability, image sensing capability, position sensing capability, and speed sensing capability.

[0436] Computing power includes at least one of the following: computing processing power, computing task partitioning power, and computing aggregation power.

[0437] In some embodiments, the capability field also includes a custom field, which indicates whether the terminal supports capabilities other than intelligence, perception, and computing capabilities.

[0438] In some embodiments, step 1701 includes:

[0439] The first network function receives a registration request from the first RAN or the terminal, the registration request carrying at least one of the following:

[0440] Terminal capability identifier;

[0441] The terminal type is used to obtain the terminal capability identifier.

[0442] In some embodiments, the registration request carries a terminal capability identifier and a terminal type, and the method further includes:

[0443] The first network function stores the mapping relationship between terminal type and terminal capability identifier locally in the second capability mapping table and / or the second capability mapping table in the second network function, the second network function including at least UDM.

[0444] In some embodiments, the registration request carries the terminal type of the terminal, and the method further includes:

[0445] The first network function queries the second capability mapping table for the terminal capability identifier associated with the terminal type, based on the terminal type.

[0446] In some embodiments, the method further includes:

[0447] The first network function sends the terminal capability identifier to the first RAN in the context setup response.

[0448] In some embodiments, the registration request also carries a terminal capability identifier, and the method further includes:

[0449] The first network function generates a terminal capability verification notification based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type.

[0450] The first network function sends a terminal capability verification notification to the first RAN.

[0451] In some embodiments, the method further includes:

[0452] If the query result is different from the terminal capability identifier, the first network function will delete the entry in the second capability mapping table that corresponds to the terminal type.

[0453] In some embodiments, sending a terminal capability verification notification to a first RAN includes:

[0454] The first network function sends the terminal capability verification notification along with the context establishment response to the first RAN.

[0455] In some embodiments, step 1701 includes:

[0456] Under the condition that the first network function meets the preset conditions, it receives the terminal capability identifier sent by the first RAN. The terminal capability identifier is sent by the terminal to the first RAN in response to the terminal capability request sent by the first RAN.

[0457] In some embodiments, before receiving the terminal capability identifier sent by the first RAN, the method further includes:

[0458] The first network function sends a terminal capability request to the first RAN;

[0459] Receive the terminal capability identifier sent by the first RAN, including:

[0460] The first network function receives the terminal capability response from the first RAN, which carries the terminal capability identifier.

[0461] In some embodiments, the preset conditions include at least one of the following:

[0462] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0463] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table based on the terminal type;

[0464] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0465] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0466] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0467] In some embodiments, the method further includes:

[0468] The first network function stores the mapping relationship between terminal type and terminal capability identifier in the second capability mapping table.

[0469] In some embodiments, the method further includes:

[0470] The first network function receives service requests sent by the target terminal. The service requests carry the service type and service requirements.

[0471] The first network function determines, based on the service request, a collaborative terminal that matches the service type and service requirements, and / or determines, based on the service request, a network node that matches the service type and service requirements, wherein the collaborative terminal and the network node are respectively used to provide collaborative services.

[0472] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN are accessed by the same network node.

[0473] In some embodiments, the method further includes:

[0474] The first network function sends service requests to the collaborating terminal;

[0475] If a collaboration confirmation message is received from the collaborating terminal, the first network function sends the terminal service provider information of the collaborating terminal to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaborating terminal.

[0476] In some embodiments, the method further includes:

[0477] If a rejection message is received from a collaborating terminal, the first network function will then re-identify other collaborating terminals that match the service type and service requirements.

[0478] In some embodiments, determining a collaborative terminal that matches the service type and service requirements based on a service request includes:

[0479] If no matching terminal is found based on the service request, the first network function will send the service request to the second network node or the central network node, so that the second network node or the central network node can determine the matching terminal. The matching terminal is the terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0480] In some embodiments, the method further includes:

[0481] The first network function receives terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[0482] The first network function sends terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaborating terminal.

[0483] In some embodiments, when the terminal service provider information is sent by the central network node, the method further includes the following before sending the terminal service provider information to the target terminal:

[0484] The first network function sends a collaborative service request to the second network node;

[0485] Send terminal service provider information to the target terminal, including:

[0486] If a confirmation and coordination response is received from the second network node, the first network function sends terminal servicer information to the target terminal.

[0487] In some embodiments, the first network function is AMF.

[0488] For the implementation methods and beneficial effects of the cooperative service method for the first network function, please refer to the relevant descriptions in the embodiments of the cooperative service method for the first RAN above, which will not be repeated here.

[0489] In some embodiments, as shown in FIG18, a collaborative service method is provided, which will be described using the application of the method to the terminal in FIG1 as an example. The method includes the following steps:

[0490] Step 1801: The terminal reports its terminal capability identifier to the first RAN it accesses, and / or reports its terminal capability identifier to the first network function it accesses.

[0491] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports the externally exposed target capability. When the terminal supports the externally exposed target capability, the terminal can provide collaborative services for the target capability.

[0492] In some embodiments, the capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field;

[0493] Among them, the intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0494] In some embodiments, intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities.

[0495] The sensing capabilities include at least one of the following: signal sensing capability, temperature sensing capability, humidity sensing capability, image sensing capability, position sensing capability, and speed sensing capability.

[0496] Computing power includes at least one of the following: computing processing power, computing task partitioning power, and computing aggregation power.

[0497] In some embodiments, the capability field also includes a custom field, which indicates whether the terminal supports capabilities other than intelligence, perception, and computing capabilities.

[0498] In some embodiments, reporting the terminal's terminal capability identifier to the first RAN accessed by the terminal includes:

[0499] The terminal sends a registration request to the first RAN, the registration request carrying at least one of the following:

[0500] Terminal capability identifier;

[0501] The terminal type is used to obtain the terminal capability identifier.

[0502] In some embodiments, before reporting the terminal's terminal capability identifier to the first RAN accessed by the terminal, the method further includes:

[0503] The terminal receives a terminal capability request sent by the first RAN, which is sent by the first RAN under preset conditions.

[0504] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, including:

[0505] Send a terminal capability response to the first RAN, the terminal capability response carrying a terminal capability identifier.

[0506] In some embodiments, the preset conditions include at least one of the following:

[0507] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0508] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table based on the terminal type;

[0509] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0510] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0511] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0512] In some embodiments, the method further includes:

[0513] The terminal sends a service request to the first RAN or the first network function. The service request carries the service type and service requirements. The service request is used to determine the cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and network node are respectively used to provide cooperative services.

[0514] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[0515] The cooperating terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed from the same network node; or,

[0516] The cooperating terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0517] In some embodiments, the method further includes:

[0518] The terminal receives terminal servicer information of the cooperating terminal sent by the first RAN or the first network function;

[0519] The terminal establishes a business session with the collaborating terminal based on the terminal service provider information.

[0520] In some embodiments, the method further includes:

[0521] During the collaborative service process between the terminal and the collaborating terminal, the terminal sends the first service processing result to the network node;

[0522] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the cooperating terminal. The service identifiers carried by the first service processing result and the second service processing result are the same.

[0523] In some embodiments, before sending a service request to the first RAN or the first network function, the method further includes:

[0524] The terminal performs business segmentation on the business to be processed, resulting in collaborative sub-businesses;

[0525] The terminal generates a service request based on the service type and requirements of the collaborative sub-service.

[0526] For the implementation methods and beneficial effects of the cooperative service method for terminals, please refer to the relevant descriptions in the embodiments of the cooperative service method for the first RAN above, which will not be repeated here.

[0527] It should be understood that although the steps in the flowchart above are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0528] The technical solutions provided in some embodiments of this disclosure can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These various systems may include terminal equipment and network equipment. The system may also include a core network component, such as an Evolved Packet Core (EPC) or a 5G core network (5GC).

[0529] Based on the same technical concept, some embodiments of this disclosure also provide a collaborative service device. This collaborative service device can implement the functions of the first RAN side in the foregoing embodiments.

[0530] In some embodiments, as shown in FIG19, a cooperative service apparatus is provided, disposed in a first RAN, the apparatus comprising:

[0531] The acquisition module 1901 is used to acquire the terminal capability identifier of at least one terminal accessing the first RAN;

[0532] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0533] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0534] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0535] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0536] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0537] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0538] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0539] In some embodiments, the acquisition module 1901 is configured to receive a registration request sent by the terminal, the registration request carrying at least one of the following:

[0540] The terminal capability identifier;

[0541] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0542] In some embodiments, the apparatus further includes:

[0543] The sending module is used to send the registration request to the first network function.

[0544] In some embodiments, the first network function is AMF.

[0545] In some embodiments, the registration request carries the terminal capability identifier and the terminal type, and the apparatus further includes:

[0546] A storage module is used to store the mapping relationship between the terminal type and the terminal capability identifier in a first capability mapping table.

[0547] In some embodiments, the registration request carries the terminal type, and the acquisition module 1901 is used for:

[0548] Based on the terminal type, obtain the terminal capability identifier.

[0549] In some embodiments, the acquisition module 1901 is used to query the terminal capability identifier associated with the terminal type in a first capability mapping table according to the terminal type.

[0550] In some embodiments, the sending module is further configured to carry the terminal capability identifier in the registration request and send it to the first network function.

[0551] In some embodiments, the apparatus further includes:

[0552] The receiving module is used to receive the terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying the second capability mapping table according to the terminal type and verifying the terminal capability identifier according to the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[0553] The deletion module is used to delete the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type if the terminal capability verification notification indicates that the query result is different from the terminal capability identifier.

[0554] In some embodiments, the second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

[0555] In some embodiments, the receiving module is configured to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

[0556] In some embodiments, the acquisition module 1901 is used to send the registration request to the first network function;

[0557] The receiving module is further configured to receive the terminal capability identifier returned by the first network function, wherein the terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

[0558] In some embodiments, the receiving module is configured to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

[0559] In some embodiments, the acquisition module 1901 is configured to send a terminal capability request to the terminal when a preset condition is met; and receive a terminal capability response sent by the terminal, wherein the terminal capability response carries the terminal capability identifier.

[0560] In some embodiments, the preset conditions include at least one of the following:

[0561] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0562] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0563] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0564] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0565] In some embodiments, when the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0566] In some embodiments, the storage module is further configured to store the mapping relationship between the terminal type and the terminal capability identifier in the first capability mapping table.

[0567] In some embodiments, the sending module is further configured to send the terminal type and the terminal capability identifier to the first network function.

[0568] In some embodiments, the receiving module is further configured to receive the terminal capability request sent by the first network function.

[0569] In some embodiments, the receiving module is further configured to receive a service request sent by the target terminal, the service request carrying a service type and service requirements;

[0570] The device further includes:

[0571] The collaboration module is used to determine a collaboration terminal that matches the service type and the service requirements based on the service request, and / or to determine a network node that matches the service type and the service requirements based on the service request, wherein the collaboration terminal and the network node are respectively used to provide the collaboration service.

[0572] In some embodiments, the cooperating terminal is a terminal that accesses the first RAN.

[0573] In some embodiments, the sending module is further configured to send the service request to the collaborative terminal; if a collaborative confirmation message is received from the collaborative terminal, the module sends the terminal service provider information of the collaborative terminal to the target terminal, wherein the terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

[0574] In some embodiments, the collaboration module is further configured to, if it receives a rejection message from the collaboration terminal, re-determine other collaboration terminals that match the service type and the service requirements.

[0575] In some embodiments, the coordination module is used to send the service request to a first network node; wherein the service request is used by the first network node to determine the coordination terminal based on the service request, the coordination terminal is a terminal accessing a second RAN, and both the first RAN and the second RAN are accessed by the first network node.

[0576] In some embodiments, the collaboration module is further configured to receive terminal servicer information of the collaborative terminal sent by the first network node, and send the terminal servicer information to the target terminal, wherein the terminal servicer information is used by the target terminal to establish a service session with the collaborative terminal.

[0577] In some embodiments, the service request is further used for the first network node to send the service request to a second network node or a central network node if the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0578] In some embodiments, the receiving module is further configured to receive terminal servicer information of the collaborative terminal sent by the first network node, wherein the terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service;

[0579] The sending module is also used to send the terminal service provider information to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0580] It should be noted that the cooperative service apparatus provided in some embodiments of this disclosure can implement all the method steps implemented in the above-described cooperative service method embodiments for the first RAN, and can achieve the same technical effects. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here. Each module in the above-described cooperative service apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the first RAN in hardware form, or it can be stored in the memory of the first RAN in software form, so that the processor can call and execute the operations corresponding to each module.

[0581] Based on the same technical concept, some embodiments of this disclosure also provide a collaborative service device. This collaborative service device can implement the functions of the first network function in the foregoing embodiments.

[0582] In some embodiments, as shown in FIG20, a collaborative service apparatus is provided, configured in a first network function, the apparatus comprising:

[0583] The acquisition module 2001 acquires the terminal capability identifier of at least one terminal accessing the first RAN, wherein the first RAN is the RAN accessing the first network function;

[0584] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0585] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0586] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0587] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0588] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0589] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0590] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0591] In some embodiments, the acquisition module 2001 is configured to receive a registration request from the first RAN or the terminal, wherein the registration request carries at least one of the following:

[0592] The terminal capability identifier;

[0593] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0594] In some embodiments, the registration request carries the terminal capability identifier and the terminal type, and the apparatus further includes:

[0595] A storage module is configured to store the mapping relationship between the terminal type and the terminal capability identifier locally in a second capability mapping table and / or a second capability mapping table in a second network function, wherein the second network function includes at least a UDM.

[0596] In some embodiments, the registration request carries the terminal type of the terminal, and the acquisition module 2001 is used to query the terminal capability identifier associated with the terminal type in the second capability mapping table according to the terminal type.

[0597] In some embodiments, the apparatus further includes:

[0598] The sending module is used to send the terminal capability identifier to the first RAN in the context establishment response.

[0599] In some embodiments, the registration request also carries the terminal capability identifier, and the device further includes:

[0600] The generation module is used to generate a terminal capability verification notification based on the query result and the terminal capability identifier, wherein the query result is obtained by querying the second capability mapping table based on the terminal type;

[0601] The sending module is further configured to send the terminal capability verification notification to the first RAN.

[0602] In some embodiments, the apparatus further includes:

[0603] The deletion module is used to delete the entry in the second capability mapping table corresponding to the terminal type if the query result is different from the terminal capability identifier.

[0604] In some embodiments, the sending module is configured to send the terminal capability verification notification along with a context establishment response to the first RAN.

[0605] In some embodiments, the acquisition module 2001 is configured to receive the terminal capability identifier sent by the first RAN when a preset condition is met. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

[0606] In some embodiments, the sending module is further configured to send the terminal capability request to the first RAN;

[0607] The acquisition module 2001 is used to receive the terminal capability response of the terminal sent by the first RAN, wherein the terminal capability response carries the terminal capability identifier.

[0608] In some embodiments, the preset conditions include at least one of the following:

[0609] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0610] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0611] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0612] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0613] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0614] In some embodiments, the storage module is further configured to store the mapping relationship between the terminal type and the terminal capability identifier in a second capability mapping table.

[0615] In some embodiments, the apparatus further includes:

[0616] The receiving module is used to receive service requests sent by the target terminal, wherein the service requests carry the service type and service requirements;

[0617] The collaboration module is used to determine a collaboration terminal that matches the service type and the service requirements based on the service request, and / or to determine a network node that matches the service type and the service requirements based on the service request, wherein the collaboration terminal and the network node are respectively used to provide the collaboration service.

[0618] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access the same network node.

[0619] In some embodiments, the sending module is further configured to send the service request to the collaborative terminal; if a collaborative confirmation message is received from the collaborative terminal, the module sends the terminal service provider information of the collaborative terminal to the target terminal, wherein the terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

[0620] In some embodiments, the collaboration module is further configured to, if it receives a rejection message from the collaboration terminal, re-determine other collaboration terminals that match the service type and the service requirements.

[0621] In some embodiments, the coordination module is configured to send the service request to a second network node or a central network node if no matching collaborative terminal is found according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing a second RAN, and the first RAN and the second RAN access different network nodes.

[0622] In some embodiments, the receiving module is further configured to receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[0623] The sending module is also used to send the terminal service provider information to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0624] In some embodiments, when the terminal service provider information is sent by the central network node, the sending module is further configured to send a collaborative service request to the second network node; if a confirmation collaborative response is received from the second network node, the terminal service provider information is sent to the target terminal.

[0625] In some embodiments, the first network function is AMF.

[0626] It should be noted that the collaborative service apparatus provided in some embodiments of this disclosure can implement all the method steps implemented in the collaborative service method embodiments for the first network function, and can achieve the same technical effects. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here. Each module in the collaborative service apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the first network function in hardware form, or stored in the memory of the first network function in software form, so that the processor can call and execute the operations corresponding to each module.

[0627] Based on the same technical concept, some embodiments of this disclosure also provide a collaborative service device. This collaborative service device can realize the terminal-side functions described in the foregoing embodiments.

[0628] In some embodiments, as shown in FIG21, a collaborative service device is provided, disposed on a terminal, the device comprising:

[0629] The sending module 2101 is used to report the terminal capability identifier of the terminal to the first RAN accessed by the terminal, and / or to report the terminal capability identifier to the first network function accessed by the terminal;

[0630] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0631] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0632] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0633] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0634] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0635] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0636] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0637] In some embodiments, the sending module 2101 is configured to send a registration request to the first RAN, the registration request carrying at least one of the following:

[0638] The terminal capability identifier;

[0639] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0640] In some embodiments, the apparatus further includes:

[0641] A receiving module is used to receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under preset conditions;

[0642] The sending module 2101 is used to send a terminal capability response to the first RAN, the terminal capability response carrying the terminal capability identifier.

[0643] In some embodiments, the preset conditions include at least one of the following:

[0644] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0645] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0646] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0647] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0648] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0649] In some embodiments, the sending module 2101 is further configured to send a service request to the first RAN or the first network function, the service request carrying a service type and service requirements, the service request being used to determine a cooperating terminal and / or network node matching the service type and service requirements, wherein the cooperating terminal and the network node are respectively used to provide the cooperative service.

[0650] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[0651] The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or,

[0652] The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0653] In some embodiments, the receiving module is further configured to receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function;

[0654] The device further includes:

[0655] The session establishment module is used to establish a business session with the collaborating terminal based on the terminal service provider information.

[0656] In some embodiments, the receiving module is further configured to send a first service processing result to the network node during the collaborative service process between the terminal and the collaborating terminal;

[0657] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

[0658] In some embodiments, the apparatus further includes:

[0659] The task segmentation module is used to segment the business to be processed into collaborative sub-businesses.

[0660] The generation module is used to generate the business request based on the business type and business requirements of the collaborative sub-business.

[0661] It should be noted that the collaborative service apparatus provided in some embodiments of this disclosure can implement all the method steps implemented in the above-described collaborative service method embodiments for terminals, and can achieve the same technical effects. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here. Each module in the above-described collaborative service apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the terminal in hardware form, or stored in the memory of the terminal in software form, so that the processor can call and execute the operations corresponding to each module.

[0662] Figure 22 is a schematic diagram of the structure of a RAN provided in some embodiments of this disclosure. The RAN may include a processor 2200, a transceiver 2210, and a memory 2220. The transceiver 2210 is used to receive and transmit data under the control of the processor 2200.

[0663] In Figure 22, the bus architecture may include any number of interconnected buses and bridges, linking various circuits of one or more processors represented by processor 2200 and memory represented by memory 2220. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0664] Transceiver 2210 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. Processor 2200 is responsible for managing the bus architecture and general processing, and memory 2220 can store data used by processor 2200 during operation.

[0665] The processor 2200 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 2200 can also adopt a multi-core architecture.

[0666] The processor 2200 invokes a program stored in memory 2220 to execute the following steps according to the obtained executable instructions:

[0667] Obtain the terminal capability identifier of at least one terminal accessing the first RAN;

[0668] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0669] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0670] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0671] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0672] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0673] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0674] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0675] In some embodiments, the processor 2200 is configured to perform the following operations:

[0676] The transceiver 2210 is controlled to receive a registration request sent by the terminal, the registration request carrying at least one of the following:

[0677] The terminal capability identifier;

[0678] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0679] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0680] The transceiver 2210 is controlled to send the registration request to the first network function.

[0681] In some embodiments, the first network function is AMF.

[0682] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0683] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0684] In some embodiments, the registration request carries the terminal type, and the processor 2200 is further configured to perform the following operations:

[0685] Based on the terminal type, obtain the terminal capability identifier.

[0686] In some embodiments, the processor 2200 is configured to perform the following operations:

[0687] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

[0688] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0689] The transceiver 2210 is controlled to send the terminal capability identifier along with the registration request to the first network function.

[0690] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0691] The transceiver 2210 is controlled to receive a terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table according to the terminal type and verifying the terminal capability identifier according to the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[0692] If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

[0693] In some embodiments, the second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

[0694] In some embodiments, the processor 2200 is configured to perform the following operations:

[0695] The transceiver 2210 is controlled to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

[0696] In some embodiments, the processor 2200 is configured to perform the following operations:

[0697] The transceiver 2210 is controlled to send the registration request to the first network function;

[0698] The transceiver 2210 is controlled to receive the terminal capability identifier returned by the first network function. The terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

[0699] In some embodiments, the processor 2200 is configured to perform the following operations:

[0700] The transceiver 2210 is controlled to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

[0701] In some embodiments, the processor 2200 is configured to perform the following operations:

[0702] Under preset conditions, the transceiver 2210 is controlled to send a terminal capability request to the terminal;

[0703] The transceiver 2210 is controlled to receive the terminal capability response sent by the terminal, the terminal capability response carrying the terminal capability identifier.

[0704] In some embodiments, the preset conditions include at least one of the following:

[0705] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0706] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0707] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0708] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0709] In some embodiments, when the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0710] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0711] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0712] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0713] The transceiver 2210 is controlled to send the terminal type and the terminal capability identifier to the first network function.

[0714] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0715] The transceiver 2210 is controlled to receive the terminal capability request sent by the first network function.

[0716] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0717] The transceiver 2210 is controlled to receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0718] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0719] In some embodiments, the cooperating terminal is a terminal that accesses the first RAN.

[0720] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0721] Control the transceiver 2210 to send the service request to the collaborative terminal;

[0722] If a collaboration confirmation message is received from the collaboration terminal, the transceiver 2210 is controlled to send the terminal servicer information of the collaboration terminal to the target terminal. The terminal servicer information is used by the target terminal to establish a service session with the collaboration terminal.

[0723] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0724] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0725] In some embodiments, the processor 2200 is configured to perform the following operations:

[0726] The transceiver 2210 is controlled to send the service request to the first network node;

[0727] The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

[0728] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0729] The transceiver 2210 is controlled to receive the terminal servicer information of the collaborative terminal sent by the first network node, and send the terminal servicer information to the target terminal. The terminal servicer information is used by the target terminal to establish a service session with the collaborative terminal.

[0730] In some embodiments, the service request is further used for the first network node to send the service request to a second network node or a central network node if the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0731] In some embodiments, the processor 2200 is further configured to perform the following operations:

[0732] The transceiver 2210 is controlled to receive terminal servicer information of the collaborative terminal sent by the first network node. The terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service.

[0733] The transceiver 2210 is controlled to send the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0734] Figure 23 is a schematic diagram of the structure of a network function provided in some embodiments of this disclosure. The network function may include a processor 2300, a transceiver 2310, and a memory 2320. The transceiver 2310 is used to receive and transmit data under the control of the processor 2300.

[0735] In Figure 23, the bus architecture may include any number of interconnected buses and bridges, linking various circuits of one or more processors represented by processor 2300 and memory represented by memory 2320. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0736] The transceiver 2310 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. The processor 2300 is responsible for managing the bus architecture and general processing, and the memory 2320 can store data used by the processor 2300 during operation.

[0737] The processor 2300 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 2300 can also adopt a multi-core architecture.

[0738] The processor 2300 invokes the program stored in memory 2320 to execute the following steps according to the obtained executable instructions:

[0739] Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN accessing the first network function (i.e., the network function shown in Figure 23);

[0740] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0741] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0742] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0743] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0744] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0745] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0746] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0747] In some embodiments, the processor 2300 is configured to perform the following operations:

[0748] The transceiver 2310 is controlled to receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following:

[0749] The terminal capability identifier;

[0750] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0751] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0752] The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

[0753] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0754] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

[0755] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0756] The transceiver 2310 is controlled to send the terminal capability identifier in the context establishment response to the first RAN.

[0757] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0758] A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type.

[0759] The transceiver 2310 is controlled to send the terminal capability verification notification to the first RAN.

[0760] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0761] If the query result is different from the terminal capability identifier, then delete the entry in the second capability mapping table that corresponds to the terminal type.

[0762] In some embodiments, the processor 2300 is configured to perform the following operations:

[0763] The transceiver 2310 is controlled to send the terminal capability verification notification along with a context establishment response to the first RAN.

[0764] In some embodiments, the processor 2300 is configured to perform the following operations:

[0765] Under preset conditions, the transceiver 2310 is controlled to receive the terminal capability identifier sent by the first RAN. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

[0766] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0767] Control the transceiver 2310 to send the terminal capability request to the first RAN;

[0768] The transceiver 2310 is controlled to receive the terminal capability response of the terminal sent by the first RAN, wherein the terminal capability response carries the terminal capability identifier.

[0769] In some embodiments, the preset conditions include at least one of the following:

[0770] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0771] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0772] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0773] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0774] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0775] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0776] The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

[0777] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0778] The transceiver 2310 is controlled to receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0779] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0780] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access the same network node.

[0781] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0782] Control the transceiver 2310 to send the service request to the collaborative terminal;

[0783] If a collaboration confirmation message is received from the collaboration terminal, the transceiver 2310 is controlled to send the terminal servicer information of the collaboration terminal to the target terminal. The terminal servicer information is used by the target terminal to establish a service session with the collaboration terminal.

[0784] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0785] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0786] In some embodiments, the processor 2300 is configured to perform the following operations:

[0787] If no matching terminal is found according to the service request, then control the transceiver 2310.

[0788] The service request is sent to a second network node or a central network node, so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0789] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0790] The transceiver 2310 is controlled to receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[0791] The transceiver 2310 is controlled to send the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0792] In some embodiments, the processor 2300 is further configured to perform the following operations:

[0793] Control the transceiver 2310 to send a cooperative service request to the second network node;

[0794] If a confirmation and coordination response is received from the second network node, the transceiver 2310 is controlled to send the terminal servicer information to the target terminal.

[0795] In some embodiments, the first network function is AMF.

[0796] Figure 24 is a schematic diagram of the structure of a terminal provided in some embodiments of this disclosure. The terminal may include a processor 2400, a transceiver 2410, and a memory 2420. The transceiver 2410 is used to receive and send data under the control of the processor 2400.

[0797] In Figure 24, the bus architecture may include any number of interconnected buses and bridges, linking various circuits of one or more processors represented by processor 2400 and memory represented by memory 2420. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0798] The transceiver 2410 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. For different user equipment, the user interface may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc. The processor 2400 is responsible for managing the bus architecture and general processing, and the memory 2420 can store data used by the processor 2400 during operation.

[0799] In some embodiments, the processor 2400 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor 2400 may also adopt a multi-core architecture.

[0800] The processor 2400 invokes a program stored in memory to perform the following steps according to the obtained executable instructions:

[0801] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal.

[0802] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0803] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0804] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0805] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0806] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0807] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0808] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0809] In some embodiments, the processor 2400 is configured to perform the following operations:

[0810] The transceiver 2410 is controlled to send a registration request to the first RAN, the registration request carrying at least one of the following:

[0811] The terminal capability identifier;

[0812] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0813] In some embodiments, the processor 2400 is further configured to perform the following operations:

[0814] The transceiver 2410 is controlled to receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under the condition that preset conditions are met;

[0815] The transceiver 2410 is controlled to send a terminal capability response to the first RAN, the terminal capability response carrying the terminal capability identifier.

[0816] In some embodiments, the preset conditions include at least one of the following:

[0817] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0818] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0819] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0820] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0821] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0822] In some embodiments, the processor 2400 is further configured to perform the following operations:

[0823] The transceiver 2410 is controlled to send a service request to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

[0824] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[0825] The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or,

[0826] The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0827] In some embodiments, the processor 2400 is further configured to perform the following operations:

[0828] The transceiver 2410 is controlled to receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function;

[0829] A business session is established with the collaborating terminal based on the terminal service provider information.

[0830] In some embodiments, the processor 2400 is further configured to perform the following operations:

[0831] During the collaborative service process between the terminal and the collaborating terminal, the transceiver 2410 is controlled to send the first service processing result to the network node;

[0832] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

[0833] In some embodiments, the processor 2400 is further configured to perform the following operations:

[0834] The business to be processed is divided into business segments to obtain collaborative sub-businesses;

[0835] The business request is generated based on the business type and business requirements of the collaborative sub-business.

[0836] In some embodiments, a computer-readable storage medium is provided, which may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO) etc.), optical memory (e.g., CD, DVD, BD, HVD etc.), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD) etc.).

[0837] In some embodiments, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0838] Obtain the terminal capability identifier of at least one terminal accessing the first RAN;

[0839] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0840] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0841] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0842] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0843] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0844] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0845] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0846] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0847] Receive a registration request sent by the terminal, the registration request carrying at least one of the following:

[0848] The terminal capability identifier;

[0849] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0850] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0851] The registration request is sent to the first network function.

[0852] In some embodiments, the first network function is AMF.

[0853] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0854] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0855] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0856] Based on the terminal type, obtain the terminal capability identifier.

[0857] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0858] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

[0859] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0860] The terminal capability identifier is carried in the registration request and sent to the first network function.

[0861] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0862] The system receives a terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table based on the terminal type and verifying the terminal capability identifier based on the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[0863] If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

[0864] In some embodiments, the second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

[0865] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0866] Receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

[0867] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0868] The registration request is sent to the first network function;

[0869] The terminal capability identifier returned by the first network function is received. The terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

[0870] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0871] The system receives a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

[0872] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0873] Under the condition that the preset conditions are met, a terminal capability request is sent to the terminal;

[0874] The terminal capability response sent by the terminal is received, and the terminal capability response carries the terminal capability identifier.

[0875] In some embodiments, the preset conditions include at least one of the following:

[0876] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0877] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0878] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0879] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0880] In some embodiments, when the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0881] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0882] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[0883] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0884] Send the terminal type and the terminal capability identifier to the first network function.

[0885] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0886] Receive the terminal capability request sent by the first network function.

[0887] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0888] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0889] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0890] In some embodiments, the cooperating terminal is a terminal that accesses the first RAN.

[0891] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0892] Send the service request to the collaborative terminal;

[0893] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[0894] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0895] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0896] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0897] The service request is sent to the first network node;

[0898] The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

[0899] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0900] The system receives terminal service provider information of the collaborative terminal sent by the first network node and sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

[0901] In some embodiments, the service request is further used for the first network node to send the service request to a second network node or a central network node if the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0902] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0903] The system receives terminal servicer information of the collaborative terminal sent by the first network node, wherein the terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service.

[0904] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0905] In some embodiments, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0906] Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function;

[0907] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0908] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0909] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0910] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0911] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0912] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0913] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0914] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0915] Receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following:

[0916] The terminal capability identifier;

[0917] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0918] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0919] The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

[0920] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0921] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

[0922] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0923] The terminal capability identifier is sent to the first RAN in the context establishment response.

[0924] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0925] A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type.

[0926] The terminal capability verification notification is sent to the first RAN.

[0927] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0928] If the query result is different from the terminal capability identifier, then delete the entry in the second capability mapping table that corresponds to the terminal type.

[0929] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0930] The terminal capability verification notification is sent to the first RAN along with the context establishment response.

[0931] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0932] Under preset conditions, the terminal capability identifier sent by the first RAN is received. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

[0933] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0934] Send the terminal capability request to the first RAN;

[0935] The step of receiving the terminal capability identifier sent by the first RAN includes:

[0936] The terminal capability response of the terminal is received from the first RAN, and the terminal capability response carries the terminal capability identifier.

[0937] In some embodiments, the preset conditions include at least one of the following:

[0938] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0939] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0940] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0941] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0942] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0943] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0944] The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

[0945] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0946] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[0947] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[0948] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access the same network node.

[0949] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0950] Send the service request to the collaborative terminal;

[0951] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[0952] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0953] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[0954] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0955] If no matching collaborative terminal is found according to the service request, the service request is sent to a second network node or a central network node so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[0956] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0957] Receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[0958] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[0959] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0960] Send a collaborative service request to the second network node;

[0961] Sending the terminal service provider information to the target terminal includes:

[0962] If a confirmation and collaboration response is received from the second network node, the terminal service provider information is sent to the target terminal.

[0963] In some embodiments, the first network function is AMF.

[0964] In some embodiments, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0965] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal.

[0966] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[0967] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[0968] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[0969] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[0970] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[0971] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[0972] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[0973] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[0974] Send a registration request to the first RAN, the registration request carrying at least one of the following:

[0975] The terminal capability identifier;

[0976] The terminal type of the terminal is used to obtain the terminal capability identifier.

[0977] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0978] Receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under the condition of meeting preset conditions;

[0979] The step of reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes:

[0980] A terminal capability response is sent to the first RAN, the terminal capability response carrying the terminal capability identifier.

[0981] In some embodiments, the preset conditions include at least one of the following:

[0982] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[0983] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[0984] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[0985] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[0986] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[0987] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0988] A service request is sent to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

[0989] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[0990] The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or,

[0991] The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[0992] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0993] Receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function;

[0994] A business session is established with the collaborating terminal based on the terminal service provider information.

[0995] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0996] During the collaborative service process between the terminal and the collaborating terminal, a first service processing result is sent to the network node;

[0997] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

[0998] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[0999] The business to be processed is divided into business segments to obtain collaborative sub-businesses;

[1000] The business request is generated based on the business type and business requirements of the collaborative sub-business.

[1001] Figure 25 is a schematic structural diagram of a chip according to some embodiments of the present disclosure. The chip 2500 shown in Figure 25 includes a processor 2510, which can call and run computer programs from memory to implement the methods in some embodiments of the present disclosure.

[1002] In some embodiments, as shown in FIG25, chip 2500 may further include memory 2520. Processor 2510 may retrieve and run computer programs from memory 2520 to implement methods in some embodiments of this disclosure.

[1003] The memory 2520 can be a separate device independent of the processor 2510, or it can be integrated into the processor 2510.

[1004] In some embodiments, the chip 2500 may further include an input interface 2530. The processor 2510 can control the input interface 2530 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[1005] In some embodiments, the chip 2500 may further include an output interface 2540. The processor 2510 can control the output interface 2540 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips.

[1006] In some embodiments, the chip 2500 can be applied to network element devices in some embodiments of this disclosure, and the chip 2500 can implement the corresponding processes implemented in various methods in some embodiments of this disclosure. For the sake of brevity, these will not be described in detail here.

[1007] It should be understood that the chip 2500 mentioned in some embodiments of this disclosure may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[1008] In some embodiments, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[1009] Obtain the terminal capability identifier of at least one terminal accessing the first RAN;

[1010] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[1011] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[1012] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[1013] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[1014] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[1015] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[1016] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[1017] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1018] Receive a registration request sent by the terminal, the registration request carrying at least one of the following:

[1019] The terminal capability identifier;

[1020] The terminal type of the terminal is used to obtain the terminal capability identifier.

[1021] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1022] The registration request is sent to the first network function.

[1023] In some embodiments, the first network function is AMF.

[1024] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1025] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[1026] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1027] Based on the terminal type, obtain the terminal capability identifier.

[1028] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1029] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

[1030] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1031] The terminal capability identifier is carried in the registration request and sent to the first network function.

[1032] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1033] The system receives a terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table based on the terminal type and verifying the terminal capability identifier based on the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier.

[1034] If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

[1035] In some embodiments, the second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

[1036] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1037] Receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

[1038] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1039] The registration request is sent to the first network function;

[1040] The terminal capability identifier returned by the first network function is received. The terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

[1041] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1042] The system receives a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

[1043] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1044] Under the condition that the preset conditions are met, a terminal capability request is sent to the terminal;

[1045] The terminal capability response sent by the terminal is received, and the terminal capability response carries the terminal capability identifier.

[1046] In some embodiments, the preset conditions include at least one of the following:

[1047] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[1048] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[1049] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[1050] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[1051] In some embodiments, when the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[1052] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1053] The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

[1054] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1055] Send the terminal type and the terminal capability identifier to the first network function.

[1056] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1057] Receive the terminal capability request sent by the first network function.

[1058] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1059] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[1060] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[1061] In some embodiments, the cooperating terminal is a terminal that accesses the first RAN.

[1062] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1063] Send the service request to the collaborative terminal;

[1064] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[1065] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1066] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[1067] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1068] The service request is sent to the first network node;

[1069] The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

[1070] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1071] The system receives terminal service provider information of the collaborative terminal sent by the first network node and sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

[1072] In some embodiments, the service request is further used for the first network node to send the service request to a second network node or a central network node if the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, wherein the collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[1073] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1074] The system receives terminal servicer information of the collaborative terminal sent by the first network node, wherein the terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service.

[1075] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[1076] In some embodiments, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[1077] Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function;

[1078] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[1079] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[1080] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[1081] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[1082] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[1083] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[1084] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[1085] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1086] Receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following:

[1087] The terminal capability identifier;

[1088] The terminal type of the terminal is used to obtain the terminal capability identifier.

[1089] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1090] The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

[1091] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1092] Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

[1093] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1094] The terminal capability identifier is sent to the first RAN in the context establishment response.

[1095] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1096] A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type.

[1097] The terminal capability verification notification is sent to the first RAN.

[1098] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1099] If the query result is different from the terminal capability identifier, then delete the entry in the second capability mapping table that corresponds to the terminal type.

[1100] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1101] The terminal capability verification notification is sent to the first RAN along with the context establishment response.

[1102] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1103] Under preset conditions, the terminal capability identifier sent by the first RAN is received. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

[1104] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1105] Send the terminal capability request to the first RAN;

[1106] The step of receiving the terminal capability identifier sent by the first RAN includes:

[1107] The terminal capability response of the terminal is received from the first RAN, and the terminal capability response carries the terminal capability identifier.

[1108] In some embodiments, the preset conditions include at least one of the following:

[1109] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[1110] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[1111] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[1112] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[1113] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[1114] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1115] The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

[1116] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1117] Receive a service request sent by the target terminal, the service request carrying the service type and service requirements;

[1118] Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

[1119] In some embodiments, the cooperating terminal is a terminal accessing the first RAN, or the cooperating terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access the same network node.

[1120] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1121] Send the service request to the collaborative terminal;

[1122] If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

[1123] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1124] If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be re-identified.

[1125] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1126] If no matching collaborative terminal is found according to the service request, the service request is sent to a second network node or a central network node so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

[1127] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1128] Receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node;

[1129] The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

[1130] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1131] Send a collaborative service request to the second network node;

[1132] Sending the terminal service provider information to the target terminal includes:

[1133] If a confirmation and collaboration response is received from the second network node, the terminal service provider information is sent to the target terminal.

[1134] In some embodiments, the first network function is AMF.

[1135] In some embodiments, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[1136] The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal.

[1137] The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

[1138] In some embodiments, the capability field includes at least one of an intelligent capability field, a perception capability field, and a computing capability field;

[1139] The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

[1140] In some embodiments, the intelligent capability includes at least one of intelligent training capability, intelligent reasoning capability, and intelligent monitoring capability;

[1141] The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities.

[1142] The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

[1143] In some embodiments, the capability field further includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

[1144] In some embodiments, when a computer program is executed by a processor, it performs the following steps:

[1145] Send a registration request to the first RAN, the registration request carrying at least one of the following:

[1146] The terminal capability identifier;

[1147] The terminal type of the terminal is used to obtain the terminal capability identifier.

[1148] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1149] Receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under the condition of meeting preset conditions;

[1150] The step of reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes:

[1151] A terminal capability response is sent to the first RAN, the terminal capability response carrying the terminal capability identifier.

[1152] In some embodiments, the preset conditions include at least one of the following:

[1153] The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type.

[1154] The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type;

[1155] The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function.

[1156] The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

[1157] In some embodiments, when the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

[1158] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1159] A service request is sent to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

[1160] In some embodiments, the cooperating terminal is a terminal accessing the first RAN; or,

[1161] The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or,

[1162] The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

[1163] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1164] Receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function;

[1165] A business session is established with the collaborating terminal based on the terminal service provider information.

[1166] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1167] During the collaborative service process between the terminal and the collaborating terminal, a first service processing result is sent to the network node;

[1168] The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

[1169] In some embodiments, when a computer program is executed by a processor, it further performs the following steps:

[1170] The business to be processed is divided into business segments to obtain collaborative sub-businesses;

[1171] The business request is generated based on the business type and business requirements of the collaborative sub-business.

[1172] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[1173] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[1174] The embodiments described above are merely illustrative of several implementations of this disclosure, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this disclosure, and these all fall within the scope of protection of this disclosure. Therefore, the scope of protection of this patent should be determined by the appended claims.

Claims

1. A collaborative service method, wherein, For the first RAN, the method includes: Obtain the terminal capability identifier of at least one terminal accessing the first RAN; The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

2. The method according to claim 1, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

3. The method according to claim 2, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

4. The method according to claim 2, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

5. The method according to claim 1, wherein, The step of obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes: Receive a registration request sent by the terminal, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

6. The method according to claim 5, wherein, The method further includes: The registration request is sent to the first network function.

7. The method according to claim 6, wherein, The first network function is AMF.

8. The method according to claim 5, wherein, The registration request carries the terminal capability identifier and the terminal type, and the method further includes: The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

9. The method according to claim 5, wherein, The registration request carries the terminal type, and the method further includes: Based on the terminal type, obtain the terminal capability identifier.

10. The method according to claim 9, wherein, The step of obtaining the terminal capability identifier based on the terminal type includes: Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

11. The method according to claim 9, wherein, The method further includes: The terminal capability identifier is carried in the registration request and sent to the first network function.

12. The method according to claim 11, wherein, The method further includes: The system receives a terminal capability verification notification sent by the first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table based on the terminal type and verifying the terminal capability identifier based on the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier. If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

13. The method according to claim 12, wherein, The second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

14. The method according to claim 12, wherein, The receiving of the terminal capability verification notification sent by the first network function includes: Receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

15. The method according to claim 9, wherein, The step of obtaining the terminal capability identifier based on the terminal type includes: The registration request is sent to the first network function; The terminal capability identifier returned by the first network function is received. The terminal capability identifier is obtained by the first network function by querying a second capability mapping table according to the terminal type.

16. The method according to claim 15, wherein, The step of receiving the terminal capability identifier returned by the first network function includes: The system receives a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

17. The method according to claim 1, wherein, The step of obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes: Under the condition that the preset conditions are met, a terminal capability request is sent to the terminal; The terminal capability response sent by the terminal is received, and the terminal capability response carries the terminal capability identifier.

18. The method according to claim 17, wherein, The preset conditions include at least one of the following: The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type. The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type; The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function. The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

19. The method according to claim 18, wherein, When the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

20. The method according to claim 19, wherein, The method further includes: The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

21. The method according to claim 19, wherein, After receiving the terminal capability response sent by the terminal, the method further includes: Send the terminal type and the terminal capability identifier to the first network function.

22. The method according to claim 21, wherein, Before sending the terminal capability request to the terminal, the method further includes: Receive the terminal capability request sent by the first network function.

23. The method according to claim 1, wherein, The method further includes: Receive a service request sent by the target terminal, the service request carrying the service type and service requirements; Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

24. The method according to claim 23, wherein, The collaborative terminal is a terminal that is connected to the first RAN.

25. The method according to claim 23, wherein, The method further includes: Send the service request to the collaborative terminal; If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

26. The method according to claim 25, wherein, The method further includes: If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be identified again.

27. The method according to claim 23, wherein, The step of determining the collaborative terminal that matches the service type and the service requirements based on the service request includes: The service request is sent to the first network node; The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

28. The method according to claim 27, wherein, The method further includes: The system receives terminal service provider information of the collaborative terminal sent by the first network node and sends the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborative terminal.

29. The method according to claim 27, wherein, The service request is also used by the first network node to send the service request to the second network node or the central network node when the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, the collaborative terminal being a terminal accessing the second RAN, and the first RAN and the second RAN accessing different network nodes.

30. The method according to claim 29, wherein, The method further includes: The system receives terminal servicer information of the collaborative terminal sent by the first network node, wherein the terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service. The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

31. A collaborative service method, wherein, For a first network function, the method includes: Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function; The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

32. The method according to claim 31, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

33. The method according to claim 32, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

34. The method according to claim 32, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

35. The method according to claim 31, wherein, The step of obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes: Receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

36. The method according to claim 35, wherein, The registration request carries the terminal capability identifier and the terminal type, and the method further includes: The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

37. The method of claim 35, wherein, The registration request carries the terminal type of the terminal, and the method further includes: Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

38. The method according to claim 37, wherein, The method further includes: The terminal capability identifier is sent to the first RAN in the context establishment response.

39. The method according to claim 37, wherein, The registration request also carries the terminal capability identifier, and the method further includes: A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type. The terminal capability verification notification is sent to the first RAN.

40. The method according to claim 39, wherein, The method further includes: If the query result is different from the terminal capability identifier, then delete the entry in the second capability mapping table that corresponds to the terminal type.

41. The method according to claim 39, wherein, Sending the terminal capability verification notification to the first RAN includes: The terminal capability verification notification is sent to the first RAN along with the context establishment response.

42. The method according to claim 31, wherein, The step of obtaining the terminal capability identifier of at least one terminal accessing the first RAN includes: Under preset conditions, the terminal capability identifier sent by the first RAN is received. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

43. The method according to claim 42, wherein, Before receiving the terminal capability identifier sent by the first RAN, the method further includes: Send the terminal capability request to the first RAN; The step of receiving the terminal capability identifier sent by the first RAN includes: The terminal capability response of the terminal is received from the first RAN, and the terminal capability response carries the terminal capability identifier.

44. The method according to claim 42, wherein, The preset conditions include at least one of the following: The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type. The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type; The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function. The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

45. The method according to claim 44, wherein, If the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

46. ​​The method according to claim 45, wherein, The method further includes: The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

47. The method according to claim 31, wherein, The method further includes: Receive a service request sent by the target terminal, the service request carrying the service type and service requirements; Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

48. The method according to claim 47, wherein, The cooperating terminal is either a terminal connected to the first RAN or a terminal connected to the second RAN, and the first RAN and the second RAN are connected to the same network node.

49. The method according to claim 47, wherein, The method further includes: Send the service request to the collaborative terminal; If a collaboration confirmation message is received from the collaboration terminal, the terminal service provider information of the collaboration terminal is sent to the target terminal. The terminal service provider information is used by the target terminal to establish a business session with the collaboration terminal.

50. The method according to claim 49, wherein, The method further includes: If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be identified again.

51. The method according to claim 47, wherein, The step of determining the collaborative terminal that matches the service type and the service requirements based on the service request includes: If no matching collaborative terminal is found according to the service request, the service request is sent to a second network node or a central network node so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

52. The method according to claim 51, wherein, The method further includes: Receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node; The terminal service provider information is sent to the target terminal, and the terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

53. The method according to claim 52, wherein, When the terminal service provider information is sent by the central network node, before sending the terminal service provider information to the target terminal, the method further includes: Send a collaborative service request to the second network node; Sending the terminal service provider information to the target terminal includes: If a confirmation and collaboration response is received from the second network node, the terminal service provider information is sent to the target terminal.

54. The method according to claim 31, wherein, The first network function is AMF.

55. A collaborative service method, wherein, For a terminal, the method includes: The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal. The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

56. The method according to claim 55, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

57. The method according to claim 56, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

58. The method according to claim 56, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

59. The method according to claim 55, wherein, The step of reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes: Send a registration request to the first RAN, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

60. The method of claim 55, wherein, Before reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal, the method further includes: Receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under the condition of meeting preset conditions; The step of reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal includes: A terminal capability response is sent to the first RAN, the terminal capability response carrying the terminal capability identifier.

61. The method according to claim 60, wherein, The preset conditions include at least one of the following: The registration request sent by the terminal to the first RAN did not include the terminal capability identifier or the terminal type. The registration request carries the terminal type, and the first RAN does not find the terminal capability identifier in the first capability mapping table according to the terminal type; The registration request carries the terminal type, and after the first RAN sends the terminal type to the first network function, the first RAN does not receive the terminal capability identifier returned by the first network function. The first RAN deletes the entry in the first capability mapping table corresponding to the terminal type, as instructed by the terminal capability verification notification sent by the first network function.

62. The method according to claim 61, wherein, If the registration request carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

63. The method according to claim 55, wherein, The method further includes: A service request is sent to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

64. The method according to claim 63, wherein, The collaborative terminal is a terminal that is connected to the first RAN; or, The collaborative terminal is a terminal accessing the second RAN, and both the first RAN and the second RAN are accessed by the same network node; or, The collaborative terminal is a terminal that accesses the second RAN, and the first RAN and the second RAN access different network nodes.

65. The method according to claim 63, wherein, The method further includes: Receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function; A business session is established with the collaborating terminal based on the terminal service provider information.

66. The method according to claim 63, wherein, The method further includes: During the collaborative service process between the terminal and the collaborating terminal, a first service processing result is sent to the network node; The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

67. The method according to claim 63, wherein, Before sending the service request to the first RAN or the first network function, the method further includes: The business to be processed is divided into business segments to obtain collaborative sub-businesses; The business request is generated based on the business type and business requirements of the collaborative sub-business.

68. A RAN, wherein, Includes memory, transceiver, and processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Obtain the terminal capability identifier of at least one terminal accessing the first RAN; The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

69. The RAN according to claim 68, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

70. The RAN according to claim 69, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

71. The RAN according to claim 69, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

72. The RAN according to claim 68, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to receive a registration request sent by the terminal, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

73. The RAN according to claim 72, wherein, The registration request carries the terminal capability identifier and the terminal type. The processor is configured to read the computer program in the memory and further perform the following operations: The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

74. The RAN according to claim 72, wherein, The registration request carries the terminal type, and the processor is configured to read the computer program in the memory and further perform the following operations: Based on the terminal type, obtain the terminal capability identifier.

75. The RAN according to claim 74, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Based on the terminal type, query the terminal capability identifier associated with the terminal type in the first capability mapping table.

76. The RAN according to claim 74, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive a terminal capability verification notification sent by a first network function. The terminal capability verification notification is generated by the first network function after querying a second capability mapping table according to the terminal type and verifying the terminal capability identifier according to the query result. The second capability mapping table stores the mapping relationship between terminal type and terminal capability identifier. If the terminal capability verification notification indicates that the query result is different from the terminal capability identifier, then the entries in the first capability mapping table and the second capability mapping table corresponding to the terminal type are deleted.

77. The RAN according to claim 76, wherein, The second capability mapping table is stored in the first network function and / or the second network function, the second network function including at least UDM.

78. The RAN according to claim 76, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability verification notification.

79. The RAN according to claim 74, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to send the registration request to the first network function; The transceiver is controlled to receive the terminal capability identifier returned by the first network function, which is obtained by the first network function by querying a second capability mapping table according to the terminal type.

80. The RAN according to claim 79, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to receive a context establishment response sent by the first network function, the context establishment response carrying the terminal capability identifier and the terminal type.

81. The RAN according to claim 68, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Under preset conditions, the transceiver is controlled to send a terminal capability request to the terminal; The transceiver is controlled to receive a terminal capability response sent by the terminal, the terminal capability response carrying the terminal capability identifier.

82. The RAN according to claim 81, wherein, When the registration request sent by the terminal carries the terminal type, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

83. The RAN according to claim 82, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The mapping relationship between the terminal type and the terminal capability identifier is stored in the first capability mapping table.

84. The RAN according to claim 82, wherein, After receiving the terminal capability response sent by the terminal, the processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to send the terminal type and the terminal capability identifier to the first network function.

85. The RAN according to claim 68, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive service requests sent by the target terminal, the service requests carrying the service type and service requirements; Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

86. The RAN according to claim 85, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: Control the transceiver to send the service request to the collaborative terminal; If a collaboration confirmation message is received from the collaboration terminal, the transceiver is controlled to send the terminal service provider information of the collaboration terminal to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaboration terminal.

87. The RAN according to claim 86, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be identified again.

88. The RAN according to claim 85, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Control the transceiver to send the service request to the first network node; The service request is used by the first network node to determine the cooperating terminal based on the service request. The cooperating terminal is a terminal that accesses the second RAN, and both the first RAN and the second RAN are accessed by the first network node.

89. The RAN according to claim 88, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive the terminal servicer information of the collaborative terminal sent by the first network node, and to send the terminal servicer information to the target terminal. The terminal servicer information is used by the target terminal to establish a service session with the collaborative terminal.

90. The RAN according to claim 88, wherein, The service request is also used by the first network node to send the service request to the second network node or the central network node when the first network node fails to match the collaborative terminal according to the service request, so that the second network node or the central network node can determine the collaborative terminal, the collaborative terminal being a terminal accessing the second RAN, and the first RAN and the second RAN accessing different network nodes.

91. The RAN according to claim 90, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive terminal servicer information of the collaborative terminal sent by the first network node. The terminal servicer information is sent by the first network node after determining that the second network node has confirmed the collaborative service. The transceiver is controlled to send the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

92. A network function, wherein, Includes memory, transceiver, and processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Obtain the terminal capability identifier of at least one terminal accessing the first RAN, where the first RAN is the RAN that accesses the first network function; The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

93. The network function according to claim 92, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

94. The network function according to claim 93, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

95. The network function according to claim 93, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

96. The network function according to claim 92, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to receive a registration request from the first RAN or the terminal, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

97. The network function according to claim 96, wherein, The registration request carries the terminal capability identifier and the terminal type. The processor is configured to read the computer program in the memory and further perform the following operations: The mapping relationship between the terminal type and the terminal capability identifier is stored locally in the second capability mapping table and / or the second capability mapping table in the second network function, wherein the second network function includes at least UDM.

98. The network function according to claim 96, wherein, The registration request carries the terminal type of the terminal, and the processor is configured to read the computer program in the memory and further perform the following operations: Based on the terminal type, query the terminal capability identifier associated with the terminal type in the second capability mapping table.

99. The network function according to claim 98, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to send the terminal capability identifier in the context setup response to the first RAN.

100. The network function according to claim 98, wherein, The registration request also carries the terminal capability identifier, and the processor is configured to read the computer program in the memory and further perform the following operations: A terminal capability verification notification is generated based on the query results and the terminal capability identifier. The query results are obtained by querying the second capability mapping table based on the terminal type. The transceiver is controlled to send the terminal capability verification notification to the first RAN.

101. The network function according to claim 100, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to send the terminal capability verification notification along with a context establishment response to the first RAN.

102. The network function according to claim 92, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Under preset conditions, the transceiver is controlled to receive the terminal capability identifier sent by the first RAN. The terminal capability identifier is sent by the terminal to the first RAN in response to a terminal capability request sent by the first RAN.

103. The network function according to claim 102, wherein, Before receiving the terminal capability identifier sent by the first RAN, the processor is configured to read the computer program in the memory and further perform the following operations: Control the transceiver to send the terminal capability request to the first RAN; The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to receive the terminal capability response of the terminal sent by the first RAN, wherein the terminal capability response carries the terminal capability identifier.

104. The network function according to claim 102, wherein, If the registration request carries the terminal type of the terminal, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

105. The network function according to claim 104, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The mapping relationship between the terminal type and the terminal capability identifier is stored in the second capability mapping table.

106. The network function according to claim 92, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive service requests sent by the target terminal, the service requests carrying the service type and service requirements; Based on the service request, a collaborative terminal matching the service type and the service requirements is determined, and / or, a network node matching the service type and the service requirements is determined based on the service request, wherein the collaborative terminal and the network node are respectively used to provide the collaborative service.

107. The network function according to claim 106, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: Control the transceiver to send the service request to the collaborative terminal; If a collaboration confirmation message is received from the collaboration terminal, the transceiver is controlled to send the terminal service provider information of the collaboration terminal to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaboration terminal.

108. The network function according to claim 107, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: If a rejection message is received from the collaborating terminal, other collaborating terminals that match the service type and service requirements will be identified again.

109. The network function according to claim 106, wherein, The processor is configured to read the computer program in the memory and perform the following operations: If no matching collaborative terminal is found according to the service request, the transceiver is controlled to send the service request to a second network node or a central network node, so that the second network node or the central network node can determine the collaborative terminal. The collaborative terminal is a terminal accessing the second RAN, and the first RAN and the second RAN access different network nodes.

110. The network function according to claim 109, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive terminal servicer information of the collaborative terminal sent by the second network node or the central network node; The transceiver is controlled to send the terminal service provider information to the target terminal. The terminal service provider information is used by the target terminal to establish a service session with the collaborating terminal.

111. The network function according to claim 110, wherein, If the terminal service provider information is sent by the central network node, before sending the terminal service provider information to the target terminal, the processor is configured to read the computer program in the memory and further perform the following operations: Control the transceiver to send a cooperative service request to the second network node; The processor is configured to read the computer program in the memory and perform the following operations: If a confirmation and coordination response is received from the second network node, the transceiver is controlled to send the terminal service provider information to the target terminal.

112. A terminal, wherein, Includes memory, transceiver, and processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: The terminal capability identifier of the terminal is reported to the first RAN accessed by the terminal, and / or the terminal capability identifier is reported to the first network function accessed by the terminal. The terminal capability identifier includes a capability field and a collaboration field. The capability field indicates whether the terminal supports the target capability, and the collaboration field indicates whether the terminal supports exposing the target capability to the outside world. If the terminal supports exposing the target capability to the outside world, the terminal can provide collaborative services for the target capability.

113. The terminal according to claim 112, wherein, The capability field includes at least one of the intelligent capability field, the perception capability field, and the computing capability field; The intelligent capability field indicates whether the terminal supports intelligent capabilities, the perception capability field indicates whether the terminal supports perception capabilities, and the computing capability field indicates whether the terminal supports computing capabilities.

114. The terminal according to claim 113, wherein, The intelligent capabilities include at least one of intelligent training capabilities, intelligent reasoning capabilities, and intelligent monitoring capabilities. The sensing capabilities include at least one of signal sensing capabilities, temperature sensing capabilities, humidity sensing capabilities, image sensing capabilities, position sensing capabilities, and speed sensing capabilities. The computing power includes at least one of computing processing power, computing task partitioning power, and computing aggregation power.

115. The terminal according to claim 113, wherein, The capability field also includes a custom field, which is used to indicate whether the terminal supports capabilities other than the intelligent capability, the perception capability, and the computing capability.

116. The terminal according to claim 112, wherein, The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to send a registration request to the first RAN, the registration request carrying at least one of the following: The terminal capability identifier; The terminal type of the terminal is used to obtain the terminal capability identifier.

117. The terminal according to claim 112, wherein, Before reporting the terminal capability identifier of the terminal to the first RAN accessed by the terminal, the processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive a terminal capability request sent by the first RAN, wherein the terminal capability request is sent by the first RAN under preset conditions; The processor is configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to send a terminal capability response to the first RAN, the terminal capability response carrying the terminal capability identifier.

118. The terminal according to claim 117, wherein, If the registration request carries the terminal type of the terminal, the terminal capability request carries the terminal type, and the terminal capability response carries the terminal type.

119. The terminal according to claim 112, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to send a service request to the first RAN or the first network function. The service request carries a service type and service requirements. The service request is used to determine a cooperating terminal and / or network node that matches the service type and service requirements. The cooperating terminal and the network node are respectively used to provide the cooperative service.

120. The terminal according to claim 119, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: The transceiver is controlled to receive terminal servicer information of the cooperative terminal sent by the first RAN or the first network function; A business session is established with the collaborating terminal based on the terminal service provider information.

121. The terminal according to claim 119, wherein, The processor is configured to read the computer program in the memory and further perform the following operations: During the collaborative service process between the terminal and the collaborating terminal, the transceiver is controlled to send the first service processing result to the network node; The first service processing result is used by the network node to perform service processing based on the first service processing result and the second service processing result sent by the collaborative terminal. The first service processing result and the second service processing result carry the same service identifier.

122. The terminal according to claim 119, wherein, Before sending a service request to the first RAN or the first network function, the processor is configured to read the computer program in the memory and further perform the following operations: The business to be processed is divided into business segments to obtain collaborative sub-businesses; The business request is generated based on the business type and business requirements of the collaborative sub-business.

123. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 67.

124. A computer program product comprising a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 67.

Images