Method and apparatus for capability registration, and storage medium

By sending a registration request message containing registration information in the 6G network, the problem of inability to register and report capabilities in the prior art is solved, and the effective registration and update of capabilities is realized, the normal provision of services is ensured, and signaling overhead is saved.

WO2024239941A1PCT designated stage expired Publication Date: 2024-11-28DATANG MOBILE COMM EQUIP CO LTD

Patent Information

Application Number
PCT/CN2024/090999
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-04-30
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

The lack of capability registration methods in the prior art has resulted in the inability to provide data services and AI services, and the inability to report and update capabilities, resulting in the inability to provide services.

Method used

By sending a registration request message between the terminal and the network device, including registration type, security parameters, capability registration identification, capability type and capability information, the capability registration and reporting of the UE as a capability node is realized, ensuring that the capability information is managed by the network management function network element Successfully registered and reported.

Benefits of technology

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

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024090999_28112024_PF_FP_ABST
    Figure CN2024090999_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure provides a method and an apparatus for capability registration and a storage medium. The method for capability registration is applicable to a terminal and comprises: sending a registration request message to a network, wherein the registration request message is configured for capability registration and comprises one or more of the following information: a registration type, a security parameter, a capability registration identifier, a capability type, a capability reporting identifier, and capability information.
Need to check novelty before this filing date? Find Prior Art

Description

Capability registration method, device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202310575213.6, filed on May 19, 2023, entitled “Capability Registration Method, Device and Storage Medium,” which is incorporated herein by reference in its entirety. Technical Field

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

[0004] The 6th Generation mobile networks (6G) will evolve into a network service platform that provides comprehensive capabilities, offering diverse, operational network services and creating value for users. However, capabilities must be registered and reported before they can be used.

[0005] However, there is no method for registering capabilities in the existing technology. Therefore, in data service, artificial intelligence (AI) service, and multi-network service scenarios, it is impossible to report capabilities and update capabilities, resulting in the inability to provide corresponding services.

[0006] Summary of the Invention

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

[0008] In a first aspect, an embodiment of the present disclosure provides a capability registration method, applied to a terminal, comprising:

[0009] 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:

[0010] Registration type;

[0011] Safety parameters;

[0012] Capability registration identifier;

[0013] Ability type;

[0014] Capability reporting identifier;

[0015] Capability information.

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

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

[0018] Or also include:

[0019] 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.

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

[0021] 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.

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

[0023] 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.

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

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

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

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

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

[0029] Data node type;

[0030] AI node type;

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

[0032] Open capability types.

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

[0034] Data collection capabilities;

[0035] Data preprocessing capabilities;

[0036] Data forwarding capability;

[0037] Data storage capacity;

[0038] Data analysis skills;

[0039] The protocols supported by the terminal;

[0040] APP supported by the terminal;

[0041] AI models supported by the terminal;

[0042] AI algorithms supported by the terminal.

[0043] In a second aspect, an embodiment of the present disclosure provides a capability registration method, applied to a network device, comprising:

[0044] 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:

[0045] Registration type;

[0046] Safety parameters;

[0047] Capability registration identifier;

[0048] Ability type;

[0049] Capability reporting identifier;

[0050] Capability information.

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

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

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

[0054] 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:

[0055] Authentication / security results;

[0056] Capability registration identifier;

[0057] UE location information.

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

[0059] 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.

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

[0061] 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.

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

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

[0064] Authentication / security results;

[0065] Capability reporting identifier;

[0066] UE location information.

[0067] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0068] 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.

[0069] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0070] 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.

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

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

[0073] Or, also include:

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

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

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

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

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

[0079] Authentication / security results;

[0080] Capability registration identifier;

[0081] Capability reporting identifier;

[0082] UE location information;

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

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

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

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

[0087] 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:

[0088] 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:

[0089] Registration type;

[0090] Safety parameters;

[0091] Capability registration identifier;

[0092] Ability type;

[0093] Capability reporting identifier;

[0094] Capability information.

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

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

[0097] Or also include:

[0098] 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.

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

[0100] 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.

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

[0102] 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.

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

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

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

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

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

[0108] Data node type;

[0109] AI node type;

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

[0111] Open capability types.

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

[0113] Data collection capabilities;

[0114] Data preprocessing capabilities;

[0115] Data forwarding capability;

[0116] Data storage capacity;

[0117] Data analysis skills;

[0118] The protocols supported by the terminal;

[0119] APP supported by the terminal;

[0120] AI models supported by the terminal;

[0121] AI algorithms supported by the terminal.

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

[0123] 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:

[0124] 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:

[0125] Registration type;

[0126] Safety parameters;

[0127] Capability registration identifier;

[0128] Ability type;

[0129] Capability reporting identifier;

[0130] Capability information.

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

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

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

[0134] 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:

[0135] Authentication / security results;

[0136] Capability registration identifier;

[0137] UE location information.

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

[0139] 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.

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

[0141] 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.

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

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

[0144] Authentication / security results;

[0145] Capability reporting identifier;

[0146] UE location information.

[0147] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0148] 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.

[0149] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0150] 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.

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

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

[0153] Or, also include:

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

[0155] In some embodiments, when 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:

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

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

[0158] 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:

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

[0160] Authentication / security results;

[0161] Capability registration identifier;

[0162] Capability reporting identifier;

[0163] UE location information;

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

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

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

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

[0168] The first sending module is configured to 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:

[0169] Registration type;

[0170] Safety parameters;

[0171] Capability registration identifier;

[0172] Ability type;

[0173] Capability reporting identifier;

[0174] Capability information.

[0175] In some embodiments, further comprising:

[0176] 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;

[0177] Or also include:

[0178] 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.

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

[0180] The first sending unit is configured 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.

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

[0182] The second sending unit is configured 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.

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

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

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

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

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

[0188] Data node type;

[0189] AI node type;

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

[0191] Open capability types.

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

[0193] Data collection capabilities;

[0194] Data preprocessing capabilities;

[0195] Data forwarding capability;

[0196] Data storage capacity;

[0197] Data analysis skills;

[0198] The protocols supported by the terminal;

[0199] APP supported by the terminal;

[0200] AI models supported by the terminal;

[0201] AI algorithms supported by the terminal.

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

[0203] A first acquisition module is configured to 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:

[0204] Registration type;

[0205] Safety parameters;

[0206] Capability registration identifier;

[0207] Ability type;

[0208] Capability reporting identifier;

[0209] Capability information.

[0210] In some embodiments, further comprising:

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

[0212] In some embodiments, further comprising:

[0213] 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:

[0214] Authentication / security results;

[0215] Capability registration identifier;

[0216] UE location information.

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

[0218] The third sending unit is configured 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.

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

[0220] The fourth sending unit is configured 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.

[0221] In some embodiments, further comprising:

[0222] The fourth sending module is configured 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:

[0223] Authentication / security results;

[0224] Capability reporting identifier;

[0225] UE location information.

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

[0227] The fifth sending unit is configured 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.

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

[0229] The sixth sending unit is configured 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.

[0230] In some embodiments, further comprising:

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

[0232] Or, also include:

[0233] 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.

[0234] In some embodiments, when the registration request message is also used for network registration, the following further comprises:

[0235] The second execution module is configured to execute a network authentication and / or security process for the UE.

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

[0237] The second acquisition module is configured 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:

[0238] Authentication / security results;

[0239] Capability registration identifier;

[0240] Capability reporting identifier;

[0241] UE location information;

[0242] The second sending module is configured 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.

[0243] In some embodiments, further comprising:

[0244] 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.

[0245] In the tenth aspect, an embodiment of the present disclosure 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.

[0246] In the eleventh aspect, an embodiment of the present disclosure 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.

[0247] In the twelfth aspect, an embodiment of the present disclosure 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 above.

[0248] In the thirteenth aspect, an embodiment of the present disclosure 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.

[0249] The capability registration method, device and storage medium provided by the embodiments of the present disclosure use the UE as a capability node to send a registration request message for capability registration to the network. 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. This implements capability registration with the UE as the capability node, thereby implementing capability reporting and capability updating, with minimal changes to the network and saving signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0251] FIG1 is a flow chart of a capability registration method according to an embodiment of the present disclosure;

[0252] FIG2 is a signaling interaction diagram of a schematic scenario of a capability registration method provided by an embodiment of the present disclosure;

[0253] FIG3 is a second signaling interaction diagram illustrating a scenario of a capability registration method provided in an embodiment of the present disclosure;

[0254] FIG4 is a third signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present disclosure;

[0255] FIG5 is a fourth signaling interaction diagram illustrating a scenario of a capability registration method provided in an embodiment of the present disclosure;

[0256] FIG6 is a fifth signaling interaction diagram illustrating a scenario of a capability registration method according to an embodiment of the present disclosure;

[0257] FIG7 is a sixth signaling interaction diagram illustrating a scenario of a capability registration method according to an embodiment of the present disclosure;

[0258] FIG8 is a seventh signaling interaction diagram illustrating a scenario of a capability registration method according to an embodiment of the present disclosure;

[0259] FIG9 is a second flow chart of the capability registration method provided in an embodiment of the present disclosure;

[0260] FIG10 is a third flow chart of the capability registration method provided in an embodiment of the present disclosure;

[0261] FIG11 is a schematic structural diagram of a terminal provided in an embodiment of the present disclosure;

[0262] FIG12 is a schematic structural diagram of a network device provided in an embodiment of the present disclosure;

[0263] FIG13 is a schematic structural diagram of a capability management function network element provided in an embodiment of the present disclosure;

[0264] FIG14 is a schematic diagram of a structure of a capability registration device according to an embodiment of the present disclosure;

[0265] FIG15 is a second structural diagram of a capability registration device provided by an embodiment of the present disclosure;

[0266] FIG16 is a third structural diagram of a capability registration device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0267] The data carried by 6G networks includes 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.

[0268] The data plane architecture of a 6G mobile communication network primarily consists of four functional components: a data orchestrator (DO) (or data controller (DC)), a data agent (DA), a trusted anchor agent (TAA), and a data storage function (DSF). The DO supports programmable data pipelines and implements data service request conversion, building data pipelines based on data service requests. The DA can be embedded in a network function element or terminal, or deployed independently to perform data collection, data preprocessing, data storage, data analysis, data sharing, and other data services orchestrated in the data pipeline. The DA can implement a variety of data processing functions, which are reported to the DO or DC as DA capabilities during DA registration, and capability updates can be reported in a timely manner.

[0269] In the existing technology, there is no registration method for data service capabilities, AI capabilities, network callable capabilities, etc., which makes it impossible to report capabilities and thus impossible to provide network services such as services and AI services.

[0270] Based on the above technical problems, an embodiment of the present disclosure proposes a capability registration method, which sends a request message for capability registration to a network device as a capability node. 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. This realizes capability registration with the UE as the capability node, and then realizes capability reporting and capability update, with little change to the network, saving signaling overhead.

[0271] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0272] FIG1 is a flow chart of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG1 , an embodiment of the present disclosure 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:

[0273] 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:

[0274] Registration type;

[0275] Safety parameters;

[0276] Capability registration identifier;

[0277] Ability type;

[0278] Capability reporting identifier;

[0279] Capability information.

[0280] Specifically, the terminal registers its capabilities as a capability node. That is, the terminal sends a registration request message to a network device for capability registration. The network device receives the registration request message sent by the terminal and registers the capabilities based on the information contained in the registration request message. The registration request message is a Non-Access Stratum (NAS) message.

[0281] In the embodiment of the present disclosure, the network device may be a radio access network (RAN), an access and mobility management function (AMF) network element, an authentication / security management function network element and / or a capability management function network element, etc.

[0282] Optionally, the UE may register and report capabilities simultaneously, or may first register capabilities and then report capabilities.

[0283] 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. 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. The capability registration request message carries information such as the capability registration identifier and UE location information. After the capability management function network element successfully registers, the terminal obtains a registration response message, thereby notifying the successful capability registration.

[0284] After the capability registration is successful, the terminal sends a registration request message to the network device. The registration request message contains the registration type, capability reporting identifier, capability type, capability information, and UE identifier. After receiving the registration request message, the network device 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. After the report is successful, the network sends a registration acceptance message to the terminal.

[0285] For another example, the terminal sends a registration request message to the network device, where 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. After receiving the registration request message, the network device 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.

[0286] Optionally, the UE may perform network registration and capability registration simultaneously or at different times, for example, performing capability registration at the same time as network registration, or performing network registration first and then capability registration, or performing capability registration first and then network registration.

[0287] The capability registration method provided by the embodiment of the present disclosure 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.

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

[0289] 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 mobile registration update, including the UE capability update type.

[0290] For example, the UE performs network registration, capability registration, and reporting simultaneously, and the registration type in the registration request message sent to the network is the initial registration type.

[0291] 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.

[0292] 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.

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

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

[0295] Specifically, the network device receives a registration request message and, based on the capability registration identifier in the registration request message, learns that a capability registration operation is required. If 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 to which the capability registration identifier corresponds, so that the capability type corresponding to the capability registration identifier can be successfully registered.

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

[0297] Specifically, the network device receives a registration request message and, based on the capability registration identifier in the registration request message, can learn that a capability reporting operation is required. 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 type corresponding to the capability reporting identifier can be successfully reported.

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

[0299] Data node type;

[0300] AI node type;

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

[0302] Open capability types.

[0303] Specifically, during 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. During 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.

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

[0305] Data collection capabilities;

[0306] Data preprocessing capabilities;

[0307] Data forwarding capability;

[0308] Data storage capacity;

[0309] Data analysis skills;

[0310] The protocols supported by the terminal;

[0311] APP supported by the terminal;

[0312] AI models supported by the terminal;

[0313] AI algorithms supported by the terminal.

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

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

[0316] Or also include:

[0317] 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.

[0318] 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.

[0319] For example, after a network device such as AMF sends a registration request message to the capability management function network element to register the capability, it sends a registration response message to the terminal. 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.

[0320] 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. 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.

[0321] 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.

[0322] 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 sends a report response message to the terminal to indicate success or failure of the capability report. The terminal receives the report response message.

[0323] 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 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.

[0324] 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 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 whether the capability reporting is successful or failed, and the terminal receives the reporting response message.

[0325] The capability registration method provided by the embodiment of the present disclosure 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.

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

[0327] 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.

[0328] 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.

[0329] 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 a RAN or an 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.

[0330] 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.

[0331] 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.

[0332] 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, where the registration request message includes a capability registration identifier. The network device sends a registration request message to the capability management function network element based on the capability registration identifier, where the registration request message includes information such as an authentication / security result, a capability registration identifier, and / or UE location information.

[0333] 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, where the registration request message includes a capability reporting identifier. The network device sends a reporting request message to the capability management function network element based on the capability reporting identifier, where the reporting request message includes information such as the authentication / security result, the capability reporting identifier, and / or the UE location information.

[0334] 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, where 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 based on the capability registration identifier and the capability reporting identifier. The registration request message sent to the capability management function network element includes information such as the authentication / security result, the capability registration identifier, the capability reporting identifier, and / or the UE location information.

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

[0336] 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.

[0337] 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.

[0338] 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 a RAN or an 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.

[0339] 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.

[0340] 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 based on the capability registration identifier, and sends a registration request message to the capability management function network element corresponding to the capability registration identifier. The registration request message sent to the capability management function network element includes information such as the authentication / security result, the capability registration identifier, and / or the UE location information.

[0341] 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, where the registration request message includes a capability reporting identifier. The network device determines that a capability reporting operation is to be performed based on the capability reporting identifier, and sends a reporting request message to the capability management function network element corresponding to the capability reporting identifier. The reporting request message sent to the capability management function network element includes information such as the authentication / security result, the capability reporting identifier, and / or the UE location information.

[0342] 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, where 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 based on 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. The registration request message sent to the capability management function network element includes information such as the authentication / security result, the capability registration identifier, the capability reporting identifier, and / or the UE location information.

[0343] The capability registration method provided by the embodiment of the present disclosure 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.

[0344] In some embodiments, after obtaining 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.

[0345] 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.

[0346] 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 capability authentication and / or security process of the UE 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 and other 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.

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

[0348] 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.

[0349] 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.

[0350] 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.

[0351] In the capability registration method provided in the embodiments of the present disclosure, the network device also performs UE capability authentication and / or security procedures based on the capability registration identifier and capability type, thereby authorizing legitimate UEs and providing guarantees for capability registration and capability reporting. When the UE is registered with the network, the UE capability authentication can be performed by the AMF or by the capability management function network element, allowing for flexible application based on actual needs.

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

[0353] Example 1:

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

[0355] FIG2 is a signaling interaction diagram of a schematic scenario of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG2 , the terminal first performs capability registration. The specific steps of capability registration are as follows:

[0356] 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 type, etc. The security parameters may include capability authentication data; the capability registration identifier indicates the registration of a certain type or multiple types of capabilities; 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.

[0357] 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.

[0358] 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 the authentication / security result, capability registration identifier, and UE location information. The network may have multiple different capability management function network elements 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.

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

[0360] FIG3 is a second signaling interaction diagram of a schematic scenario of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG3 , the specific steps for a terminal to report capabilities after performing the above-mentioned capability registration process are as follows:

[0361] 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., as well as callable capabilities, such as supported protocols, supported applications (APPs), supported AI models or algorithms, etc.; the registration type refers to mobile registration update (UE capability update type).

[0362] Step 2: After receiving the UE's registration request, 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 the UE's 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. If the report is successful, a response message is sent.

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

[0364] Example 2:

[0365] FIG4 is a third signaling interaction diagram illustrating a scenario of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG4 , the UE registers its capability while performing network registration, and the registration and capability reporting are performed together.

[0366] 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 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, and other capability types. Capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, and other capabilities. It also includes callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, and other capabilities. The registration type refers to the initial registration type.

[0367] 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.

[0368] Step 3: After successful authentication, the network sends 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 the 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.

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

[0370] Example 3:

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

[0372] FIG5 is a fourth signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present disclosure. As shown in FIG5 , when the UE has registered with the network, the specific steps for the UE to perform capability registration are as follows:

[0373] 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 type, etc. The security parameters include capability authentication data, the capability reporting identifier indicates a certain type or multiple types of capability reporting; the capability type refers to the capability to be reported, such as data node type, callable capability type, etc.; the registration type refers to the mobile registration update (UE capability update type).

[0374] 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.

[0375] 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 the authentication / security result, 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 using the capability registration identifier. After successful registration, a response message is sent.

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

[0377] FIG6 is a fifth signaling interaction diagram illustrating a scenario of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG6 , after capability registration is completed, capability reporting can be performed. The specific steps of capability reporting are as follows:

[0378] 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., as well as 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).

[0379] Step 2: After receiving the UE's registration request, 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 other information such as the UE's location. If the network has multiple capability management functions, the access mobility management function sends capability reporting requests to the corresponding capability management function based on the capability reporting identifier and capability type. If the report is successful, a response message is sent.

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

[0381] Example 4:

[0382] FIG7 is a sixth signaling interaction diagram of a schematic scenario of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG7 , the UE has registered with the network. The specific steps for the UE to register and report capabilities are as follows:

[0383] 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 instructions; the capability type refers to the capability to be reported, such as data node type, callable capability type, and other capability types; capability information refers to specific capabilities, including data service capabilities, such as data collection, data preprocessing, data forwarding, data storage, data analysis, and other capabilities, as well as callable capabilities, such as supported protocols, supported apps, supported AI models or algorithms, and other capabilities; the registration type refers to mobile registration update (UE capability update type).

[0384] 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.

[0385] Step 3: After successful authentication, the network sends a capability registration and 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 the authentication / security result, capability registration identifier, capability reporting identifier, capability type, capability information, 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.

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

[0387] Example 5:

[0388] FIG8 is a seventh signaling interaction diagram of a schematic scenario of a capability registration method provided in an embodiment of the present disclosure. As shown in FIG8 , when the UE has registered with the network, the process of the UE performing capability update is similar to the process of capability reporting. The specific steps of the UE performing capability update are as follows:

[0389] 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., as well as 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).

[0390] Step 2: After receiving the UE's registration request, the network sends 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 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.

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

[0392] The capability registration method provided by the embodiment of the present disclosure uses the UE as a capability node to send a registration request message for capability registration to the network. 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. This implements capability registration with the UE as the capability node, and further implements capability reporting and capability updating, with minimal changes to the network, saving signaling overhead.

[0393] In some embodiments, if the RAN can interact directly with the authentication function and 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.

[0394] 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.

[0395] 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 performing the UE capability authentication and / or security process, it also needs to perform the UE network authentication and / or security process.

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

[0397] Alternatively, when the UE needs to register with the network and also register its capabilities, it is also possible to only perform an authentication / security process on whether the UE can register with the network.

[0398] The capability registration method provided by the embodiments of the present disclosure eliminates the need for capability authentication and / or security procedures for UEs that have already registered with the network, thereby simplifying the signaling process and improving the efficiency of capability registration and reporting.

[0399] In some embodiments, if the UE has successfully registered with the network and does not require capability authentication / security procedures, and the RAN can directly access 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 perform registration, authentication, and capability reporting to the capability management function.

[0400] The capability registration method provided in the embodiments of the present disclosure performs capability registration by sending a registration request message from the RAN to the capability management function network element when the authentication / security function network element can directly interact with the management function network element. Based on the existing network architecture, a variety of network devices are provided to perform capability registration, which can be flexibly applied to various scenarios.

[0401] FIG9 is a second flow chart of a capability registration method provided by an embodiment of the present disclosure. As shown in FIG9 , an embodiment of the present disclosure provides a capability registration method, the execution subject of which may be a network device, such as a radio access network (RAN), an 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:

[0402] Step 901: Obtain a registration request message sent by a terminal; the registration request message sent by the terminal is used to register capabilities; the registration request message sent by the terminal includes one or more of the following information:

[0403] Registration type;

[0404] Safety parameters;

[0405] Capability registration identifier;

[0406] Ability type;

[0407] Capability reporting identifier;

[0408] Capability information.

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

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

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

[0412] 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:

[0413] Authentication / security results;

[0414] Capability registration identifier;

[0415] UE location information.

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

[0417] 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.

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

[0419] 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.

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

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

[0422] Authentication / security results;

[0423] Capability reporting identifier;

[0424] UE location information.

[0425] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0426] 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.

[0427] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0428] 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.

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

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

[0431] Or, also include:

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

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

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

[0435] Specifically, the capability registration method provided in the embodiment of the present disclosure 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.

[0436] FIG10 is a flow chart of the capability registration method provided by the embodiment of the present disclosure. As shown in FIG10 , the embodiment of the present disclosure provides a capability registration method, the execution subject of which may be a capability management function network element. The method includes:

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

[0438] Authentication / security results;

[0439] Capability registration identifier;

[0440] Capability reporting identifier;

[0441] UE location information;

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

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

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

[0445] Specifically, the capability registration method provided in the embodiment of the present disclosure 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.

[0446] FIG11 is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure. As shown in FIG11 , the terminal includes a memory 1103, a transceiver 1101, and a processor 1102, wherein:

[0447] 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:

[0448] 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:

[0449] Registration type;

[0450] Safety parameters;

[0451] Capability registration identifier;

[0452] Ability type;

[0453] Capability reporting identifier;

[0454] Capability information.

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

[0456] In FIG11 , 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 1102 and memory represented by memory 1103. The bus architecture may also link together various other circuits such as peripheral devices, 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 over a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 1104 may also be an interface capable of connecting external or internal devices as required, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0457] 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.

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

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

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

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

[0462] Or also include:

[0463] 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.

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

[0465] 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.

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

[0467] 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.

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

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

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

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

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

[0473] Data node type;

[0474] AI node type;

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

[0476] Open capability types.

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

[0478] Data collection capabilities;

[0479] Data preprocessing capabilities;

[0480] Data forwarding capability;

[0481] Data storage capacity;

[0482] Data analysis skills;

[0483] The protocols supported by the terminal;

[0484] APP supported by the terminal;

[0485] AI models supported by the terminal;

[0486] AI algorithms supported by the terminal.

[0487] It should be noted here that the above-mentioned terminal provided in the embodiment of the present disclosure can implement all the method steps implemented by the method embodiment in which the 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 those of the method embodiment will not be described in detail here.

[0488] FIG12 is a schematic diagram of the structure of a network device provided by an embodiment of the present disclosure. As shown in FIG12 , the network device includes a memory 1203, a transceiver 1201, and a processor 1202, wherein:

[0489] 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:

[0490] 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:

[0491] Registration type;

[0492] Safety parameters;

[0493] Capability registration identifier;

[0494] Ability type;

[0495] Capability reporting identifier;

[0496] Capability information.

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

[0498] In FIG12 , 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 peripheral devices, 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, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or 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.

[0499] 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.

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

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

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

[0503] 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:

[0504] Authentication / security results;

[0505] Capability registration identifier;

[0506] UE location information.

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

[0508] 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.

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

[0510] 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.

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

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

[0513] Authentication / security results;

[0514] Capability reporting identifier;

[0515] UE location information.

[0516] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0517] 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.

[0518] In some embodiments, the sending of the report request message to the capability management function network element includes:

[0519] 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.

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

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

[0522] Or, also include:

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

[0524] In some embodiments, when 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:

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

[0526] Specifically, the above-mentioned network device provided in the embodiment of the present disclosure 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.

[0527] FIG13 is a schematic diagram of the structure of a capability management function network element provided in an embodiment of the present disclosure. As shown in FIG13 , the capability management function network element includes a memory 1303, a transceiver 1301, and a processor 1302, wherein:

[0528] 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:

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

[0530] Authentication / security results;

[0531] Capability registration identifier;

[0532] Capability reporting identifier;

[0533] UE location information;

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

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

[0536] In FIG13 , 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 1302 and memory represented by memory 1303. The bus architecture may also link together various other circuits such as peripheral devices, 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 over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. 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.

[0537] 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.

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

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

[0540] Specifically, the capability management function network element provided in the embodiment of the present disclosure 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.

[0541] FIG14 is a schematic diagram of a structure of a capability registration device provided by an embodiment of the present disclosure. As shown in FIG14 , an embodiment of the present disclosure provides a capability registration device, including a first sending module 1401, wherein:

[0542] The first sending module 1401 is configured to 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:

[0543] Registration type;

[0544] Safety parameters;

[0545] Capability registration identifier;

[0546] Ability type;

[0547] Capability reporting identifier;

[0548] Capability information.

[0549] In some embodiments, further comprising:

[0550] 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;

[0551] Or also include:

[0552] 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.

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

[0554] The first sending unit is configured 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.

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

[0556] The second sending unit is configured 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.

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

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

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

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

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

[0562] Data node type;

[0563] AI node type;

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

[0565] Open capability types.

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

[0567] Data collection capabilities;

[0568] Data preprocessing capabilities;

[0569] Data forwarding capability;

[0570] Data storage capacity;

[0571] Data analysis skills;

[0572] The protocols supported by the terminal;

[0573] APP supported by the terminal;

[0574] AI models supported by the terminal;

[0575] AI algorithms supported by the terminal.

[0576] Specifically, the capability registration device provided in the embodiment of the present disclosure can implement all the method steps implemented in the method embodiment in which the 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 those of the method embodiment will not be described in detail here.

[0577] FIG15 is a second structural diagram of a capability registration device provided by an embodiment of the present disclosure. As shown in FIG15 , an embodiment of the present disclosure provides a capability registration device, including a first acquisition module 1501 .

[0578] The first acquisition module 1501 is configured to 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:

[0579] Registration type;

[0580] Safety parameters;

[0581] Capability registration identifier;

[0582] Ability type;

[0583] Capability reporting identifier;

[0584] Capability information.

[0585] In some embodiments, further comprising:

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

[0587] In some embodiments, further comprising:

[0588] 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:

[0589] Authentication / security results;

[0590] Capability registration identifier;

[0591] UE location information.

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

[0593] The third sending unit is configured 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.

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

[0595] The fourth sending unit is configured 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.

[0596] In some embodiments, further comprising:

[0597] The fourth sending module is configured 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:

[0598] Authentication / security results;

[0599] Capability reporting identifier;

[0600] UE location information.

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

[0602] The fifth sending unit is configured 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.

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

[0604] The sixth sending unit is configured 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.

[0605] In some embodiments, further comprising:

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

[0607] Or, also include:

[0608] 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.

[0609] In some embodiments, when the registration request message is also used for network registration, the following further comprises:

[0610] The second execution module is configured to execute a network authentication and / or security process for the UE.

[0611] Specifically, the capability registration device provided in the embodiment of the present disclosure 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.

[0612] FIG16 is a third structural diagram of a capability registration device provided by an embodiment of the present disclosure. As shown in FIG16 , an embodiment of the present disclosure provides a capability registration device, including a second acquisition module 1601 and a second sending module 1602 .

[0613] 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 register capabilities; the registration request message sent by the network device includes one or more of the following information:

[0614] Authentication / security results;

[0615] Capability registration identifier;

[0616] Capability reporting identifier;

[0617] UE location information.

[0618] The second sending module 1602 is configured 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.

[0619] In some embodiments, further comprising:

[0620] 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.

[0621] Specifically, the capability registration device provided in the embodiment of the present disclosure can implement all the method steps implemented in 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.

[0622] It should be noted that the division of units / modules in the above-mentioned embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The above-mentioned integrated units may be implemented in the form of hardware or software functional units.

[0623] 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 disclosure 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 for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0624] 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.

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

[0626] 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 CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0627] It should also be noted that the terms "first," "second," and the like in the embodiments of the present disclosure are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present disclosure can be implemented in an order other than that illustrated or described herein. Furthermore, the terms "first" and "second" generally distinguish objects of the same type, and do not limit the number of objects. For example, the first object can be one or more.

[0628] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

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

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

[0631] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with 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 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 "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 voice and / or data with a radio 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, or a user device, but is not limited in the embodiments of the present disclosure.

[0632] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting 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 disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. 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 geographically separated.

[0633] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple 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. It can also use diversity transmission, precoding transmission, or beamforming transmission.

[0634] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0635] The present disclosure 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 disclosure. 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0636] 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 a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0637] 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, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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

Claims

1. A capability registration method, applied to a terminal UE, comprising: 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.

2. The capability registration method according to claim 1, wherein: 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, wherein: 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, wherein: 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, wherein: The registration types include initial registration type and mobile registration update.

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

7. The capability registration method according to claim 1 or 2, wherein: 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, wherein: 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, wherein: 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, wherein: 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, applied to a network device, comprising: Obtain the registration request message sent by the terminal; The registration request message sent by the terminal is used to register the capability; 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, applied to a capability management function network element, comprising: Obtain the registration request message sent by the 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: 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, wherein: 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 comprising a memory, a transceiver, and a processor; a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform 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, wherein: 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, wherein: 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, wherein: 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, wherein: The registration types include initial registration type and mobile registration update.

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

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

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

31. The terminal according to claim 23 or 24, wherein: 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, wherein: 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 comprising a memory, a transceiver, and a processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, comprising a memory, a transceiver, and a processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform 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, wherein: 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, comprising: A first sending module, used to 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.

46. ​​The capability registration device according to claim 45, wherein: Also includes: 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; Or also include: 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.

47. The capability registration device according to claim 45 or 46, wherein: The first sending module includes: 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.

48. The capability registration device according to claim 45 or 46, wherein: The first sending module includes: 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.

49. The capability registration device according to claim 45 or 46, wherein: The registration types include initial registration type and mobile registration update.

50. The capability registration device according to claim 45 or 46, wherein: The security parameters include capability authentication data.

51. The capability registration device according to claim 45 or 46, wherein: The capability registration identifier is used to represent one or more capability registration indications.

52. The capability registration device according to claim 45 or 46, wherein: The capability reporting identifier is used to represent one or more capability reporting indications.

53. The capability registration device according to claim 45 or 46, wherein: 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.

54. The capability registration device according to claim 45 or 46, wherein: 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.

55. A capability registration device, comprising: A first acquisition module, used to acquire a registration request message sent by a terminal; The terminal sends The registration request message sent by the terminal is used to register the capability; 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.

56. The capability registration device according to claim 55, wherein: Also includes: 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.

57. The capability registration device according to claim 56, wherein: Also includes: A third sending module is used 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: Authentication / security results; Capability registration identifier; UE location information.

58. The capability registration device according to claim 57, wherein: The first acquisition module includes: 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.

59. The capability registration device according to claim 57, wherein: The first acquisition module includes: 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.

60. The capability registration device according to claim 56, wherein: Also includes: A fourth sending module, 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: Authentication / security results; Capability reporting identifier; UE location information.

61. The capability registration device according to claim 60, wherein: The first acquisition module includes: 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.

62. The capability registration device according to claim 60, wherein: The first acquisition module includes: 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.

63. The capability registration device according to any one of claims 55 to 62, wherein: Also includes: A fifth sending module, used to send a registration response message to the terminal; The registration response message is used to indicate the success or failure of capability registration; Or, also include: A sixth sending module, used to send a report response message to the terminal; The reporting response message is used to indicate the success or failure of the capability reporting.

64. The capability registration device according to any one of claims 55 to 62, wherein: In the case where the registration request message is also used for network registration, it further includes: The second execution module is used to execute the network authentication and / or security process of the UE.

65. A capability registration device, comprising: 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.

66. The capability registration device according to claim 65, wherein: Also includes: A seventh sending module, used to send a report response message to the terminal; The reporting response message is used to indicate the success or failure of the capability reporting.

67. A computer-readable storage medium storing a computer program, wherein the computer program is used to cause a computer to execute the capability registration method according to any one of claims 1 to 10.

68. A computer-readable storage medium storing a computer program, wherein the computer program is used to cause a computer to execute the capability registration method according to any one of claims 11 to 20.

69. A computer-readable storage medium storing a computer program, wherein the computer program is used to enable a computer to execute the capability registration method according to claim 21 or 22.

Citation Information

Patent Citations

  • Registration method and device, storage medium and chip

    CN115606265A

Cited By

  • Methods and systems to support automated extended reality (XR) service provisioning

    WO2026157034A1