Model registration method, terminal, first network element, and second network element

Abstract

The present disclosure relates to a model registration method, a terminal, a first network element, and a second network element. The method comprises: sending a first message, wherein the first message comprises information about a first model and / or a first function that a terminal needs to register. Thus, the terminal can achieve, by sending the information about the first model and / or the first function that the terminal needs to register, registration of models and / or functions deployed on the terminal, thereby ensuring normal use of the models and / or the functions deployed on the terminal.

Description

Model registration method, terminal, first network element, second network element Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a model registration method, a terminal, an access network device, a first network element, and a second network element. Background Art

[0002] In recent years, artificial intelligence (AI) technology has achieved continuous breakthroughs in various fields. For example, AI technology has been widely applied in education, transportation, home appliances, healthcare, retail, security, and other fields, bringing convenience to people's lives while also promoting industrial upgrades in various fields. In the field of communications, the introduction of AI technology into wireless air interfaces has been proposed to assist in improving wireless air interface transmission technology.

[0003] Summary of the Invention

[0004] The method disclosed in the present invention can be used to solve the technical problem of "how to register the model on the terminal side".

[0005] The embodiments of the present disclosure provide a model registration method, a terminal, an access network device, a first network element, and a second network element.

[0006] According to a first aspect of an embodiment of the present disclosure, a model registration method is proposed, which is executed by a terminal. The method includes: sending a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0007] According to the second aspect of an embodiment of the present disclosure, a model registration method is proposed, which is executed by a first network element. The method includes: receiving a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0008] According to the third aspect of an embodiment of the present disclosure, a model registration method is proposed, which is executed by a second network element. The method includes: receiving a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a model registration method is proposed, which is executed by an access network device. The method includes: receiving indication information sent by a first network element, wherein the indication information is used to instruct the terminal to perform model and / or function registration.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module for sending a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a first network element is proposed, comprising: a transceiver module for receiving a first message, wherein the first message includes information about a first model and / or a first function that a terminal needs to register.

[0012] According to the seventh aspect of an embodiment of the present disclosure, a second network element is proposed, including: a transceiver module for receiving a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0013] According to an eighth aspect of an embodiment of the present disclosure, an access network device is proposed, comprising: a transceiver module for receiving indication information sent by a first network element, wherein the indication information is used to instruct a terminal to perform model and / or function registration.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a terminal is proposed, comprising: one or more processors; wherein the terminal is used to execute the model registration method described in the embodiment of the first aspect above.

[0015] According to the tenth aspect of the embodiment of the present disclosure, a first network element is proposed, comprising: one or more processors; wherein the first network element is used to execute the model registration method described in the embodiment of the second aspect above.

[0016] According to the eleventh aspect of the embodiment of the present disclosure, a second network element is proposed, comprising: one or more processors; wherein the second network element is used to execute the model registration method described in the embodiment of the third aspect above.

[0017] According to the twelfth aspect of the embodiments of the present disclosure, an access network device is proposed, including: one or more processors; wherein, the second network element is used to execute the model registration method described in the fourth or fifth aspect embodiments above.

[0018] According to the thirteenth aspect of an embodiment of the present disclosure, a model registration method is proposed, including: a terminal sends a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register; a first network element or a second network element receives the first message.

[0019] According to the fourteenth aspect of the embodiments of the present disclosure, a communication system is proposed, including a terminal and a first network element, wherein the terminal is configured to implement the model registration method described in the embodiment of the first aspect above, and the first network element is configured to implement the model registration method described in the embodiment of the second aspect above.

[0020] According to the fifteenth aspect of the embodiments of the present disclosure, a communication system is proposed, including a terminal, a first network element and a second network element, wherein the terminal is configured to implement the model registration method described in the embodiment of the first aspect above, the first network element is configured to implement the model registration method described in the embodiment of the second aspect above, and the second network element is configured to implement the model registration method described in the embodiment of the third aspect above.

[0021] According to the sixteenth aspect of the embodiments of the present disclosure, a communication system is proposed, including a terminal, a first network element, a second network element and an access network device, wherein the terminal is configured to implement the model registration method described in the embodiment of the first aspect above, the first network element is configured to implement the model registration method described in the embodiment of the second aspect above, the second network element is configured to implement the model registration method described in the embodiment of the third aspect above, and the access network device is configured to implement the model registration method described in the embodiment of the fourth aspect above.

[0022] According to the seventeenth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal, a first network element, a second network element and an access network device, wherein the communication system can execute the model registration method as described in any one of the first, second, third and fourth aspects.

[0023] According to the eighteenth aspect of an embodiment of the present disclosure, a communication system is proposed, including a terminal, a first network element, a second network element and an access network device, the terminal sends a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register; the first network element or the second network element receives the first message.

[0024] According to the nineteenth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the model registration method as described in any one of the first, second, third and fourth aspects.

[0025] In an embodiment of the present disclosure, a terminal may send a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register. Thus, the terminal can register the model and / or function deployed on the terminal by sending the information about the first model and / or the first function that needs to be registered, thereby ensuring normal use of the model and / or function deployed on the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0027] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0028] 2A-2B are interactive schematic diagrams illustrating a model registration method according to an embodiment of the present disclosure;

[0029] 3A-3D are flowcharts illustrating a model registration method according to an embodiment of the present disclosure;

[0030] 4A-4F are flowcharts illustrating a model registration method according to an embodiment of the present disclosure;

[0031] 5A-5D are interactive schematic diagrams illustrating a model registration method according to an embodiment of the present disclosure;

[0032] FIG6A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0033] FIG6B is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

[0034] FIG6C is a schematic structural diagram of a second network element proposed in an embodiment of the present disclosure;

[0035] FIG7A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0036] FIG7B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0037] The embodiments of the present disclosure provide a model registration method, a terminal, a first network element, and a second network element.

[0038] In a first aspect, an embodiment of the present disclosure proposes a model registration method, which is executed by a terminal. The method includes: sending a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0039] In the above embodiment, the terminal may send a first message, wherein the first message includes information about the first model and / or first function that the terminal needs to register. Thus, by sending the information about the first model and / or first function that needs to be registered, the terminal can register the model and / or function deployed on the terminal, thereby ensuring normal use of the model and / or function deployed on the terminal.

[0040] In combination with some embodiments of the first aspect, in some embodiments, sending the first message includes: sending a first message to a first network element, wherein the first message includes information about the first model and / or first function that the terminal needs to register.

[0041] In the above embodiment, the terminal can register the model and / or function deployed on the terminal by sending information about the first model and / or first function that the terminal needs to register to the first network element, thereby ensuring the normal use of the model and / or function deployed on the terminal.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the first message is any one of the following: a registration request message; a first request message, wherein the first request message is a service request message in the service request process triggered by the terminal; a second request message, wherein the second request message is a service request message in the service request process triggered by the first network element.

[0043] In the above embodiment, registration of the model and / or function can be implemented in the registration process, the service request process triggered by the terminal, and the service request process triggered by the first network element, thereby improving the flexibility of the model and / or function registration method.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving instruction information sent by a first network element, where the instruction information is used to instruct the terminal to perform model and / or function registration. That is, the terminal receives the instruction information sent by the first network element, where the instruction information is used to instruct the terminal to perform model and / or function registration; and sending the first message to the first network element.

[0045] In the above embodiment, the terminal may send the first message to the first network element after receiving the model and / or function registration indication sent by the first network element, thereby saving resources.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a first paging message sent by an access network device, wherein the first paging message includes the indication information, and the indication information in the first paging message is sent by the first network element to the access network device through a second paging message.

[0047] In the above embodiment, the terminal can receive the indication information from the first network element through the paging message of the access network device, which enriches the method of obtaining the indication information.

[0048] In combination with some embodiments of the first aspect, in some embodiments, sending the first message includes: sending the first message to the second network element.

[0049] In the above embodiment, the terminal may directly send the first message to the second network element to register the model and / or function with the second network element, thereby registering the model and / or function of the terminal with the second network element.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the first message is any one of the following: a third request message, wherein the third request message is a positioning request message sent to the first network element in a mobile originated-location request procedure (mobile originated-location request Procedure, MO-LR Procedure); a location result message, wherein the location result message is a location notification return result message sent to the first network element in a mobile terminated location request procedure (mobile terminated location request, MT-LR Procedure).

[0051] In the above embodiment, the terminal may send a first message to the first network element during the positioning process to implement model and / or function registration with the second network element during the positioning process, thereby enriching the registration method of the model and / or function.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a second message sent by the first network element, wherein the second message is used to request the terminal to perform model and / or function registration.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving a second message sent by the first network element, wherein the second message is used to request the terminal to perform model and / or function registration; and sending the first message to the first network element.

[0054] In the above embodiment, the terminal may send the first message to the first network element after receiving the request message sent by the first network element requesting the terminal to register the model and / or function, thereby saving resources.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the second message is a non-access stratum (NAS) message for positioning sent by the first network element during the positioning process.

[0056] In the above embodiment, the terminal can receive the NAS message for positioning sent by the first network element during the positioning process to obtain indication information. The first network element does not need to send the indication information through additional signaling, thus saving signaling overhead.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a third message sent by the first network element, wherein the third message includes the registration result of the first model and / or the first function.

[0058] In the above embodiment, the terminal can receive the registration result of the first model and / or first function sent by the first network element, so that the terminal can know the registration result of the first model and / or first function, which facilitates the subsequent use of the model and / or function.

[0059] In combination with some embodiments of the first aspect, in some embodiments, receiving the third message sent by the first network element includes: receiving the registration result of the first model and / or first function sent by the first network element through the access network device.

[0060] In the above embodiment, the terminal can receive the registration result sent by the first network element through the access network device, thereby enriching the method of obtaining the model and / or function registration result.

[0061] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a radio resource control (RRC) reconfiguration message sent by an access network device, wherein the RRC reconfiguration message includes a registration result of the first model and / or first function, and the registration result in the RRC reconfiguration message is sent by the first network element to the access network device via an N2 request message.

[0062] In the above embodiment, the terminal can obtain the registration result of the first model and / or the first function by receiving the RRC reconfiguration message sent by the access network device, so that the access network device does not need to send the registration result of the first model and / or the first function through additional signaling, saving signaling overhead.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the first message is a registration request message, and the third message is a registration acceptance message.

[0064] In the above embodiment, the terminal can send information about the first model and / or first function that needs to be registered to the first network element through a registration request message, and receive the registration result of the first model and / or first function through a registration acceptance message, thereby realizing the registration of the model and / or function during the registration process.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the registration result of the first model and / or the first function includes at least one of the following: information of models that are successfully registered in the first model; information of models that fail to register in the first model; information of functions that are successfully registered in the first function; information of functions that fail to register in the first function.

[0066] In the above embodiment, the terminal can determine the model that has been successfully registered, the model that has failed to be registered, the function that has been successfully registered, the function that has failed to be registered, etc. based on the registration results of the first model and / or the first function, which facilitates the application of the model and / or function.

[0067] In combination with some embodiments of the first aspect, in some embodiments, the information of the first model and / or first function includes at least one of the following: an identification of the first model; a function of the first model; a structure of the first model; parameters of the first model; or an identification of the first function.

[0068] In the above embodiment, the terminal sends the identifier, function, result, parameters, etc. of the first model and the identifier of the first function to the first network element, so that the network can register the model and / or function based on this information, thereby improving the efficiency of model and / or function registration.

[0069] In a second aspect, an embodiment of the present disclosure proposes a model registration method, which is executed by a first network element. The method includes: receiving a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0070] In the above embodiment, the first network element can receive information about the first model and / or first function that the terminal needs to register, which is sent through the first message, so that the model and / or function deployed on the terminal can be registered based on the information about the first model and / or first function that the terminal needs to register, thereby ensuring the normal use of the model and / or function deployed on the terminal.

[0071] In combination with some embodiments of the second aspect, in some embodiments, receiving the first message includes: receiving a first message sent by the terminal, wherein the first message includes information about the first model and / or first function that the terminal needs to register.

[0072] In the above embodiment, the first network element can receive information about the first model and / or first function that the terminal needs to register, which is sent by the terminal through the first message, so that the model and / or function deployed on the terminal can be registered based on the information about the first model and / or first function that the terminal needs to register, thereby ensuring the normal use of the model and / or function deployed on the terminal.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the first message is any one of the following: a registration request message; a first request message, wherein the first request message is a service request message in the service request process triggered by the terminal; a second request message, wherein the second request message is a service request message in the service request process triggered by the first network element.

[0074] In the above embodiment, registration of models and / or functions can be implemented in the registration process, the service request process triggered by the terminal, and the service request process triggered by the first network element, thereby improving the flexibility of the registration method of the models and / or functions.

[0075] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending indication information to the terminal, wherein the indication information is used to instruct the terminal to perform model and / or function registration.

[0076] In combination with some embodiments of the second aspect, in some embodiments, receiving the first message sent by the terminal includes: sending indication information to the terminal, wherein the indication information is used to instruct the terminal to perform model and / or function registration; and receiving the first message sent by the terminal.

[0077] In the above embodiment, the first network element can send indication information to the first network element to instruct the terminal to perform model and / or function registration, so that the terminal can send the first message to the first network element after receiving the model and / or function registration indication sent by the first network element, saving resources.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending the indication information to the terminal through an access network device.

[0079] In combination with some embodiments of the second aspect, in some embodiments, sending the indication information to the terminal includes: sending the indication information to the terminal through an access network device.

[0080] In the above embodiment, the first network element may send the indication information to the terminal through the access network device, thereby enriching the sending method of the indication information.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a second paging message to the access network device, wherein the second paging message includes the indication information.

[0082] In combination with some embodiments of the second aspect, in some embodiments, sending the indication information to the terminal through the access network device includes: sending a second paging message to the access network device, wherein the second paging message includes the indication information.

[0083] In the above embodiment, the first network element may send a paging message to the access network device, so as to send the indication information to the terminal through the access network device, thereby enriching the sending method of the indication information.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a fourth message to the second network element, wherein the fourth message includes information on the successfully registered second model and / or second function.

[0085] In the above embodiment, the first network element may send information about the successfully registered second model and / or second function to the second network element, so that the second network element may use the successfully registered model and / or function.

[0086] In combination with some embodiments of the second aspect, in some embodiments, sending the fourth message to the second network element includes: sending the fourth message to the second network element during the positioning process.

[0087] In the above embodiment, during the positioning process, the first network element sends information about the successfully registered second model and / or second function to the second network element, so that the second network element can use the successfully registered model and / or function during the positioning process, thereby improving positioning accuracy and efficiency.

[0088] In combination with some embodiments of the second aspect, in some embodiments, sending the fourth message to the second network element includes: receiving a fifth message sent by the second network element, wherein the fifth message is used to request information on the model and / or function of the successful registration of the terminal; and sending the fourth message to the second network element.

[0089] In the above embodiment, after receiving the request from the second network element to obtain the information of the model and / or function of the successful terminal registration, the first network element can send the information of the successfully registered second model and / or second function to the second network element, thereby saving resources.

[0090] In combination with some embodiments of the second aspect, in some embodiments, the first message is any one of the following: a third request message, wherein the first positioning request message is a positioning request message in the MO-LR Procedure; a location result message, wherein the location result message is a location notification return result message in the MT-LR Procedure.

[0091] In the above embodiment, the first network element can obtain information about the first model and / or first function that the terminal needs to register during the positioning process, thereby registering the model during the positioning process and enriching the model and / or function registration method.

[0092] In combination with some embodiments of the second aspect, in some embodiments, receiving the first message sent by the terminal includes: sending a second message to the terminal, wherein the second message is used to request the terminal to perform model and / or function registration; and receiving the first message sent by the terminal.

[0093] In the above embodiment, the first network element can send a message to the terminal requesting the terminal to register the model and / or function, so that after receiving the request message sent by the first network element requesting the terminal to register the model and / or function, the terminal sends the first message to the first network element, thereby saving resources.

[0094] In combination with some embodiments of the second aspect, in some embodiments, the second message is a non-access stratum NAS message for positioning sent by the first network element during the positioning process.

[0095] In the above embodiment, the first network element may request the terminal to perform model and / or function registration by sending a NAS message for positioning during the positioning process. The first network element does not need to send a request through additional signaling, thus saving signaling overhead.

[0096] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending information about the first model and / or first function that the terminal needs to register to the second network element.

[0097] In the above embodiment, the first network element can send information about the first model and / or first function that the terminal needs to register to the second network element, so that the second network element registers the first model and / or first function, enriching the model and / or function registration method.

[0098] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a registration result of the first model and / or first function sent by the second network element.

[0099] In the above embodiment, the first network element can receive the registration result of the first model and / or the first function sent by the second network element, so that the first network element can know the registration status of the first model and / or the first function.

[0100] In the above embodiment, the first network element can send information about the first model and / or first function that the terminal needs to register to the second network element, so that the second network element can register the model and / or function of the terminal, enriching the model and / or function registration method.

[0101] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a third message to the terminal, wherein the third message includes the registration result of the first model and / or first function.

[0102] In the above embodiment, the first network element can send the registration result of the first model and / or the first function to the terminal, so that the terminal can obtain the registration result of the first model and / or the first function, facilitating the subsequent use of the model and / or function.

[0103] In combination with some embodiments of the second aspect, in some embodiments, sending the third message to the terminal includes: sending the registration result of the first model and / or first function to the terminal through an access network device.

[0104] In the above embodiment, the first network element may send the registration result of the first model and / or the first function to the terminal through the access network device, thereby enriching the sending method of the model and / or function registration result.

[0105] In combination with some embodiments of the second aspect, in some embodiments, sending the registration result of the first model and / or first function to the terminal through the access network device includes: sending an N2 request message to the access network device, wherein the N2 request message includes the registration result of the first model and / or first function.

[0106] In the above embodiment, the first network element can send the registration result of the first model and / or the first function to the access network device through the N2 request message, without sending the registration result of the first model and / or the first function through additional signaling, thereby saving signaling overhead.

[0107] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending an N2 request message to the access network device, wherein the N2 request message includes the first model and / or the registration result of the first model.

[0108] In combination with some embodiments of the second aspect, in some embodiments, the registration result of the first model and / or the first function includes at least one of the following: information of the model that is successfully registered in the first model; information of the model that fails to register in the first model; information of the function that is successfully registered in the first function; information of the function that fails to register in the first function.

[0109] In the above embodiment, information about the model that has been successfully registered, information about the model that has failed to be registered, etc. is sent to the terminal, so that the terminal can determine the model that has been successfully registered and the model that has failed to be registered based on the registration results of the first model and / or the first function, thereby facilitating the application of the model.

[0110] In combination with some embodiments of the second aspect, in some embodiments, the information of the first model and / or first function includes at least one of the following: an identification of the first model; a function of the first model; a structure of the first model; parameters of the first model; or an identification of the first function.

[0111] In the above embodiment, the first network element can receive the identifier, function, result, parameters, etc. of the first model sent by the terminal, so that the network can register the model and / or function according to this information, thereby improving the efficiency of model and / or function registration.

[0112] In a third aspect, an embodiment of the present disclosure proposes a model registration method, which is executed by a second network element. The method includes: receiving a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

[0113] In the above embodiment, the second network element can receive the information of the first model and / or first function that the terminal needs to register sent through the first message, so that according to the information of the first model and / or first function that the terminal needs to register, the registration of the model and / or function deployed on the terminal can be realized, and the normal use of the model and / or function deployed on the terminal can be ensured.

[0114] In combination with some embodiments of the third aspect, in some embodiments, receiving the first message includes: receiving the first message sent by the terminal or the first network element.

[0115] In combination with some embodiments of the third aspect, in some embodiments, the receiving of the first message includes at least one of the following: receiving the first message sent by the terminal; receiving the first message sent by the terminal via the first network element.

[0116] In the above embodiment, the second network element may directly receive the first message sent by the terminal, or may receive the first message through the first network element, thereby enriching the ways of receiving the first message.

[0117] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: sending a registration result of the first model and / or first function to the first network element.

[0118] In the above embodiment, the second network element may send the registration result of the first model and / or the first function to the first network element, thereby facilitating the first network element to learn the registration status of the first model and / or the first function.

[0119] In combination with some embodiments of the third aspect, in some embodiments, the registration result of the first model and / or the first function includes at least one of the following: information of the model that is successfully registered in the first model; information of the model that fails to be registered in the first model; information of the function that is successfully registered in the first function; information of the function that fails to be registered in the first function.

[0120] In the above embodiment, information on the model that has been successfully registered, information on the model that has failed to be registered, information on the function that has been successfully registered, information on the function that has failed to be registered, etc. are sent to the first network element, so that the first network element can determine the model and / or function that has been successfully registered, the model and / or function that has failed to be registered, etc.

[0121] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: receiving a fourth message sent by the first network element, wherein the fourth message includes information on the successful registration of the second model and / or second function.

[0122] In the above embodiment, the second network element can use the successfully registered model and / or function according to the fourth message, thereby improving the efficiency of model use.

[0123] In combination with some embodiments of the third aspect, in some embodiments, the receiving the fourth message sent by the first network element includes: receiving the fourth message sent by the first network element during the positioning process.

[0124] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: receiving the fourth message sent by the first network element in the MO-LR Procedure or the MT-LR Procedure.

[0125] In the above embodiment, during the positioning process, the second network element receives information about the successfully registered second model and / or second function sent by the first network element, so that the second network element can use the successfully registered model and / or function in the positioning process, thereby improving positioning accuracy and efficiency.

[0126] In combination with some embodiments of the third aspect, in some embodiments, receiving the fourth message sent by the first network element includes: sending a fifth message to the first network element, wherein the fifth message is used to request information on the model and / or function of the successful registration of the terminal; and receiving the fourth message sent by the first network element.

[0127] In the above embodiment, the second network element requests the first network element for information on the model and / or function of the successful terminal registration, so that the first network element can send the information on the successfully registered second model and / or second function to the second network element after receiving the request from the second network element to obtain information on the model and / or function of the successful terminal registration, thereby saving resources.

[0128] In combination with some embodiments of the third aspect, in some embodiments, the information of the first model and / or first function includes at least one of the following: an identification of the first model; a function of the first model; a structure of the first model; parameters of the first model; or an identification of the first function.

[0129] In the above embodiment, the second network element can register the model according to the identification, function, result, parameter and other information of the first model, and register the function according to the identification of the first function, thereby improving the efficiency of model and / or function registration.

[0130] In a fourth aspect, an embodiment of the present disclosure proposes a model registration method, which is executed by an access network device. The method includes: receiving indication information sent by a first network element, wherein the indication information is used to instruct the terminal to perform model and / or function registration.

[0131] In the above embodiment, the access network device may receive the indication information sent by the first network element, and thus may send the indication information to other devices.

[0132] In combination with some embodiments of the fourth aspect, in some embodiments, it also includes: sending indication information to the terminal.

[0133] In the above embodiment, the access network device sends the indication information sent by the first network element to the terminal, thereby sending the indication information to the terminal through the access network device, so that the terminal can register the model according to the indication letter request, enriching the indication information sending method.

[0134] In combination with some embodiments of the fourth aspect, in some embodiments, receiving indication information sent by the first network element includes receiving a second paging message sent by the first network element, wherein the second paging message includes the indication information.

[0135] In the above embodiment, when receiving the indication information sent by the first network element through the paging message, the first network element does not need to send the indication information through additional signaling, thus saving signaling overhead.

[0136] In combination with some embodiments of the fourth aspect, in some embodiments, it also includes: receiving a registration result of the first model and / or the first function sent by the first network element.

[0137] In the above embodiment, the registration result of the first model and / or the first function can be sent to the terminal through the access network device, so that the terminal can know the registration status of the first model and / or the first function, which is convenient for subsequent model use.

[0138] In combination with some embodiments of the fourth aspect, in some embodiments, receiving the registration result of the first model and / or first function sent by the first network element includes: receiving an N2 request message sent by the first network element, wherein the N2 request message includes the registration result of the first model and / or first function.

[0139] In the above embodiment, upon receiving the registration result of the first model and / or first function sent by the first network element via an N2 request message, the first network element does not need to send indication information via additional signaling, thereby saving signaling overhead. In a fifth aspect, embodiments of the present disclosure provide a terminal, comprising at least one of a transceiver module and a processing module, wherein the terminal is configured to execute the first aspect and optional implementations of the first aspect.

[0140] In the sixth aspect, an embodiment of the present disclosure proposes a first network element, which includes at least one of a transceiver module and a processing module: wherein the first network element is used to execute the second aspect and the optional implementation method of the second aspect.

[0141] In the seventh aspect, an embodiment of the present disclosure proposes a second network element, which includes at least one of a transceiver module and a processing module: wherein the second network element is used to execute the third aspect and the optional implementation method of the third aspect.

[0142] In an eighth aspect, an embodiment of the present disclosure proposes a terminal, which includes: one or more processors; wherein the terminal is used to execute according to the first aspect and the optional implementation method of the first aspect.

[0143] In a ninth aspect, an embodiment of the present disclosure proposes a first network element, which includes: one or more processors; wherein the first network element is used to execute according to the second aspect and the optional implementation method of the second aspect.

[0144] In the tenth aspect, an embodiment of the present disclosure proposes a second network element, which includes: one or more processors; wherein the second network element is used to execute according to the third aspect and the optional implementation method of the third aspect.

[0145] In the eleventh aspect, an embodiment of the present disclosure proposes a second network element, and the above-mentioned access network device includes: one or more processors; wherein, the access network device is used to execute according to the third aspect and the optional implementation method of the third aspect.

[0146] In the twelfth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal and a first network element, wherein the terminal is configured to implement the method described in the first aspect and the optional implementation method of the first aspect, and the first network element is configured to implement the method described in the second aspect and the optional implementation method of the second aspect.

[0147] In the thirteenth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal, a first network element and a second network element, wherein the terminal is configured to implement the method described in the first aspect and the optional implementation method of the first aspect, the first network element is configured to implement the method described in the second aspect and the optional implementation method of the second aspect, and the second network element is configured to implement the method described in the third aspect and the optional implementation method of the third aspect.

[0148] In the fourteenth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal, a first network element, a second network element and an access network device, wherein the terminal is configured to implement the method described in the first aspect and the optional implementation method of the first aspect, the first network element is configured to implement the method described in the second aspect and the optional implementation method of the second aspect, the second network element is configured to implement the method described in the third aspect and the optional implementation method of the third aspect, and the second network element is configured to implement the method described in the fourth aspect and the optional implementation method of the fourth aspect.

[0149] In the fifteenth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal, a first network element, a second network element and an access network device, wherein the communication system can be used to execute the methods described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, the optional implementation of the third aspect, the fourth aspect, and the optional implementation of the fourth aspect.

[0150] In the sixteenth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal, a first network element, and a second network element, wherein the terminal sends a first message, wherein the first message includes information about the first model and / or first function that the terminal needs to register; the first network element or the second network element receives the first message.

[0151] In the seventeenth aspect, an embodiment of the present disclosure proposes a model registration method, including: a terminal sends a first message to a first network element, wherein the first message includes information about the first model and / or first function that the terminal needs to register; the first network element or the second network element receives the first message.

[0152] In aspect 18, an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the processor is used to execute the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect and the optional implementation of the third aspect.

[0153] In the twentieth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, the optional implementation of the third aspect, the fourth aspect, and the optional implementation of the fourth aspect.

[0154] In the twenty-first aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, the optional implementation of the third aspect, the fourth aspect, and the optional implementation of the fourth aspect.

[0155] In aspect 22, an embodiment of the present disclosure proposes a computer program which, when running on a computer, enables the computer to execute the method described in aspect 1, the optional implementation of aspect 1, the second aspect, the optional implementation of aspect 2, the third aspect, the optional implementation of aspect 3, the fourth aspect, and the optional implementation of aspect 4.

[0156] In a twenty-third aspect, an embodiment of the present disclosure provides a chip or chip system. The chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, the optional implementation of the third aspect, the fourth aspect, and the optional implementation of the fourth aspect.

[0157] It is understandable that the above-mentioned terminal, access network device, first network element, second network element, communication system, storage medium, program product, computer program, chip or chip system are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0158] The embodiments of the present disclosure provide a model registration method, a terminal, an access network device, a first network element, and a second network element. In some embodiments, the terms model registration method, terminal, access network device, first network element, and second network element are interchangeable with information processing method, communication method, etc.; information transmission device is interchangeable with information processing device, communication device, etc.; and information processing system is interchangeable with communication system.

[0159] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0160] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0161] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0162] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0163] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0164] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0165] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0166] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0167] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0168] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0169] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0170] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0171] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0172] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0173] In some embodiments, an access network device, a core network device, or a network device may be replaced with a terminal. For example, embodiments of the present disclosure may be applied to a structure in which communication between an access network device, a core network device, or a network device and a terminal is replaced with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal may also have all or part of the functions of the access network device.

[0174] In addition, the terms "uplink" and "downlink" can also be replaced with terms corresponding to inter-device communication (e.g., "side"). For example, uplink channel, downlink channel, etc. can be replaced with side channel, and uplink, downlink, etc. can be replaced with sidelink.

[0175] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0176] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0177] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0178] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, communication system 100 may include a terminal 110, a core network device 120, and an access network device 130. Core network device 120 may include a first network element 121 and a second network element 122. For example, first network element 121 may be an access and mobility management function (AMF), and second network element 122 may be a location management function (LMF).

[0179] In some embodiments, the terminal 110 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0180] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB) in a 5G communication system, a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a WiFi system, but is not limited thereto.

[0181] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0182] In some embodiments, the access network device 130 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0183] In some embodiments, the core network device 120 can be a device including one or more network elements, or can be multiple devices or device groups, each including all or part of one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0184] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0185] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0186] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0187] In some embodiments, AI or machine learning (deep learning, ML) is applied to 5G networks or (6th generation mobile networks, 6G) networks, such as positioning based on AI or ML. For AI-based positioning, there may be multiple AI models for positioning, and different AI models are applied to different positioning application scenarios. That is, for different positioning application scenarios, different data sets are used to train the AI ​​model, thereby obtaining different AI models for different positioning application scenarios.

[0188] AI models for positioning can be deployed in the UE, gNB, and LMF. A brief description of AI or ML-based models is as follows: direct AI or ML positioning, such as the AI ​​or ML model output: UE location; AI or ML-assisted positioning, such as the AI ​​or ML model output: new measurements and / or enhancements to existing measurements.

[0189] For example, line of sight (LOS) identification, non-line of sight (NLOS) identification, timing and / or measurement angles, measurement possibilities.

[0190] In some embodiments, the following situations may be: Example 1: UE-based positioning, UE side model, direct AI or ML positioning; Example 2a: UE-assisted or LMF-based positioning, with UE side model, AI or ML-assisted positioning; Example 2b: UE-assisted or LMF positioning based on LMF side model, direct AI or ML positioning; Example 3a: NG-RAN node-assisted positioning, gNB side model, AI or ML-assisted positioning; Example 3b: NG-RAN node-assisted positioning with LMF side model, direct AI or ML positioning.

[0191] For direct AI or ML positioning, the model input of AI or ML can be channel measurements related to (transmit receive point, TRP), such as TRP0, TRP1, ..., TRP(N-1), and the model output of AI or ML can be the location of the terminal.

[0192] In some embodiments, in Example 1 and Example 2a, the AI ​​function and / or AI model is deployed on the UE side. Therefore, the AI ​​function and / or AI model deployed on the UE side may require network registration.

[0193] In some embodiments, for Example 1 (i.e., UE based AI positioning, direct AI / ML positioning) or Example 2a (i.e., UE-assisted / LMF-based positioning with UE-side model, AI / ML assisted positioning), the AI ​​function and / or AI model is deployed on the UE side. Therefore, the AI ​​function and / or AI model deployed on the UE side may require network registration.

[0194] In some embodiments, there is no detailed solution for how the terminal registers the AI ​​model.

[0195] Based on this, the present disclosure proposes a model registration method.

[0196] FIG2A is an interactive diagram of a model registration method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a model registration method for a communication system 100, the method comprising:

[0197] Step S2101: The terminal 110 sends a first message to the first network element 121.

[0198] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "arbitrary", "any", "first", etc. can be interchangeable, and "specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", "any A", "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, any A, any A or first A, etc., but not limited to this.

[0199] In some embodiments, terminal 110 may send a first message.

[0200] In some embodiments, the terminal 110 may send a first message to the first network element 121 .

[0201] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0202] In some embodiments, the first message may include information about the first model and / or first function that terminal 110 needs to register. Exemplarily, the first model may be an AI model. Exemplarily, the first function may be an AI function, and the AI ​​function may be implemented by an AI model. Exemplarily, multiple AI models may implement the same AI function. Exemplarily, one AI model may implement multiple AI functions. Exemplarily, the first message may include the AI ​​model and / or AI function that terminal 110 needs to register.

[0203] Exemplarily, the information of the first model and / or the first function may include at least one of the following: an identifier of the first model; a function of the first model; a structure of the first model; a parameter of the first model; or an identifier of the first function.

[0204] Exemplarily, the functions of the first model may include but are not limited to obtaining the location of the terminal 110, obtaining a multipath NLOS indication, obtaining a multipath LOS indication, obtaining a positioning measurement result, and the like.

[0205] Exemplarily, the parameters of the first model may include but are not limited to the gradient and weight matrix of the first model.

[0206] In some embodiments, the terminal 110 may send a first message to the first network element 121 to register the first model and / or the first function with the first network element 121 .

[0207] In some embodiments, terms such as "AI model", "AI function", "model", "function", etc. can be used interchangeably.

[0208] In some embodiments, terms such as "registration," "identification," and "authentication" may be used interchangeably.

[0209] In some embodiments, the first message can be any one of the following: a registration request message; a first request message; wherein the first request message is a service request message in a service request process triggered by a terminal; a second request message; wherein the second request message is a service request message in a service request process triggered by a first network element.

[0210] In some embodiments, the terminal 110 registers the first model and / or the first function with the first network element 121. The terminal 110 registers the first model and / or the first function during the registration process with the network. Exemplarily, the registration request message (registration request) sent by the terminal 110 to the access device includes the AI ​​model or AI function that the terminal 110 needs to register. The access network device includes the AI ​​model or AI function that the terminal needs to register sent by the terminal 110 in the registration request message sent to the first network element 121.

[0211] In some embodiments, the terminal 110 includes the AI ​​model or AI function that the terminal 110 needs to register in the registration request message (registration request) sent to the first network element 121.

[0212] In some embodiments, the terminal 110 may register the first model and / or the first function with the first network element 121, and the terminal 110 may register the first model and / or the first function during a service request process triggered by the terminal 110. Exemplarily, the terminal 110 includes the AI ​​model that the terminal 110 needs to register in the service request message sent to the access network device, and the access network device includes the AI ​​model that the terminal 110 needs to register in the service request message sent to the first network element 121.

[0213] In some embodiments, the service request message (service request) sent by the terminal 110 to the first network element 121 includes the AI ​​model or AI function that the terminal 110 needs to register.

[0214] In some embodiments, the service request message (service request) sent by the terminal 110 to the first network element 121 during the network-triggered service request process includes the AI ​​model or AI function that the terminal 110 needs to register.

[0215] In some embodiments, the first network element 121 may send indication information to the terminal 110 , where the indication information may be used to instruct the terminal 110 to perform model and / or function registration.

[0216] Optionally, the first network element 121 may send indication information to the terminal 110 through the access network device.

[0217] Optionally, the first network element 121 may send a second paging message to the access network device, and the access network device receives the second paging message sent by the first network element 121, wherein the second paging message includes the indication information. Optionally, the access network device sends a first paging message to the terminal 121, wherein the first paging message includes the indication information.

[0218] Optionally, the access network device may send the first paging message to the terminal 110 after receiving the second paging message sent by the first network element 121. In some embodiments, the terminal 110 may receive the indication information sent by the first network element 121.

[0219] Optionally, the terminal 110 may receive indication information sent by the first network element 110 through the access network device.

[0220] Optionally, the terminal 110 may receive a paging message sent by the first network element 110 , where the paging message includes the indication information.

[0221] Optionally, the terminal 110 may receive a first paging message sent by the access network device, where the first paging message includes indication information.

[0222] In some embodiments, after receiving the indication information sent by the first network element 121 , the terminal 110 sends a first message to the first network element 121 .

[0223] In some embodiments, after receiving the indication information sent by the first network element 121, the terminal 110 sends a service request message to the first network element 121, where the service request message includes the AI ​​model or AI function that the terminal 110 needs to register.

[0224] Exemplarily, the first network element 121 instructs the terminal 110 to register the AI ​​model and / or AI function in the first paging message sent to the access network device, and the access network device instructs the terminal 110 to register the AI ​​model and / or AI function in the second paging message sent to the terminal 110, and the terminal 110 includes the AI ​​model and / or AI function that needs to be registered in the service request message.

[0225] In some embodiments, the first message may be any one of the following: a third request message; wherein the third request message is a positioning request message sent to the first network element 121 in the MO-LR Procedure; a location result message; wherein the location result message is a location notification return result message sent to the first network element 121 in the MT-LR Procedure.

[0226] Exemplarily, in the MO-LR Procedure, the first message is a third request message, and the terminal 110 includes information about the first model and / or first function that the terminal 110 needs to register in the third request message sent to the first network element 121 .

[0227] Exemplarily, in the MO-LR Procedure, the first network element 121 may receive the third request information sent by the terminal 110 .

[0228] Exemplarily, in the MO-LR Procedure, the terminal 110 includes information about the first model and / or first function that the terminal 110 needs to register in a third request message sent to the first network element 121 , and the first network element 121 may receive the third request information sent by the terminal 110 .

[0229] In some embodiments, first network element 121 may send a second message to terminal 110, where the second message may be used to request terminal 110 to perform model and / or function registration. Exemplarily, the second message may be a NAS message for positioning sent by first network element 121 during a positioning process. Exemplarily, the second message may be a NAS message for positioning sent by first network element 121 during an MT-LR procedure.

[0230] Exemplarily, in the MT-LR Procedure, the first message is a location result message, and the location result message sent by the terminal 110 to the first network element 121 includes information about the first model and / or first function that the terminal 110 needs to register.

[0231] Exemplarily, in the MT-LR Procedure, the first network element 121 may receive a location result message sent by the terminal 110 .

[0232] Exemplarily, in the MT-LR Procedure, the terminal 110 includes information about the first model and / or first function that the terminal 110 needs to register in the location result message sent to the first network element 121 , and the first network element 121 can receive the location result message sent by the terminal 110 .

[0233] In some embodiments, the first network element may be an AMF, or other network element that can register a model, which is not limited in this application.

[0234] Step S2102 : The first network element 121 sends a third message to the terminal 110 .

[0235] In some embodiments, the first network element 121 may receive a first message sent by the terminal 110 .

[0236] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0237] In some embodiments, the first network element 121 may register the model and / or function according to the first message, and send a third message to the terminal 110 according to the registration result. The third message may include the registration result of the first model and / or the first function.

[0238] Illustratively, in the MO-LR Procedure, the first network element 121 may receive a third request message sent by the terminal 110 , register the first model and / or the first function according to the third request information, and send a third message to the terminal 110 according to the registration result.

[0239] Illustratively, in the MO-LR Procedure, the first network element 121 may receive a third request message sent by the terminal 110 , register the first model and / or the first function according to the third request information, and send a third message to the terminal 110 according to the registration result.

[0240] Illustratively, in the MT-LR Procedure, the first network element 121 may receive a location result message sent by the terminal 110 , register the first model and / or the first function according to the location result message, and send a third message to the terminal 110 according to the registration result.

[0241] Exemplarily, in the MT-LR Procedure, the first network element 121 may receive a location result message sent by the terminal 110, register the first model and / or the first function according to the location result message information, and send a third message to the terminal 110 according to the registration result.

[0242] In some embodiments, the terminal 110 may receive a third message sent by the first network element 121 .

[0243] Exemplarily, the registration result of the first model and / or the first function may include at least one of the following: information of models that are successfully registered in the first model; information of models that fail to register in the first model; information of functions that are successfully registered in the first function; information of functions that fail to register in the first function.

[0244] In some embodiments, the model information may include an identifier of the model, and the function information may include an identifier of the function.

[0245] In some embodiments, the first network element 121 may receive a first message sent by the terminal 110. After receiving the first message, the first network element 121 may send a third message to the terminal 110. For example, the first message may be a registration request message, and the third message may be a registration acceptance message.

[0246] Exemplarily, the terminal 110 can register the first model and / or the first function with the first network element 121, the first network element 121 can receive the information of the first model and / or the first function that needs to be registered sent by the terminal 110 through a registration request message, and the first network element 121 can send the registration result of the first model and / or the first function to the terminal 110 through a registration acceptance message.

[0247] In some embodiments, the first network element 121 may send the registration result of the first model and / or the first function to the terminal 110 through the access network device.

[0248] In some embodiments, the terminal 110 may receive a registration result of the first model and / or the first function sent by the first network element 121 through the access network device.

[0249] In some embodiments, the first network element 121 may send an N2 request message to the access network device, wherein the N2 request message includes a registration result of the first model and / or the first function.

[0250] In some embodiments, the access network device may send an RRC reconfiguration message to the terminal 110 , wherein the RRC reconfiguration message includes a registration result of the first model and / or the first function.

[0251] In some embodiments, the terminal 110 may receive an RRC reconfiguration message sent by the access network device, wherein the RRC reconfiguration message includes a registration result of the first model and / or the first function.

[0252] In some embodiments, the first network element 121 may send the registration result of the first model and / or the first function to the access network device through an N2 request message. After receiving the N2 request message, the access network device may send the registration result of the first model and / or the first function to the terminal 110 through an RRC reconfiguration message. The terminal 110 receives the registration result of the first model and / or the first function sent by the access network device through the RRC reconfiguration message.

[0253] Step S2103: The first network element 121 sends a fourth message to the second network element.

[0254] In some embodiments, the first network element 121 may send a fourth message to the second network element 122, wherein the fourth message may include information about the successfully registered second model and / or second function. Thus, the first network element 121 may send information about the successfully registered model and / or function to the second network element 122.

[0255] Exemplarily, the information of the second model and / or the second function may include at least one of the following: an identifier of the second model; a function of the second model; a structure of the second model; a parameter of the second model; or an identifier of the first function.

[0256] In some embodiments, a successfully registered model may also be understood as a registered model, and a successfully registered function may also be understood as a registered function.

[0257] In some embodiments, during the positioning procedure, the first network element 121 may send a fourth message to the second network element 122. For example, the positioning procedure may be an MO-LR procedure. For example, the positioning procedure may be an MT-LR procedure.

[0258] In some embodiments, if terminal 110 registers a first model and / or a first function with first network element 121, first network element 121 may send information about a successfully registered second model and / or second function to second network element 122, where the second model is a model successfully registered in the first model, and the second function is a function successfully registered in the first function. Exemplarily, the positioning procedure may be an MO-LR procedure. Exemplarily, the positioning procedure may be an MT-LR procedure.

[0259] Exemplarily, in the MO-LR Procedure, the first network element 121 may send information about the second model and / or second function successfully registered by the terminal 110 to the second network element 122 via a fourth message. Exemplarily, the second model may be a model and / or function successfully registered in the first model that the terminal 110 requested to register from the first network element 121.

[0260] Exemplarily, in the MO-LR Procedure, information about the second model and / or second function successfully registered by the terminal 110 may be sent to the second network element 122 via a fourth message. Exemplarily, the second model may be a model and / or function successfully registered in the first model that the terminal 110 requested to register with the first network element 121.

[0261] In some embodiments, the second network element 122 may receive information of the successfully registered second model and / or second function sent by the first network element 121 .

[0262] In some embodiments, during the positioning process, the second network element 122 may receive information sent by the first network element 121 indicating successful registration of the second model and / or the second function. An exemplary positioning process may be an MO-LR procedure. An exemplary positioning process may be an MT-LR procedure.

[0263] In some embodiments, if the terminal 110 registers the first model and / or the first function with the first network element 121 , the second network element 122 may receive information of the second model and / or the second function successfully registered in the first model sent by the first network element 121 .

[0264] In some embodiments, if terminal 110 registers a first model and / or a first function with first network element 121, during the positioning process, second network element 122 may receive information from first network element 121 regarding a successfully registered second model and / or a successfully registered second function within the first model. An exemplary positioning process may be an MO-LR procedure. An exemplary positioning process may be an MT-LR procedure.

[0265] In some embodiments, the second network element 122 may send a fifth message to the first network element 121 , where the fifth message may be used to request information about a model and / or function for which the terminal 110 has successfully registered.

[0266] In some embodiments, the first network element 121 may receive a fifth message sent by the second network element 122 .

[0267] In some embodiments, after receiving the fifth message sent by the second network element 122, the first network element 121 may send a fourth message to the second network element 122, and the second network element 122 may receive the fourth message sent by the first network element 121. Exemplarily, the second model successfully registered in the fourth message may be a model in the first model that the terminal 110 requested the first network element 121 to register. Exemplarily, the second function successfully registered in the fourth message may be a function in the first function that the terminal 110 requested the first network element 121 to register.

[0268] In some embodiments, the second network element may be a LMF, or may be other network elements that manage positioning functions, which is not limited.

[0269] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, or both steps S2101 and S2102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0270] In some embodiments, one or more of these steps may be omitted or replaced in different embodiments.

[0271] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0272] FIG2B is an interactive diagram of a model registration method according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to a model registration method for a communication system 100, the method comprising:

[0273] Step S2201: The terminal 110 sends a first message to the first network element 121.

[0274] In some embodiments, terminal 110 may send a first message.

[0275] In some embodiments, the explanation of the first message can refer to the explanation in the embodiment of Figure 2A, which will not be repeated here.

[0276] In some embodiments, the explanation of the first model can refer to the explanation in the embodiment of Figure 2A, which will not be repeated here.

[0277] In some embodiments, the terminal 110 may send a first message to the first network element 121 .

[0278] In some embodiments, the first network element 121 may receive a first message sent by the terminal 110 .

[0279] In some embodiments, the terminal 110 sends the first message to the first network element 121 in order to register the first model and / or the first function with the second network element 122 .

[0280] In some embodiments, the terminal 110 may register the first model and / or the first function with the second network element 122 .

[0281] In some embodiments, the terminal 110 may send a first message to the first network element 121 in order to register the first model and / or the first function with the second network element 122 .

[0282] Exemplarily, the first message may be any one of the following: a third request message; wherein the third request message is a positioning request message sent to the first network element 121 in the MO-LR Procedure; a location result message; wherein the second positioning request message is a location notification return result message sent to the first network element 121 in the MT-LR Procedure.

[0283] Exemplarily, in the MO-LR Procedure, the first message is a third request message, and the terminal 110 includes information about the first model and / or first function that the terminal 110 needs to register in the third request message sent to the first network element 121 .

[0284] Exemplarily, in the MO-LR Procedure, the first network element 121 may receive the third request information sent by the terminal 110 .

[0285] Exemplarily, in the MO-LR Procedure, the terminal 110 includes information about the first model and / or first function that the terminal 110 needs to register in a third request message sent to the first network element 121 , and the first network element 121 may receive the third request information sent by the terminal 110 .

[0286] In some embodiments, first network element 121 may send a second message to terminal 110, where the second message may be used to request terminal 110 to perform model and / or function registration. Exemplarily, the second message may be a NAS message for positioning sent by first network element 121 during a positioning process. Exemplarily, the second message may be a NAS message for positioning sent by first network element 121 during an MT-LR procedure.

[0287] In some embodiments, the terminal 110 may receive a second message sent by the first network element 121 .

[0288] In some embodiments, the terminal 110 may send the first message to the first network element 121 after receiving the second message sent by the first network element 121 .

[0289] Exemplarily, in the MT-LR Procedure, the first message is a location result message, and the terminal 110 sends information about the first model and / or first function to be registered to the first network element 121 via the location result message. Exemplarily, the location result message may be a NAS location notification return result message.

[0290] Exemplarily, in the MT-LR Procedure, the first network element 121 may receive information about the first model and / or first function that needs to be registered, sent by the terminal 110 via a location result message. Exemplarily, the location result message may be a NAS location notification return result message.

[0291] Exemplarily, in the MT-LR Procedure, the first network element 121 may request the terminal 110 to send information about the first model and / or first function that needs to be registered through a second message. Exemplarily, the second message may be a NAS location notification return invoke request message.

[0292] For example, in the MT-LR Procedure, the first network element 121 may request the terminal 110 to send information about the first model and / or first function that needs to be registered through a second message. After receiving the second message, the terminal 110 may send information about the first model and / or first function that needs to be registered to the first network element 121 through a location result message.

[0293] In some embodiments, the first network element may be an AMF, or other network element that can register a model, which is not limited in this application.

[0294] In some embodiments, the terminal 110 may register the first model and / or the first function with the second network element 122 .

[0295] In some embodiments, the terminal 110 may send a first message to the second network element 122. Exemplarily, the first message may be any one of the following: an LPP message; or an LPP provisioning capability message.

[0296] In some embodiments, the explanation of the first message can refer to the explanation in the embodiment of Figure 2A, which will not be repeated here.

[0297] In some embodiments, the explanation of the first model and / or the first function can refer to the explanation in the embodiment of Figure 2A, which will not be repeated here.

[0298] In some embodiments, the second network element 122 may receive the first message sent by the terminal 110. In some embodiments, the terminal 110 may receive a model and / or function registration request message from the second network element 122, such as an LPP request capability message.

[0299] In some embodiments, the second network element 122 sends a model and / or function registration request message to the terminal 110, such as an LPP request capability message.

[0300] In some embodiments, after receiving the model and / or function registration request message sent by the second network element 122 , the terminal 110 sends a first message to the second network element 122 .

[0301] In some embodiments, the first network element 121 may transparently forward the first message sent by the terminal 110 to the second network element 122 .

[0302] In some embodiments, the second network element 122 may be a LMF, or other network element that manages positioning functions, which is not limited in this application.

[0303] Step S2202 : The first network element 121 sends a sixth message to the second network element 122 .

[0304] In some embodiments, the first network element 121 may send a sixth message to the second network element 122, wherein the sixth message includes information about the first model and / or first function that the terminal 110 needs to register, and the second network element 122 receives the sixth message sent by the first network element 121.

[0305] In some embodiments, if the terminal 110 registers a model with the second network element 122, during the positioning process, the first network element 121 may send a sixth message to the second network element 122. For example, the positioning process may be an MO-LR procedure. For example, the positioning process may be an MT-LR procedure.

[0306] In some embodiments, during the positioning process, the second network element 122 may receive the sixth message sent by the first network element 121. For example, the positioning process may be an MO-LR procedure. For example, the positioning process may be an MT-LR procedure.

[0307] For example, in the MO-LR Procedure, the sixth message sent by the first network element 121 to the second network element 122 may be an Nlmf_Location_DetermineLocation request message. That is, in the MO-LR Procedure, the first network element 121 may send information about the first model and / or first function that the terminal 110 needs to register to the second network element 122 through the Nlmf_Location_DetermineLocation request message.

[0308] For example, in the MT-LR Procedure, the sixth message sent by the first network element 121 to the second network element 122 may be an Nlmf_Location_DetermineLocation request message. That is, in the MT-LR Procedure, the first network element 121 may send information about the first model and / or first function that the terminal 110 needs to register to the second network element 122 through the Nlmf_Location_DetermineLocation request message.

[0309] In some embodiments, the second network element may be an LMF or other network element, without limitation.

[0310] Step S2203 : The second network element 122 sends a seventh message to the first network element 121 .

[0311] In some embodiments, the second network element 122 may send a seventh message to the first network element 121 , wherein the seventh message may include a registration result of the first model and / or the first function.

[0312] In some embodiments, during the positioning procedure, the second network element 122 may send the seventh message to the first network element 121. For example, the positioning procedure may be an MO-LR Procedure. For example, the positioning procedure may be an MT-LR Procedure.

[0313] Illustratively, in the MO-LR Procedure, the seventh message sent by the second network element 122 to the first network element 121 may be an Nlmf_Location_DetermineLocation response. That is, in the MO-LR Procedure, the second network element 122 may send the registration result of the first model and / or the first function to the first network element 121 via the Nlmf_Location_DetermineLocation response.

[0314] Exemplarily, in the MT-LR Procedure, the seventh message sent by the second network element 122 to the first network element 121 may be Nlmf_Location_DetermineLocation response. That is, in the MT-LR Procedure, the second network element 122 may send the registration result of the first model and / or the first function to the first network element 121 via Nlmf_Location_DetermineLocation response.

[0315] In some embodiments, the first network element 121 may send a third message to the terminal 110. The third message may include a registration result of the first model and / or the first function. Specific explanations can be found in the above embodiments, so they are not repeated here.

[0316] In some embodiments, the terminal 110 may receive the third message sent by the first network element 121. Specific explanations can be found in the above embodiments, so they will not be repeated here.

[0317] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2203. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, step S2201 and step S2202 can be implemented as independent embodiments, step S2202 and step S2203 can be implemented as independent embodiments, and steps S2201, S2202, and S2203 can be implemented as independent embodiments, but are not limited thereto.

[0318] In some embodiments, one or more of these steps may be omitted or replaced in different embodiments.

[0319] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0320] FIG3A is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a model registration method for terminal 110, the method comprising:

[0321] Step S3101, sending the first message.

[0322] In some embodiments, the terminal 110 may send the first message to the first network element 121 , but is not limited thereto and may also send the first message to other entities.

[0323] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0324] In some embodiments, the terminal 110 may receive a first message sent by the first network element 121 , but is not limited thereto and may also receive a first message sent by other entities.

[0325] Step S3102, obtain the third message.

[0326] In some embodiments, the terminal 110 may receive the third message sent by the first network element 121 , but is not limited thereto and may also receive the third message sent by other entities.

[0327] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0328] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0329] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, or both steps S3101 and S3102 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0330] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0331] FIG3B is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a model registration method for terminal 110, the method comprising:

[0332] Step S3201: Receive indication information sent by the first network element.

[0333] The optional implementation of step S3201 can be found in step S2102 of FIG. 2A and other related parts of the embodiment involved in 2A, which will not be described again here.

[0334] Step S3202: Send a first message to the first network element.

[0335] The optional implementation of step S3202 can be found in step S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0336] Step S3203: Receive the third message sent by the first network element.

[0337] The optional implementation of step S3203 can be found in step S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0338] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, step S3203 can be implemented as an independent embodiment, step S3201 and step S3202 can be implemented as independent embodiments, step S3202 and step S3203 can be implemented as independent embodiments, step S3201 and step S3203 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0339] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0340] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0341] FIG3C is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a model registration method for terminal 110, the method comprising:

[0342] Step S3301: Receive a second message sent by a first network element.

[0343] The optional implementation of step S3301 can be found in step S2101 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0344] Step S3302: Send a first message to the first network element.

[0345] The optional implementation of step S3302 can be found in step S2101 of FIG. 2 and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here.

[0346] Step S3303: Receive the third message sent by the first network element.

[0347] The optional implementation of step S3303 can be found in step S2102 of FIG. 2 and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here.

[0348] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, step S3303 can be implemented as an independent embodiment, steps S3301 and S3302 can be implemented as independent embodiments, steps S3302 and S3303 can be implemented as independent embodiments, steps S3301 and S3303 can be implemented as independent embodiments, steps S3301, S3302, and S3303 can be implemented as independent embodiments, but are not limited thereto.

[0349] In some embodiments, step S3301 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0350] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0351] FIG3D is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a model registration method for terminal 110, the method comprising:

[0352] Step S3401, sending the first message.

[0353] The optional implementation of step S3401 can be found in step S2101 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0354] In some embodiments, the terminal 110 may send the first message to the first network element, but is not limited thereto and may also send the first message to other entities.

[0355] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0356] FIG4A is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0357] Step S4101, obtain the first message.

[0358] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0359] In some embodiments, the first network element 121 may receive a first message sent by the terminal 110 , but is not limited thereto and may also receive a first message sent by a subject.

[0360] Step S4102, sending a third message.

[0361] The optional implementation of step S4101 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0362] In some embodiments, the first network element 121 may send the third message to the terminal 110 , but is not limited thereto and may also send the third message to the subject.

[0363] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, or both steps S4101 and S4102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0364] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0365] FIG4B is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0366] Step S4201, obtain the first message.

[0367] The optional implementation of step S4201 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0368] Step S4202, sending the sixth message.

[0369] The optional implementation of step S4202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0370] Step S4203, obtain the seventh message.

[0371] The optional implementation of step S4203 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0372] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 can be implemented as an independent embodiment, step S4202 can be implemented as an independent embodiment, step S4203 can be implemented as an independent embodiment, step S4201 and step S4202 can be implemented as independent embodiments, step S4202 and step S4203 can be implemented as independent embodiments, and step S4201, step S4202, and step S4203 can be implemented as independent embodiments, but are not limited thereto.

[0373] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0374] FIG4C is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0375] Step S4301: Send instruction information to the terminal.

[0376] The optional implementation of step S4301 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0377] Step S4302: Receive the first message sent by the terminal.

[0378] The optional implementation of step S4302 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0379] Step S4303: Send a third message to the terminal.

[0380] The optional implementation of step S4303 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0381] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S4301 to S4303. For example, step S4301 can be implemented as an independent embodiment, step S4302 can be implemented as an independent embodiment, step S4303 can be implemented as an independent embodiment, step S4301 and step S4302 can be implemented as independent embodiments, step S4302 and step S4303 can be implemented as independent embodiments, and step S4301, step S4302, and step S4303 can be implemented as independent embodiments, but are not limited thereto.

[0382] In some embodiments, step S4301 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0383] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0384] FIG4D is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4D , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0385] Step S4401: Receive a first message sent by a terminal.

[0386] The optional implementation of step S4401 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0387] Step S4402: Send a third message to the terminal.

[0388] The optional implementation of step S4402 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0389] Step S4403: Send a fourth message to the second network element.

[0390] The optional implementation of step S4403 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0391] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S4401 to S4403. For example, step S4401 can be implemented as an independent embodiment, step S4402 can be implemented as an independent embodiment, step S4403 can be implemented as an independent embodiment, step S4401 and step S4402 can be implemented as independent embodiments, step S4402 and step S4403 can be implemented as independent embodiments, step S4401 and step S4403 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0392] In some embodiments, step S4403 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0393] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0394] FIG4E is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4E , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0395] Step S4501: Receive a first message sent by a terminal.

[0396] The optional implementation of step S4501 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0397] Step S4502: Send a sixth message to the second network element.

[0398] The optional implementation of step S4502 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0399] Step S4503: Receive the seventh message sent by the second network element.

[0400] The optional implementation of step S4503 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0401] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S4501 to S4503. For example, step S4501 can be implemented as an independent embodiment, step S4502 can be implemented as an independent embodiment, step S4503 can be implemented as an independent embodiment, step S4501 and step S4502 can be implemented as independent embodiments, step S4502 and step S4503 can be implemented as independent embodiments, step S4501 and step S4503 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0402] In some embodiments, step S4503 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0403] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0404] FIG4F is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4F , the embodiment of the present disclosure relates to a model registration method for a first network element 121, the method comprising:

[0405] Step S4601: Receive a first message sent by a terminal.

[0406] The optional implementation of step S4603 can refer to the optional implementation of step S2101 in Figure 2A, the optional implementation of step S2201 in 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0407] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0408] 5A is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG5A , an embodiment of the present disclosure relates to a model registration method for a second network element 122, the method comprising:

[0409] Step S5101, obtain the sixth message.

[0410] The optional implementation of step S5101 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0411] In some embodiments, the second network element 122 may receive the sixth message sent by the first network element 121 , but is not limited thereto and may also receive the sixth message sent by the subject.

[0412] Step S5102, sending the seventh message.

[0413] The optional implementation of step S5102 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0414] In some embodiments, the second network element 122 may send the seventh message to the first network element 121 , but is not limited thereto and may also send the seventh message to the subject.

[0415] The model registration method involved in the embodiments of the present disclosure may include at least one of steps S5101 and S5102. For example, step S5101 may be implemented as an independent embodiment, step S5102 may be implemented as an independent embodiment, or both steps S5101 and S5102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0416] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0417] FIG5B is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a model registration method for the second network element 122, the method comprising:

[0418] Step S5201: Receive the sixth message sent by the first network element.

[0419] The optional implementation of step S5201 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0420] The model registration method involved in the embodiment of the present disclosure may include step S5201.

[0421] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0422] FIG5C is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG5C , the embodiment of the present disclosure relates to a model registration method for the second network element 122, the method comprising:

[0423] Step S5301: Receive the fourth message sent by the first network element.

[0424] The optional implementation of step S5301 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0425] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0426] FIG5D is a flow chart of a model registration method according to an embodiment of the present disclosure. As shown in FIG5D , the embodiment of the present disclosure relates to a model registration method for the second network element 122, the method comprising:

[0427] Step S5401, receiving a first message.

[0428] The optional implementation of step S5401 can refer to the optional implementation of step S2102 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0429] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0430] The embodiment of the present disclosure also proposes a model registration method. The model registration method is used in a communication system 100, which may include a terminal 110 and a first network element 121, wherein the terminal 110 may be used to execute the model registration method applied to the terminal 110, and the first network element 121 may be used to execute the model registration method applied to the first network element 121.

[0431] The present disclosure also provides a model registration method for use in a communication system 100, which may include a terminal 110, a first network element 121, and a second network element 122. The terminal 110 may be configured to execute the model registration method applied to the terminal 110, the first network element 121 may be configured to execute the model registration method applied to the first network element 121, and the second network element 122 may be configured to execute the model registration method applied to the second network element 122.

[0432] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, first network element side, second network element side, etc., which will not be repeated here.

[0433] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0434] The following is an exemplary introduction to the above method.

[0435] 1. A registration / identification process of an AI model / AI function, comprising: the UE registering / identifying the AI ​​model / AI function with the AMF; the UE registering / identifying the AI ​​model / AI function with the LMF.

[0436] Optionally, the registration process is used to register / identify the AI ​​model / AI function, as described in points 2, 3, and 4 below.

[0437] 2. The UE registers / identifies the AI ​​model / AI function with the AMF, including registering / identifying the AI ​​model / AI function during the registration procedure with the network.

[0438] 3. Based on 2, the UE includes the AI ​​function / AI model that the UE needs to register / identify in the registration request message (registration request); the base station includes the AI ​​function / AI model that the UE needs to register / identify sent by the UE in the registration request message sent to the AMF.

[0439] 4. AMF includes the AI ​​function / AI model that was successfully registered / identified in the registration accept message.

[0440] Optionally, the UE triggered service request process is used to register / identify the AI ​​model / AI function, as described in points 5, 6, 7, and 8 below.

[0441] 5. The UE registers / identifies the AI ​​model / AI function with the AMF, including the UE registering / identifying the AI ​​model / AI function during the UE-triggered service request process.

[0442] 6. Based on 5, the UE includes the AI ​​function / AI model that the UE needs to register / identify in the service request message (service request); the base station includes the AI ​​function / AI model that the UE needs to register / identify sent by the UE in the service request (service request) message sent to the AMF.

[0443] 7. AMF includes the AI ​​function / AI model that was successfully registered / identified in the N2 request message (N2 request).

[0444] 8. The gNB sends the successfully registered / identified AI function / AI model to the UE, for example, via an RRC reconfiguration message. Optionally, the registration / identification of the AI ​​model / AI function is implemented using a network triggered service request procedure.

[0445] Optionally, the network triggered service request process is used to register / identify the AI ​​model / AI function, as described in points 9, 10, 11, 12 and 13 below.

[0446] 9. Based on 1, the AMF instructs the UE to register / identify the AI ​​model / AI function in the paging message sent to the base station.

[0447] 10. The base station sends a paging message to the UE to instruct the UE to register / identify the AI ​​model / AI function.

[0448] 11. Based on 10, the UE needs to register / identify the AI ​​function / AI model in the service request message.

[0449] 12. The message sent by the UE indicating the AI ​​model / AI function that the UE needs to register / identify also includes the function of the AI ​​model / AI function (e.g., obtaining UE location, obtaining NLOS / LOS indication of multipath, obtaining measurement results), structure, and parameters (e.g., gradient, weight matrix); for example, registration request, service request;

[0450] 13. The AMF / gNB sends the AI ​​function / AI model that has been successfully registered / identified to the UE, including the AI ​​function / AI model ID; for example, registration accept, N2 request, RRC reconfiguration.

[0451] Optionally, the MO-LR Procedure is used to register / identify the AI ​​model / AI function, as described in points 14, 15, 16, 17, and 18 below.

[0452] 14. In the MO-LR Procedure, the AMF sends the AI ​​function / AI model successfully registered / identified by the UE to the LMF.

[0453] 15. The AI ​​function / AI model successfully registered / identified by the UE includes the AI ​​function / AI model successfully registered and identified between the UE and the AMF.

[0454] 16. The UE includes the AI ​​function / AI model that the UE needs to register / identify in the MO-LR request message sent to the AMF.

[0455] 17. The AMF sends the Nlmf_Location_DetermineLocation request message to the LMF, which specifies the AI ​​function / AI model that the UE needs to register / identify; it may also include the AI ​​function / model ID.

[0456] 18. LMF sends an indication of successful registration of the UE’s AI model / function to AMF, for example, via Nlmf_Location_DetermineLocation response.

[0457] Optionally, the MT-LR / deferred MT-LR / Low Power Periodic and Triggered 5GC-MT-LR Procedures are used to implement / identify AI models / AI functions, as described in points 19, 20, 21, 22, 23 and 24 below.

[0458] 19. During the above positioning process, the AMF sends the AI ​​function / AI model successfully registered / identified by the UE to the LMF.

[0459] 20. The AI ​​function / AI model successfully registered / identified by the UE includes the AI ​​function / AI model successfully registered and identified between the UE and the AMF.

[0460] 21. Or (relative to 20), the UE sends the AI ​​function / AI model that needs to be registered / identified to the AMF during the positioning process, for example, through a NAS location notification return result message.

[0461] 22. Based on 21, the AMF requests the UE to send a message to register / identify the AI ​​function / model through a NAS message, for example, through a NAS location notification return invoke request message.

[0462] 23. The AMF sends the Nlmf_Location_DetermineLocation request message to the LMF, which specifies the AI ​​function / AI model that the UE needs to register / identify; it may also include the AI ​​function / model ID.

[0463] 24. LMF sends an indication of successful registration of the UE’s AI model / function to AMF, for example, via Nlmf_Location_DetermineLocation response.

[0464] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0465] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0466] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0467] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0468] Figure 6A is a structural diagram of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 6A, the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the above-mentioned transceiver module is used to send a first message; wherein, the first message includes information about the first model and / or first function that the terminal needs to register. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step S2101, but not limited to this) performed by the terminal 110 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps performed by the terminal 110 in any of the above methods, which will not be repeated here.

[0469] Figure 6B is a schematic diagram of the structure of the first network element proposed in an embodiment of the present disclosure. As shown in Figure 6B, the first network element 6200 may include: at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the above-mentioned transceiver module is used to receive a first message; wherein, the first message includes information about the first model and / or first function that the terminal needs to register. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S4301, but not limited to this) performed by the first network element 121 in any of the above methods, which will not be repeated here.

[0470] Figure 6C is a schematic diagram of the structure of the second network element proposed in an embodiment of the present disclosure. As shown in Figure 6C, the second network element 6300 may include: at least one of a transceiver module 6301, a processing module 6302, etc. In some embodiments, the above-mentioned transceiver module is used to receive a first message; wherein, the first message includes information about the first model and / or first function that the terminal needs to register. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S5201, step S5202, but not limited to this) performed by the second network element 122 in any of the above methods, which will not be repeated here.

[0471] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0472] In some embodiments, the processing module can be a single module or include multiple submodules. Optionally, the multiple submodules each execute all or part of the steps required to be executed by the processing module. Optionally, the processing module and the processor can be interchangeable.

[0473] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), or a chip, chip system, or processor that supports the network device to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0474] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 7100 is used to perform any of the above methods.

[0475] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0476] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, but not limited thereto), and the processor 7101 performs at least one of the other steps.

[0477] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0478] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0479] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0480] 7B is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7200 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0481] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.

[0482] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.

[0483] In some embodiments, the interface circuit 7202 executes at least one of the communication steps such as sending and / or receiving in the above method (such as step S2101, but not limited thereto), and the processor 7201 executes at least one of the other steps.

[0484] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0485] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0486] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 7100, causes the communication device 7100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0487] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0488] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A model registration method, characterized in that: Executed by a terminal, the method includes: A first message is sent, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

2. The method according to claim 1, wherein The first message is any one of the following: Registration request message; A first request message, wherein the first request message is a service request message in a service request process triggered by the terminal; A second request message, wherein the second request message is a service request message in a service request process triggered by the first network element.

3. The method according to claim 1 or 2, wherein: The method further comprises: Receive indication information sent by the first network element, where the indication information is used to instruct the terminal to perform model and / or function registration.

4. The method according to claim 3, wherein The method further comprises: A first paging message sent by an access network device is received, wherein the first paging message includes the indication information, and the indication information in the first paging message is sent by the first network element to the access network device through a second paging message.

5. The method according to claim 1, wherein The first message is any one of the following: a third request message, wherein the third request message is a positioning request message sent to the first network element in a mobile-initiated positioning request procedure MO-LR Procedure; The location result message is a location notification return result message sent to the first network element in the mobile terminated location request process MT-LR Procedure.

6. The method according to claim 1 or 5, wherein: Also includes: A second message sent by the first network element is received, wherein the second message is used to request the terminal to perform model and / or function registration.

7. The method according to claim 6, wherein The second message is a non-access stratum (NAS) message for positioning sent by the first network element during the positioning process.

8. The method according to any one of claims 1 to 7, wherein Also includes: Receive a third message sent by the first network element, wherein the third message includes a registration result of the first model and / or the first function.

9. The method according to claim 8, wherein The method further comprises: Receive a radio resource control RRC reconfiguration message sent by an access network device, wherein the RRC reconfiguration message includes a registration result of the first model and / or the first function, and the registration result in the RRC reconfiguration message is sent by the first network element to the access network device through an N2 request message.

10. The method according to claim 8, wherein The first message is a registration request message, and the third message is a registration acceptance message.

11. The method according to any one of claims 8 to 10, wherein: The registration result includes at least one of the following: Information of the model that is successfully registered in the first model; Information of the model that failed to be registered in the first model; Information about the successfully registered functions in the first function; Information about the function that failed to be registered among the first functions.

12. The method according to any one of claims 1 to 11, wherein The information of the first model and / or the first function includes at least one of the following: an identifier of the first model; Functions of the first model; the structure of the first model; parameters of the first model; An identifier of the first function.

13. A model registration method, characterized in that: Executed by a first network element, the method includes: A first message is received, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

14. The method according to claim 13, wherein The first message is any one of the following: Registration request message; A first request message, wherein the first request message is a service request message in a service request process triggered by the terminal; A second request message, wherein the second request message is a service request message in a service request process triggered by the first network element.

15. The method according to claim 14, wherein The method further comprises: Sending instruction information to the terminal, wherein the instruction information is used to instruct the terminal to perform model and / or function registration.

16. The method according to any one of claims 13 to 15, wherein: The method further comprises: The indication information is sent to the terminal through an access network device.

17. The method according to claim 16, wherein The method further comprises: Sending a second paging message to the access network device, wherein the second paging message includes the indication information.

18. The method according to any one of claims 13 to 17, wherein: Also includes: A fourth message is sent to the second network element, wherein the fourth message includes information about the successfully registered second model and / or second function.

19. The method according to claim 18, wherein The sending the fourth message to the second network element includes: During the positioning process, the fourth message is sent to the second network element.

20. The method of claim 18, wherein: The method further comprises: Receive a fifth message sent by the second network element, wherein the fifth message is used to request information about the model and / or function of successful registration of the terminal.

21. The method according to claim 13, wherein The first message is any one of the following: a third request message, wherein the first positioning request message is a positioning request message in an MO-LR Procedure; Position result message, wherein the second positioning request message is a position notification return result message in the MT-LR Procedure.

22. The method according to claim 13 or 21, wherein: The method further comprises: A second message is sent to the terminal, wherein the second message is used to request the terminal to perform model and / or function registration.

23. The method according to claim 22, wherein The second message is a non-access stratum (NAS) message for positioning sent by the first network element during the positioning process.

24. The method according to any one of claims 21 to 23, wherein Also includes: Send information about the first model and / or the first function that the terminal needs to register to the second network element.

25. The method according to any one of claims 21 to 24, wherein Also includes: Receive a registration result of the first model and / or the first function sent by a second network element.

26. The method according to any one of claims 13 to 25, wherein Also includes: A third message is sent to the terminal, wherein the third message includes a registration result of the first model and / or the first function.

27. The method according to claim 26, wherein The method further comprises: Send an N2 request message to the access network device, wherein the N2 request message includes the first model and / or the registration result of the first model.

28. The method according to any one of claims 25 to 27, wherein The first model and / or the registration result of the first model includes at least one of the following: Information of the model that is successfully registered in the first model; Information of the model that failed to be registered in the first model; Information about the successfully registered functions in the first function; Information about the function that failed to be registered among the first functions.

29. The method according to any one of claims 13 to 28, wherein The information of the first model and / or the first function includes at least one of the following: an identifier of the first model; Functions of the first model; the structure of the first model; parameters of the first model; An identifier of the first function.

30. A model registration method, characterized in that: Executed by the second network element, the method includes: A first message is received, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

31. The method of claim 30, wherein: The receiving of the first message includes: Receive the first message sent by the terminal or the first network element.

32. The method according to claim 30 or 31, wherein The method further comprises: Sending a registration result of the first model and / or the first function to the first network element.

33. The method of claim 32, wherein: The registration result includes at least one of the following: Information of the model that is successfully registered in the first model; Information of the model that failed to be registered in the first model; Information about the successfully registered functions in the first function; Information about the function that failed to be registered among the first functions.

34. The method according to any one of claims 30 to 33, wherein The information of the first model and / or the first function includes at least one of the following: an identifier of the first model; Functions of the first model; the structure of the first model; parameters of the first model; An identifier of the first function.

35. A terminal, characterized in that: include: The transceiver module is used to send a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

36. A first network element, characterized in that: include: The transceiver module is used to receive a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

37. A second network element, characterized in that: include: The transceiver module is used to receive a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register.

38. A terminal, characterized in that: include: one or more processors; Wherein, the terminal is used to execute the model registration method according to any one of claims 1-12.

39. A first network element, characterized in that: include: one or more processors; Wherein, the first network element is used to execute the model registration method described in any one of claims 13-29.

40. A second network element, characterized in that: include: one or more processors; Wherein, the second network element is used to execute the model registration method described in any one of claims 30-34.

41. A communication device, characterized in that: include: one or more processors; Wherein, the processor is used to execute the model registration method according to any one of claims 1-34.

42. A communication system, characterized in that include: A terminal, a first network element and a second network element, wherein: The terminal sends a first message, wherein the first message includes information about a first model and / or a first function that the terminal needs to register; The first network element or the second network element receives the first message.

43. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the model registration method according to any one of claims 1-12, 13-29, and 30-34.

Images