Communication method, device and system

Abstract

The invention provides a communication method, device and system, which can be applied to a scene of satisfactory communication. The method is applied to a network intelligent agent function network element NIAF, the NIAF receives first information, and the first information is used for describing the intention of a first user; determining a first sub-network according to the intention of the first user, the first sub-network being determined from at least one sub-network, or the first sub-network being established by an NIAF; and sending second information, wherein the second information indicates the first subnet. The NIAF selects the subnet for the user based on the user intention or performs networking based on the user intention, the user does not need to perform networking by himself, the difficulty of networking by using equipment by the user is reduced, the user demand can be met in time, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of communications. In particular, it relates to a communication method, apparatus, and system. Background Art

[0002] Semantic communication redefines the protocol interface between the terminal and the network, changing from signaling-driven to intent-driven, and realizing the semantic transformation and efficient transmission of "human-machine-data-spirit" communication intents based on network-native artificial intelligence (AI), driving network functions, intelligent agents, and multimodal terminals to achieve user intents. In the current technology, networking requires professional knowledge from users, which is not user-friendly. For example, a user may just want to use their mobile phone to control a camera to check their home, but they must first learn how to network the devices, which increases the difficulty of using the devices for the user and affects the user experience. Summary of the Invention

[0003] This application provides a communication method, apparatus, and system that can reduce the difficulty of using devices for users and improve the user experience.

[0004] In a first aspect, a communication method is provided, which is applied to a Network Intelligent Agent Function Network Element (NIAF). This method can be executed by the NIAF, or by a module (such as a chip or circuit) in the NIAF, or by a logical node, logical module, or software that can implement all or part of the NIAF functions. This application does not limit this.

[0005] The method includes: receiving first information, where the first information is used to describe the intent of a first user; determining a first subnet according to the intent of the first user, where the first subnet is determined from at least one subnet, or the first subnet is formed by the NIAF; and sending second information, where the second information indicates the first subnet.

[0006] In this method, the intent of the user indirectly expresses that the first device interacts with devices in a subnet, or the third device accessed by the first device to the communication network interacts with devices in a subnet.

[0007] In this method, the NIAF accesses the first subnet for the first device or forms the first subnet for the third device based on the user intent, reducing the difficulty of using device networking for the user and being able to meet the user's needs in a timely manner, improving the user experience.

[0008] In some implementations, the first subnet is determined from at least one subnet. Determining the first subnet according to the intention of the first user includes: determining the service type of the subnet that the first user requests to access according to the intention of the first user, and the first subnet is the subnet among the at least one subnet that has the same service type as the subnet that the first user requests to access.

[0009] Or, determining the service type of the subnet that the first user requests to access according to the intention of the first user; among the at least one subnet, taking the subnet that has the same service type as the subnet that the first user requests to access as the first subnet.

[0010] In this way, selecting a subnet with the same service type to provide to the user can meet the user's needs.

[0011] In some implementations, the method further includes: receiving a first user identifier from the first device, the first user identifier being associated with the first user; determining the at least one subnet according to the first user identifier, and the at least one subnet belongs to the subnets subscribed by the first user.

[0012] In this way, the first user is the user of the subscribed subnet, so the subscribed subnet can be directly obtained.

[0013] In some implementations, the method further includes: receiving a first user identifier, the first user identifier being associated with the first user;

[0014] Determining the at least one subnet according to the first user identifier and the relationship information between the first user and the second user, the at least one subnet belongs to the subnets subscribed by the second user, and the relationship information between the first user and the second user is included in the intention of the first user.

[0015] In this way, the first user and the user (second user) of the subscribed subnet are not the same person, but the subnet information subscribed by the second user can be obtained through the relationship information, avoiding the inability to access the subnet.

[0016] In some implementations, the method further includes: determining to allow the first device to access the first subnet according to the verification information of the second user, where the first device is the device that sends the intention of the first user.

[0017] Optionally, NIAF can contact the digital human avatar of the second user or user M himself (such as sending a confirmation text message) to confirm whether to allow the first user to access the first subnet.

[0018] This way can further improve the security of using the subnets subscribed by the second user.

[0019] In some implementations, the method further includes: updating the subscription information so that the subscription information of the first subnet includes the identifier of the first user, or the subscription information of the identifier of the first user includes the identifier of the first subnet.

[0020] In this way, updating the subscription information can facilitate subsequent subnet access.

[0021] In some implementations, the second information includes the identifier of the first subnet.

[0022] In some implementations, the identifier of the first subnet is used by the first device to establish a first protocol data unit (PDU) session, and the first device is the device that sends the intention of the first user.

[0023] In some implementations, if the first PDU session and the second PDU session established with a second device in the first subnet are in different administrative domains, the method further includes: establishing a communication tunnel between a second network element and a third network element, where the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0024] This way provides a communication method in a scenario where they are not in the same administrative domain, increasing the compatibility of the solution with multiple communication scenarios.

[0025] In some implementations, the first subnet is formed by the NIAF, and the method includes: forming the first subnet by combining at least two devices according to the intention of the first user, where the at least two devices include a third device and a fourth device, where the third device belongs to a second subnet, the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

[0026] In this way, the NIAF forms a new subnet between devices that are not in the same subnet to meet user requirements, which can improve the user experience.

[0027] In some implementations, the method further includes: receiving a second user identifier associated with the first user; determining the second subnet and the third subnet subscribed to by the first user according to the second user identifier.

[0028] In some implementations, the method further includes: receiving a third user identifier and the identity information of the first user, where the third user identifier is associated with a second user; determining the second subnet subscribed to by the second user according to the third user identifier; determining the third subnet subscribed to by the first user according to the identity information of the first user.

[0029] In some implementations, the method further includes: determining to allow the third device to form a network with the fourth device according to the authentication information of the third user.

[0030] In some implementations, the method further includes: creating subscription information for the first subnet, where the subscription information for the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device, the fourth user identifier being associated with the first user, or updating the subscription information so that the subscription information of the first device and the fourth device includes the identifier of the first subnet.

[0031] In this way, creating new subscription information or updating the subscription information can facilitate subsequent subnet access.

[0032] In some implementations, the second information includes the identifier of the first subnet and the identifier of the third device, the identifier of the first subnet being used to establish a third PDU session, and the method further includes: sending third information to a fifth device, the third information including the identifier of the first subnet and the identifier of the fourth device, the identifier of the first subnet being used for the fifth device to establish a fourth PDU session, and the fourth device accesses the communication network through the fifth device.

[0033] In some implementations, sending the second information to the first device includes: sending the second information to the first device via a first application server, the first application server being the application server registered for the first device; sending the third information to the fifth device includes: sending the third information to the fifth device via a second application server, the second application server being the application server registered for the fifth device.

[0034] In some implementations, the third PDU session and the fourth PDU session are in different administrative domains, and the method further includes: establishing a communication tunnel between a fourth network element and a fifth network element, the fourth network element being the user plane network element of the third PDU session, and the fifth network element being the user plane network element of the fourth PDU session.

[0035] This way provides a communication method after forming a new subnet in a scenario where they are not in the same administrative domain, increasing the compatibility of the solution with various communication scenarios.

[0036] In a second aspect, a communication method is provided. This method can be executed by a terminal device (such as the first device), or can be executed by a module (such as a chip or circuit) in the terminal device, or can also be executed by a logical node, logical module or software that can implement all or part of the functions of the terminal device. This application does not make any limitations in this regard. This method is applied to the first device.

[0037] The method includes: sending first information for describing the intention of a first user; receiving second information indicating a first subnet, where the first subnet is determined according to the intention of the first user, the first subnet is determined from at least one subnet, or the first subnet is formed by NIAF; accessing the first subnet according to the second information.

[0038] In this method, the intention of the user indirectly expresses that the first device interacts with devices in a subnet, or the third device accessing the communication network through the first device interacts with devices in a subnet.

[0039] In some implementations, the first subnet is determined from at least one subnet, and the first subnet is a subnet with the same service type as the subnet that the first user requests to access, and the service type of the subnet that the first user requests to access is determined according to the intention of the first user.

[0040] In some implementations, the method further includes: sending a first user identifier associated with the first user, where the first user identifier is used to determine the at least one subnet, and the at least one subnet belongs to the subnets subscribed by the first user.

[0041] In some implementations, a first user identifier associated with the first user is sent, and the first user identifier and the relationship information between the first user and the second user are used to determine the at least one subnet, and the at least one subnet belongs to the subnets subscribed by the second user, and the relationship information between the first user and the second user is included in the intention of the first user.

[0042] In some implementations, the first device being allowed to access the first subnet is determined according to the authentication information of the second user.

[0043] In some implementations, the method further includes: updating the subscription information so that the subscription information of the first subnet includes the identifier of the first user, or the subscription information of the identifier of the first user includes the identifier of the first subnet.

[0044] In some implementations, the second information includes the identifier of the first subnet.

[0045] In some implementations, a first PDU session is established according to the identifier of the first subnet.

[0046] In some implementations, the second PDU session established between the first device and the second device in the first subnet is in a different administrative domain. The first device interacts with the second device through a communication tunnel between a second network element and a third network element. The second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0047] In some implementations, the first subnet is formed by the NIAF. The first subnet is composed of at least two devices according to the intention of the first user. The at least two devices include a third device and a fourth device. The third device belongs to a second subnet, and the fourth device belongs to a third subnet. The second subnet is different from the third subnet.

[0048] In some implementations, the method further includes: sending a second user identifier, which is associated with the first user and is used to determine the second subnet and the third subnet subscribed by the first user.

[0049] In some implementations, the method further includes: sending a third user identifier and the identity information of the first user. The third user identifier is associated with a second user and is used to determine the second subnet subscribed by the second user. The identity information of the first user is used to determine the third subnet subscribed by the first user.

[0050] In some implementations, the permission for the third device and the fourth device to form a network is determined according to the verification information of the second user.

[0051] In some implementations, the subscription information of the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device. The fourth user identifier is associated with the first user. Alternatively, the subscription information of the first device and the fourth device includes the identifier of the first subnet.

[0052] In some implementations, the second information is from the NIAF and is forwarded via the first application server, which is the application server registered for the first device.

[0053] In some implementations, the second information includes the identifier of the first subnet and the identifier of the second device.

[0054] In some implementations, a third PDU session is established according to the identifier of the first subnet.

[0055] In some implementations, the fourth PDU session established between the first PDU session and the fourth device is in a different management domain. The first device communicates with the fourth device through a communication tunnel between the fourth network element and the fifth network element. The fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0056] It should be understood that the second aspect is the implementation on the terminal device side corresponding to the first aspect. The explanations, supplements, and descriptions of the beneficial effects regarding the first aspect are equally applicable to the second aspect and will not be elaborated herein.

[0057] In a third aspect, a communication device is provided. The device can be a network element (such as NIAF), a module in the network element (such as a chip or a circuit), or a logical node, logical module, or software that can implement all or part of the functions of the network element. The device includes: a transceiver unit configured to receive first information from the first device, where the first information is used to describe the intention of a first user; second information is used to describe the intention; a processing unit configured to determine a first subnet according to the intention of the first user. The first subnet is determined from at least one subnet, or the first subnet is formed by the NIAF, and the first subnet is used for the first device to access; the transceiver unit is further configured to send second information to the first device, where the second information indicates the first subnet.

[0058] In some implementations, the first subnet is determined from at least one subnet. The processing unit is configured to determine the service type of the subnet to which the first user requests access according to the intention of the first user, and the first subnet is the subnet among the at least one subnet that has the same service type as the subnet to which the first user requests access.

[0059] In some implementations, the transceiver unit is configured to receive a first user identifier that is associated with the first user; determine the at least one subnet according to the first user identifier, where the at least one subnet belongs to the subnets subscribed by the first user.

[0060] In some implementations, the transceiver unit is configured to receive a first user identifier that is associated with the first user; the processing unit is configured to receive a first user identifier that is associated with the first user; determine the at least one subnet according to the first user identifier and the relationship information between the first user and the second user, where the at least one subnet belongs to the subnets subscribed by the second user, and the relationship information between the first user and the second user is included in the intention of the first user.

[0061] In some implementations, the processing unit is configured to determine to allow the first device to access the first subnet according to the authentication information of the second user.

[0062] In some implementations, the processing unit is used to update the subscription information so that the subscription information of the first subnet includes the identifier of the first user, or the subscription information of the identifier of the first user includes the identifier of the first subnet.

[0063] In some implementations, the second information includes the identifier of the first subnet.

[0064] In some implementations, the identifier of the first subnet is used for a first device to establish a first protocol data unit (PDU) session, where the first device is a device that sends the intention of the first user.

[0065] In some implementations, if the first PDU session and a second PDU session established with a second device in the first subnet are in different administrative domains, the processing unit is used to establish a communication tunnel between a second network element and a third network element, where the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0066] In some implementations, the processing unit is used to form the first subnet from at least two devices according to the intention of the first user. The at least two devices include a third device and a fourth device, where the third device belongs to a second subnet, the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

[0067] In some implementations, the transceiver unit is used to receive a second user identifier from the first device, where the second user identifier is associated with the first user. The processing unit is used to determine the second subnet and the third subnet subscribed to by the first user according to the second user identifier.

[0068] In some implementations, the transceiver unit is used to receive a third user identifier from the first device and the identity information of the first user, where the third user identifier is associated with a second user. The second subnet subscribed to by the third user is determined according to the second user identifier. The processing unit is used to determine the third subnet subscribed to by the first user according to the identity information of the first user.

[0069] In some implementations, the processing unit is used to determine to allow the third device to form a network with the fourth device according to the verification information of the third user.

[0070] In some implementations, the processing unit is used to create the subscription information of the first subnet, where the subscription information of the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device, and the fourth user identifier is associated with the first user, or to update the subscription information so that the subscription information of the first device and the fourth device includes the identifier of the first subnet.

[0071] In some implementations, the second information includes the identifier of the first subnet and the identifier of the third device, and the identifier of the first subnet is used to establish a third PDU session. The method further includes: sending third information to a fifth device, where the third information includes the identifier of the first subnet and the identifier of the fourth device, and the identifier of the first subnet is used for the fifth device to establish a fourth PDU session, and the fourth device accesses the communication network through the fifth device.

[0072] In some implementations, the transceiver unit is used to send the second information to the first device via a first application server, and the first application server is the application server registered for the first device; sending the third information to the fifth device includes: sending the third information to the fifth device via a second application server, and the second application server is the application server registered for the fifth device.

[0073] In some implementations, the third PDU session and the fourth PDU session are in different administrative domains, and the processing unit is used to establish a communication tunnel between a fourth network element and a fifth network element, where the fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0074] Fourthly, a communication device is provided. The device can be a terminal device (such as the first device), or a module in the terminal device (such as a chip or a circuit), or a logical node, a logical module or software that can implement all or part of the functions of the terminal device. The device includes: a transceiver unit, configured to send first information, where the first information is used to describe the intention of a first user; the transceiver unit is further configured to receive second information, where the second information indicates a first subnet, and the first subnet is determined according to the intention of the first user, and the first subnet is determined from at least one subnet, or the first subnet is formed by the NIAF; a processing unit, configured to access the first subnet according to the second information.

[0075] In some implementations, the first subnet is determined from at least one subnet, and the first subnet is the subnet among the at least one subnet that has the same service type as the subnet that the first user requests to access, and the service type of the subnet that the first user requests to access is determined according to the intention of the first user.

[0076] In some implementations, the transceiver unit is used to send a first user identifier, the first user identifier is associated with the first user, and the first user identifier is used to determine the at least one subnet, and the at least one subnet belongs to the subnet subscribed by the first user.

[0077] In some implementations, the transceiver unit is used to send a first user identifier, the first user identifier is associated with the first user, and the first user identifier and the relationship information of the first user and the second user are used to determine the at least one subnet, and the at least one subnet belongs to the subnet subscribed by the second user, and the relationship information of the first user and the second user is included in the intention of the first user.

[0078] In some implementations, whether the first device is allowed to access the first subnet is determined according to the authentication information of the second user.

[0079] In some implementations, the processing unit is used to update the subscription information so that the subscription information of the first subnet includes the identifier of the first user, or the subscription information of the identifier of the first user includes the identifier of the first subnet.

[0080] In some implementations, the second information includes the identifier of the first subnet.

[0081] In some implementations, the processing unit is used to establish a first PDU session according to the identifier of the first subnet.

[0082] In some implementations, the second PDU session established between the first device and the second device in the first subnet is in a different management domain, and the first device interacts with the second device through a communication tunnel between a second network element and a third network element, the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0083] In some implementations, the first subnet is formed by the NIAF, and the first subnet is composed of at least two devices according to the intention of the first user, and the at least two devices include a third device and a fourth device, where the third device belongs to a second subnet and the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

[0084] In some implementations, the transceiver unit is used to send a second user identifier, the second user identifier is associated with the first user, and the second user identifier is used to determine the second subnet and the third subnet subscribed by the first user.

[0085] In some implementations, the transceiver unit is used to send the third user identifier and the identity information of the first user. The third user identifier is associated with a second user, and the second user identifier is used to determine the second subnet subscribed by the third user. The identity information of the first user is used to determine the third subnet subscribed by the first user.

[0086] In some implementations, whether the third device and the fourth device are allowed to form a network is determined according to the authentication information of the second user.

[0087] In some implementations, the subscription information of the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device. The fourth user identifier is associated with the first user. Alternatively, the subscription information of the first device and the fourth device includes the identifier of the first subnet.

[0088] In some implementations, the second information comes from the NIAF and is forwarded via the first application server, which is the application server registered for the first device.

[0089] In some implementations, the second information includes the identifier of the first subnet and the identifier of the second device.

[0090] In some implementations, the processing unit is used to establish a third PDU session according to the identifier of the first subnet.

[0091] In some implementations, the first PDU session and the fourth PDU session established with the fourth device are in different administrative domains. The first device communicates with the fourth device through the communication tunnel of the fourth network element and the fifth network element. The fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0092] It should be understood that the third aspect and the fourth aspect are the implementation manners on the device side corresponding to the first aspect and the second aspect respectively. The explanations, supplements, and beneficial effects regarding the first aspect and the second aspect are equally applicable to the third aspect and the fourth aspect, and will not be elaborated here.

[0093] In a fifth aspect, a communication device is provided, including a processor, which is configured to cause the communication device to execute the method described in the first aspect and any possible implementation of the first aspect, or cause the communication device to execute the method described in the second aspect and any possible implementation of the second aspect, by executing a computer program or instruction or through a logic circuit.

[0094] In a possible implementation manner, the communication device further includes a memory, which is used to store the computer program or instruction.

[0095] In one possible implementation, the communication device further includes a communication interface for inputting and / or outputting signals.

[0096] In a sixth aspect, a communication device is provided, including a logic circuit and an input / output interface. The input / output interface is used for inputting and / or outputting signals, and the logic circuit is used to execute the method described in the first aspect or any possible implementation of the first aspect; or, the logic circuit is used to execute the method described in the second aspect and any possible implementation of the second aspect.

[0097] In a seventh aspect, a communication system is provided. The communication system includes the communication device described in any possible implementation of the third aspect, and / or the communication device described in the fourth aspect or any possible implementation of the fourth aspect.

[0098] In an eighth aspect, a computer-readable storage medium is provided. A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs on a computer, the method described in the first aspect or any possible implementation of the first aspect is executed; or, the method described in the second aspect and any possible implementation of the second aspect is executed.

[0099] In a ninth aspect, a computer program product is provided, including instructions. When the instructions run on a computer, the method described in the first aspect or any possible implementation of the first aspect is executed; or, the method described in the second aspect and any possible implementation of the second aspect is executed. Description of the Drawings

[0100] Figure 1 It is a schematic diagram of a communication architecture.

[0101] Figure 2 It is a schematic diagram of an application scenario applicable to the communication method provided in the embodiments of the present application.

[0102] Figure 3 It is a schematic diagram of a communication system provided in the embodiments of the present application.

[0103] Figure 4 It is a schematic flowchart of a communication method provided in the embodiments of the present application.

[0104] Figure 5 In (a) of [reference], it is a schematic diagram of a communication system provided in the embodiments of the present application.

[0105] Figure 5 In (b) of [reference], it is a schematic diagram of a communication system provided in the embodiments of the present application.

[0106] Figure 6It is a schematic flowchart showing the implementation of a communication method provided by an embodiment of the present application.

[0107] Figure 7 It is a schematic flowchart showing the implementation of another communication method provided by an embodiment of the present application.

[0108] Figure 8 It is a schematic flowchart showing the implementation of another communication method provided by an embodiment of the present application.

[0109] Figure 9 It is a schematic flowchart showing the implementation of another communication method provided by an embodiment of the present application.

[0110] Figure 10 It is a schematic block diagram showing the structure of a communication device provided by an embodiment of the present application.

[0111] Figure 11 It is a schematic block diagram showing the structure of another communication device provided by an embodiment of the present application.

[0112] Figure 12 It is a schematic block diagram showing the structure of another communication device provided by an embodiment of the present application. Detailed implementation manners

[0113] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth-generation (5G) system, the sixth-generation (6G) system or new radio (NR), and future communication systems.

[0114] By way of example and not limitation, in the embodiments of the present application, the terminal device in the embodiments of the present application may refer to a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal device may also be a subscriber unit, a terminal device station, a terminal device agent, a terminal device device, a terminal in V2X communication. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, a terminal in a 6G network or a terminal in a future evolved network, etc., and the embodiments of the present application are not limited thereto.

[0115] The terminal device in the embodiments of the present application may also be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a tactile terminal device, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, or a wireless terminal in smart home.

[0116] Among them, wearable devices, also known as wearable intelligent devices, are the general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as head-mounted extended reality (XR) glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are either directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, as well as those that focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0117] In addition, in the embodiments of the present application, the terminal device may also be a terminal device in the Internet of Things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to realize an intelligent network of human-machine interconnection and object-object interconnection.

[0118] In addition, in the present application, the terminal device may also include sensors such as intelligent printers, train detectors, and gas stations. The main functions include collecting data (for some terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0119] The network device in the embodiments of the present application may be a device for communicating with a terminal device. The network device may be a base transceiver station (BTS) in a global system of mobile communication (GSM) or a code division multiple access (CDMA) system, or a node B (NB) in a wideband code division multiple access (WCDMA) system, or an evolutional node base (eNB) in an LTE system, or a radio controller in a cloud radio access network (CRAN) scenario. Alternatively, the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G or 6G network and future communication systems, or a network device in a future evolved PLMN network, etc. It may be an access point (AP) in a WLAN or a gNB in a new radio (NR) system. The embodiments of the present application do not limit this. It can be understood that all or part of the functions of the network device in the present application can also be implemented by software functions running on hardware or by virtualized functions instantiated on a platform (such as a cloud platform).

[0120] Among them, the functions and specific implementation manners of the terminal device and the network device listed above are only for illustrative purposes, and the present application does not limit thereto.

[0121] In the embodiments of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement service processing through processes. For example, the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system, etc. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it can communicate according to the method provided in the embodiments of the present application by running a program recorded with the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application can be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.

[0122] In addition, various aspects or features of the present application can be implemented as a method, an apparatus, or an article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in the present application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (such as hard disks, floppy disks, or magnetic tapes, etc.), optical discs (such as compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (such as erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" can include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0123] Based on the enhanced connection of 5G systems, 6G systems add resources and capabilities in new dimensions such as computing, intelligence, data, and perception. It is no longer a simple pipeline but provides platform-based service capabilities to achieve the intelligent connection of all things. However, the enhanced evolution based on the existing mobile network protocol system will continuously accumulate the complexity of system design and implementation, resulting in unsustainability. The main reason is that the existing network architecture depends on the definition of standardized signaling processes, and the complexity of the architecture system and signaling process design depends on the number of service scenarios, the number of business processes in each scenario, and the number of network functions involved in each business process.

[0124] Figure 1Shows a schematic of a personal Internet of Things (personal IoT network, PIN) device interconnection architecture based on a 5G local area network (5G-LAN). In the figure, two PIN elements with gateway capability (PEGCs), two PIN elements with management capability (PEMCs), and a personal IoT network element (also known as a personal IoT member) belong to the same PIN. The PEGC is a 3GPP UE and has the ability to access the 5G network. The PEMC is used to manage the local network and register the PEGC and PINE with the PIN agent function (AF). The PIN can communicate with other PINEs within the local network or communicate with the 5G network through the PEGC. The PIN AF requests the creation of a 5G virtual network group (VN Group) from the unified data management (UDM) through the network equipment functions (NEF) based on the registration of the PEMC. The request message includes the UE ID of the registered PEGC. The UDM creates a 5G VN Group according to the request and saves the 5G VN Group subscription information, including the 5G VN Group Identifier (External Group ID and Internal Group ID), the members of the 5G VN Group, i.e., the user identifiers of the PEGC (Subscription permanent identifier (SUPI) and generic public subscription identifier (GPSI)), and the data information of the 5G VN Group (protocol data unit session (PDU session) type, data network name (DNN), single network slice selection assistance information (S-NSSAI), etc.).After the PEGC registers to the network, the PCF authorizes the UE policy for the UE according to the subscribed parameters of the 5G VN Group, which is used to indicate the establishment of the UE PDU session. The PEGC requests to establish a PDU session according to the UE Policy (parameters include PDU Session type, DNN, S-NSSAI). When multiple PEGCs belong to the same network management domain, the PDU sessions of different PEGCs usually select the same service management function (SMF). The SMF further configures the user plane function (UPF) according to the parameters of the PDU session to select the same UPF for the PDU session, and realizes the local exchange of data between PEGCs in the UPF. This PEGC#2 can communicate with the camera through the 5GC.

[0125] Currently, all network elements in the PIN must be registered to the AF, and the AF is required to manage the PIN network. That is, the devices in the PIN network must support the application layer protocol with the AF, which results in the inability to interoperate and form a network for devices in different scenarios. For the user experience, network formation requires users to have professional knowledge, which is not user-friendly. For example, if a user just wants to control a camera through a mobile phone to check at home, the user must first learn how to form a network for the device, which increases the difficulty of using the device for the user.

[0126] In view of this, the communication system provided in the embodiments of the present application forms a network for the user based on the user's intention, and the network formation method can be independent of third-party applications, reducing the threshold for the user to form a network for the device.

[0127] Figure 2 It is a schematic diagram of an application scenario applicable to the communication method of the embodiments of the present application. As Figure 2 shown, the system is a meaning-expression communication system, centered on the user, and based on the intention sent by the user through the terminal device, driving multi-modal information interaction among people, machines, numbers, and spirits. Using the capabilities of communication, sensing, computing, numbers, intelligence, etc. endogenous to the intelligent agent, the user's intention is translated into a specific service flow, so as to directly call or indirectly drive the capabilities of multiple objects to achieve the user's intention.

[0128] Among them, the "person" mentioned in the above meaning-expression communication scenario can refer to the user's terminal device, such as Figure 2 the mobile phone shown in, or other terminal devices capable of sending user intentions, including but not limited to tablet computers, computers with wireless transceiver functions, smart watches, etc. The present application does not make specific limitations on this.

[0129] In the above-mentioned communicative scenario of conveying meaning, the "machine" can refer to a machine, that is, a type of terminal device with specific functions or capable of performing specific tasks. For example Figure 2 the XR device or drone shown in Figure 2 , or other terminal devices with specific functions or capable of performing specific tasks, including but not limited to in-vehicle terminal devices, wireless terminals in smart homes, terminal devices in Internet of Things systems, etc. This application does not make specific limitations on this.

[0130] In the above-mentioned communicative scenario of conveying meaning, the "digital being" can refer to a digital human or a digital intelligence human. A digital human or a digital intelligence human is a digital virtual image created based on computer graphics (CG) technology and artificial intelligence technology, with a human appearance or behavior pattern, and capable of intelligent voice interaction, visual recognition, emotional experience, etc. For example Figure 2 the digital intelligence human avatar shown in Figure 2 .

[0131] In the above-mentioned communicative scenario of conveying meaning, the "intelligent entity" can refer to a type of entity with autonomous or semi-autonomous intelligence. The above-mentioned entity can include physical devices, such as Figure 2 the service robot shown in Figure 2 , or other terminal devices with autonomous or semi-autonomous intelligence, including but not limited to robots or robotic dogs, etc.; the above-mentioned entity can also include virtual entities, such as intelligent agents in the network. This intelligent assistant can recognize and understand the intentions and semantics of physical communication objects and / or virtual communication objects, realize the efficient interaction and transmission of intentions and semantics between communication objects, and can assist in task processing.

[0132] An artificial intelligence agent (AI Agent) is an entity based on artificial intelligence (AI) technology, such as the digital human or digital intelligence human corresponding to the "digital being" in the foregoing description, or the virtual entity included in the "intelligent entity" in the foregoing description. Different types of terminal devices include but are not limited to the terminal devices corresponding to the "human", "machine", and "intelligent entity" in the foregoing description.

[0133] As used in the embodiments of the present application, the "intention" refers to the desired result for the target object. The intention includes, but is not limited to, the following information: intention expectation, intention object, intention target, intention context, etc. The intention expectation refers to the business scenario targeted by the intention, such as commissioning a digital human to act on behalf of a user to perform tasks, intelligently driving a terminal device, expanding the computing power of a terminal device, forming a virtual network for a machine group, etc.; the intention object refers to the target object targeted by the intention, such as a terminal device, a base station, a virtual private network, a call application, a computing service, a third-party application, etc.; the intention target refers to the target value that the performance index needs to reach, such as throughput, latency, handover success rate, etc.; the intention context refers to the constraints on the intention expressed through relationships such as comparison, inclusion, association, etc., such as the duration of the intention's action, the priority of the intention, etc. The description form of the intention includes, but is not limited to, natural language, a formatted intention expression model, etc., and the present application does not make specific limitations thereon.

[0134] As used in the embodiments of the present application, the "service flow" refers to the specific information interaction process between the intelligent agent and the object and / or between multiple objects required to complete a specific service in a specific business scenario, that is, the specific implementation manner of the intention. According to the type of the information recipient and the degree of autonomous intelligence, the information for interaction can include specific signaling, can also include a task scheduling strategy, and can also include an intention. The "service flow" in the present application is also referred to as "service".

[0135] The following Figure 3 specifically introduces the communication system 300 provided by the embodiments of the present application. As Figure 4 shown, the system 300 includes a network element 310, and the network element 310 may be a network intelligent agent function (NIAF). The NIAF is an implementation manner of the intelligent agent mentioned above, and is used to receive and recognize the intention from a terminal device (such as an intelligent terminal device) (or rather, the intention sent by the terminal device through an access network (AN)), and translate the intention into a specific information interaction method, so as to directly call or indirectly drive the capabilities of various objects to finally achieve the intention sent by the user through the terminal device. As mentioned above, these objects include, but are not limited to, other NFs or MFs, intelligent agents (such as digital humans), call applications (such as IMS new calls), third-party AFs, and different types of terminal devices, etc.

[0136] The network element 310 can also map an intention to an information interaction method based on a local intention knowledge base. The network element 310 can also have an interaction interface, which can be used to receive an intention, can also be used for the interaction of other types of information, and can also be used to forward an intention or a sub-intention of an intention to other devices. It should be understood that the composition and working process of the above network element 310 are only examples, and the present application does not make specific limitations on the internal design of the network element 310.

[0137] Optionally, the communication system 300 can also include a network element 330, which can be a session management function (SMF). Various terminal devices, including but not limited to mobile phones, XR glasses, Internet of Things terminals, drones, robotic dogs, robots, etc., can establish a session with the network element 310 through the network element 330. In the embodiments of the present application, the session established between the NIAF and the terminal device can be referred to as an intelligent session. This intelligent session is used to implement the intention interaction between the terminal device and the network element 310, and / or to implement the information interaction between the network element 310 and the terminal device required to achieve the intention, including but not limited to semantic information for expressing an intention sent by the terminal device to the network element 310, an intention sent by the network element 310 to an intelligent terminal device capable of recognizing and implementing the intention, specific signaling used by the network element 310 to control the terminal device, and multimodal data (such as sensing data, image data, audio-visual data, etc.) received or collected by the network element 310 from the terminal device. The terminal device can be addressed to the network element 330 through other network elements (such as an access and mobility management function (AMF) network element), or can be directly connected to the network element 330. The present application does not make specific limitations on this. The communication system 300 can also include other network elements, such as a policy control function (PCF), UDM, NEF, UPF.

[0138] The following specifically introduces the communication method provided by the embodiments of the present application based on the above communication system. Figure 4 Fig. shows a schematic flowchart of a communication method 400 provided by an embodiment of the present application. Optionally, Figure 4 The method shown can be applied to Figure 3 the communication system 300 shown.

[0139] In this embodiment, the network element and the terminal device are used as an example of the execution subject of the interaction to illustrate the method, but the present application does not limit the execution subject of this interaction illustration. For example, Figure 4 the network element in can also be a chip, a chip system, or a processor that supports the method that the network element can implement, and can also be a logic module or software that can implement all or part of the functions of the network element; Figure 4The terminal device in [the above] can also be a chip, a chip system, or a processor that supports the method that the terminal device can implement, and can also be a logical module or software that can implement all or part of the functions of the terminal device.

[0140] The following uses NIAF as an example of a network element and the first device as an example of a terminal device for illustration.

[0141] It should be understood that the specific type of the terminal device is not limited in the embodiments of the present application. For example, the terminal device can be a UE, or other types of terminal devices, and the present application does not make specific limitations thereto.

[0142] As Figure 4 shown, the method includes the following steps.

[0143] S410, device #A sends a first piece of information to NIAF. Correspondingly, NIAF receives the first piece of information.

[0144] Device #A is an example of the first device.

[0145] The first piece of information is used to describe the intention of the first user. Therefore, the first piece of information can also be called an intention description. The intention description can be a natural language description, such as text, voice, or image in natural language, or a formatted intention expression model, such as the intention expression model defined by the intent driven management service (IDMS) of the Service and System Aspects (SA5) working group of the 3rd generation partnership project (3GPP) management standard.

[0146] The first piece of information can be included in an intention request message sent by device #A to NIAF. The intention request message is used to request to implement the intention described by the first piece of information. Optionally, the intention request message can also include other information, such as the SUPI, for NIAF or other entities in the system to determine the identity of device #A that sends the information.

[0147] Optionally, the intention request message can also carry attachments, including but not limited to pictures, texts, voices, videos, binary code files, application (APP) installation packages, etc., for expanding or supplementing the content of the intention description.

[0148] Optionally, there may be multiple interactions between the NIAF and Device #A to confirm the specific intention of Device #A. For example, the NIAF may request Device #A to supplement detailed information about the intention description, or the NIAF may also send the recognized intention to Device #A to confirm whether the recognition is correct, etc. The above attachments may also be provided during the multiple intention confirmation interactions. The indirect expression of the user's intention is to interact with a device in a subnet using the first device or to interact with a device in a subnet using other devices accessed through the first device. For example, "I want to view the family photos saved on the NAS at home"; "I want to use the PAD in the back seat to watch the movies saved on the NAS at home", etc. The user does not need to send explicit instructions through the first device to connect the first device to the home network.

[0149] S420, the NIAF determines the first subnet according to the intention of the first user.

[0150] This step includes two ways to determine the first subnet, which are described separately below.

[0151] Method 1: The NIAF determines the first subnet from at least one subnet according to the intention of the first user.

[0152] Or rather, the NIAF selects the first subnet from at least one subnet.

[0153] In the embodiments of the present application, the service types borne by different subnets may be different. For example, the service types can be divided into entertainment services and work services. For instance, Subnet A is used for work (i.e., the service type corresponding to Subnet A is work), and Subnet B is used for entertainment (i.e., the service type corresponding to Subnet B is entertainment). The network assigns different identifiers to subnets corresponding to different service types. For example, the network assigns identifier 1 to Subnet A and identifier 2 to Subnet B. It should be understood that the user needs to subscribe to the subnet service of the operator (such as the PIN service) before using the subnet. Specifically, the subnet identifier can be represented by DNN, S-NSSAI.

[0154] The NIAF determines the service type of the subnet that the first user requests to access according to the intention of the first user, and further determines the first subnet from at least one subnet according to the service type. For example, among at least one subnet, the NIAF takes the subnet with the same service type as the subnet that the first user requests to access as the first subnet. For example, there are 3 subnets, the service type corresponding to Subnet 1 is work, the service type corresponding to Subnet 2 is entertainment, and the service type corresponding to Subnet 3 is learning. And the intention of the first user is work, that is, the service type of the subnet that the first user requests to access is work, and further Subnet 1 is determined as the first subnet.

[0155] A possible scenario 1 is that at least one of the above subnets belongs to the subnets subscribed by the first user. Device #A sends the first user identifier associated with the first user to the NIAF. Then the NIAF can determine the subnets subscribed by the first user based on the first user identifier, and further determine at least one of the above subnets. That is, the NIAF determines at least one subnet based on the first user itself, and further determines the first subnet among these subnets.

[0156] Another possible scenario 2 is that at least one of the above subnets belongs to the subnets subscribed by the second user. Device #A sends the first user identifier associated with the first user to the NIAF. The relationship information between the first user and the second user is included in the intention of the first user. The NIAF determines the subnets subscribed by the second user based on the first user identifier and the relationship information to determine at least one of the above subnets. By way of example, the relationship information may be a kinship, such as the first user and the second user belonging to the same family. That is, the NIAF determines at least one subnet based on the second user associated with the first user, and further determines the first subnet among these subnets.

[0157] At least one of the above subnets may be the subnets subscribed by the first user or the second user, or may be a part of the subnets subscribed by the first user or the second user. The embodiments of the present application do not make any limitations in this regard.

[0158] Further, in scenario 2, there is a possible implementation where the NIAF determines to allow Device #A to access the first subnet based on the verification information of the second user. Or rather, the NIAF determines whether to allow Device #A to access the first subnet based on the verification information of the second user. For example, the NIAF can contact the digital human avatar of the second user or the second user himself (such as sending a confirmation text message) to confirm whether to allow the first user to access the first subnet.

[0159] The NIAF can also update the subscription information. By way of example, the NIAF can update the subscription information of the first subnet, such as including the identifier of the first user in the subscription information of the first subnet. Or, the NIAF can update the subscription information of the identifier of the first user, such as including the identifier of the first subnet in the subscription information of the identifier of the first user. In this way, the first user can successfully access the first subnet.

[0160] The identifier of the first subnet can be used to establish a first PDU session. By way of example, device #A establishes a first PDU session based on the identifier of the first subnet. Specifically, the DNN and S-NSSAI of the first PDU session are the identifier of the first subnet. If the first PDU session and the second PDU session are in different administrative domains, the NIAF can establish a communication tunnel between the second network element and the third network element. The second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session. Among them, device #B (an example of the second device) is a device belonging to the first subnet. In this way, device #A and device #B in different administrative domains can establish communication through the communication tunnel.

[0161] Method 2: The NIAF forms the first subnet according to the intention of the first user.

[0162] By way of example, the NIAF forms the first subnet by combining at least two devices according to the intention of the first user. The at least two devices include device #C (an example of the third device) and device #E (an example of the fourth device).

[0163] Optionally, device #A and device #C belong to the second subnet, and device #D (an example of the fifth device) and device #E belong to the third subnet. Among them, device #C accesses the communication network through device #A, and device #E accesses the communication network through device #D. That is, the NIAF forms a new subnet by combining devices in two different subnets according to the intention of the first user.

[0164] A possible implementation 1: The NIAF receives a second user identifier from device #A. The second user identifier is associated with the first user. The NIAF determines the subnets subscribed by the first user according to the second user identifier, such as the second subnet and the third subnet. That is, both the second subnet and the third subnet are subnets subscribed by the first user himself.

[0165] Another possible implementation 2: The NIAF receives a third user identifier from device #A and the identity information of the first user. The third user identifier is associated with the second user. The NIAF determines the second subnet subscribed by the second user according to the third user identifier, and determines the third subnet subscribed by the first user according to the identity information of the first user. That is, the second subnet and the third subnet are subnets subscribed by different users respectively.

[0166] In Implementation 2, NIAF can determine to allow Device #C to be networked with Device #E based on the verification information of the third user. Or rather, NIAF determines whether to allow Device #C to be networked with Device #E based on the verification information of the third user. For example, Device #C is a vehicle-mounted device and Device #E is a home device of the third user. NIAF contacts the digital human avatar of the third user or the third user himself / herself (such as sending a confirmation text message) to confirm whether to allow the first user to network the vehicle-mounted device with the home device of the third user. This vehicle-mounted device can be the vehicle-mounted device of the third user or the vehicle-mounted device of someone else, and there is no limitation on this.

[0167] Furthermore, NIAF can create the subscription information of the first subnet so that the subscription information of the first subnet includes the third user identifier and the fourth user identifier, and the fourth user identifier is associated with the first user. Or, NIAF updates the subscription information so that the subscription information of Device #A and Device #D includes the identifier of the first subnet, so that the first user can successfully access the newly formed first subnet.

[0168] The identifier of the first subnet can be used for Device #A to establish a third PDU session or for Device #D to establish a fourth PDU session. When the third PDU session and the fourth PDU session are in different administrative domains, NIAF can establish a communication tunnel between the fourth network element and the fifth network element. The fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session. In this way, Device #A and Device #D can establish communication through this communication tunnel.

[0169] S430, NIAF sends the second information to Device #A. Correspondingly, Device #A receives this second information.

[0170] The second information indicates the first subnet.

[0171] Corresponding to Method 1 in S420, the second information can include the identifier of the first subnet.

[0172] Corresponding to Method 2 in S420, the second information can include the identifier of the first subnet and the identifier of Device #C. That is, the second information includes the identifier of the first subnet and the identifier of the device joining this first subnet.

[0173] Optionally, NIAF can also send the third information to Device #D, and this third information includes the identifier of the first subnet and the identifier of Device #E.

[0174] In a possible implementation, NIAF can send information to Device #A or Device #D through other servers. For example, NIAF sends the second information to Device #A via the first application server, which is the application server registered for Device #A. NIAF sends the third information to Device #D via the second application server, which is the application server registered for Device #D.

[0175] S440, Device #A accesses the first subnet according to the second information.

[0176] For example, the second information is a DNN, S-NSSAI combination. Device #A establishes a PDU session corresponding to the (DNN, S-NSSAI) combination and accesses the 5G network. The 5G network connects Device #A to the first subnet. Device #A and Device #C can then communicate with other devices in the first subnet.

[0177] In this method, NIAF identifies the user's intention and determines whether the user requests to connect a terminal device to a subnet or requests to form a new subnet for devices in two subnets to achieve the user's intention. The network forms a network for the user based on the user's intention, reducing the difficulty of the user's device networking and improving the user experience.

[0178] The above describes the communication method provided in the embodiments of the present application. The following further illustrates the embodiment solutions of the present application in combination with specific implementation examples.

[0179] First, two communication architectures are introduced. One communication architecture is as shown in (a) of Figure 5 There are 2 subnets (Subnet#1, Subment#2) pre-configured in the user's home network. Subnet#1 is for work and includes terminal devices such as network attached storage 2 (NAS), printers, and laptops. Subnet#2 is for entertainment and includes terminal devices such as smart speakers, NAS1, and smart screens. User A (i.e., an example of the first user) requests to access the home network.

[0180] Another communication architecture is as shown in (b) of Figure 5 There is 1 subnet (Subnet#1) pre-configured in the user's home network and 1 subnet (Subnet#2) pre-configured in the vehicle network. User A requests to form a new subnet by combining the NAS and smart screen in Subnet#1 with the in-vehicle camera and in-vehicle Pad in Subnet#2.

[0181] A possible implementation 1: Xiao A sends an intention to the NIAF through the user interface of the mobile phone: I want to view the family photos saved on the home NAS. This intention indicates that Xiao A is a family member of this "home", and the family photos are saved in the subnet for entertainment. Xiao A's mobile phone and the home network are in the same management domain (that is, the PDU sessions established by PEGC1 accessing the 5G network and the PDU sessions established by the UE accessing the 5G network are managed by the same SMF or the same set of SMFs). In this implementation, the NIAF can, according to Xiao A's intention request, help Xiao A's UE access the corresponding subnet. Since the UE and the subnet are in the same management domain, the same SMF is responsible for managing the establishment of the PDU session for the UE and the PEGC of the subnet. It should be understood that this implementation is an example of Method 1 in S420. For specific details, reference can be made to the description in S420, which will not be elaborated here. This implementation is applicable to Figure 5 the communication architecture shown in (a) of

[0182] Specifically, reference can be made to Figure 6 , and this implementation includes the following steps:

[0183] S610, User M (an example of the first user or the second user) requests to establish PDU sessions corresponding to Subnet#1 and Subnet#2.

[0184] Subnet#1 and Subnet#2 are examples of at least one subnet. User M subscribes to the services of 2 subnets of the operator (such as PIN service). Subnet#1 is for work, and Subnet#2 is for entertainment. The network assigns the identifier (S-NSSAI1, DNN1) to Subnet#1 and the identifier (S-NSSAI2, DNN2) to Subnet#2. The user identifier of PEGC1 is SUPI1. After the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish PDU sessions corresponding to Subnet#1 and Subnet#2. Specifically, PEGC1 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI1, DNN1) and (S-NSSAI2, DNN2) respectively. The SMF selects the UPF according to (S-NSSAI1, DNN1) and (S-NSSAI2, DNN2).

[0185] S620, PEGC1 and the UPF establish a tunnel for Subnet#1.

[0186] S630, PEGC1 and the UPF establish a tunnel for Subnet#2.

[0187] S640, Add NAS1 to Subnet#2 subnet.

[0188] For example, after the NAS1 for saving the family portrait starts up, NAS1 is added to the Subnet#2 subnet according to the configuration of PEMC1.

[0189] At S650, the UE registers to the network.

[0190] Optionally, the UE can also establish a PDU session. This PDU session is used for the interaction between the UE and the NIAF.

[0191] At S660, Little A sends an intent request to the NIAF through the UE (PEGC2).

[0192] Among them, the user identifier of the UE is SUPI2. Little A and user M can be the same person or not. The UE can send the intent to the NIAF through the control plane message or the user plane. Specifically, the description in S410 can be referred to and will not be elaborated here. By way of example, Little A's intent is to view the family portrait.

[0193] At S670, the NIAF performs intent decision-making.

[0194] That is, the NIAF determines, according to Little A's intent request, that Little A requests to access the home network.

[0195] At S680, the NIAF identifies and authenticates the user based on the digital identity.

[0196] By way of example, the NIAF identifies and authenticates based on SUPI2 and the received images (such as obtained through the mobile phone camera) or sounds (such as obtained through the mobile phone microphone), as well as Little A's digital identity in the network.

[0197] At S690, the NIAF performs identity confirmation and determines to access Subnet#2.

[0198] In a possible way, if Little A and user M are the same person, when the identification and authentication are passed, the NIAF requests the subscription information of the subnet service subscribed by Little A from the UDM.

[0199] In another possible way, if Little A and user M are not the same person, the NIAF queries the digital human avatar of Little A in the network, determines Little A's family members (user M is among the family members), and subscribes from the UDM subnet according to the identity of family member M. That is, the relationship information between Little A and user M is a family relationship. The NIAF contacts the digital human avatar of user M or user M himself / herself (such as sending a confirmation text message) to confirm whether to allow Little A to access the home network.

[0200] After the NIAF obtains the subscription of the subnet from the UDM, since Little A's intent is to view the family portrait, the NIAF determines that Little A requests to access Subnet#2.

[0201] At S6100, the NIAF returns an intention response message to the UE.

[0202] This intention response message includes an indication to trigger the establishment of a PDU session, as well as the Subnet#2 identification (S-NSSAI2, DNN2).

[0203] At S6110, the NIAF updates the subscription in the UDM.

[0204] That is, the subscription information for the Subnet#2 subnet includes SUPI2 or the subscription information in SUP2 includes S-NSSAI2, DNN2.

[0205] At S6120, the UE sends a message requesting the establishment of a PDU session to the SMF. Correspondingly, the SMF receives this message requesting the establishment of a PDU session.

[0206] This message includes S-NSSAI2 and DNN2. The SMF can obtain the subscription information from the UDM, accept the UE's request, and select a UPF for the PDU session.

[0207] At S6130, the UE and the UPF establish a PDU session for Subnet#2.

[0208] At S6140, the SMF sends N4 rules to the UPF to configure local exchange.

[0209] The data packets of the UE and NAS1 will perform local exchange at the UPF.

[0210] At S6150, application layer interaction.

[0211] That is, Little A searches for NAS1 through the UE and views the family photo saved on NAS1.

[0212] A possible implementation 2: Little A sends an intention to the NIAF through the user interface of the mobile phone: I want to view the family photos saved on the NAS at my grandmother's house. My grandmother's house and Little A's UE are not in the same administrative domain. Little A's mobile phone and the grandmother's home network are not in the same administrative domain. (That is, the PDU sessions established by PEGC1 accessing the 5G network and the UE accessing the 5G network are managed by different SMFs or different sets of SMFs). In this implementation, the NIAF can, according to Little A's intention request, help Little A's UE access the subnet corresponding to the grandmother. It should be understood that this implementation is an example where the first PDU session and the second PDU session in Mode 1 of S420 are in different administrative domains. For specific details, reference can be made to the description in S420 and will not be elaborated here. This implementation is applicable to Figure 5 the communication architecture shown in (a) of

[0213] Specifically, reference can be made to Figure 7 , and the implementation includes the following steps:

[0214] S710, User M requests to establish PDU sessions corresponding to Subnet#1 and Subnet#2.

[0215] User M (the grandmother of Little A, i.e., an example of the second user) subscribes to the services of 2 subnets of the operator (such as PIN service). Subnet#1 is for work and Subnet#2 is for entertainment. The network assigns the identifier (S-NSSAI1, DNN1) to Subnet#1 and (S-NSSAI2, DNN2) to Subnet#2. The user identifier of PEGC1 is SUPI1. After the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish PDU sessions corresponding to Subnet#1 and Subnet#2. Specifically, PEGC1 sends a PDU session establishment request message to the network, carrying (S-NSSAI1, DNN1) and (S-NSSAI2, DNN2) respectively in the message. SMF1 selects UPF1 according to (S-NSSAI1, DNN1) and (S-NSSAI2, DNN2).

[0216] S720, PEGC1 and UPF establish a tunnel for Subnet#1.

[0217] S730, PEGC1 and UPF establish a tunnel for Subnet#2.

[0218] S740, Add NAS1 (i.e., an example of Device#B) to Subnet#2.

[0219] For example, after NAS1 that stores family photos of the user is started, according to the configuration of PEMC1, NAS1 is added to Subnet#2.

[0220] S750, The UE registers to the network.

[0221] Optionally, the UE can also establish a PDU session. This PDU session is used for the UE to interact with the NIAF.

[0222] S760, Little A sends an intention to the NIAF through the UE (PEGC2).

[0223] The user identifier of the UE is SUPI2. Little A and User M (grandmother) are not the same person. The UE can send an intention to the NIAF through the control plane message or through the user plane. Specifically, reference can be made to the description in S410, which will not be elaborated here. By way of example, Little A's intention is to view the family portrait.

[0224] S770, the NIAF executes the intention decision.

[0225] That is, the NIAF determines, according to the intention request of Little A, that Little A requests to access the grandmother's home subnet.

[0226] S780, the NIAF identifies and authenticates the user based on the digital identity.

[0227] For example, the NIAF identifies and authenticates based on the SUPI2, the received images (such as obtained through the mobile phone camera) or sounds (such as obtained through the mobile phone microphone), and the digital identity of Little A in the network.

[0228] S790, the NAIF executes the identity confirmation and determines to access Subnet#2.

[0229] In a possible way, if the identification and authentication are passed, the NIAF determines the identity of Little A's grandmother according to the digital avatar of Little A in the network, and

[0230] the NIAF contacts the digital avatar of Little A's grandmother or Little A's grandmother herself (such as sending a confirmation text message) to confirm whether to allow Little A to access the home network. If allowed, the subscription information of the grandmother's subnet is obtained from the UDM.

[0231] After the NIAF obtains the subscription of the subnet from the UDM, according to the intention of Little A, which is to view the family photo, the NIAF determines that the subnet requested by Little A to access is Subnet#2.

[0232] S7100, the NIAF returns an intention response message to the UE.

[0233] The message includes an indication to trigger the establishment of a PDU session and the Subnet#2 identifier (S-NSSAI2, DNN2)

[0234] S7110, the NIAF updates the subscription in the UDM.

[0235] That is, the subscription information of Subnet#2 includes SUPI2 or the subscription information in SUP2 includes S-NSSAI2, DNN2.

[0236] S7120, the UE sends a message requesting to establish a PDU session to the SMF2.

[0237] The message includes S-NSSAI2, DNN2. The SMF2 can obtain the subscription information from the UDM, accept the request of the UE, and select the UPF2 for the PDU session.

[0238] S7130, the UE and the UPF2 establish a PDU session for Subnet#2.

[0239] At S7140, NIAF sends N9 tunnel establishment requests to SMF1 and SMF2 respectively.

[0240] For example, NIAF interacts with SMF1 and SMF2 respectively to establish an N9 tunnel between UPF1 and UPF2. Packets of UE and NAS1 can be exchanged through the N9 tunnel between UPF1 and UPF2.

[0241] At S7150, an N9 tunnel is established between UPF1 and UPF2.

[0242] At S7160, application layer interaction occurs.

[0243] That is, Little A searches for NAS1 through UE and views the family portrait saved on NAS1.

[0244] A possible implementation 3: Little A sends intentions to NIAF through the in-vehicle terminal user interface: (1) Let family members watch the video captured by the in-vehicle camera on the smart screen; (2) Play movie #1 on the rear seat PAD from NAS. The in-vehicle terminal and the home network are in the same management domain. In this implementation, NIAF can, according to Little A's intention request, help the in-vehicle camera, PAD in the in-vehicle network, smart screen, and NAS in the home network to form the same subnet. Since the in-vehicle subnet and the home subnet are in the same management domain, the same SMF is responsible for managing the establishment of PDU sessions for PEGC in the in-vehicle subnet and PEGC in the home subnet. And the devices in the home network and the in-vehicle network are all registered with the application functions provided by the operator. It should be understood that this implementation is an example of Method 2 in S420. For specific details, reference can be made to the description in S420 and will not be elaborated here. This implementation applies to Figure 5 the communication architecture shown in (b) of

[0245] Specifically, reference can be made to Figure 8 This implementation includes the following steps:

[0246] At S810, establish a PDU session corresponding to Subnet#1.

[0247] Exemplarily, PEMC1 in the home network of User A registers PEGC1 and the home network devices to the AF. The AF requests the UDM to create Subnet#1 through the NEF. The identifier assigned by the UDM for Subnet#1 is (S-NSSAI1, DNN1). The user identifier of PEGC1 is SUPI1. PEMC1 configures PEGC1. After the gateway PEGC1 starts up, PEGC1 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#1. Specifically, PEGC1 sends a PDU session establishment request message to the network, carrying (S-NSSAI1, DNN1) respectively in the message. The SMF selects the UPF according to (S-NSSAI1, DNN1).

[0248] S820, Device 1 starts up and accesses PEGC1.

[0249] This Device 1 is a device in the home network of User A.

[0250] S830, Establish a PDU session corresponding to Subnet#2.

[0251] Exemplarily, PEMC2 in the vehicle network of User M registers PEGC2 and the vehicle network devices to the AF. The AF requests the UDM to create Subnet#2 through the NEF. The identifier assigned by the UDM for Subnet#2 is (S-NSSAI2, DNN2). The user identifier of PEGC2 is SUPI2. PEMC2 configures PEGC2. After the gateway PEGC2 starts up, PEGC2 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#2. Specifically, PEGC2 sends a PDU session establishment request message to the network, carrying (S-NSSAI2, DNN2) respectively in the message. The SMF selects the UPF according to (S-NSSAI2, DNN2).

[0252] S840, Device 2 starts up and accesses PEGC2.

[0253] This Device 2 is a device in the vehicle network.

[0254] S850, User A sends an intent request to the NIAF through the vehicle terminal (PEGC2).

[0255] User A and User M can be the same person (the car is purchased by User A), or they can be different people (the car is a friend's of User A, or rented by User A). PEGC2 can send the intent to the NIAF through the control plane message or through the user plane. Specifically, reference can be made to the description in S410 and will not be elaborated here.

[0256] S860, The NIAF executes intent decision-making.

[0257] That is, NIAF determines, according to the intention request of Little A, that Little A wants to network the devices in the vehicle network and the home network devices.

[0258] S870, NIAF identifies and authenticates the user based on the digital identity.

[0259] Exemplarily, NIAF identifies and authenticates based on SUPI2 and the received image (obtained through the mobile phone camera) or sound (obtained through the mobile phone microphone), as well as the digital identity of Little A in the network. Based on SUPI2 and the digital identity of Little A, NIAF can determine whether SUPI2 is the terminal device subscribed by Little A. If not, then NIAF can determine the subscribed user M according to SUPI2.

[0260] S880, NAIF performs identity confirmation and determines to form Subnet#3.

[0261] This Subnet#3 is an example of the first subnet in S420.

[0262] In a possible way, if Little A and user M are the same person, when the identification and authentication are passed, NIAF requests the subscription of the subnet service subscribed by Little A from the UDM. Then NIAF obtains the subscription description information in steps S810 and S830;

[0263] In another possible way, if Little A and user M are not the same person, NIAF contacts the digital human avatar of user M or user M himself (such as sending a confirmation text message) to confirm whether to allow Little A to network the vehicle network with other networks. Usually when Little A rents a vehicle from user M, user M updates his digital avatar for authorizing Little A to network. After NIAF obtains the subscriptions of the subnets of Little A and user M from the UDM, it interacts with the AF to obtain the devices in Subnet#1 and Subnet#2 subnets, and according to the intention of Little A, forms the vehicle-mounted camera, PAD in the vehicle network and the smart screen and NAS in the home network into the same subnet.

[0264] S890, NIAF sends a network formation policy provision message to PEGC1 / PEMC1.

[0265] This message includes the indication to form Subnet#3, as well as the identifier of Subnet3 (S-NSSAI3, DNN3) and the identifiers of the devices (i.e., device#C) (smart screen, NAS) added to Subnet3.

[0266] S8100, NIAF sends a network formation policy provision message to PEGC2 / PEMC2.

[0267] This message includes the instruction to form Subnet #3, as well as the identification of Subnet 3 (S-NSSAI3, DNN3) and the identification of the devices (i.e., device #E) (carrying a camera, PAD) added to Subnet 3.

[0268] S8110, NIAF updates the subscription in the UDM.

[0269] That is, add the subscription information for Subnet #3 subnet, which includes SUPI1, SUPI2, the identification of Subnet #3 (S-NSSAI3, DNN3), or the S-NSSAI3, DNN3 is included in the subscription information of SUPI1 and SUPI2.

[0270] S8120, PEGC1 sends a message to the SMF requesting to establish a PDU session.

[0271] This message includes S-NSSAI3, DNN3. The SMF obtains the subscription information from the UDM, accepts the request from PEGC1, and selects a UPF for the PDU session.

[0272] S8130, PEGC2 sends a message to the SMF requesting to establish a PDU session.

[0273] This message includes S-NSSAI3, DNN3. The SMF obtains the subscription information from the UDM, accepts the request from PEGC2, and selects a UPF for the PDU session.

[0274] S8140, the SMF sends N4 rules to the UPF to configure local exchange.

[0275] For example, data packets of smart screens, NAS, and devices carrying cameras and PADs will perform local exchange at the UPF.

[0276] S8150, application layer interaction.

[0277] Exemplarily, Little A searches for the NAS through the PAD and views the movies saved on the NAS. The smart screen searches for the in-vehicle camera and watches the captured images.

[0278] For the scenario where Little A's home network and in-vehicle network are not in the same management domain, the implementation process is similar to the above process. The difference is that in S8120 and S8130, the PDU sessions established by PEGC1 and PEGC2 will select different UPFs. At this time, NIAF will be responsible for establishing a tunnel between the two different UPFs for establishing communication.

[0279] A possible implementation 4. User A sends the following intents to NIAF through the in-vehicle terminal user interface: (1) allowing family members to view the images captured by the in-vehicle camera on the smart screen; (2) playing Movie #1 on the rear-seat PAD from the NAS. The in-vehicle terminal and the home network are in the same administrative domain. In this implementation, NIAF can, according to User A's intent requests, help the in-vehicle camera, PAD in the in-vehicle network, the smart screen, and NAS in the home network to form the same subnet. Since the in-vehicle subnet and the home subnet are in the same administrative domain, the same SMF or the same set of SMFs is responsible for managing the establishment of PDU sessions for the PEGC in the in-vehicle subnet and the PEGC in the home subnet. Also, the devices in the home network and the in-vehicle network are registered with an application server provided by a third party. This implementation is applicable to Figure 5 the communication architecture shown in (b) of

[0280] S910, establish the PDU session corresponding to Subnet#1.

[0281] Exemplarily, PEMC1 in User A's home network registers PEGC1 and the home network devices with the third-party AS1. AS1 requests the UDM to create Subnet#1 through the NEF. The identifier assigned by the UDM for Subnet#1 is (S-NSSAI1, DNN1). The user identifier of PEGC1 is SUPI1. PEMC1 configures PEGC1. After the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish the PDU session corresponding to Subnet#1. Specifically, PEGC1 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI1, DNN1) respectively. The SMF selects the UPF according to (S-NSSAI1, DNN1).

[0282] S920, Device 1 starts up and accesses PEGC1.

[0283] This Device 1 is a device in User A's home network.

[0284] S930, establish the PDU session corresponding to Subnet#2.

[0285] Exemplarily, PEMC2 in the in-vehicle network of user M registers PEGC2 and home network devices to the third-party AS2. AS2 requests UDM to create subnet Subnet#2 through NEF. The identifier assigned by UDM for Subnet#2 is (S-NSSAI2, DNN2). The user identifier of PEGC2 is SUPI2. PEMC2 configures PEGC2. After the gateway PEGC2 starts up, PEGC2 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#2. Specifically, PEGC2 sends a PDU session establishment request message to the network, carrying (S-NSSAI2, DNN2) respectively in the message. SMF selects UPF according to (S-NSSAI2, DNN2).

[0286] S940, Device 2 starts up and accesses PEGC2.

[0287] This Device 2 is a device in the in-vehicle network.

[0288] S950, Little A sends an intent request to NIAF through the in-vehicle terminal (PEGC2).

[0289] Little A and user M can be the same person (the car is bought by Little A), or they can be different people (the car belongs to Little A's friend or is rented by Little A). PEGC2 can send the intent to NIAF through control plane messages or through the user plane. Specifically, the description in S410 can be referred to and will not be elaborated here.

[0290] S960, NIAF executes intent decision-making.

[0291] That is, NIAF determines according to Little A's intent request that Little A wants to network the devices in the in-vehicle network and the devices in the home network.

[0292] S970, NIAF identifies and authenticates the user based on the digital identity.

[0293] Exemplarily, NIAF identifies and authenticates according to SUPI2 and the received image (obtained through the mobile phone camera) or sound (obtained through the mobile phone microphone), as well as Little A's digital identity in the network. According to SUPI2 and Little A's digital identity, NIAF can determine whether SUPI2 is the terminal device subscribed by Little A. If not, NIAF can determine the subscribed user M according to SUPI2.

[0294] S980, NAIF executes identity confirmation and determines to form Subnet#3.

[0295] This Subnet#3 is an example of the first subnet in S420.

[0296] A possible way is that if Little A and User M are the same person, when the identification and authentication are passed, NIAF requests the subscription of the subnet service subscribed by Little A from the UDM. NIAF obtains the subscription description information in steps S910 and S930;

[0297] Another possible way is that Little A and User M are not the same person. NIAF contacts the digital twin of User M or User M himself (such as sending a confirmation text message) to confirm whether Little A is allowed to network the in-vehicle network with other networks. If allowed, then NIAF requests the subscription of the subnet services of Little A and User M from the UDM. Usually, when Little A rents a vehicle from User M, User M updates his digital twin for authorizing Little A to network. After NIAF obtains the subnet subscription from the UDM, it interacts with the AF to obtain the devices in Subnet#1 and Subnet#2 subnets, and according to Little A's intention, forms the in-vehicle camera, PAD of the in-vehicle network and the smart screen and NAS in the home network into the same subnet.

[0298] S990, NIAF requests the information of Subnet#1 from AS1 (an example of the first application server).

[0299] The information of Subnet#1 includes PEGC1 (SUP1) (an example of Device #A), PEMC1 and other devices in this subnet.

[0300] S9100, NIAF requests the information of Subnet#2 from AS2 (an example of the second application server),.

[0301] The information of Subnet#2 includes PEGC2 (SUP2) (an example of Device #D), PEMC2 and other devices in this subnet.

[0302] S9110, NIAF sends a network formation policy provision message to PEMC1 / PEGC1 via AS1.

[0303] This message includes the indication to form Subnet#3, as well as the identifier of Subnet3 (S-NSSAI3, DNN3) and the identifiers of the devices (i.e., Device #C) (smart screen, NAS) to be added to Subnet3. AS1 further sends this network formation policy provision message to PEMC1 / PEGC1.

[0304] S9120, NIAF sends a network formation policy provision message to PEMC2 / PEGC2 via AS2.

[0305] This message includes instructions for forming Subnet#3, as well as the identification of Subnet3 (S-NSSAI3, DNN3) and the identification of the devices added to Subnet3 (i.e., Device#E) (carrying cameras, PAD). AS1 further sends a network configuration policy provisioning message to PEMC2 / PEGC2.

[0306] S9130, NIAF updates the subscription in the UDM.

[0307] That is, add the subscription information for Subnet#3 subnet, which includes SUPI1, SUPI2, the identification of Subnet#3 (S-NSSAI3, DNN3), or the S-NSSAI3, DNN3 is included in the subscription information of SUPI1, SUPI2.

[0308] S9140, PEGC1 sends a message to the SMF requesting to establish a PDU session.

[0309] This message includes S-NSSAI3, DNN3. The SMF obtains the subscription information from the UDM, accepts the request from PEGC1, and selects a UPF for the PDU session.

[0310] S9150, PEGC2 sends a message to the SMF requesting to establish a PDU session.

[0311] This message includes S-NSSAI3, DNN3. The SMF obtains the subscription information from the UDM, accepts the request from PEGC2, and selects a UPF for the PDU session.

[0312] S9160, the SMF sends N4 rules to the UPF to configure local exchange.

[0313] For example, data packets of smart screens, NAS, and devices carrying cameras and PADs will perform local exchange at the UPF.

[0314] S9170, application layer interaction.

[0315] Exemplarily, Little A searches for the NAS through the PAD and views the movies saved on the NAS. The smart screen searches for the in-vehicle camera and views the captured images.

[0316] For the scenario where Little A's home network and in-vehicle network are not in the same management domain, the implementation process is similar to the above process. The difference is that in S9140 and S9150, the PDU sessions established by PEGC1 and PEGC2 will select different UPFs. At this time, NIAF will be responsible for establishing a tunnel between the two different UPFs for establishing communication.

[0317] Finally, the device embodiments of this application are introduced.

[0318] To implement the various functions in the method provided by this application, each communication device, such as a network element or a terminal device, may include a hardware structure and / or a software module, and implement the above-mentioned various functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether a certain function among the above-mentioned various functions is executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraints of the technical solution.

[0319] Figure 10 It is a schematic block diagram of the communication device 1000 according to an embodiment of this application. The communication device 1000 includes a processor 1010 and a communication interface 1020, and the processor 1010 and the communication interface 1020 can be connected to each other through a bus 1030. The communication device 1000 can be at least one of the foregoing various network elements, such as it can be a NIAF.

[0320] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a compact disc read-only memory (CD-ROM). The memory 1040 is used to store relevant instructions and data.

[0321] The processor 1010 can be one or more central processing units (CPUs). When the processor 1010 is a single CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0322] When the communication device 1000 is a NIAF network element, exemplarily, the communication device 1000 is used to perform the following operations: select a first subnet, or form a first subnet, etc.

[0323] When the communication device 1000 is an SMF network element, exemplarily, the communication device 1000 is used to perform the following operations: establish a PDU session, etc.

[0324] When the communication device 1000 is a UPF network element, exemplarily, the communication device 1000 is used to perform the following operations: process subscription information, etc.

[0325] When the communication device 1000 is a terminal device, such as a first device, exemplarily, the communication device 1000 is used to perform the following operations: send a first message; receive a second message; access a first subnet, etc.

[0326] The above content is only for exemplary description. When the communication device 1000 is at least one of the foregoing network elements, it will be responsible for executing at least one of the methods or steps related to each network element in the foregoing method embodiments.

[0327] The above description is only for exemplary description. For specific content, reference may be made to the content shown in the foregoing method embodiments. Figure 10 The implementation of each operation in may also be correspondingly referred to Figures 4 to 9 the corresponding description of the method embodiment shown.

[0328] Figure 11 FIG. is a schematic block diagram of the communication device 1100 according to an embodiment of the present application. The communication device 1100 may be at least one of the foregoing communication devices, or may be a chip or module in each communication device, and is used to implement the method involved in the foregoing embodiments. The communication device 1100 includes a transceiver unit 1110 and a processing unit 1120. The transceiver unit 1110 and the processing unit 1120 will be introduced exemplarily below.

[0329] The transceiver unit 1110 may include a sending unit and a receiving unit. The sending unit is used to perform the sending action of the communication device 1100, and the receiving unit is used to perform the receiving action of the communication device 1100. For the convenience of description, in the embodiments of the present application, the sending unit and the receiving unit are combined into one transceiver unit. A unified description is made here and will not be repeated hereinafter.

[0330] When the communication device 1100 is a NIAF, exemplarily, the transceiver unit 1110 is used to receive first information from a first device, and the processing unit 1120 is used to determine a first subnet in at least one subnet according to the intention of a first user, or to form a first subnet according to the intention of the first user.

[0331] When the communication device 1100 is a terminal device, such as a first device, exemplarily, the transceiver unit 1110 is used to receive second information.

[0332] The above content is only for exemplary description. When the communication device 1100 is at least one of the foregoing communication devices, it will be responsible for executing at least one of the methods or steps related to each communication device in the foregoing method embodiments.

[0333] Optionally, the communication device 1100 further includes a storage unit 1130, and the storage unit 1130 is used to store a program or code for executing the foregoing method.

[0334] Figure 10 and Figure 11 The device embodiment shown is used to implement Figures 4 to 9 the content described. Figure 10 andFigure 11 The specific implementation steps and methods of the device shown can refer to the content described in the foregoing method embodiments.

[0335] Figure 12 FIG. 5 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 is used to implement the functions of at least one of the foregoing communication devices. The communication device 1200 may be a chip in at least one of the foregoing communication devices.

[0336] The communication device 1200 includes: an input / output interface 1220 and a processor 1210. The input / output interface 1220 may be an input / output circuit. The processor 1210 may be a signal processor, a chip, or other integrated circuits that can implement the method of the present application. Among them, the input / output interface 1220 is used for input or output of signals or data.

[0337] For example, when the communication device 1200 is a first network element, the input / output interface 1220 is used to receive first information from a terminal device, and the processor 1210 is used to determine a first subnet in at least one subnet according to the intention of a first user, or to form a first subnet according to the intention of the first user.

[0338] In a possible implementation, the processor 1210 realizes the functions implemented by at least one of the foregoing first network element, second network element, third network element, or fourth network element by executing instructions stored in a memory.

[0339] Optionally, the communication device 1200 further includes a memory.

[0340] Optionally, the processor and the memory are integrated together.

[0341] Optionally, the memory is outside the communication device 1200.

[0342] In a possible implementation, the processor 1210 may be a logic circuit, and the processor 1210 inputs / outputs messages or signaling through the input / output interface 1220. The logic circuit may be a signal processor, a chip, or other integrated circuits that can implement the method of the embodiments of the present application.

[0343] The above description of the communication device 1200 is only an exemplary description. The communication device 1200 can be used to execute the method described in the foregoing embodiments. The specific content can refer to the description of the foregoing method embodiments and will not be repeated here.

[0344] It should also be understood that the above communication device is equally applicable to various devices, such as a first device, a second device, a third device, a fourth device, an Xth device, and an application server, etc.

[0345] The present application also provides a chip, including a processor configured to call and run instructions stored in a memory, such that a communication device installed with the chip executes the methods in the above respective examples.

[0346] The present application also provides a chip, including: an input interface, an output interface, and a processor. The input interface, the output interface, and the processor are connected through an internal connection path. The processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above respective examples. Optionally, the chip further includes a memory configured to store a computer program or code.

[0347] The present application also provides a processor configured to be coupled with a memory and execute the methods and functions related to at least one of the foregoing communication devices in any one of the above embodiments.

[0348] The present application provides a computer program product containing instructions. When the computer program product runs on a computer, the methods of the foregoing embodiments are implemented.

[0349] The present application also provides a computer program. When the computer program runs on a computer, the methods of the foregoing embodiments are implemented.

[0350] The present application also provides a computer-readable storage medium storing a computer program, and the computer program, when executed by a computer, implements the method described in the foregoing embodiments.

[0351] Those of ordinary skill in the art can realize that the units and algorithm steps of the respective examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0352] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0353] In several embodiments provided in the present application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be in electrical, mechanical, or other forms.

[0354] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the technical solutions of the embodiments of the present application.

[0355] In addition, each functional unit in various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0356] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the embodiments of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of each method embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0357] As described above, the above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claimed rights.

Claims

1. A communication method, characterized in that, Applied to the Network Intelligent Agent Function Network Element (NIAF), the method includes: Receiving first information, which is used to describe the intention of a first user; Determining a first subnet according to the intention of the first user, where the first subnet is determined from at least one subnet, or the first subnet is formed by the NIAF; Sending second information, which indicates the first subnet.

2. The method according to claim 1, wherein When the first subnet is determined from at least one subnet, the determining the first subnet according to the intention of the first user includes: Determining the service type of the subnet to which the first user requests access according to the intention of the first user, and the first subnet is the subnet among the at least one subnet that has the same service type as the subnet to which the first user requests access.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receiving a first user identifier, which is associated with the first user; Determining the at least one subnet according to the first user identifier, and the at least one subnet belongs to the subnets subscribed by the first user.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Receiving a first user identifier, which is associated with the first user; Determining the at least one subnet according to the first user identifier and the relationship information between the first user and a second user, and the at least one subnet belongs to the subnets subscribed by the second user, and the relationship information between the first user and the second user is included in the intention of the first user.

5. The method according to claim 4, characterized in that The method further includes: Determining to allow a first device to access the first subnet according to the verification information of the second user, where the first device is the device that sends the intention of the first user.

6. According to the method of any one of claims 2 to 5, the second information includes the identifier of the first subnet.

7. According to the method of claim 6, the identifier of the first subnet is used for the first device to establish a first Protocol Data Unit (PDU) session, where the first device is the device that sends the intention of the first user.

8. The method according to claim 7, characterized in that, If the first PDU session and the second PDU session established with a second device in the first subnet are in different administrative domains, the method further includes: Establishing a communication tunnel between a second network element and a third network element, where the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

9. The method according to claim 1, characterized in that When the first subnet is formed by the NIAF, the method includes: Forming the first subnet by combining at least two devices according to the intention of the first user, where the at least two devices include a third device and a fourth device, and the third device belongs to a second subnet, and the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

10. The method according to claim 9, wherein The method further includes: Receiving a second user identifier, which is associated with the first user; Determining the second subnet and the third subnet subscribed by the first user according to the second user identifier.

11. The method according to claim 9, wherein The method further includes: Receiving a third user identifier and the identity information of the first user, where the third user identifier is associated with a second user; Determining the second subnet subscribed by the second user according to the third user identifier; Determine the third subnet subscribed by the first user according to the identity information of the first user.

12. The method according to claim 11, wherein The method further includes: Determine that the third device is allowed to form a network with the fourth device according to the authentication information of the third user.

13. The method according to any one of claims 9 to 12, characterized in that, The second information includes the identifier of the first subnet and the identifier of the third device. The identifier of the first subnet is used for the first device to establish a third PDU session, and the third device accesses the communication network through the first device. The method further includes: Send third information to a fifth device. The third information includes the identifier of the first subnet and the identifier of the fourth device. The identifier of the first subnet is used for the fifth device to establish a fourth PDU session, and the fourth device accesses the communication network through the fifth device.

14. A communication method, characterized in that, Applied to a first device, the method includes: Send first information, which is used to describe the intention of the first user; Receive second information, which indicates the first subnet. The first subnet is determined according to the intention of the first user, the first subnet is determined from at least one subnet, or the first subnet is formed by NIAF; Access the first subnet according to the second information.

15. The method according to claim 14, wherein The first subnet is determined from at least one subnet. The first subnet is the subnet among the at least one subnet that has the same service type as the subnet requested by the first user to access. The service type of the subnet requested by the first user to access is determined according to the intention of the first user.

16. The method according to claim 14 or 15, characterized in that, The method further includes: Send a first user identifier, which is associated with the first user and is used to determine the at least one subnet that belongs to the subnets subscribed by the first user.

17. The method according to claim 14 or 15, characterized in that, The method further includes: Send a first user identifier, which is associated with the first user. The first user identifier and the relationship information between the first user and the second user are used to determine the at least one subnet that belongs to the subnets subscribed by the second user. The relationship information between the first user and the second user is included in the intention of the first user.

18. The method according to claim 17, wherein The first device is allowed to access the first subnet is determined according to the authentication information of the second user.

19. The method according to any one of claims 14 to 18, wherein the second information includes the identifier of the first subnet.

20. The method according to claim 19, characterized in that, The method further includes: Establish a first PDU session according to the identifier of the first subnet.

21. The method according to claim 20, wherein If the first PDU session and the second PDU session established with a second device in the first subnet are in different administrative domains, the method further includes: Establish a communication tunnel between a second network element and a third network element. The second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

22. The method according to claim 14, characterized in that, The first subnet is formed by the NIAF and is composed of at least two devices according to the intention of the first user. The at least two devices include a third device and a fourth device, where the third device belongs to a second subnet and the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

23. The method according to claim 22, characterized in that, The method further includes: Sending a second user identifier associated with the first user, where the third user identifier is used to determine the second subnet and the third subnet subscribed to by the first user.

24. The method according to claim 22, wherein The method further includes: Sending a third user identifier and the identity information of the first user, where the third user identifier is associated with a second user, the third user identifier is used to determine the second subnet subscribed to by the second user, and the identity information of the first user is used to determine the third subnet subscribed to by the first user.

25. The method according to claim 24, wherein The permission for the third device and the fourth device to form a network is determined according to the verification information of the second user.

26. The method according to any one of claims 22 to 25, characterized in that, The second information includes the identifier of the first subnet and the identifier of the third device. The identifier of the first subnet is used to establish a third PDU session, and the third device accesses the communication network through the first device.

27. The method according to claim 26, characterized in that, The method further includes: Establishing a third PDU session according to the identifier of the first subnet.

28. A communication device, characterized in that, Including a unit for performing the method according to any one of claims 1 to 13 or claims 14 to 27.

29. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 13; or, the computer is caused to execute the method according to any one of claims 14 to 27.

30. A communication system, characterized in that, Including a communication device for performing the method according to any one of claims 1 to 13; and, a communication device for performing the method according to any one of claims 14 to 27.

Images