Communication method, and apparatus

Abstract

Disclosed in the present application are a communication method, and an apparatus. The method comprises: a second device acquires from a first device a first message for requesting to establish or modify a PDU session of the first device; the second device sends to a first network element a second message for requesting to modify or establish a PDU session corresponding to a first device identifier, the first device identifier corresponding to the first device, and the first device identifier and QoS parameters corresponding thereto being present in subscription information of the second device; the first network element indicates to the second device that the establishment or modification of the PDU session corresponding to the first device identifier is completed, the PDU session satisfying the aforementioned QoS parameters; and the second device indicates to the first device that the establishment or modification of the PDU session corresponding to the first device is completed. The method of the embodiments of the present application allows a network side to provide the corresponding QoS guarantee for the first device accessing the network by means of the subscription information of the second device.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410406897.1 and invention name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0003] Current mobile networks provide services based on the subscription information of network devices, which ensures that operators can effectively control user access to the network. From a business scenario perspective, for services such as voice calls and short message service (SMS), a user only needs one mobile phone and one set of subscription information. However, with the development of the times, a person may have different types of devices (such as personal phones, tablets, laptops, etc.), which may be connected to network devices, such as terminal devices, through non-3GPP connections such as Bluetooth and WiFi, and then access the network through the terminal devices. In a home network, there may be multiple devices, such as multiple computers, accessing the network through a unified network device, such as a 5G residential gateway (RG). The connection between the network and a UE or 5G-RG will be used by multiple devices with different network setting requirements.

[0004] In current network architectures, to provide differentiated quality of service (QoS) guarantees for each device accessing the network through a network device, the device accesses the network based on its own subscription information, and the network provides corresponding network services based on the device's subscription information. However, for multiple devices accessing the network using the same subscription, the network cannot provide differentiated QoS guarantees for these different devices. Summary of the Invention

[0005] The embodiments of the present application provide a communication method and apparatus, which enable the network side to provide corresponding QoS guarantees for a first device that accesses the network through the subscription information of a second device.

[0006] In the first aspect, the present application provides a communication method, which includes: a second device obtains a first message from a first device, the first message being used to request establishment or modification of a protocol data unit (PDU) session of the first device; the second device sends a second message to the first network element based on the first message, the second message including a first device identifier, and the second message being used to request modification or establishment of a protocol data unit (PDU) session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, the first device identifier exists in the contract information of the second device, the contract information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine the quality of service (QoS) parameters of the PDU session; the second device receives a first feedback message from the first network element, the first feedback message indicating completion of establishment or modification of the PDU session corresponding to the first device identifier, and the PDU session meets the QoS parameters; the second device sends a second feedback message to the first device based on the first feedback message, the second feedback message indicating completion of establishment or modification of the PDU session corresponding to the first device.

[0007] From a technical perspective, this embodiment adds a device identifier and a corresponding device profile to the second device's contract information, and assigns a first device identifier to the first device accessing the network through the second device. This allows the network to determine QoS parameters based on the device profile corresponding to the first device identifier and establish a PDU session for the first device that meets the QoS parameters. This enables the network to provide differentiated QoS guarantees for multiple devices accessing the network through a single device.

[0008] In a feasible implementation manner, the first message includes the first device identifier.

[0009] In a feasible implementation, the first message includes device-related information of the first device, and the device-related information of the first device is used to uniquely identify the first device; before the second device sends a second message to the first network element based on the first message, the method also includes: the second device determines the first device identifier based on the device-related information of the first device, wherein the second device stores one or more correspondences between device identifiers and device-related information, including the correspondence between the first device identifier and the device-related information of the first device.

[0010] From a technical perspective, when a first device requests to establish a PDU session with the first device via a first message, carrying the first device identifier in the first message allows the second device to quickly identify and send the second message, improving communication efficiency. Carrying the first device's device-related information in the first message allows the second device to determine the first device identifier based on the first device's device-related information, thereby improving the reliability of the communication process.

[0011] In a feasible implementation, before the second device obtains the first message from the first device, the method further includes: after the first device establishes a connection with the second device, the second device sends the first device identifier to the first device.

[0012] In a feasible implementation, before the second device obtains the first message from the first device, the method further includes: the second device receiving and storing one or more device identifiers from the first network element; and the second device assigning a first device identifier among the one or more device identifiers to the first device.

[0013] From a technical perspective, the first network element sends one or more device identifiers to the second device at one time, and the second device assigns the first device identifier to the first device based on the access of the first device. This can improve the flexibility of the device identifier allocation process and thus improve communication efficiency.

[0014] In a feasible embodiment, before the second device obtains the first message from the first device, the method also includes: the second device sends a first request message to the first network element, the first request message is used to request that a device identifier be assigned to the first device; the second device receives a first response message, the first response message includes the first device identifier; the second device determines to assign the first device identifier to the first device based on the first response message.

[0015] From a technical perspective, the second device requests the first network element to obtain the first device identifier corresponding to the first device based on each access to the first device. This allows the first network element, in combination with the third network element that stores the device identifier, to individually allocate a device identifier for each device based on the stored device identifier allocation situation, thereby improving the reliability of the device identifier allocation process.

[0016] In the second aspect, the present application provides a communication method, which includes: a first network element receives a second message sent by a second device, the second message includes a first device identifier, and the second message is used to request modification or establishment of a protocol data unit PDU session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, and the first device identifier exists in the contract information of the second device, and the contract information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine the quality of service QoS parameters of the PDU session; the first network element sends a third request message to the second network element, requesting to establish an SM context for the PDU session corresponding to the first device identifier; the first network element receives a third feedback message from the second network element, and the third feedback message indicates that the establishment of the SM context is completed; the first network element sends a first feedback message to the second device, and the first feedback message indicates that the establishment or modification of the PDU session corresponding to the first device identifier is completed, and the PDU session meets the QoS parameters determined by the device profile corresponding to the first device identifier.

[0017] In a feasible embodiment, before the first network element receives the second message sent by the second device, the method also includes: the first network element receives a first request message from the second device, the first request message is used to request that a device identifier be assigned to the first device; the first network element sends a first response message to the second device, the first response message including the first device identifier.

[0018] In a feasible implementation, before the first network element sends the first response message to the second device, the method further includes: the first network element queries the contract information of the second device from the third network element, and allocates a first device identifier to the first device according to the contract information of the second device.

[0019] In a feasible embodiment, after the first network element assigns a first device identifier to the first device based on the contract information of the second device, the method also includes: the first network element sends an indication message to the third network element, and the indication message instructs the third network element to update the stored contract information of the second device based on the first device identifier assigned to the first device.

[0020] From a technical perspective, after receiving the second message from the second device, the first network element can query the third network element for the device identifier included in the second device's contract information and assign a first device identifier to the first device based on the device identifier assignment status. This process, in which the first network element assigns the device identifier, adheres to existing network element operating principles and reduces the execution complexity of the device identifier assignment process.

[0021] In a feasible implementation, before the first network element sends a first response message to the second device, the method further includes: the first network element sends a second request message to the second network element based on the first request message, the second request message is used to request that a device identifier be assigned to the first device, and the second network element stores the contract information of the second device; the first network element receives a second response message from the second network element, and the second response message includes the first device identifier.

[0022] From a technical perspective, after receiving the second message from the second device, the first network element can request the third network element identified by the storage device to assign the first device identifier to the first device based on the device identifier allocation status. This process can reduce the number of interactions between network elements and thereby improve the efficiency of device identifier allocation.

[0023] In a feasible implementation manner, the subscription information of the second device includes one or more device identifiers and whether the one or more device identifiers are allocated to the device.

[0024] In a feasible implementation, before the first network element receives the second message sent by the second device, the method further includes: the first network element receives one or more device identifiers included in the contract information of the second device from the third network element, the one or more device identifiers including the first device identifier.

[0025] In a third aspect, the present application provides a communication method, which includes: a first device sends a first message to a second device, the first message being used to request establishment or modification of a protocol data unit (PDU) session of the first device, the first message including a first device identifier, the first device identifier being present in the contract information of the second device, the contract information also including a device profile corresponding to the first device identifier, the device profile being used to determine quality of service (QoS) parameters; the first device receives a second feedback message indicating completion of establishment or modification of the PDU session corresponding to the first device.

[0026] In a feasible implementation, after the first device establishes a connection with the second device, the first device receives the first device identification from the second device.

[0027] In a fourth aspect, a communication device is provided, which includes a unit or module for executing a possible method in any of the first aspect, the second aspect or the third aspect.

[0028] In a fifth aspect, an embodiment of the present application provides a communication device, which includes at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that any method that may be implemented in any of the above-mentioned first to third aspects is executed.

[0029] In a sixth aspect, an embodiment of the present application provides a communication system, comprising a first device, a second device, and a first network element, wherein the second device is configured to execute any of the methods described in the first aspect, the first network element is configured to execute any of the methods described in the second aspect, and the first device is configured to execute any of the methods described in the third aspect. Where possible, the communication system further includes the second network element described in the first aspect, and the third network element described in the second aspect, etc., configured to execute the related methods described in the first and second aspects.

[0030] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, which, when executed, enable the computer to execute a method as described in any of the above methods.

[0031] In an eighth aspect, an embodiment of the present application provides a computer program product, which includes: a computer program code, and when the computer program code is executed by a computer, the computer executes a method as described in any of the above methods.

[0032] In a ninth aspect, an embodiment of the present application provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory so that the device where the chip is located implements the method described in any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The following is an introduction to the drawings used in the embodiments of this application.

[0034] FIG1 is a schematic diagram of a scenario in which multiple devices access a network through a single network device, as provided in an embodiment of the present application.

[0035] FIG2A is a network architecture in which a device accesses a network through a terminal device, provided in an embodiment of the present application.

[0036] FIG2B is a network architecture in which a device accesses a network through a 5G-RG according to an embodiment of the present application.

[0037] FIG3A is a flowchart of a PDU session establishment provided in an embodiment of the present application.

[0038] FIG3B is a flowchart of a URSP workflow provided in an embodiment of the present application.

[0039] FIG4A is a flowchart of a communication method provided in an embodiment of the present application.

[0040] FIG4B is a schematic diagram of a PDU session establishment scenario provided in an embodiment of the present application.

[0041] FIG5 is a flowchart of a first device identification allocation provided in an embodiment of the present application.

[0042] FIG6 is another flowchart of allocating a first device identifier provided in an embodiment of the present application.

[0043] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0044] FIG8 is a schematic structural diagram of a simplified AN device provided in an embodiment of the present application.

[0045] FIG9 is a schematic structural diagram of a simplified UE provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be one or more. In addition, to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish between network elements and identical or similar items with substantially the same functions. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and terms such as "first" and "second" do not necessarily limit differences.

[0047] References to "one embodiment" or "some embodiments" in the embodiments of the present application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0048] The following specific implementation methods further describe in detail the objectives, technical solutions and beneficial effects of the present application. It should be understood that the following are only specific implementation methods of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

[0049] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0050] The following describes the scenarios involved in the embodiments of this application.

[0051] Please refer to Figure 1, which is a schematic diagram of a scenario in which multiple devices access the network through a single network device provided by an embodiment of the present application. As shown in Figure 1, multiple different devices access the mobile network based on the network device. The network device refers to a device that can sign a contract to access the mobile network, and can be a terminal device or 5G-RG, etc., and Figure 1 takes the terminal device as an example. Multiple devices refer to devices that access the network through the network device. Specifically, it can be a 3rd Generation Partnership Project (3GPP) device or a non-3GPP (N3GPP) device. The 3GPP device refers to a device that supports accessing the network using wireless communication standards and technologies established by 3GPP. The N3GPP device refers to a device that supports accessing the network using wireless communication standards and technologies specified by non-3GPP, such as a device that accesses the network through Bluetooth or WiFi. The specific implementation scenario is not limited in this application. Here, as an example, in one possible scenario, a non-3GPP device accesses the network through the UE's hotspot. At this time, a human user applies to connect to the UE through the user interface (UI) of the non-3GPP device. In another possible scenario, a family's non-3GPP devices, such as VR / XR, network-attached storage, and other devices, access the 5G-RG gateway via Wi-Fi, Bluetooth, or wired connections. Figure 1 takes tablet computers, personal phones, and laptops as examples, and network devices as terminal devices as examples. The terminal device accesses the core network (CN) through the access network (AN) to achieve contracted communication. The above-mentioned mobile network can be built based on various communication systems, such as long-term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), fifth-generation (5G) mobile communication system or new radio (NR) system, sixth-generation (6G) mobile communication system, or communication systems applied to the future or other similar communication systems. Unless otherwise specified, the mobile network built by the 5G mobile communication system will be described below as an example.

[0052] To facilitate understanding of the embodiments of the present application, Figures 2A-2B show the network architectures of two 5G communication systems for building a mobile network.

[0053] Figure 2A shows a network architecture for a device accessing a network through a terminal device according to an embodiment of the present application. The network architecture may include: a terminal device portion, an AN portion, a CN portion, and a device accessing the CN through the terminal device. The terminal device (terminal device), which may also be referred to as user equipment (UE) or terminal, is represented by UE in the figure. Optionally, the network architecture may also include a data network (DN) portion and / or an application network element portion. The terminal device accesses the CN through the access network, and the CN communicates with the DN or application network element.

[0054] A UE is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as ships); or in the air (such as airplanes, balloons, and satellites). UE may include, but is not limited to, user equipment, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal device, mobile terminal device, user terminal device, wireless communication device, user agent, user device, cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device, processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in the Internet of Things, home appliance, virtual reality device, terminal device in future 5G network, or terminal device in future evolved PLMN, etc.

[0055] The AN includes AN equipment. This AN equipment connects terminal devices to the wireless network in a mobile communication system. AN equipment, as a node in the radio access network, can also be referred to as an access network element, base station, radio access network (RAN) node (or device, or network element), access point (AP), network equipment, or small tower. The RAN devices in the embodiments of the present application include, but are not limited to, next-generation base stations (g nodeB, gNB) in 5G, evolved nodeB (eNB), radio network controller (RNC), nodeB (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved nodeB, or home nodeB, HNB), baseband unit (BBU), wireless fidelity (WiFi) access point, world interoperability for microwave access (WiMAX) base station, transmitting and receiving point (TRP), transmitting point (TP), or mobile switching center, etc. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in 5G communication systems, they are called RAN or gNB (5G NodeB); in LTE systems, they are called evolved NodeB (eNB or eNodeB); in third generation (3G) communication systems, they are called Node B, etc. In some deployments of AN devices, AN devices may include centralized units (CU) and distributed units (DU), etc. In other deployments of AN devices, CU can also be divided into CU-control plane (CP) and CU-user plane (UP), etc. In still other deployments of AN devices, AN devices can also be antenna units (radio units, RO). In still other deployments of AN devices, AN devices can be open radio access network (ORAN) architecture, etc.For example, when the AN device is an ORAN architecture, the AN device in the embodiment of the present application may be an access network element in the ORAN, or a module of the access network element. In the ORAN system, CU may also be referred to as open (O)-CU, DU may also be referred to as O-DU, CU-CP may also be referred to as O-CU-CP, CU-UP may also be referred to as O-CU-UP, and RU may also be referred to as O-RU.

[0056] DN is a network located outside the mobile communication system and can provide services to users. For example, the DN can be a packet data network (PDN), such as the Internet, Internet protocol multimedia service (IMS) network, certain application-specific data networks, Ethernet, Internet protocol (IP) local network, etc., and the embodiments of the present application are not limited to this. A variety of services can be deployed on the DN, which can provide data and / or voice services to terminal devices. There can be multiple application servers (AS) in the DN, and each AS can provide at least one service.

[0057] The application network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side. In the 5G communication system, the application network element can be an application function (AF) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names, which are not limited in the embodiments of this application.

[0058] The network elements in the core network can be divided into two categories: user plane function network elements (also referred to as user plane network elements) and control plane function network elements (also referred to as control plane network elements). The control plane function network elements include access management network elements, network open network elements, session management network elements, data management network elements, policy control network elements, and network slices and standalone non-public networks (SNPN) in 5G communication systems. The authentication and authorization function (NSSAAF) network element is a network slice-specific and SNPN Authentication and Authorization Function in 5G communication systems.

[0059] The user plane network element is responsible for forwarding and receiving user data in the terminal device. It can receive user data from the data network and transmit it to the terminal device through the access network device; the user plane network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the user plane network element are managed and controlled by the SMF network element. In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names, which are not limited in the embodiments of this application.

[0060] The access management network element is a control plane network element provided by the operator network, which is responsible for access control and mobility management of terminal devices accessing the operator network, such as mobile state management, allocation of user temporary identity, authentication and user functions. In the 5G communication system, the access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names, which are not limited in the embodiments of this application.

[0061] The network open network element is mainly responsible for supporting the secure interaction between the 3GPP network and third-party applications. It can safely expose network capabilities and events to third parties to enhance or improve the quality of application services. It can also ensure that the 3GPP network securely obtains relevant data from third parties to enhance the network's intelligent decision-making. At the same time, the network element supports recovering structured data from a unified database or storing structured data in a unified database. In a 5G communication system, the network open network element can be a Network Exposure Function (NEF) network element. In future communication systems, the network open network element can still be an NEF network element, or it can have other names, which are not limited in the embodiments of this application.

[0062] The session management network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting user plane network elements that provide message forwarding functions. In 5G communication systems, this session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or it may have other names, which are not limited in the present embodiment.

[0063] The data management network element is used for generating authentication credentials, user identification processing (such as storing and managing user permanent identities), access control, and contract information management. In a 5G communication system, this data management network element can be a unified data management (UDM) network element. In future communication systems, the unified data management can still be a UDM network element, or it can have other names, which are not limited in the embodiments of this application.

[0064] The policy control network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decisions. In the 4G communication system, the policy control network element can be a policy and charging rules function (PCRF) network element. In the 5G communication system, the policy control network element can be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names, which are not limited in the embodiments of this application.

[0065] Figure 2A also shows the interfaces for interaction between network elements, such as the N1 interface for interaction between the UE and the AMF, which are not listed here one by one.

[0066] As mentioned above, the network elements that may be involved in the various embodiments of the present application are mainly introduced. In addition, Figure 2A also involves other network elements, such as the network slice selection function (NSSF) network element and the authentication service function (AUSF) network element, which will not be introduced in detail here. In addition, the core network may also include a unified data repository (UDR) network element (not shown in Figure 2A). For another example, the core network may also include a network repository function (NRF) network element (not shown in Figure 2A).

[0067] Figure 2B provides a network architecture for a device to access the network through a 5G-RG according to an embodiment of the present application. The network architecture may include: a 5G-RG, a CN part, and a device that accesses the CN through the 5G-RG. Among them, the 5G-RG is an RG that can be connected to the 5G core network (5th generation core network, 5GC), and plays the role of a UE relative to the 5G core network. It supports security units and exchanges N1 signaling with the 5GC. The 5G-RG can be a 5G-BRG (enterprise-level residential gateway) or a 5G-CRG (personal-level residential gateway).

[0068] The CN part of the system may include an access management network element (AMF network element), a session management network element (SMF network element), a user plane network element (P network element), and may also include a UDM network element, a PCF network element (not shown in the figure), etc. Furthermore, the system may also include an NSSF network element, an AUSF network element (not shown in the figure), etc. The CN part of the system and other network elements used to support system functions can be specifically referred to the relevant description in the aforementioned Figure 2A, and will not be repeated here.

[0069] Figure 2B also shows the interfaces for interaction between network elements, such as the N1 interface for interaction between 5G-RG and AMF, which are not listed here one by one.

[0070] In addition, the system may also include a wireline access gateway function (W-AGF), which is a network function in the wired 5G access network (W-5GAN) and is used to provide a connection between the 5G-RG and the 5GC.

[0071] It is understandable that the network elements or functions shown in Figures 2A and 2B can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). In one possible implementation, the above-mentioned network elements or functions can be implemented by one device, or by multiple devices together, or can be a functional module within a device. The embodiments of the present application do not specifically limit this. In addition, in the following text, for the convenience of description, "network element" can be omitted. For example, the SMF network element in the embodiment of the present application has the same meaning as SMF. The two words "network element" are omitted for the convenience of description, and the rest are similar. In addition, it should be noted that the embodiments of the present application do not limit the names of the network elements in the communication system. For example, in communication systems of different standards, each network element can have other names; for another example, when multiple network elements are integrated into the same physical device, the physical device can also have other names.

[0072] The following introduces the prior art involved in the embodiments of this application.

[0073] Please refer to FIG3A , which is a flowchart of establishing a protocol data unit (PDU) session according to an embodiment of the present application. As shown in FIG3A , the process includes the following steps:

[0074] 1. The UE sends a PDU session establishment request message to the AMF.

[0075] It carries the PDU session ID and request type. The request types are as follows:

[0076] 1) Initial request: used to request the establishment of a new PDU session;

[0077] 2) Existing PDU session: This request type refers to the handover of an existing PDU session between 3GPP access and non-3GPP access;

[0078] 3) Emergency request: This request type refers to a PDU session established for emergency services.

[0079] 2.AMF selects SMF.

[0080] The AMF checks whether the session identifier in the session establishment request message of the initial request type has been used by other PDU sessions of the UE. If the non-access stratum (NAS) message does not carry single network slice selection assistance information (S-NSSAI), the AMF determines the slice information of the serving public land mobile network (PLMN) of the requested PDU session from the UE's current allowed NSSAI. If there is only one slice information in the allowed NSSAI, the slice information is used as the S-NSSAI. If there are multiple slice information in the allowed NSSAI, the S-NSSAI is selected based on the UE subscription (when the subscription contains only one default S-NSSAI and the corresponding serving PLMN's mapped home PLMN (HPLMN) S-NSSAI is included in the allowed NSSAI) or based on the operator policy (for example, if a selected S-NSSAI allows any UE-requested data network name (DNN), it will be used as the S-NSSAI). When the NAS message contains the slice information of the serving PLMN but does not contain the DNN, if the default DNN exists in the UE's subscription information, the AMF uses the DNN corresponding to the slice information in the subscription as the DNN of the requested PDU session; otherwise, the serving AMF selects the locally configured DNN for the S-NSSAI of the serving PLMN.

[0081] The AMF discovers a suitable SMF based on the S-NSSAI and DNN. The suitable SMF is the SMF that contains the UE's PDU session policy. The specific process of the SMF obtaining the UE's PDU session policy (the process of the SMF performing SM policy association) includes: the SMF sends a session management (SM) policy association request to the PCF to request the UE's policy and charging control (PCC) authorization, wherein the SM policy association request includes the UE's identification information, such as the UE's user permanent identifier (SUPI); then the PCF determines whether the SUPI contains the UE's subscription information, including the PCF querying the UE's subscription information from the UDR and other network elements based on the SUPI. If so, the PCF establishes an SM policy association with the SMF and sends a response message to the SMF, and the response message includes the PDU session policy information.

[0082] If the session establishment request type is initial, the AMF stores the relationship between the S-NSSAI, DNN, session identifier, SMF ID, and access type of the PDU session. Access types include 3GPP access and non-3GPP access.

[0083] 3.AMF sends a PDU session establishment request message (Nsmf_PDU session_CreateSMContext Request) to SMF. This message includes the UE's SUPI, the UE's requested DNN, and the S-NSSAI.

[0084] 4. The SMF performs a subscription retrieval from the UDM. That is, if the HPLMN session management subscription data corresponding to the SUPI, DNN, and S-NSSAI is not available, the SMF queries the UDM for the subscription information (of the UE corresponding to the SUPI).

[0085] 5. SMF sends a response message (Nsmf_PDU session_CreateSMContext Response) to the PDU session establishment request to AMF. If SMF accepts AMF's PDU session establishment request, SMF creates an SM context (SM Context) for the PDU session and includes the SM context identifier (SM Context ID) in the request response message returned to AMF. If SMF does not accept AMF's PDU session establishment request, the response message sent to AMF includes the reason for rejection.

[0086] 6. This step is optional. If the session request type is an existing PDU session or an emergency request, this step is skipped. The SMF determines whether secondary authentication is required based on the SM policy associated with the DN.

[0087] 7a. If the PDU session uses dynamic PCC rules, SMF needs to select the appropriate PCF.

[0088] 7b.SMF performs the SM policy association process, as described in step 2 above.

[0089] 8. If the session establishment request type is an initial request, the SMF allocates a session and service continuity (SSC) mode for the session. The SMF selects a UPF and allocates an IP address for the PDU session.

[0090] 9-11.SMF sends relevant information of the PDU session to the UE, including the PDU session identifier, control plane tunnel information (N3 tunnel information), etc.

[0091] The following is an introduction to the URSP rules:

[0092] URSP can be sent to UE by PCF or generated based on UE's local pre-definition to enable UE to select matching network resources (PDU session) for services or applications, that is, to determine whether an application or service can be associated with an established PDU session, whether N3GPP access can be used, or whether a new PDU session needs to be established.

[0093] Currently, URSP rules have the following dimensions: rule priority, transmission descriptor, and routing descriptor list.

[0094] For the description of rule priority and transmission descriptor, please refer to Table 0-1 below, and for the list of routing descriptors, please refer to Table 0-2 below.

[0095] Table 0-1

[0096] Table 0-2

[0097] Where > indicates the subdirectory of the previous line.

[0098] Based on the above table, an example of a URSP rule is shown in Table 0-3:

[0099] Table 0-3

[0100] As shown in Table 0-3, if the DNN where App_1 is located is DNN_1, then according to the rule priority, the PDU session should be matched first according to the first rule in the table.

[0101] Please refer to FIG3B , which is a flowchart of a URSP provided in an embodiment of the present application. As shown in FIG3B , the URSP workflow includes the following steps:

[0102] 1. The UE sends a URSP policy request to the PCF through the AMF, and the PCF issues the URSP policy to the UE.

[0103] 2. The UE initiates a network connection request to the application that matches the uploaded and uploaded flow descriptions on the UE according to the URSP policy.

[0104] 3. The process of establishing a network connection will match the specific "network parameters" carried by the components in the terminal URSP rules (i.e. the DNN, SSC mode, etc. mentioned above) with the actual network resources.

[0105] 4. Only when all components in the URSP are matched successfully will the network allocate a network resource that meets the UE's request to the UE's corresponding application and provide network services.

[0106] In the existing technology, a PDU session is established for a UE based on the UE's subscription information. Therefore, after the PDU session is established, the server provides the UE with QoS guarantees that correspond to the UE's subscription information (which can be used to determine QoS parameters). In other words, a PDU session established for the same UE will only have one default QoS parameter. This will prevent multiple devices accessing the network through a single UE from obtaining differentiated QoS guarantees.

[0107] Based on this, an embodiment of the present application provides a communication method. Please refer to FIG4A, which is a flowchart of a communication method provided in an embodiment of the present application. As shown in FIG4A, the method includes the following steps:

[0108] 201. A first device sends a first message to a second device, where the first message is used to request to establish or modify a protocol data unit (PDU) session of the first device.

[0109] The first device in the embodiment of the present application refers to a device that accesses the network through the second device, and itself has not signed a contract with the network. A specific example is the 3GPP device or N3GPP device described in Figures 1 to 2B above. The first device can be connected to the second device through Bluetooth, WiFi, wireless local area network (WLAN) or wired. The second device refers to a device that has signed a contract with a mobile network, such as the UE or 5G-RG described in Figures 1 to 2B above. The subscription information of the second device includes a device identifier that can be connected to the second device, that is, a device identifier that can be used by the first device, and a device profile corresponding to the device identifier (or, the subscription data of the device that can be logged in on the UE, or the context information associated with the device identifier). In addition, the device profile and the device identifier exist in the subscription information of the second device. The storage location is not limited. In one possible implementation, the device profile and the device management subscription information (device management subscription data) corresponding to the device identifier are added to the subscription information. In another possible implementation, the device identifier is stored in the existing identifier translation data, and the device profile is stored in the existing session management subscription information (session management subscription data). For example, a device configuration file may include one or more of the following:

[0110] One or more device identifiers, i.e., identifiers assigned to the connected device after the device and the second device are connected, are used to identify the device, and the device identifier contains at least an information portion that uniquely identifies the second device, so that the network side can identify the second device connected to the device through the device identifier. The specific data structure is not limited in the present invention. One possible implementation method is to add bit information to the UE identifier such as SUPI. In another possible implementation method, the device identifier is identified using the NAI format: name+deviceid@realm. The name part is used to carry information that uniquely identifies the second device, the deviceid part is used to distinguish different devices connected to the second device, and the realm part carries routing information. In an embodiment of the present application, the device identifier in the contract information of the second device is set using the contract identifier of the second device, which can reduce the implementation complexity on the one hand. On the other hand, for the network side, when the device identifier is obtained, it can quickly associate it with the contract information of the second device, which can improve the efficiency of querying the contract information of the second device, and thereby improve the efficiency of establishing a PDU session.

[0111] Device level. For example, the device level is used to distinguish the service level provided by the network side for the device, such as gold equipment, silver equipment, bronze equipment, etc.

[0112] QoS parameters: For example, QoS parameters are used to identify the parameters of the default QoS flow corresponding to the device when establishing a session, such as the maximum bandwidth, delay, packet loss rate, etc. of the service.

[0113] Session management information. Exemplarily, the session management information is used to indicate session-related parameters that can be used by the device, such as DNN, S-NSSAI, SSC mode, etc.

[0114] Device-related information, such as the MAC address or PEI mentioned above, is used to limit devices that must use the device profile, such as the first device. For example, certain devices in a home network scenario, such as projectors and laptops, require the highest level of QoS protection. Device-related information for such devices can be written to the device profile.

[0115] After establishing a connection with the second device, the first device may send a first message to the second device to request the establishment or modification of a PDU session for the first device, that is, to establish a data transmission channel between the first device and the network side, so that the first device can obtain service data from the network side.

[0116] 202. The second device receives the first message and, based on the first message, sends a second message to the first network element. The second message is used to request modification or establishment of a PDU session corresponding to the first device identifier. Exemplarily, the second message may be Nsmf_PDUSession_CreateSMContext Request, and the first network element may be an AMF. The second message includes the first device identifier, where the first device identifier corresponds to the first device and is related to the subscription information of the second device in the first network element. The subscription information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine Quality of Service (QoS) parameters.

[0117] In an embodiment of the present application, during the process of establishing a PDU session between the first device and the network side, since the first device is invisible to the network side, only the second device can communicate directly with the network side. Therefore, the second device initiates a PDU session establishment request to the network side. Furthermore, since the first device has no contract information on the network side, the network side can only establish or modify the PDU session based on the contract information of the first device. Therefore, in order to enable the network side to establish a PDU session for the first device, one or more device identifiers are added to the contract information of the second device on the network side, and the first device identifier among these device identifiers is assigned to the first device, so that the second device can complete the establishment or modification of the PDU session of the first device by requesting the network side to establish or modify the PDU session corresponding to the first device identifier.

[0118] Please refer to Figure 4B, which is a schematic diagram of a PDU session establishment scenario provided by an embodiment of the present application. As shown in Figure 4B, for the first device 1, the second device initiates a PDU session establishment request to the first network element based on the first device identifier 1 assigned to the first device 1 (the second message sent by the second device to the first network element includes the first device identifier 1). The first network element itself, or other network elements connected to the first network element, establishes or modifies a PDU session with the second device based on the first device identifier 1, that is, modifies or establishes the PDU session corresponding to the first device identifier 1. Then the PDU session is the PDU session corresponding to the first device 1. Corresponding to Figure 4B, the first device 1, the first device 2 and the first device 3 correspond to three PDU sessions ①②③ respectively.

[0119] After receiving the first message sent by the first device, the second device can obtain the first device identifier corresponding to the first device, so as to determine which device identifier corresponds to the device to request the network side to establish a PDU session. The second device can specifically determine the first device identifier in the second message in the following two ways:

[0120] (1) Determined according to the first device identifier included in the first message.

[0121] It should be noted that in this case, the first device stores the first device identifier, wherein the first device identifier can be sent by the second device to the first device. Specifically, when the first device and the second device establish a connection, including a Bluetooth connection, a WiFi connection, or a wireless connection, the second device sends the first device identifier to the first device based on the application layer.

[0122] (2) The first message does not include the first device identifier but includes device-related information of the first device. The second device determines the first device identifier based on the correspondence between the first device identifier and the device-related information of the first device stored in the second device.

[0123] The device-related information of the first device is used to uniquely identify the first device. Exemplarily, the device-related information of the first device may be a media access control address (MAC) address, a permanent equipment identity (PEI), etc. The second device stores a correspondence between at least one device identifier and the device-related information. The storage format is not limited in this application; exemplarily, it may be stored in a table.

[0124] After receiving the relevant information of the first device sent by the first device, the second device obtains the first device identifier based on the stored corresponding relationship, and then determines to request to establish a PDU session for the first device corresponding to the first device identifier.

[0125] 203. The first network element receives the second message sent by the second device, and sends a third request message to the second network element, requesting to establish a corresponding SM context for the session requested by the first device through the second message, that is, the first device identifier corresponds to the PDU session.

[0126] The first network element on the network side is the network element that performs access and mobility management of the second device, and the second network element is the network element responsible for session management. The first network element can specifically be an AMF, and the second network element can be an SMF. Exemplarily, the message requesting the establishment of an SM context can be an Nsmf_PDUSession_CreateSMContext Request message. The first network element AMF can send the first device identifier, as well as related information such as DNN and S-NSSAI, to the SMF through the Nsmf_PDUSession_CreateSMContext Request message, so that the SMF can establish an SM context for the session.

[0127] 204. The second network element sends a third feedback message to the first network element according to the first device identifier, where the third feedback message indicates that establishment of the SM context is completed.

[0128] Optionally, before determining whether the SM context can be established, if there is no device configuration file corresponding to the first device identifier in the SMF, the SMF queries the device configuration file corresponding to the first device identifier from the third network element to determine whether the PDU session requested by the first device and the QoS parameters of the established PDU session (i.e., the QoS parameters in the device configuration file corresponding to the first device identifier) ​​can be established for the first device. The third network element is a network element that stores the contract information of the second device. Exemplarily, the third network element can be a UDM network element. The SMF sends a query request message to the UDM to query the device configuration file corresponding to the first device identifier. The query request message can specifically be a Nudm_SDM_Get Request message.

[0129] The correspondence between the device identifier and the device configuration file in the contract information of the second device can be one-to-one or many-to-one, which is not limited in this application. That is, when the device identifier and the device configuration file correspond one-to-one, the specific storage method can be one device identifier indexing one device configuration file, or each device configuration file can include one device identifier; when the device identifier and the device configuration file correspond many-to-one, the specific storage method can be to include multiple device identifiers in each device configuration file.

[0130] The query request sent by the SMF includes the first device identifier, and the device configuration file corresponding to the first device identifier can be obtained.

[0131] The QoS parameters corresponding to the device profile of the device identifier are different, and the QoS requirements that need to be met by the PDU session established for the device identifier are also different. The multiple devices connected to the second device can establish PDU sessions that meet different QoS requirements with the network side through their corresponding device identifiers. The network side establishes PDU sessions with different QoS parameters for different devices based on the QoS parameters in the device profile corresponding to different device identifiers.

[0132] Optionally, the device identifier present in the contract information of the second device may be related to the contract identifier of the second device.

[0133] The third network element sends a query feedback message in response to the query request message of the second network element, and the query feedback message includes the device configuration information corresponding to the first device identifier. The second network element determines the QoS parameters based on the device configuration information, and then establishes a PDU session that meets the QoS parameters. The second network element then sends a third feedback message to the first network element to indicate the completion of the establishment or update of the SM context of the PDU session corresponding to the first device identifier. When the second network element is an SMF network element and the first network element is an AMF network element, the third feedback message can specifically be Nsmf_PDUSession_CreateSMContext Response, which is used to indicate the result of the SM context establishment. If successful, the message includes the SM context ID. If it fails, the reason for the failure is returned.

[0134] If possible, after receiving the query feedback message from the third network element, the second network element can also determine whether secondary authentication of the second device is required based on the security information in the device configuration information, and initiate an authentication process if necessary.

[0135] 205. The network performs secondary authentication on the first device.

[0136] If possible, after receiving the query feedback message from the third network element, the second network element can also determine whether secondary authentication of the first device is required based on the security information in the device configuration information. If required, the authentication process is initiated. Alternatively, the second network element can trigger secondary authentication of the first device based on policies related to the DN. For example, if the policy related to the DN accessed by the first device indicates that all session requesters of that DN, such as terminal devices / users, need to undergo secondary authentication, the second network element will trigger secondary authentication.

[0137] 206. The second network element selects PCF.

[0138] That is, when the PDU session uses dynamic PCC rules, the SMF needs to select the appropriate PCF.

[0139] 207. The second network element sends an SM policy update request message to the PCF.

[0140] That is, the SMF initiates an SM policy update request to the PCF, and the request message includes the UE identifier, the PDU session identifier, and the device identifier. In this embodiment, the device identifier in the request message can be the first device identifier. The SM policy update request message can specifically be an Npcf_SMPolicyControl_Update Request message.

[0141] 208a. The PCF sends a policy request message to the UDR, requesting to obtain the session policy control data of the PDU corresponding to the device identifier. The request message carries the device identifier, such as the first device identifier of the first device. The policy request message may specifically be a Nudr_DM_Query Request message.

[0142] 208b. The UDR returns the PDU session policy control data corresponding to the first device identifier to the PCF. The UDR uses the device identifier (including the first device identifier) ​​to find the data corresponding to the device identifier in the relevant data of the UE and returns the PDU session policy control data corresponding to the PCF device (e.g., the first device), such as the allowed services, user level, and the maximum aggregate bit rate of all GBR QoS flows corresponding to this DNN / S-NSSAI. Specifically, this data may be returned to the PCF via a Nudr_DM_Query Response message.

[0143] 209. PCF decides whether to update the policy or send new policy control data to SMF.

[0144] 210. The PCF sends a policy update request response to the SMF, where the message carries the PDU session policy control data corresponding to the first device identifier. The policy update request response may specifically be an Npdf_SMPolicyControl_Update Response message.

[0145] 211. The second network element selects the UPF. That is, the SMF selects the UPF.

[0146] The parameters that SMF needs to consider when selecting UPF include one or more of the following: dynamic load of UPF, relative static capacity of UPF in UPF supporting the same DNN, location of UPF, location information of UE, performance of UPF and functions required for specific UE session, data network name DNN, PDU session type (IPV4 / IPV6 / Ethernet type / unstructured type), SSC mode selection of PDU session, UE subscription information in UDM, etc.

[0147] It should be noted that the implementation process of the above steps 206 to 211 may be different from the description. As long as the process can obtain the N3 tunnel information corresponding to the PDU session, it can be used in the embodiment method of the present application.

[0148] 212a. The second network element sends a fourth feedback message to the first network element, where the fourth feedback message includes information related to the PDU session corresponding to the first device identifier, such as the PDU session identifier and N3 tunnel information. For example, the fourth feedback message may be a Namf_Communication_N1N2MessageTransfer message.

[0149] 212b. The first network element receives the fourth feedback message and, based on the fourth feedback message, sends a first feedback message to the second device. The first feedback message indicates that establishment or modification of the PDU session corresponding to the first device identifier has been completed, allowing the second device to perform user plane data transmission. The PDU session satisfies the QoS parameters determined by the device profile corresponding to the first device identifier. The first feedback message may also include relevant information about the PDU session. Exemplarily, the first feedback message may be a PDU Session Establishment Accept message.

[0150] 213. The second device receives the first feedback message and sends a second feedback message to the first device according to the first feedback message, where the second feedback message indicates that the establishment or modification of the PDU session corresponding to the first device is completed. Correspondingly, the first device receives the second feedback message.

[0151] The second device learns from the first feedback message that the establishment or modification of the PDU session corresponding to the first device identifier has been completed. The second device may send a first feedback message to the first device, indicating that the establishment or modification of the PDU session corresponding to the first device is complete. The first feedback message may also include relevant information about the PDU session so that when the first device wants to communicate with the network side, it can initiate a session request to the second device based on the PDU session information. Exemplarily, the second feedback message may be a PDU Session Establishment Accept message.

[0152] As can be seen, this embodiment adds a device identifier and a corresponding device profile to the subscription information of the second device, and assigns a first device identifier to the first device that accesses the network through the second device. This enables the network to determine QoS parameters based on the device profile corresponding to the first device identifier and establish a PDU session for the first device that meets the QoS parameters. This enables the network to provide differentiated QoS guarantees for multiple devices that access the network through a single device.

[0153] The above embodiment describes the process of establishing a PDU session between a first device and a network side through a second device. In the implementation process of the above embodiment, the second message sent by the second device to the first network element includes the first device identifier corresponding to the first device. The following describes possible implementation methods for assigning the first device identifier to the first device. Please refer to Figure 5, which is a flowchart of a first device identifier assignment provided in an embodiment of the present application. As shown in Figure 5, the method includes the following steps:

[0154] 301a. The third network element sends a third message to the first network element, where the third message is used to request modification of UE parameters and includes one or more device identifiers in the subscription information of the second device.

[0155] As described above, the third network element may be a UDM, the first network element may be an AMF, the second device may be a UE, and the first device may be an N3GPP device. This is used as an example in the following embodiments and will not be repeated hereafter.

[0156] After completing the authentication of the UE, the UDM decides to update the pre-stored parameters in the UE based on the UE's subscription information. The UDM sends a third message to the AMF requesting to modify the UE parameters. The third message can specifically be a Nudm_SDM_Notification message. This message is used to transmit the UE-related parameters to be updated. This message includes one or more device identifiers in the UE's subscription information. One or more device identifiers are used to allocate to one or more N3GPP devices connected to the UE. Alternatively, the message may also include whether the UE needs to send a confirmation return message to the UDM, and whether the UE needs to re-register with the network after updating the parameters.

[0157] 302a. The first network element receives the third message and sends a fourth message to the second device according to the third message. The fourth message includes one or more device identifiers in the contract information of the second device.

[0158] After the AMF obtains one or more device identifiers in the subscription information of the second device, it sends the fourth message to the UE via the fourth message. The fourth message can be a downlink NAS message that instructs the UE to update UE parameters and includes the device identifier in the UE subscription information.

[0159] Steps 301a to 302a above describe a method for a second device to obtain its corresponding device identification. This may be referred to as operation a. Where possible, the second device may obtain its corresponding device identification through operation b. Operation b includes the following steps:

[0160] 301b. The fourth network element updates the policy information of the second device to the fifth network element.

[0161] The fourth network element is a network element for storing structured data such as static subscription policy data of the second device, and the fifth network element is a policy control network element. The fourth network element can be specifically a UDR, and the fifth network element can be specifically a PCF. The subscription policy data stored in the UDR can specifically include: the UE's unassigned device identifier and the PDU session policy control data corresponding to the device identifier, such as allowed services, user level (gold / silver), the maximum aggregate bit rate of all GBR QoS flows corresponding to this DNN / S-NSSAI, etc. The UDR updates the device identifier in the subscription policy data to the PCF, which can be specifically updated through the Nudr_DM_Notify message. The message carries the device identifier, and the PCF uses the device identifier to update related policies, such as using the device identifier to update the user routing policy (URSP), and adding the device identifier in the transmission descriptor of the URSP. That is, the PCF will update one or more URSP rules with the device identifier as the transmission descriptor to the UE. When the device identifier is consistent with the device identifier in the transmission descriptor, a PDU session that complies with the routing component will be established for the device with the device identifier based on the rule, enabling the UE to establish the same PDU session for one or several devices (N3GPP devices) with the same QoS or the same user level based on the URSP.

[0162] 302b-1. The fifth network element sends the updated policy information of the second device to the first network element. The PCF sends the updated UE policy, such as the URSP policy, to the AMF. The policy update message includes the device identifier and the new associated policy generated based on the device identifier. Exemplarily, the PCF sends the UE policy including the device identifier to the AMF via Namf_Communication_N1N2Message Transfer.

[0163] 302b-2. The first network element sends the updated policy information of the second device to the second device, illustratively via a DL NAS message.

[0164] Exemplarily, the AMF sends it to the UE via a DL NAS message.

[0165] 303. The second device obtains one or more device identifiers, including the second device receiving the fourth message and obtaining the one or more device identifiers from the contract information of the second device in the fourth message; or the second device obtaining the one or more device identifiers according to the updated policy information of the second device.

[0166] The UE obtains the UE parameters that need to be updated based on the fourth message, including updating the device identifier in the UE subscription information to the UE. The UE performs a security check on the updated data. If the security check passes, the information is forwarded to the Universal Subscriber Identity Module (USIM) and stored in the USIM card.

[0167] Alternatively, the UE performs policy update according to the received updated policy information and simultaneously obtains the device identity that can be allocated.

[0168] The device identification in the UE may also be stored in the UE in other ways, such as by pre-setting, etc. That is, the above steps 301a to 302a, or steps 301b to 302b-2 are optional steps.

[0169] 304. The first device establishes a connection with the second device.

[0170] The manner in which the N3GPP device (first device) establishes a connection with the UE may be as described above, using Bluetooth technology, WIFI technology, WLAN or wired technology, etc., which is not limited in this embodiment.

[0171] 305. The second device allocates a first device identifier to the first device.

[0172] During this process, the UE first authenticates the N3GPP device and determines that the N3GPP device is legal. The UE then determines whether there are any unused device identifiers in its own stored device identifiers. If so, a device identifier that is not assigned to any device is selected from the device identifiers stored in the USIM card and assigned to the N3GPP device. This includes assigning a first device identifier to a first device. The allocation rule is based on the internal implementation of the UE and may be allocated based on information such as whether N3GPP is trustworthy and the QoS level required by the N3GPP device. One possible implementation method is to implement it based on the application layer. The application will learn from the UE which devices are connected to the UE. The user can log in to the application and configure the relationship between the device identifier and the device. For example, if the user configures the AR / VR device connected to the UE to use the highest QoS through the application, then for the UE, the UE will assign it a device identifier with the highest level QoS parameters.

[0173] If the N3GPP device is illegal or all device identifiers in the UE are used, that is, the number of devices connected to the UE has reached the upper limit, the UE refuses to connect to the N3GPP device or only provides the device with the basic QoS guarantee in the UE's contract. It should be noted that the method of rejecting the connection can be to display a pop-up window indicating a connection failure on the N3PP device, etc., which is not limited in this embodiment. Another possible implementation method is that the UE still accepts the connection with the N3GPP device, but does not assign a device identifier to the device. The network side only provides services to the device based on the QoS parameters in the UE's own contract information.

[0174] After the second device assigns the first device identifier to the first device, the embodiment of the present application may further include the following steps:

[0175] 306. The second device sends the first device identification to the first device. Correspondingly, the first device receives and stores the first device identification.

[0176] The UE sends the device identifier assigned to the N3GPP to the N3GPP device, causing the N3GPP device to store the corresponding device identifier. The first device receives and stores the first device identifier. When the first device sends a first message to the second device requesting to establish or modify a PDU session for the first device, the first device identifier may also be sent to the second device. The UE may specifically send the device identifier to the N3GPP device via an EAP message.

[0177] Alternatively, the embodiment of the present application may further include the following steps:

[0178] 307. The second device stores the first device identifier and the device-related information of the first device in the second device in correspondence therewith.

[0179] When establishing a connection with an N3GPP device, the UE obtains the device-related information of the N3GPP device. Therefore, after assigning a device identifier to the N3GPP device, the UE can store the device identifier and the N3GPP device-related information accordingly. This includes the correspondence between the device-related information of the first device and the first device identifier. In this way, when the first device sends a first message to the second device, if the first message includes the device-related information of the first device, the second device can match the first device identifier based on the device-related information of the first device and send the first device identifier in the second message.

[0180] In other words, steps 306 and 307 are optional method steps. If step 306 is included in the method embodiment, step 307 can also be performed simultaneously. When the first device sends a first message that carries the first device identifier, the second device verifies the first device identifier based on the correspondence between its stored device identifier and device-related information, further ensuring communication reliability. If step 306 is not included in the method embodiment and only step 307 is included, the exchange of information between the second device and the first device can be reduced, thereby reducing UE overhead.

[0181] In addition, device-related information and device identifiers are not fixedly corresponding. That is, a device uses a device identifier after connecting to a UE. After the device is disconnected from the UE, the device identifier can be assigned to any other device. For example, a first device identifier is assigned to the first device when the first device is connected to the second device. After the first device is disconnected from the second device, the first device identifier can be assigned to another N3GPP device connected to the second device. In other words, the device identifier is only unique on the PLMN corresponding to the UE, and is not guaranteed to be unique globally.

[0182] As can be seen, in the embodiment of the present application, the second device obtains the device identifier included in its own contract information and assigns the first device identifier therein to the first device connected to itself. This can reduce the complexity of assigning the device identifier to the first device and improve communication efficiency.

[0183] Please refer to FIG6 , which is another flowchart of allocating a first device identifier according to an embodiment of the present application. As shown in FIG6 , the method includes the following steps:

[0184] 401. A first device establishes a connection with a second device.

[0185] Please refer to the related description of the aforementioned step 304.

[0186] 402. The second device authenticates the first device.

[0187] That is, the UE determines that the N3GPP device is legal.

[0188] 403. The second device sends a first request message to the first network element, where the first request message is used to request allocation of a device identifier for the first device.

[0189] The UE requests the network to allocate a device identifier for the N3GPP device. In other words, the device identifier in the UE's subscription information is stored in the UDM and not previously distributed to the UE. The UE sends a first request message to the AMF to request allocation of a device identifier for the N3GPP device. The first request message may specifically be a device identifier request message. The first request message carries first device information, which is used to uniquely identify the first device.

[0190] After the AMF receives the first request message, it should be noted that the network side may determine that a device identifier needs to be allocated to it based on the name of the first request message, or may determine that a device identifier needs to be allocated to it based on the device-related information of the first device in the first request message. The specific allocation method is as follows:

[0191] 404a. The first network element queries the third network element for the contract information of the second device.

[0192] 405a. The first network element allocates a first device identifier to the first device according to the subscription information of the second device.

[0193] The following example uses the third network element as UDM. AMF queries the UE's contract information from UDM to determine whether the device identifier can still be allocated to the N3GPP device and which device identifiers can be allocated to the N3GPP device. For example, AMF can complete the query through the Nudm_SDM_Get operation. AMF sends a Nudm_SDM_Get Request message to UDM, requesting to query the UE's contract data. The message carries the UE's contract identifier, such as SUPI, to indicate which UE's contract data is requested. After UDM queries the contract data based on the contract identifier, it returns a Nudm_SDM_Get Response message to AMF, which includes the contract data of the UE.

[0194] The UE's subscription information includes the device identifier and, more specifically, whether the device identifier has been assigned to the device. A single bit can be used to indicate whether the device identifier has been assigned. For example, a single bit value of 1 indicates that the device identifier has been assigned to an N3GPP device, while a value of 0 indicates that the device identifier has not been assigned to an N3GPP device.

[0195] The AMF checks whether there are any unassigned device identifiers based on the subscription information. If not, no identifier is assigned to the device. In this case, the UE can refuse to connect to the device or only provide the basic QoS guarantees in the UE subscription. If there are still unassigned device identifiers, an unassigned device identifier is assigned to the device.

[0196] Alternatively, the UE's subscription information may also include the UE's maximum number of connectable devices. The AMF determines whether the number of devices connected to the UE reaches the UE's maximum number of connectable devices based on the subscription information. If so, no device identifier is assigned to the device. In this case, the UE may refuse to connect to the device or only provide the device with the basic QoS guarantees specified in the UE's subscription information. If not, an unassigned device identifier is assigned to the device.

[0197] Alternatively, the UE's subscription information may further include a correspondence between the device identifier and the device-related information. For example, if the device identifier 1 corresponds to the device-related information 1, and the device-related information 1 is used to uniquely identify the N3GPP device 1, it means that the device identifier 1 has been assigned to the N3GPP device 1. In this case, the first request information sent by the UE to the AMF includes the device-related information of the N3GPP device. During the process of the AMF obtaining the device identifier assigned to the N3GPP device, the UDM correspondingly stores the device-related information of the N3GPP device and its assigned device identifier.

[0198] After the AMF allocates the device identifier, it records the device identifier and the device-related information in the UE context. For example, the AMF allocates a first device identifier to the first device and records the first device identifier and the device-related information of the first device in the UE context.

[0199] 406a. The first network element sends instruction information to the third network element. The instruction information instructs the third network element to update the stored subscription information of the second device according to the first device identifier allocated to the first device.

[0200] The AMF allocates a device identifier for the N3GPP device, and the AMF updates the information to the UE's subscription information in the UDM. For example, if the AMF allocates a first device identifier for the first device, the indication information instructs the UDM to update the allocation of the first device identifier in the subscription information to allocated.

[0201] Assuming that the UDM stores the correspondence between the allocated device identifier and the N3GPP device to which the device identifier is allocated, the AMF updates the newly allocated device identifier and the device-related information of the allocated N3GPP device to the UE's subscription information in the UDM. For example, the AMF updates the first device identifier and the device-related information of the first device to the UE's subscription information.

[0202] Alternatively, after receiving the first request message, the AMF may execute the following method:

[0203] 404b. The first network element sends a second request message to the third network element based on the first request message. The second request message is used to request allocation of a device identifier for the first device. The third network element stores the subscription information of the second device.

[0204] The AMF sends a second request message to the UDM, requesting that the UDM directly allocate a device identity for the N3GPP device. The second request message may be a Nudm_UECM_Update Request message, which carries the UE's subscription identity such as SUPI, device-related information, etc.

[0205] 405b. The third network element allocates a first device identifier to the first device according to the subscription information of the second device.

[0206] The process of the UDM allocating a device identifier to the N3GPP device can refer to the process of the AMF allocating a device identifier to the N3GPP device in step 405a above, which will not be repeated here. The allocation result includes allocating a first device identifier to the first device.

[0207] 406b. The third network element sends a second response message to the first network element, where the second response message includes the first device identifier.

[0208] The UDM sends a second response message to the AMF to return the allocation result. Exemplarily, the second response message may be a Nudm_UECM_Update Response message, which includes the UE's subscription identifier and device identifier. For example, it includes the SUPI and first device identifier of the first device. Alternatively, it may include device-related information of the first device.

[0209] That is to say, the above steps 404a to 406a and steps 404b to 406b are optional method steps. After performing one of the method steps, the method further includes:

[0210] 407. The first network element sends a first response message to the second device, where the first response message includes the first device identifier.

[0211] The AMF returns a first response message to the UE, which may include the device identity allocated to the N3GPP device, implicitly indicating that the device identity allocation result is successful. Alternatively, the device identity allocation success may be explicitly indicated through indication information.

[0212] Alternatively, the first response information may include indication information of device identification allocation failure.

[0213] The indication information may be expressed as a string, such as success (device identification allocation success) / failure (device identification allocation failure). Alternatively, the indication information may be expressed as a binary bit representing the result, such as 0 for device identification allocation failure and 1 for device identification allocation success, which is not limited in this application.

[0214] Specifically, the first response message may be a request for allocation identifier response.

[0215] 408. When the indication information in the first response message indicates that the allocation of the device identifier fails, the second device may refuse to establish a connection with the first device.

[0216] For example, the UE may notify the N3GPP device through a pop-up window indicating a connection failure. Alternatively, the UE's basic subscription may be used to provide QoS guarantees for the N3GPP device, rather than rejecting the connection. The details depend on the UE's internal implementation.

[0217] 409. When the device identifier is successfully allocated, the second device stores the correspondence between the device-related information of the first device and the first device identifier, or the second device sends the first device identifier to the first device.

[0218] The UE may send the device identifier to the first device, and the first device may retain the correspondence between the first device identifier and the device-related information of the first device. Alternatively, the UE may store the correspondence between the device-related information of the first device and the first device identifier. In this case, the UE may also simultaneously send the first device identifier to the first device. For details, please refer to the relevant descriptions of steps 306 and 307 above, which will not be repeated here.

[0219] As can be seen, in the embodiment of the present application, the second device initiates a request message to the network side to request a device identifier for the first device. The first network element on the network side, which is used for access and mobility management, or the third network element, which is used to store the subscription information of the second device, allocates the first device identifier to the first device, and the first network element returns the device identifier allocation result to the second device. This can improve the reliability of the device identifier allocation for the first device, thereby improving the reliability of the communication process.

[0220] Please refer to Figure 7, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device can be used to execute any of the methods in the aforementioned embodiments.

[0221] As shown in Figure 7, the communication device includes: a processing module 1501 and a transceiver module 1502. The processing module 1501 can be one or more processors, and the transceiver module 1502 can be a transceiver or a communication interface. The communication device can be used to implement the functions of the first device, the second device, the first network element, the second network element, the third network element, the fourth network element, the fifth network element or even more network elements in any of the above method embodiments. These network elements or network functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the communication device may also include a storage module 1503 for storing program code and data of the communication device.

[0222] In a first example, the communication device can function as the second device or a chip within the second device in Figures 4A-6 and execute the steps performed by the second device in the aforementioned method embodiments. Transceiver module 1502 is configured to support communication with the first device or first network element. Processing module 1501 can be configured to support actions performed by the second device in the aforementioned method embodiments, other than sending and receiving.

[0223] Specifically, the transceiver module 1502 is used to obtain a first message from the first device, where the first message is used to request to establish or modify a protocol data unit (PDU) session of the first device;

[0224] The processing module 1501 sends a second message to the first network element in combination with the transceiver module 1502 based on the first message, where the second message includes the first device identifier, and the second message is used to request modification or establishment of a protocol data unit (PDU) session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, the first device identifier exists in the contract information of the second device, and the contract information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine the quality of service (QoS) parameters of the PDU session;

[0225] The transceiver module 1502 receives a first feedback message from the first network element, where the first feedback message indicates that establishment or modification of a PDU session corresponding to the first device identifier is completed, and the PDU session meets QoS parameters;

[0226] The processing module 1501 sends a second feedback message to the first device based on the first feedback message in combination with the transceiver module 1502. The second feedback message indicates that establishment or modification of the PDU session corresponding to the first device is completed.

[0227] In a feasible implementation manner, the first message includes the first device identifier.

[0228] In a feasible implementation, the first message includes device-related information of the first device, and the device-related information of the first device is used to uniquely identify the first device; before the second device sends a second message to the first network element based on the first message, the processing module 1501 is also used to determine the first device identifier based on the device-related information of the first device, wherein the second device stores one or more correspondences between device identifiers and device-related information, including the correspondence between the first device identifier and the device-related information of the first device.

[0229] In a feasible implementation, before the second device obtains the first message from the first device and after the first device establishes a connection with the second device, the transceiver module 1502 sends the first device identifier to the first device.

[0230] In a feasible implementation, before the second device obtains the first message from the first device, the transceiver module 1502 receives and stores one or more device identifiers from the first network element; the processing module 1501 assigns a first device identifier among the one or more device identifiers to the first device.

[0231] In a feasible embodiment, before the second device obtains the first message from the first device, the transceiver module 1502 is also used to send a first request message to the first network element, where the first request message is used to request that a device identifier be assigned to the first device; receive a first response message, where the first response message includes the first device identifier; and the processing module 1501 determines to assign the first device identifier to the first device based on the first response message.

[0232] In a second example, the communication device can serve as the first network element or a chip within the first network element in Figures 4A-6 and execute the steps performed by the first network element in the above-described method embodiment. Transceiver module 1502 is configured to support communication with a second network element, a second network element, or a third network element. Processing module 1501 can be configured to support execution of actions other than sending and receiving performed by the first network element in the above-described method embodiment.

[0233] Specifically, the transceiver module 1502 is used to receive a second message sent by the second device, where the second message includes a first device identifier, and the second message is used to request modification or establishment of a protocol data unit (PDU) session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, and the first device identifier exists in the contract information of the second device, and the contract information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine the quality of service (QoS) parameters of the PDU session; send a third request message to the second network element, for requesting establishment of an SM context for the PDU session corresponding to the first device identifier; receive a third feedback message from the second network element, and the third feedback message indicates that establishment of the SM context is completed;

[0234] The processing module 1501 sends a first feedback message to the second device according to the third feedback message. The first feedback message indicates that the establishment or modification of the PDU session corresponding to the first device identifier is completed, and the PDU session meets the QoS parameters determined by the device configuration file corresponding to the first device identifier.

[0235] In a feasible embodiment, before the first network element receives the second message sent by the second device, the transceiver module 1502 is also used to receive a first request message from the second device, where the first request message is used to request that a device identifier be assigned to the first device; and send a first response message to the second device, where the first response message includes the first device identifier.

[0236] In a feasible implementation, before the first network element sends the first response message to the second device, the processing module 1501 is further configured to query the contract information of the second device from the third network element, and allocate a first device identifier to the first device according to the contract information of the second device.

[0237] In a feasible implementation, after the first network element assigns a first device identifier to the first device based on the contract information of the second device, the transceiver module 1502 is also used to send an indication message to the third network element, and the indication message instructs the third network element to update the stored contract information of the second device based on the first device identifier assigned to the first device.

[0238] In a feasible implementation, before the first network element sends a first response message to the second device, the processing module 1501 is also used to send a second request message to the second network element based on the first request message in combination with the transceiver module 1502, where the second request message is used to request that a device identifier be assigned to the first device, and the second network element stores the contract information of the second device; and receive a second response message from the second network element, where the second response message includes the first device identifier.

[0239] In a feasible implementation manner, the subscription information of the second device includes one or more device identifiers and whether the one or more device identifiers are allocated to the device.

[0240] In a feasible implementation, before the first network element receives the second message sent by the second device, the transceiver module 1502 is further used to receive one or more device identifiers included in the contract information of the second device from the third network element, where the one or more device identifiers include the first device identifier.

[0241] In a third example, the communication device can function as the first device or a chip within the first device in Figures 4A-6 and execute the steps performed by the first device in the above-described method embodiment. Transceiver module 1502 is configured to support communication with the second device. Processing module 1501 can be configured to support actions performed by the first device in the above-described method embodiment, other than sending and receiving.

[0242] Specifically, the transceiver module 1502 is used to send a first message to the second device, where the first message is used to request the establishment or modification of the protocol data unit (PDU) session of the first device. The first message includes a first device identifier, and the first device identifier exists in the contract information of the second device. The contract information also includes a device configuration file corresponding to the first device identifier, and the device configuration file is used to determine the quality of service (QoS) parameters; and receive a second feedback message, where the second feedback message indicates the completion of the establishment or modification of the PDU session corresponding to the first device.

[0243] In a feasible implementation, after the first device establishes a connection with the second device, the transceiver module 1502 receives the first device identification from the second device.

[0244] The processing module 1501 may be a processor that may execute computer-executable instructions stored in the storage module, so that the chip executes the method involved in any of the above embodiments.

[0245] Furthermore, the processor may include a controller, an arithmetic unit and a register. For example, the controller is mainly responsible for decoding instructions and issuing control signals for operations corresponding to the instructions. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations and logical operations, etc., and may also perform address operations and conversions. The register is mainly responsible for storing register operands and intermediate operation results temporarily stored during the execution of instructions. In a specific implementation, the hardware architecture of the processor may be an ASIC architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced RISC machines (ARM) architecture or a second processor (NP) architecture, etc. The processor may be single-core or multi-core.

[0246] The storage module may be a storage module within the chip, such as a register, cache, etc. The storage module may also be a storage module located outside the chip, such as a ROM or other type of static storage device that can store static information and instructions, RAM, etc.

[0247] It should be noted that the functions corresponding to the processor and the interface can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.

[0248] Please refer to Figure 8, which is a structural diagram of a simplified AN device provided in an embodiment of the present application, which can be used as an implementation method of the first network element, second network element, third network element, fourth network element, fifth network element or even more network elements of the present application.

[0249] The AN device includes a radio frequency signal transceiver and conversion part and a baseband part 42. The radio frequency signal transceiver and conversion part further includes a receiving module 41 and a sending module 43 (also collectively referred to as a transceiver module). The radio frequency signal transceiver and conversion part is mainly used for receiving and sending radio frequency signals and converting radio frequency signals into baseband signals; the baseband part 42 is mainly used for baseband processing and controlling the AN device. The receiving module 41 can also be called a receiver, a receiver, a receiving circuit, etc., and the sending module 43 can also be called a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The baseband part 42 is usually the control center of the AN device, and can also be called a processing module, which is used to execute the steps performed by the AN device in any of the above methods. For details, please refer to the description of the relevant parts above.

[0250] The baseband section 42 may include one or more boards, each of which may include one or more processors and one or more memories. The processors are used to read and execute programs stored in the memories to implement baseband processing functions and control AN devices. If multiple boards are present, the boards may be interconnected to increase processing power. As an alternative embodiment, multiple boards may share one or more processors, one or more memories, or one or more processors.

[0251] For example, the sending module 43 is used to perform the function of the reader in any of the above methods.

[0252] Please refer to Figure 9, which is a simplified structural diagram of a UE provided in an embodiment of the present application, as an implementation method of the second device in the present application.

[0253] For ease of understanding and illustration, in Figure 9, the UE takes a mobile phone as an example. As shown in Figure 9, the UE includes at least one processor, and may also include a radio frequency circuit, an antenna, and input and output devices. Among them, the processor can be used to process communication protocols and communication data, and can also be used to control the UE, execute software programs, process software program data, etc. The UE may also include a memory, which is mainly used to store software programs and data. These programs involved can be loaded into the memory when the communication device leaves the factory, or loaded into the memory later when needed. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves, and the antenna is the antenna provided in the embodiment of the present application. Input and output devices, such as a touch screen, a display screen, a keyboard, etc., are mainly used to receive data input by the user and output data to the user. It should be noted that some types of UE may not have input and output devices.

[0254] When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the UE, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, only one memory and processor are shown in Figure 9. In an actual UE product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and this is not limited in the embodiments of the present application.

[0255] In the embodiments of the present application, the antenna and radio frequency circuit with transceiver functions can be regarded as the receiving unit and transmitting unit of the UE (also collectively referred to as the transceiver unit), and the processor with processing function can be regarded as the processing unit of the UE. As shown in Figure 9, the UE includes a receiving module 31, a processing module 32, and a transmitting module 33. The receiving module 31 can also be referred to as a receiver, a receiver, a receiving circuit, etc., and the transmitting module 33 can also be referred to as a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The processing module 32 can also be referred to as a processor, a processing board, a processing device, etc.

[0256] For example, the processing module 32 is used to perform the functions of the reader in any of the above methods.

[0257] An embodiment of the present application provides a communication device, which includes at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that the method corresponding to each device or network element in any of the above methods is executed.

[0258] An embodiment of the present application provides a communication system, which includes a first device, a first device, a first network element, and a third network element.

[0259] An embodiment of the present application provides a communication system, which includes a first device, a first device, a first network element, a second network element, and a third network element.

[0260] An embodiment of the present application provides a communication system, which includes a first device, a first device, a first network element, a second network element, a third network element, a fourth network element and a fifth network element.

[0261] An embodiment of the present application provides a communication system, which includes a first device, a first device, a first network element, a second network element, a third network element, a fourth network element, a fifth network element, and other network elements such as a UPF.

[0262] An embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and when the computer instructions are executed, the computer executes any of the methods described above.

[0263] An embodiment of the present application provides a computer program product, which includes: computer program code, and when the computer program code is executed by a computer, causes the computer to execute any of the methods described above.

[0264] An embodiment of the present application provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory, so that a device where the chip is located implements any of the methods described above.

[0265] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. It should be noted that for the aforementioned method embodiments, in order to simplify the description, they are all expressed as a series of action combinations, but those skilled in the art should know that this application is not limited to the order of the actions described, because according to this application, some steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for this application.

[0266] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the above-mentioned units is only a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0267] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0268] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method comprises: The second device obtains a first message from the first device, where the first message is used to request to establish or modify a protocol data unit (PDU) session of the first device; The second device sends a second message to the first network element based on the first message, where the second message includes a first device identifier, and the second message is used to request modification or establishment of a protocol data unit (PDU) session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, and the first device identifier exists in the subscription information of the second device, and the subscription information also includes a device profile corresponding to the first device identifier, and the device profile is used to determine a quality of service (QoS) parameter of the PDU session; The second device receives a first feedback message from the first network element, where the first feedback message indicates that establishment or modification of a PDU session corresponding to the first device identifier is completed, and the PDU session meets the QoS parameters; The second device sends a second feedback message to the first device based on the first feedback message, where the second feedback message indicates that establishment or modification of the PDU session corresponding to the first device is completed.

2. The method according to claim 1, characterized in that The first message includes the first device identifier.

3. The method according to claim 1, characterized in that The first message includes device-related information of the first device, where the device-related information of the first device is used to uniquely identify the first device; Before the second device sends the second message to the first network element based on the first message, the method further includes: The second device determines the first device identifier based on the device-related information of the first device, wherein the second device stores a correspondence between one or more device identifiers and device-related information, including a correspondence between the first device identifier and the device-related information of the first device.

4. The method according to claim 2, characterized in that Before the second device obtains the first message from the first device, the method further includes: After the first device establishes a connection with the second device, the second device sends the first device identifier to the first device.

5. The method according to any one of claims 2 to 4, characterized in that: Before the second device obtains the first message from the first device, the method further includes: The second device receives and stores one or more device identifiers from the first network element; The second device assigns the first device identification among the one or more device identifications to the first device.

6. The method according to any one of claims 2 to 4, characterized in that: Before the second device obtains the first message from the first device, the method further includes: The second device sends a first request message to the first network element, where the first request message is used to request allocation of a device identifier for the first device; The second device receives a first response message, where the first response message includes the first device identifier; The second device determines, according to the first response message, to allocate the first device identifier to the first device.

7. A communication method, characterized in that: The method comprises: The first network element receives a second message sent by the second device, where the second message includes a first device identifier, and the second message is used to request modification or establishment of a protocol data unit (PDU) session corresponding to the first device identifier, wherein the first device identifier corresponds to the first device, the first device identifier exists in subscription information of the second device, the subscription information further includes a device profile corresponding to the first device identifier, and the device profile is used to determine a quality of service (QoS) parameter of the PDU session; The first network element sends a third request message to the second network element, requesting to establish an SM context for the PDU session corresponding to the first device identifier; The first network element receives a third feedback message from the second network element, where the third feedback message indicates that establishment of the SM context is completed; The first network element sends a first feedback message to the second device, where the first feedback message indicates that establishment or modification of a PDU session corresponding to the first device identifier is completed, and the PDU session meets QoS parameters determined by a device configuration file corresponding to the first device identifier.

8. The method according to claim 7, characterized in that Before the first network element receives the second message sent by the second device, the method further includes: The first network element receives a first request message from the second device, where the first request message is used to request allocation of a device identifier for the first device; The first network element sends a first response message to the second device, where the first response message includes the first device identifier.

9. The method according to claim 8, characterized in that Before the first network element sends the first response message to the second device, the method further includes: The first network element queries the subscription information of the second device from the third network element, and allocates the first device identifier to the first device according to the subscription information of the second device.

10. The method according to claim 9, characterized in that After the first network element allocates the first device identifier to the first device according to the subscription information of the second device, the method further includes: The first network element sends instruction information to the third network element, where the instruction information instructs the third network element to update the stored subscription information of the second device according to the first device identifier allocated to the first device.

11. The method according to claim 8, characterized in that Before the first network element sends the first response message to the second device, the method further includes: The first network element sends a second request message to the second network element based on the first request message, where the second request message is used to request allocation of a device identifier for the first device, and the second network element stores subscription information of the second device; The first network element receives a second response message from the second network element, where the second response message includes the first device identifier.

12. The method according to any one of claims 9 to 11, characterized in that: The contract information of the second device includes one or more device identifiers and whether the one or more device identifiers are allocated to the device.

13. The method according to claim 7, characterized in that Before the first network element receives the second message sent by the second device, the method further includes: The first network element receives one or more device identifiers included in the subscription information of the second device from the third network element, where the one or more device identifiers include the first device identifier.

14. A communication method, characterized in that: The method comprises: A first device sends a first message to a second device, where the first message is used to request establishment or modification of a protocol data unit (PDU) session of the first device, the first message including a first device identifier, the first device identifier being present in subscription information of the second device, the subscription information also including a device profile corresponding to the first device identifier, the device profile being used to determine a quality of service (QoS) parameter; The first device receives a second feedback message, where the second feedback message indicates that establishment or modification of a PDU session corresponding to the first device is completed.

15. The method according to claim 14, characterized in that The method further comprises: After the first device establishes a connection with the second device, the first device receives a first device identification from the second device.

16. A communication device, characterized in that: The method comprises a unit or module for implementing the method according to any one of claims 1 to 15.

17. A communication device, characterized in that: The communication device includes at least one processor and a memory; The memory is used to store computer programs or instructions; and the at least one processor is used to execute the computer programs or instructions in the memory, so that the method according to any one of claims 1 to 15 is executed.

18. A communication system, characterized in that: The communication system includes a first device, a second device, and a first network element; The second device is used to execute the method according to any one of claims 1 to 6, the first network element is used to execute the method according to any one of claims 7 to 13, and the first device is used to execute the method according to any one of claims 14 to 15.

19. A chip system, characterized in that: The chip system includes at least one processor, a memory and an interface circuit, the memory, the interface circuit and the at least one processor are interconnected by lines, and instructions are stored in the at least one memory; when the instructions are executed by the processor, the method described in any one of claims 1 to 15 is implemented.

20. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 1 to 15 is implemented.

21. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed, the method according to any one of claims 1 to 15 is implemented.

Images