Communication method and apparatus, and program product and storage medium

Abstract

A communication method and apparatus, and a program product and a storage medium. In the communication method, a terminal device can determine a device identifier of a first non-3GPP device on the basis of device description information of the first non-3GPP device and a first mapping relationship, wherein the first mapping relationship indicates a mapping relationship between one or more pieces of device description information and one or more device identifiers. A mechanism for determining a device identifier is provided, such that during communication, non-3GPP devices can be distinguished on the basis of device identifiers, thereby facilitating the provision of differentiated services for different non-3GPP devices.

Description

Communication method, apparatus, program product and storage medium

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese patent application No. 202411396162.1, filed on October 4, 2024, entitled “A communication method, apparatus, program product and storage medium”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a communication method, apparatus, program product and storage medium. BACKGROUND

[0004] Non-3rd generation partnership project (3 rd Generation Partnership Project, 3GPP) devices can connect to a 3GPP communication network (such as a 5th generation (5 th Generation, 5G) communication network) through terminal devices. The 3GPP communication network can determine different policies to control the quality of service (QoS) of non-3GPP devices, thereby providing differentiated services for different non-3GPP devices. However, there is no solution for the 3GPP communication network to identify different non-3GPP devices. SUMMARY

[0005] The present application provides a communication method, apparatus, program product and storage medium to identify non-3GPP devices.

[0006] In a first aspect, an embodiment of the present application provides a communication method. The method can be applied to a terminal device side or a 3GPP device side. In the following, the terminal device side can also be described as the 3GPP device side. The terminal device side can be the terminal device itself, or a module in the terminal device, or a logic module or software that can realize part or all of the functions of the terminal device. The module in the terminal device is, for example, a processor, a communication module, or a circuit or chip responsible for communication functions in the terminal device. The chip is, for example, a modem chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core, etc. For simplicity of description, the following describes the method as being applied to a terminal device. The method comprises: obtaining a first mapping relationship, the first mapping relationship indicating a mapping relationship between one or more device description information and one or more device identifiers; determining device description information of a first non-3GPP device; and determining a device identifier of the first non-3GPP device based on the first mapping relationship and the device description information of the first non-3GPP device.

[0007] The order of obtaining the first mapping relationship and determining the device description information of the first non-3GPP device by the terminal device can be arbitrary, and is not limited. The device description information can also be referred to as device-related information, and is used to describe the non-3GPP device. For example, the device description information of the first non-3GPP device indicates at least one of a device type, a device level, a quality of service level, an address or a host name of the first non-3GPP device, which can be described as at least one parameter indicated by the device description information. The first mapping relationship can also be referred to as a first association relationship, a first correspondence relationship, etc., and its name is not specifically limited. The device identifier of the first non-3GPP device can be used to temporarily identify the first non-3GPP device, and to distinguish the first non-3GPP device from other non-3GPP devices accessing the terminal device.

[0008] The embodiment of the present application provides a mechanism for the terminal device to determine the device identifier of the first non-3GPP device, so that the terminal device and a network (such as a 3GPP communication network) can identify the first non-3GPP device based on the device identifier of the first non-3GPP device, and provide services for the first non-3GPP device based on the same. In addition, the device identifier is determined based on the device description information of the first non-3GPP device, which can make the determined device identifier more suitable for the needs of the first non-3GPP device.

[0009] In a possible implementation, the one or more device description information includes device description information of the first non-3GPP device, the first mapping relationship indicates a mapping relationship between the device description information of the first non-3GPP device and the plurality of device identifiers, and the plurality of device identifiers includes a device identifier of the first non-3GPP device; and the method further includes: determining device description information of a second non-3GPP device, the device description information of the second non-3GPP device being same as the device description information of the first non-3GPP device; and determining, based on the first mapping relationship and the device description information of the second non-3GPP device, a device identifier of the second non-3GPP device, the device identifier of the second non-3GPP device being a device identifier of the plurality of device identifiers that is different from the device identifier of the first non-3GPP device.

[0010] In this way, even if the device description information of two non-3GPP devices is same, the device identifiers determined for the two non-3GPP devices are different, and device identifier collision of the two non-3GPP devices is avoided.

[0011] In a possible implementation, after the connection of the first non-3GPP device is disconnected, for example, after the connection of the first non-3GPP device with the terminal device is disconnected, the method further includes: determining device description information of a third non-3GPP device, wherein the device description information of the third non-3GPP device is same as the device description information of the first non-3GPP device; and determining, based on the first mapping relationship and the device description information of the third non-3GPP device, a device identifier of the third non-3GPP device, the device identifier of the third non-3GPP device being same as the device identifier of the first non-3GPP device.

[0012] In this way, the device identifiers of two non-3GPP devices that access the terminal device at different times can be same, and the utilization rate of the device identifiers can be improved while avoiding device identifier collision.

[0013] In a possible implementation, the first mapping relationship can be acquired from a first application network element or pre-stored in the terminal device, and no limitation is made in this regard. The application network element is, for example, an application function (application function, AF).

[0014] In this way, in the case where the first mapping relationship is acquired from the first application network element, the resources consumed by the terminal device for storing the first mapping relationship can be reduced. In the case where the first mapping relationship is pre-stored in the terminal device, the number of interactions between the terminal device and the first application network element can be reduced.

[0015] In a possible implementation, before the first mapping relationship is acquired from the first application function application network element, the method further includes: sending, to the first application network element, the device description information of the first non-3GPP device.

[0016] Therefore, the first mapping relationship is more targeted and accurate, and the terminal device can determine the device identifier of the first non-3GPP device based on the first mapping relationship.

[0017] In a possible implementation, the method further includes: sending a first message, the first message being used to request establishment or modification of a session, the session being used to carry data of the first non-3GPP device, and the first message including the device identifier of the first non-3GPP device. The session being used to carry data of the first non-3GPP device can also be described as the session being used to transmit data of the first non-3GPP device, the data of the first non-3GPP device being data sent by the first non-3GPP device, and / or the data sent by the first non-3GPP device.

[0018] Therefore, the network side can determine a session that is more suitable for the first non-3GPP device based on the device identifier of the first non-3GPP device, and provide more targeted services for the first non-3GPP device, thereby improving the user experience.

[0019] In a possible implementation, the device description information of the first non-3GPP device is determined by: obtaining a second mapping relationship, the second mapping relationship indicating a mapping relationship between a device parameter of the first non-3GPP device and the device description information of the first non-3GPP device; and determining the device description information of the first non-3GPP device based on the second mapping relationship and the device parameter of the first non-3GPP device. The content of the device parameter can be different from the parameter item indicated by the device description information. Alternatively, the content of the device parameter is the same as the parameter item indicated by the device description information, but the representation form of the device parameter is different from the representation form of the parameter item indicated by the device description information. In another possible implementation, the terminal device can also identify the device description information of the first non-3GPP device by itself, or obtain the device description information of the first non-3GPP device from the first non-3GPP device.

[0020] Therefore, some ways of determining the device description information of the first non-3GPP device by the terminal device are provided, and these ways do not involve complex processes, and are beneficial to improving the efficiency of determining the device description information by the terminal device.

[0021] In a possible implementation, the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameter of the first non-3GPP device is a device level of the first non-3GPP device. Optionally, the quality of service level is related to a quality of service parameter, and the quality of service parameter includes at least one of the following: a differentiated services code point, a quality of service indicator, an allocation retention priority, a guaranteed bit rate, or a maximum bit rate.

[0022] In this way, the terminal device does not need to perceive the quality of service level of the first non-3GPP device, the modification to the terminal device is reduced, and the implementation cost is reduced.

[0023] In a second aspect, an embodiment of the present application provides a communication method. The method can be applied to an application network element side. The application network element side can be the application network element itself, or a module in the application network element, or a logical module or software capable of realizing part or all functions of the application network element. The application network element can also be referred to as an application entity, an application device, or an application apparatus, and the like, and the name thereof is not specifically limited. The module in the application network element is, for example, a processor, a communication module, or a circuit or chip responsible for a communication function in the application network element. The application network element is, for example, an AF. For the purpose of simplifying the description, the method is taken as an example of being applied to the AF in the following description. The method comprises: sending, to a terminal device, information used for indicating a first mapping relationship, the first mapping relationship indicating a mapping relationship between one or more device description information and one or more device identifiers, and the first mapping relationship being used for determining a device identifier of a non-3GPP device accessing the terminal device.

[0024] In this way, the resources consumed by the terminal device for storing the first mapping relationship can be reduced, and the terminal device can quickly determine the device identifier of the non-3GPP device based on the first mapping relationship and the device description information of the non-3GPP device.

[0025] In a possible implementation, the method further comprises: receiving the one or more device description information; and determining the device identifier corresponding to each of the one or more device description information, so as to establish the first mapping relationship. The one or more device identifiers indicated by the first mapping relationship can be determined by the AF itself, or received from the terminal device, and the specific implementation is not limited.

[0026] In this way, a mechanism for the AF to create the first mapping relationship is provided, and the mechanism does not involve a complex calculation process, and the efficiency of determining the first mapping relationship can be improved.

[0027] In a possible implementation, the device description information indicates at least one of a device type, a device level, a quality of service level, an address, or a host name of the non-3GPP device. Optionally, the quality of service level is related to a quality of service parameter, and the quality of service parameter comprises at least one of a differentiated services code point, a quality of service indicator, an allocation retention priority, a guaranteed bit rate, or a maximum bit rate.

[0028] In a third aspect, an embodiment of the present application provides a communication method. The method can be applied to a terminal device side or also referred to as a 3GPP device side. The content of the terminal device side can refer to the content of the terminal device side discussed in the first aspect, which is not listed here. To simplify the description, the following is introduced by taking an example of the method applied to a terminal device. The method comprises: obtaining one or more rules, a traffic descriptor (TD) of each rule in the one or more rules indicating device description information, the device description information being common to a plurality of non-3GPP devices; determining, from the one or more rules, a first rule, the TD of the first rule indicating device description information matching device description information of a first non-3GPP device, the first rule being used for determination of a session, the session being used to carry data of the first non-3GPP device. The one or more rules are, for example, one or more user equipment route selection policy (URSP) rules. As the standard evolves, the rules can have other names, which are not specifically limited.

[0029] Optionally, the device description information of the first non-3GPP device indicates at least one of: a device type of the first non-3GPP device; a quality of service level corresponding to the first non-3GPP device; or, a device level of the first non-3GPP device.

[0030] In an embodiment of the present application, the TD in any rule indicates device description information common to a plurality of non-3GPP devices, rather than information specific to a certain non-3GPP device, which makes the rule applicable to a plurality of non-3GPP devices having the device description information, reduces the number of times of obtaining rules, and in the case of a non-3GPP device newly accessing a terminal device, if the non-3GPP device has a rule with device description information of the non-3GPP device as the TD, there is no need to trigger a rule updating process, reducing the number of times of updating rules, thereby reducing signaling overhead. In addition, the session used to carry data of the first non-3GPP device is determined based on the first rule of the first non-3GPP device, which realizes that the network side provides personalized services for the first non-3GPP device.

[0031] In a possible implementation, the method further comprises: determining a device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device and a sequence number, the sequence number being used to distinguish the first non-3GPP device from at least one non-3GPP device, the at least one non-3GPP device being connected to a same terminal device as the first non-3GPP device, and the device description information of the at least one non-3GPP device being the same as the device description information of the first non-3GPP device. Optionally, the sequence number can be assigned by the terminal device.

[0032] Thus, the device identity of the first non-3GPP device not only indicates the device identity information shared by the first non-3GPP device and other devices, but also indicates the serial number unique to the first non-3GPP device, so that the network side and the terminal device can determine the device description information shared by the first non-3GPP device and other devices based on the device identity of the first non-3GPP device, and can distinguish the first non-3GPP device from other non-3GPP devices.

[0033] In a possible implementation, the method further includes: sending a first message, the first message being used to request establishment or modification of a session, and the first message including the device identity of the first non-3GPP device.

[0034] Thus, the network side can determine a session more suitable for the first non-3GPP device based on the device identity of the first non-3GPP device, and can serve the first non-3GPP device more targetedly, thereby improving user experience.

[0035] In a possible implementation, the method further includes: obtaining a second mapping relationship, the second mapping relationship indicating a mapping relationship between the device parameter of the first non-3GPP device and the device description information of the first non-3GPP device; and determining the device description information of the first non-3GPP device based on the second mapping relationship and the device parameter of the first non-3GPP device.

[0036] Thus, a manner of determining the device description information of the first non-3GPP device is provided, and no complex process is involved, which is beneficial to improving the efficiency of determining the device description information.

[0037] In a possible implementation, the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameter of the first non-3GPP device is a device level of the first non-3GPP device.

[0038] Thus, the terminal device does not need to perceive the quality of service level of the first non-3GPP device, and the modification to the terminal device is reduced, and the implementation cost is reduced.

[0039] In a possible implementation, the quality of service level is related to a quality of service parameter, and the quality of service parameter includes at least one of the following: a differentiated services code point, a quality of service indicator, an allocation retention priority, a guaranteed bit rate, or a maximum bit rate.

[0040] In a possible implementation, the device description information of the first non-3GPP device is obtained from a second application network element; and the device description information of the first non-3GPP device is pre-stored device description information.

[0041] In a fourth aspect, an embodiment of the present application provides a communication method. The method can be applied to an application network element side. The content of the application network element side can refer to the content of the application network element side discussed in the second aspect above. To simplify the description, the following takes the method applied to the AF as an example for introduction. The method comprises: receiving a second message from a terminal device, the second message indicating device parameters of a first non-3GPP device; and sending a third message to the terminal device, the third message indicating a second mapping relationship, the second mapping relationship indicating a mapping relationship between the device parameters of the first non-3GPP device and device description information of the first non-3GPP device.

[0042] In a possible implementation, the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameters of the first non-3GPP device are device levels of the first non-3GPP device.

[0043] In a possible implementation, the method further comprises: sending a fourth message, the fourth message comprising the device description information of the first non-3GPP device, the fourth message being used for determining a first rule, the first rule being used for determining a session, the session being used for carrying data of the first non-3GPP device.

[0044] In a fifth aspect, an embodiment of the present application provides a communication method. The method can be applied to a policy control network element side. The policy control network element side can be the policy control network element side itself, or a module in the policy control network element side, or a logic module or software capable of realizing part or all functions of the policy control network element side. The policy control network element side can also be referred to as a policy control entity, a policy control device, or a policy control apparatus, and the like, and its name is not specifically limited. The module in the policy control network element is, for example, a processor, a communication module, or a circuit or chip responsible for a communication function in the policy control network element. The policy control network element is, for example, a policy control function (PCF). To simplify the description, the following takes the method applied to the PCF as an example for introduction. The method comprises: obtaining device description information, the device description information being common to a first non-3GPP device and at least one non-3GPP device; and sending a rule, the TD of the rule indicating the device description information, the rule being used for determining a session, the session being used for carrying data of the first non-3GPP device.

[0045] In a possible implementation, the method further includes: receiving a fifth message, the fifth message indicating to establish a session management policy of the first non-3GPP device, and the fifth message including device description information or a device identifier of the first non-3GPP device, the device identifier of the first non-3GPP device being related to the device description information of the first non-3GPP device; obtaining information of the first non-3GPP device based on the device description information or the device identifier of the first non-3GPP device, the information of the first non-3GPP device corresponding to the device description information of the first non-3GPP device; and determining the session management policy of the first non-3GPP device based on the information of the first non-3GPP device, the session management policy being used to manage a session.

[0046] In a possible implementation, the obtaining the information of the first non-3GPP device based on the device description information or the device identifier of the first non-3GPP device includes: sending a sixth message, the sixth message being used to request the information of the first non-3GPP device, and the sixth message including the device description information of the first non-3GPP device; and receiving the information of the first non-3GPP device. Optionally, in the case that the fifth message includes the device identifier of the first non-3GPP device, the PCF can determine the device description information of the first non-3GPP device based on the fifth message including the device identifier of the first non-3GPP device.

[0047] In a sixth aspect, an embodiment of the present application provides a communication method. The method can be applied to a unified data storage network element side. The unified data storage network element side can be the unified data storage network element itself, or a module in the unified data storage network element, or a logical module or software capable of realizing part or all functions of the unified data storage network element. The unified data storage network element can also be referred to as a unified data storage entity, a unified data storage device, or a unified data storage apparatus, and the like, and its name is not specifically limited. The module in the unified data storage network element is, for example, a processor, a communication module, or a circuit or chip responsible for a communication function in the unified data storage network element. The unified data storage network element is, for example, a unified data repository (UDR). For the purpose of simplifying the description, the method is taken as an example applied to the UDR in the following. The method includes: receiving a sixth message, the sixth message being used to request information of a first non-3GPP device, and the sixth message including device description information of the first non-3GPP device, the device description information being common to the first non-3GPP device and at least one non-3GPP device; and sending the information of the first non-3GPP device, the information of the first non-3GPP device corresponding to the device description information of the first non-3GPP device.

[0048] In a possible implementation, the method further includes: receiving a fourth message from the application network element, the fourth message including device description information of the first non-3GPP device; and determining information of the first non-3GPP device according to the fourth message. Optionally, the information of the first non-3GPP device can be used to determine the first rule and determine the session management policy, which means that the fourth message can be used to determine the first rule and the session management policy. The first rule is used for determining the session used to carry data of the first non-3GPP device. The session management policy is a policy related to the session, and the session management policy can be used to manage the session.

[0049] In a seventh aspect, an embodiment of the present application provides a communication apparatus. For example, the communication apparatus includes a processing unit (sometimes also referred to as a processing module), and a communication unit (sometimes also referred to as a communication module). The communication unit is configured to perform a transceiving operation, such as functions related to transmitting and receiving; the communication unit can be referred to as a transceiving unit; optionally, the communication unit includes a receiving unit and a transmitting unit. The processing unit is configured to perform a processing operation. Alternatively, the communication unit can be a transmitter and a receiver, or the communication unit is a transmitter and a receiver. Optionally, the communication apparatus further includes a storage unit (sometimes also referred to as a storage module).

[0050] In a first embodiment, the communication apparatus can be on the terminal device side in the first aspect, for example, can be a terminal device, or a module (for example, a chip system) configured in the terminal device. The communication apparatus includes means or modules for performing the corresponding operations in the first aspect or any possible implementation. For example, the processing unit is configured to obtain the first mapping relationship, determine the device description information of the first non-3GPP device, and determine the device identifier of the first non-3GPP device based on the first mapping relationship and the device description information of the first non-3GPP device.

[0051] The communication apparatus can also implement the content of any possible implementation of the first aspect, which will not be listed one by one here.

[0052] In a second embodiment, the communication apparatus can be on the application network element side in the second aspect, for example, can be an application network element, or a module (for example, a chip system) configured in the application network element. The communication apparatus includes means or modules for performing the corresponding operations in the second aspect or any possible implementation. For example, the communication unit is configured to send information indicating the first mapping relationship to the terminal device.

[0053] The communication apparatus can also implement the content of any possible implementation of the second aspect, which will not be listed one by one here.

[0054] The third embodiment can be a terminal device side of the third aspect, for example, a terminal device, or a module (e.g., a chip system) configured in the terminal device. The communication apparatus comprises means or modules for performing the third aspect or any possible implementation thereof. For example, a communication unit is configured to obtain one or more rules, and a processing unit is configured to determine the first rule.

[0055] The communication apparatus can also implement the content of any possible implementation of the third aspect, which will not be listed one by one here.

[0056] The fourth embodiment can be an application network element side of the fourth aspect, for example, an application network element, or a module (e.g., a chip system) configured in the application network element. The communication apparatus comprises means or modules for performing the fourth aspect or any possible implementation thereof. For example, a communication unit is configured to receive the second message and transmit the third message.

[0057] The communication apparatus can also implement the content of any possible implementation of the fourth aspect, which will not be listed one by one here.

[0058] The fifth embodiment can be a policy control network element side of the fifth aspect, for example, a policy control network element, or a module (e.g., a chip system) configured in the policy control network element. The communication apparatus comprises means or modules for performing the fifth aspect or any possible implementation thereof. For example, a communication unit is configured to obtain the device description information, and transmit the rule.

[0059] The communication apparatus can also implement the content of any possible implementation of the fifth aspect, which will not be listed one by one here.

[0060] The sixth embodiment can be a unified data storage network element side of the sixth aspect, for example, a unified data storage network element, or a module (e.g., a chip system) configured in the unified data storage network element. The communication apparatus comprises means or modules for performing the sixth aspect or any possible implementation thereof. For example, a communication unit is configured to receive the sixth message and transmit the information of the first non-3GPP device.

[0061] The communication apparatus can also implement the content of any possible implementation of the sixth aspect, which will not be listed one by one here.

[0062] In an eighth aspect, an embodiment of the present application provides a communication apparatus. The communication apparatus includes one or more processors. The one or more processors can execute computer programs or instructions in a memory, when the computer programs or instructions are executed, cause the communication apparatus to implement any possible method in the first aspect to the sixth aspect.

[0063] Optionally, the communication apparatus can include a memory, in which case the memory can be coupled with the one or more processors, or the memory can be disposed independently of the one or more processors. Alternatively, the memory exists independently of the communication apparatus.

[0064] In a possible design, the communication apparatus can further include an interface circuit, and the processor can be configured to communicate with other apparatuses or components through the interface circuit.

[0065] The communication apparatus can be a terminal device, a communication module in the terminal device, or a chip responsible for communication function in the terminal, such as a Modem chip (also referred to as a baseband chip) or a SoC or SIP chip including a modem module. Alternatively, the communication apparatus can be an access network device or a module in the access network device.

[0066] In a ninth aspect, an embodiment of the present application provides a communication apparatus. The communication apparatus includes a processor and an interface circuit. The interface circuit is configured to receive a signal from another communication apparatus outside the communication apparatus and transmit the signal to the processor, or send a signal from the processor to another communication apparatus outside the communication apparatus. The processor is configured to implement any possible method in the first aspect to the sixth aspect through a logic circuit or by executing code instructions. The number of processors can be one or more, which is not limited.

[0067] In a specific implementation process, the communication apparatus can be a chip, and the processor can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc. The specific implementation of the processor is not limited in the embodiments of the present application.

[0068] In an implementation, the communication apparatus can be a wireless communication device, i.e., a computer device supporting wireless communication function. Specifically, the wireless communication device can be a terminal device such as a smart phone, or a network device such as a wireless access network device (e.g., a base station).

[0069] In yet another implementation, the communication apparatus can be part of a device in a wireless communication system, such as an integrated circuit product including a system on chip (SoC) or a communication chip. The system on chip can also be referred to as SoC or SoC chip. The communication chip can include a baseband processing chip and a radio frequency processing chip. The baseband processing chip can also be referred to as a modem or baseband chip. The radio frequency processing chip can also be referred to as a radio frequency transceiver or radio frequency chip. In physical implementation, part or all of the chips in the communication chip can be integrated inside the SoC chip. For example, the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip. The interface circuit can be a radio frequency processing chip in the wireless communication device, and the processor can be a baseband processing chip in the wireless communication device. The interface circuit can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuitry on the chip or chip system. The processor can also be embodied as a processing circuit or logic circuit.

[0070] In yet another implementation, the communication apparatus can be a chip system, which can be composed of chips or can include chips and other discrete devices. The chip system can include, for example, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an SoC, a CPU, a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chip.

[0071] In a tenth aspect, an embodiment of the present application provides a communication system. The system includes a terminal device and an application network element. The terminal device can be the communication apparatus in the first embodiment of the seventh aspect, and the application network element can be the communication apparatus in the second embodiment of the seventh aspect.

[0072] In an eleventh aspect, an embodiment of the present application provides a communication system. The system includes a terminal device and a policy control network element. The terminal device can be the communication apparatus discussed in the third embodiment of the seventh aspect, and the policy control network element can be the communication apparatus discussed in the fifth embodiment of the seventh aspect. Optionally, the system further includes an application network element and / or a unified data storage network element. The application network element can be the communication apparatus discussed in the fourth embodiment of the seventh aspect, and the unified data storage network element can be the communication apparatus discussed in the sixth embodiment of the seventh aspect.

[0073] In a twelfth aspect, an embodiment of the present application provides a communication system. The system comprises a policy control network element and a unified data storage network element. The policy control network element can be the communication apparatus discussed in the fifth embodiment of the seventh aspect, and the unified data storage network element can be the communication apparatus discussed in the sixth embodiment of the seventh aspect. Optionally, the system further comprises an application network element, which can be the communication apparatus discussed in the fourth embodiment of the seventh aspect. Optionally, the system further comprises a terminal device, which can be the communication apparatus discussed in the third embodiment of the seventh aspect.

[0074] In a thirteenth aspect, an embodiment of the present application provides a chip system. The chip system comprises a processor. Optionally, the chip system further comprises an interface (such as a communication interface). The processor can be used to implement any of the methods discussed in the first aspect and possible implementation manners to the fourth aspect and possible implementation manners. Optionally, the chip system further comprises a memory. The memory is used to store a computer program (which can also be referred to as code or instruction). The processor is used to call and run the computer program from the memory, so that the device installed with the chip system executes any of the possible methods in the first aspect to the sixth aspect. The implementation manners of the chip system can refer to the content of the chip system involved in the foregoing, which will not be listed here.

[0075] In a fourteenth aspect, an embodiment of the present application provides a computer readable storage medium. The computer readable storage medium is used to store a computer program or instruction, which, when executed, implements any of the possible methods in the first aspect to the sixth aspect.

[0076] In a fifteenth aspect, an embodiment of the present application provides a computer program product. When the computer program product is executed, the processor executes any of the possible methods in the first aspect to the sixth aspect. The computer program product comprises a computer program and / or instruction, etc.

[0077] The beneficial effects of any of the technical solutions in the fourth aspect to the fifteenth aspect described above can refer to the beneficial effects of the corresponding technical solutions in the first aspect to the third aspect, which will not be listed here. BRIEF DESCRIPTION OF DRAWINGS

[0078] FIG. 1 is a schematic diagram of an architecture of a communication network to which embodiments of the present application are applicable;

[0079] FIG. 2 is a schematic diagram of an architecture of a fifth generation communication network to which embodiments of the present application are applicable;

[0080] FIGS. 3 to 5 are schematic diagrams of three communication methods provided by embodiments of the present application;

[0081] FIG. 6 is a schematic diagram of a flow of creating or modifying a session provided by an embodiment of the present application;

[0082] FIG. 7 and FIG. 8 are schematic diagrams of two communication methods provided by embodiments of the present application;

[0083] FIG. 9 to FIG. 11 are schematic diagrams of structures of three communication apparatuses provided by embodiments of the present application. DETAILED DESCRIPTION

[0084] Embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0085] The technical solutions provided by embodiments of the present application can be applied to various communication networks (which can also be referred to as networks or communication systems, etc.), such as a 3GPP communication network, for example, a 5th generation (5G) mobile communication network (such as a new radio (NR) network), a future communication network, a short-range wireless communication network (such as a side link, a wireless fidelity (Wi-Fi) network, a Bluetooth network, etc.), a long range radio (LoRa) communication network, a wired network, a vehicle to everything (V2X) communication network, a device-to-device (D2D) communication network, a satellite communication network, or a vehicle networking communication network, or a fusion network of at least two of the above communication networks, or other similar communication networks, etc., without limitation.

[0086] FIG. 1 is a schematic diagram of an architecture of a communication network to which embodiments of the present application are applicable. As shown in FIG. 1, a terminal device can access a core network through an access network device in an access network. For example, terminal device #1 and terminal device #2 can both access the core network through an access network (such as a network device). FIG. 1 illustrates two terminal devices, but the number of terminal devices is not limited in practice.

[0087] Optionally, one or more non-3rd generation partnership project (non-3GPP) devices can access a core network through a terminal device and an access network, such as connecting to a communication network through a terminal device subscribed to an operator network. The communication network includes an access network and a core network, and the like. The non-3GPP device can communicate with the terminal device through wireless or wired means, such as short distance communication between the non-3GPP device and the terminal device, such as Bluetooth communication, near-field communication (NFC), wireless fidelity (WIFI), or wireless local area network (WLAN), ultra-wideband (UWB), or near link, and the like.

[0088] As shown in FIG. 1, non-3GPP device #1, non-3GPP device #2, and non-3GPP device #3. Non-3GPP device #4, non-3GPP device #5, and non-3GPP device #6 access terminal device #2. One or more non-3GPP devices can access a terminal device, and the one or more non-3GPP devices can belong to the same type of device or belong to different types of devices, which is not specifically limited. The non-3GPP device accessing the terminal device or the terminal device accessing the 3GPP device mentioned in various embodiments of the present application can be understood as the terminal device establishing a connection with the non-3GPP device.

[0089] The access network can include at least one network device, which is a network-side device with wireless transceiving function. The network device can be located at the network side of the communication system and have a device or module with corresponding communication function. The network device is usually provided with a communication module, circuit, or chip for executing corresponding communication functions. The network device is also configured with program instructions for executing corresponding communication functions and corresponding program instructions. The network device can be a device in a radio access network (RAN) that provides wireless communication functions for terminal devices, referred to as a RAN device. The RAN can be an access network in a 3GPP communication network, such as a 4G, 5G, or future-oriented network. The RAN can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network of two or more of the above networks.

[0090] The RAN device can also be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future evolved mobile communication system, a base station in a future mobile communication system, an access node in a WiFi system, etc.

[0091] The RAN device can also be a module or unit that completes the functions of a base station part, for example, can be a central unit (CU), can also be a distributed unit (DU), and can also be a radio unit (RU). The CU here completes the functions of the radio resource control protocol and the packet data convergence layer protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or the entire physical layer. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of 3GPP. The CU and the DU can be separately arranged, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a radio frequency remote unit (RRU), an active antenna processing unit (AAU), or a remote radio head (RRH). In different systems, the CU, the DU, or the RU can also have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (ORAN) system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, and the RU can also be referred to as an O-RU. Any one of the CU (or CU-CP, CU-UP), the DU, and the RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. The RAN device can be a macro base station, or a micro base station or an indoor station, and can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technologies and specific device forms adopted by the network device.

[0092] In the embodiments of the present application, the functions of the network device can also be performed by a module (such as a chip) in the network device, or by a control subsystem containing the functions of the network device. The control subsystem containing the functions of the network device herein can be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation, smart city, etc.

[0093] A terminal device is a user-side device with wireless transceiving function. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely applied in various scenarios, such as device-to-device (D2D) communication, vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal device can be a mobile phone, tablet computer, computer with wireless transceiving function, wearable device, vehicle, unmanned aerial vehicle, helicopter, airplane, ship, robot, mechanical arm, smart home device, etc. The terminal device is usually provided with a communication module, circuit or chip for performing corresponding communication functions, and is also configured with program instructions for performing corresponding communication functions. In the embodiments of the present application, the device for realizing the functions of the terminal device can be the terminal device, or a device capable of supporting the terminal device to realize the functions, such as a chip system or a combination device or component capable of realizing the functions of the terminal device, which can be installed in the terminal device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0094] In the embodiments of the present application, the functions of the terminal device can also be performed by a module (such as a chip or modem) in the terminal device, or by a device containing the functions of the terminal device.

[0095] The network device and the terminal device can be fixed in position or movable. The network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed on airplanes, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the network device and the terminal device.

[0096] The roles of the network device and the terminal device can be relative, for example, a helicopter or a drone can be configured as a mobile network device, and for those terminal devices that access the wireless access network, the terminal device is the network device. Therefore, the network device and the terminal device can be collectively referred to as a communication apparatus, the terminal device can be referred to as a communication apparatus with network device function, and the network device can be referred to as a communication apparatus with terminal device function.

[0097] The non-3GPP device refers to a device using a technology standard or protocol not defined by 3GPP, such as Bluetooth, wireless local area network, etc., for data transmission, or refers to a device that does not support direct access to a communication network through an access network, or refers to a device that does not support a technology standard or protocol defined by 3GPP (3rd generation partnership project, 3GPP) or does not support a technology standard or protocol defined by 3GPP in the future. The non-3GPP device does not support the technology standard or protocol defined by 3GPP, which may be due to the software or hardware limitations of the non-3GPP device, and the non-3GPP device does not have the ability to support the technology standard or protocol defined by 3GPP. Alternatively, the non-3GPP device itself may have the ability to support the technology standard or protocol defined by 3GPP, but due to the limitation of the communication environment or the limitation of the working mode, the non-3GPP device cannot use its ability to support the technology standard or protocol defined by 3GPP. With respect to the non-3GPP device, the terminal device mentioned in the embodiments of the present application can be referred to as or belong to the 3GPP device, that is, the terminal device provided in the embodiments of the present application can be a device capable of using the technology standard or protocol defined by 3GPP for data transmission, or the terminal device can directly access the communication network through the access network, has the ability to support the technology standard or protocol defined by 3GPP and can use the ability.

[0098] The non-3GPP device may, for example, be various internet of things (internet of things, IoT) devices, such as tablets, smart televisions, fitness trackers, wearable devices, smart home devices (such as smart refrigerators, washing machines), cameras, video cameras, cars, traffic lights, airplane engines, printers, and home security systems, etc. Wearable devices such as smart watches, earphones, various smart glasses, such as virtual reality (virtual reality, VR) glasses, augmented reality (augmented reality, AR) glasses, mixed reality (mixed reality, MR) glasses, extended reality (extended reality, ER) glasses, etc.

[0099] The following takes the network device and the core network in FIG. 1 as an example, which belongs to a 5G communication network, and introduces by example in combination with the architecture of a 5G communication network shown in FIG. 2. FIG. 2 shows a terminal device, a (R)AN, some network elements, and a DN. The network elements are, for example, core network elements in a core network, which can also be referred to as core network entities, core network devices, or core network apparatuses, etc.

[0100] The core network elements include, for example, a network capability exposure network element (such as a network exposure function (NEF)), a policy control network element (such as a policy control function (PCF)), a unified data storage network element (such as a UDR), an application network element (such as an AF), a mobility management network element (such as an access and mobility management function (AMF)), and a session management network element (such as a session management function (SMF)), etc. The AF can be an AF deployed by an operator network itself, or a third-party AF, which is not limited.

[0101] Optionally, the core network elements further include a network slice selection network element (such as a network slice selection function (NSSF)), a unified data management network element (such as a unified data management function (UDM)), a network repository network element (such as a network repository function (NRF)), a network slice-specific authentication and authorization network element (such as a network slice-specific authentication and authorization function (NSSAAF)), an authentication service network element (such as an authentication server function (AUSF)), a service communication proxy network element (such as a service communication proxy (SCP)), a network slice admission control network element (such as a network slice admission control function (NSACF)), and a user plane function network element (such as a user plane function (UPF)), etc. The following takes the network elements in the 5G communication network shown in FIG. 2 as an example to introduce the basic functions of the above-mentioned core network elements.

[0102] NEF, which is responsible for managing the opening of network data to the outside. For example, converting information received from the AF into information sent to internal core network elements, and vice versa; securely opening network capabilities and events provided by the core network elements to the AF, etc.

[0103] PCF, which mainly provides terminal device access and mobility related policy control, session management related policy control, etc.

[0104] UDR, which is used to support the storage and retrieval of user data and the like by other different network elements, including subscription data, policy data, structured data, or application data, etc.

[0105] AF, which is a server end that provides a certain type of service for users, and can also be called an application server or a service server.

[0106] AMF, which is responsible for providing mobility management, lawful monitoring, or access authorization and authentication, etc.

[0107] SMF, which is used to implement session and bearer management, address allocation, etc.

[0108] Each of the above network elements can provide corresponding services through a service interface. The terminal device and the AMF can communicate through the N1 interface, and the (R)AN and the AMF can communicate through the N2 interface. The (R)AN and the UPF can communicate through the N3 interface. The SMF and the UPF can communicate through the N4 interface. The UPF and the DN can communicate through the N6 interface. The UPFs can communicate through the N9 interface.

[0109] The above Figure 2 is an example of a 5G communication system architecture, and the communication system can further include more network elements, which are not limited. In addition, with the continuous evolution of standards, the functions or names of the above network elements can change, and more network elements can also appear, which are not specifically limited.

[0110] The network architecture and service scenarios described in the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0111] With the rapid development of mobile communication technology, a communication system can meet the needs of different users in low latency, large bandwidth, and high reliable communication through customized services. Network service customization can not only be used for 3GPP devices such as 3GPP terminal devices signed by operators, but also be used for non-3GPP devices connected to a communication network (such as a wireless mobile communication network, specifically a 5G communication network) through a terminal device. For example, a non-3GPP device is connected to a terminal device through a wireless local area network hotspot, and then connected to a communication network through the terminal device. In this case, the communication network can provide special network access and services, quality of service (QoS) management and control, and the like for these devices according to different non-3GPP device requirements, which is a typical application scenario of communication networks in vertical industries. Different non-3GPP devices may have different requirements. For example, smart home devices require small traffic, while XR glasses require high real-time performance and more traffic. In order to support service differentiation of non-3GPP devices, it is necessary to solve how the 5G communication system identifies non-3GPP devices connected to the terminal device.

[0112] Therefore, embodiments of the present application provide a communication scheme. In the communication scheme, the terminal device can determine the device identifier of the non-3GPP device based on the device description information of the non-3GPP device and the first mapping relationship between one or more device description information and one or more device identifiers. In this way, the terminal device and the network side (an access network device in the access network and / or a core network element, etc.) can distinguish the non-3GPP device based on the device identifier, thereby facilitating the network to provide differentiated services for different non-3GPP devices. The terminal device can determine the device identifier corresponding to the device description information of the non-3GPP device based on the first mapping relationship, and the efficiency of determining the device identifier is high.

[0113] The communication method provided by each of the embodiments of the present application is described below with reference to the accompanying drawings. In the corresponding drawings of each of the embodiments of the present application, the steps indicated by dashed lines are optional steps. The terminal device involved in each of the embodiments of the present application may be, for example, the terminal device #1 or the terminal device #2 shown in FIG. 1, or the UE involved in FIG. 2. The access network device involved in each of the embodiments of the present application may be, for example, the network device involved in FIG. 1, or the (R)AN involved in FIG. 2, or a module or component in the RAN device, such as a CU, a DU, a RU, an O-CU, an O-DU, etc. The first non-3GPP device, the second non-3GPP device, or the third non-3GPP device involved in each of the embodiments of the present application may be, for example, any of the non-3GPP devices involved in FIG. 1. The application network element or the AF (such as the first AF, the second AF, etc.) involved in each of the embodiments of the present application may be, for example, the application network element or the AF involved in FIG. 2. The policy control network element or the PCF involved in each of the embodiments of the present application may be, for example, the PCF involved in FIG. 2. The unified data storage network element or the UDR involved in each of the embodiments of the present application may be, for example, the unified data storage network element or the UDR involved in FIG. 2. The network exposure network element or the NEF involved in each of the embodiments of the present application may be, for example, the network exposure network element or the NEF involved in FIG. 2. As the standards evolve, the names and / or functions of devices or network elements may change, which is not limited.

[0114] The communication method is described below with reference to the flowchart shown in FIG. 3. Each of the steps involved in FIG. 3 is described below.

[0115] In S301, the terminal device obtains the first mapping relationship. This can also be described as the terminal device determining the first mapping relationship.

[0116] The first mapping relationship can also be referred to as a first association relationship, a first correspondence relationship, or a first relationship, etc., without limitation on its name. The form of the first mapping relationship can be a function, a graph, a table, a bit map, a bit sequence, etc., without limitation on its form. The first mapping relationship indicates a mapping relationship (or an association relationship, or a correspondence relationship, etc.) between one or more device description information and one or more device identifications (device IDs). In the embodiments of the present application, one or more device description information includes the device description information of the first non-3GPP device as an example. The device description information can also be referred to as device-related information, which is used to describe the device. The device identification is used to identify the device. The device description information indicates at least one parameter item in A1 to A4 below. Or, the device description information includes information of at least one parameter item in A1 to A4 below.

[0117] A1, attribute of the device. The attribute is a stable characteristic of the device. The attribute indicates at least one of, for example, a device type, a device address, or a host name of the device.

[0118] The device type indicates a category to which the device belongs. For example, the device type indicates a primary category (or a large category) to which the device belongs. For example, the primary category is a result of classification based on whether the device can be worn, and the primary category indicates, for example, whether the device belongs to a non-wearable device or a wearable device. Alternatively, the device type indicates a secondary category (or a small category) to which the device belongs. For example, the secondary category is a result of further classification of devices belonging to a certain primary category, and the secondary category indicates, for example, whether the wearable device is an XR glass or a VR glass. Of course, the device type can be classified in various manners, and the classification manner is not limited. The device address is, for example, a media access control address (MAC) or an internet protocol (IP) address of the device.

[0119] A2, service parameter of the device. The service parameter includes, for example, a device level of the device and / or a quality of service (QoS) level of the device.

[0120] The device level is related to a service corresponding to the device, such as a user identifier architecture (UIA) service. The device level includes, for example, a diamond level, a gold level, a silver level, and the like. The QoS level indicates a QoS requirement of the device. Optionally, the QoS level is a granularity of an application corresponding to a non-3GPP device, and in this case, the non-3GPP device can have different QoS levels corresponding to different applications. Alternatively, the QoS level is a granularity of a non-3GPP device, and in this case, the non-3GPP device has one QoS level.

[0121] QoS levels are associated with at least one of the following: Differentiated Services Code Point (DSCP), Quality of Service Indicator (QoS), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR), or Maximum Bit Rate (MBR). DSCP is used to differentiate service categories and service priorities. A QoS Indicator is, for example, the 5G QoS Identifier (5QI). 5QI indicates latency, throughput, packet loss rate, and jitter, among other things. ARP refers to the allocation and retention priority. Guaranteed Bit Rate refers to the bit rate that the bearer can guarantee to provide. Maximum Bit Rate refers to the maximum bit rate that the bearer can provide, which can be used to limit the data transmission rate of a service.

[0122] For example, higher DSCP, ARP, GBR, or MBR values ​​indicate higher data transmission priority for the device, resulting in a higher QoS level or service quality requirement. Conversely, lower DSCP, ARP, GBR, or MBR values ​​indicate lower data priority, resulting in a lower QoS level or service quality requirement.

[0123] For example, a higher packet loss rate, latency, or jitter indicates a lower priority for data transmission by the device, resulting in a lower QoS level or lower quality of service requirements. Conversely, a lower packet loss rate, latency, or jitter indicates a higher priority for data transmission by the device, resulting in a higher QoS level or higher quality of service requirements. For instance, lower throughput indicates a lower priority for data transmission by the device, resulting in a lower QoS level or lower quality of service requirements. Conversely, higher throughput indicates a higher priority for data transmission by the device, resulting in a higher QoS level or higher quality of service requirements.

[0124] A3. Device status. Status includes, for example, whether the device is online or offline. The online status can be further divided into busy or idle states.

[0125] A4. Equipment operating parameters. Operating parameters include equipment temperature, humidity, etc.

[0126] Optionally, the device description information indicates at least one parameter item of the device, such as a device type, a quality of service level, a device level, an address, or a host name. This can be described as the device description information indicating at least one of information of a device type, information of a quality of service level, information of a device level, information of an address, or information of a host name. The information of the device type is, for example, an index (or identifier or value or number, etc.) of the device type. The information of the quality of service level is, for example, a value of the quality of service level. The information of the device level is, for example, a value of the device level. The information of the address is, for example, a value of an IP address or a value of a MAC address, etc. The information of the host name is, for example, a value of the host name or a value of the host address. The address of the host includes, for example, an IP address, a MAC address, or a domain name address, etc.

[0127] The following is an example of the content of the first mapping relationship. For example, the first mapping relationship includes a mapping relationship between one or more device description information and one or more device identifiers, or a mapping relationship between an index of one or more device description information and one or more device identifiers, or a mapping relationship between part or all of the parameter items indicated by one or more device description information and one or more device identifiers. The embodiments of the present application do not limit the content of the first mapping relationship.

[0128] The following is an example of an index of one device description information in the index of one or more device description information.

[0129] The index of one device description information can be an identifier, a serial number, or a number, etc. allocated to one device description information. Alternatively, the index of one device description information can be a value of a parameter item indicated by one device description information. For example, the device description information indicates that the quality of service level of the device is 3, and the index of the device description information can be 3.

[0130] Alternatively, the index of one device description information can be a value range to which a value of part or all of the parameter items indicated by one device description information belongs. For example, the device description information indicates a device level and a device type, the device level is 2, and the device type is 1, and the index of the device description information is, for example, 1-3.

[0131] Alternatively, the index of one device description information can be an index corresponding to a value range to which a value of part or all of the parameter items indicated by one device description information belongs. The index of one device description information can also have various implementation manners, which are not limited herein.

[0132] The following is an example of the relationship between one or more device description information and one or more device identifiers indicated by the first mapping relationship.

[0133] B1, the first mapping relationship indicates that one or more device description information and one or more device identifiers can be a one-to-one correspondence, for example, each device description information in the one or more device description information indicated by the first mapping relationship is associated with one device identifier in the one or more device identifiers.

[0134] Please refer to Table 1 below for an example of a first mapping relationship provided by an embodiment of the present application. In Table 1, the first mapping relationship includes the mapping relationship between the index of one or more device description information and one or more device identifiers, and the device description information indicates the device type.

[0135] Table 1

[0136] In Table 1, "00", "01", "10" and "11" respectively represent the device type as XR glasses, smart TV, camera and tablet computer, and the device identifiers corresponding to the XR glasses, smart TV, camera and tablet computer are 111, 110, 100 and 001 respectively.

[0137] B2, the first mapping relationship indicates that one or more device description information and one or more device identifiers can be a one-to-many relationship, for example, each device description information in the one or more device description information indicated by the first mapping relationship is associated with multiple device identifiers.

[0138] Please refer to Table 2 below for an example of a first mapping relationship provided by an embodiment of the present application. In Table 2, the first mapping relationship includes the mapping relationship between the index of one or more device description information and one or more device identifiers, and the device description information indicates the device type and the quality of service level.

[0139] Table 2

[0140] In Table 2, "00", "11" respectively represent the device type as XR glasses and camera, and "1", "3" respectively represent the quality of service level of the device as 1 and 3. As shown in Table 2, the device identifier corresponding to the XR glasses with the quality of service level of 1 is 000 or 001, and the device identifier corresponding to the camera with the quality of service level of 3 is 011 or 111.

[0141] B3, the first mapping relationship indicates that one or more device description information and one or more device identifiers include both a one-to-one correspondence and a one-to-many relationship, for example, part of the device description information in the one or more device description information indicated by the first mapping relationship respectively corresponds to multiple device identifiers, and another part of the device description information respectively corresponds to one device identifier.

[0142] Please refer to Table 3 below for an example of a first mapping relationship provided by the embodiments of the present application. Table 3 is an example of a mapping relationship between an index of one or more device description information and one or more device identifiers in the first mapping relationship, and device description information indicating device type and quality of service level.

[0143] Table 3

[0144] “00”, “11” in Table 3 respectively represent device type as XR glasses, camera, and “1”, “3” respectively represent quality of service level of the device as 1, 3. As shown in Table 3, the device identifier corresponding to the quality of service level of 1 and the device type of XR glasses is 000 or 001, and the device identifier corresponding to the quality of service level of 3 and the device type of camera is 111.

[0145] The way for the terminal device to obtain the first mapping relationship will be introduced below in combination with the way shown in C1 or C2.

[0146] C1, the terminal device obtains the first mapping relationship from a first application network element (such as AF).

[0147] For example, the first application network element can be pre-configured or pre-defined with the first mapping relationship, such as pre-defined with the first mapping relationship through a protocol, or can generate (or establish) the first mapping relationship by itself. The first application network element sends the first mapping relationship to the terminal device, which is equivalent to the terminal device obtaining the first mapping relationship from the first application network element.

[0148] The first application network element can obtain one or more device description information, determine the device identifier corresponding to each of the one or more device description information, and generate the first mapping relationship.

[0149] The first application network element can obtain the one or more device description information from the terminal device. For example, the terminal device can send the non-3GPP device description information to the first application network element when sending a UIA service subscription request to the first application network element. The UIA service subscription request is used to request to subscribe the non-3GPP device accessing the terminal device to the UIA service. Alternatively, the device description information of the non-3GPP device is directly carried (or carried) in the UIA service subscription request. Alternatively, the first application network element can obtain the device description information from one or more devices (such as one or more non-3GPP devices) to obtain the one or more device description information.

[0150] The first application network element can respectively assign a device identifier to the one or more device description information to generate the first mapping relationship. For example, the first application network element can process one device description information according to a first algorithm to obtain a device identifier corresponding to the device description information, and the first algorithm can be a hash algorithm. For another example, the first application network element can directly assign different device identifiers to the one or more device description information, and the manner of assigning the device identifiers to the first application network element is not limited.

[0151] Alternatively, the first application network element can also obtain one or more device identifiers and one or more device description information from the terminal device, and the first application network element maps the one or more device description information to the one or more device identifiers to generate the first mapping relationship.

[0152] Optionally, the first application network element can carry information indicating the first mapping relationship in a UIA service subscription response. The UIA service subscription response is used to respond to a UIA service subscription request and is used to indicate that the terminal device successfully subscribes to the UIA service.

[0153] In this case, optionally, the first application network element can also store the information of the first non-3GPP device into the UDR. The information of the first non-3GPP device includes, for example, a data network name (DNN) and / or single network slice selection assistance information (S-NSSAI) corresponding to the first non-3GPP device. The information of the first non-3GPP device corresponds to, for example, the device identifier of the first non-3GPP device, such as the data sub-key (or sub-key) of the information of the first non-3GPP device being the device identifier of the first non-3GPP device, and the data key (or key) of the information of the first non-3GPP device being the identifier of the terminal device. The identifier of the terminal device is, for example, a subscription permanent identifier (SUPI) of the terminal device. Both the data key and the data sub-key are used to find the data (or information) stored in the UDR. For example, a network element (such as a policy control network element or a unified data storage network element) can first find all data corresponding to the terminal device based on the data key, and then find the information of the first non-3GPP device from all the data corresponding to the terminal device based on the data sub-key. The data key and the data sub-key can improve the efficiency of the network element in finding data.

[0154] C2, the terminal device pre-stores the first mapping relationship. For example, the terminal device locally stores the first mapping relationship.

[0155] Exemplarily, the terminal device can be pre-configured or pre-defined with the first mapping relationship, such as pre-defined with the first mapping relationship through a protocol, or can generate (or establish) the first mapping relationship by itself. In this case, optionally, in order for the first application network element to synchronously perceive, the terminal device can further send information for indicating the first mapping relationship to the first application network element, which is equivalent to registering the first mapping relationship in the first application network element.

[0156] The above C1 or C2 is an example of the manner in which the terminal device obtains the first mapping relationship, and does not actually limit the manner in which the terminal device obtains the first mapping relationship.

[0157] S302, the terminal device determines the device description information of the first non-3GPP device. This can also be described as the terminal device obtaining the device description information of the first non-3GPP device.

[0158] The device description information of the first non-3GPP device can refer to the device description information discussed above, which is not listed here. For example, the device description information of the first non-3GPP device indicates at least one of the attributes, service parameters, states or working parameters of the first non-3GPP device, such as at least one of the device type, quality of service level, device level, address and host name of the first non-3GPP device.

[0159] The content of the terminal device determining the device description information of the first non-3GPP device will be introduced below in combination with the manner shown in D1, D2, D3 or D4.

[0160] D1, the terminal device identifies the device description information of the first non-3GPP device.

[0161] Exemplarily, the terminal device identifies the device description information of the first non-3GPP device in the process of establishing a connection with the first non-3GPP device, or after the terminal device can establish a connection with the first non-3GPP device.

[0162] For example, taking the device description information of the first non-3GPP device indicating the device type of the first non-3GPP device as an example, if the terminal device and the first non-3GPP device are products of the same manufacturer, then the terminal device can identify the device type of the first non-3GPP device after establishing a connection with the first non-3GPP device, and thus obtain the device description information of the first non-3GPP device.

[0163] D2, the terminal device obtains the device description information of the first non-3GPP device from the second application network element. The second application network element can be the same application network element as the first application network element, or can be a different application network element, which is not limited.

[0164] Exemplarily, the terminal device can identify the device parameter of the first non-3GPP device, or pre-store the device parameter of the first non-3GPP device. The implementation content of the device parameter can also refer to the implementation content of the parameter item indicated by the device description information, which is not listed here. The content of the device parameter is different from the content of the parameter item indicated by the device description information, for example, the device parameter is the address or the device level of the first non-3GPP device, and the device description information is the quality of service level of the first non-3GPP device. Or, the content of the device parameter is the same as the content of the parameter item indicated by the device description information, but the representation form of the device parameter is different from the representation form of the parameter item indicated by the device description information, for example, the device parameter is a floating-point device type, and the device description information indicates an integer device type.

[0165] The terminal device obtains a second mapping relationship from the second application network element. The second mapping relationship indicates the mapping relationship between the device parameter of the first non-3GPP device and the device description information of the first non-3GPP device. In this way, the terminal device can determine the device description information of the first non-3GPP device based on the second mapping relationship and the device parameter of the first non-3GPP device.

[0166] Please refer to Table 4 below for an example of a second mapping relationship provided by an embodiment of the present application. In Table 4, the device parameter is taken as the device level, and the device description information is taken as the quality of service level for example.

[0167] Table 4

[0168] As shown in Table 4, if the device parameter of the first non-3GPP device is the diamond level, the terminal device can determine the quality of service level of the first non-3GPP device as 3 based on Table 4 to obtain the device description information of the first non-3GPP device. If the device parameter of the first non-3GPP device is the gold medal level, the terminal device can determine the quality of service level of the first non-3GPP device as 2 based on Table 4 to obtain the device description information of the first non-3GPP device. If the device parameter of the first non-3GPP device is the silver medal level, the terminal device can determine the quality of service level of the first non-3GPP device as 1 based on Table 4 to obtain the device description information of the first non-3GPP device.

[0169] D3, the terminal device obtains the device description information of the first non-3GPP device from the first non-3GPP device.

[0170] Exemplarily, the terminal device can obtain the device description information of the first non-3GPP device in the process of establishing a connection with the first non-3GPP device. Or, the terminal device can obtain the device description information of the first non-3GPP device from the first non-3GPP device after establishing a connection with the first non-3GPP device.

[0171] D4, the terminal device cooperates with at least two of the above D1 to D3 to obtain the device description information of the first non-3GPP device. For example, the terminal device identifies part of the information in the device description information of the first non-3GPP device, and obtains another part of the information of the first non-3GPP device from the second application network element.

[0172] For example, the device description information of the first non-3GPP device indicates the address and the device type of the first non-3GPP device. The terminal device identifies the address of the first non-3GPP device, and obtains the device type of the first non-3GPP device from the second application network element, thereby obtaining the device description information of the first non-3GPP device.

[0173] The execution order of S301 and S302 can be arbitrary, such as executing S301 first and then executing S302, or executing S302 first and then executing S301, or executing S301 and S302 synchronously, and no specific limitation is made to this.

[0174] S303, the terminal device determines the device identifier of the first non-3GPP device according to the device description information of the first non-3GPP device and the first mapping relationship.

[0175] After the terminal device determines the device description information of the first non-3GPP device, it can determine the device identifier corresponding to the device description information matching the device description information of the first non-3GPP device from the first mapping relationship, which is the device identifier of the first non-3GPP device. If the first mapping relationship associates multiple device identifiers with the device description information of the first non-3GPP device, the terminal device can determine the unoccupied device identifier in the multiple device identifiers as the device identifier of the first non-3GPP device. The unoccupied device identifier means that the non-3GPP device currently accessing the terminal device does not use the device identifier, and the non-3GPP device currently accessing the terminal device can also be understood as the non-3GPP device currently connected to the terminal device.

[0176] Taking the first mapping relationship shown in Table 2 as an example, if the device type indicated by the device description information of the first non-3GPP device is an XR glasses, and the quality of service level of the first non-3GPP device is 1, the terminal device can determine the device identifier of the first non-3GPP device as 000 or 001 according to the first mapping relationship shown in Table 2.

[0177] Optionally, the terminal device determines different device identities for the different two non-3GPP devices accessing the terminal device. Optionally, the two non-3GPP devices can have a connection relationship with the terminal device at the same time. This can be understood as the time of the two non-3GPP devices accessing the terminal device overlapping. For example, one non-3GPP device is in a connection state with the terminal device from 10:00 to 12:00 on September 30, 2024, and the other non-3GPP device is in a connection state with the terminal device from 10:00 to 11:00 on September 30, 2024, so it can be considered that the two non-3GPP devices have a connection relationship with the terminal device at the same time.

[0178] For example, the first non-3GPP device and the second non-3GPP device are both devices accessing the terminal device, and the terminal device can determine the device description information of the second non-3GPP device. The content of determining the device description information of the second non-3GPP device can refer to the content of determining the device description information of the first non-3GPP device discussed above, which will not be listed here.

[0179] If the device description information of the first non-3GPP device is the same as the device description information of the second non-3GPP device, the terminal device can determine the device identity of the second non-3GPP device. The device identity of the second non-3GPP device is a device identity different from the device identity of the first non-3GPP device in the plurality of device identities, and the plurality of device identities are the device identities corresponding to the device description information of the second non-3GPP device in the first mapping relationship. In this way, it is equivalent to excluding the occupied device identity, avoiding the device identity conflict of the two non-3GPP devices having a connection relationship with the terminal device at the same time.

[0180] Taking the first mapping relationship shown in Table 3 as an example, if the device description information of the first non-3GPP device and the device description information of the second non-3GPP device both indicate that the device type is an XR glasses, and the quality of service level is 1, the terminal device can determine the device identity of the first non-3GPP device as 000 and the device identity of the second non-3GPP device as 001 according to the first mapping relationship shown in Table 3. Alternatively, the terminal device determines the device identity of the first non-3GPP device as 001 and the device identity of the second non-3GPP device as 000.

[0181] Optionally, the terminal device can determine one same device identifier for the two non-3GPP devices which do not exist in the connection relationship with the terminal device at the same time. The two non-3GPP devices which do not exist in the connection relationship with the terminal device at the same time can be understood as the time period of the two non-3GPP devices accessing the terminal device does not overlap. For example, one non-3GPP device is in the connection state with the terminal device from 10:00 to 12:00 on September 30, 2024, and another non-3GPP device is in the connection state with the terminal device from 13:00 to 14:00 on September 30, 2024, which can be regarded as the two non-3GPP devices do not exist in the connection relationship with the terminal device at the same time.

[0182] For example, after the connection between the first non-3GPP device and the terminal device is disconnected, the terminal device determines the device description information of the third non-3GPP device. The content of determining the device description information of the third non-3GPP device can refer to the content of determining the device description information of the first non-3GPP device discussed above, which will not be listed here. If the device description information of the third non-3GPP device is the same as the device description information of the first non-3GPP device, the terminal device can determine the device identifier of the third non-3GPP device based on the first mapping relationship and the device description information of the third non-3GPP device. The device identifier of the third non-3GPP device is the same as the device identifier of the first non-3GPP device. In this way, in the case of avoiding device identifier conflict, some device identifiers can also be reused, thereby ensuring the utilization rate of device identifiers.

[0183] For example, if the device description information of the first non-3GPP device and the device description information of the third non-3GPP device both indicate that the device type is an XR glasses and the quality of service level is 1, the terminal device can determine the device identifier of the first non-3GPP device as 000 according to the first mapping relationship shown in Table 3. After the connection between the terminal device and the first non-3GPP device is disconnected, the terminal device can determine the device identifier of the third non-3GPP device as 000.

[0184] Optionally, the device identifiers of non-3GPP devices accessing different terminal devices can be the same or different, which is not limited specifically. For example, the device identifier of non-3GPP device #1 accessing terminal device #1 can be 1111, and the device identifier of non-3GPP device #2 accessing terminal device #2 can also be 1111. Alternatively, the device identifier of non-3GPP device #1 accessing terminal device #1 can be 1111, and the device identifier of non-3GPP device #2 accessing terminal device #2 can also be 1110.

[0185] In a possible design, after determining the device identifier of the first non-3GPP device, the terminal device can send a first message, for example, to a session management network element, for example, by sending the first message to the session management network element through a mobility management network element. The mobility management network element can perform transparent forwarding, or the mobility management network element can process (for example, convert the format of the first message) the first message and then send the processed first message to the session management network element. The session management network element is, for example, an SMF network element in a 5G communication network, and the mobility management network element is, for example, an AMF in the 5G communication network. The first message, which can also be referred to as a session establishment or modification request (for example, a protocol data unit (PDU) session establishment or modification request), is used to request establishment or modification of a session for carrying data of the first non-3GPP device. The first message includes the device identifier of the first non-3GPP device. Optionally, the first message can be carried in a non-access stratum (NAS) message. The session is used to transmit data of the first non-3GPP device, for example, data received by the first non-3GPP device, for example, data received from a network side (for example, a DN), and / or data sent by the first non-3GPP device, for example, data sent by the first non-3GPP device to a network side (for example, a DN). The session is, for example, a PDU session.

[0186] Optionally, after receiving the first message or the processed first message, the session management network element can further request a policy control network element to generate a session management policy for managing the session. Optionally, when requesting the policy control network element to generate the session management policy for managing the session, the session management network element can further provide the device identifier of the first non-3GPP device to the PCF.

[0187] The policy control network element can obtain information of the first non-3GPP device from a unified data storage network element according to the device identifier of the first non-3GPP device, and determine a session management policy based on the information of the first non-3GPP device. The session management policy is used to manage the session, for example, including policy and charging control (PCC) rules. The session management network element can create or modify the session and configure a QoS parameter based on the session management policy, so that the session carries data of the first non-3GPP device.

[0188] In the embodiments of this application, the terminal device can determine the device identifier based on the device description information of the non-3GPP device and the first mapping relationship, and a mechanism for identifying the non-3GPP device based on the device identifier is provided, so that the terminal device and the network side can identify the non-3GPP device based on the device identifier, so as to provide differentiated services for different non-3GPP devices by the network side.

[0189] The terminal device acquires the first mapping relationship in the manner of C1 described above. For example, the terminal device acquires the first mapping relationship from the first application network element. The interaction process between the devices involved in the communication method shown in FIG. 3 is described below in conjunction with the schematic diagram of the communication method shown in FIG. 4.

[0190] S401. The terminal device sends a UIA service subscription request to the first application network element. Correspondingly, the first application network element receives the UIA service subscription request from the terminal device. The meaning of the UIA service subscription request can refer to the content of the UIA service subscription request described above with reference to FIG. 3, which is not repeated here. Optionally, the UIA service subscription request includes one or more device description information. Optionally, the UIA service subscription request also includes one or more device identifier. The content of the device description information and the device identifier can refer to the content of the device description information and the device identifier described above with reference to FIG. 3, which is not repeated here.

[0191] S402. The first application network element sends a UIA service subscription response to the terminal device. Correspondingly, the terminal device receives the UIA service subscription response from the first application network element. The meaning of the UIA service subscription response can refer to the content of the UIA service subscription response described above with reference to FIG. 3, which is not repeated here. Optionally, the UIA service subscription response includes information indicating the first mapping relationship. The content of the first mapping relationship can refer to the content of the first mapping relationship described above with reference to FIG. 3.

[0192] It is possible that the terminal device has subscribed to the UIA service before, or the terminal device has subscribed to the UIA service by default, or the non-3GPP device does not need the UIA service, etc. In this case, the steps of S401 and S402 are not needed, i.e., the steps of S401 and S402 are optional steps, which are shown in FIG. 4 in dashed lines.

[0193] S403. The first application network element sends information indicating the first mapping relationship to the terminal device. Correspondingly, the terminal device receives the information indicating the first mapping relationship from the first application network element. If the UIA service subscription response includes the information indicating the first mapping relationship, or the first mapping relationship is also pre-stored in the terminal device, the step of S403 is not needed, i.e., S403 is an optional step, which is shown in FIG. 4 in dashed lines.

[0194] S404. The first non-3GPP device establishes a connection with the terminal device. For example, the terminal device can broadcast information of the terminal device, and the first non-3GPP device receives the information of the terminal device, and then establishes a connection with the terminal device according to the information of the terminal device. There are various ways for the first non-3GPP device to establish a connection with the terminal device, which are not limited in the embodiments of the present application.

[0195] S405, the first non-3GPP device sends device description information of the first non-3GPP device to the terminal device. Correspondingly, the terminal device receives the device description information of the first non-3GPP device from the first non-3GPP device. The content of the device description information of the first non-3GPP device can refer to the content of the device description information of the first non-3GPP device discussed in the foregoing FIG. 3, which will not be listed here.

[0196] The terminal device can identify the device description information of the first non-3GPP device by itself or obtain the device description information of the first non-3GPP device from the second application network element, so that the step of S405 is not needed, that is, S405 is an optional step, which is shown by a dashed line in FIG. 4.

[0197] S406, the terminal device determines the device identifier of the first non-3GPP device according to the device description information of the first non-3GPP device and the first mapping relationship.

[0198] The content of the device identifier of the first non-3GPP device and the content of determining the device identifier of the first non-3GPP device can refer to the content of the device identifier of the first non-3GPP device and the content of determining the device identifier of the first non-3GPP device discussed in the foregoing FIG. 3, respectively.

[0199] In the embodiment of the application, the terminal device can determine the device identifier based on the device description information of the non-3GPP device and the first mapping relationship, a mechanism for identifying the non-3GPP device based on the device identifier is provided, and the terminal device does not need to generate or pre-store the first mapping relationship, which is beneficial to reducing the processing amount of the terminal device.

[0200] In the 5G communication network, other non-3GPP devices are allowed to connect to the 5G communication network through the terminal device, and the 5G communication network can provide dedicated network access and services, service quality control, and the like for the non-3GPP devices. The 5G communication network can update the URSP rule corresponding to the terminal device based on the information of the non-3GPP device accessing the terminal device, and the URSP rule indicates the PDU session parameter. Therefore, the terminal device requests to create or modify the PDU session for the non-3GPP device according to the updated URSP rule, so as to realize the control of the QoS of the non-3GPP device.

[0201] However, in this way, once the non-3GPP device accessing the terminal device changes, for example, a non-3GPP device accessing the terminal device is added, the process of updating the URSP rule of the 5G communication network will be triggered, and the signaling overhead is large.

[0202] Therefore, embodiments of the present application provide a communication scheme, in which a traffic descriptor (TD) in a URSP rule indicates device description information common to multiple non-3rd Generation Partnership Project (3GPP) devices rather than information specific to a certain non-3GPP device, so that in the case of a non-3GPP device that has a new access terminal device, if the non-3GPP device has the device description information, the previously determined URSP rule can be reused without triggering an update URSP rule procedure, thereby reducing the number of URSP rule updates and signaling overhead.

[0203] FIG. 5 shows a schematic diagram of a communication method, and the following describes each step shown in FIG. 5.

[0204] S501, a policy control network element sends one or more rules to a terminal device. Correspondingly, the terminal device receives one or more rules from the policy control network element. Any rule in the one or more rules is used for session determination, and the name of the rule can be various and is not specifically limited. In embodiments of the present application, one or more rules are taken as one or more URSP rules for example. That is, the URSP rules involved in embodiments of the present application can be replaced by rules.

[0205] The TD of each URSP rule in the one or more URSP rules indicates device description information, and the device description information is common to multiple non-3GPP devices.

[0206] The policy control network element can be a PCF, for example, specifically an AM PCF, which means a PCF connected to an AMF, and the AM PCF is selected by the AMF. The AM PCF is a PCF for the UE (PCF for the UE).

[0207] For example, the second application network element can obtain information of the non-3GPP device (or referred to as data of the non-3GPP device or non-3GPP device data), for example, including information of the non-3GPP device, for example, including device description information of the non-3GPP device, which is device description information common to a plurality of non-3GPP devices. The device description information indicates at least one of a quality of service level, a device level or a device type of the non-3GPP device, for example. The content of the quality of service level, the device level or the device type can be discussed with reference to the content of the quality of service level, the device level or the device type discussed in FIG. 3, respectively. The non-3GPP device refers to a non-3GPP device that can access the terminal device. The information of the non-3GPP device further includes an identifier of the UE, and can further include a DNN and / or an S-NSSAI corresponding to the non-3GPP device, and the like. In the embodiment of the present application, the device description information of the non-3GPP device includes device description information of the first non-3GPP device as an example.

[0208] The manner in which the second application network element obtains the information of the non-3GPP device will be described below in combination with the manner of E1, E2 or E3.

[0209] E1, when the terminal device requests to subscribe to the UIA service, the terminal device can send the information of the non-3GPP device to the second application network element. In this case, the information of the non-3GPP device can be carried in the UIA service subscription request. The content of the UIA service subscription request can be discussed with reference to the content of the UIA service subscription request discussed in FIG. 3, which will not be listed here.

[0210] E2, the terminal device can identify device parameters of the non-3GPP device, or pre-store device parameters of the first non-3GPP device. The terminal device sends the device parameters of the non-3GPP device to the second application network element, and the second application network element determines the device description information of the first non-3GPP device according to the second mapping relationship and the device parameters of the non-3GPP device. The content of the device parameters can also be discussed with reference to the content of the device parameters discussed in FIG. 3, which will not be listed here. The content of the device parameters is different from the content of the parameter item indicated by the device description information, for example, the device parameters are the address or the device level of the first non-3GPP device, and the device description information is the quality of service level of the first non-3GPP device. Alternatively, the content of the device parameters is the same as the content of the parameter item indicated by the device description information, but the representation form of the device parameters is different from the representation form of the parameter item indicated by the device description information.

[0211] E3, the second application network element can determine the device description information of the non-3GPP device that the terminal device accesses by default, or the device description information of the non-3GPP device that the terminal device accesses frequently.

[0212] For example, when the terminal device sends a UIA service subscription request to the second application network element, the second application network element stores the device description information of the non-3GPP device. The second application network element can take one or more device description information with high frequency as the device description information of the non-3GPP device of the common access terminal device.

[0213] For example, when the terminal device does not provide the device description information of the non-3GPP device to the second application network element, the second application network element can determine the information of the non-3GPP device in the E3 mode.

[0214] In summary, after the second application network element obtains the information of the non-3GPP device, the second application network element can store the device description information of the non-3GPP device in the unified data storage network element through the NEF. For example, the second application network element sends a fourth message to the unified data storage network element. The fourth message includes the device description information of the non-3GPP device. In this way, the unified data storage network element stores the information of the non-3GPP device in the terminal device application data or policy data. Optionally, the application data (or policy data) corresponds to the device description information of the non-3GPP device, for example, the data sub key (or simply referred to as the sub key) of the application data is the device description information of the non-3GPP device. The application data (or policy data) corresponds to the terminal device, for example, the data key (or simply referred to as the key) of the application data is the identifier of the terminal device, for example, the SUPI of the terminal device.

[0215] Please refer to the following table 5 or table 6 for examples of application data provided by the embodiments of the present application. Table 5 takes the device description information indicating the device type (or the device description information including the information of the device type) as an example.

[0216] Table 5

[0217] As shown in table 5, the unified data storage network element stores the information of the non-3GPP device, and the data key of the information of the non-3GPP device is the SUPI of the terminal device, and the data sub key is the information of the device type.

[0218] Table 6 takes the device description information indicating the quality of service level (or the device description information including the information of the quality of service level) as an example.

[0219] Table 6

[0220] As shown in Table 6, the unified data storage network element stores information of the non-3GPP device, and the data index of the information of the non-3GPP device is the SUPI of the terminal device, and the data sub-index is the information of the quality of service level of the device.

[0221] After determining the updated policy data of the terminal device, the unified data storage network element can send the updated policy data to the policy control network element, which includes the information of the non-3GPP device. Alternatively, the policy control network element has previously obtained the updated policy data, which includes the information of the non-3GPP device. In this way, the policy control network element can determine one or more URSP rules based on the information of the non-3GPP device (or the updated policy data). For example, the policy control network element sets the device description information of the non-3GPP device provided by the application network element as the TD in the URSP rule, and sets the DNN and S-NSSAI corresponding to the non-3GPP device as the corresponding components of the route selection descriptor (RSD) of the URSP rule, to obtain one or more URSP rules. The one or more URSP rules can be all or part of the URSP rules determined by the policy control network element, which is not limited.

[0222] The policy control network element can send the one or more URSP rules to the terminal device through the AMF. Each of the one or more URSP rules includes a TD. Each of the one or more URSP rules can also include one or more route selection descriptors (RSDs). The RSDs include one or more of the session and service continuity (SSC) mode, the access type, the redundancy sequence number (RSN), the session pair ID, the DNN, or the S-NSSAI. Optionally, the policy control network element can also send the priority of the one or more RSDs to the terminal device.

[0223] In the embodiments of the present application, the TD of each of the one or more URSP rules indicates the device description information, and the device description information is the device description information common to the plurality of non-3GPP devices, which makes any URSP rule applicable to a plurality of non-3GPP devices, rather than a specific non-3GPP device.

[0224] Please refer to Table 7 or Table 8 below for examples of URSP rules provided by embodiments of the present application. Table 7 takes the example of device description information indicating device type (or in other words, device description information including information of device type).

[0225] Table 7

[0226] As shown in Table 7 above, the TD of the URSP rule is information of device type.

[0227] Table 8 takes the example of device description information indicating quality of service level (or in other words, device description information including information of quality of service level).

[0228] Table 8

[0229] As shown in Table 8 above, the TD of the URSP rule is information of quality of service level.

[0230] For example, please refer to Table 9 for examples of one or more URSP rules provided by embodiments of the present application. Table 9 takes the example of device description information including values of device type.

[0231] Table 9

[0232] As shown in Table 9 above, values of device type of 1, 2, and 3 respectively represent device type of camera, printer, and VR glasses, value of device type of 1 corresponds to URSP rule #1, value of device type of 2 corresponds to URSP rule #2, and value of device type of 3 corresponds to URSP rule #3.

[0233] For example, please refer to Table 10 for examples of one or more URSP rules provided by embodiments of the present application. Table 10 takes the example of device description information including values of quality of service level.

[0234] Table 10

[0235] As shown in Table 10 above, values of quality of service level of 1 corresponds to URSP rule #1, values of quality of service level of 2 corresponds to URSP rule #2, and values of quality of service level of 3 corresponds to URSP rule #3.

[0236] S502, the terminal device determines a first rule from the one or more rules. The TD of the first rule indicates device description information that matches the device description information of the first non-3GPP device, and the first rule is used to determine a session for carrying data of the first non-3GPP device. Hereinafter, the rule is still taken as an example of URSP rule.

[0237] The terminal device can obtain the device description information of the first non-3GPP device. The content of the device description information of the first non-3GPP device obtained by the terminal device can refer to the content of the device description information of the first non-3GPP device obtained by the terminal device discussed in FIG. 3, for example, the terminal device obtains the device description information of the first non-3GPP device in any of the manners of D1 to D4 discussed above, which will not be listed one by one here.

[0238] For example, the terminal device can send a second message to the second application network element, the second message indicating the device parameter of the first non-3GPP device. The device parameter of the first non-3GPP device can refer to the device parameter of the first non-3GPP device discussed in FIG. 3. The second message is carried in the UIA service subscription request for example. The terminal device can receive a third message from the second application network element, the third message indicating the second mapping relationship, the content of the second mapping relationship can refer to the content of the second mapping relationship discussed in FIG. 3, and the terminal device can determine the device description information of the first non-3GPP device based on the second mapping relationship and the device parameter of the first non-3GPP device. The third message is carried in the UIA service subscription response for example. In this way, the terminal device can determine the first URSP rule corresponding to the first non-3GPP device from one or more URSP rules based on the device description information of the first non-3GPP device. The terminal device can determine whether to create or modify a session for the first non-3GPP device based on the first URSP rule.

[0239] For example, continuing to refer to the example shown in Table 9, if the device description information of the first non-3GPP device includes the value of the device type of the first non-3GPP device as 2, the terminal device determines the first URSP rule as URSP rule #2. For another example, continuing to refer to the example shown in Table 10, if the device description information of the first non-3GPP device includes the value of the quality of service level of the first non-3GPP device as 3, the terminal device determines the first URSP rule as URSP rule #3.

[0240] In a possible implementation, the terminal device can further determine the device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device. For example, the terminal device can determine the device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device and the serial number.

[0241] The sequence number can also be referred to as a number, a serial number, an order, an identification code, or an access code, and the like, and the name thereof is not limited. The sequence number is used to distinguish the first non-3GPP device from the at least one non-3GPP device. The at least one non-3GPP device and the first non-3GPP device are both non-3GPP devices of the terminal device. Optionally, the device description information of the at least one non-3GPP device is the same as the device description information of the first non-3GPP device. The sequence number can be assigned by the terminal device. For example, the terminal device assigns the sequence number to the first non-3GPP device according to the order in which the first non-3GPP device accesses the terminal device, or the terminal device randomly generates the sequence number for the first non-3GPP device, and the manner of assigning the sequence number is not limited. Optionally, if the quality of service level is application-granular, the first non-3GPP device can have different quality of service levels corresponding to different applications, and accordingly, the terminal device can determine multiple device identifiers for the first non-3GPP device.

[0242] The manner in which the terminal device determines the device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device and the sequence number is described below.

[0243] F1, the terminal device combines the device description information of the first non-3GPP device and the sequence number to obtain the device identifier of the first non-3GPP device. The device identifier of the first non-3GPP device includes the device description information of the first non-3GPP device and the sequence number.

[0244] In a possible design, the terminal device directly combines the device description information of the first non-3GPP device and the sequence number. For example, the device identifier of the first non-3GPP device is, for example, device description information + sequence number, or sequence number + device description information. For example, the device identifier of the first non-3GPP device is, for example, device type information + sequence number, quality of service level information + sequence number, sequence number + device type information, or sequence number + quality of service level information. Here, “+” represents a parallel relationship.

[0245] Optionally, the device identifier of the first non-3GPP device includes a first field and a second field, the first field indicates the device description information of the first non-3GPP device, and the second field indicates the sequence number. The first field and the second field each include at least one bit. For example, the first field includes N bits, and the second field includes M bits, where N and M are positive integers, for example, N is 3 and M is 2.

[0246] In another possible design, the terminal device combines at least one parameter item indicated by the device description information of the first non-3GPP device and the sequence number to obtain the device identity of the first non-3GPP device. The device identity of the first non-3GPP device includes at least one parameter item indicated by the device description information of the first non-3GPP device and the sequence number.

[0247] For example, the device identity of the first non-3GPP device is, for example, a value of at least one parameter item indicated by the device description information + the sequence number, or the sequence number + a value of at least one parameter item indicated by the device description information. For example, the device identity of the first non-3GPP device is, for example, a device type + a sequence number, a quality of service class + a sequence number, a sequence number + a device type, or a sequence number + a quality of service class. Here, "+" represents a parallel relationship. For example, a first field in the device identity of the first non-3GPP device indicates at least one parameter item indicated by the device description information of the first non-3GPP device, and a second field in the device identity of the first non-3GPP device indicates the sequence number.

[0248] F2, the terminal device processes the device description information of the first non-3GPP device and the sequence number based on a second algorithm to obtain the device identity of the first non-3GPP device. The second algorithm is, for example, a hash algorithm. The second algorithm can be predefined or preconfigured in the terminal device, for example, predefined by a protocol, or can be determined by negotiation between the terminal device and a network side (for example, an access network device or an AF, etc.), or indicated to the terminal device by the network side.

[0249] There are various ways for the terminal device to determine the device identity of the first non-3GPP device, which are not limited herein.

[0250] In the embodiments of this application, the TD in the URSP uses device description information common to multiple non-3GPP devices, so that different non-3GPP devices can use the same URSP, reducing the number of URSP updates and thus reducing signaling overhead.

[0251] After the terminal device determines the device identity of the first non-3GPP device and determines that a session needs to be created or modified for the first non-3GPP device, the terminal device can optionally request a session management network element (for example, an SMF) to establish or modify the session. The session is used to carry (or transmit) data of the first non-3GPP device. The following is an example description in conjunction with the schematic diagram of establishing or modifying a session shown in FIG. 6.

[0252] [Corrected according to Rule 91 19.11.2025] S601, the terminal device sends a first message to a mobility management network element (e.g. AMF). Correspondingly, the mobility management network element receives the first message from the terminal device. The content of the first message can refer to the content of the first message discussed in FIG. 3, which is not listed here. For example, the first message is used to request to establish or modify a session, and the first message includes the device identifier of the first non-3GPP device.

[0253] S602, the mobility management network element determines the number of non-3GPP devices accessing the terminal device according to the device identifier of the first non-3GPP device.

[0254] The mobility management network element accumulates the number of non-3GPP devices accessing the terminal device according to the device identifier of the first non-3GPP device. If the number of non-3GPP devices accessing the terminal device exceeds the threshold, a prompt message is sent to the terminal device indicating that the number of non-3GPP devices accessing the terminal device exceeds the threshold. If the number of non-3GPP devices accessing the terminal device does not exceed the threshold, the subsequent steps are continued.

[0255] S603, the mobility management network element sends a create session management context request to the session management network element. Correspondingly, the session management network element receives the create session management context request from the mobility management network element. The create session management context request can include the device identifier of the first non-3GPP device. Optionally, the session management network element can also parse the device description information of the first non-3GPP device according to the device identifier of the first non-3GPP device.

[0256] For example, the session management network element is pre-configured or pre-defined with the way in which the terminal device generates the device identifier of the first non-3GPP device, so that based on this way, the device identifier of the first non-3GPP device can be parsed to obtain the device description information of the first non-3GPP device.

[0257] For example, the first field in the device identifier of the first non-3GPP device indicates the device description information, and the second field indicates the serial number, so that the session management network element can parse the first field to obtain the device description information of the first non-3GPP device.

[0258] S604, the session management network element sends a fifth message to the policy control network element. Correspondingly, the policy control network element receives the fifth message from the session management network element. The fifth message is used to request a session management policy request. The fifth message includes the device identifier or the device description information of the first non-3GPP device.

[0259] The policy control network element determines the session management policy based on the information (e.g., policy data or application data) of the first non-3GPP device. The session management policy includes, for example, policy and charging control (PCC) rules. The content of the determination of the session management policy can refer to the content of the determination of the session management policy discussed in FIG. 3, which is not listed here.

[0260] If the policy control network element does not have the information of the first non-3GPP device, the policy control network element can send a sixth message to the unified data storage network element for requesting the information of the first non-3GPP device according to the device description information of the first non-3GPP device, and the sixth message includes the device description information of the first non-3GPP device. After receiving the sixth message, the unified data storage network element can send the information of the first non-3GPP device to the policy control network element. The policy control network element can obtain the device description information of the first non-3GPP device from the session management policy request. Alternatively, the policy control network element can determine the device description information of the first non-3GPP device based on the device identifier of the first non-3GPP device.

[0261] S605, the policy control network element sends the session management policy to the session management network element. Correspondingly, the session management network element receives the session management policy from the policy control network element.

[0262] S606, the session management network element configures the QoS parameter based on the session management policy, and creates or modifies the session. In this way, the session carries (or said) the data of the non-3GPP device.

[0263] FIG. 6 is an example of the process of creating or modifying the session, which does not limit the specific process of creating or modifying the session. Each step shown in FIG. 6 is an optional step, which is shown in FIG. 6 with a dashed line.

[0264] The following takes the device description information including the information of the device type, and one or more rules as one or more URSP rules as an example, and combines the schematic diagram of the communication method shown in FIG. 7 to exemplarily introduce the communication method involved in FIG. 5.

[0265] S701, the terminal device sends a UIA service subscription request to the second application network element. Correspondingly, the second application network element receives the UIA service subscription request from the terminal device. The content of the UIA service subscription request can refer to the content of the UIA service subscription request discussed in FIG. 3, and the repeated parts will not be listed. Optionally, the UIA service subscription request includes the information of the device type of the non-3GPP device, such as XR glasses, a smart television, a printer, etc. The other content of the device type can refer to the content of the device type discussed in FIG. 3, which will not be listed here. The information of the device type of the non-3GPP device includes the information of the device type of the first non-3GPP device.

[0266] S702, the second application network element sends a UIA service subscription response to the terminal device. Correspondingly, the terminal device receives the UIA service subscription response from the second application network element. Optionally, if the UIA service subscription request includes the information of the device type of the non-3GPP device, the UIA service subscription response can indicate the second mapping relationship, or in other words, the UIA service subscription response includes information for indicating the second mapping relationship. In this case, the content of the device parameter is the same as that of the parameter item indicated by the device description information, but the representation form of the device parameter is different from that of the parameter item indicated by the device description information.

[0267] [Corrected according to Rule 91, 19.11.2025] S703, the second application network element sends a fourth message to the unified data storage network element. Correspondingly, the unified data storage network element receives the fourth message from the second application network element. The fourth message in the embodiment of the application includes the information of the first non-3GPP device. The information of the first non-3GPP device, for example, includes the device description information of the first non-3GPP device.

[0268] [Corrected according to Rule 91, 19.11.2025] Exemplarily, the second application network element calls the service of the NEF, and sends the fourth message to the NEF, which for example includes the information of the first non-3GPP device, such as the information of the device type of the first non-3GPP device and the identifier of the terminal device, and can also include the DNN and / or S-NSSAI corresponding to the first non-3GPP device. If the UIA service subscription request includes the information of the device type of the first non-3GPP device, the information of the device type in the fourth message can be the information of the device type included in the UIA service subscription request. If the UIA service subscription request does not include the information of the device type of the first non-3GPP device, the information of the device type in the fourth message can be the information of the default or commonly used non-3GPP device type corresponding to the terminal device subscription.

[0269] S704, the unified data storage network element stores the information of the first non-3GPP device, and the information of the first non-3GPP device corresponds to the information of the device description type of the first non-3GPP device.

[0270] The NEF converts the information of the non-3GPP device sent by the application network element into application data or policy data of the terminal device, and stores the application data or the policy data in the unified data storage network element. The information of the non-3GPP device (or the application data, or the policy data) corresponds to the information of the device type of the non-3GPP device. The content of the information of the non-3GPP device, the application data, and the policy data can be referred to the content of the information of the non-3GPP device, the application data, and the policy data discussed in FIG. 5, which will not be listed here.

[0271] S705, the unified data storage network element sends the information of the first non-3GPP device to the policy control network element. Correspondingly, the policy control network element receives the information of the first non-3GPP device from the unified data storage network element. For example, the unified data storage network element calls the service of the policy control network element, and notifies the policy control network element of the information of the first non-3GPP device (or the updated policy data or the updated application data).

[0272] S706, the policy control network element sends one or more URSP rules to the terminal device. Correspondingly, the terminal device receives one or more URSP rules from the policy control network element. The TD of each URSP rule in the one or more URSP rules is the information of the device type of the non-3GPP device. For example, the policy control network element sends the one or more URSP rules to the terminal device through the terminal device policy delivery process. The content of the one or more URSP rules and the determination of the content of the one or more URSP rules can be referred to the content of the one or more URSP rules and the determination of the content of the one or more URSP rules discussed in FIG. 5, which will not be listed here.

[0273] S707, the first non-3GPP device establishes a connection with the terminal device. The manner of establishing the connection can be referred to the content of establishing the connection discussed in FIG. 3, which will not be listed here.

[0274] S708, the terminal device determines a first URSP rule according to the information of the device type of the first non-3GPP device and the one or more URSP rules.

[0275] The content of the first URSP rule and the determination of the content of the first URSP rule by the terminal device can be referred to the content of the first URSP rule and the determination of the content of the first URSP rule by the terminal device discussed in FIG. 5, which will not be listed here.

[0276] S709, the terminal device generates the device identity of the first non-3GPP device according to the information of the device type of the first non-3GPP device and the sequence number.

[0277] The content of the sequence number, the content of the device identity of the first non-3GPP device, and the content of the device identity of the first non-3GPP device determined by the terminal device are respectively discussed above with reference to the content of the sequence number, the content of the device identity of the first non-3GPP device, and the content of the device identity of the first non-3GPP device determined by the terminal device discussed above with reference to FIG. 5, and are not listed here.

[0278] After the terminal device determines the device identity of the first non-3GPP device and determines that the session needs to be created or modified for the first non-3GPP device, the terminal device can optionally request the session management network element to establish or modify the session. The process of the session management network element establishing or modifying the session can refer to the content discussed above with reference to FIG. 6, and is not listed here.

[0279] In the embodiments of the present application, the TD of the URSP rule is the information of the device type, so that the same type of device can use the same URSP rule, avoiding frequent updating of the URSP rule and reducing signaling overhead. Further, the device identity of the non-3GPP device can be determined based on the device type of the non-3GPP device, and a mechanism for determining the device identity of the non-3GPP device is provided.

[0280] The communication method involved in FIG. 5 is exemplarily introduced below by taking the device description information including the information of the quality of service level and one or more rules as one or more URSP rules as an example, in combination with the schematic diagram of the communication method shown in FIG. 8.

[0281] S801, the terminal device sends a UIA service subscription request to the second application network element. Correspondingly, the second application network element receives the UIA service subscription request from the terminal device. The content of the UIA service subscription request can refer to the content of the UIA service subscription request discussed above with reference to FIG. 3, and the repeated part is not listed here. Optionally, the UIA service subscription request includes the information of the device level of the non-3GPP device, such as the diamond level, the gold medal level, and the silver medal level. Other content of the device level can refer to the content of the device level discussed above with reference to FIG. 3, and is not listed here.

[0282] S802, the second application network element sends a UIA service subscription response to the terminal device. Correspondingly, the terminal device receives the UIA service subscription response from the second application network element. Optionally, if the UIA service subscription request includes the device level information of the non-3GPP device, the UIA service subscription response can indicate the second mapping relationship, or the UIA service subscription response includes information for indicating the second mapping relationship. In this case, the content of the device parameter is different from the content of the parameter item indicated by the device description information, and the device parameter is, for example, the device level, and the device description information includes the information of the quality of service level.

[0283] [According to Rule 91 Correction 19.11.2025]S803, the second application network element sends a fourth message to the unified data storage network element. Correspondingly, the unified data storage network element receives the fourth message from the second application network element. The fourth message in the embodiment of the application includes the information of the first non-3GPP device. The information of the first non-3GPP device includes, for example, the device description information of the first non-3GPP device.

[0284] The content of the fourth message sent by the second application network element to the unified data storage network element can refer to the content of the fourth message sent by the second application network element to the unified data storage network element discussed in the foregoing FIG. 7, which will not be listed here.

[0285] S804, the unified data storage network element stores the information of the first non-3GPP device, and the information of the first non-3GPP device corresponds to the device description type information of the first non-3GPP device.

[0286] The content of the information of the first non-3GPP device, the information of the non-3GPP device, the content of the application data, and the content of the policy data stored by the unified data storage network element can refer to the content of the information of the first non-3GPP device, the information of the non-3GPP device, the content of the application data, and the content of the policy data stored by the unified data storage network element discussed in the foregoing FIG. 7, which will not be listed here.

[0287] S805, the unified data storage network element sends the information of the first non-3GPP device to the policy control network element. Correspondingly, the policy control network element receives the information of the first non-3GPP device from the unified data storage network element.

[0288] The content of the information of the first non-3GPP device sent by the unified data storage network element to the policy control network element can refer to the content of the information of the first non-3GPP device sent by the unified data storage network element to the policy control network element discussed in the foregoing FIG. 7, which will not be listed here.

[0289] S806, the policy control network element sends one or more URSP rules to the terminal device. Correspondingly, the terminal device receives one or more URSP rules from the policy control network element. The TD of each URSP rule in the one or more URSP rules is the information of the quality of service level of the non-3GPP device. The content of the one or more URSP rules and the determination of the content of the one or more URSP rules can refer to the content of the one or more URSP rules and the determination of the content of the one or more URSP rules discussed in the foregoing FIG. 5, which will not be listed here.

[0290] S807, the first non-3GPP device establishes a connection with the terminal device. The manner of establishing the connection can refer to the content of establishing the connection discussed in the foregoing FIG. 3, which will not be listed here.

[0291] S808, the terminal device determines a first URSP rule according to the information of the quality of service level of the first non-3GPP device and the one or more URSP rules.

[0292] The content of the first URSP rule and the determination of the content of the first URSP rule by the terminal device can refer to the content of the first URSP rule and the determination of the content of the first URSP rule by the terminal device discussed in the foregoing FIG. 5, which will not be listed here.

[0293] S809, the terminal device generates a device identifier of the first non-3GPP device according to the information of the quality of service level of the first non-3GPP device and the sequence number.

[0294] The content of the sequence number, the content of the device identifier of the first non-3GPP device, and the determination of the content of the device identifier of the first non-3GPP device by the terminal device can refer to the content of the sequence number, the content of the device identifier of the first non-3GPP device, and the determination of the content of the device identifier of the first non-3GPP device by the terminal device discussed in the foregoing FIG. 5, which will not be listed here.

[0295] After the terminal device determines the device identifier of the first non-3GPP device and determines that the session needs to be created or modified for the first non-3GPP device, the terminal device can optionally request the session management network element to establish or modify the session. The process of the session management network element establishing or modifying the session can refer to the content discussed in the foregoing FIG. 6, which will not be listed here.

[0296] In the embodiments of the present application, the TD of the URSP rule is the information of the quality of service level, so that the devices of the same quality of service level can use the same URSP rule, avoiding frequent updating of the URSP rule and reducing signaling overhead. Further, the device identifier of the non-3GPP device can be determined based on the quality of service level, providing a mechanism for determining the device identifier of the non-3GPP device.

[0297] Based on the same inventive concept, the embodiment of the present application provides a communication device. The communication device shown in any of FIGS. 9 to 11 is described below. The communication device is, for example, the terminal device involved in FIG. 1, the UE involved in FIG. 2, the AF involved in FIG. 2, the UDR, or the PCF, etc., or can be a module or the like of these devices, and no specific limitation is made thereto.

[0298] As shown in FIG. 9, the communication device 900 can include modules or units for implementing the method embodiments described above. In one possible design, the communication device 900 includes a processing unit 910 and a communication unit 920. The communication unit 920 is configured to perform transceiving operations, such as functions related to transmitting and receiving; the communication unit 920 can be referred to as a transceiver; optionally, the communication unit 920 includes a receiving unit and a transmitting unit. The processing unit 910 is configured to perform processing operations. Alternatively, the communication unit 920 can be a transmitter and a receiver, or the communication unit 920 is a transmitter and a receiver. Optionally, the communication device 900 further includes a storage unit 930. The storage unit 930 is configured to store program codes or data of the device. The storage unit 930 is an optional unit, which is shown in FIG. 9 with a dashed box.

[0299] In a first embodiment, the communication device 900 can be the terminal device in the method embodiments shown in FIG. 3 or FIG. 4, or a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device, or implement the functions of the terminal device in the method embodiments shown in FIG. 3 or FIG. 4. For example, the communication device 900 is a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device.

[0300] In the above embodiments, the communication unit 920 is configured to obtain the first mapping relationship, determine the device description information of the first non-3GPP device, and determine the device identifier of the first non-3GPP device, etc.

[0301] The communication device 900 can also implement other steps performed by the terminal device in the method embodiments shown in FIG. 3 or FIG. 4, which are not listed one by one here.

[0302] In a second embodiment, the communication device 900 can be the application network element in the method embodiments shown in FIG. 3 or FIG. 4, or a communication module in the application network element, or a circuit or chip responsible for communication functions in the application network element, or implement the functions of the application network element in the method embodiments shown in FIG. 3 or FIG. 4. For example, the communication device 900 is a communication module in the application network element, or a circuit or chip responsible for communication functions in the terminal device.

[0303] In the above embodiments, the communication unit 920 is configured to transmit the first mapping relationship, etc.

[0304] The communication apparatus 900 can also implement other steps performed by the application network element in the method embodiments of FIG. 3 or FIG. 4, which are not listed one by one here.

[0305] In a third embodiment, the communication apparatus 900 can be the terminal device in the method embodiments of FIG. 5, or the terminal device involved in FIG. 7 or FIG. 8, or a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device, or the like, or implement the functions of the terminal device in the method embodiments of FIG. 5, or the functions of the terminal device in the method embodiments of FIG. 7 or FIG. 8. For example, the communication apparatus 900 is the terminal device, or a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device.

[0306] In the above embodiments, the communication unit 920 is configured to obtain one or more rules, and determine a first rule from the one or more rules according to the device description information of the first non-3GPP device.

[0307] The communication apparatus 900 can also implement other steps performed by the terminal device in the method embodiments of FIG. 5, and can also perform steps performed by the terminal device involved in FIG. 6, or can also implement other steps performed by the terminal device in FIG. 7 or FIG. 8, which are not listed one by one here.

[0308] In a fourth embodiment, the communication apparatus 900 can be the policy control network element in the method embodiments of FIG. 5, FIG. 7 or FIG. 8, a communication module in the policy control network element, or a circuit or chip responsible for communication functions in the policy control network element, or the like, or implement the functions of the policy control network element in the method embodiments of FIG. 5, FIG. 7 or FIG. 8. For example, the communication apparatus 900 is a communication module in the policy control network element, or a circuit or chip responsible for communication functions in the policy control network element.

[0309] In the above embodiments, the communication unit 920 is configured to send one or more rules, etc.

[0310] The communication apparatus 900 can also implement other steps performed by the policy control network element in the method embodiments of FIG. 5, and can also perform steps performed by the policy control network element involved in FIG. 6, or can also perform other steps performed by the policy control network element in the method embodiments of FIG. 7 or FIG. 8, which are not listed one by one here.

[0311] In a fifth possible implementation, the communication apparatus 900 can be an application function entity, a communication module in the application function entity, or a circuit or chip responsible for communication functions in the application function entity, or implement functions of the application function entity in the method embodiments of FIG. 5, FIG. 7 or FIG. 8. For example, the communication apparatus 900 is a communication module in the application function entity, or a circuit or chip responsible for communication functions in the application function entity.

[0312] In the above implementation, the communication unit 920 is configured to send the second mapping relationship, etc.

[0313] The communication apparatus 900 can also implement other steps performed by the application function entity in the method embodiment of FIG. 5, and can also perform steps performed by the application function entity involved in FIG. 6, or can also implement other steps performed by the application function entity in the method embodiments of FIG. 7 or FIG. 8, which are not listed one by one here.

[0314] In a sixth possible implementation, the communication apparatus 900 can be a unified data storage network element, a communication module in the AF, or a circuit or chip responsible for communication functions in the unified data storage network element, or implement functions of the unified data storage network element in the method embodiments of FIG. 5, FIG. 7 or FIG. 8. For example, the communication apparatus 900 is a communication module in the unified data storage network element, or a circuit or chip responsible for communication functions in the unified data storage network element.

[0315] In the above implementation, the communication unit 920 is configured to receive the sixth message, and send information of the first non-3GPP device, etc.

[0316] The communication apparatus 900 can also implement other steps performed by the unified data storage network element in the method embodiment of FIG. 5, and can also perform steps performed by the unified data storage network element involved in FIG. 6, or can also implement other steps performed by the unified data storage network element in the method embodiments of FIG. 7 or FIG. 8, which are not listed one by one here.

[0317] In a possible design, when the communication apparatus 900 is a terminal device or a communication module in the terminal device, the function of the processing unit 910 can be implemented by one or more processors. Specifically, the processor can include a Modem chip, or a System on Chip (SoC) chip or a SIP chip including a Modem core. The function of the communication unit 920 can be implemented by a transceiver circuit.

[0318] In a possible design, when the communication apparatus 900 is a circuit or a chip responsible for communication functions in a terminal device, such as a Modem chip or a System on Chip (SoC) chip or a System in Package (SIP) chip including a Modem core, the function of the processing unit 910 can be implemented by circuitry including one or more processors or processor cores in the chip. The function of the communication unit 920 can be implemented by interface circuitry or data transceiver circuitry on the chip.

[0319] It can be understood that the division of units in the above apparatus is merely a logical division of functions, and each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or part of the units can be integrated on one physical entity, or distributed on different physical entities. In addition, the above functional units can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a certain function is implemented in hardware or software depends on a specific application and design constraint condition of the technical solution. Those skilled in the art can implement the described functions by using different methods for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0320] In one example, the functional units in any of the above communication apparatuses can be one or more integrated circuits configured to implement the above methods, for example, one or more application specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more DSPs, or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0321] In one example, the storage unit 930 can include random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, and / or registers, etc.

[0322] The communication apparatus shown in FIG. 10 is described below. As shown in FIG. 10, the communication apparatus 1000 includes a processor 1010. Optionally, the communication apparatus 1000 further includes an interface circuit 1020 and a memory 1030. The processor 1010 and the interface circuit 1020 are coupled to each other. It can be understood that the interface circuit 1020 can be a transceiver or an input / output interface. The memory 1030 is configured to store instructions executed by the processor 1010 or store input data required by the processor 1010 to execute instructions or store data generated after the processor 1010 executes instructions. The interface circuit 1020 and the memory 1030 are optional modules, which are shown in a dashed box in FIG. 10. In addition, FIG. 10 takes one processor 1010 and one memory 1030 as an example, which actually does not limit the number of the processor 1010 and the memory 1030.

[0323] The communication apparatus 1000 is configured to implement any of the method embodiments shown in FIGS. 3-5, 7 or 8. Optionally, the processor 1010 is configured to implement the functions of the processing unit 910, and the interface circuit 1020 is configured to implement the functions of the communication unit 920.

[0324] For example, the communication apparatus 1000 can be configured to implement the functions of the terminal device or the AF in the method embodiments shown in FIGS. 3 or 4, or implement the functions of the terminal device, the PCF, the AF or the UDR involved in the method embodiments shown in FIGS. 5, 7 or 8.

[0325] When the above communication apparatus 1000 is a chip applied to a certain apparatus (such as the terminal apparatus or the network apparatus described above), the apparatus chip implements the functions of the apparatus in the above method embodiments. The apparatus chip receives information from other modules (such as a radio frequency module or an antenna) in the apparatus, and the information is sent by other apparatuses to the apparatus; or the apparatus chip sends information to other modules (such as a radio frequency module or an antenna) in the apparatus, and the information is sent by the apparatus to other apparatuses. The communication apparatus 1000 here can be a baseband chip of a certain apparatus, or a DU or other modules, and the DU here can be a DU under the open radio access network (O-RAN) architecture.

[0326] The processor 1010 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, or any conventional processor. In addition, the memory involved in various embodiments of the present application can include volatile memory (such as random access memory (RAM)), and can also include non-volatile memory (such as read-only memory (ROM), flash memory, a hard disk drive (HDD), or a solid state drive (SSD)).

[0327] The communication apparatus shown in FIG. 11 is described below. As shown in FIG. 11, the communication apparatus 1100 includes a processor 1110 and a transceiver 1130. The processor 1110 can also be referred to as a processing unit, a processing board, a processing module, a processing device, etc. The implementation of the processor 1110 can refer to the content of the processor 1010 in FIG. 10. The transceiver 1130 can also be referred to as a transceiving unit, a transceiver, a transceiving device, etc. The transceiver 1130 includes a transmitter 1131, a receiver 1132, and an antenna 1133. Optionally, the transceiver 1130 can also include radio frequency circuitry, input / output devices, etc., which are not limited herein.

[0328] Optionally, the devices in the transceiver 1130 for implementing the receiving function are regarded as a receiving module, and the devices in the transceiver 1130 for implementing the sending function are regarded as a sending module, that is, the transceiver 1130 includes a receiver and a transmitter. The transceiver can also be referred to as a transceiver, a transceiving module, or a transceiving circuit, etc. The receiver can also be referred to as a receiver, a receiving module, or a receiving circuit, etc. The transmitter can also be referred to as a transmitter, a transmitting module, or a transmitting circuit, etc.

[0329] Optionally, the communication apparatus 1100 can also include a memory 1120, which can store computer program codes and / or data.

[0330] The processor 1110 is mainly used for processing communication protocols and communication data, controlling the communication device 1100, executing software programs, processing data of the software programs, etc. The memory 1120 is mainly used for storing software programs and data. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of the radio frequency signals. The antenna 1133 is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. The input and output device, such as a touch screen, a display screen, a keyboard, etc., is mainly used for receiving data input by a user and outputting data to the user.

[0331] When data needs to be transmitted, the processor 1110 performs baseband processing on the data to be transmitted, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is transmitted to the communication device 1100, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor 1110 converts the baseband signal into data and processes the data. For the convenience of description, only one memory 1120, one processor 1110 and one transceiver 1130 are shown in FIG. 11. In actual terminal products, there can be one or more processors 1110 and one or more memories 1120. The memory 1120 can also be referred to as a storage medium or a storage device, etc. The memory 1120 can be arranged independently of the processor 1110, or can be integrated with the processor 1110, which is not limited.

[0332] In the embodiments of the present application, the antenna and the radio frequency circuit with the transceiving function are regarded as the communication unit of the communication device 1100, and the processor with the processing function is regarded as the processing unit of the communication device 1100. The processor 1110 is used to execute the processing actions of the terminal device or the application network element in the method embodiments shown in FIG. 3 or FIG. 4, or execute the processing actions of the terminal device, the policy control network element, the application network element or the unified data storage network element involved in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8. The transceiver 1130 is used to execute the transceiving actions of the terminal device or the application network element in the method embodiments shown in FIG. 3 or FIG. 4, or execute the transceiving actions of the terminal device, the policy control network element, the application network element or the unified data storage network element involved in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8.

[0333] When the communication device 1100 is a chip, the chip includes a processor and a transceiver. The transceiver can be an input and output circuit or a communication interface; the processor can be a processing module integrated on the chip or a microprocessor or an integrated circuit. Optionally, the chip can further include a memory. The transmitting operation of the terminal device in the above method embodiments can be understood as the output of the chip, and the receiving operation of the terminal device in the above method embodiments can be understood as the input of the chip.

[0334] Based on the same inventive concept, embodiments of the present application provide a communication system. The communication system comprises a terminal device and an application network element. The terminal device is configured to perform the functions of the terminal device in the method embodiments shown in FIG. 3 or FIG. 4, and the application network element is configured to perform the functions of the application network element in the method embodiments shown in FIG. 3 or FIG. 4.

[0335] Based on the same inventive concept, embodiments of the present application provide a communication system. The communication system comprises a terminal device and a policy control network element. The terminal device is configured to perform the functions of the terminal device in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8, and the policy control network element is configured to perform the functions of the policy control network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8.

[0336] In a possible implementation, the communication system further comprises an application network element and / or a unified data storage network element. The application network element is configured to perform the functions of the application network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8, and the unified data storage network element is configured to perform the functions of the unified data storage network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8. Optionally, the terminal device, the application network element, the policy control network element and the unified data storage network element can also perform the functions of the terminal device, the application network element, the policy control network element and the unified data storage network element involved in FIG. 6, respectively.

[0337] Based on the same inventive concept, embodiments of the present application provide a communication system. The communication system comprises a policy control network element and a unified data storage network element. The policy control network element is configured to perform the functions of the policy control network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8, and the unified data storage network element is configured to perform the functions of the unified data storage network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8.

[0338] In a possible implementation, the communication system further comprises an application network element. The application network element is configured to perform the functions of the application network element in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8.

[0339] In a possible implementation, the communication system further comprises a terminal device. The terminal device is configured to perform the functions of the terminal device in the method embodiments shown in FIG. 5, FIG. 7 or FIG. 8.

[0340] Optionally, the terminal device, the application network element, the policy control network element and the unified data storage network element can also perform the functions of the terminal device, the application network element, the policy control network element and the unified data storage network element involved in FIG. 6, respectively.

[0341] Based on the same inventive concept, the embodiment of the present application provides a chip system, comprising: a processor and an interface. The processor is configured to call and run an instruction from the interface, and when the processor executes the instruction, any one of the method embodiments shown in FIG. 3, FIG. 4, FIG. 5, FIG. 7 or FIG. 8 is implemented.

[0342] Based on the same inventive concept, the embodiment of the present application provides a computer readable storage medium for storing computer programs or instructions, when executed, any one of the method embodiments shown in FIG. 3, FIG. 4, FIG. 5, FIG. 7 or FIG. 8 is implemented.

[0343] Based on the same inventive concept, the embodiment of the present application provides a program product, when executed, the processor implements any one of the method embodiments shown in FIG. 3, FIG. 4, FIG. 5, FIG. 7 or FIG. 8. The program product is, for example, a computer program product, and specifically, for example, a computer program and / or instructions, etc. The processor is, for example, a processor running in a computer.

[0344] In the above embodiments, all or part of them can be realized by software, hardware, firmware or any combination thereof. When realized by software, all or part of them can be realized in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are executed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment or other programmable device. The computer program or instruction can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another, for example, the computer program or instruction can be transferred from one website, computer, server or data center to another by wired or wireless manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; an optical medium, such as a digital video disc; and a semiconductor medium, such as a solid state disk. The computer readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0345] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0346] The various digital numbers involved in the embodiments of the present application are only used for distinguishing conveniently, and do not limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be based on its function and inherent logic.

Claims

1. A communication method characterized by comprising: The method comprises: obtaining a first mapping relationship, the first mapping relationship indicating a mapping relationship between one or more device description information and one or more device identifiers; determining device description information of a first non-3rd Generation Partnership Project (3GPP) device; determining a device identifier of the first non-3GPP device based on the first mapping relationship and the device description information of the first non-3GPP device.

2. The method of claim 1, wherein, The one or more device description information comprises device description information of the first non-3GPP device, and the first mapping relationship indicates a mapping relationship between the device description information of the first non-3GPP device and a plurality of device identifiers, the plurality of device identifiers comprising the device identifier of the first non-3GPP device; The method further comprises: determining device description information of a second non-3GPP device, wherein the device description information of the second non-3GPP device is the same as the device description information of the first non-3GPP device; determining a device identifier of the second non-3GPP device based on the first mapping relationship and the device description information of the second non-3GPP device, the device identifier of the second non-3GPP device being a device identifier of the plurality of device identifiers different from the device identifier of the first non-3GPP device.

3. The method according to claim 1 or 2, characterized in that, After the connection of the first non-3GPP device is disconnected, the method further comprises: determining device description information of a third non-3GPP device, wherein the device description information of the third non-3GPP device is the same as the device description information of the first non-3GPP device; determining a device identifier of the third non-3GPP device based on the first mapping relationship and the device description information of the third non-3GPP device, the device identifier of the third non-3GPP device being the same as the device identifier of the first non-3GPP device.

4. The method according to any one of claims 1 to 3, characterized in that, The obtaining of the first mapping relationship comprises: obtaining the first mapping relationship from a first application network element.

5. The method of claim 4, wherein, Before the first mapping relationship is obtained from the first application network element, the method further comprises: sending the device description information of the first non-3GPP device to the first application network element.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: sending a first message, the first message being used for requesting establishment or modification of a session, the session being used for carrying data of the first non-3GPP device, and the first message comprising the device identifier of the first non-3GPP device.

7. The method according to any one of claims 1 to 6, characterized in that, The device description information of the first non-3GPP device indicates at least one of: a device type of the first non-3GPP device; a quality of service level corresponding to the first non-3GPP device; a device level of the first non-3GPP device; an address of the first non-3GPP device; or a host name of the first non-3GPP device.

8. The method according to any one of claims 1 to 7, characterized in that, The determining of the device description information of the first non-3GPP device comprises: obtaining a second mapping relationship, the second mapping relationship indicating a mapping relationship between a device parameter of the first non-3GPP device and the device description information of the first non-3GPP device; determine the device description information of the first non-3GPP device based on the device parameter of the first non-3GPP device and the second mapping relationship.

9. The method of claim 8, wherein the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameter of the first non-3GPP device is a device level of the first non-3GPP device. The method comprises:

10. A communication method characterized by comprising: sending, to a terminal device, information indicating a first mapping relationship, the first mapping relationship indicating a mapping relationship between one or more device description information and one or more device identifiers, the first mapping relationship being used to determine a device identifier of a non-third generation partnership project (3GPP) device in the terminal device. The method further comprises:

11. The method of claim 10, wherein, receiving the one or more device description information; determining the device identifier corresponding to each of the one or more device description information to establish the first mapping relationship. The method comprises:

12. A communication method, comprising: obtaining one or more rules, each rule of the one or more rules having a traffic descriptor indicating a device description information, the device description information being common to a plurality of non-third generation partnership project (3GPP) devices; from the one or more rules, determining a first rule, the device description information indicated by the traffic descriptor of the first rule matching the device description information of a first non-3GPP device, the first rule being used for determining a session, the session being used to carry data of the first non-3GPP device. The device description information of the first non-3GPP device indicates at least one of:

13. The method of claim 12, wherein, a device type of the first non-3GPP device; a quality of service level corresponding to the first non-3GPP device; or a device level of the first non-3GPP device. The method further comprises:

14. The method according to claim 12 or 13, characterized in that, determining the device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device and a sequence number, the sequence number being used to distinguish the first non-3GPP device from at least one non-3GPP device, the at least one non-3GPP device being connected to a same terminal device as the first non-3GPP device, and the at least one non-3GPP device having the same device description information as the first non-3GPP device. Before determining the device identifier of the first non-3GPP device based on the device description information of the first non-3GPP device and the sequence number, the method further comprises:

15. The method of claim 14, wherein, allocating the sequence number to the first non-3GPP device. The method further comprises:

16. The method according to claim 14 or 15, characterized in that sending a first message, the first message being used to request establishment or modification of a session, and the first message comprising the device identifier of the first non-3GPP device. The method further comprises:

17. The method according to any one of claims 14-16, characterized by, obtaining a second mapping relationship, the second mapping relationship indicating a mapping relationship between a device parameter of the first non-3GPP device and the device description information of the first non-3GPP device; determining the device description information of the first non-3GPP device based on the device parameter of the first non-3GPP device and the second mapping relationship. ​ 18. The method of claim 17, wherein the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameter of the first non-3GPP device is a device level of the first non-3GPP device. The method comprises:

19. A method of communication, comprising: receiving a second message from a terminal device, the second message indicating a device parameter of a first non-3rd Generation Partnership Project, 3GPP, device; sending a third message to the terminal device, the third message indicating a second mapping relationship, the second mapping relationship indicating a mapping relationship between the device parameter of the first non-3GPP device and the device description information of the first non-3GPP device.

20. The method of claim 19, wherein the device description information of the first non-3GPP device indicates a quality of service level of the first non-3GPP device, and the device parameter of the first non-3GPP device is a device level of the first non-3GPP device. The method further comprises: sending a fourth message, the fourth message comprising the device description information of the first non-3GPP device, the fourth message being used for determining a first rule, the first rule being used for determining a session carrying data of the first non-3GPP device.

21. The method of claim 19 or 20, wherein, The method comprises: obtaining device description information, the device description information being common to the first non-3GPP device and at least one non-3GPP device; 22. A method of communication, comprising: sending a rule, a traffic descriptor, TD, of the rule indicating the device description information, the rule being used for determination of a session, the session being used for carrying data of the first non-3GPP device. The method further comprises: receiving a fifth message, the fifth message indicating establishment of a session management policy of a first non-3GPP device, and the fifth message comprising device description information of the first non-3GPP device or a device identifier of the first non-3GPP device, the device identifier of the first non-3GPP device being related to the device description information of the first non-3GPP device; 23. The method of claim 22, wherein, obtaining information of the first non-3GPP device based on the device description information of the first non-3GPP device or the device identifier of the first non-3GPP device, wherein the information of the first non-3GPP device corresponds to the device description information of the first non-3GPP device; determining the session management policy of the first non-3GPP device based on the information of the first non-3GPP device, the session management policy being used for management of the session. The obtaining the information of the first non-3GPP device based on the device description information of the first non-3GPP device or the device identifier of the first non-3GPP device comprises: sending a sixth message, the sixth message being used for requesting the information of the first non-3GPP device, and the sixth message comprising the device description information of the first non-3GPP device; 24. The method of claim 23, wherein, receiving the information of the first non-3GPP device. The method comprises: receiving a sixth message, the sixth message being used for requesting information of a first non-3GPP device, and the sixth message comprising device description information of the first non-3GPP device, the device description information being common to the first non-3GPP device and at least one non-3GPP device; 25. A method of communication, comprising: ​ ​ sending information of the first non-3GPP device, the information of the first non-3GPP device corresponding to the device description information of the first non-3GPP device.

26. The method of claim 25, wherein, The method further comprises: receiving a fourth message from an application network element, the fourth message comprising device description information of the first non-3GPP device; determining the information of the first non-3GPP device according to the fourth message.

27. A communications device, characterized by comprising: a module or unit for performing the method according to any one of claims 1-9; a module or unit for performing the method according to claim 10 or 11; or a module or unit for performing the method according to any one of claims 12-18; or a module or unit for performing the method according to any one of claims 19-21; or a module or unit for performing the method according to any one of claims 22-24; or a module or unit for performing the method according to claim 25 or 26.

28. A communications device, characterized by comprising one or more processors for executing computer programs or instructions in a memory, so that the communication device implements the method according to any one of claims 1-9, or implements the method according to claim 10 or 11, or implements the method according to any one of claims 12-18, or implements the method according to any one of claims 19-21, or implements the method according to any one of claims 22-24, or implements the method according to claim 25 or 26.

29. A computer program product, characterised in that, when the computer program product is executed, the processor performs the method according to any one of claims 1-9, or performs the method according to claim 10 or 11, or performs the method according to any one of claims 12-18, or performs the method according to any one of claims 19-21, or performs the method according to any one of claims 22-24, or performs the method according to claim 25 or 26.

30. A computer-readable storage medium, characterized in that, The storage medium has stored therein computer programs or instructions, when the computer programs or instructions are executed by a communication device, the method according to any one of claims 1-9 is implemented, or the method according to claim 10 or 11 is implemented, or the method according to any one of claims 12-18 is implemented, or the method according to any one of claims 19-21 is implemented, or the method according to any one of claims 22-24 is implemented, or the method according to claim 25 or 26 is implemented.

Images