Capability registration method and device and storage medium

By realizing the ability registration and reporting of terminals to the network in a 6G network, the problem of inability to register and report in the prior art is solved, ensuring the normal operation of network services and saving signaling overhead.

CN119012338APending Publication Date: 2024-11-22DATANG MOBILE COMM EQUIP CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202310575213.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The lack of capability registration methods in the prior art has resulted in the inability to register and report capabilities in 6G networks, and are unable to provide network services such as data services and AI services.

Method used

Provide a capability registration method, sending registration request messages to the network through a terminal, including registration type, security parameters, capability registration identification, capability type and capability information, realizing capability registration and reporting, saving signaling overhead.

Benefits of technology

It realizes the registration and reporting of capabilities in the 6G network, ensures the normal provision of data services and AI services, and reduces network changes and signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119012338A_ABST
    Figure CN119012338A_ABST
Patent Text Reader

Abstract

The invention provides a capability registration method and device and a storage medium. The capability registration method is applied to the terminal and comprises the following steps: sending a registration request message to a network; the registration request message is used for carrying out capability registration; the registration request message comprises one or more of the following information: a registration type; safety parameters; a capability registration identifier; a capability type; a capability report identifier; and capability information. According to the capability registration method and device and the storage medium provided by the embodiment of the invention, the request message for capability registration is sent to the network equipment by taking the terminal as the capability node, so that capability registration under data service, AI service and multi-network service scenes is realized, and signaling overhead is saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a capability registration method, device and storage medium. Background Art

[0002] The 6th Generation mobile networks (6G) will evolve into a network service platform that provides comprehensive capabilities, providing diverse and operational network services to create value for users. Capabilities need to be registered and reported before they can be provided for use.

[0003] However, there is no method for registering capabilities in the prior art. Therefore, in data service, artificial intelligence (AI) service, and multi-network service scenarios, it is impossible to report capabilities and update capabilities, resulting in an inability to provide corresponding services. Summary of the invention

[0004] The embodiments of the present application provide a capability registration method, device and storage medium to solve the technical problem that the prior art cannot provide 6G corresponding network services.

[0005] In a first aspect, an embodiment of the present application provides a capability registration method, which is applied to a terminal, including:

[0006] Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information:

[0007] Registration type;

[0008] Safety parameters;

[0009] Capability registration identifier;

[0010] Type of capability;

[0011] Capability reporting identifier;

[0012] Capability information.

[0013] In some embodiments, the method further comprises:

[0014] Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration;

[0015] Or also include:

[0016] Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0017] In some embodiments, sending a registration request message to the network includes:

[0018] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0019] In some embodiments, sending a registration request message to the network includes:

[0020] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0021] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0022] In some embodiments, the security parameters include capability authentication data.

[0023] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0024] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0025] In some embodiments, the capability type includes one or more of the following types:

[0026] Data node type;

[0027] AI node type;

[0028] The type of capability that can be called;

[0029] Open capability types.

[0030] In some embodiments, the capability information includes one or more of the following information:

[0031] Data collection capabilities;

[0032] Data pre-processing capabilities;

[0033] Data forwarding capability;

[0034] Data storage capabilities;

[0035] Data analysis skills;

[0036] The protocols supported by the terminal;

[0037] APP supported by the terminal;

[0038] AI models supported by the terminal;

[0039] AI algorithms supported by the terminal.

[0040] In a second aspect, an embodiment of the present application provides a capability registration method, which is applied to a network device, including:

[0041] Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0042] Registration type;

[0043] Safety parameters;

[0044] Capability registration identifier;

[0045] Type of capability;

[0046] Capability reporting identifier;

[0047] Capability information.

[0048] In some embodiments, the method further comprises:

[0049] UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

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

[0051] Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0052] Authentication / security results;

[0053] Capability registration identifier;

[0054] UE location information.

[0055] In some embodiments, sending a registration request message to a capability management function network element includes:

[0056] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0057] In some embodiments, sending a registration request message to a capability management function network element includes:

[0058] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0059] In some embodiments, the method further comprises:

[0060] Send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0061] Authentication / security results;

[0062] Capability reporting identifier;

[0063] UE location information.

[0064] In some embodiments, sending a report request message to a capability management function network element includes:

[0065] In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

[0066] In some embodiments, sending a report request message to a capability management function network element includes:

[0067] In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

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

[0069] Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration;

[0070] Or, also include:

[0071] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0072] In some embodiments, when the registration request message is also used for network registration, the method further includes:

[0073] Perform network authentication and / or security procedures for the UE.

[0074] In a third aspect, an embodiment of the present application provides a capability registration method, which is applied to a capability management function network element, including:

[0075] Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0076] Authentication / security results;

[0077] Capability registration identifier;

[0078] Capability reporting identifier;

[0079] UE location information;

[0080] Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

[0081] In some embodiments, the method further comprises:

[0082] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0083] In a fourth aspect, an embodiment of the present application provides a terminal, including a memory, a transceiver, and a processor;

[0084] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0085] Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information:

[0086] Registration type;

[0087] Safety parameters;

[0088] Capability registration identifier;

[0089] Type of capability;

[0090] Capability reporting identifier;

[0091] Capability information.

[0092] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0093] Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration;

[0094] Or also include:

[0095] Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0096] In some embodiments, sending a registration request message to the network includes:

[0097] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0098] In some embodiments, sending a registration request message to the network includes:

[0099] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0100] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0101] In some embodiments, the security parameters include capability authentication data.

[0102] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0103] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0104] In some embodiments, the capability type includes one or more of the following types:

[0105] Data node type;

[0106] AI node type;

[0107] The type of capability that can be called;

[0108] Open capability types.

[0109] In some embodiments, the capability information includes one or more of the following information:

[0110] Data collection capabilities;

[0111] Data pre-processing capabilities;

[0112] Data forwarding capability;

[0113] Data storage capabilities;

[0114] Data analysis skills;

[0115] The protocols supported by the terminal;

[0116] APP supported by the terminal;

[0117] AI models supported by the terminal;

[0118] AI algorithms supported by the terminal.

[0119] In a fifth aspect, an embodiment of the present application provides a network device, including a memory, a transceiver, and a processor;

[0120] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0121] Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0122] Registration type;

[0123] Safety parameters;

[0124] Capability registration identifier;

[0125] Type of capability;

[0126] Capability reporting identifier;

[0127] Capability information.

[0128] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0129] UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

[0130] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0131] Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0132] Authentication / security results;

[0133] Capability registration identifier;

[0134] UE location information.

[0135] In some embodiments, sending a registration request message to a capability management function network element includes:

[0136] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0137] In some embodiments, sending a registration request message to a capability management function network element includes:

[0138] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0139] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0140] Send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0141] Authentication / security results;

[0142] Capability reporting identifier;

[0143] UE location information.

[0144] In some embodiments, sending a report request message to a capability management function network element includes:

[0145] In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

[0146] In some embodiments, sending a report request message to a capability management function network element includes:

[0147] In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

[0148] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0149] Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration;

[0150] Or, also include:

[0151] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0152] In some embodiments, when the registration request message is also used for network registration, the processor is further used to read the computer program in the memory and perform the following operations:

[0153] Perform network authentication and / or security procedures for the UE.

[0154] In a sixth aspect, an embodiment of the present application provides a capability management function network element, including a memory, a transceiver, and a processor;

[0155] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0156] Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0157] Authentication / security results;

[0158] Capability registration identifier;

[0159] Capability reporting identifier;

[0160] UE location information;

[0161] Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

[0162] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0163] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0164] In a seventh aspect, an embodiment of the present application provides a capability registration device, including:

[0165] The first sending module is used to send a registration request message to the network; the registration request message is used to perform capability registration; the registration request message includes one or more of the following information:

[0166] Registration type;

[0167] Safety parameters;

[0168] Capability registration identifier;

[0169] Type of capability;

[0170] Capability reporting identifier;

[0171] Capability information.

[0172] In some embodiments, it also includes:

[0173] A third acquisition module is used to obtain a registration response message fed back by the network; the registration response message is used to indicate whether the capability registration is successful or failed;

[0174] Or also include:

[0175] The fourth acquisition module is used to obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0176] In some embodiments, the first sending module includes:

[0177] The first sending unit is used to send a registration request message to the capability management function network element when there is only one capability management function network element in the network.

[0178] In some embodiments, the first sending module includes:

[0179] The second sending unit is used to send a registration request message to the capability management function network element corresponding to the capability registration identifier when there are multiple capability management function network elements in the network.

[0180] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0181] In some embodiments, the security parameters include capability authentication data.

[0182] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0183] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0184] In some embodiments, the capability type includes one or more of the following types:

[0185] Data node type;

[0186] AI node type;

[0187] The type of capability that can be called;

[0188] Open capability types.

[0189] In some embodiments, the capability information includes one or more of the following information:

[0190] Data collection capabilities;

[0191] Data pre-processing capabilities;

[0192] Data forwarding capability;

[0193] Data storage capabilities;

[0194] Data analysis skills;

[0195] The protocols supported by the terminal;

[0196] APP supported by the terminal;

[0197] AI models supported by the terminal;

[0198] AI algorithms supported by the terminal.

[0199] In an eighth aspect, an embodiment of the present application provides a capability registration device, including:

[0200] The first acquisition module is used to acquire a registration request message sent by a terminal; the registration request message sent by the terminal is used to perform capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0201] Registration type;

[0202] Safety parameters;

[0203] Capability registration identifier;

[0204] Type of capability;

[0205] Capability reporting identifier;

[0206] Capability information.

[0207] In some embodiments, it also includes:

[0208] The first execution module is used to execute the UE capability authentication and / or security process based on the capability registration identifier and the capability type.

[0209] In some embodiments, it also includes:

[0210] The third sending module is configured to send a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0211] Authentication / security results;

[0212] Capability registration identifier;

[0213] UE location information.

[0214] In some embodiments, the first acquisition module includes:

[0215] The third sending unit is used to send a registration request message to the capability management function network element when there is only one capability management function network element in the network.

[0216] In some embodiments, sending a registration request message to a capability management function network element includes:

[0217] The fourth sending unit is used to send a registration request message to the capability management function network element corresponding to the capability registration identifier when there are multiple capability management function network elements in the network.

[0218] In some embodiments, it also includes:

[0219] The fourth sending module is used to send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0220] Authentication / security results;

[0221] Capability reporting identifier;

[0222] UE location information.

[0223] In some embodiments, the first acquisition module includes:

[0224] The fifth sending unit is used to send a reporting request message to the capability management function network element when there is only one capability management function network element in the network.

[0225] In some embodiments, the first acquisition module includes:

[0226] The sixth sending unit is used to send a reporting request message to the capability management function network element corresponding to the capability reporting identifier when there are multiple capability management function network elements in the network.

[0227] In some embodiments, it also includes:

[0228] A fifth sending module, configured to send a registration response message to the terminal; the registration response message is used to indicate a success or failure of the capability registration;

[0229] Or, also include:

[0230] The sixth sending module is used to send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0231] In some embodiments, when the registration request message is also used for network registration, it further includes:

[0232] The second execution module is used to execute the network authentication and / or security process of the UE.

[0233] In a ninth aspect, an embodiment of the present application provides a capability registration device, including:

[0234] The second acquisition module is used to acquire a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0235] Authentication / security results;

[0236] Capability registration identifier;

[0237] Capability reporting identifier;

[0238] UE location information;

[0239] The second sending module is used to send a registration response message to the terminal; the registration response message is used to indicate whether the capability registration is successful or failed.

[0240] In some embodiments, it also includes:

[0241] The seventh sending module is used to send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0242] In the tenth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the capability registration method described in the first aspect, the second aspect, or the third aspect as described above.

[0243] In the eleventh aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the capability registration method described in the first aspect, the second aspect, or the third aspect as described above.

[0244] In the twelfth aspect, an embodiment of the present application further provides a communication device-readable storage medium, wherein the communication device-readable storage medium stores a computer program, and the computer program is used to enable the communication device to execute the capability registration method described in the first aspect, the second aspect, or the third aspect as described above.

[0245] In the thirteenth aspect, an embodiment of the present application further provides a chip product readable storage medium, wherein the chip product readable storage medium stores a computer program, and the computer program is used to enable the chip product to execute the capability registration method described in the first aspect, the second aspect, or the third aspect as described above.

[0246] The capability registration method, device and storage medium provided in the embodiments of the present application use the UE as a capability node to send a registration request message for capability registration to the network, wherein the registration request message includes one or more of the following information: registration type, security parameters, capability registration identifier, capability type, capability reporting identifier, and capability information, thereby realizing capability registration with the UE as a capability node, and further realizing capability reporting and capability updating, with little change to the network, saving signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0247] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0248] Figure 1 This is one of the flow charts of the capability registration method provided in the embodiment of the present application;

[0249] Figure 2 It is one of the signaling interaction diagrams of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0250] Figure 3 This is the second signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0251] Figure 4 This is the third signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0252] Figure 5 This is the fourth signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0253] Figure 6 This is the fifth signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0254] Figure 7 This is the sixth signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0255] Figure 8 This is the seventh signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application;

[0256] Fig. 9 This is the second flowchart of the capability registration method provided in the embodiment of the present application;

[0257] Fig.10 This is the third flow chart of the capability registration method provided in the embodiment of the present application;

[0258] Fig.11 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0259] Fig.12 It is a structural diagram of a network device provided in an embodiment of the present application;

[0260] Fig.13 It is a structural diagram of a capability management function network element provided in an embodiment of the present application;

[0261] Fig.14 This is one of the structural diagrams of a capability registration device provided in an embodiment of the present application;

[0262] Fig.15 This is the second structural diagram of a capability registration device provided in an embodiment of the present application;

[0263] Fig.16 This is the third structural diagram of a capability registration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0264] The data carried by 6G networks include data generated and consumed by 6G network users and terminal devices, network equipment and functions, infrastructure such as cloud platforms, as well as algorithms and applications.

[0265] The data plane architecture of the 6G mobile communication network mainly consists of four functional parts: Data Orchestrator (DO) (or Data Controller (DC)), Data Agent (DA), Trust Anchor Agent (TAA) and Data Storage Function (DSF). DO supports programmable data pipelines and implements data service request conversion, and builds data pipelines based on data service requests. DA can be built into network function elements or terminals, or it can be deployed independently to perform data collection, data preprocessing, data storage, data analysis, data sharing and other data services orchestrated in the data pipeline. DA can implement a variety of data processing functions, which are reported to DO or DC as DA capabilities during DA registration, and capability updates can be reported in a timely manner.

[0266] In the prior art, since there is no registration method for data service capabilities, AI capabilities, network callable capabilities, etc., the capabilities cannot be reported, and thus network services such as services and AI services cannot be provided.

[0267] Based on the above technical problems, an embodiment of the present application proposes a capability registration method, by which a terminal sends a request message for capability registration to a network device as a capability node, and the request message includes one or more of the following information: registration type, security parameters, capability registration identifier, capability type, capability reporting identifier, and capability information. Capability registration with the UE as the capability node is realized, and capability reporting and capability update are further realized, with little change to the network, saving signaling overhead.

[0268] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0269] Figure 1This is one of the flow charts of the capability registration method provided in the embodiment of the present application, such as Figure 1 As shown, the embodiment of the present application provides a capability registration method, the execution subject of which may be a terminal / user equipment (UE), such as a mobile phone. The method includes:

[0270] Step 101: Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information:

[0271] Registration type;

[0272] Safety parameters;

[0273] Capability registration identifier;

[0274] Type of capability;

[0275] Capability reporting identifier;

[0276] Capability information.

[0277] Specifically, the terminal performs capability registration as a capability node, that is, the terminal sends a registration request message for capability registration to the network device; the network device obtains the registration request message sent by the terminal and performs capability registration according to the information contained in the registration request message. The registration request message is a Non-Access Stratum (NAS) message.

[0278] In an embodiment of the present application, the network device may be a radio access network (Radio Access Network, RAN), an access and mobility management function (Access and Mobility Management Function, AMF) network element, an authentication / security management function network element and / or a capability management function network element, etc.

[0279] Optionally, the UE may register and report capabilities at the same time, or may first register capabilities and then report capabilities.

[0280] For example, the terminal sends a registration request message to the network device, and the registration request message includes the registration type, security parameters, capability registration identifier, capability type and UE identifier, etc. After the network device obtains the registration request message, it sends a capability registration request message to the corresponding capability management function network element based on the capability registration identifier and capability type in the registration request message, and the capability registration request message carries information such as capability registration identifier and UE location information. After the capability management function network element successfully registers, the terminal obtains a registration response message, thereby knowing that the capability registration is successful.

[0281] After the capability registration is successful, the terminal sends a registration request message to the network device, and the registration request message includes the registration type, capability reporting identifier, capability type, capability information and UE identifier, etc. After the network device obtains the registration request message, it sends a capability reporting request message to the corresponding capability management function network element based on the capability reporting identifier and capability type in the registration request message. The capability reporting request message carries the information in the registration request message and UE location information, etc. After the report is successful, the network sends a registration acceptance message to the terminal.

[0282] For another example, the terminal sends a registration request message to the network device, and the registration request message includes a registration type, security parameters, a capability registration identifier, a capability reporting identifier, a capability type, capability information, and a UE identifier, etc. After the network device obtains the registration request message, it initiates a capability registration request and a capability reporting request to the corresponding capability management function network element based on the capability registration identifier, capability reporting identifier, and capability type in the registration request message. The request message sent by the network device to the capability management function network element carries information such as the capability registration identifier, capability type, capability information, and UE location information, and then sends a response message to the terminal to indicate that the capability registration and reporting are successful.

[0283] Optionally, the UE may perform network registration and capability registration simultaneously or at different times, for example, perform capability registration while performing network registration, or perform network registration first and then capability registration, or perform capability registration first and then network registration.

[0284] The capability registration method provided in the embodiment of the present application uses the UE as a capability node to register and report capabilities. The network registers and reports capabilities simultaneously or sequentially according to the parameters contained in the registration request message sent by the UE, thereby realizing capability registration in network service scenarios such as data services and AI services, and saving signaling overhead.

[0285] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0286] Specifically, when the UE performs network registration and capability registration at the same time, the registration type in the registration request message sent to the network is the initial registration type; after the UE has performed network registration and / or capability registration, the registration type contained in the registration request message sent to the network is a mobile registration update, including a UE capability update type.

[0287] For example, the UE performs network registration, capability registration and reporting at the same time, and the registration type in the registration request message sent to the network is the initial registration type.

[0288] For another example, the UE performs network registration and capability registration at the same time, and the registration type in the registration request message sent to the network is the initial registration type; then when the UE reports the capability, the registration type in the registration request message sent to the network is the UE capability update type.

[0289] For another example, the UE has registered with the network. When the UE performs capability registration and capability reporting, the registration type in the registration request message sent by the UE to the network is a mobile registration update or a UE capability update type.

[0290] In some embodiments, the security parameters include capability authentication data.

[0291] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0292] Specifically, the network device receives the registration request message and can learn that a capability registration operation needs to be performed according to the capability registration identifier in the registration request message. In the case where there are multiple capability management function network elements in the network, the capability registration identifier can also be used to determine the capability management function network element corresponding to the capability registration identifier, so that the capability of the type corresponding to the capability registration identifier can be successfully registered.

[0293] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0294] Specifically, the network device receives a registration request message and can learn that a capability reporting operation needs to be performed based on the capability registration identifier in the registration request message. In the case where there are multiple capability management function network elements in the network, the capability reporting identifier can also be used to determine the capability management function network element corresponding to the capability reporting identifier, so that the capability of the type corresponding to the capability reporting identifier can be successfully reported.

[0295] In some embodiments, the capability type includes one or more of the following types:

[0296] Data node type;

[0297] AI node type;

[0298] The type of capability that can be called;

[0299] Open capability types.

[0300] Specifically, in the capability registration process, the capability types included in the registration request message sent by the terminal include: data node type, AI node type and / or open capability type and other capability types. In the capability reporting process, the capability types included in the registration request message sent by the terminal include: data node type, AI node type and / or callable capability type and other capability types.

[0301] In some embodiments, the capability information includes one or more of the following information:

[0302] Data collection capabilities;

[0303] Data pre-processing capabilities;

[0304] Data forwarding capability;

[0305] Data storage capabilities;

[0306] Data analysis skills;

[0307] The protocols supported by the terminal;

[0308] APP supported by the terminal;

[0309] AI models supported by the terminal;

[0310] AI algorithms supported by the terminal.

[0311] In some embodiments, the method further comprises:

[0312] Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration;

[0313] Or also include:

[0314] Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0315] Specifically, after sending a registration request message to the network, the terminal also obtains a registration response message and / or a reporting response message fed back by the network. The registration response message is used to indicate the success or failure of capability registration. The reporting response message is used to indicate the success or failure of capability reporting.

[0316] For example, after a network device such as AMF sends a registration request message to a capability management function network element for capability registration, it sends a registration response message to the terminal, where the registration response message is used to indicate the success or failure of the capability registration, and the terminal receives the registration response message fed back by the AMF.

[0317] For another example, after a network device such as AMF sends a reporting request message to the capability management function network element for capability registration, it sends a reporting response message to the terminal, where the reporting response message is used to indicate the success or failure of the capability reporting, and the terminal receives the reporting response message fed back by the AMF.

[0318] For another example, the capability management function network element receives a registration request message sent by the network device, registers the capability based on the information therein, and then sends a registration response message to the terminal to indicate whether the capability registration succeeds or fails. The terminal receives the registration response message.

[0319] For another example, the capability management function network element receives a report request message sent by the network device, reports the capability based on the information therein, and then sends a report response message to the terminal to indicate the success or failure of the capability report, and the terminal receives the report response message.

[0320] For another example, the capability management function network element receives a registration request message sent by a network device, registers the capability based on the information therein, and then sends a registration response message to a network device such as AMF. The AMF then sends a registration response message to the terminal to indicate whether the capability registration is successful or failed, and the terminal receives the registration response message.

[0321] For another example, the capability management function network element receives a reporting request message sent by a network device, reports the capability based on the information therein, and then sends a reporting response message to a network device such as AMF. The AMF then sends a reporting response message to the terminal to indicate the success or failure of the capability reporting, and the terminal receives the reporting response message.

[0322] The capability registration method provided in the embodiment of the present application determines the success or failure of capability registration through a registration response message fed back by the network, and determines the success or failure of capability reporting through a reporting response message fed back by the network, thereby realizing capability registration and reporting with the UE as the capability node.

[0323] In some embodiments, sending a registration request message to the network includes:

[0324] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0325] Specifically, when there is only one capability management function network element in the network, the terminal sends a registration request message to the capability management function network element.

[0326] In some embodiments, when there is only one capability management function network element in the network, the terminal sends a registration request message to a network device such as RAN or AMF, and then the network device sends a registration request message and / or a reporting request message to the capability management function network element based on the information contained in the registration request message.

[0327] In some embodiments, the registration request message sent to the capability management function network element includes one or more of the following information: authentication / security result, capability registration identifier, and UE location information.

[0328] In some embodiments, the reporting request message sent to the capability management function network element includes one or more of the following information: authentication / security result, capability reporting identifier, and UE location information.

[0329] For example, when there is only one capability management function network element in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability registration identifier. The network device sends a registration request message to the capability management function network element according to the capability registration identifier, and the registration request message sent to the capability management function network element includes information such as authentication / security results, capability registration identifier and / or UE location information.

[0330] For another example, when there is only one capability management function network element in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability reporting identifier. The network device sends a reporting request message to the capability management function network element according to the capability reporting identifier, and the reporting request message sent to the capability management function network element includes information such as authentication / security results, capability reporting identifier and / or UE location information.

[0331] For another example, when there is only one capability management function network element in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability registration identifier and a capability reporting identifier. The network device sends a registration and reporting request message to the capability management function network element according to the capability registration identifier and the capability reporting identifier, and the registration request message sent to the capability management function network element includes information such as authentication / security results, capability registration identifier, capability reporting identifier and / or UE location information.

[0332] In some embodiments, sending a registration request message to the network includes:

[0333] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0334] Specifically, when there are multiple capability management function network elements in the network, the terminal sends a registration request message to the capability management function network element corresponding to the capability registration identifier.

[0335] In some embodiments, when there are multiple capability management function network elements in the network, the terminal sends a registration request message to a network device such as RAN or AMF, and then the network device determines the corresponding capability management function network element based on the capability registration identifier (and / or capability type) contained in the registration request message, that is, determines the capability management function network element that can register the capability type indicated by the capability registration identifier (and / or capability type), and sends a registration request message to the capability management function network element.

[0336] Optionally, when reporting capabilities or simultaneously registering and reporting capabilities, since the registration request message includes a capability reporting identifier, the terminal may also send a registration request message and / or a reporting request message to the capability management function network element corresponding to the capability reporting identifier.

[0337] For example, when there are multiple capability management function network elements in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability registration identifier. The network device determines that a capability registration operation is to be performed according to the capability registration identifier, and sends a registration request message to the capability management function network element corresponding to the capability registration identifier, and the registration request message sent to the capability management function network element includes information such as authentication / security results, capability registration identifier and / or UE location information.

[0338] For another example, when there are multiple capability management function network elements in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability reporting identifier. The network device determines to perform a capability reporting operation according to the capability reporting identifier, and sends a reporting request message to the capability management function network element corresponding to the capability reporting identifier, and the reporting request message sent to the capability management function network element includes information such as authentication / security results, capability reporting identifier and / or UE location information.

[0339] For another example, when there are multiple capability management function network elements in the network, the terminal sends a registration request message to the network device, and the registration request message includes a capability registration identifier and a capability reporting identifier. The network device determines that capability registration and reporting operations are to be performed according to the capability registration identifier and the capability reporting identifier, and sends a registration (and reporting) request message to the capability management function network element corresponding to the capability registration identifier, and the registration request message sent to the capability management function network element includes information such as authentication / security results, capability registration identifier, capability reporting identifier and / or UE location information.

[0340] The capability registration method provided in the embodiment of the present application determines the corresponding capability management function network element based on the capability registration identifier, so that the capability registration can be quickly completed based on the capability management function network element, thereby improving the efficiency of capability registration.

[0341] In some embodiments, after acquiring the registration request message sent by the terminal, the network device further performs a capability authentication and / or security process of the UE based on the capability registration identifier and capability type included in the registration request message.

[0342] Specifically, after receiving the registration request message, the network device needs to first perform capability authentication and / or security process on the UE. After the authentication is successful, the network performs capability registration based on the information included in the registration request message.

[0343] For example, the terminal sends a registration request message to the network device, and the registration request message includes the registration type, security parameters, capability registration identifier, capability type and UE identifier, etc. The network device performs the UE capability authentication and / or security process based on the capability registration identifier and capability type. After successful authentication, the network device sends the authentication / security result, capability registration identifier and UE location information to the capability management function network element for capability registration. When the registration is completed and the capability reporting request is initiated, since the capability authentication and / or security process has been passed before the capability registration, there is no need to perform capability authentication and / or security process on the UE at this time. The network device directly performs the capability reporting process based on the capability reporting identifier and capability type in the registration request message sent by the UE.

[0344] For another example, the terminal sends a registration request message to the network device, and the registration request message includes a registration type, a security parameter, a capability registration identifier, a capability reporting identifier, a capability type, capability information, and a UE identifier. The network device performs a capability authentication and / or security process for the UE based on the capability registration identifier and the capability type. After successful authentication, the network device sends information such as the authentication / security result, the capability registration identifier, the capability reporting identifier, the capability type, the capability information, and the UE location information to the capability management function network element for capability registration and reporting.

[0345] In some embodiments, when the UE has been registered with the network, after the network device receives the registration request message sent by the UE, the network device can perform a capability authentication / security process on the UE based on the capability registration identifier and capability type; the network device can also send the UE's registration request message to the corresponding capability management function network element based on the capability registration identifier and capability type, and the capability management function network element will perform the UE authentication process.

[0346] For example, the UE has registered with the network. When the UE initiates a registration request, the AMF receives the registration request message sent by the UE, and the AMF performs a capability authentication / security process on the UE based on the capability registration identifier and capability type.

[0347] For another example, the UE has registered with the network. When the UE initiates a registration request, the AMF receives the registration request message sent by the UE, and sends the registration request message to the corresponding capability management function network element based on the capability registration identifier and capability type in the registration request message. The capability management function network element performs capability authentication / security process on the UE.

[0348] In the capability registration method provided in the embodiment of the present application, the network device also performs the capability authentication and / or security process of the UE based on the capability registration identifier and capability type, thereby realizing the authorization of the legal UE and providing guarantee for capability registration and capability reporting. When the UE has registered with the network, the capability authentication of the UE can be performed by the AMF or by the capability management function network element, which can be flexibly applied according to actual needs.

[0349] The capability registration method provided in the above embodiment is further described below through a specific example:

[0350] Example 1:

[0351] The UE registers its capabilities while registering the network. After completing the capability registration, the UE reports its capabilities.

[0352] Figure 2 is one of the signaling interaction diagrams of the schematic scenario of the capability registration method provided in the embodiment of the present application, such as Figure 2 As shown, the terminal first registers the capability. The specific steps of capability registration are as follows:

[0353] Step 1: UE initiates a registration request, and the registration request message (NAS message) includes registration type, UE identifier, security parameters, capability registration identifier, capability type, etc. Among them, the security parameters may include capability authentication data; the capability registration identifier refers to a certain type / multiple types of capability registration indications; the capability type refers to the specific capability type to be registered, such as data node type, AI node type, open capability type, etc. The registration type refers to the initial registration type.

[0354] Step 2: After receiving the registration request from the UE, the network performs the UE authentication / security process, which also includes the authentication / security process of the UE capability based on the capability registration identifier and capability type.

[0355] Step 3: After successful authentication, the network makes a capability registration request to the corresponding capability management function network element based on the capability registration identifier and capability type. The request message carries information such as authentication / security results, capability registration identifier, and UE location information. There may be multiple different capability management function network elements in the network or only one comprehensive capability management function network element. If there are multiple different capability management function network elements, the access mobility management function network element sends capability registration requests to the corresponding capability management function network element based on the capability registration identifier. After successful registration, a response message is sent.

[0356] Step 4: The network performs other registration processes.

[0357] Figure 3 This is the second signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application, such as Figure 3 As shown, the specific steps for the terminal to report capabilities after completing the above capability registration process are as follows:

[0358] Step 1. The UE initiates a registration request. The registration request message (NAS message) includes the registration type, UE identifier, capability reporting identifier, capability type, capability information, etc. Among them, the capability reporting identifier refers to a certain type / multiple types of capability reporting indications; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc.; capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, etc., and also includes callable capabilities, such as supported protocols, supported applications (Application, APP), supported AI models or algorithms, etc.; the registration type refers to mobile registration update (UE capability update type).

[0359] Step 2: After receiving the registration request from the UE, the network sends a capability reporting request to the corresponding capability management function network element based on the capability reporting identifier and capability type. The request message carries the information in the registration request and UE location information. If there are multiple different capability management function network elements in the network, the access mobility management function network element sends capability reporting requests to the corresponding capability management function network element based on the capability reporting identifier and capability type. After the report is successful, a response message is sent.

[0360] Step 3: After the capability is successfully reported, the network sends a registration acceptance message to the UE.

[0361] Example 2:

[0362] Figure 4 FIG. 3 is a signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present application, such as Figure 4 As shown, the UE registers the capability while performing network registration, and the registration and capability reporting are performed together.

[0363] Step 1. The UE initiates a registration request. The registration request message (NAS message) includes the registration type, UE identifier, security parameters, capability registration identifier, capability reporting identifier, capability type, capability information, etc. Among them, the security parameters may include capability authentication data, the capability reporting identifier refers to a certain type / multiple types of capability reporting instructions; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc.; capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, etc., and also includes callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, etc.; the registration type refers to the initial registration type.

[0364] Step 2: After receiving the registration request from the UE, the network performs the UE authentication / security process, which also includes the authentication / security process of the UE capability based on the capability registration identifier and capability type.

[0365] Step 3: After successful authentication, the network makes a capability registration and capability reporting request to the corresponding capability management function network element based on the capability registration identifier and capability type. The request message carries information such as authentication / security result, capability registration identifier, capability reporting identifier, capability type, capability information, and UE location information. If there are multiple different capability management function network elements in the network, the access mobility management function network element sends capability registration requests to the corresponding capability management function network element based on the capability registration identifier. After successful registration, a response message is sent.

[0366] Step 4: The network performs other registration processes.

[0367] Example 3:

[0368] After the UE registers with the network, it registers and reports its capabilities.

[0369] Figure 5 FIG4 is a fourth signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present application, such as Figure 5 As shown, when the UE has registered with the network, the specific steps for the UE to register capabilities are as follows:

[0370] Step 1: UE initiates a registration request, and the registration request message (NAS message) includes registration type, UE identifier, security parameters, capability registration identifier, capability type, etc. The security parameters include capability authentication data, capability reporting identifier refers to a certain type / multiple types of capability reporting indications; capability type refers to the capability to be reported, such as data node type, callable capability type, etc.; registration type refers to mobile registration update (UE capability update type).

[0371] Step 2: The access mobility management function network element performs the authentication / security process of the UE capability based on the capability registration identifier and capability type. Alternatively, the UE registration request message is sent to the corresponding capability management function network element based on the capability registration identifier and capability type, and the capability management function network element performs the UE authentication process.

[0372] Step 3: After successful authentication, the network sends a capability registration request to the corresponding capability management function network element based on the capability registration identifier and capability type. The request message carries information such as authentication / security results, capability registration identifier, and UE location information. If the network has multiple different capability management functions, the access mobility management function network element sends capability registration requests to the corresponding capability management function network element based on the capability registration identifier. After successful registration, a response message is sent.

[0373] Step 4: The network performs other registration processes.

[0374] Figure 6 FIG5 is a fifth signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present application, such as Figure 6 As shown in the figure, after the capability registration is completed, the capability can be reported. The specific steps for capability reporting are as follows:

[0375] Step 1. The UE initiates a registration request. The registration request message (NAS message) includes the registration type, UE identifier, capability reporting identifier, capability type, capability information, etc. The capability reporting identifier refers to a certain type / multiple types of capability reporting indications; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc. Capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, etc., and also includes callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, etc.; the registration type refers to mobile registration update (UE capability update type).

[0376] Step 2: After receiving the registration request from the UE, the network sends a capability reporting request to the corresponding capability management function based on the capability reporting identifier and capability type. The request message carries the information in the registration request and UE location information. If there are multiple different capability management functions in the network, the access mobility management function sends capability reporting requests to the corresponding capability management functions based on the capability reporting identifier and capability type. After the report is successful, a response message is sent.

[0377] Step 3: After the capability is successfully reported, the network sends a registration acceptance message to the UE.

[0378] Example 4:

[0379] Figure 7 This is the sixth signaling interaction diagram of the schematic scenario of the capability registration method provided in the embodiment of the present application, such as Figure 7 As shown, the UE has registered with the network. The specific steps for the UE to register and report capabilities are as follows:

[0380] Step 1. The UE initiates a registration request. The registration request message (NAS message) includes the registration type, UE identifier, security parameters, capability registration identifier, capability reporting identifier, capability type, capability information, etc. The security parameters include capability authentication data, the capability reporting identifier refers to a certain type / multiple types of capability reporting indications; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc.; capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, etc., and also includes callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, etc.; the registration type refers to mobile registration update (UE capability update type).

[0381] Step 2: The access mobility management function network element performs the authentication / security process of the UE capability based on the capability registration identifier and capability type. Alternatively, the UE registration request message is sent to the corresponding capability management function based on the capability registration identifier and capability type, and the capability management function performs the UE authentication process.

[0382] Step 3: After successful authentication, the network makes a capability registration and capability reporting request to the corresponding capability management function network element based on the capability registration identifier and capability type. The request message carries information such as authentication / security result, capability registration identifier, capability reporting identifier, capability type, capability information, and UE location information. If there are multiple different capability management functions in the network, the access mobility management function network element sends capability registration requests to the corresponding capability management function network element based on the capability registration identifier. After successful registration, a response message is sent.

[0383] Step 4: The network performs other registration processes.

[0384] Example 5:

[0385] Figure 8 FIG. 7 is a signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present application, such as Figure 8 As shown, when the UE has registered with the network, the process of the UE updating the capability is similar to the process of reporting the capability. The specific steps of the UE updating the capability are as follows:

[0386] Step 1. The UE initiates a registration request. The registration request message (NAS message) includes the registration type, UE identifier, capability reporting identifier, capability type, capability information, etc. The capability reporting identifier refers to a certain type / multiple types of capability reporting indications; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc. Capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, etc., and also includes callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, etc.; the registration type refers to mobile registration update (UE capability update type).

[0387] Step 2: After the network receives the registration request from the UE, it makes a capability update request to the corresponding capability management function network element based on the capability reporting identifier and capability type. The request message carries the information in the registration request and the UE location information. Here, there may be multiple different capability management function network elements or a comprehensive capability management function network element in the network. If there are multiple different capability management function network elements, the access mobility management function network element sends capability reporting requests to the corresponding capability management function network element based on the capability reporting identifier and capability type. After the report is successful, a response message is sent.

[0388] Step 3: After the capability update is successful, the network sends a registration acceptance message to the UE.

[0389] The capability registration method provided in the embodiment of the present application uses the UE as a capability node to send a registration request message for capability registration to the network, and the registration request message includes one or more of the following information: registration type, security parameters, capability registration identifier, capability type, capability reporting identifier, and capability information, thereby realizing capability registration with the UE as the capability node, and further realizing capability reporting and capability updating, with little change to the network, saving signaling overhead.

[0390] In some embodiments, if the RAN can interact directly with the authentication function and the capability management function, when the UE needs to register and report capabilities, the capability registration and reporting related parameters can be placed in the AN parameters, and the RAN will register, authenticate and report capabilities to the capability management function.

[0391] In some embodiments, when the registration request message is also used for network registration, the network device also needs to perform network authentication and / or security procedures for the UE.

[0392] Specifically, when network registration and capability registration are performed simultaneously, after the network device receives the registration request message sent by the terminal, in addition to executing the UE's capability authentication and / or security process, it also needs to execute the UE's network authentication and / or security process.

[0393] In some embodiments, when the UE is in the process of capability registration and reporting, if the UE has performed an authentication / security process when registering with the network and the authentication is successful, there is no need to perform an authentication / security process on the relevant capabilities of the UE.

[0394] Alternatively, when the UE needs to register with the network and also register its capabilities, an authentication / security process may be performed only on whether the UE can register with the network.

[0395] The capability registration method provided in the embodiment of the present application can eliminate the need to perform capability authentication and / or security procedures on UEs that have already registered with the network, thereby simplifying the signaling process and improving the efficiency of capability registration and reporting.

[0396] In some embodiments, if the UE has successfully registered with the network and does not need to perform the authentication / security process of the capability, and the RAN can directly access the capability management function, when the UE needs to register and report the capability, the capability registration and reporting related parameters can be placed in the AN parameters, and the RAN will register, authenticate and report the capability to the capability management function.

[0397] The capability registration method provided in the embodiment of the present application is that when the authentication / security function network element can directly interact with the management function network element, the RAN sends a registration request message to the capability management function network element to perform capability registration, etc. On the basis of the original network architecture, a variety of network devices are provided to perform capability registration so as to be flexibly applied to various scenarios.

[0398] Fig. 9 This is a second flow chart of the capability registration method provided in the embodiment of the present application, such as Fig. 9 As shown, the embodiment of the present application provides a capability registration method, the execution subject of which can be a network device, for example, a radio access network (Radio Access Network, RAN), an access and mobility management function (Access and Mobility Management Function, AMF) network element, an authentication / security management function network element and / or a capability management function network element. The method includes:

[0399] Step 901: Acquire a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0400] Registration type;

[0401] Safety parameters;

[0402] Capability registration identifier;

[0403] Type of capability;

[0404] Capability reporting identifier;

[0405] Capability information.

[0406] In some embodiments, the method further comprises:

[0407] UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

[0408] In some embodiments, the method further comprises:

[0409] Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0410] Authentication / security results;

[0411] Capability registration identifier;

[0412] UE location information.

[0413] In some embodiments, sending a registration request message to a capability management function network element includes:

[0414] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0415] In some embodiments, sending a registration request message to a capability management function network element includes:

[0416] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0417] In some embodiments, the method further comprises:

[0418] Send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0419] Authentication / security results;

[0420] Capability reporting identifier;

[0421] UE location information.

[0422] In some embodiments, sending a report request message to a capability management function network element includes:

[0423] In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

[0424] In some embodiments, sending a report request message to a capability management function network element includes:

[0425] In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

[0426] In some embodiments, the method further comprises:

[0427] Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration;

[0428] Or, also include:

[0429] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0430] In some embodiments, when the registration request message is also used for network registration, the method further includes:

[0431] Perform network authentication and / or security procedures for the UE.

[0432] Specifically, the capability registration method provided in the embodiment of the present application can refer to the above-mentioned capability registration method embodiment in which the execution subject is a terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the above-mentioned corresponding method embodiments will not be described in detail here.

[0433] Fig.10 This is the third flow chart of the capability registration method provided in the embodiment of the present application, such as Fig.10 As shown, the embodiment of the present application provides a capability registration method, and the execution subject may be a capability management function network element. The method includes:

[0434] Step 1001: Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0435] Authentication / security results;

[0436] Capability registration identifier;

[0437] Capability reporting identifier;

[0438] UE location information;

[0439] Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

[0440] In some embodiments, the method further comprises:

[0441] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0442] Specifically, the capability registration method provided in the embodiment of the present application can refer to the above-mentioned capability registration method embodiment in which the execution subject is a terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the above-mentioned corresponding method embodiments will not be described in detail here.

[0443] Fig.11 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application, such as Fig.11 As shown, the terminal includes a memory 1103, a transceiver 1101, and a processor 1102, wherein:

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

[0445] Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information:

[0446] Registration type;

[0447] Safety parameters;

[0448] Capability registration identifier;

[0449] Type of capability;

[0450] Capability reporting identifier;

[0451] Capability information.

[0452] Specifically, the transceiver 1101 is used to receive and send data under the control of the processor 1102 .

[0453] Among them, Fig.11In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1102 and various circuits of memory represented by memory 1103 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1101 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media. For different user devices, the user interface 1104 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0454] The processor 1102 is responsible for managing the bus architecture and general processing, and the memory 1103 can store data used by the processor 1102 when performing operations.

[0455] In some embodiments, the processor 1102 may 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), and the processor may also adopt a multi-core architecture.

[0456] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0457] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0458] Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration;

[0459] Or also include:

[0460] Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0461] In some embodiments, sending a registration request message to the network includes:

[0462] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0463] In some embodiments, sending a registration request message to the network includes:

[0464] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0465] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0466] In some embodiments, the security parameters include capability authentication data.

[0467] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0468] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0469] In some embodiments, the capability type includes one or more of the following types:

[0470] Data node type;

[0471] AI node type;

[0472] The type of capability that can be called;

[0473] Open capability types.

[0474] In some embodiments, the capability information includes one or more of the following information:

[0475] Data collection capabilities;

[0476] Data pre-processing capabilities;

[0477] Data forwarding capability;

[0478] Data storage capabilities;

[0479] Data analysis skills;

[0480] The protocols supported by the terminal;

[0481] APP supported by the terminal;

[0482] AI models supported by the terminal;

[0483] AI algorithms supported by the terminal.

[0484] It should be noted here that the above-mentioned terminal provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the above-mentioned execution subject is the terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0485] Fig.12 is a schematic diagram of the structure of a network device provided in an embodiment of the present application, such as Fig.12 As shown, the network device includes a memory 1203, a transceiver 1201, and a processor 1202, wherein:

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

[0487] Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0488] Registration type;

[0489] Safety parameters;

[0490] Capability registration identifier;

[0491] Type of capability;

[0492] Capability reporting identifier;

[0493] Capability information.

[0494] Specifically, the transceiver 1201 is used to receive and send data under the control of the processor 1202 .

[0495] Among them, Fig.12 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1202 and memory represented by memory 1203. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1201 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 1202 is responsible for managing the bus architecture and general processing, and the memory 1203 may store data used by the processor 1202 when performing operations.

[0496] The processor 1202 may 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 may also adopt a multi-core architecture.

[0497] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0498] UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

[0499] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0500] Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0501] Authentication / security results;

[0502] Capability registration identifier;

[0503] UE location information.

[0504] In some embodiments, sending a registration request message to a capability management function network element includes:

[0505] In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

[0506] In some embodiments, sending a registration request message to a capability management function network element includes:

[0507] In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

[0508] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0509] Send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0510] Authentication / security results;

[0511] Capability reporting identifier;

[0512] UE location information.

[0513] In some embodiments, sending a report request message to a capability management function network element includes:

[0514] In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

[0515] In some embodiments, sending a report request message to a capability management function network element includes:

[0516] In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

[0517] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0518] Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration;

[0519] Or, also include:

[0520] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0521] In some embodiments, when the registration request message is also used for network registration, the processor is further used to read the computer program in the memory and perform the following operations:

[0522] Perform network authentication and / or security procedures for the UE.

[0523] Specifically, the above-mentioned network device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the network device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0524] Fig.13 is a schematic diagram of the structure of a capability management function network element provided in an embodiment of the present application, such as Fig.13 As shown, the capability management function network element includes a memory 1303, a transceiver 1301, and a processor 1302, wherein:

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

[0526] Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0527] Authentication / security results;

[0528] Capability registration identifier;

[0529] Capability reporting identifier;

[0530] UE location information;

[0531] Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

[0532] Specifically, the transceiver 1301 is used to receive and send data under the control of the processor 1302 .

[0533] Among them, Fig.13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1302 and various circuits of memory represented by memory 1303 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1301 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 1302 is responsible for managing the bus architecture and general processing, and the memory 1303 may store data used by the processor 1302 when performing operations.

[0534] The processor 1302 may 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 may also adopt a multi-core architecture.

[0535] In some embodiments, the processor is further configured to read the computer program in the memory and perform the following operations:

[0536] Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0537] Specifically, the capability management function network element provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the capability management function network element, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0538] Fig.14 This is one of the structural diagrams of a capability registration device provided in an embodiment of the present application, such as Fig.14 As shown, the embodiment of the present application provides a capability registration device, including a first sending module 1401, wherein:

[0539] The first sending module 1401 is used to send a registration request message to the network; the registration request message is used to perform capability registration; the registration request message includes one or more of the following information:

[0540] Registration type;

[0541] Safety parameters;

[0542] Capability registration identifier;

[0543] Type of capability;

[0544] Capability reporting identifier;

[0545] Capability information.

[0546] In some embodiments, it also includes:

[0547] A third acquisition module is used to obtain a registration response message fed back by the network; the registration response message is used to indicate whether the capability registration is successful or failed;

[0548] Or also include:

[0549] The fourth acquisition module is used to obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

[0550] In some embodiments, the first sending module includes:

[0551] The first sending unit is used to send a registration request message to the capability management function network element when there is only one capability management function network element in the network.

[0552] In some embodiments, the first sending module includes:

[0553] The second sending unit is used to send a registration request message to the capability management function network element corresponding to the capability registration identifier when there are multiple capability management function network elements in the network.

[0554] In some embodiments, the registration type includes an initial registration type and a mobile registration update.

[0555] In some embodiments, the security parameters include capability authentication data.

[0556] In some embodiments, the capability registration identifier is used to represent one or more capability registration indications.

[0557] In some embodiments, the capability reporting identifier is used to represent one or more capability reporting indications.

[0558] In some embodiments, the capability type includes one or more of the following types:

[0559] Data node type;

[0560] AI node type;

[0561] The type of capability that can be called;

[0562] Open capability types.

[0563] In some embodiments, the capability information includes one or more of the following information:

[0564] Data collection capabilities;

[0565] Data pre-processing capabilities;

[0566] Data forwarding capability;

[0567] Data storage capabilities;

[0568] Data analysis skills;

[0569] The protocols supported by the terminal;

[0570] APP supported by the terminal;

[0571] AI models supported by the terminal;

[0572] AI algorithms supported by the terminal.

[0573] Specifically, the capability registration device provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment in which the execution subject is a terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0574] Fig.15 This is a second structural diagram of a capability registration device provided in an embodiment of the present application, such as Fig.15 As shown, an embodiment of the present application provides a capability registration device, including a first acquisition module 1501.

[0575] The first acquisition module 1501 is used to acquire a registration request message sent by a terminal; the registration request message sent by the terminal is used to perform capability registration; the registration request message sent by the terminal includes one or more of the following information:

[0576] Registration type;

[0577] Safety parameters;

[0578] Capability registration identifier;

[0579] Type of capability;

[0580] Capability reporting identifier;

[0581] Capability information.

[0582] In some embodiments, it also includes:

[0583] The first execution module is used to execute the UE capability authentication and / or security process based on the capability registration identifier and the capability type.

[0584] In some embodiments, it also includes:

[0585] The third sending module is configured to send a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information:

[0586] Authentication / security results;

[0587] Capability registration identifier;

[0588] UE location information.

[0589] In some embodiments, the first acquisition module includes:

[0590] The third sending unit is used to send a registration request message to the capability management function network element when there is only one capability management function network element in the network.

[0591] In some embodiments, sending a registration request message to a capability management function network element includes:

[0592] The fourth sending unit is used to send a registration request message to the capability management function network element corresponding to the capability registration identifier when there are multiple capability management function network elements in the network.

[0593] In some embodiments, it also includes:

[0594] The fourth sending module is used to send a report request message to the capability management function network element; the report request message includes one or more of the following information:

[0595] Authentication / security results;

[0596] Capability reporting identifier;

[0597] UE location information.

[0598] In some embodiments, the first acquisition module includes:

[0599] The fifth sending unit is used to send a reporting request message to the capability management function network element when there is only one capability management function network element in the network.

[0600] In some embodiments, the first acquisition module includes:

[0601] The sixth sending unit is used to send a reporting request message to the capability management function network element corresponding to the capability reporting identifier when there are multiple capability management function network elements in the network.

[0602] In some embodiments, it also includes:

[0603] A fifth sending module, configured to send a registration response message to the terminal; the registration response message is used to indicate a success or failure of the capability registration;

[0604] Or, also include:

[0605] The sixth sending module is used to send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0606] In some embodiments, when the registration request message is also used for network registration, it further includes:

[0607] The second execution module is used to execute the network authentication and / or security process of the UE.

[0608] Specifically, the capability registration device provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment in which the execution subject is a network device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0609] Fig.16 This is a third structural diagram of a capability registration device provided in an embodiment of the present application, such as Fig.16As shown, an embodiment of the present application provides a capability registration device, including a second acquisition module 1601 and a second sending module 1602.

[0610] The second acquisition module 1601 is used to acquire a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information:

[0611] Authentication / security results;

[0612] Capability registration identifier;

[0613] Capability reporting identifier;

[0614] UE location information.

[0615] The second sending module 1602 is used to send a registration response message to the terminal; the registration response message is used to indicate whether the capability registration is successful or failed.

[0616] In some embodiments, it also includes:

[0617] The seventh sending module is used to send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

[0618] Specifically, the capability registration device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the capability management function network element, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0619] It should be noted that the division of units / modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0620] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0621] In some embodiments, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the capability registration method provided by the above-mentioned method embodiments.

[0622] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0623] It should be noted that the computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0624] It should also be noted that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0625] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0626] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0627] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 6G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, a 6G system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), a 6G system (6GS), etc.

[0628] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 6G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0629] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0630] Network devices and terminal devices can each use one or more antennas for multi-input multi-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.

[0631] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0632] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0633] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0634] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0635] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A capability registration method, characterized in that: Applied to terminal UE, including: Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

2. The capability registration method according to claim 1, characterized in that: The method further comprises: Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration; Or also include: Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

3. The capability registration method according to claim 1 or 2, characterized in that: The sending of a registration request message to the network includes: In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

4. The capability registration method according to claim 1 or 2, characterized in that: The sending of a registration request message to the network includes: In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

5. The capability registration method according to claim 1 or 2, characterized in that: The registration types include initial registration type and mobile registration update.

6. The capability registration method according to claim 1 or 2, characterized in that: The security parameters include capability authentication data.

7. The capability registration method according to claim 1 or 2, characterized in that: The capability registration identifier is used to represent one or more capability registration indications.

8. The capability registration method according to claim 1 or 2, characterized in that: The capability reporting identifier is used to represent one or more capability reporting indications.

9. The capability registration method according to claim 1 or 2, characterized in that: The capability type includes one or more of the following types: Data node type; Artificial intelligence AI node type; The type of capability that can be called; Open capability types.

10. The capability registration method according to claim 1 or 2, characterized in that: The capability information includes one or more of the following information: Data collection capabilities; Data pre-processing capabilities; Data forwarding capability; Data storage capabilities; Data analysis skills; The protocols supported by the terminal; Applications APP supported by the terminal; AI models supported by the terminal; AI algorithms supported by the terminal.

11. A capability registration method, characterized in that: Applied to network equipment, including: Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

12. The capability registration method according to claim 11, characterized in that: The method further comprises: UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

13. The capability registration method according to claim 12, characterized in that: The method further comprises: Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information: Authentication / security results; Capability registration identifier; UE location information.

14. The capability registration method according to claim 13, characterized in that: The sending of a registration request message to the capability management function network element includes: In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

15. The capability registration method according to claim 13, characterized in that: The sending of a registration request message to the capability management function network element includes: In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

16. The capability registration method according to claim 12, characterized in that: The method further comprises: Send a report request message to the capability management function network element; the report request message includes one or more of the following information: Authentication / security results; Capability reporting identifier; UE location information.

17. The capability registration method according to claim 16, characterized in that: The sending of a report request message to the capability management function network element includes: In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

18. The capability registration method according to claim 16, characterized in that: The sending of a report request message to the capability management function network element includes: In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

19. The capability registration method according to any one of claims 11 to 18, characterized in that: The method further comprises: Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration; Or, also include: Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

20. The capability registration method according to any one of claims 11 to 18, characterized in that: In the case where the registration request message is also used for network registration, the method further includes: Perform network authentication and / or security procedures for the UE.

21. A capability registration method, characterized in that: Applicable to capability management functional network elements, including: Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information: Authentication / security results; Capability registration identifier; Capability reporting identifier; UE location information; Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

22. The capability registration method according to claim 21, characterized in that: The method further comprises: Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

23. A terminal, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Send a registration request message to the network; the registration request message is used to register capabilities; the registration request message includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

24. The terminal according to claim 23, characterized in that The processor is further configured to read the computer program in the memory and perform the following operations: Obtaining a registration response message fed back by the network; the registration response message is used to indicate success or failure of capability registration; Or also include: Obtain a reporting response message fed back by the network; the reporting response message is used to indicate the success or failure of the capability reporting.

25. The terminal according to claim 23 or 24, characterized in that: The sending of a registration request message to the network includes: In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

26. The terminal according to claim 23 or 24, characterized in that: The sending of a registration request message to the network includes: In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

27. The terminal according to claim 23 or 24, characterized in that: The registration types include initial registration type and mobile registration update.

28. The terminal according to claim 23 or 24, characterized in that: The security parameters include capability authentication data.

29. The terminal according to claim 23 or 24, characterized in that: The capability registration identifier is used to represent one or more capability registration indications.

30. The terminal according to claim 23 or 24, characterized in that: The capability reporting identifier is used to represent one or more capability reporting indications.

31. The terminal according to claim 23 or 24, characterized in that: The capability type includes one or more of the following types: Data node type; AI node type; The type of capability that can be called; Open capability types.

32. The terminal according to claim 23 or 24, characterized in that: The capability information includes one or more of the following information: Data collection capabilities; Data pre-processing capabilities; Data forwarding capability; Data storage capabilities; Data analysis skills; The protocols supported by the terminal; APP supported by the terminal; AI models supported by the terminal; AI algorithms supported by the terminal.

33. A network device, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used for capability registration; the registration request message sent by the terminal includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

34. The network device according to claim 33, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: UE capability authentication and / or security procedures are performed based on the capability registration identifier and capability type.

35. The network device according to claim 34, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Sending a registration request message to the capability management function network element; the registration request message sent to the capability management function network element includes one or more of the following information: Authentication / security results; Capability registration identifier; UE location information.

36. The network device according to claim 35, characterized in that The sending of a registration request message to the capability management function network element includes: In the case that there is only one capability management function network element in the network, a registration request message is sent to the capability management function network element.

37. The network device according to claim 35, characterized in that: The sending of a registration request message to the capability management function network element includes: In the case that there are multiple capability management function network elements in the network, a registration request message is sent to the capability management function network element corresponding to the capability registration identifier.

38. The network device according to claim 34, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Send a report request message to the capability management function network element; the report request message includes one or more of the following information: Authentication / security results; Capability reporting identifier; UE location information.

39. The network device according to claim 38, characterized in that: The sending of a report request message to the capability management function network element includes: In the case that there is only one capability management function network element in the network, a reporting request message is sent to the capability management function network element.

40. The network device according to claim 38, characterized in that The sending of a report request message to the capability management function network element includes: In the case that there are multiple capability management function network elements in the network, a reporting request message is sent to the capability management function network element corresponding to the capability reporting identifier.

41. The network device according to any one of claims 33 to 40, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Sending a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration; Or, also include: Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

42. The network device according to any one of claims 33 to 40, characterized in that: In a case where the registration request message is also used for network registration, the processor is further configured to read the computer program in the memory and perform the following operations: Perform network authentication and / or security procedures for the UE.

43. A capability management function network element, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Obtain a registration request message sent by a network device; the registration request message sent by the network device is used to perform capability registration; the registration request message sent by the network device includes one or more of the following information: Authentication / security results; Capability registration identifier; Capability reporting identifier; UE location information; Send a registration response message to the terminal; the registration response message is used to indicate the success or failure of the capability registration.

44. The capability management function network element according to claim 43, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: Send a reporting response message to the terminal; the reporting response message is used to indicate the success or failure of the capability reporting.

45. A capability registration device, characterized in that: include: The first sending module is used to send a registration request message to the network; the registration request message is used to perform capability registration; the registration request message includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

46. ​​A capability registration device, characterized in that: include: The first acquisition module is used to acquire a registration request message sent by a terminal; the registration request message sent by the terminal is used to perform capability registration; the registration request message sent by the terminal includes one or more of the following information: Registration type; Safety parameters; Capability registration identifier; Type of capability; Capability reporting identifier; Capability information.

47. A capability registration device, characterized in that: include: A second acquisition module, used to acquire a registration request message sent by a network device; The registration request message sent by the network device is used for capability registration; The registration request message sent by the network device includes one or more of the following information: Authentication / security results; Capability registration identifier; Capability reporting identifier; UE location information; The second sending module is used to send a registration response message to the terminal; the registration response message is used to indicate whether the capability registration is successful or failed.

48. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is used to cause a computer to execute the capability registration method according to any one of claims 1 to 10.

49. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is used to cause a computer to execute the capability registration method according to any one of claims 11 to 20.

50. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the capability registration method described in claim 21 or 22.

Citation Information

Cited By

  • Method and apparatus for capability registration, and storage medium

    EP4716320A1