Communication method and device, equipment and storage medium

Abstract

Provided in an embodiment of the present application are a communication method, apparatus, device and storage medium, the method comprising: a UE sending a PDU session modification request message to a first network function, and receiving a response message to the PDU session modification request message from the first network function, the response message comprising first information, the first information being used to indicate a relationship between a PDU session and a PIN, therefore, the UE can process the PDU session according to the relationship between the PDU session and the PIN, so that the PDU session is matched with the PIN service, and the problem of data transmission error of the PIN service or failure of the PIN service caused by mismatching of the PDU session and the PIN service is avoided.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method, apparatus, device and storage medium. Background Art

[0002] A personal IoT network (PIN) is a network composed of multiple IoT devices. IoT devices can be wearable devices (such as headphones, watches, earphones, health monitors, etc.), smart home appliances (such as smart lights, cameras, thermostats, refrigerators, washing machines), etc., as well as other electronic devices such as mobile terminals and car terminals.

[0003] When the terminal device in the PIN communicates with other devices, it is necessary to use the user equipment (UE) route selection policy (URSP) for traffic routing. In one implementation, the application function (AF) in the new radio (NR) system can provide corresponding guidance to the 5G core network (5Gcore / new generation core, 5GC / NGC) to generate URSP. However, the URSP of the PIN service is different from the ordinary URSP. When the AF provides guidance for the PIN service, the parameters provided by the AF may be incorrect, which will cause the URSP generated by the policy control function (PCF) to be incorrect, and then the terminal device or IoT device uses the wrong URSP route, which will cause data transmission errors or PIN service failures. Summary of the invention

[0004] The embodiments of the present application provide a communication method, apparatus, device, and storage medium, which can avoid data transmission errors or PIN service failures of PIN services.

[0005] In a first aspect, an embodiment of the present application provides a communication method, including: a UE sends a protocol data unit PDU session modification request message to a first network function; the UE receives a response message to the PDU session modification request message from the first network function, the response message including first information, and the first information is used to indicate the relationship between the PDU session and the PIN.

[0006] In a second aspect, an embodiment of the present application provides a communication method, including: a first network function receives a protocol data unit PDU session modification request message from a user equipment UE; the first network function sends a response message to the UE to the PDU session modification request message, and the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the PIN.

[0007] In a third aspect, an embodiment of the present application provides a communication method, including: a fifth network function sends a first terminal policy to a user equipment UE, the first terminal policy including at least one of the following: at least one PIN information, the PIN information including: a PIN identification ID, a data network name DNN dedicated to the PIN, a single network slice selection auxiliary information S-NSSAI dedicated to the PIN; a default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI applicable to all PIN services.

[0008] In a fourth aspect, an embodiment of the present application provides a communication method, including: a sixth network function sends second error type information related to a personal Internet of Things PIN to a seventh network function, wherein the second error type information is used to indicate at least one of the following: an error in the data network name DNN and / or a single network slice selection auxiliary information S-NSSAI, an error in the terminal routing selection strategy URSP parameters, an error in the PDU session parameters, and an error in the parameters provided by the application function AF.

[0009] In a fifth aspect, an embodiment of the present application provides a communication device, comprising: a sending module, used to send a protocol data unit PDU session modification request message to a first network function; a receiving module, used to receive a response message to the PDU session modification request message from the first network function, the response message including first information, and the first information is used to indicate the relationship between the PDU session and the PIN.

[0010] In the sixth aspect, an embodiment of the present application provides a communication device, including: a receiving module, used to receive a protocol data unit PDU session modification request message from a user equipment UE; a sending module, used to send a response message of the PDU session modification request message to the UE, the response message including first information, and the first information is used to indicate the relationship between the PDU session and the PIN.

[0011] In the seventh aspect, an embodiment of the present application provides a communication device, including: a sending module, used to send a first terminal policy to a user equipment UE, the first terminal policy including at least one of the following: at least one PIN information, the PIN information including: a PIN identification ID, a data network name DNN dedicated to the PIN, a single network slice selection auxiliary information S-NSSAI dedicated to the PIN; a default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI applicable to all PIN services.

[0012] In the eighth aspect, an embodiment of the present application provides a communication device, including: a sending module, used to send second error type information related to a personal Internet of Things PIN to a seventh network function, wherein the second error type information is used to indicate at least one of the following: data network name DNN and / or single network slice selection auxiliary information S-NSSAI error, terminal routing selection strategy URSP parameter error, PDU session parameter error, and parameter error provided by the application function AF.

[0013] In a ninth aspect, an embodiment of the present application provides a user device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method described in the first aspect above.

[0014] In the tenth aspect, an embodiment of the present application provides a network function, which includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method described in the second aspect, the third aspect or the fourth aspect above.

[0015] In an eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program, and the computer program enables a computer to execute the method described in any one of the first to fourth aspects above.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method described in any one of the first to fourth aspects above.

[0017] In a thirteenth aspect, an embodiment of the present application provides a communication system, including: a user device and a first network function, wherein the user device is used to execute the method described in the first aspect above, and the first network function is used to execute the method described in the second aspect above.

[0018] Optionally, the communication system further includes a fifth network function, and the fifth network function is used to execute the method described in the third aspect above.

[0019] In a fourteenth aspect, an embodiment of the present application provides a communication system, including: a sixth network function and a seventh network function, wherein the sixth network function and the seventh network function are used to execute the method described in the fourth aspect above.

[0020] In a fifteenth aspect, an embodiment of the present application provides a chip, comprising a processor, wherein the processor is used to call and run a computer program from a memory so that the chip executes the method described in any one of the first to fourth aspects above.

[0021] The communication method, apparatus, device and storage medium provided in the embodiments of the present application send a PDU session modification request message to the first network function through the UE, and receive a response message to the PDU session modification request message from the first network function, wherein the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the PIN, so that the UE can process the PDU session according to the relationship between the PDU session and the PIN, so that the PDU session matches the PIN service, thereby avoiding the problem of data transmission error of the PIN service or PIN service failure caused by the mismatch between the PDU session and the PIN service. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 A schematic diagram of an architecture of an NR system to which this application is applicable;

[0024] Figure 2 A flow chart showing the process of AF instructing the core network equipment to generate URSP;

[0025] Figure 3 is a flow chart of the communication method provided in Embodiment 1 of the present application;

[0026] Figure 4 is a flow chart of the communication method provided in Embodiment 2 of the present application;

[0027] Figure 5 is a signaling flow chart of the communication method provided in Embodiment 3 of the present application;

[0028] Figure 6 It is a signaling flow chart of the communication method provided in Embodiment 4 of the present application;

[0029] Figure 7A flow chart of a communication method provided in Embodiment 5 of the present application;

[0030] Figure 8 A signaling flow chart of the communication method provided in Embodiment 6 of the present application;

[0031] Fig. 9 A signaling flow chart of the communication method provided in Embodiment 7 of the present application;

[0032] Fig.10 A flow chart of a communication method provided in Embodiment 8 of the present application;

[0033] Fig.11 A schematic diagram of the structure of a communication device provided in Embodiment 9 of the present application;

[0034] Fig.12 A schematic diagram of the structure of a communication device provided in Embodiment 10 of the present application;

[0035] Fig.13 A schematic diagram of the structure of a communication device provided in Example 11 of the present application;

[0036] Fig.14 A structural diagram of a UE provided in Embodiment 13 of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0038] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0039] The communication method provided in the embodiment of the present application can be applied in an existing communication system, which includes but is not limited to a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a NR system, a next generation communication system or other communication systems, etc. The terms "system" and "network" in the embodiments of the present application are often used interchangeably.

[0040] Figure 1 A schematic diagram of the architecture of the NR system to which this application is applicable is shown in FIG. Figure 1 As shown, the NR system includes UE, (radio) access network ((radio) access network, (R)AN) and core network.

[0041] The NR system is also called the 5G system. The (R)AN equipment in the 5G system may include: non-3rd Generation partnership project (non-3GPP) access networks such as access points (APs) of WiFi networks, next-generation base stations (collectively referred to as next-generation radio access network nodes (NG-RAN nodes)), where the next-generation base stations include new air interface base stations (NR nodeB, gNB), new-generation evolved base stations (NG-eNB), separated gNBs, etc., transmission receive points (TRPs), transmission points (TPs) or other nodes.

[0042] The 5G core network (5G core, 5GC) includes but is not limited to the following network function network elements: access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), user plane function (user plane function, UPF), authentication server function (authentication server function, AUSF), PCF, AF, unified data management function (unified data management, UDM), network slice selection function (network slice Selection function, NSSF), etc.

[0043] AMF is mainly responsible for services such as mobility management and access management. SMF is mainly responsible for session management, UE address management and allocation, dynamic host configuration protocol functions, selection and control of user plane functions, etc. UPF is mainly responsible for external connection to the data network (DN) and data packet routing and forwarding, message filtering, and execution of service quality control related functions on the user plane. AUSF is mainly responsible for UE authentication functions, etc. PCF is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions. It should be noted that these functional units can work independently or be combined to implement certain control functions.

[0044] Although Figure 1 Not shown, the 5G core network may also include other network elements, such as a unified data repository (UDR) and a network exposure function (NEF). UDR is mainly used to store the contract data and policy data of UDM and PCF. The main function of NEF is to expose the capabilities of the 5G system to the external network. At the same time, NEF can also accept information from the outside and manage the update of some network information.

[0045] UE can be called terminal equipment or terminal. UE can be a mobile phone, a laptop computer or a notebook computer, or a tablet personal computer, an extended reality (XR) device, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal-side devices. Wearable devices include: bracelets, headphones, glasses, etc. It should be noted that the specific type of UE is not limited in the embodiments of the present application.

[0046] When the UE communicates with other devices, it needs to use URSP for traffic routing. In one implementation, the AF network element in the NR system can provide corresponding guidance to the 5G core network to generate URSP. For PIN services, the AF can also provide guidance to the 5G core network to generate URSP.

[0047] Figure 2 The flowchart of the AF guiding the core network device to generate URSP is shown in FIG. This flowchart is applicable not only to generating URSP for PIN services, but also to generating URSP for other services, such as Figure 2 As shown, the process includes the following steps.

[0048] S101. AF creates an AF request (AF request).

[0049] AF creates AF requests based on services triggered by users.

[0050] S102. The AF sends a service parameter create / update / delete request (Nnef_ServiceParameter_Create / Update / Delete Request) to the NEF.

[0051] When AF creates an AF request for a service for the first time, it sends a service parameter creation request to NEF. When the service parameters of AF are wrong or in other situations, AF sends a service parameter update request or a service parameter deletion request to NEF.

[0052] S102a: NEF and UDM obtain UE subscription data from UDR.

[0053] NEF and UDM can obtain UE subscription data through Nudm_SDM_get message.

[0054] S102b, NEF and UDM authenticate service parameters according to UE subscription data.

[0055] NEF and UDM authenticate the service parameters requested by AF based on the UE subscription data obtained from UDR. The service parameters requested by AF are also called parameters provided by AF or AF parameters. The service parameters requested by AF include parameters used to generate URSP for PIN service or other services.

[0056] S103. NEF stores / updates / deletes service parameters in UDR.

[0057] When NEF receives a service parameter creation request sent by AF, NEF stores the service parameters requested by AF in UDR; when NEF receives a service parameter update / delete request sent by AF, NEF updates / deletes the service parameters requested by AF stored in UDR.

[0058] The UDR may store the service parameters requested by the AF as application data, and specifically may store the service parameters requested by the AF in a data subset named service specific information.

[0059] S104. NEF sends a service parameter create / update / delete response (Nnef_ServiceParameter_Create / Update / Delete Response) to AF.

[0060] S105. UDR sends a data modification (DM) notification (Nudr_DM_Notify) to PCF.

[0061] When the UDR data changes, the UDR will trigger the PCF to update the UE policy.

[0062] S106: UE policy update is performed between the PCF and the UE.

[0063] The PCF updates the UE policy according to the Nudr_DM_Notify sent by the UDR. The UE policy includes but is not limited to the URSP.

[0064] S107. PCF sends an event exposure notification (Npcf_EventExposure_Notify) to NEF.

[0065] S108. NEF sends a service parameter notification (Npcf_ServiceParameter_Notify) to AF.

[0066] Figure 2 The process shown in the figure can generate and update URSP by PCF, and URSP can be used to describe the correspondence between UE application traffic and network slices. A URSP includes a traffic descriptor (TD) and a route selection descriptor (RSD).

[0067] TD may include application descriptors (such as APP ID), internet protocol (IP) descriptors, domain descriptors, non-IP descriptors, and data network name (DNN) descriptors, etc.

[0068] RSD may include network slice selection strategy, DNN selection strategy, PDU session selection strategy, access type priority, etc. Among them, the network slice selection strategy may include single network slice selection assistance information (S-NSSAI), and the DNN selection strategy includes DNN.

[0069] The URSP for PIN service is different from the URSP for ordinary service. If a URSP serves the PIN service, its TD only contains the PIN ID (no other components), and the RSD contains a DNN and / or S-NSSAI specifically for PIN. The DNN or S-NSSAI specifically for PIN is also called a DNN or S-NSSAI dedicated to PIN.

[0070] When AF provides guidance for PIN services, the following errors may occur:

[0071] (1) PIN ID is provided in TD, but DNN or S-NSSAI in RSD is not dedicated to PIN.

[0072] (2) The PIN ID is not provided in TD, but the DNN or S-NSSAI in RSD is dedicated to the PIN.

[0073] (3) The PIN ID is provided in TD, but the DNN or S-NSSAI in RSD is not provided.

[0074] (4) AF only provides the PIN ID, but NEF does not use the PIN-specific DNN or S-NSSAI when supplementing the parameters for AF.

[0075] The URSP generated by the PCF based on missing (e.g. missing PIN ID) or incorrect parameters (e.g. DNN and / or S-NSSAI errors) may have the following three types of error strategies:

[0076] The first type of error strategy: TD contains the PIN ID and other components, and the RSD is the DNN and / or S-NSSAI dedicated to the PIN.

[0077] The second type of error strategy: TD contains the PIN ID, and the RSD contains DNN and / or S-NSSAI that are not dedicated to the PIN.

[0078] The third type of error strategy: TD does not contain the PIN ID, and the RSD contains the DNN and / or S-NSSAI dedicated to the PIN.

[0079] It should be noted that the DNN and / or S-NSSAI errors mentioned here are relative to the PIN service. DNN and / or S-NSSAI are not dedicated to PIN, so the PCF considers that DNN and / or S-NSSAI are erroneous.

[0080] For the first type of error strategy, the UE will ignore other components in the TD and use the PIN ID for PIN related services. In other words, this type of error strategy will not affect the UE.

[0081] For the second type of error strategy, the UE will use DNN / S and / or NSSAI that are not dedicated to PIN to establish a PDU session. The DNN / S-NSSAI of the established PDU session is not dedicated to PIN, which will affect the UE's traffic routing, resulting in UE data transmission errors or PIN service failures.

[0082] For the third type of error strategy, since the TD does not contain the PIN ID and the UE wants to use the PIN service, the UE will not use this URSP to establish a PDU session according to the current mechanism. In other words, this type of error strategy will not affect the UE, but may cause the UE to have no URSP available when it wants to use the PIN service.

[0083] In order to avoid the impact of the URSP error of the PIN service on the terminal, the embodiment of the present application provides a communication method, which can judge or modify the correctness of the parameters used to generate the URSP of the PIN service by the core network device before the PCF updates the URSP to the UE, so that the PCF can use the correct parameters to generate the URSP of the PIN service. Alternatively, when the PCF generates the URSP of the PIN service according to the wrong parameters, that is, when the generated URSP of the PIN service is wrong, the UE or SMF handles the error caused by the wrong URSP, thereby avoiding the impact of the wrong URSP on the terminal.

[0084] The following is a brief description of PIN related content.

[0085] In the embodiment of the present application, PIN is a network composed and derived from a large number of consumer IoT devices. These devices can be wearable devices (i.e., devices on the body, such as cameras, headphones, watches, earphones, health monitors, etc.), or IoT devices at home (such as smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, washing machines, etc.). Users mainly use all these personal IoT devices at home or around their bodies to create PINs. Generally speaking, PINs are generally used in scenarios such as homes and offices. IoT devices deployed in these scenarios can be interconnected, communicate with each other, and obtain services, so they are called personal IoT. At the same time, there is another point to explain that the IoT devices in the PIN can access the 5G network, access other servers on the network, or complete business through a device with gateway function in the PIN through a certain mechanism and implementation.

[0086] The terminal or device in a PIN is called a PIN element (PINE), which is the basic element that constitutes a PIN.

[0087] The PIN consists of a set of PIN elements that can communicate with each other directly or through PIN elements with gateway capability (PEGC), communicate with the 5G network through at least one PEGC, and be managed by at least one PIN element with management capability (PEMC).

[0088] PEMC manages the entire PIN, for example, adding a PINE to the PIN managed by PEMC, or deleting a PIN in the PIN.

[0089] PEGC is responsible for routing the traffic of PINE to the destination. For example, if a PINE wants to communicate with other PINEs in the PIN, it can be routed through PEGC. Taking the home scenario as an example, the mobile phone and smart home appliances (such as smart speakers, air conditioners, TVs, refrigerators, etc.) at home form a PIN. At this time, the mobile phone can be used as a PEGC. Smart home appliances at home connect to the network and communicate through the mobile phone. The traffic of smart home appliances needs to be forwarded through PEGC.

[0090] When the devices in the PIN communicate with each other in the PIN, they can communicate through the PIN direct connection, or through PEGC, or through PEGC and 5GC. Each device in the PIN can communicate with devices outside the PIN through PEGC and 5GC.

[0091] The following is a detailed description of the communication method provided by the embodiments of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings. The following embodiments may be combined with each other, and the same or similar concepts and processes may not be repeated in some embodiments.

[0092] Embodiment 1

[0093] Figure 3 is a flow chart of a communication method provided in Embodiment 1 of the present application. This embodiment describes the communication method from the UE side, such as Figure 3 As shown, the method provided in this embodiment includes the following steps.

[0094] S201. UE sends a PDU session modification request message to a first network function.

[0095] The first network function includes but is not limited to SMF, and this embodiment is described by taking SMF as an example. Before the UE sends a PDU session modification request message to the first network function, the UE can match the URSP, and if the match is successful, a PDU session is established according to the successfully matched URSP, and a suitable PDU session can be established for the current service of the UE by matching the URSP, and the data of the current service of the UE can be transmitted using the appropriate PDU session.

[0096] Exemplarily, the UE matches the URSP in the following manner: the UE obtains the TD parameters associated with the application, matches the obtained TD parameters with the TD parameters in the URSP, and determines the successfully matched URSP as the target URSP. Then, the UE establishes a PDU session for the application according to the RSD in the target URSP, and the DNN and / or S-NSSAI of the established PDU session is the DNN and / or S-NSSAI in the RSD.

[0097] The URSP used by the UE may be preconfigured or received from the network side. For example, the fifth network function on the network side sends a first terminal policy to the UE, the first terminal policy may be the URSP, and the fifth network function may be the PCF.

[0098] The preconfigured URSP may be stored in the mobile equipment (ME) or the Universal Integrated Circuit Card (UICC) of the UE.

[0099] Optionally, the URSP of the PIN service includes at least one of the following: at least one PIN information, the PIN information including: PIN ID, DNN dedicated to the PIN, S-NSSAI dedicated to the PIN; a default TD applicable to all PIN services; DNN and / or S-NSSAI applicable to all PIN services. In some implementations, the default TD is a default PIN ID.

[0100] In this embodiment, the network side configures a URSP for the UE, the purpose of which is to allow the UE supporting the PIN service to have at least one URSP that can be used to support the PIN service. For example, if the policy configured on the network side does not contain other DNNs and / or S-NSSAIs dedicated to the PIN service, the UE can match the current PIN service through the default TD applicable to all PIN services, which can solve the problem of no corresponding URSP when the UE needs to use the PIN service.

[0101] In some implementations, the UE may also configure at least one of the following in the local configuration: at least one PIN information, the PIN information including: PIN ID, DNN dedicated to PIN, S-NSSAI dedicated to PIN; default TD applicable to all PIN services; DNN and / or S-NSSAI applicable to all PIN services. It can be understood that this is to solve the problem that if all URSPs configured on the network side do not contain URSPs related to PIN, for example, the URSP does not contain PIN ID, DNN dedicated to PIN, or S-NSSAI dedicated to PIN, the UE can use the configuration information in the above local configuration to select a PDU session for transmission of PIN services.

[0102] The URSP of the PIN service sent by the network side may be correct or incorrect. For example, the PCF generates an incorrect URSP for the PIN service based on missing or incorrect information, and updates the incorrect URSP to the UE.

[0103] The erroneous URSP generated by PCF for the PIN service based on missing or incorrect information may have the above three types of error strategies. The embodiment of the present application mainly solves the above second type of error, that is, TD contains PIN ID, and RSD contains DNN and / or S-NSSAI that are not dedicated to PIN.

[0104] In PIN, there is usually a UE as a PEGC that matches the URSP and establishes a PDU. For example, when the UE is a PEGC in the PIN, if the UE wants to use the PIN service, the UE matches the URSP. If the network side does not send down the URSP, the UE uses the pre-configured URSP. If the network side sends down the URSP, the UE uses the URSP sent by the network side. If the URSP is pre-configured for the UE and the network side sends down the URSP, different priorities can be set for the pre-configured URSP and the URSP sent by the network side, and the UE matches according to the priority of the URSP.

[0105] Exemplarily, when the priority of the URSP sent by the network side is higher than the priority of the pre-configured URSP, the UE preferentially matches the URSP sent by the network side. When the URSP sent by the network side fails to match, for example, when there is no PIN ID in the URSP sent by the network side, the UE matches the pre-configured URSP.

[0106] When the UE matches the PIN ID through URSP and the RSD contains DNN and / or S-NSSAI, the UE uses the DNN and / or S-NSSAI contained in the RSD to establish a PDU session with the SMF. The SMF accepts the PDU session, which is used for subsequent transmission of PIN service data.

[0107] For the URSP of the PIN service, the PDU session established by the UE based on the correct URSP (which may be pre-configured or sent by the network side) is dedicated to the PIN, and the PDU session established by the UE based on the incorrect URSP is not dedicated to the PIN.

[0108] When the PDU session established by the UE based on the wrong URSP is not dedicated to the PIN, the UE matches the PINID, so the UE believes that the PDU session it established is dedicated to the PIN. However, from the perspective of the SMF, the PDU session established by the UE using a DNN / S-NSSAI that is not dedicated to the PIN is a common PDU session, not a PDU session dedicated to the PIN.

[0109] After the UE establishes a PDU session, if the UE believes that it has established a PDU session dedicated to PIN, it will initiate a PDU session modification process to provide the SMF with a non-3GPP delay budget. The PDU session modification request message includes information indicating the non-3GPP delay budget. The UE believes that it has established a PDU session dedicated to PIN in the following two cases: the UE actually establishes a PDU session dedicated to PIN; the PDU session established by the UE based on the wrong URSP is not dedicated to PIN, but the UE believes that it has established a PDU session dedicated to PIN.

[0110] S202. The UE receives a response message to a PDU session modification request message from a first network function, where the response message includes first information, where the first information is used to indicate a relationship between the PDU session and the PIN.

[0111] After receiving the PDU session modification request message, the first network function determines the relationship between the PDU session and the PIN according to the PDU session modification request message, and the relationship between the PDU session and the PIN includes any of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

[0112] Optionally, the PDU session is not dedicated to the PIN and satisfies at least one of the following: the DNN and / or S-NSSAI are not dedicated to the PIN, the PDU session parameters are not dedicated to the PIN, and the URSP does not contain the PIN ID.

[0113] Optionally, the PDU session is dedicated to the PIN and satisfies at least one of the following: DNN and / or S-NSSAI are dedicated to the PIN, and PDU session parameters are dedicated to the PIN.

[0114] When the PDU session is dedicated to the PIN, the first network function may return a PDU session modification accept message to the UE, wherein the PDU session modification accept message includes first information, and the first information is used to indicate that the PDN session is dedicated to the PIN, and the UE may use the PDU session normally.

[0115] When the PDU session is not dedicated to the PIN, the first network function can choose to accept or reject the PDU session modification and return a response message to the PDU session modification request message to the UE. Accordingly, the response message can be a PDU session modification rejection message or a PDU session modification acceptance message.

[0116] When the response message is a PDU session modification reject message, the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, the PDU session is not dedicated to PIN, and the PDU session parameter error.

[0117] In some implementations, after receiving the PDU session modification rejection message, the UE may release the PDU session according to the first information, and optionally, the SMF may also release the PDU session. Since the PDU session is not applicable to the PIN service, the SMF or the UE avoids the waste of PDU session resources by releasing the PDU session.

[0118] When the response message is a PDU session modification accept message, the PDU session modification accept message satisfies at least one of the following: the PDU session modification accept message includes first information, and the first information is used to indicate at least one of the following: the PDU session is not dedicated to PIN, and the PDU session is modified to be applicable to PIN; the PDU session modification accept message also includes: DNN and / or S-NSSAI dedicated to PIN service.

[0119] After the UE receives the PDU session modification acceptance message, if the PDU session modification acceptance message does not include the DNN and / or S-NSSAI dedicated to the PIN service, the UE modifies the PDU session to be suitable for PIN according to the first information, that is, modifies the DNN and / or S-NSSAI of the PDU session to the DNN and / or S-NSSAI dedicated to the PIN service, and sends the modified DNN and / or S-NSSAI dedicated to the PIN service to the first network function.

[0120] If the PDU session modification accept message includes the DNN and / or S-NSSAI dedicated to the PIN service, the UE modifies the DNN and / or S-NSSAI of the PDU session to the DNN and / or S-NSSAI dedicated to the PIN service indicated by the first network function according to the first information.

[0121] Optionally, after receiving the PDU session modification acceptance message, the UE may not modify the DNN and / or S-NSSAI of the PDU session, but choose to release the PDU session.

[0122] It should be noted that the DNN and / or S-NSSAI errors indicated by the first information are relative to the PIN service. For a PIN service, if the DNN and / or S-NSSAI are not dedicated to the PIN, the SMF considers that the DNN and / or S-NSSAI are erroneous. The PDU session parameters include the DNN and / or S-NSSAI of the PDU, and the PDU session parameter errors include the DNN and / or S-NSSAI errors of the PDU session or the DNN and / or S-NSSAI of the PDU session are not dedicated to the PIN. Therefore, in the embodiments of the present application, in some cases, the DNN and / or S-NSSAI errors have the same meaning as the PDU session parameter errors, and the two errors can be replaced with each other.

[0123] In this embodiment, the PDU session is not dedicated to PIN, which can be understood as the PDU session does not match the PIN service, the PDU session is not suitable for transmitting the PIN service, and using the PIN session to transmit the PIN service will cause the PIN service to fail or the data transmission error of the PIN service.

[0124] In this embodiment, the UE sends a PDU session modification request message to the first network function, and receives a response message to the PDU session modification request message from the first network function, where the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the PIN, so that the UE processes the PDU session according to the relationship between the PDU session and the PIN, so that the PDU session matches the PIN service, thereby avoiding the problem of data transmission errors or PIN service failures of the PIN service caused by the mismatch between the PDU session and the PIN service.

[0125] Embodiment 2

[0126] On the basis of the first embodiment, the second embodiment of the present application provides a communication method. This embodiment describes the communication method from the first network function side. Figure 4 is a flow chart of the communication method provided in Embodiment 2 of the present application, such as Figure 4 As shown, the method provided in this embodiment includes the following steps.

[0127] S301. A first network function receives a PDU session modification request message from a UE.

[0128] The first network function includes but is not limited to SMF, and this embodiment is described by taking SMF as an example. The PDU session modification request message is sent by the UE after the UE believes that it has established a PDU session dedicated to the PIN, and the PDU session modification request message is used to provide the SMF with a non-3GPP delay budget, and the PDU session modification request message includes information indicating the non-3GPP delay budget.

[0129] The first network function receives the PDU session modification request message, and determines the relationship between the PDU session and the PIN according to the PDU session modification request message. The relationship between the PDU session and the PIN includes any of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

[0130] Exemplarily, the first network function may determine that the PDU session is not dedicated to a PIN based on at least one of the following: the PDU session modification request message includes information indicating a non-3GPP delay budget, and the DNN and / or S-NSSAI of the PDU session is not dedicated to the PIN.

[0131] There is non-3GPP delay budget only in PIN service. Therefore, only when the PDU session is used for PIN service, the UE carries information indicating non-3GPP delay budget in the PDU session modification request message. If the PDU session is not used for PIN service, the UE does not carry information indicating non-3GPP delay budget in the PDU session modification request message.

[0132] After receiving the PDU session modification request message, the first network function determines whether the PDU session modification request message carries information indicating the non-3GPP delay budget, obtains the DNN and / or S-NSSAI of the PDU session from the PDU session parameters, determines whether the DNN and / or S-NSSAI of the PDU session are dedicated to the PIN, and determines the relationship between the PDU session and the PIN according to the determination result. When the PDU session is established, the first network function saves the parameters of the PDU session, and the parameters of the PDU session include the DNN and / or S-NSSAI of the PDU session.

[0133] When the PDU session modification request message includes information indicating a non-3GPP delay budget, and the DNN and / or S-NSSAI of the PDU session is not dedicated to the PIN, the first network function determines that the PDU session is not dedicated to the PIN.

[0134] When the PDU session modification request message includes information indicating a non-3GPP delay budget, and the DNN and / or S-NSSAI of the PDU session is dedicated to the PIN, the first network function determines that the PDU session is dedicated to the PIN.

[0135] When the PDU session modification request message does not include information indicating the non-3GPP delay budget, and the DNN and / or S-NSSAI of the PDU session are not dedicated to the PIN, it is determined that the PDU session is not dedicated to the PIN.

[0136] When the PDU session modification request message does not include information indicating the non-3GPP delay budget, and the DNN and / or S-NSSAI of the PDU session are DNN and / or S-NSSAI dedicated to the PIN, it is determined that the PDU session is dedicated to the PIN.

[0137] S302. The first network function sends a response message to the PDU session modification request message to the UE, where the response message includes first information, where the first information is used to indicate a relationship between the PDU session and the PIN.

[0138] After the first network function determines the relationship between the PDU session and the PIN, it generates first information indicating the relationship between the PDU session and the PIN, and carries the first information in a response message of the PDU session modification request message to the UE. The response message may be a PDU session modification rejection message or a PDU session modification acceptance message.

[0139] When the PDU session is dedicated to the PIN, the first network function may return a PDU session modification accept message to the UE, wherein the PDU session modification accept message includes first information, and the first information is used to indicate that the PDN session is dedicated to the PIN, and the UE may use the PDU session normally.

[0140] When the PDU session is not dedicated to the PIN, the first network function can choose to accept or reject the PDU session modification and return a response message to the PDU session modification request message to the UE. Accordingly, the response message can be a PDU session modification rejection message or a PDU session modification acceptance message.

[0141] When the PDU session is not dedicated to PIN and the first network function returns a PDU session modification reject message to the UE, the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, the PDU session is not dedicated to PIN, and the PDU session parameter error.

[0142] Optionally, the first network function may release the PDU session after sending a PDU session modification reject message to the UE. Optionally, the UE may release the PDU session after receiving the PDU session modification reject message.

[0143] When the PDU session is not dedicated to PIN and the first network function returns a PDU session modification accept message to the UE, the PDU session modification accept message satisfies at least one of the following: the PDU session modification accept message includes first information, and the first information is used to indicate at least one of the following: the PDU session is not dedicated to PIN and the PDU session is modified to be applicable to PIN; the PDU session modification accept message also includes: DNN and / or S-NSSAI dedicated to PIN service.

[0144] The DNN and / or S-NSSAI dedicated to the PIN service included in the PDU session modification acceptance message is the DNN and / or S-NSSAI modified by the first network function from the locally stored DNN and / or S-NSSAI of the PDU session when it is determined that the PDU session is not dedicated to the PIN. The DNN and / or S-NSSAI modified by the first network function is the DNN and / or S-NSSAI dedicated to the PIN service.

[0145] Optionally, when the first network function determines that the PDU session is not dedicated to the PIN, the first network function sends first error type information to the second network function, the third network function or the fourth network function, where the first error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session parameter error, parameter error provided by the AF, and PIN service parameter error.

[0146] The PDU session parameter error includes the DNN and / or S-NSSAI error of the PDU session. The parameter error provided by the AF refers to the parameter error provided by the AF for generating the URSP, including but not limited to one or more errors in the PIN ID, DNN and S-NSSAI. The PIN service parameters include the PIN ID, DNN and S-NSSAI. The PIN service parameter error includes one or more errors in the PIN ID, DNN and S-NSSAI. It should be noted that in some cases, the four errors indicated by the first error type information have the same meaning and can be replaced with each other.

[0147] Optionally, the second network function is AF, the third network function is NEF, and the fourth network function is PCF. The first network function sends the first error type information to AF, NEF or PCF, so that AF, NEF or PCF modifies or deletes the parameters provided by AF.

[0148] Optionally, the first error type information is carried in an event exposure notification (Event Exposure Notify). Of course, the first error type information may also be carried in other messages, which is not limited in this embodiment.

[0149] The first error type information is indicated by an error type value (failure Cause), which may be a newly defined error type value or an existing error type value. When an existing error type value is used to represent the first error type information, the description of the existing error type value needs to be expanded.

[0150] In this embodiment, the first network function receives a PDU session modification request message from the UE, determines the relationship between the PDU session and the PIN according to the PDU session modification request message, and sends a response message to the PDU session modification request message to the UE, the response message including first information, and the first information is used to indicate the relationship between the PDU session and the PIN. When the relationship between the PDU session and the PIN is that the PDU session is not dedicated to the PIN, the first network function can process the PDU session, and instruct the UE to process the PDU session through the first information, so that the PDU session matches the PIN service, avoiding the problem of data transmission error of the PIN service or PIN service failure caused by the mismatch between the PDU session and the PIN service.

[0151] Embodiment 3

[0152] Based on the first and second embodiments, the third embodiment of the present application provides a communication method. The implementation methods recorded in the first and second embodiments can be applied to the fifth embodiment and can achieve the same technical effect. This embodiment is explained by taking the example that the SMF determines that the PDU session is not dedicated to the PIN and refuses to modify the PDU session. Figure 5 is a signaling flow chart of the communication method provided in Example 3 of the present application, such as Figure 5 As shown, the method provided in this embodiment includes the following steps.

[0153] S401: UE policy is transmitted between PCF and UE.

[0154] The UE policy includes the URSP for the PIN service, and the DNN and / or S-NSSAI of the URSP for the PIN service are wrong.

[0155] The PCF and the UE can communicate UE policies through one or more messages. The UE policy includes the UESP for the PIN service. It is understandable that the UE policy also includes other policies. The PCF generates an incorrect URSP for the PIN service based on missing or incorrect information, that is, the DNN and / or S-NSSAI errors of the URSP of the PIN service are incorrect. The DNN and / or S-NSSAI errors of the URSP of the PIN service refer to the second type of error policy mentioned above, that is, the TD contains the PIN ID, and the RSD contains the DNN and / or S-NSSAI that are not dedicated to the PIN.

[0156] It is understandable that the URSP generated by the PCF for the PIN service based on missing or erroneous information is not limited to the second type of error strategy mentioned above, but also includes the first error strategy and the third type of error strategy mentioned above. The embodiment of the present application is mainly used to process the second type of error strategy.

[0157] S402. UE and SMF establish a PDU session using the incorrect DNN and / or S-NSSAI in the URSP of the PIN service.

[0158] When the TD of the URSP of the PIN service contains a PIN ID and the RSD contains a DNN and / or S-NSSAI that is not dedicated to the PIN, when the UE expects to use the PIN service, it can match the PIN ID through the URSP, and the RSD contains a DNN and / or S-NSSAI. Then the UE uses the DNN and / or S-NSSAI in the URSP to establish a PDU session. The DNN and / or S-NSSAI in the URSP is not dedicated to the PIN. Therefore, for the PIN service, the DNN and / or S-NSSAI in the URSP is incorrect.

[0159] S403. The UE sends a PDU session modification request message to the SMF, where the PDU session modification request message includes information indicating a non-3GPP delay budget.

[0160] Since the UE matches the PIN ID when matching the URSP, the UE believes that the PDU session it has established is dedicated to the PIN, so the UE initiates a PDU session modification request message to provide the SMF with a non-3GPP delay budget.

[0161] After the SMF receives the PDU session modification request message, it determines that the PDU session is not dedicated to the PIN based on the information used to indicate the non-3GPP delay budget included in the PDU session modification request message and the DNN and / or S-NSSAI of the PDU session stored locally, wherein the DNN and / or S-NSSAI of the PDU session stored locally by the SMF is not dedicated to the PIN.

[0162] S404. SMF sends a PDU session modification reject message to the UE, where the PDU session modification reject message includes the first information.

[0163] After the SMF determines that the PDU session is not dedicated to the PIN, it sends a PDU session modification reject message to the UE. The PDU session modification reject message includes first information, and the first information is used to indicate the reason why the SMF rejects the PDU session modification request.

[0164] Optionally, the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session not dedicated to PIN, PDU session parameter error.

[0165] The first information may be a newly defined error cause value or an existing error cause value. When the first information adopts an existing error cause value, the existing error cause value needs to be expanded. For example, the first information adopts a 5GSM cause value in the related art. Exemplarily, the existing 5GSM cause values ​​include:

[0166] Cause#31–Request rejected,unspecified

[0167] Cause#32–Service option not supported

[0168] Cause#33–Requested service option not subscribed

[0169] Cause #38–Network failure.

[0170] S405. SMF or UE triggers PDU session release.

[0171] Optionally, the PDU session release process can be triggered by SMF or by UE, where the PDU session release process triggered by SMF is also called the PDU session release process requested by the network, and the PDU session release process triggered by UE is also called the PDU session release process requested by the terminal.

[0172] S406. The SMF sends first error type information to the PCF.

[0173] This step is an optional step. After releasing the PDU session, SMF may not report the first error type information to the core network.

[0174] The first error type information is used to indicate at least one of the following: a DNN and / or S-NSSAI error of a PDU session, a PDU session parameter error, a parameter error provided by an AF, or a PIN service parameter error.

[0175] The first error type information may use a newly defined error type value or an existing error type value.

[0176] S407. The PCF sends first error type information to the NEF.

[0177] S408: NEF updates or deletes the parameters provided by AF and stored in UDR.

[0178] The parameters provided by the AF refer to parameters provided by the AF for generating the URSP, including but not limited to NDD and / or S-NSSAI.

[0179] This step is an optional step. After receiving the first error type information sent by PCF, NEF may not update or delete the AF-provided parameters stored in UDR, but directly execute step S309 to send the first error type information to AF, and AF initiates the update or deletion of the AF-provided parameters stored in UDR.

[0180] S409: NEF sends first error type information to AF.

[0181] If the NEF executes step S408, this step is an optional step. Since the NEF has updated or deleted the parameters provided by the AF and stored in the UDR, the first error type information may not be sent to the AF.

[0182] If the NEF does not execute step S408, after the AF receives the first error type information sent by the NEF, the AF may initiate an update or deletion of the AF-provided parameters stored in the UDR. Specifically, the AF sends a service parameter update request or a service parameter deletion request to the NEF. The service parameter update request is used to update the parameters provided by the AF, and the service parameter deletion request is used to delete the parameters provided by the AF. After receiving the service parameter update request or the service parameter deletion request, the NEF deletes the AF-provided parameters stored in the UDR.

[0183] The update or deletion of the AF-provided parameters stored in the UDR is initiated by NEF or AF, so that no incorrect AF-provided parameters are stored in the UDR, that is, all the parameters stored in the UDR are correct AF-provided parameters. Therefore, the AF-provided parameters obtained by the PCF from the UDR when generating the URSP are correct parameters, thereby ensuring that the URSP of the PIN service is correct.

[0184] Optionally, in steps S406, S407 and S408, the SMF, PCF and NEF send the first error type information through Event ExposureNotify.

[0185] In this embodiment, when the DNN and / or S-NSSAI of the URSP of the PIN service generated by the PCF is wrong, the SMF determines that the DNN and / or S-NSSAI of the PDU session are not dedicated to the PIN based on the PDU session modification request sent by the UE and the DNN and / or S-NSSAI of the PDU session, thereby rejecting the PDN session modification and sending the rejection reason to the UE, so that the established PDU session matches the PIN service, avoiding the problem of data transmission error or PIN service failure of the PIN service caused by the mismatch between the PDU session and the PIN service. Furthermore, the SMF can also send the first error type information to the core network device so that the core network device modifies or deletes the parameters provided by the AF stored in the UDR, ensuring that the parameters provided by the AF stored in the UDR are correct, thereby ensuring that the URSP of the PIN service generated according to the parameters provided by the AF stored in the UDR is correct.

[0186] Embodiment 4

[0187] On the basis of Embodiment 1 and Embodiment 2, Embodiment 4 of the present application provides a communication method, and the implementation methods recorded in Embodiment 1 and Embodiment 2 can be applied to Embodiment 5, and can achieve the same technical effect. The difference between this embodiment and Embodiment 3 is that: when the SMF determines that the PDU session is not dedicated to the PIN, the SMF chooses to accept the PDU session and modifies the parameters of the PDU session so that the modified PDU session is applicable to the PIN. Figure 6 is a signaling flow chart of the communication method provided in Embodiment 4 of the present application, such as Figure 6 As shown, the method provided in this embodiment includes the following steps.

[0188] S501: UE policy is transferred between PCF and UE.

[0189] The UE policy includes the URSP for the PIN service, and the DNN and / or S-NSSAI of the URSP for the PIN service are wrong.

[0190] S502. UE and SMF establish a PDU session using the incorrect DNN and / or S-NSSAI in the URSP of the PIN service.

[0191] S503. The UE sends a PDU session modification request message to the SMF, where the PDU session modification request message includes information indicating a non-3GPP delay budget.

[0192] The specific implementation of S501-S503 refers to the description of steps S401-S403 in the third embodiment, which will not be repeated here.

[0193] S504. SMF sends a PDU session modification acceptance message to the UE. The PDU session modification acceptance message includes the first information, the DNN dedicated to the PIN service and / or the S-NSSAI.

[0194] When the SMF determines that the PDU session is not dedicated to PIN, the SMF chooses to accept the PDU session modification, but the PDN session needs to be modified. The SMF can choose to modify the PDU session itself or instruct the UE to modify the PDU session. If the SMF modifies the DNN and / or S-NSSAI of the PDU session to the DNN and / or S-NSSAI dedicated to the PIN service, the SMF carries the modified DNN and / or S-NSSAI dedicated to the PIN service in the PDU session modification acceptance message and sends it to the UE.

[0195] Optionally, the first information is used to indicate at least one of the following: the PDU session is not dedicated to the PIN, and the PDU session is modified to be applicable to the PIN.

[0196] If the SMF does not modify the PDU session, the PDU session modification acceptance message includes only the first information, and does not include the DNN and / or S-NSSAI dedicated to the PIN service. After receiving the PDU session modification acceptance message, the UE modifies the DNN and / or S-NSSAI of the PDU session to the DNN and / or S-NSSAI dedicated to the PIN service according to the first information, and sends the modified DNN and / or S-NSSAI dedicated to the PIN service to the SMF.

[0197] Optionally, after receiving the PDU session modification accept message, the UE may choose not to modify the PDN session but to release the PDU session.

[0198] S505. The SMF sends first error type information to the PCF.

[0199] S506. The PCF sends first error type information to the NEF.

[0200] S507: NEF updates or deletes the parameters provided by AF and stored in UDR.

[0201] S508: NEF sends first error type information to AF.

[0202] Steps S505-S508 are the same as steps S406-S409 in the third embodiment. Please refer to the description of the third embodiment for details, which will not be repeated here.

[0203] In this embodiment, when the DNN and / or S-NSSAI of the URSP of the PIN service generated by the PCF is wrong, the SMF determines that the DNN and / or S-NSSAI of the PDU session are not dedicated to the PIN according to the PDU session modification request sent by the UE and the DNN and / or S-NSSAI of the PDU session, and the SMF chooses to accept the PDN session modification and modifies the parameters of the PDU session so that the PDU session matches the PIN service, thereby avoiding the problem of data transmission error or PIN service failure of the PIN service caused by the mismatch between the PDU session and the PIN service. The SMF can also send the first error type information to the core network device so that the core network device modifies or deletes the parameters provided by the AF stored in the UDR, ensuring that the parameters provided by the AF stored in the UDR are correct, thereby ensuring that the URSP of the PIN service generated according to the parameters provided by the AF stored in the UDR is correct.

[0204] Embodiment 5

[0205] Embodiment 5 of the present application provides a communication method, in which the core network device determines that the parameters provided by the AF are wrong and reports the error to modify or delete the parameters provided by the AF to ensure that the parameters provided by the AF stored in the UDR are correct. Figure 7 This is a flow chart of the communication method provided in Embodiment 5 of the present application, such as Figure 7 As shown, the method provided in this embodiment includes the following steps.

[0206] S601. A sixth network function determines that a target parameter is wrong, where the target parameter is a parameter of a URSP for generating a PIN service.

[0207] The sixth network function is located on the core network side, and the sixth network function can be NEF, UDM or PCF.

[0208] The target parameter is a parameter provided by the AF, and the target parameter is a parameter used to generate the URSP of the PIN service. The target parameter includes but is not limited to at least one of the following parameters: PIN ID, DNN of the PIN service, and S-NSSAI of the PIN service.

[0209] Among them, the PIN ID, the DNN of the PIN service, and the S-NSSAI of the PIN service can all be parameters provided by the AF. The DNN and / or S-NSSAI of the PIN service provided by the AF may be erroneous, that is, the DNN and / or S-NSSAI provided by the AF are not dedicated to PIN.

[0210] Alternatively, the AF only provides the DNN and / or S-NSSAI for the PIN service without providing the PIN ID. Optionally, the PCF may supplement the PIN ID.

[0211] Alternatively, the AF does not provide DNN and / or S-NSSAI for the PIN service, and the NEF supplements the DNN and / or S-NSSAI, wherein the DNN and / or S-NSSAI supplemented by the NEF may be correct or incorrect, that is, the DNN and / or S-NSSAI supplemented by the NEF is not dedicated to PIN.

[0212] It should be noted that, in some implementations, when the sixth network function determines whether the target parameter is wrong, it does not need to distinguish the actual source of the target parameter (i.e., whether it is provided by the AF or supplemented by other devices), but only needs to determine whether the target parameter is missing and whether the target parameter is a parameter of the PIN service. Regardless of whether the target parameter is actually provided by the AF, the sixth network function can uniformly consider that the parameter provided by the AF is wrong.

[0213] S602. The sixth network function sends second error type information related to the PIN to the seventh network function, where the second error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, URSP parameter error, PDU session parameter error, and parameter error provided by AF.

[0214] When the sixth network function is NEF, the seventh network function may be AF. When the sixth network function is UDM or PCF, the seventh network function may be AF or NEF.

[0215] The second error type information is used to indicate errors related to the PIN service, for example, it can be used to indicate DNN and / or S-NSSAI errors of the PIN service. DNN and / or S-NSSAI errors of the PIN service provided by the AF will result in URSP errors of the PIN service generated based on the DNN and / or S-NSSAI. The PDU session parameters of the PIN service are established based on the URSP of the PIN service, which will lead to PDU session parameter errors of the PIN service, that is, DNN and / or S-NSSAI errors of the PDU session. Therefore, in some cases, the four errors indicated by the second error type information are the same errors, and the four errors can be replaced with each other.

[0216] Optionally, the second error type information is indicated by an error type value, which may be a newly defined error type value or an existing error type value. When the second error type information adopts an existing error type value, the description of the existing error type value needs to be expanded.

[0217] Correspondingly, the seventh network function receives the second error type information from the sixth network function, and determines that the parameter provided by the AF is wrong according to the second error type information.

[0218] Optionally, after the seventh network function determines that the parameter provided by the AF is wrong according to the second error type information, it sends a parameter modification request message to the sixth network function, where the parameter modification request message is used to modify the parameter provided by the AF. Alternatively, the seventh network function sends a parameter deletion request message to the sixth network function, where the parameter deletion request message is used to delete the parameter provided by the AF.

[0219] The seventh network function modifies the parameters provided by the AF stored in the UDR according to the parameter modification request message, or the seventh network function deletes the parameters provided by the AF stored in the UDR according to the parameter deletion request message. By updating or deleting the parameters provided by the AF stored in the UDR, the correctness of the parameters provided by the AF stored in the UDR is ensured.

[0220] If the seventh network function is AF, AF first creates a new AF request according to the second error type information, and then sends a parameter modification request message to NEF, and NEF updates the parameters provided by AF stored in UDR according to the parameter modification request message. Alternatively, AF first deletes the created AF request according to the second error type information, and then sends a parameter deletion request message to NEF, and NEF deletes the parameters provided by AF stored in UDR according to the parameter deletion request message.

[0221] If the seventh network function is NEF, the NEF updates or deletes the parameters provided by the AF stored in the second error type information UDR.

[0222] When the parameters provided by the AF stored in the UDR are updated or deleted, the PCF will be triggered to update the UE policy. The PCF reads the parameters provided by the AF from the UDR and generates the URSP of the PIN service based on the parameters provided by the AF. Since the parameters provided by the AF read by the PCF from the UDR are correct, the URSP of the generated PIN service can be guaranteed to be correct.

[0223] In this embodiment, the sixth network function determines that the target parameter is wrong, and the target parameter is a parameter used to generate the URSP of the PIN service. The sixth network function sends the second error type information related to the PIN to the seventh network function, and the second error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, URSP parameter error, PDU session parameter error, and AF-provided parameter error. The seventh network function can modify or delete the parameters provided by the AF according to the second error type information to ensure that the parameters provided by the AF stored in the UDR are correct. Subsequently, the PCF generates the URSP of the PIN service according to the parameters provided by the AF stored in the UDR, and provides the correct URSP to the UE. The UE performs data transmission of the PIN service according to the correct URSP, thereby avoiding the problem of data transmission errors or PIN service failures of the PIN service.

[0224] Embodiment 6

[0225] Based on the fifth embodiment, the sixth embodiment of the present application provides a communication method, and the implementation methods recorded in the fifth embodiment can be applied to the sixth embodiment and can achieve the same technical effect. In this embodiment, the NEF determines that the parameters provided by the AF are wrong and reports the error to the AF. Figure 8 The signaling flow chart of the communication method provided in Example 6 of the present application is as follows: Figure 8 As shown, the method provided in this embodiment includes the following steps.

[0226] S701: AF creates an AF request.

[0227] S702: AF sends a service parameter creation request to NEF.

[0228] Steps S701 and S702 can refer to Figure 2 S101 and S102 in the illustrated process are not repeated here.

[0229] S703: The NEF sends a service parameter creation response to the AF, where the service parameter creation response includes second error type information related to the PIN.

[0230] The second error type information is used to indicate at least one of the following: a DNN and / or S-NSSAI error, a URSP parameter error, a PDU session parameter error, and a parameter error provided by the AF.

[0231] After receiving the service parameter creation request, the NEF determines the target parameter according to the service parameter creation request and determines whether the target parameter is wrong. The target parameter includes at least one of the PIN ID, DNN, and S-NSSAI of the PIN service.

[0232] NEF determines whether the target parameter is wrong according to the local configuration policy. Taking the target parameter as DNN and / or S-NSSAI as an example, NEF authenticates the AF request. If the DNN and / or S-NSSAI provided by AF cannot be authorized to trigger the subsequent process, NEF sends a service parameter creation response to AF, and the service parameter creation response includes the second error type information related to PIN.

[0233] Specifically, the local configuration policy of NEF includes the range of DNN and / or S-NSSAI that can be used by various services. After determining the DNN and / or S-NSSAI of the current service based on the service parameter creation request, NEF matches the DNN and / or S-NSSAI of the current service with the range of DNN and / or S-NSSAI that can be used by various services in the local configuration policy. If the DNN and / or S-NSSAI of the current service belongs to the range of DNN and / or S-NSSAI that can be used by various services in the local configuration policy, it is determined that the target parameters are correct; otherwise, it is determined that the target parameters are incorrect.

[0234] In one implementation, the service parameter creation request carries the DNN and / or S-NSSAI of the service, and the NEF can directly read the DNN and / or S-NSSAI of the current service from the service parameter creation request.

[0235] In another implementation method, the service parameter creation request does not carry the DNN and / or S-NSSAI of the service, but carries the AF service ID (AF-Service-Identifier). The NEF maps the AF service ID to the DNN and / or S-NSSAI of the current service according to the mapping rules in the local configuration.

[0236] S704: The AF updates the AF request or deletes the AF request according to the second error type information.

[0237] This step is an optional step. After the AF learns that the parameters provided by the AF are wrong according to the second error type information, the AF can choose to update the AF request created in step S601 and modify the service parameters of the AF request. Alternatively, the AF can delete the AF request created in step S601, that is, delete the wrong AF request and delete the service parameters of the AF request. Specifically, the AF calls a service parameter update request to update the parameters of the AF request, or calls a service parameter deletion request to delete the parameters of the AF request.

[0238] Optionally, after the AF deletes the created AF request, it can recreate a correct AF request.

[0239] In this embodiment, after receiving the service parameter creation request sent by the AF, the NEF determines whether the target parameter provided by the AF for generating the URSP of the PIN service is wrong. If the target parameter is wrong, the NEF sends the second error type information to the AF, and the second error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, URSP parameter error, PDU session parameter error, and parameter error provided by the AF. The AF updates or deletes the parameters provided by the AF according to the second error type information to ensure that the parameters provided by the AF stored in the UDR are correct.

[0240] Embodiment 7

[0241] Based on the fifth embodiment, the seventh embodiment of the present application provides a communication method. That is to say, the implementation methods recorded in the fifth embodiment can be applied to the seventh embodiment and can achieve the same technical effect. In this embodiment, the UDM determines that the parameter provided by the AF is wrong and reports the error to the AF. Fig. 9 The signaling flow chart of the communication method provided in Embodiment 7 of the present application is as follows: Fig. 9 As shown, the method provided in this embodiment includes the following steps.

[0242] S801: AF creates an AF request.

[0243] S802: AF sends a service parameter creation request to NEF.

[0244] Steps S801 and S802 can refer to Figure 2 S101 and S102 in the illustrated process are not repeated here.

[0245] S803: NEF and UDM perform service parameter authentication.

[0246] NEF obtains the target parameter of the PIN service according to the service parameter creation request. The target parameter is a parameter used to generate the URSP of the PIN service. NEF provides the target parameter to UDM, and UDM uses the target parameter for authentication. Exemplarily, UDM matches the DNN and / or S-NSSAI in the target parameter with the UE subscription information. The UE subscription information includes information about the service type that the UE is authorized to use. If the DNN and / or S-NSSAI in the target parameter is not authorized to use, it is determined that the authentication fails. NEF considers that the DNN and / or S-NSSAI in the target parameter is wrong. In the case of authentication failure, UDM sends the second error type information to NEF.

[0247] S804. UDM sends second error type information to NEF.

[0248] The second error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, URSP parameter error, PDU session parameter error, and parameter error provided by AF.

[0249] S805. The NEF sends a service parameter creation response to the AF. The service parameter creation response includes second error type information.

[0250] Optionally, the AF may update or delete the AF request according to the second error type information.

[0251] In this embodiment, UDM performs service parameter authentication with NEF. If the authentication result indicates that the target parameter of the PIN service provided by AF is not authorized for use, UDM determines that the target parameter is wrong, and UDM sends the second error type information to NEF, so that AF updates or deletes the parameter provided by AF according to the second error type information, ensuring that the parameter provided by AF stored in UDR is correct. Subsequently, PCF generates URSP of PIN service according to the parameter provided by AF stored in UDR, and provides the correct URSP to UE. UE performs data transmission of PIN service according to the correct URSP, thereby avoiding the problem of data transmission error or PIN service failure of PIN service.

[0252] Embodiment 8

[0253] Based on the fifth embodiment, the eighth embodiment of the present application provides a communication method, and the implementation methods recorded in the fifth embodiment can be applied to the eighth embodiment and can achieve the same technical effect. In this embodiment, the PCF determines that the parameter provided by the AF is wrong and reports the error to the AF. Fig.10 This is a flow chart of the communication method provided in Embodiment 8 of the present application, such as Fig.10 As shown, the method provided in this embodiment includes the following steps.

[0254] S901: AF creates an AF request.

[0255] S902: AF sends a service parameter creation request to NEF.

[0256] S903. NEF stores the service parameters requested by AF in UDR.

[0257] S904. NEF sends a service parameter creation response to AF.

[0258] S905. UDR sends a data modification notification to PCF.

[0259] Steps S901-S905 can refer to Figure 2 S101-S105 in the shown process will not be repeated here.

[0260] S906. Before generating the URSP according to the target parameters, the PCF determines that the target parameters are wrong, stops updating the URSP to the UE or modifies the target parameters, and updates the URSP to the UE according to the modified target parameters.

[0261] After receiving the data modification notification, the PCF obtains the parameters of the URSP used to generate the PIN service from the UDR, that is, obtains the target parameters from the UDR. After obtaining the target parameters from the UDR, the PCF detects whether the target parameters are wrong.

[0262] If the PCF determines that the target parameters are correct, the PCF generates a URSP for the PIN service and updates the URSP to the UE.

[0263] If the PCF determines that the target parameter is wrong, the PCF stops updating the URSP to the UE, or the PCF modifies the target parameter and updates the URSP to the UE according to the modified target parameter.

[0264] For example, if the PCF determines that the DNN and / or S-NSSAI are not dedicated to the PIN, it can stop updating the URSP to the UE. If the PCF detects that the PIN ID is missing in the parameters provided by the AF, the PCF can supplement the PIN ID and update the URSP to the UE using the supplementary PIN ID.

[0265] S907. The PCF sends second error type information related to the PIN to the NEF.

[0266] This step is an optional step. After determining that the target parameter is wrong, the PCF may also choose not to send the second error type information to the NEF, where the second error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, URSP parameter error, PDU session parameter error, and parameter error provided by the AF.

[0267] S908. The NEF updates or deletes the parameters provided by the AF and stored in the UDR.

[0268] S909. The NEF sends second error type information to the AF.

[0269] The specific implementation of steps S908 and S909 refers to steps S408-S409 in the third embodiment, which will not be described in detail here.

[0270] In this embodiment, before generating the URSP according to the target parameters of the PIN service, the PCF detects whether the target parameters are wrong. When the target parameters are wrong, the PCF stops updating the URSP to the UE or the PCF modifies the target parameters, and updates the URSP to the UE according to the modified target parameters, thereby ensuring that the URSP of the PIN service sent by the PCF to the UE is correct. The PCF may also send a second error type information to the NEF so that the AF updates or deletes the parameters provided by the AF according to the second error type information, thereby ensuring that the parameters provided by the AF stored in the UDR are correct. Subsequently, the PCF generates the URSP of the PIN service according to the parameters provided by the AF stored in the UDR, and provides the correct URSP to the UE. The UE performs data transmission of the PIN service according to the correct URSP, thereby avoiding the problem of data transmission errors or PIN service failures of the PIN service.

[0271] Embodiment 9

[0272] In order to better implement the communication method of the embodiment of the present application, the embodiment of the present application also provides a communication device, which can be applied in the UE. Fig.11 A schematic diagram of the structure of a communication device provided in Embodiment 9 of the present application is shown in FIG. Fig.11 As shown, the communication device 100 provided in this embodiment includes the following modules.

[0273] A sending module 11, configured to send a protocol data unit (PDU) session modification request message to the first network function;

[0274] The receiving module 12 is used to receive a response message to the PDU session modification request message from the first network function, wherein the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the personal Internet of Things network PIN.

[0275] In an optional implementation, the relationship between the PDU session and the PIN includes any one of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

[0276] In an optional implementation, the PDU session is not dedicated to the PIN and satisfies at least one of the following:

[0277] Data Network Name DNN and / or Single Network Slice Selection Auxiliary Information S-NSSAI are not specific to PIN;

[0278] The PDU session parameters are not specific to PIN;

[0279] The terminal routing policy URSP does not include the PIN ID.

[0280] In an optional implementation manner, the PDU session modification request message includes information indicating a non-3rd Generation Partnership Project 3GPP delay budget.

[0281] In an optional implementation, the response message is a PDU session modification reject message, and the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, the PDU session is not dedicated to PIN, and the PDU session parameter error.

[0282] In an optional implementation manner, the response message is a PDU session modification accept message, and the PDU session modification accept message satisfies at least one of the following:

[0283] The PDU session modification accept message includes the first information, where the first information is used to indicate at least one of the following: the PDU session is not dedicated to the PIN, and the PDU session is modified to be applicable to the PIN;

[0284] The PDU session modification acceptance message also includes: DNN and / or S-NSSAI dedicated to the PIN service.

[0285] In an optional implementation, the device 100 further includes: a releasing module, configured to release the PDU session according to the first information.

[0286] In an optional implementation, the apparatus 100 further includes: a matching module, configured to match the URSP.

[0287] In an optional implementation, the URSP includes at least one of the following:

[0288] At least one PIN information, the PIN information including: a PIN ID, a DNN dedicated to the PIN, and an S-NSSAI dedicated to the PIN;

[0289] Default traffic descriptor applicable to all PIN services;

[0290] DNN and / or S-NSSAI for all PIN services.

[0291] In an optional implementation, the URSP is preconfigured or received from the network side.

[0292] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here.

[0293] Embodiment 10

[0294] Embodiment 10 of the present application provides a communication device, which can be applied in network functions. Fig.12 A schematic diagram of the structure of a communication device provided in Embodiment 10 of the present application is shown in FIG. Fig.12 As shown, the communication device 200 provided in this embodiment includes the following modules.

[0295] A receiving module 21, configured to receive a protocol data unit (PDU) session modification request message from a user equipment (UE);

[0296] The sending module 22 is used to send a response message of the PDU session modification request message to the UE, wherein the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the personal Internet of Things network PIN.

[0297] In an optional implementation, the relationship between the PDU session and the PIN includes any one of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

[0298] In an optional implementation, the apparatus 200 further includes: a determination module, configured to determine, based on the PDU session modification request message, that the PDU session is not dedicated to the PIN.

[0299] In an optional implementation, the determining module is specifically configured to: determine that the PDU session is not dedicated to the PIN based on at least one of the following:

[0300] The PDU session modification request message includes information indicating a non-3rd Generation Partnership Project 3GPP delay budget;

[0301] The data network name DNN and / or single network slice selection auxiliary information S-NSSAI of the PDU session are not dedicated to the PIN.

[0302] In an optional implementation, the response message is a PDU session modification reject message, and the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, the PDU session is not dedicated to PIN, and the PDU session parameter error.

[0303] In an optional implementation manner, the response message is a PDU session modification accept message, and the PDU session modification accept message satisfies at least one of the following:

[0304] The PDU session modification accept message includes the first information, where the first information is used to indicate at least one of the following: the PDU session is not dedicated to the PIN, and the PDU session is modified to be applicable to the PIN;

[0305] The PDU session modification acceptance message also includes: DNN and / or S-NSSAI dedicated to the PIN service.

[0306] In an optional implementation, the device 200 further includes: a releasing module, configured to release the PDU session.

[0307] In an optional implementation, the sending module 22 is also used to: send first error type information to the second network function, the third network function or the fourth network function, wherein the first error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session parameter error, AF provided parameter error, PIN service parameter error.

[0308] In an optional implementation, the first error type information is carried in an event exposure notification.

[0309] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here.

[0310] Embodiment 11

[0311] Embodiment 11 of the present application provides a communication device, which can be applied in network functions. Fig.13 A schematic diagram of the structure of a communication device provided in Example 11 of the present application is shown in FIG. Fig.13 As shown, the communication device 300 provided in this embodiment includes the following modules.

[0312] The sending module 31 is used to send second error type information related to the personal Internet of Things PIN to the seventh network function, where the second error type information is used to indicate at least one of the following: data network name DNN and / or single network slice selection auxiliary information S-NSSAI error, terminal routing selection strategy URSP parameter error, PDU session parameter error, and parameter error provided by the application function AF.

[0313] In an optional implementation, the communication device 300 further includes:

[0314] The determination module 32 is used to determine that a target parameter is wrong, where the target parameter is a parameter used to generate a URSP for the PIN service.

[0315] In an optional implementation, the communication device 300 is applied in a NEF, and the determination module 32 is specifically used to: determine that the target parameter is wrong according to a local configuration policy.

[0316] In an optional implementation, when the communication device 300 is applied in NEF, the communication device 300 also includes a receiving module for receiving a parameter modification request message or a parameter deletion request message sent by the AF, wherein the parameter modification request message is used to request modification of the parameters provided by the AF, and the parameter deletion request message is used to request deletion of the parameters provided by the AF.

[0317] In an optional implementation, the second error type information is indicated by an error type value.

[0318] In an optional implementation, the communication device 300 is applied in a PCF, and the determination module 32 is specifically used to: determine that the target parameter is wrong before the PCF generates a URSP according to the target parameter.

[0319] In an optional implementation, when the communication device 300 is applied in PCF, the determination module 32 is further used to: stop updating the URSP to the user equipment UE after determining that the target parameter is wrong.

[0320] In an optional implementation, when the communication device 300 is applied to PCF, the determination module 32 is further used to: after determining that the target parameter is wrong, modify the target parameter, and update the URSP to the UE according to the modified target parameter.

[0321] In an optional implementation, the target parameter includes at least one of the following: PIN ID, DNN, S-NSSAI.

[0322] In an optional implementation manner, the seventh network function is used to: receive the second error type information from the sixth network function.

[0323] In an optional implementation manner, the seventh network function is further used to: send a parameter modification request message to the sixth network function according to the second error type information, where the parameter modification request message is used to modify the parameters provided by the AF.

[0324] In an optional implementation manner, the seventh network function is further used to: send a parameter deletion request message to the sixth network function according to the second error type information, where the parameter deletion request message is used to delete the parameters provided by the AF.

[0325] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here.

[0326] Embodiment 12

[0327] Embodiment 12 of the present application provides a communication device, which can be used in network functions. The communication device provided in this embodiment includes a sending module, which is used to send a first terminal policy to a user equipment UE, and the first terminal policy includes at least one of the following: at least one personal Internet of Things network PIN information, and the PIN information includes: a PIN identification ID, a data network name DNN dedicated to the PIN, and a single network slice selection auxiliary information S-NSSAI dedicated to the PIN; a default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI applicable to all PIN services.

[0328] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here.

[0329] The communication device of the embodiment of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0330] Embodiment 13

[0331] An embodiment of the present application also provides a UE. Fig.14 A structural diagram of a UE provided in Embodiment 13 of the present application is shown as follows: Fig.14 As shown, the UE 400 may include:

[0332] The memory 41 and the processor 42, the memory 41 is used to store the computer program and transmit the program code to the processor 42. In other words, the processor 42 can call and run the computer program from the memory 41 to implement the method in the embodiment of the present application.

[0333] In some embodiments of the present application, the processor 42 may include but is not limited to: a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0334] In some embodiments of the present application, the memory 41 includes, but is not limited to: a volatile memory and / or a non-volatile memory, or a non-transient readable memory. Among them, the non-volatile memory or the non-transient readable memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM).

[0335] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 41 and executed by the processor 42 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the UE.

[0336] like Fig.14As shown, the UE 400 may further include: a transceiver 43 , which may be connected to the processor 42 or the memory 41 .

[0337] The processor 42 may control the transceiver 43 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 43 may include a transmitter and a receiver. The transceiver 43 may further include an antenna, and the number of antennas may be one or more.

[0338] Understandable, although Fig.14 Not shown, the UE 400 may also include a camera module, a wireless fidelity WIFI module, a positioning module, a Bluetooth module, a display, a controller, etc., which will not be repeated here.

[0339] It should be understood that the various components in the UE are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0340] The embodiment of the present application also provides a network function, the network function includes a processor and a memory, and the structure of the network function refers to Fig.14 The structure of the UE shown in the figure, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method steps performed by each network function (including SMF, PCF, NEF, UDM or AF) in the method embodiments 1 to 11 of the present application. Similar descriptions can refer to the method embodiments, and to avoid repetition, they are not repeated here.

[0341] The embodiment of the present application also provides a computer storage medium on which a computer program is stored. When the computer program is executed by a computer, the computer can execute the method for executing the UE or network function in the above-mentioned embodiment 1 to embodiment 19. Similar descriptions can refer to the method embodiments. To avoid repetition, they are not repeated here. Optionally, the computer storage medium can be a non-transient computer storage medium.

[0342] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to execute the method for executing the UE or network function in the above-mentioned embodiments 1 to 19. Similar descriptions can refer to the method embodiments, and will not be repeated here to avoid repetition.

[0343] An embodiment of the present application also provides a chip, the chip includes a processor, the processor is used to call and run a computer program from a memory so that the chip executes the above-mentioned method embodiments 1 to 11. The terminal device or positioning device in the above-mentioned method embodiments 1 to 11 can refer to the method embodiments. To avoid repetition, it is not repeated here.

[0344] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0345] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0346] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: The method comprises: The user equipment UE sends a protocol data unit PDU session modification request message to the first network function; The UE receives a response message to the PDU session modification request message from the first network function, where the response message includes first information, where the first information is used to indicate a relationship between the PDU session and the personal Internet of Things network PIN.

2. The method according to claim 1, characterized in that: The relationship between the PDU session and the PIN includes any one of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

3. The method according to claim 2, characterized in that The PDU session is not dedicated to the PIN and meets at least one of the following conditions: Data Network Name DNN and / or Single Network Slice Selection Auxiliary Information S-NSSAI are not specific to PIN; The PDU session parameters are not specific to PIN; The terminal routing policy URSP does not include the PIN ID.

4. The method according to claim 1, characterized in that The PDU session modification request message includes information indicating a non-3rd Generation Partnership Project 3GPP delay budget.

5. The method according to claim 1 or 2, characterized in that: The response message is a PDU session modification rejection message, and the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session is not dedicated to PIN, and PDU session parameter error.

6. The method according to claim 1 or 2, characterized in that: The response message is a PDU session modification accept message, and the PDU session modification accept message satisfies at least one of the following: The PDU session modification accept message includes the first information, where the first information is used to indicate at least one of the following: the PDU session is not dedicated to the PIN, and the PDU session is modified to be applicable to the PIN; The PDU session modification acceptance message also includes: DNN and / or S-NSSAI dedicated to the PIN service.

7. The method according to claim 1, characterized in that The method further comprises: The UE releases the PDU session according to the first information.

8. The method according to any one of claims 1 to 7, characterized in that: Before the UE sends the PDU session modification request message to the first network function, the method further includes: The UE matches the URSP.

9. The method according to claim 8, characterized in that The URSP includes at least one of the following: At least one PIN information, the PIN information including: a PIN ID, a DNN dedicated to the PIN, and an S-NSSAI dedicated to the PIN; Default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI for all PIN services.

10. The method according to claim 8, characterized in that The URSP is preconfigured or received from the network side.

11. A communication method, characterized in that: The method comprises: The first network function receives a protocol data unit (PDU) session modification request message from a user equipment (UE); The first network function sends a response message to the PDU session modification request message to the UE, where the response message includes first information, where the first information is used to indicate a relationship between the PDU session and the personal Internet of Things network PIN.

12. The method according to claim 11, characterized in that The relationship between the PDU session and the PIN includes any one of the following: the PDU session is dedicated to the PIN, and the PDU session is not dedicated to the PIN.

13. The method according to claim 11, characterized in that Before the first network function sends a response message to the PDU session modification request message to the UE, the method further includes: The first network function determines, based on the PDU session modification request message, that the PDU session is not dedicated to the PIN.

14. The method according to claim 13, characterized in that The first network function determines, according to the PDU session modification request message, that the PDU session is not dedicated to the PIN, including: The first network function determines that the PDU session is not dedicated to a PIN based on at least one of the following: The PDU session modification request message includes information indicating a non-3rd Generation Partnership Project 3GPP delay budget; The data network name DNN and / or single network slice selection auxiliary information S-NSSAI of the PDU session are not dedicated to the PIN.

15. The method according to claim 11 or 12, characterized in that: The response message is a PDU session modification rejection message, and the first information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session is not dedicated to PIN, and PDU session parameter error.

16. The method according to claim 11 or 12, characterized in that: The response message is a PDU session modification accept message, and the PDU session modification accept message satisfies at least one of the following: The PDU session modification accept message includes the first information, where the first information is used to indicate at least one of the following: the PDU session is not dedicated to the PIN, and the PDU session is modified to be applicable to the PIN; The PDU session modification acceptance message also includes: DNN and / or S-NSSAI dedicated to the PIN service.

17. The method according to claim 13, characterized in that The method further comprises: The first network function releases the PDU session.

18. The method according to any one of claims 11 to 17, characterized in that: Also includes: The first network function sends first error type information to the second network function, the third network function or the fourth network function, where the first error type information is used to indicate at least one of the following: DNN and / or S-NSSAI error, PDU session parameter error, parameter error provided by AF, and PIN service parameter error.

19. The method according to claim 18, characterized in that The first error type information is carried in the event exposure notification.

20. A communication method, characterized in that: The method comprises: The fifth network function sends a first terminal policy to the user equipment UE, where the first terminal policy includes at least one of the following: At least one personal Internet of Things network PIN information, the PIN information including: PIN identification ID, data network name DNN dedicated to the PIN, and single network slice selection auxiliary information S-NSSAI dedicated to the PIN; Default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI for all PIN services.

21. A communication method, characterized in that: The method comprises: The sixth network function sends second error type information related to the personal Internet of Things PIN to the seventh network function, where the second error type information is used to indicate at least one of the following: data network name DNN and / or single network slice selection auxiliary information S-NSSAI error, terminal routing selection strategy URSP parameter error, PDU session parameter error, and parameter error provided by the application function AF.

22. The method according to claim 21, characterized in that Before the sixth network function sends the second error type information related to the PIN to the seventh network function, the method further includes: The sixth network function determines that a target parameter is wrong, where the target parameter is a parameter of a URSP used to generate a PIN service.

23. The method according to claim 22, characterized in that When the sixth network function is NEF, the sixth network function determines that a target parameter is wrong, including: The NEF determines, according to a local configuration policy, that the target parameter is wrong.

24. The method according to claim 23, characterized in that Also includes: The NEF receives a parameter modification request message or a parameter deletion request message sent by the AF, where the parameter modification request message is used to request modification of a parameter provided by the AF, and the parameter deletion request message is used to request deletion of a parameter provided by the AF.

25. The method according to claim 21 or 22, characterized in that The second error type information is indicated by an error type value.

26. The method according to claim 22, characterized in that When the sixth network function is a PCF, the sixth network function determines that a target parameter is wrong, including: The PCF determines that the target parameter is wrong before generating a URSP according to the target parameter.

27. The method according to claim 26, characterized in that After the PCF determines that the target parameter is wrong, it also includes: The PCF stops updating the URSP to the user equipment UE.

28. The method according to claim 26, characterized in that After the PCF determines that the target parameter is wrong, the further step includes: The PCF modifies the target parameter, and updates the URSP to the UE according to the modified target parameter.

29. The method according to claim 22, characterized in that The target parameter includes at least one of the following: PINID, DNN, S-NSSAI.

30. The method according to claim 21 or 22, characterized in that The method comprises: The seventh network function receives the second error type information from the sixth network function.

31. The method according to claim 30, characterized in that Also includes: The seventh network function sends a parameter modification request message to the sixth network function according to the second error type information, where the parameter modification request message is used to modify the parameters provided by the AF.

32. The method according to claim 30, characterized in that Also includes: The seventh network function sends a parameter deletion request message to the sixth network function according to the second error type information, where the parameter deletion request message is used to delete the parameters provided by the AF.

33. A communication device, characterized in that: The device comprises: A sending module, used to send a protocol data unit PDU session modification request message to the first network function; A receiving module is used to receive a response message to the PDU session modification request message from the first network function, wherein the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the personal Internet of Things network PIN.

34. A communication device, characterized in that: The device comprises: A receiving module, configured to receive a protocol data unit (PDU) session modification request message from a user equipment (UE); A sending module is used to send a response message of the PDU session modification request message to the UE, wherein the response message includes first information, and the first information is used to indicate the relationship between the PDU session and the personal Internet of Things network PIN.

35. A communication device, characterized in that: The device comprises: A sending module is configured to send a first terminal policy to a user equipment UE, where the first terminal policy includes at least one of the following: At least one personal Internet of Things network PIN information, the PIN information including: PIN identification ID, data network name DNN dedicated to the PIN, and single network slice selection auxiliary information S-NSSAI dedicated to the PIN; Default traffic descriptor applicable to all PIN services; DNN and / or S-NSSAI for all PIN services.

36. A communication device, characterized in that: The device comprises: A sending module is used to send second error type information related to the personal Internet of Things PIN to the seventh network function, where the second error type information is used to indicate at least one of the following: data network name DNN and / or single network slice selection auxiliary information S-NSSAI error, terminal routing selection strategy URSP parameter error, PDU session parameter error, and parameter error provided by the application function AF.

37. A user equipment, characterized in that: include: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 10.

38. A network function, characterized in that include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method of any one of claims 11 to 19, or the method of claim 20, or the method of any one of claims 21-32.

39. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 19, or the method according to claim 20, or the method according to any one of claims 21-32.

Images