Communication method, network element, terminal, communication system, and storage medium

Abstract

A communication method, a network element, a terminal, a communication system, and a storage medium. The method executed by a unified data management network element (UDM) comprises: receiving a first request sent by an access and mobility management function network element (AMF), wherein the first request is sent by the AMF after receiving a second request sent by a terminal, and the first request comprises first user information of the terminal; and managing the first user information. In this way, the performance of the communication system can be enhanced by managing the first user information of the terminal by means of the UDM.

Description

Communication method, network element, terminal, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method, a network element, a terminal, a communication system, and a storage medium. Background Art

[0002] By enhancing 5G (5th Generation Mobile Communication Technology) systems to allow the creation and use of user-specific identities, operators will be able to provide an enhanced user experience, optimized performance, and provide services to devices and users that are not part of the operator's 3GPP (3rd Generation Partnership Project) network.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication method, a network element, a terminal, a communication system, and a storage medium.

[0005] According to the first aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a unified data management network element UDM, and the method includes: receiving a first request sent by an access and mobility management function network element AMF, the first request being sent by the AMF after receiving a second request sent by a terminal, and the first request including first user information of the terminal; and managing the first user information.

[0006] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by an AMF. The method includes: receiving a second request sent by a terminal, where the second request includes first user information of the terminal; sending a first request to a UDM, where the first request includes the first user information, and the first request is used to request the UDM to manage the first user information.

[0007] According to a third aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a terminal. The method includes: sending a second request to the AMF, the second request including first user information of the terminal, the first user information being used for the AMF to send a first request including the first user information to the UDM, and the first request being used by the AMF to request the UDM to manage the first user information.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a first network element is proposed, including: a transceiver module for receiving a first request sent by an access and mobility management function network element AMF, wherein the first request is sent by the AMF after receiving a second request sent by a terminal, and the first request includes first user information of the terminal; and a processing module for managing the first user information.

[0009] According to the fifth aspect of an embodiment of the present disclosure, a second network element is proposed, including: a transceiver module, used to receive a second request sent by a terminal, the second request including first user information of the terminal; and send a first request to a UDM, the first request including the first user information, and the first request being used to request the UDM to manage the first user information.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, including: a transceiver module for sending a second request to an AMF, the second request including first user information of the terminal, the first user information being used for the AMF to send a first request including the first user information to the UDM, and the first request being used by the AMF to request the UDM to manage the first user information.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a first network element is proposed, comprising: one or more processors; a memory coupled to the processor, wherein the memory stores executable instructions, and when the executable instructions are executed by the processor, the first network element executes the communication method described in the first aspect.

[0012] According to the eighth aspect of an embodiment of the present disclosure, a second network element is proposed, comprising: one or more processors; a memory coupled to the processor, wherein executable instructions are stored on the memory, and when the executable instructions are executed by the processor, the second network element executes the communication method described in the second aspect.

[0013] According to the ninth aspect of the embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; a memory coupled to the processor, wherein the memory stores executable instructions, and when the executable instructions are executed by the processor, the terminal executes the communication method described in the third aspect.

[0014] According to the tenth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first network element, a second network element, and a terminal, wherein the first network element is configured to implement the communication method described in the first aspect, the second network element is configured to implement the communication method described in the second aspect, and the terminal is configured to implement the communication method described in the third aspect.

[0015] According to an eleventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method described in the first aspect, the second aspect or the third aspect.

[0016] By adopting the technical solution of the present disclosure, the communication system can be enhanced by managing the first user information of the terminal through the UDM. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0018] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0019] FIG2 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0020] FIG3A is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0021] FIG3B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0022] FIG3C is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0023] FIG3D is a flow chart of a communication method according to an embodiment of the present disclosure.

[0024] FIG4A is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0025] FIG4B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0026] FIG5A is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0027] FIG5B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0028] FIG6A is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0029] FIG6B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0030] FIG7A is an interactive diagram illustrating a communication method according to an embodiment of the present disclosure.

[0031] FIG7B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0032] FIG7C is an interactive diagram illustrating a communication method according to an embodiment of the present disclosure.

[0033] FIG8A is a schematic structural diagram of a first network element proposed according to an embodiment of the present disclosure.

[0034] FIG8B is a schematic structural diagram of a second network element proposed according to an embodiment of the present disclosure.

[0035] FIG8C is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0036] FIG9A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

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

[0038] The embodiments of the present disclosure provide a communication method, a network element, a terminal, a communication system, and a storage medium.

[0039] In the first aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a unified data management network element UDM, and the method includes: receiving a first request sent by an access and mobility management function network element AMF, the first request being sent by the AMF after receiving a second request sent by a terminal, and the first request including first user information of the terminal; and managing the first user information.

[0040] In the above embodiments, managing the first user information of the terminal through UDM in the 5G system can enhance the 5G system, thereby providing users with an enhanced user experience and optimized performance.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the first user information includes at least one of the following:

[0042] User identifier;

[0043] a device identifier of the terminal;

[0044] Specific Quality of Service (QoS) settings;

[0045] Security credentials.

[0046] In the above embodiment, it is specified that at least one of a terminal user identifier, a terminal device identifier, a terminal specific QoS setting, and a security credential can be configured as the content of the first user information. Specifically, when managing the terminal specific QoS setting, differentiated services can be provided to users based on the user specific QoS setting when providing communication services in the 3GPP system.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the second request is any one of the following:

[0048] Registration request;

[0049] Service Request.

[0050] In the above embodiment, it is specified that the UDM can be requested to manage the first user information during the registration process or the service request process.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the managing the first user information includes: storing the first user information.

[0052] In the above embodiment, the UDM may manage the first user information of the terminal by storing the first user information so as to facilitate the use of the first user information in the 5G system, thereby providing the user with an enhanced user experience and optimized performance.

[0053] In combination with some embodiments of the first aspect, in some embodiments, storing the first user information includes: creating second user information of a predefined user data structure in the UDM according to the first user information.

[0054] In the above embodiment, when the UDM stores the first user information, if the data structure of the first user information does not meet the network requirements, then the second user information with a predefined user data structure can be created in the UDM based on the first user information, thereby standardizing the data storage method and facilitating network use.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the managing the first user information includes: associating the first user information with the subscription data of the terminal.

[0056] In the above embodiment, the UDM may manage the first user information of the terminal by associating or binding the first user information with the subscription data of the terminal, thereby facilitating the network to use the first user information and improving network performance.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the managing the first user information includes: allocating a first ID to a user corresponding to the first user information.

[0058] In the above embodiment, the UDM may manage the first user information of the terminal by additionally allocating a first ID to the user corresponding to the first user information, so as to facilitate unified management of users by the network.

[0059] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending a first response message to the AMF, where the first response message includes the first ID.

[0060] In the above embodiment, when the UDM successfully manages the first user information, it can respond to the successful management of the first request by sending a first response message including the first ID to the AMF.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the second user information includes at least one of the following:

[0062] User identifier;

[0063] a device identifier of the terminal;

[0064] Specific Quality of Service (QoS) settings;

[0065] security credentials;

[0066] First ID.

[0067] In the above embodiment, the content of the second user information stored according to the first user information is standardized.

[0068] In combination with some embodiments of the first aspect, in some embodiments, the management of the first user information includes: determining that the first user information also includes a first ID, and updating or deleting the second user information of the predefined user data structure corresponding to the first ID stored in the UDM based on the first user information.

[0069] In the above embodiment, the UDM manages the first user information of the terminal by updating or deleting the second user information of the predefined user data structure corresponding to the first ID in the first user information stored in the UDM.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending a third request to the structured data storage network element UDR, where the third request is used by the UDM to request the UDR to store the second user information.

[0071] In the above embodiment, in order to reduce the storage pressure of the UDM, the second user information created based on the first user information can be stored in the UDR. Alternatively, the second user information can be further backed up in the UDR while the UDM stores the second user information.

[0072] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending a fourth request to the UDR, where the fourth request is used by the UDM to request the UDR to update or delete the stored second user information.

[0073] In the above embodiment, if the second user information created based on the first user information is stored or backed up in the UDR, then in the subsequent process, the second user information stored or backed up by the UDR can be updated or deleted, making the management of the second user information more flexible, secure and accurate.

[0074] In the second aspect, an embodiment of the present disclosure proposes a communication method, which is executed by AMF, and the method includes: receiving a second request sent by a terminal, the second request including first user information of the terminal; sending a first request to a UDM, the first request including the first user information, and the first request is used to request the UDM to manage the first user information.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the first user information includes at least one of the following:

[0076] User identifier;

[0077] a device identifier of the terminal;

[0078] Specific Quality of Service (QoS) settings;

[0079] Security credentials.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the second request is any one of the following:

[0081] Registration request;

[0082] Service Request.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a first response message sent by the UDM, the first response message including a first ID, the first ID being the ID assigned by the UDM to the user corresponding to the first user information; and sending a second response message to the terminal, the second response message including the first ID.

[0084] In a third aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a terminal, and the method includes: sending a second request to the AMF, the second request including the first user information of the terminal, and the first user information is used for the AMF to send a first request including the first user information to the UDM, and the first request is used by the AMF to request the UDM to manage the first user information.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the first user information includes at least one of the following:

[0086] User identifier;

[0087] a device identifier of the terminal;

[0088] Specific Quality of Service (QoS) settings;

[0089] Security credentials.

[0090] In conjunction with some embodiments of the third aspect, in some embodiments, the second request is any one of the following:

[0091] Registration request;

[0092] Service Request.

[0093] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: receiving a second response message sent by the AMF, the second response message including a first ID, the first ID being an ID assigned by the UDM to the user corresponding to the first user information; updating the local first user information according to the first ID.

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

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

[0096] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute the optional implementation method of the third aspect.

[0097] In a seventh aspect, an embodiment of the present disclosure proposes a first network element, comprising: one or more processors; wherein the above-mentioned first network element is used to execute an optional implementation method of the first aspect.

[0098] In an eighth aspect, an embodiment of the present disclosure proposes a second network element, comprising: one or more processors; wherein the above-mentioned second network element is used to execute an optional implementation method of the second aspect.

[0099] In a ninth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the optional implementation method of the third aspect.

[0100] In the tenth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first network element, a second network element, and a terminal, wherein the first network element is configured to execute the method described in the optional implementation manner of the first aspect, the second network element is configured to execute the method described in the optional implementation manner of the second aspect, and the terminal is configured to execute the method described in the optional implementation manner of the third aspect.

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

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

[0103] In a thirteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the second aspect, and the optional implementation of the third aspect.

[0104] In a fourteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

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

[0106] The present disclosure provides a communication method, network element, terminal, communication system, and storage medium. In some embodiments, the terms "communication method," "information processing method," and "method for creating user information in a network" are interchangeable, and the terms "communication system," "information processing system," and "system for creating user information in a network" are interchangeable.

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

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

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

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

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

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

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

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

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

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

[0117] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

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

[0119] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

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

[0121] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0122] 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", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

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

[0124] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

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

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

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

[0128] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0129] Although operations are described in a particular order in the accompanying drawings in the disclosed embodiments, this should not be construed as requiring that the operations be performed in the particular order shown or in a serial order, or that all of the operations shown be performed to obtain the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, sending multiple messages via the same message may also be advantageous.

[0130] Figure 1 is a schematic diagram illustrating the architecture of a communication system 100 according to an embodiment of the present disclosure. As shown in Figure 1 , communication system 100 includes a terminal 101, an access network device 102, and a core network device 103. Core network device 103 includes a first network element 1031, a second network element 1032, and a third network element 1033.

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

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

[0133] Optionally, the base station is, for example, a macro base station, a micro base station (also known as a small station), a relay station, an access point, a 5G base station or a future base station, a satellite, a transmission point (Transmitting and Receiving Point, TRP), a transmission point (Transmitting Point, TP), a mobile switching center, or other devices that perform base station functions in a communication system, etc., which are not specifically limited in the embodiments of the present disclosure. For the convenience of description, in all embodiments of the present disclosure, devices that provide wireless communication functions for terminal devices are collectively referred to as network devices or base stations.

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

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

[0136] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, a third network element 1033, etc., or may be a plurality of devices or a device group including all or part of the first network element 1031, the second network element 1032, the third network element 1033, etc. The network element 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), and a next generation core (NGC).

[0137] In some embodiments, the first network element 1031 is, for example, a UDM (Unified Data Management).

[0138] In some implementations, the unified data management network element is used to store user subscription data, authentication, etc. The name is not limited thereto.

[0139] In some embodiments, the second network element 1032 is, for example, an AMF (Access and Mobility Management Function).

[0140] In some implementations, the access and mobility management function network element is used for access and mobility management of terminals in a mobile network.

[0141] In some embodiments, the third network element 1033 is, for example, a Unified Data Repository (UDR).

[0142] In some implementations, the structured data storage network element is used to store structured data, such as user subscription data and policy data managed by the UDM, etc. The name is not limited thereto, and it may be, for example, a user data register network element or a unified data warehouse function network element.

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

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

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

[0146] In some embodiments, by enhancing the 5G system to allow the creation and use of user-specific identities, operators will be able to provide an enhanced user experience, optimized performance, and provide services to devices and users that are not part of the operator's 3GPP network. For example, network settings can be adjusted and services can be provided to users based on their needs, which is different from the subscription identifier used by the user to establish a connection.

[0147] In some embodiments, in the context of this work, the user that needs to be identified can be an individual user using a UE with a specific subscription, an application running on or connected through a UE, or a device behind a gateway UE (such as PEGC) (such as PINE).

[0148] In some embodiments, Task 1.x focuses on supporting use cases where a person's user identifier is associated with traffic flowing into / out of a UE:

[0149] In some embodiments, WT #1.1: Define the architectural assumptions required to support identifying user identifiers associated with UE traffic.

[0150] NOTE A: In some embodiments, when a user identifier applies to a real person, only one user identifier is associated with a UE at a given time, and that user identifier is assumed to be associated with all services accessed by the UE during the period the user identifier and the UE are associated.

[0151] In some embodiments, WT#1.2: What information is stored as part of the user profile (e.g., user identifier, related security credentials, related devices, user-specific QoS settings), including how to obtain, store, and update the user profile in the 5GC.

[0152] In some embodiments, WT #1.3: Whether and how a user identifier is linked and unlinked (ie, associated) with a 3GPP subscription in an operator-controlled manner.

[0153] In some embodiments, WT#1.4: Whether and how the 3GPP system considers user-specific QoS settings when providing communication services to provide differentiated services.

[0154] In some embodiments, since user information (such as user identifier, device, user-specific QoS, etc.) is not stored / managed / used in the 5G system, there is no solution for how the 5G CN uses user information. In view of this, the embodiments of the present disclosure provide a communication method, network element, terminal, communication system, and storage medium to implement a method for obtaining / storing / updating user information in the 5G CN. The user information (including user identifier, device, user-specific QoS settings) can be stored in the UDM as part of the subscription data, and the user information can be carried in the 5G CN using a registration procedure.

[0155] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to a communication method, and the method includes:

[0156] Step S201: Terminal 101 sends a second request to the second network element 1032.

[0157] In some embodiments, the second network element 1032 is an AMF, and the AMF receives the second request.

[0158] In some embodiments, the second request is used to trigger step S202.

[0159] In some embodiments, the name of the second request is not limited, and it can be, for example, a specific request.

[0160] In some embodiments, the second request is a registration request in a registration process. In some embodiments, the second request is a service request in a service request process. In addition, in some embodiments, the second request can also be a specific request in other network access processes, such as a security verification request.

[0161] In some embodiments, the second request includes first user information of the terminal 101. Optionally, the user corresponding to the first user information may be a real person using the terminal 101, an application running on the terminal 101 or connected through the terminal 101, or a device (such as a PINE) behind the terminal 101 (such as the terminal 101 being a gateway UE, such as a PEGC).

[0162] In some embodiments, the first user information includes at least one of the following:

[0163] User identifier;

[0164] The device identifier of the terminal;

[0165] Specific Quality of Service (QoS) settings;

[0166] Security credentials.

[0167] The user identifier refers to the identifier of the user corresponding to the first user information. The specific QoS setting refers to the QoS setting of the user corresponding to the first user information. The QoS settings of different users may be different.

[0168] It should be noted that because 3GPP is a highly secure system, numerous algorithms and protocols have been introduced to ensure not only authentication and confidentiality / privacy, but also other security features such as data integrity and availability. Therefore, when terminal 101 accesses the network, the network performs security processing on terminal 101, which may include legitimacy verification and privacy protection. Terminal 101 can carry security credentials to legally access the network. Security credentials include, but are not limited to, information representing legitimate identity, such as the secret key used during the security establishment process.

[0169] Step S202 : The second network element 1032 sends a first request to the first network element 1031 .

[0170] In some embodiments, the first network element 1031 is a UDM, and the UDM receives the first request.

[0171] In some embodiments, the first request includes first user information, and the first request is used to request the UDM to manage the first user information.

[0172] In some embodiments, the name of the first request is not limited, and it may be, for example, an information management request.

[0173] In some embodiments, the UDM manages the first user information in ways including, but not limited to, storage, update, removal, and other processing methods.

[0174] In some embodiments, when the UDM receives the first user information for the first time, one or more steps from step S203 to step S209 are executed. For example, when the UDM does not store the first user information or the second user information generated based on the first user information, one or more steps from step S203 to step S209 are executed.

[0175] In some embodiments, if the UDM does not receive the first user information for the first time, one or more steps S210 to S214 are executed. For example, if the UDM already stores the first user information or the second user information generated based on the first user information, one or more steps S210 to S214 are executed.

[0176] In step S203 , the first network element 1031 associates the first user information with the subscription data of the terminal 101 .

[0177] In some embodiments, the UDM management of the first user information may include associating or binding the first user information with subscription data of the terminal 101. The subscription data of the terminal 101 may include information such as a network access indication of the terminal 101 and an allowed area.

[0178] Step S204: The first network element 1031 allocates a first ID to the user corresponding to the first user information.

[0179] In some embodiments, the implementation of the UDM managing the first user information may include: allocating an additional first ID to the user corresponding to the first user information.

[0180] In some embodiments, the first ID is associated with subscription data of the terminal 101 .

[0181] Step S205: The first network element 1031 creates second user information according to the first user information.

[0182] In some embodiments, the implementation of the UDM managing the first user information may include: storing the first user information.

[0183] Optionally, the implementation method for storing the first user information may be: if the data structure of the first user information is not a predefined user data structure, then second user information of a predefined user data structure may be created in the UDM according to the first user information, and the second user information may be stored.

[0184] In some embodiments, the second user information includes at least one of the following:

[0185] User identifier;

[0186] a device identifier of the terminal;

[0187] Specific Quality of Service (QoS) settings;

[0188] security credentials;

[0189] First ID.

[0190] In some embodiments, the second user information may be stored in predefined user profile data (User Profile Data).

[0191] In some embodiments, the second user information is associated with the subscription data of the terminal 101 .

[0192] Alternatively, if the data structure of the first user information is a predefined user data structure, the first user information may be stored directly in the UDM. In some embodiments, step S205 may be replaced by directly storing the first user information in the predefined user data structure in the UDM. In some embodiments, when step S205 is replaced by directly storing the first user information in the predefined user data structure in the UDM, the first ID may be added to the first user information before storage.

[0193] Step S206 : The first network element 1031 sends a third request to the third network element 1033 .

[0194] In some embodiments, the third network element 1033 is a UDR, and the UDR receives the third request.

[0195] In some embodiments, the third request is for the UDM to request the UDR to store the second user information.

[0196] In some embodiments, the name of the third request is not limited, and it is, for example, a storage request.

[0197] In some embodiments, the third request includes the second user information.

[0198] Step S207: The third network element 1033 stores the second user information.

[0199] Step S208 : The first network element 1031 sends a first response message to the second network element 1032 .

[0200] In some embodiments, the AMF receives the first response information.

[0201] In some embodiments, the first response information is used to respond to the first request.

[0202] In some embodiments, the first response information includes a first ID.

[0203] Step S209 : The second network element 1032 sends a second response message to the terminal 101 .

[0204] In some embodiments, terminal 101 receives a second response message.

[0205] In some embodiments, the second response information is used to respond to the second request.

[0206] In some embodiments, the second response information includes the first ID. Optionally, the terminal 101 updates the local first user information according to the first ID. For example, the terminal 101 adds the first ID to the first user information.

[0207] In step S210 , the first network element 1031 determines that the first user information includes a first ID, and updates or deletes the second user information corresponding to the first ID stored in the first network element 1031 according to the first user information.

[0208] In some embodiments, the UDM may manage the first user information by: determining that the first user information also includes a first ID, and updating or deleting second user information in a predefined user data structure corresponding to the first ID stored in the UDM according to the first user information.

[0209] In some embodiments, indication information representing update or deletion information may be carried in the first request and the second request to instruct the UDM to perform an operation of updating or deleting information.

[0210] Step S211 : The first network element 1031 sends a fourth request to the third network element 1033 .

[0211] In some embodiments, the UDR receives a fourth request.

[0212] In some embodiments, the fourth request is used by the UDM to request the UDR to update or delete the stored second user information.

[0213] In some embodiments, the name of the fourth request is not limited, and it can be, for example, an update request, a delete request, etc.

[0214] In some embodiments, the fourth request includes the first ID. In some embodiments, the fourth request may carry indication information representing update or deletion information to instruct the UDR to perform an operation of updating or deleting information.

[0215] Step S212: The third network element 1033 updates or deletes the stored second user information.

[0216] In some embodiments, the UDR updates or deletes the corresponding second user information based on the first ID in the fourth request.

[0217] Step S213 , the first network element 1031 sends third response information to the second network element 1032 .

[0218] In some embodiments, the AMF receives a third response message.

[0219] In some embodiments, the third response information is used to respond to the fourth request.

[0220] Step S214 : The second network element 1032 sends a fourth response message to the terminal 101 .

[0221] In some embodiments, when the AMF receives the third response information, it may send a fourth response message to the terminal 101 in response to the successful update or deletion of the second user information corresponding to the first ID.

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

[0223] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

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

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

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

[0227] In some embodiments, deletion or update of information can be indicated by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited to this.

[0228] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 to S214. For example, step S203 may be implemented as an independent embodiment, step S204 may be implemented as an independent embodiment, step S205 may be implemented as an independent embodiment, step S210 may be implemented as an independent embodiment, and steps S203 to S205 may be implemented as independent embodiments, but are not limited thereto.

[0229] In some embodiments, step S203 and step S204 can be exchanged in order or executed simultaneously, step S203 and step S205 can be exchanged in order or executed simultaneously, step S204 and step S205 can be exchanged in order or executed simultaneously, step S206 and step S208 can be exchanged in order or executed simultaneously, and step S211 and step S213 can be exchanged in order or executed simultaneously.

[0230] In some embodiments, step S201, step S202, and step S204 to step S214 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0231] In some embodiments, steps S201 to S203 and steps S205 to S214 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0232] In some embodiments, steps S201 to S204 and steps S206 to S214 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0233] In some embodiments, steps S201 to S209 and steps S2011 to S214 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0234] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0235] FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a communication method, which is executed by the first network element 1031 (UDM), and the method includes:

[0236] Step S3101, receiving a first request.

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

[0238] In some embodiments, the first network element 1031 (UDM) receives the first request sent by the second network element 1032 (AMF), but is not limited thereto and may also receive the first request sent by other entities.

[0239] In some embodiments, the first network element 1031 (UDM) obtains a first request specified by a protocol.

[0240] In some embodiments, the first network element 1031 (UDM) obtains the first request from upper layer(s).

[0241] In some embodiments, the first network element 1031 (UDM) performs processing to obtain the first request.

[0242] In some embodiments, step S3101 is omitted, and the first network element 1031 (UDM) autonomously implements the function indicated by the first request, or the above function is default or by default.

[0243] Step S3102: associate the first user information with the contract data.

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

[0245] Step S3103: assign a first ID to the user corresponding to the first user information.

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

[0247] Step S3104: store the first user information.

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

[0249] Step S3105: Send a third request.

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

[0251] In some embodiments, the first network element 1031 (UDM) sends the third request to the third network element 1033 (UDR), but is not limited thereto and the third request may also be sent to other entities.

[0252] Step S3106: Send the first response information.

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

[0254] In some embodiments, the first network element 1031 (UDM) sends the first response information to the second network element 1032 (AMF), but is not limited thereto, and the first response information may also be sent to other entities.

[0255] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3106. For example, step S3102 may be implemented as an independent embodiment, step S3103 may be implemented as an independent embodiment, and step S3104 may be implemented as an independent embodiment. Steps S3101 to S3104 may be implemented as independent embodiments, but are not limited thereto.

[0256] In some embodiments, step S3102 and step S3103 may be exchanged in order or executed simultaneously, step S3102 and step S3104 may be exchanged in order or executed simultaneously, step S3103 and step S3104 may be exchanged in order or executed simultaneously, and step S3105 and step S3106 may be exchanged in order or executed simultaneously.

[0257] In some embodiments, step S3101 and step S3103 to step S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0258] In some embodiments, step S3101, step S3102, and step S3104 to step S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0259] In some embodiments, steps S3101 to S3103, step S3105, and step S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0260] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to a communication method, which is executed by the first network element 1031 (UDM), and the method includes:

[0261] Step S3201, receiving a first request.

[0262] The optional implementation of step S3201 can refer to step S202 in FIG. 2 , the optional implementation of step S3101 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0263] Step S3202: Update the corresponding second user information according to the first ID in the first user information.

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

[0265] Step S3203: Send the fourth request.

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

[0267] In some embodiments, the first network element 1031 (UDM) sends the fourth request to the third network element 1033 (UDR), but is not limited thereto and the fourth request may also be sent to other entities.

[0268] Step S3204: Send third response information.

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

[0270] In some embodiments, the first network element 1031 (UDM) sends the third response information to the second network element 1032 (AMF), but is not limited thereto, and the third response information may also be sent to other entities.

[0271] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3201 to S3204. For example, step S3202 may be implemented as an independent embodiment, but is not limited thereto.

[0272] In some embodiments, step S3203 and step S3204 may be performed in an interchangeable order or simultaneously.

[0273] In some embodiments, step S3201, step S3203, and step S3204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0274] FIG3C is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a communication method, which is executed by the first network element 1031 (UDM), and the method includes:

[0275] Step S3301, receiving a first request.

[0276] The optional implementation of step S3301 can refer to step S202 in FIG. 2 , the optional implementation of step S3101 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0277] Step S3302: Delete the corresponding second user information according to the first ID in the first user information.

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

[0279] Step S3303: Send the fourth request.

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

[0281] In some embodiments, the first network element 1031 (UDM) sends the fourth request to the third network element 1033 (UDR), but is not limited thereto and the fourth request may also be sent to other entities.

[0282] Step S3304: Send third response information.

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

[0284] In some embodiments, the first network element 1031 (UDM) sends the third response information to the second network element 1032 (AMF), but is not limited thereto. The third response information may also be sent to other entities.

[0285] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3301 to S3304. For example, step S3302 may be implemented as an independent embodiment, but is not limited thereto.

[0286] In some embodiments, step S3303 and step S3304 may be performed in an interchangeable order or simultaneously.

[0287] In some embodiments, step S3301, step S3303, and step S3304 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0288] FIG3D is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to a communication method, which is executed by the first network element 1031 (UDM), and the method includes:

[0289] Step S3401: Receive a first request.

[0290] The optional implementation of step S3401 can refer to step S202 in FIG. 2 , the optional implementation of step S3101 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0291] Step S3402: Manage the first user information.

[0292] The optional implementation methods of step S3402 can be found in steps S203 to S205, step S210 of Figure 2, steps S3102 to S3104 of Figure 3A, step S3202 of Figure 3B, and the optional implementation methods of step S3302 of Figure 3C, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0293] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3401 to S3402. For example, step S3402 may be implemented as an independent embodiment, but is not limited thereto.

[0294] FIG4A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to a communication method, which is executed by the second network element 1032 (AMF), and the method includes:

[0295] Step S4101, receiving a second request.

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

[0297] In some embodiments, the second network element 1032 (AMF) receives the second request sent by the terminal 101, but is not limited thereto and may also receive the second request sent by other entities.

[0298] In some embodiments, the second network element 1032 (AMF) obtains a second request specified by the protocol.

[0299] In some embodiments, the second network element 1032 (AMF) obtains the second request from upper layer(s).

[0300] In some embodiments, the second network element 1032 (AMF) performs processing to obtain the second request.

[0301] In some embodiments, step S4101 is omitted, and the second network element 1032 (AMF) autonomously implements the function indicated by the second request, or the above function is default or by default.

[0302] Step S4102: Send a first request.

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

[0304] In some embodiments, the second network element 1032 (AMF) sends the first request to the first network element 1031 (UDM), but is not limited thereto and the first request may also be sent to other entities.

[0305] Step S4103: Receive a first response message.

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

[0307] In some embodiments, the second network element 1032 (AMF) receives the first response message sent by the first network element 1031 (UDM), but is not limited thereto and may also receive the first response message sent by other entities.

[0308] In some embodiments, the second network element 1032 (AMF) obtains a first response message specified by the protocol.

[0309] In some embodiments, the second network element 1032 (AMF) obtains the first response message from the upper layer(s).

[0310] In some embodiments, the second network element 1032 (AMF) performs processing to obtain a first response message.

[0311] In some embodiments, step S4103 is omitted, and the second network element 1032 (AMF) autonomously implements the function indicated by the first response message, or the above function is default or by default.

[0312] Step S4104: Send a second response message.

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

[0314] In some embodiments, the second network element 1032 (AMF) sends a second response message to the terminal 101, but is not limited to this, and the second response message may also be sent to other entities.

[0315] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4104. For example, step S4102 may be implemented as an independent embodiment, but is not limited thereto.

[0316] In some embodiments, step S4101, step S4103, and step S4104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0317] FIG4B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to a communication method, which is executed by the second network element 1032 (AMF), and the method includes:

[0318] Step S4201, receiving a second request.

[0319] The optional implementation of step S4201 can refer to the optional implementation of step S201 in Figure 2, step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0320] Step S4202, sending a first request.

[0321] The optional implementation of step S4202 can refer to the optional implementation of step S202 in Figure 2, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0322] Step S4203: Receive a third response message.

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

[0324] In some embodiments, the second network element 1032 (AMF) receives the third response message sent by the first network element 1031 (UDM), but is not limited thereto and may also receive the third response message sent by other entities.

[0325] In some embodiments, the second network element 1032 (AMF) obtains a third response message specified by the protocol.

[0326] In some embodiments, the second network element 1032 (AMF) obtains the third response message from the upper layer(s).

[0327] In some embodiments, the second network element 1032 (AMF) performs processing to obtain a third response message.

[0328] In some embodiments, step S4203 is omitted, and the second network element 1032 (AMF) autonomously implements the function indicated by the third response message, or the above function is default or by default.

[0329] Step S4204: Send a fourth response message.

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

[0331] In some embodiments, the second network element 1032 (AMF) sends a fourth response message to the terminal 101, but is not limited to this, and the fourth response message may also be sent to other entities.

[0332] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4204. For example, step S4202 may be implemented as an independent embodiment, but is not limited thereto.

[0333] In some embodiments, step S4201, step S4203, and step S4204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0334] FIG5A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5A , the present disclosure embodiment relates to a communication method, which is executed by the terminal 101 side, and the method includes:

[0335] Step S5101, sending a second request.

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

[0337] In some embodiments, the terminal 101 sends the second request to the second network element 1032, but is not limited thereto, and the second request may also be sent to other entities.

[0338] Step S5102: Receive a second response message.

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

[0340] In some embodiments, the terminal 101 receives the second response message sent by the second network element 1032, but is not limited thereto and may also receive the second response message sent by other entities.

[0341] In some embodiments, terminal 101 obtains a second response message specified by the protocol.

[0342] In some embodiments, terminal 101 obtains the second response message from upper layer(s).

[0343] In some embodiments, terminal 101 performs processing to obtain a second response message.

[0344] In some embodiments, step S5102 is omitted, and the terminal 101 autonomously implements the function indicated by the second response message, or the above function is default or by default.

[0345] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5102. For example, step S5101 may be implemented as an independent embodiment, but is not limited thereto.

[0346] In some embodiments, step S5102 is optional and may be omitted or replaced in different embodiments.

[0347] FIG5B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5B , the present disclosure embodiment relates to a communication method, which is executed by the terminal 101 side, and the method includes:

[0348] Step S5201, sending a second request.

[0349] The optional implementation of step S5201 can refer to the optional implementation of step S201 in Figure 2, step S5101 in Figure 5A, and other related parts in the embodiments involved in Figures 2 and 5A, which will not be repeated here.

[0350] Step S5202: Receive the fourth response message.

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

[0352] In some embodiments, the terminal 101 receives the fourth response message sent by the second network element 1032, but is not limited thereto. The terminal 101 may also receive the fourth response message sent by other entities.

[0353] In some embodiments, terminal 101 obtains a fourth response message specified by the protocol.

[0354] In some embodiments, the terminal 101 obtains the fourth response message from an upper layer(s).

[0355] In some embodiments, terminal 101 performs processing to obtain a fourth response message.

[0356] In some embodiments, step S5202 is omitted, and the terminal 101 autonomously implements the function indicated by the fourth response message, or the above function is default or by default.

[0357] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5201 and S5202. For example, step S5201 may be implemented as an independent embodiment, but is not limited thereto.

[0358] In some embodiments, step S5202 is optional and may be omitted or replaced in different embodiments.

[0359] FIG6A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6A , the embodiment of the present disclosure relates to a communication method, which is executed by the third network element 1033 (UDR), and the method includes:

[0360] Step S6101, receiving the third request.

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

[0362] In some embodiments, the third network element 1033 receives the third request sent by the first network element 1031, but is not limited thereto and may also receive the third request sent by other entities.

[0363] In some embodiments, the third network element 1033 obtains a third request specified by the protocol.

[0364] In some embodiments, the third network element 1033 obtains the third request information from an upper layer(s).

[0365] In some embodiments, the third network element 1033 performs processing to obtain a third request.

[0366] In some embodiments, step S6101 is omitted, and the third network element 1033 autonomously implements the function indicated by the third request, or the above function is default or by default.

[0367] Step S6102: store the second user information.

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

[0369] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6101 to S6102. For example, step S6102 may be implemented as an independent embodiment, but is not limited thereto.

[0370] In some embodiments, step S6101 is optional and may be omitted or replaced in different embodiments.

[0371] FIG6B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6B , the embodiment of the present disclosure relates to a communication method, which is executed by the third network element 1033 (UDR), and the method includes:

[0372] Step S6201, receiving the fourth request.

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

[0374] In some embodiments, the third network element 1033 receives the fourth request sent by the first network element 1031 , but is not limited thereto and may also receive the fourth request sent by other entities.

[0375] In some embodiments, the third network element 1033 obtains a fourth request specified by the protocol.

[0376] In some embodiments, the third network element 1033 obtains the fourth request information from an upper layer(s).

[0377] In some embodiments, the third network element 1033 performs processing to obtain the fourth request.

[0378] In some embodiments, step S6201 is omitted, and the third network element 1033 autonomously implements the function indicated by the fourth request, or the above function is default or by default.

[0379] Step S6202: Update or delete the second user information.

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

[0381] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6201 to S6202. For example, step S6202 may be implemented as an independent embodiment, but is not limited thereto.

[0382] In some embodiments, step S6201 is optional and may be omitted or replaced in different embodiments.

[0383] FIG7A is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG7A , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0384] Step S7101: The terminal sends a second request to the AMF, where the second request includes the first user information.

[0385] The optional implementation of step S7101 can refer to the optional implementation of step S201 in Figure 2, step S4101 in Figure 4A, step S5101 in Figure 5A, and other related parts in the embodiments involved in Figures 2, 4A, and 5A, which will not be repeated here.

[0386] Step S7102: AMF sends a first request to UDM, where the first request includes first user information.

[0387] The optional implementation of step S7102 can refer to the optional implementation of step S202 in Figure 2, step S3101 in Figure 3A, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 3A, and 4A, which will not be repeated here.

[0388] Step S7103: UDM manages the first user information.

[0389] Optional implementations of step S7103 may refer to steps S203 to S205 and S210 in FIG. 2 , optional implementations of steps S3102 to S3104 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

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

[0391] FIG7B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG7B , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0392] Step S7201, UDM receives a first request sent by an access and mobility management function network element AMF, where the first request is sent by the AMF after receiving a second request sent by the terminal, and the first request includes the first user information of the terminal.

[0393] The optional implementation of step S7201 can refer to the optional implementation of step S202 in Figure 2, step S3101 in Figure 3A, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 3A, and 4A, which will not be repeated here.

[0394] Step S7202: UDM manages the first user information.

[0395] The optional implementation of step S7202 can refer to the optional implementation of steps S203 to S205 and step S210 in Figure 2, steps S3102 to S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

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

[0397] In some embodiments, defining a user profile / user context / user description information / user data / user information (User Profile) includes the following user information:

[0398] User identifier;

[0399] equipment;

[0400] Relevant safety certificates;

[0401] User-specific QoS settings.

[0402] In some embodiments, the user profile is stored in the UE, UDM or UDR.

[0403] In some embodiments, user profile data is defined to store the user profile of the user.

[0404] FIG7C is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG7C , the embodiment of the present disclosure relates to a communication method, and the method includes the following steps:

[0405] 1. The UE sends a registration request to the AMF via the gNB, which includes a user profile consisting of a user identifier, device ID, and user-specific QoS settings (corresponding to the first user information in the above embodiment).

[0406] 2. When a user profile is detected, AMF sends a user profile management request to UDM (including the user profile consisting of user identifier, device ID, and user-specific QoS settings.

[0407] 3. If the association ID (corresponding to the first ID in the aforementioned embodiment) is not included, UDM will create a user profile in the user profile data (corresponding to the second user information in the aforementioned embodiment); and when associating the user profile with the contract data, assign an association ID to the user profile.

[0408] 4. UDM sends a user profile management response including the user profile (association ID) to AMF.

[0409] 5. The AMF sends a registration acceptance message to the UE via the gNB, including the user profile (association ID).

[0410] 6. The UE updates the local user profile based on the association ID.

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

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

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

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

[0415] Figure 8A is a structural diagram of the first network element proposed according to an embodiment of the present disclosure. As shown in Figure 8A, the first network element 8100 may include: at least one of a transceiver module 8101, a processing module 8102, etc. In some embodiments, the transceiver module 8101 is used to receive a first request sent by an access and mobility management function network element AMF, wherein the first request is sent by the AMF after receiving a second request sent by the terminal, and the first request includes the first user information of the terminal; the processing module 8102 is used to manage the first user information. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving executed by the first network element 1031 in any of the above methods (for example, step S201, step S202, step S206, step S208, step S209, step S211, step S213, step S214, but not limited thereto), which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps (for example, step S203, step S204, step S205, step S207, step S210, step S212, but not limited to these) performed by the first network element 1031 in any of the above methods, which are not repeated here.

[0416] In some embodiments, the first user information includes at least one of the following:

[0417] User identifier;

[0418] a device identifier of the terminal;

[0419] Specific Quality of Service (QoS) settings;

[0420] Security credentials.

[0421] In some embodiments, the second request is any one of the following:

[0422] Registration request;

[0423] Service Request.

[0424] In some embodiments, the processing module 8101 is configured to store the first user information.

[0425] In some embodiments, the processing module 8101 is configured to create second user information of a predefined user data structure in the UDM according to the first user information.

[0426] In some embodiments, the processing module 8101 is configured to associate the first user information with the subscription data of the terminal.

[0427] In some embodiments, the processing module 8101 is configured to assign a first ID to the user corresponding to the first user information.

[0428] In some embodiments, the above-mentioned transceiver module 8102 is used to send a first response message to the AMF, where the first response message includes the first ID.

[0429] In some embodiments, the processing module 8101 is configured to determine that the first user information further includes a first ID, and update or delete second user information of a predefined user data structure corresponding to the first ID stored in the UDM according to the first user information.

[0430] In some embodiments, the transceiver module 8102 is configured to send a third request to the structured data storage network element UDR, where the third request is used by the UDM to request the UDR to store the second user information.

[0431] In some embodiments, the transceiver module 8102 is configured to send a fourth request to the UDR, where the fourth request is used by the UDM to request the UDR to update or delete the stored second user information.

[0432] Figure 8B is a structural diagram of the second network element proposed according to an embodiment of the present disclosure. As shown in Figure 8B, the second network element 8200 may include: at least one of a transceiver module 8201, a processing module 8202, etc. In some embodiments, the transceiver module 8201 is used to receive a second request sent by the terminal, the second request including the first user information of the terminal; send a first request to the UDM, the first request including the first user information, and the first request is used to request the UDM to manage the first user information. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S201, step S202, step S206, step S208, step S209, step S211, step S213, step S214, but not limited to this) performed by the second network element 1032 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps (for example, step S203, step S204, step S205, step S207, step S210, step S212, but not limited to these) performed by the second network element 1032 in any of the above methods, which are not repeated here.

[0433] In some embodiments, the first user information includes at least one of the following:

[0434] User identifier;

[0435] a device identifier of the terminal;

[0436] Specific Quality of Service (QoS) settings;

[0437] Security credentials.

[0438] In some embodiments, the second request is any one of the following:

[0439] Registration request;

[0440] Service Request.

[0441] In some embodiments, the above-mentioned transceiver module 8201 is used to receive a first response message sent by the UDM, the first response message includes a first ID, and the first ID is the ID assigned by the UDM to the user corresponding to the first user information; and send a second response message to the terminal, the second response message includes the first ID.

[0442] Figure 8C is a structural diagram of a terminal proposed according to an embodiment of the present disclosure. As shown in Figure 8C, the terminal 8300 may include: at least one of a transceiver module 8301, a processing module 8302, etc. In some embodiments, the transceiver module 8301 is used to send a second request to the AMF, the second request including the first user information of the terminal, the first user information being used for the AMF to send a first request including the first user information to the UDM, the first request being used for the AMF to request the UDM to manage the first user information. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving executed by the terminal 101 in any of the above methods (for example, step S201, step S202, step S206, step S208, step S209, step S211, step S213, step S214, but not limited thereto), which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps (such as step S203, step S204, step S205, step S207, step S210, step S212, but not limited to these) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0443] In some embodiments, the first user information includes at least one of the following:

[0444] User identifier;

[0445] a device identifier of the terminal;

[0446] Specific Quality of Service (QoS) settings;

[0447] Security credentials.

[0448] In some embodiments, the second request is any one of the following:

[0449] Registration request;

[0450] Service Request.

[0451] In some embodiments, the transceiver module 8301 is configured to receive a second response message sent by the AMF, where the second response message includes a first ID, where the first ID is an ID assigned by the UDM to the user corresponding to the first user information;

[0452] The processing module 8302 is configured to update the local first user information according to the first ID.

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

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

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

[0456] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 9100 is used to perform any of the above methods. Optionally, one or more processors 9101 are used to call instructions to enable the communication device 9100 to perform any of the above methods.

[0457] In some embodiments, the communication device 9100 further includes one or more transceivers 9102. When the communication device 9100 includes one or more transceivers 9102, the transceiver 9102 performs at least one of the communication steps (e.g., steps S201, S202, S206, S208, S209, S211, S213, and S214, but not limited thereto) of sending and / or receiving in the above method, and the processor 9101 performs at least one of the other steps (e.g., steps S203, S204, S205, S207, S210, and S212, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

[0458] In some embodiments, the communication device 9100 further includes one or more memories 9103 for storing data. Alternatively, all or part of the memories 9103 may be located outside the communication device 9100. In alternative embodiments, the communication device 9100 may include one or more interface circuits 9104. Optionally, the interface circuits 9104 are connected to the transceiver 9102 and may be configured to receive data from the transceiver 9102 or other devices, and to send data to the memories 9103 or other devices. For example, the interface circuits 9104 may read data stored in the memories 9103 and send the data to the processor 9101.

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

[0460] 9B is a schematic diagram of the structure of a chip 9200 according to an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9B , but the present disclosure is not limited thereto.

[0461] The chip 9200 includes one or more processors 9201. The chip 9200 is configured to execute any of the above methods.

[0462] In some embodiments, chip 9200 further includes one or more interface circuits 9202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 9200 further includes one or more memories 9203 for storing data. Alternatively, all or part of memory 9203 may be located external to chip 9200. Optionally, interface circuit 9202 is connected to memory 9203 and may be used to receive data from memory 9203 or other devices, or may be used to send data to memory 9203 or other devices. For example, interface circuit 9202 may read data stored in memory 9203 and send the data to processor 9201.

[0463] In some embodiments, the interface circuit 9202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S201, step S202, step S206, step S208, step S209, step S211, step S213, and step S214, but not limited thereto). The interface circuit 9202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 9202 performs data exchange between the processor 9201, chip 9200, memory 9203, or transceiver device. In some embodiments, the processor 9201 performs at least one of the other steps (e.g., step S203, step S204, step S205, step S207, step S210, and step S212, but not limited thereto).

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

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

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

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

Claims

1. A communication method, characterized in that, Performed by the Unified Data Management Network Element (UDM), the method includes: Receiving a first request sent by the Access and Mobility Management Function Network Element (AMF), where the first request is sent by the AMF after receiving a second request sent by the terminal, and the first request includes first user information of the terminal; Managing the first user information.

2. The method according to claim 1, wherein The first user information includes at least one of the following: User identifier; Device identifier of the terminal; Specific Quality of Service (QoS) setting; Security credential.

3. The method according to claim 1 or 2, wherein The second request is any one of the following: Registration request; Service request.

4. The method according to any one of claims 1 to 3, characterized in that, The managing of the first user information includes: Storing the first user information.

5. The method according to claim 4, wherein The storing of the first user information includes: Creating second user information of a predefined user data structure in the UDM according to the first user information.

6. The method according to any one of claims 1-5, characterized in that, The managing of the first user information includes: Associating the first user information with the subscription data of the terminal.

7. The method according to claim 6, characterized in that, The managing of the first user information includes: Assigning a first ID to the user corresponding to the first user information.

8. The method according to claim 7, wherein The method further includes: Sending a first response message to the AMF, where the first response message includes the first ID.

9. The method according to any one of claims 1 to 3, characterized in that, The managing of the first user information includes: Determining that the first user information further includes a first ID, and updating or deleting the second user information of the predefined user data structure corresponding to the first ID stored in the UDM according to the first user information.

10. The method according to claim 5, wherein The method further includes: Sending a third request to the Structured Data Repository Network Element (UDR), where the third request is for the UDM to request the UDR to store the second user information.

11. The method according to claim 9, wherein The method further includes: Sending a fourth request to the UDR, where the fourth request is for the UDM to request the UDR to update or delete the stored second user information.

12. A communication method, characterized in that, Performed by the AMF, the method includes: Receiving a second request sent by the terminal, where the second request includes first user information of the terminal; Sending a first request to the UDM, where the first request includes the first user information, and the first request is for requesting the UDM to manage the first user information.

13. The method according to claim 12, wherein The first user information includes at least one of the following: User identifier; Device identifier of the terminal; Specific Quality of Service (QoS) setting; Security credential.

14. The method according to claim 12 or 13, wherein The second request is any one of the following: Registration request; Service request.

15. The method according to any one of claims 12 - 14, characterized in that, The method further includes: Receiving a first response message sent by the UDM, where the first response message includes a first ID, and the first ID is an ID assigned by the UDM to the user corresponding to the first user information; Sending a second response message to the terminal, where the second response message includes the first ID.

16. A communication method, characterized in that, Performed by the terminal, the method includes: Send a second request to the AMF, the second request including first user information of the terminal, the first user information being used for the AMF to send a first request including the first user information to the UDM, the first request being for the AMF to request the UDM to manage the first user information.

17. The method according to claim 16, wherein the first user information includes at least one of the following: User identifier; Device identifier of the terminal; Specific quality of service (QoS) setting; Security credentials.

18. The method according to claim 16 or 17, wherein the second request is any one of the following: Registration request; Service request.

19. The method according to any one of claims 16 - 18, characterized in that, The method further includes: Receiving second response information sent by the AMF, the second response information including a first ID, the first ID being an ID assigned by the UDM to the user corresponding to the first user information; Updating the first user information locally according to the first ID.

20. A first network element, characterized in that, including: A transceiver module, configured to receive a first request sent by an access and mobility management function network element (AMF), the first request being sent by the AMF after receiving a second request sent by a terminal, the first request including first user information of the terminal; A processing module, configured to manage the first user information.

21. A second network element, characterized in that, including: A transceiver module, configured to receive a second request sent by a terminal, the second request including first user information of the terminal; Sending a first request to the UDM, the first request including the first user information, the first request being for requesting the UDM to manage the first user information.

22. A terminal, characterized in that, including: A transceiver module, configured to send a second request to the AMF, the second request including first user information of the terminal, the first user information being used for the AMF to send a first request including the first user information to the UDM, the first request being for the AMF to request the UDM to manage the first user information.

23. A first network element, characterized in that, including: One or more processors; A memory coupled to the processor, having executable instructions stored thereon, which when executed by the processor cause the first network element to perform the communication method according to any one of claims 1-11.

24. A second network element, characterized in that, including: One or more processors; A memory coupled to the processor, having executable instructions stored thereon, which when executed by the processor cause the second network element to perform the communication method according to any one of claims 12-15.

25. A terminal, characterized in that, including: One or more processors; A memory coupled to the processor, having executable instructions stored thereon, which when executed by the processor cause the terminal to perform the communication method according to any one of claims 16-19.

26. A communication system, characterized in that, It includes a first network element, a second network element, and a terminal. Among them, the first network element is configured to implement the communication method described in any one of claims 1-11, the second network element is configured to implement the communication method described in any one of claims 12-15, and the terminal is configured to implement the communication method described in any one of claims 16-19.

27. A storage medium storing instructions, characterized in that, When the instruction runs on the communication device, it causes the communication device to execute the communication method described in any one of claims 1-19.

Images