Information processing method, communication device, communication system and storage medium

Abstract

Provided in the embodiments of the present disclosure are an information processing method, a communication device, a communication system and a storage medium. The information processing method is executed by a first network function, and comprises: receiving first information sent by a terminal, wherein the first information is used for indicating that the terminal supports at least one service or that the terminal does not support a service; and sending second information to a second network function, wherein the second information is used for requesting the management of the service supported by the terminal.

Description

Information processing methods, communication equipment, communication systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an information processing method, communication device, communication system and storage medium. Background Technology

[0002] In the field of communication technology, there is a growing demand for services that require data processing within communication systems. For example, terminals, core network equipment, and access network equipment are supporting an increasing number of new services that require processing. Furthermore, service-based architectures can be applied to terminals, core network equipment, and access network equipment to support these data processing services within the communication system.

[0003] Summary of the Invention

[0004] The embodiments disclosed herein aim to address the technical problem of the lack of management of services provided by service-based terminals in the network.

[0005] According to a first aspect of the present disclosure, an information processing method is proposed, executed by a first network function, comprising: receiving first information sent by a terminal, wherein the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support a service; and sending second information to a second network function, wherein the second information is used to request management of services supported by the terminal.

[0006] According to a second aspect of the present disclosure, an information processing method is proposed, executed by a terminal, comprising: sending first information to a first network function, wherein the first information is used to indicate: at least one service supported by the terminal, or that the terminal does not support a service; wherein the first information is used by the first network function to send second information to a second network function, the second information being used to request management of services supported by the terminal.

[0007] According to a third aspect of the present disclosure, an information processing method is proposed, executed by a second network function, comprising: receiving second information sent by a first network function, wherein the second information is used to request services supported by a management terminal; wherein the second information is sent by the first network function based on first information, and the first information is used to indicate that: the terminal supports at least one service, or that the terminal does not support a service.

[0008] According to a fourth aspect of the present disclosure, an information processing method is proposed, comprising: a terminal sending first information to a first network function, wherein the first information is used to indicate that: the terminal supports at least one service, or that the terminal does not support a service; and the first network function sending second information to a second network function, wherein the second information is used to request management of services supported by the terminal.

[0009] According to a fifth aspect of the present disclosure, a first network function is provided, comprising: a first transceiver module configured to receive first information sent by a terminal, wherein the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support a service; and sending second information to a second network function, wherein the second information is used to request management of services supported by the terminal.

[0010] According to a sixth aspect of the present disclosure, a terminal is provided, comprising: a second transceiver module configured to send first information to a first network function, wherein the first information is used to indicate: at least one service supported by the terminal, or that the terminal does not support a service; wherein the first information is used by the first network function to send second information to a second network function, the second information being used to request management of services supported by the terminal.

[0011] According to a seventh aspect of the present disclosure, a second network function is provided, comprising: a third transceiver module configured to receive second information sent by a first network function, wherein the second information is used to request services supported by a management terminal; wherein the second information is sent by the first network function based on first information, and the first information is used to indicate that: the terminal supports at least one service, or that the terminal does not support a service.

[0012] According to an eighth aspect of the embodiments of this disclosure, a communication device is provided, which is used to perform an optional implementation of the first aspect, the second aspect, the third aspect, the fourth aspect, or the first aspect, the second aspect, the third aspect, and the fourth aspect.

[0013] According to a ninth aspect of the present disclosure, a communication system is provided, comprising: a first network function, a terminal, and a second network function; wherein the first network function is configured to perform a method as described in an optional implementation of the first aspect, the terminal is configured to perform a method as described in an optional implementation of the second aspect, and the second network function is configured to perform a method as described in an optional implementation of the third aspect.

[0014] According to a tenth aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, or an optional implementation of the first aspect, the second aspect, the third aspect, and the fourth aspect.

[0015] According to the eleventh aspect of the present disclosure, a computer program product is provided, the computer program product including a computer program or instructions, which, when executed by a processor, implement the methods described in the first aspect, second aspect, third aspect, fourth aspect, or optional implementations of the first aspect, second aspect, third aspect, and fourth aspect.

[0016] The embodiments disclosed herein enable the network to perform service management on service-based terminal services, so that the services provided by the terminal can be discovered and / or consumed (e.g., invoked) by network functions in the core network. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0018] Figure 1 is a schematic diagram of the structure of an information processing system according to an embodiment of the present disclosure.

[0019] Figure 2 is an interactive schematic diagram of an information processing method according to an embodiment of the present disclosure.

[0020] Figure 3 is an interactive schematic diagram of an information processing method according to an embodiment of the present disclosure.

[0021] Figure 4A is a schematic flowchart illustrating an information processing method according to an embodiment of the present disclosure.

[0022] Figure 4B is a schematic flowchart illustrating an information processing method according to an embodiment of the present disclosure.

[0023] Figure 4C is a schematic flowchart illustrating an information processing method according to an embodiment of the present disclosure.

[0024] Figure 5A is a schematic diagram of the structure of a first network function according to an embodiment of the present disclosure.

[0025] Figure 5B is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure.

[0026] Figure 5C is a schematic diagram of the structure of a second network function according to an embodiment of the present disclosure.

[0027] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0028] Figure 6B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0029] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium.

[0030] This disclosure provides an information processing method executed by a first network function, comprising: receiving first information sent by a terminal, wherein the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support a service; and sending second information to a second network function, wherein the second information is used to request the management of services supported by the terminal.

[0031] In the above embodiments, the first network function can obtain the support service capabilities provided by the terminal and request the second network function to manage the support services provided by the terminal, thereby enabling the second network function to manage the services provided by the terminal. This facilitates the discovery and / or invocation of services provided by the UE by network functions in the core network. Since the terminal does not know the addresses of many network functions in the core network, the first network function in the core network needs to send the information of the services provided by the terminal to the second network function in the core network. In other words, the first network function can send the service capabilities provided by the terminal to the second network function to request the second network function to manage the services provided by the terminal.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the service includes a first service or a second service, the first information is used to indicate that the terminal supports at least one first service, and the second information is used to request one of the following: register at least one second service supported by the terminal, update at least one second service supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes a portion of the second service; or, the first information is used to indicate that the terminal does not support at least one first service, and the second information is used to request the revocation of the second service registered by the terminal; or, the first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

[0033] In the above embodiments, for the registration or updating of services provided by the terminal, the second network function can register or update at least some of the services provided by the terminal. This allows for flexible registration or updating of services provided by the terminal when the capabilities of previously received supported services change compared to the current capabilities of services supported by the terminal. Alternatively, the second network function can register or update not only the services provided by the terminal but also previously provided services by the terminal, thereby enabling the management of previously registered or updated services and unified management of services supported by each terminal. Alternatively, for the deregistration of services provided by the terminal, the first network function can deregister one or more specified services provided by the terminal. Alternatively, if the first network function does not specify the deregistration of one or more specified services but instructs the deregistration of all terminal services, it can deregister all terminal services. This provides more ways to deregister terminal services, thus adapting to more application scenarios.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the service includes at least one of the following: data detection supporting at least one service; data processing supporting at least one service; data collection supporting at least one service; data distribution supporting at least one service; data management supporting at least one service; and service management supporting at least one service.

[0035] In the above embodiments, it is clear what services the terminal provides, that is, it is clear that the terminal implements service-oriented functions, etc.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes: a first identifier, wherein the first identifier is used to indicate a terminal; and / or, the second information includes at least one of the following: the first identifier; a third service, wherein the third service is used to manage services supported by the terminal.

[0037] In the above embodiments, the second information includes a first identifier, which enables the second network function to know which terminal is providing the service to be managed, and facilitates the second network function to store the service that needs to be managed by the terminal accordingly; or, the second information includes a third service, which enables the second network function to know what kind of management service needs to be performed, so that the second network function can manage the service provided by the terminal.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes: third information, which is used to indicate whether the terminal supports the first service or does not support the first service; and / or, the second information includes: fourth information, which is used to indicate whether the terminal supports the second service or does not support the second service; or, the third service includes the fourth information.

[0039] In the above embodiments, the first information and / or the second information carry information about the services provided by the terminal, or the third service included in the first information carries information about the services provided by the terminal, thereby providing multiple ways to inform the second network function which services are provided by the terminal. This allows for flexible notification of the services provided by the terminal that the second network function needs to manage, adapting to more application scenarios.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the third service includes at least one of the following: a first sub-service, wherein the first sub-service is used to request registration of a first service supported by the terminal; a second sub-service, wherein the second sub-service is used to request updates to the first service supported by the terminal; and a third sub-service, wherein the third sub-service is used to request the revocation of the first service or all services supported by the terminal.

[0041] In the above embodiments, the second network function can know what the service management requested by the terminal is, such as service management for service registration, update or deregistration of the terminal.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, before sending the second information to the second network function, at least one of the following is included: determining the second network function; determining a third service based on the first information; and determining the second information based on the third service.

[0043] In the above embodiments, the first network function can determine the second network function, thereby accurately knowing which second network function should manage the services provided by the terminal; and based on this, it can also determine the management request for managing the services provided by the terminal, so that the second network function can subsequently manage the services provided by the terminal.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, sending second information to a second network function includes at least one of the following: the second network function is a third network function, and the second information is sent to the third network function; the second network function is a fourth network function, and the second information is sent to the fourth network function through the third network function; the second network function is a fourth network function, and the second information is sent to the fourth network function.

[0045] In the above embodiments, the second information can be sent from the first network function to the second network function through multiple means, thereby adapting to more application scenarios.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a first response sent by a second network function, wherein the first response is used to indicate the execution result of managing the first service and / or the second service.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the first network function is: access and mobility management function; and / or, the second network function is: service communication proxy, network storage function, or other network functions in the core network other than service communication proxy and network storage function; and / or, the third network function is: service communication proxy; and / or, the fourth network function is: network storage function, or other network functions in the core network other than service communication proxy and network storage function.

[0048] Secondly, embodiments of this disclosure propose an information processing method executed by a terminal, comprising: sending first information to a first network function, wherein the first information is used to indicate: at least one service supported by the terminal, or that the terminal does not support a service; wherein the first information is used by the first network function to send second information to a second network function, the second information being used to request the management of services supported by the terminal.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the service includes a first service or a second service, the first information is used to indicate that the terminal supports at least one first service, and the second information is used to request one of the following: register at least one second service supported by the terminal, update at least one second service supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes at least a portion of the second service; or, the first information is used to indicate that the terminal does not support at least one first service, and the second information is used to request the revocation of the second service registered by the terminal; or, the first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the service includes at least one of the following: data detection supporting at least one service; data processing supporting at least one service; data collection supporting at least one service; data distribution supporting at least one service; data management supporting at least one service; and service management supporting at least one service.

[0051] Thirdly, this disclosure provides an information processing method executed by a second network function, comprising: receiving second information sent by a first network function, wherein the second information is used to request services supported by a management terminal; wherein the second information is sent by the first network function based on first information, and the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support a service.

[0052] In conjunction with some embodiments of the third aspect, in some embodiments, the service includes a first service or a second service, the first information is used to indicate that the terminal supports at least one first service, and the second information is used to request one of the following: register at least one second service supported by the terminal, update at least one second service supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes at least a portion of the second service; or, the first information is used to indicate that the terminal does not support at least one first service, and the second information is used to request the revocation of the second service registered by the terminal; or, the first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

[0053] In conjunction with some embodiments of the third aspect, in some embodiments, the service includes at least one of the following: data detection supporting at least one service; data processing supporting at least one service; data collection supporting at least one service; data distribution supporting at least one service; data management supporting at least one service; and service management supporting at least one service.

[0054] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes: a first identifier, wherein the first identifier is used to indicate a terminal; and / or, the second information includes at least one of the following: the first identifier; a third service, wherein the third service is used to manage services supported by the terminal.

[0055] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes: third information, which is used to indicate whether the terminal supports the first service or does not support the first service; and / or, the second information includes: fourth information, which is used to indicate whether the terminal supports the second service or does not support the second service; or, the third service includes the fourth information.

[0056] In conjunction with some embodiments of the third aspect, in some embodiments, the third service includes at least one of the following: a first sub-service, wherein the first sub-service is used to request registration of a first service supported by the terminal; a second sub-service, wherein the second sub-service is used to request updates to the first service supported by the terminal; and a third sub-service, wherein the third sub-service is used to request the revocation of the first service or all services supported by the terminal.

[0057] In conjunction with some embodiments of the third aspect, in some embodiments, the method includes: determining first management information, wherein the first management information includes: a first identifier and a second service corresponding to the first identifier, the first identifier being used to indicate a terminal; and adding the first identifier and the second service to the second management information.

[0058] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: sending a first response to a first network function, wherein the first response is used to indicate the execution result of managing the first service.

[0059] Fourthly, this disclosure provides an information processing method, comprising: a terminal sending first information to a first network function, wherein the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support a service; and the first network function sending second information to a second network function, wherein the second information is used to request the management of services supported by the terminal.

[0060] Fifthly, embodiments of this disclosure propose a first network function, including: a first transceiver module configured to receive first information sent by a terminal, wherein the first information is used to indicate that: the terminal supports at least one service, or that the terminal does not support a service; and to send second information to a second network function, wherein the second information is used to request the management of services supported by the terminal.

[0061] In a sixth aspect, embodiments of this disclosure provide a terminal, including: a second transceiver module configured to send first information to a first network function, wherein the first information is used to indicate: at least one service supported by the terminal, or that the terminal does not support a service; wherein the first information is used by the first network function to send second information to a second network function, and the second information is used to request management of services supported by the terminal.

[0062] In a seventh aspect, embodiments of this disclosure provide a second network function, including: a third transceiver module configured to receive second information sent by a first network function, wherein the second information is used to request services supported by a management terminal; wherein the second information is sent by the first network function based on the first information, and the first information is used to indicate that: the terminal supports at least one service, or that the terminal does not support a service.

[0063] Eighthly, embodiments of this disclosure provide a communication device for performing the first aspect, the second aspect, the third aspect, the fourth aspect, or optional implementations of the first aspect, the second aspect, the third aspect, and the fourth aspect.

[0064] In a ninth aspect, embodiments of this disclosure provide a communication system, including: a first network function, a terminal, and a second network function; wherein the first network function is configured to perform the method described in the optional implementation of the first aspect, the terminal is configured to perform the method described in the optional implementation of the second aspect, and the second network function is configured to perform the method described in the optional implementation of the third aspect.

[0065] In a tenth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect, second aspect, third aspect, fourth aspect, or optional implementations of the first aspect, second aspect, third aspect, and fourth aspect.

[0066] In one aspect, embodiments of this disclosure provide a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the methods described in the first aspect, second aspect, third aspect, fourth aspect, or optional implementations of the first aspect, second aspect, third aspect, and fourth aspect.

[0067] In a twelfth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the information processing method as described in the first aspect, second aspect, third aspect, fourth aspect, or optional implementations of the first aspect, second aspect, third aspect, and fourth aspect.

[0068] In a thirteenth aspect, embodiments of this disclosure provide a chip or chip system including processing circuitry configured to perform the methods described in accordance with the first, second, third, and fourth aspects, or alternative implementations of the first, second, third, and fourth aspects.

[0069] It is understood that the aforementioned communication devices (such as a first network device, a terminal, a second network function, etc.), communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0070] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "information processing method" and "information processing apparatus" are interchangeable, as are "information processing system" and "communication system".

[0071] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0072] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be used interchangeably. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0073] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0074] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0075] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0077] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0078] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0079] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0080] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0081] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0082] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0083] 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”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0084] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0085] 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," and "bandwidth part (BWP)" can be used interchangeably.

[0086] 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", and "client" can be used interchangeably.

[0087] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0088] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0089] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0091] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0092] Figure 1 is a schematic diagram of an information processing system 100 according to an embodiment of the present disclosure. As shown in Figure 1, the information processing system 100 may include: a terminal 101 and a network device 102.

[0093] In some embodiments, network device 102 may include at least one of an access network device and a core network device.

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

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

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

[0097] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0098] In some embodiments, a core network device may be a network function, including a first network function, a second network function, a third network function, etc., or it may be multiple devices or a group of devices, each including all or part of the aforementioned first network function, second network function, and / or third network function. The first network function and / or the second network function may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and a 6G Core Network (6GCN).

[0099] In some embodiments, the name of the first network function is not limited, and it may be any network element, entity or function in the core network used for access management and / or mobility management.

[0100] In some embodiments, the first network function may be an Access and Mobility Management Function (AMF).

[0101] In some embodiments, the name of the second network function is not limited, and it may be any network element, entity, or function used for services such as communication proxy and / or data management.

[0102] In some embodiments, the second network function may be one of the following: a Service Communication Proxy (SCP), a Network Repository Function (NRF), or another network function (NF) in the core network other than SCP and NRF. For example, the other NF may be a new network function specifically used for user service management, or a Unified Data Management (UDM) or Unified Data Repository (UDR) that provides user data management.

[0103] In some embodiments, the second network function can be a third network function or a fourth network function; wherein the third network function can be an SCP; and the fourth network function can be an NRF, or another NF in the core network other than SCP and NRF. For example, the other NF can be a new network function specifically used for user service management, or a Unified Data Management (UDM) or Unified Data Repository (UDR) that provides user data management.

[0104] It is understood that the information processing system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0105] The following embodiments of this disclosure can be applied to the information processing system 100 shown in FIG1, or some of its components, but are not limited thereto. The components shown in FIG1 are illustrative. The information processing system may include all or some of the components in FIG1, or may include other components outside of FIG1. ​​The number and form of each component are arbitrary. The connection relationship between the components is illustrative. The components may not be connected to each other or may be connected in any way. The connection may be direct or indirect, wired or wireless.

[0106] The embodiments disclosed herein 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), 6th generation mobile communication system (6G), 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A combined with 5G, 5G combined with 5G, 5G combined with 6G, etc.) for application.

[0107] In some embodiments, an increasing number of application services that require data processing within the communication system are supported, such as on terminals, in the core network, and in some network functions of the access network, and support is not limited to supporting at least one of the following services:

[0108] Sensing services. Sensing is the use of radio frequency signals to acquire information about the characteristics of the environment and / or objects in the environment (e.g., shape, size, orientation, speed, position, distance, or relative motion between objects).

[0109] Integrated sensing and communication (ISAC) services. ISAC involves the simultaneous use of radio frequency signals for sensing and communication. This integration of sensing and communication can improve spectrum efficiency, reduce latency, and / or enhance the reliability of various applications. ISAC is particularly suitable for at least one of the following: mobile operators, UE vendors, automotive vendors, and users, as it can significantly enhance the overall user experience, improve network efficiency, and / or generate new business opportunities.

[0110] Artificial Intelligence (AI) / Machine Learning (ML) services. The convergence of communication networks and AI technologies is leveraging AI / ML to achieve intelligence in the core network and air interface through closed-loop processes such as data collection, ML model training, analysis and inference, and consumer data analysis.

[0111] Ranging / Sidelink Positioning service. Ranging refers to determining at least one of the following via the PC5 interface: the distance between two or more UEs, the orientation of one UE (i.e., the target UE) relative to another UE (i.e., the reference UE), and / or relative positioning. Sidelink positioning uses PC5 to locate the UE.

[0112] For example, the reference UE is a UE that determines a reference plane and reference orientation in ranging and / or lateral walkway-based positioning. The target UE is a UE whose distance, orientation, and / or position are measured compared to the reference plane, reference orientation, and / or position of the reference UE in ranging and / or lateral walkway-based positioning.

[0113] For example, ranging / sidewalking link positioning may include the following steps: measuring the absolute position between two UEs, or between one UE and multiple UEs, or between one or more positioned UEs; calculating the result (e.g., at the location server UE, or at the LMF, or at both); and making the ranging / sidewalking link positioning result available to the UE or the server (or a third-party application server).

[0114] Enhanced Location Service (eLCS) / Location Services. UE positioning can be supported by RAT-related positioning methods, which rely on, for example, RAT measurements obtained by the target UE and / or measurements of RAT signals transmitted by the target UE obtained by the access network. UE positioning can also be supported by RAT-independent positioning methods, which may rely on non-RAT measurements and / or other information obtained by the UE.

[0115] For example, the entire procedure of eLCS / location includes: measuring the absolute position between the UE and the base station; calculating the result (e.g., on the UE or in the LMF); and making it available to the UE or a third-party server (or a third-party application server).

[0116] In order to support applications that require data processing in communication systems, based on the development of terminals and their increasingly powerful capabilities, such as handheld computers, it is feasible to apply service-based architecture (SBA) on terminals to support applications that require data processing in communication systems.

[0117] Currently, it is not possible to achieve service management for services provided by the UE, and the UE's services cannot be discovered and / or consumed by network functions (NFs) within the core network (consumption can be replaced by invocation).

[0118] In some embodiments, the terminal can be a UE, and the UE can be a terminal.

[0119] Figure 2 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 2, the present disclosure relates to an information processing method used in an information processing system 100, the method comprising:

[0120] Step S2101: The terminal sends first information to the first network function.

[0121] In some embodiments, the first network function sends first information to the terminal.

[0122] Optionally, the first network function can be any network element, entity, or function used for access management and / or mobility management, etc. For example, the first network function is AMF.

[0123] In some embodiments, the first information is used to indicate that the terminal supports at least one service, or that the terminal does not support any service.

[0124] In some embodiments, the first information is used to indicate at least one of the following: whether the terminal supports the service capability, whether the terminal supports the provided service, or whether the terminal does not support the provided service. Whether the terminal supports the service capability includes: the terminal supports the service capability, or the terminal does not support the service capability.

[0125] Optionally, the service includes a first service or a second service, and the first information is used to indicate that the terminal supports at least one first service. Here, the first service is one or more services supported by the terminal. For example, the indication of whether the terminal supports a service is a bit, a field, or a domain in the first information, which can be used to indicate one first service supported by the terminal, or the bit, field, or domain can be used to indicate multiple first services supported by the terminal. For example, different bits, fields, or domains in the first information can each be used to indicate different first services not supported by the terminal. Here, the first information is used to indicate support for one or more first services, which can be used to register with a network function (e.g., a second network function) for managing services provided by the terminal, or the one or more first services can be used for updates within the network function (e.g., the second network function) for managing services provided by the terminal.

[0126] Optionally, the first information is used to indicate that the terminal does not support at least one first service. For example, different values ​​for the same field or the same domain of the terminal can indicate whether at least one first service is supported or not supported. For example, the terminal's first field has a first value, indicating support for the first first service; or, the terminal's first field has a second value, indicating that the first service is not supported. For example, the terminal's first field has a first value, indicating support for both the first and second first services; or, the terminal's first field has a second value, indicating that both the first and second first services are not supported; the first field can be any field or a predetermined field of the first information. Here, since the first information indicates that one or more first services are not supported, the registered first services provided by the terminal can be deleted or deregistered in the network function (e.g., the second network function) used to manage the services provided by the terminal.

[0127] Optionally, the first information is used to indicate that the terminal does not support the service. For example, the first information includes first indication information, which indicates that the terminal does not support the service. For example, any bit, field, or domain in the first information carries second indication information, which indicates that the service is not supported, and the second indication information can be a predetermined value. Here, if the first information indicates that a first service is not supported, then all services registered by the terminal can be deleted or deregistered in the network function (e.g., a second network function) used to manage the services provided by the terminal.

[0128] In some embodiments, the first information includes at least one of the following: a first identifier and third information.

[0129] Optionally, the first identifier is used to indicate the terminal. For example, the first identifier can be any identifier indicating the terminal, as long as it uniquely identifies the terminal. For instance, the first identifier can be any string or number, etc.

[0130] Optionally, the third information is used to indicate whether the terminal supports the first service or not. Here, the third information is used to indicate whether the terminal supports the first service or not; this third information is a capability indication information.

[0131] It is understood that the first information may include a first identifier and third information; wherein, the first identifier is used to indicate the terminal, and the third information is used to indicate whether a first service is supported or not supported; thus, the indication of the first information can indicate which terminal's capability for which service is supported or not supported, while the indication of the third information can indicate whether the capability for which service is supported or not supported. Therefore, if the first information includes the first identifier, it indicates which terminal's capability it is, and / or, if the first information includes the third information, it indicates what service's capability it is.

[0132] In some embodiments, the name of the first information is not limited, and it may be, for example, service indication information or terminal service capability information.

[0133] In some embodiments, the services described above, the first service, and the second service described below can all be: supporting at least one of the following for a single business: data detection, data collection, data processing, data distribution, data management, and business management; or supporting at least one of the following for multiple businesses: data detection, data collection, data processing, data distribution, data management, and business management.

[0134] Optionally, the service can be any service in the previous embodiments, or the service can be at least one of the following, including but not limited to: sensing service, positioning service, ranging / SL positioning service, AI service, ML service, AI / ML service, ISAC service, and environmental IoT service, etc.

[0135] In some embodiments, the names of the service, the first service, and the second service described below are not limited; for example, the service, the first service, and the second service can all be terminal services or UE services, etc.

[0136] In some embodiments, the terminal sends first information to the first network function via NAS messages.

[0137] Optionally, the NAS message can be a UL NAS message.

[0138] Optionally, the terminal sends a NAS message to the first network function, the NAS message including the first information.

[0139] Optionally, the first network function receives NAS messages sent by the terminal, the NAS messages including first information.

[0140] Step S2102: The first network function performs the first operation.

[0141] Optionally, the second network function can be one of the following: SCP, NRF, or other network functions in the core network besides SCP and NRF. For example, the other network function could be a new network function specifically for user service management, or a UDM or UDR that provides user data management.

[0142] Optionally, the first operation includes at least one of the following: determining a second network function, determining a third service, and determining second information.

[0143] In some embodiments, the first network function determines the second network function.

[0144] Optionally, the first network function makes management requests for services provided by the terminal. Here, management includes, but is not limited to, at least one of the following: registration, update, and revocation. Here, revocation may be replaced by deletion.

[0145] Optionally, the first network function determines the network function used to provide services for the management terminal as the second network function, for example, by determining the second network function based on configuration information or network discovery function. For example, the first network function may also determine a second identifier for the second network function; the second identifier is used to indicate the second network function.

[0146] In some embodiments, a first network function determines second information based on first information. Optionally, determining second information based on first information includes: determining a third service based on the first information; and determining the second information based on the third service.

[0147] In some embodiments, the first network function determines the third service based on the first information. Optionally, the first network function determines the third service based on the first information and local information. Local information may refer to information related to terminal support services and / or terminal registration and other related information.

[0148] Optionally, the third service is used to manage the services provided by the terminal (e.g., the first service, the second service, and / or other services).

[0149] Optionally, the third service is a service used to manage the services provided by the terminal (such as the first service).

[0150] Optionally, the third service is a service for managing terminal support (such as the first service and / or the second service, etc.).

[0151] Optionally, the third service is determined by the core network equipment. Here, the core network equipment can be any network function in the core network; for example, the network function includes, but is not limited to, the second network function.

[0152] Optionally, the third service may include at least one of the following: fourth information and a second identifier. For example, the third service includes fourth information. For example, the third service may not include fourth information. Here, the fourth information is used to indicate whether the terminal supports the second service or not.

[0153] Optionally, the third service may include at least one of the following: the first sub-service, the second sub-service, and the third sub-service.

[0154] For example, the first sub-service is used to request the first service supported by the registered terminal.

[0155] For example, the second sub-service is used to request an update to the first service supported by the terminal.

[0156] For example, the third sub-service is used to request the revocation or deletion of the first service or all services supported by the terminal.

[0157] For example, the first sub-service is used to request a second service supported by the registered terminal.

[0158] For example, the second sub-service is used to request an update to the second service supported by the terminal.

[0159] For example, the third sub-service is used to request the revocation or deletion of the first service or all services supported by the terminal.

[0160] In some embodiments, the first network function determines the second information based on a third service.

[0161] Optionally, the first network function uses the first identifier included in the first information as the first identifier of the second information; the first network function determines the second service supported by the terminal for management based on the first service provided in the first information.

[0162] Optionally, the second information is used to request services supported by the management terminal. Here, management includes, but is not limited to, at least one of the following: registration, update, revocation (or deletion or cancellation).

[0163] Optionally, the second information includes at least one of the following: a first identifier, a third service, and a fourth information.

[0164] For example, the fourth information may also include information related to at least one second service provided by the terminal, such as the status of each second service, access address information of the second service, conditions under which the second service is allowed to be accessed, and / or the version number of the second service.

[0165] For example, the second information may include a first identifier, a third service, and a fourth information.

[0166] For example, the second information may include a first identifier and a third service, and the third service may include fourth information.

[0167] For example, the third information is used to indicate whether the capability of supporting or not supporting the first service is supported; the fourth information is used to indicate whether the second service is supported or not supported; that is, the third information is an indication of the capability of supporting or not supporting a service, while the fourth information is an indication of supporting or supporting a specific service; and the first service supported or not supported in the third information and the second service supported or not supported in the fourth information may be the same or different.

[0168] Optionally, the second information is used to request at least one of the following: registering at least one second service supported by the terminal, updating at least one second service supported by the terminal, requesting the cancellation of the terminal registration for a second service, and requesting the cancellation of all services for the terminal registration.

[0169] Optionally, the second service may include a portion of the first service, or the first service may include a portion of the second service.

[0170] Optionally, the second service is the same as the first service.

[0171] Optionally, the service includes a first service or a second service, the first information being used to indicate that the terminal supports at least one first service, and the second information being used to request one of the following: registering at least one second service supported by the terminal, or updating at least one second service supported by the terminal.

[0172] Optionally, the first information is used to indicate that the terminal does not support at least one first service, and the second information is used to request the revocation of the terminal's registration for a second service.

[0173] Optionally, the first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

[0174] For example, when the first information is used to indicate the terminal's ability to support services A, B, and C, or to provide services A, B, and C, the second information can be used to request management (e.g., registration and update) of services A and B provided by the terminal; in this case, the first service includes a portion of the second service. Here, the second network function can compare the terminal's supported service capabilities indicated by the previously received first information with the determined currently supported service capabilities of the terminal, which may result in a difference between the first service and the second service.

[0175] For example, the first information is used to indicate when the terminal supports services A, B, and C or to provide services A, B, and C, and the second information can be used to request management (e.g., registration and update) services A, B, C, and D provided by the terminal; service D may be a previously registered service; in this case, the second service includes a portion of the first service.

[0176] For example, when the first information is used to indicate the terminal's ability to support service A or provide services for service A, the second information can be used to request management (e.g., registration and update) of services B, C, and D provided by the terminal to support the provision of services for service A; at this time, the second service is mapped according to the first service.

[0177] For example, when the first information is used to indicate that the terminal supports services A, B, and C, the second information can be used to request management (e.g., registration and update) services A, B, and C provided by the terminal; in this case, the second service is the same as the first service.

[0178] For example, the first information is used to indicate that the terminal does not support service A, and the second information can be used to request the cancellation or deletion of service A. Alternatively, the first information is used to indicate that the terminal does not support the service, and the second information can be used to request the cancellation or deletion of all services supported by the terminal.

[0179] Optionally, the terminal supports an indication of its ability to provide services (i.e., the services indicated in the first information) and there is a correspondence between the services that can be invoked. This correspondence may be one-to-one or not.

[0180] For example, there is a one-to-one correspondence; the first information indicates the capability to support certain services, and the services that can be provided must be registered. For instance, if the first information indicates support for the service-oriented processing capability of perception as a receiver, then it corresponds to supporting data distribution and data collection services for perception services; or, if the first information indicates support for the service-oriented processing capability of perception as a transmitter, then it corresponds to supporting data distribution and data collection services and data detection services for perception services.

[0181] An example is a one-to-one correspondence; for instance, if the first information indicates the capability of one or more services, then the second network function mapping requests the terminal to register and update a list of all services supported in the second information.

[0182] Optionally, the name of the second information is not limited, and it may be, for example, a service registration request or service registration request message or service update request or service management request message or service cancellation request or service cancellation request message or service management request or service management request message, etc.

[0183] Step S2103: The first network function sends the second information to the second network function.

[0184] In some embodiments, the second network function receives second information sent by the first network function.

[0185] In some embodiments, the second network function is a third network function, and the first network function sends second information to the third network function.

[0186] In some embodiments, the second network function is a third network function, and the third network function receives second information sent by the first network function.

[0187] In some embodiments, the second network function is a fourth network function, and the first network function sends the second information to the fourth network function through the third network function. Optionally, the first network function sends the second information to the third network function, and the third network function sends the second information to the fourth network function.

[0188] In some embodiments, the second network function is a fourth network function, which receives second information sent by the first network function through a third network function. Optionally, the fourth network function receives the second information sent by the third network function, wherein the second information is obtained by the third network function from the fourth network function.

[0189] Optionally, the second information sent by the first network function to the third network function is the same as the second information sent by the third network function to the fourth network function, or the second information sent by the first network function to the third network function differs from the second information sent by the third network function to the fourth network function in terms of content, parameter format, etc., as long as both satisfy the same requested purpose.

[0190] In some embodiments, the second network function is a fourth network function, and the first network function sends second information to the fourth network function.

[0191] In some embodiments, the second network function is a fourth network function, which receives second information sent by the first network function.

[0192] Step S2104, the services provided by the second network function management terminal.

[0193] In some embodiments, the second network function manages the services provided by the terminal based on the second information.

[0194] Optionally, the second network function manages the services provided by the terminal based on the third service, the first identifier, and the fourth information included in the second information.

[0195] Optionally, if the second network function determines that the third service of the second information is the first sub-service, it registers the service indicated by the fourth information provided by the terminal corresponding to the first identifier (such as the second service).

[0196] Optionally, if the second network function determines that the third service of the second information is the second sub-service, it updates the service indicated by the fourth information provided by the terminal corresponding to the first identifier (such as the second service).

[0197] Optionally, if the second network function determines that the third service of the second information is a third sub-service, it may revoke or delete the service (such as the second service) indicated by the fourth information provided by the terminal corresponding to the first identifier.

[0198] In some embodiments, the second network function determines first management information, wherein the first management information includes: a first identifier and a second service corresponding to the first identifier, the first identifier being used to indicate a terminal.

[0199] Optionally, the second network function determines the first management information, wherein the first management information includes: a first identifier and fourth information corresponding to the first identifier.

[0200] In some embodiments, the second network function adds the first identifier and the second service to the second management information.

[0201] Optionally, the second network function adds the first identifier and the fourth information to the second management information.

[0202] Optionally, a first management message can be specific to a terminal.

[0203] Optionally, the second network function may determine second management information, which is previously stored in the second network function. This second management information may be specific to one or more terminals.

[0204] For example, the second network function receives second information, which includes a third service and a first identifier. If the third service is used to request registration of service 1 for service 1 and service 2, the second network function can determine first management information, which may include: the first identifier, and service 1 for service 1 and service 2 corresponding to the first identifier.

[0205] For example, the second network function receives second information, which includes a third service and a first identifier. If the third service is used to request registration of service 1 for services 1 and 2, and the second network function stores service 2 for services 3 and 4 corresponding to the terminal with the first identifier, then the second network function can add service 1 for services 1 and 2 corresponding to the first identifier to the second management information. The second management information may include: the first identifier, and service 1 for services 1 and 2 and service 2 for services 3 and 4 corresponding to the first identifier.

[0206] Step S2105: The second network function sends a first response to the first network function.

[0207] In some embodiments, the first network function receives a first response sent by the second network function.

[0208] Optionally, the first response is determined based on the second information.

[0209] Optionally, the first response is used to indicate the execution result of the third service.

[0210] Optionally, the first response is used to indicate the execution result of the service provided by the request management terminal (such as the first service, the second service, or all services supported by the terminal).

[0211] For example, the first response indicates whether the service provided by the terminal was successfully registered or not. Here, the service can be a first service or a second service, etc.

[0212] For example, the first response indicates whether the service provided by the terminal was successfully updated or not. Here, the service can be a first service or a second service, etc.

[0213] For example, the first response indicates whether the service provided by the terminal was successfully revoked or not. Here, the service can be the first service or all services, etc.

[0214] For example, the first response includes third indication information, which indicates successful registration, update, or cancellation of the services provided by the terminal; or, the first response includes fourth indication information, which indicates unsuccessful registration, update, or cancellation of the services provided by the terminal.

[0215] Optionally, the name of the first response is not limited, and may be, for example, a service registration response, a service registration response message, a service update response, a service management response message, a service deregistration response, a service deregistration response message, a service management response, or a service management response message, etc.

[0216] In some alternative embodiments, the first network function sends fifth information to the terminal; wherein the fifth information is used to indicate the execution result of the third service and / or request the execution result of the service provided by the management terminal.

[0217] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0218] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0219] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0220] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0221] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0222] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2105. For example, step S2101 can be implemented as an independent embodiment; step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2104 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; a combination of steps S2101 and S2103 can be implemented as an independent embodiment; a combination of steps S2101, S2102, and S2103 can be implemented as an independent embodiment; a combination of steps S2103 and S2104 can be implemented as an independent embodiment; a combination of steps S2101, S2102, S2103, and S2104 can be implemented as an independent embodiment; a combination of steps S2101 to S2105 can be implemented as an independent embodiment.

[0223] In some embodiments, steps S2102 and S2105 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0224] In some embodiments, step S2105 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0225] In some embodiments, steps S2102, S2104 and S2105 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0226] In the embodiments disclosed herein, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished by their order.

[0227] Figure 3 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in Figure 3, this embodiment of the present disclosure relates to an information processing method for an information processing system 100, the method including one of the following steps:

[0228] In step S3101, the terminal sends first information to the first network function. Optionally, the first information indicates that the terminal supports at least one service, or that the terminal does not support any service.

[0229] The optional implementations of step S3101 can be found in the optional implementations of step S2101 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0230] In step S3102, the first network function sends second information to the second network function. Optionally, the second information is used to request services provided by the management terminal.

[0231] The optional implementation of step S3102 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0232] In some embodiments, the above methods may include the methods described in the above-described information processing system side, first device side and / or second device side embodiments, which will not be repeated here.

[0233] This disclosure relates to an information processing method that can provide UE-supported services to core network equipment for management by a service-based UE, so that the services provided by the UE can be discovered and / or consumed by network functions (NFs) within the core network. Here, consumption can be replaced by invocation.

[0234] This disclosure relates to a method for service management in a network based on services provided by a UE's capabilities. The method includes: the UE registering, updating, or deregistering its capabilities to support UE services in the AMF; and the AMF performing UE service registration, updating, or deregistration for the UE. Optionally, the UE service refers to a service provided or supported by the UE.

[0235] In some embodiments, the communication system may include core network equipment, access network equipment, and UE; for some SBA UEs, some functions of the mobile station (e.g., UE) are provided through services, such as the function of providing at least one or more (application) services: sensing services, positioning services, ranging / side-link positioning services, AI services, ML services, ISAC services, and environmental IoT services.

[0236] In some embodiments, at least one of the following services may be provided for one or more of the above-described (application) services: data detection, data collection, data processing, data distribution, data management, and business management.

[0237] In some embodiments, the UE can be a terminal, or the terminal can be a UE.

[0238] Example 1: UE service registration process.

[0239] In this embodiment, services provided by the UE are registered in the core network as UE capabilities, so that the AMF can perform UE service registration on behalf of the UE based on the UE capabilities, enabling the UE services to be discovered and / or consumed (e.g., invoked) by network functions in the core network. Optionally, the UE can reuse existing procedures to send UE capabilities to the network (e.g., core network equipment).

[0240] In some embodiments, as shown in FIG4A, the information processing method may include the following steps:

[0241] In step S4101, the UE sends a NAS message to the AMF, which includes the UE's capabilities for the services it supports.

[0242] Optionally, the UE may include at least one UE, such as UE1 or UE2; in Figure 4A, the UE may be UE1.

[0243] Optionally, the UE may send its UE capabilities for providing UE services to the network to the AMF in a NAS (e.g., UL NAS) message. For example, UE capabilities supporting UE services may include instructing the UE to support at least one of the following services for at least one of the following services: sensing services, positioning services, ranging / side-link positioning services, AI services, ML services, ISAC services, and environmental IoT services: service management, data detection, data processing, data collection, data distribution, and data management. The UL NAS message may be an existing UL NAS message, such as a registration request message during registration or a service request message during a service request process.

[0244] Optionally, the UE capabilities of the UE support services included in the NAS message or UL NAS message can be the first information in the previous embodiments.

[0245] In step S4102, the AMF processes the UE service registration request for the UE.

[0246] Optionally, the AMF, based on the UE capabilities provided to the network in the NAS (e.g., UL NAS) message received in step S4101, performs the processing of the UE service registration request message for the UE:

[0247] When constructing a request for UE service registration (a service call that can be implemented via HTTP), rules for UE service configuration files are set in the AMF and UE configuration files, or rules for UE service configuration files are received from the UE. The UE service configuration file may include the service name and / or service address information, status information, etc. for each service.

[0248] If the requested target NF is determined, the target NF can be an SCP or an NRF or any new NF used for UE service management;

[0249] If an SCP is involved, a request for UE service registration is sent to the SCP as in step S4103A below. If no SCP is involved (e.g., UE service management is provided directly by the NRF), a request for UE service registration is sent to the NRF as in step S4103B below. Alternatively, if UE service management is provided by a new NF, a request for UE service registration is sent to the new NF.

[0250] Optionally, the target NF can be the second network function in the previous embodiment; the request for UE service registration can be the second information in the previous embodiment.

[0251] In step S4103A, the AMF sends a request for UE service registration to the NRF via the SCP.

[0252] Optionally, if the AMF determines in step S4102 that an SCP is involved, it sends a request for UE service registration to the SCP. This request for UE service registration can reuse an extended NF management NF registration service (e.g., Nnrf_NFManagement_NFRegister service) to support services provided by UE service registration; the services requested for registration may include services provided by the UE corresponding to the terminal's identifier (UE ID). The services requested for registration may also be new services, such as services provided by the UE with the UE ID included in the management terminal service registration request (e.g., Nnrf_SvcManagement_UERegister Request). The user UE service registration request may include the UE file containing the UE ID and the services provided by the UE.

[0253] Optionally, the SCP will send the received request for UE service registration to the NRF or a new NF for UE service management.

[0254] In step S4104A, the NRF sends a response for UE service registration to the AMF via the SCP.

[0255] Optionally, the NRF or the new NF for UE service management stores a UE file containing UE services, indicating the relevant services available to the UE, and confirms acceptance of UE service registration with the AMF via SCP. For example, the NRF or the new NF for UE service management sends a response for UE service registration to the AMF via SCP, indicating acceptance of UE service registration.

[0256] Optionally, the response for UE service registration can be the first response in the previous embodiments.

[0257] In step S4103B, the AMF sends a request to the NRF for UE service registration.

[0258] Optionally, the AMF sends a request for UE service registration to the NRF or a new NF for UE service management. The request for UE service registration in step S4103B is similar to the request for UE service registration in step S4103A, except that step S4103B involves information for direct communication, while step S4103A involves information for indirect communication.

[0259] In step S4104B, the NRF sends a response to the AMF for UE service registration.

[0260] Optionally, the NRF or the new NF for UE service management stores a UE file containing UE services, indicating the relevant services available to the UE, and confirms acceptance of UE service registration with the AMF. For example, the NRF or the new NF for UE service management sends a response for UE service registration to the AMF, indicating acceptance of UE service registration.

[0261] Step S4105, AMF performs the processing of UE service registration response.

[0262] Optionally, the AMF performs processing of the UE service registration response; for example, the AMF records the UE service registration status based on the UE service registration response.

[0263] Example 2: UE service update process.

[0264] In this embodiment, the capability to support UE services is updated, and the UE services are updated in the network so that, for example, when some UE services on the UE are disabled or newly deployed, they can be discovered and / or consumed (e.g., invoked) by network functions in the core network.

[0265] In some embodiments, as shown in FIG4B, the information processing method may include the following steps:

[0266] In step S4201, the UE sends a NAS message to the AMF, which includes the UE's capabilities for the services it supports.

[0267] Optionally, the UE may include at least one UE, such as UE1 or UE2; in Figure 4B, the UE may be UE1.

[0268] Optionally, the UE may update its capabilities to support UE services provided to the network and send them to the AMF in a NAS (e.g., UL NAS) message. For example, the UE capabilities supporting UE services may include instructing the UE to support at least one of the following services for at least one of the following services: sensing services, positioning services, ranging / side-link positioning services, AI services, ML services, ISAC services, and environmental IoT services: service management, data detection, data processing, data collection, data distribution, and data management. The UL NAS message may be an existing UL NAS message, such as an update request message during an update process, or a service request message during a service request process.

[0269] Optionally, the UE capabilities of the UE support services included in the NAS message or UL NAS message can be the first information in the previous embodiments.

[0270] In step S4202, the AMF processes the UE service update request for the UE.

[0271] Optionally, the AMF, based on the UE capabilities provided to the network for updating UE services in the NAS (e.g., UL NAS) message received in step S4201, performs the processing of the UE service update request message for the UE:

[0272] If the UE service has been registered in the network, then construct a request for UE service update for the UE (a service call that can be implemented via HTTP); for example, configure rules for UE service profiles in the AMF and UE, or receive rules for UE service profiles from the UE. The UE service profile may include the service name and / or service address information, status information, etc. for each service.

[0273] If the requested target NF is determined, the target NF can be an SCP, an NRF, or any new NF used for UE service management. Information about the target NF (e.g., an NRF) (e.g., the second identifier in the previous embodiment) can be included in the response for UE service registration, and the target NF information can be used by the AMF to determine the target NF requested for the UE service update request.

[0274] If an SCP is involved, a request for UE service update is sent to the SCP as in step S4203A below. If no SCP is involved (e.g., UE service management is provided directly by the NRF), a request for UE service update is sent to the NRF as in step S4203B below. Alternatively, if UE service management is provided by a new NF, a request for UE service update is sent to the new NF.

[0275] Optionally, the target NF can be the second network function in the previous embodiment; the request for UE service update can be the second information in the previous embodiment.

[0276] In step S4203A, the AMF sends a request for UE service update to the NRF via the SCP.

[0277] Optionally, if the AMF determines in step S4202 that an SCP is involved, it sends an HTTT request for UE service update to the SCP. This UE service update request can reuse an extended NF management NF update service (e.g., Nnrf_NFManagement_NFUpdate service) to support services provided by the UE service update; the service requested for update may include services provided by the UE corresponding to the terminal's identifier (UE ID). The service requested for update may also be a new service, such as a UE-provided service with the UE ID included in a management terminal service update request (e.g., Nnrf_SvcManagement_UEUpdate Request). A user UE service update request may include the UE file containing the UE ID and the services provided by the UE.

[0278] Optionally, the SCP will send the received request for UE service update to the NRF or a new NF for UE service management.

[0279] In step S4204A, the NRF sends a response for UE service update to the AMF via SCP.

[0280] Optionally, the NRF or the new NF for UE service management stores a UE update file containing UE services, indicating the relevant services available to the UE, and confirms acceptance of the UE service update to the AMF via SCP. For example, the NRF or the new NF for UE service management sends a response for the UE service update to the AMF via SCP, indicating acceptance of the UE service update.

[0281] Optionally, the response for UE service update can be the first response in the previous embodiments.

[0282] In step S4203B, the AMF sends a request to the NRF for UE service updates.

[0283] Optionally, the AMF sends a request for UE service update to the NRF or a new NF for UE service management. The request for UE service update in step S4203B is similar to the request for UE service update in step S4203A, except that step S4203B involves information for direct communication, while step S4203A involves information for indirect communication.

[0284] In step S4204B, the NRF sends a response to the AMF for UE service update.

[0285] Optionally, the NRF or the new NF for UE service management stores a UE update file containing information about the UE services available to the UE and confirms acceptance of the UE service update to the AMF. For example, the NRF or the new NF for UE service management sends a response to the AMF for the UE service update, indicating acceptance of the UE service update.

[0286] Step S4205: AMF performs UE service update response processing.

[0287] Optionally, the AMF performs processing of the UE service update response; for example, the AMF records the UE service update status based on the UE service update response.

[0288] Example 3: UE service deregistration process.

[0289] In this embodiment, the UE capability supporting the UE service is at least partially disabled, or the UE needs to deregister from the network so that the UE service is deregistered and cannot be discovered and / or consumed (e.g., invoked) by network functions in the core network.

[0290] In some embodiments, as shown in FIG4C, the information processing method may include the following steps:

[0291] Step S4301: Trigger UE service deregistration.

[0292] Optionally, the UE may include at least one UE, such as UE1 or UE2; in Figure 4C, the UE may be UE1.

[0293] Optionally, the UE may disable or partially disable UE capabilities that support UE services provided to the network. For example, all UE capabilities supporting UE services may be disabled, or the UE may be requested to deregister or cancel registration (i.e., deregister) due to a power outage. For instance, the UE may include information about the disabled UE capabilities supporting UE services provided to the network in a NAS (e.g., UL NAS) message sent to the AMF. The UL NAS message can be an existing UL NAS message, such as a deregister request message during the deregistration process, or a service request message during the service request process.

[0294] Optionally, the information in the NAS message or UL NAS message that the UE capability of the UE support service is disabled can be the first information in the previous embodiments.

[0295] In step S4302, the AMF processes the UE service deregistration request for the UE.

[0296] Optionally, the AMF processes a UE service deregistration request message for the UE based on the UE capabilities that are disabled in the NAS (e.g., UL NAS) message received in step S4301, which support UE services provided to the network.

[0297] If the UE service has already been registered in the network, then construct a request for UE service updates (a service that can be implemented via HTTP) for the UE.

[0298] If the requested target NF is determined, the target NF can be an SCP, an NRF, or any new NF used for UE service management. Information about the target NF (e.g., an NRF) (e.g., the second identifier in the previous embodiment) is recorded from a previous UE service registration or UE service update process, and it can be used by the AMF to determine the target NF requested for the UE service deregistration request.

[0299] If an SCP is involved, a request for UE service deregistration is sent to the SCP as in step S4303A below. If no SCP is involved (e.g., UE service management is provided directly by the NRF), a request for UE service deregistration is sent to the NRF as in step S4303B below. Alternatively, if UE service management is provided by a new NF, a request for UE service deregistration is sent to the new NF.

[0300] Optionally, the target NF can be the second network function in the previous embodiment; the request for UE service registration can be the second information in the previous embodiment.

[0301] In step S4303A, the AMF sends a request for UE service deregistration to the NRF via the SCP.

[0302] Optionally, if the AMF determines in step S4302 that an SCP is involved, it sends an HTTT request for UE service deregistration to the SCP. This UE service deregistration request can reuse an extended NF management NF deregistration service (e.g., Nnrf_NFManagement_NFUpdate service) to support services provided for UE service deregistration; the services requested for deregistration may include services provided by the UE corresponding to the terminal's identifier (UE ID). The services requested for deregistration may also be new services, such as services provided by the UE with the UE ID included in the management terminal service deregistration request (e.g., Nnrf_SvcManagement_UEUpdate Request); the user UE service deregistration request may include the UE file for the UE ID and the services provided by the UE. Revoking one or more services supported by the terminal requires including a list of revoked services. Revoking all services supported by the terminal may not include the list of revoked services; the revocation can be indicated by a service revocation operation or specific instructions to revoke all services supported by the specified terminal.

[0303] Optionally, the SCP will send the received request for UE service deregistration to the NRF or a new NF for UE service management.

[0304] Optionally, the request for UE service deregistration may be the second information in the previous embodiments.

[0305] In step S4304A, the NRF sends a response for UE service deregistration to the AMF via the SCP.

[0306] Optionally, the NRF or the new NF for UE service management stores a UE file containing UE services, indicating that the relevant services for the UE are unavailable, and confirms acceptance of UE service deregistration to the AMF via SCP. For example, the NRF or the new NF for UE service management sends a response for UE service deregistration to the AMF via SCP, indicating acceptance of UE service deregistration.

[0307] Optionally, the response for UE service deregistration can be the first response in the previous embodiments.

[0308] In step S4303B, the AMF sends a request to the NRF for UE service deregistration.

[0309] Optionally, the AMF sends a request for UE service deregistration to the NRF or a new NF for UE service management. The request for UE service deregistration in step S4303B is similar to the request for UE service deregistration in step S4303A, the difference being that step S4303B involves information for direct communication, while step S4303A involves information for indirect communication.

[0310] In step S4304B, the NRF sends a response to the AMF for UE service deregistration.

[0311] Optionally, the NRF or the new NF for UE service management stores a UE file containing UE services, indicating that the relevant services for the UE are unavailable, and confirms acceptance of UE service deregistration to the AMF. For example, the NRF or the new NF for UE service management sends a response for UE service deregistration to the AMF, indicating acceptance of UE service deregistration.

[0312] Step S4305, AMF performs the processing of the UE service deregistration response.

[0313] Optionally, the AMF processes the UE service deregistration response; for example, the AMF records the UE service registration status based on the UE service deregistration response.

[0314] In a Service-Based Architecture (SBA), interaction between network functions can be achieved by invoking services, rather than sending request and response messages. In non-SBA architectures, this is achieved by sending corresponding messages. For example, in SBA, sending a request to a specified interface corresponds to invoking the service provided by the corresponding network function, and the corresponding response corresponds to the output of that service. Of course, for other requests, it is also possible to invoke the corresponding service implementation, and the response to that request corresponds to the output of that service; there are no specific limitations on the requests and / or responses.

[0315] In some embodiments, if the access network device (e.g., (R)AN mentioned above) supports the Service-Based Interface (SBI) interface with the AMF, the above scheme can also be applied. Similarly, sending a request is achieved by calling the corresponding service, and the corresponding response is the result of the service call.

[0316] In the above embodiments, considering the emergence of more and more application services and the development of mobile terminals, a service-based UE architecture is developed. Services provided by service-based UEs are managed in the network so that UE services can be discovered and / or consumed (e.g., invoked) by network functions in the core network. It can also provide lower complexity and better scalability to support new application services that require data processing within the telecommunications system.

[0317] In this embodiment of the disclosure, some or all of the steps and their optional implementations can be arbitrarily combined with some or all of the steps in other embodiments, or arbitrarily combined with the optional implementations in other embodiments.

[0318] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0319] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an Application-Specific Integrated Circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0320] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 configuring the hardware circuit 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 hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0321] Figure 5A is a schematic diagram of the structure of the first network function 5100 provided in an embodiment of this disclosure. As shown in Figure 5A, the first network function 5100 includes a first transceiver module 5101. In some embodiments, the first transceiver module 5101 is used to receive first information and / or send second information. Optionally, the first transceiver module 5101 is used to perform at least one of the sending and / or receiving steps (e.g., steps S2101, S2103, S2105, and / or S2106, etc., but not limited thereto) performed by the first network function 5100 in any of the above methods, which will not be described in detail here. In some embodiments, the first network function 5100 may include a first processing module.

[0322] Figure 5B is a schematic diagram of the structure of a terminal 5200 provided in an embodiment of this disclosure. As shown in Figure 5B, the terminal 5200 includes a second transceiver module 5201. In some embodiments, the second transceiver module 5201 is used to send first information. Optionally, the second transceiver module 5201 is used to perform at least one of the sending and / or receiving steps (e.g., steps S2101 and / or S2102, but not limited thereto) performed by the terminal 5200 in any of the above methods, which will not be described in detail here. In some embodiments, the terminal 5200 may include a second processing module.

[0323] Figure 5C is a schematic diagram of the structure of the second network function 5300 provided in an embodiment of this disclosure. As shown in Figure 5C, the second network function 5300 includes a third transceiver module 5301. In some embodiments, the third transceiver module 5301 is used to obtain the address information of the server. Optionally, the third transceiver module 5301 is used to perform at least one of the sending and / or receiving steps (e.g., steps S2103 and / or S2105, but not limited thereto) performed by the second network function 5300 in any of the above methods, which will not be described in detail here. In some embodiments, the second network function 5300 may include a third processing module.

[0324] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver. For example, the first transceiver module described above includes a first transmitting module and / or a first receiving module. For example, the second transceiver module described above includes a second transmitting module and / or a second receiving module.

[0325] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0326] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal, a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0327] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0328] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101 and / or steps S2102 and / or steps S2103 and / or steps S2104, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2105 and / or steps S2106, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0329] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

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

[0331] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0332] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0333] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0334] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101 and / or S2102 and / or S2103 and / or S2104, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2105 and / or S2106, but not limited thereto).

[0335] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0336] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0337] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0338] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. An information processing method characterized by comprising: Performed by the first network function, including: The receiving terminal sends first information, wherein the first information is used to indicate that: the terminal supports at least one service, or the terminal does not support any service; Send a second message to a second network function, wherein the second message is used to request the management of services supported by the terminal.

2. The method according to claim 1, characterized in that, The service includes a first service or a second service, the first information being used to indicate that the terminal supports at least one of the first services, and the second information being used to request one of the following: registering at least one of the second services supported by the terminal, or updating at least one of the second services supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes a portion of the second service; or, The first information is used to indicate that the terminal does not support at least one of the first services, and the second information is used to request the revocation of the second service registered by the terminal; or, The first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

3. The method according to claim 1 or 2, characterized in that, The at least one service includes at least one of the following: Supports data detection for at least one business function; Supports data processing for at least one business function; Supports data collection for at least one business function; Supports data distribution for at least one business function; Supports data management for at least one business function; Supports business management for at least one business function.

4. The method according to any one of claims 1 to 3, characterized in that, The first information includes: a first identifier, wherein the first identifier is used to indicate the terminal; And / or, The second information includes at least one of the following: The first identifier; The third service is used to manage the services supported by the terminal.

5. The method according to claim 4, characterized in that, The first information includes: third information, which is used to indicate whether the terminal supports the first service or whether the terminal does not support the first service; and / or, the second information includes: fourth information, which is used to indicate whether the terminal supports the second service or whether the terminal does not support the second service; or, The third service includes the fourth information.

6. The method of claim 4, wherein, The third service includes at least one of the following: The first sub-service is used to request registration of a first service supported by the terminal; The second sub-service is used to request an update to the first service supported by the terminal. The third sub-service is used to request the cancellation of the first service or all services supported by the terminal.

7. The method according to any one of claims 1 to 6, characterized in that, Before sending the second information to the second network function, at least one of the following is also included: Determine the second network function; Based on the first information, a third service is determined; Based on the third service, the second information is determined.

8. The method according to any one of claims 1 to 7, characterized in that, Sending the second information to the second network function includes at least one of the following: The second network function is the third network function, and the second information is sent to the third network function; The second network function is the fourth network function, which sends the second information to the fourth network function through the third network function; The second network function is the fourth network function, which sends the second information to the fourth network function.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive a first response sent by the second network function, wherein the first response is used to indicate the execution result of managing the first service.

10. The method according to any one of claims 1 to 9, characterized in that, The first network function is: access and mobility management functions; and / or, The second network function is: a service communication proxy, a network storage function, or other network functions in the core network besides the service communication proxy and network storage functions; and / or, The third network function is: to serve as a communication proxy; and / or, The fourth network function is: network storage function, or other network functions in the core network other than service communication proxy and network storage function.

11. An information processing method characterized by comprising: Executed by the terminal, including: Send first information to a first network function, wherein the first information is used to indicate: at least one service supported by the terminal, or the terminal does not support a service; Wherein, the first information is used by the first network function to send the second information to the second network function, and the second information is used to request the management of the services supported by the terminal.

12. The method according to claim 11, characterized in that, The service includes a first service or a second service, the first information being used to indicate that the terminal supports at least one of the first services, and the second information being used to request one of the following: registering at least one of the second services supported by the terminal, or updating at least one of the second services supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes at least a portion of the second service; or, The first information is used to indicate that the terminal does not support at least one of the first services, and the second information is used to request the revocation of the second service registered by the terminal; or, The first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

13. The method according to claim 11 or 12, characterized in that, The at least one service includes at least one of the following: Supports data detection for at least one business function; Supports data processing for at least one business function; Supports data collection for at least one business function; Supports data distribution for at least one business function; Supports data management for at least one business function; Supports business management for at least one business function.

14. An information processing method characterized by comprising: Performed by the second network function, including: Receive second information sent by the first network function, wherein the second information is used to request services supported by the management terminal; The second information is sent by the first network function based on the first information, which indicates that the terminal supports at least one service, or that the terminal does not support any service.

15. The method according to claim 14, characterized in that, The service includes a first service or a second service, the first information being used to indicate that the terminal supports at least one of the first services, and the second information being used to request one of the following: registering at least one of the second services supported by the terminal, or updating at least one of the second services supported by the terminal; wherein, the second service includes a portion of the first service, or, the first service includes at least a portion of the second service; or, The first information is used to indicate that the terminal does not support at least one of the first services, and the second information is used to request the revocation of the second service registered by the terminal; or, The first information is used to indicate that the terminal does not support the service, and the second information is used to request the revocation of all services registered by the terminal.

16. The method according to claim 14 or 15, characterized in that The at least one service includes at least one of the following: Supports data detection for at least one business function; Supports data processing for at least one business function; Supports data collection for at least one business function; Supports data distribution for at least one business function; Supports data management for at least one business function; Supports business management for at least one business function.

17. The method according to any one of claims 14 to 16, characterized in that, The first information includes: a first identifier, wherein the first identifier is used to indicate the terminal; And / or, The second information includes at least one of the following: The first identifier; The third service is used to manage the services supported by the terminal.

18. The method according to claim 17, characterized in that, The first information includes: third information, which is used to indicate whether the terminal supports the first service or whether the terminal does not support the first service; and / or, the second information includes: fourth information, which is used to indicate whether the terminal supports the second service or whether the terminal does not support the second service; or, The third service includes the fourth information.

19. The method of claim 17, wherein, The third service includes at least one of the following: The first sub-service is used to request registration of a first service supported by the terminal; The second sub-service is used to request an update to the first service supported by the terminal. The third sub-service is used to request the cancellation of the first service or all services supported by the terminal.

20. The method according to any one of claims 14 to 19, characterized in that, The method includes: First management information is determined, wherein the first management information includes: a first identifier and a second service corresponding to the first identifier, wherein the first identifier is used to indicate the terminal; Add the first identifier and the second service to the second management information.

21. The method according to any one of claims 14 to 20, characterized in that, The method further includes: Send a first response to the first network function, wherein the first response is used to indicate the execution result of managing the first service and / or the second service.

22. An information processing method characterized by comprising: The method includes: The terminal sends first information to a first network function, wherein the first information is used to indicate that: the terminal supports at least one service, or the terminal does not support a service; The first network function sends second information to the second network function, wherein the second information is used to request the management of services supported by the terminal.

23. A communications device, characterized by The communication device is used to perform the information processing method according to any one of claims 1 to 10, or claims 11 to 13, or claims 14 to 21, or claim 22.

24. A communication system, characterized by include: A first network function, a terminal, and a second network function; wherein the first network function is configured to implement the information processing method according to any one of claims 1 to 10, the terminal is configured to implement the information processing method according to any one of claims 11 to 13, and the second network device is configured to implement the information processing method according to any one of claims 14 to 21.

25. A storage medium, the storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the information processing method as described in any one of claims 1 to 10, or claims 11 to 13, or claims 14 to 21, or claim 22.

26. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the information processing method according to any one of claims 1 to 10, or claims 11 to 13, or claims 14 to 21, or claim 22.

Images