WO2024164203A1 - Pdu会话方法及装置、通信设备及存储介质 - Google Patents

Pdu会话方法及装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2024164203A1
WO2024164203A1 PCT/CN2023/075083 CN2023075083W WO2024164203A1 WO 2024164203 A1 WO2024164203 A1 WO 2024164203A1 CN 2023075083 W CN2023075083 W CN 2023075083W WO 2024164203 A1 WO2024164203 A1 WO 2024164203A1
Authority
WO
WIPO (PCT)
Prior art keywords
pin
pdu session
request message
response
message
Prior art date
Application number
PCT/CN2023/075083
Other languages
English (en)
French (fr)
Inventor
刘建宁
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202380008177.3A priority Critical patent/CN116349383A/zh
Priority to PCT/CN2023/075083 priority patent/WO2024164203A1/zh
Publication of WO2024164203A1 publication Critical patent/WO2024164203A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular to a method and device for establishing a protocol data unit (PDU) session, an electronic device, and a storage medium.
  • PDU protocol data unit
  • the Personal Internet Network consists of PIN elements (Personal Internet Network Element, PINE) that communicate using PIN direct connection or network connection and are managed locally.
  • PINEs within a PIN may include: normal PINEs, PINEs with Gateway Capability (PINE with Gateway Capability, PEGC), and PINEs with Management Capability (PINE with Management Capability, PEMC).
  • PEGC can be used for connection between PIN and mobile communication network.
  • PEMC can be used for local management of PIN.
  • Typical ordinary PINEs may include but are not limited to: wearable device networks and smart home/smart office devices.
  • PINEs can access the fifth generation mobile communication network (5th Generation, 5G) through PEGC, and can communicate with devices that are not in PIN based on mobile communication networks such as 5G.
  • 5G fifth generation mobile communication network
  • the embodiments of the present disclosure provide a PDU session method and apparatus, a communication device, and a storage medium.
  • a first aspect of an embodiment of the present disclosure provides a PDU session method, wherein the method is performed by a user equipment (User Equipment, UE), and the method includes:
  • Send a first request message wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request the core network device to establish a PDU session;
  • a second aspect of the disclosed embodiment provides a method for establishing a protocol data unit (PDU) session, wherein:
  • the method is performed by a core network device and includes:
  • the message requesting to establish a PDU session being a first request message including a personal Internet of Things PIN identification ID, determining to accept or reject the PDU session based on the PIN ID;
  • a third aspect of an embodiment of the present disclosure provides a method for establishing a protocol data unit (PDU) session, wherein the method is performed by an access management function (AMF) or a mobility management entity (MME), and the method includes:
  • a second request message is sent, wherein the second request message includes: the PIN ID; and the second request message is used by the session management function SMF to determine whether to accept or reject the establishment of a PDU session based on the PIN ID;
  • a fourth aspect of the embodiments of the present disclosure provides a method for establishing a protocol data unit (PDU) session, which is executed by a session management function (SMF) in a core network device.
  • the method includes:
  • the received request message being a second request message including a personal Internet of Things PIN identification ID
  • a second response message is sent, wherein the second response message is used by the access management function AMF or the mobility management entity MME to indicate acceptance or refusal to establish a PDU session based on the PIN ID.
  • a fifth aspect of the embodiments of the present disclosure provides a method for establishing a protocol data unit (PDU) session, which is executed by a user data manager (UDM) or a unified data repository (UDR) in a core network device, wherein the method includes:
  • request message being a third request message including a personal Internet of Things PIN identification ID, querying the contract data of the PIN;
  • the third response message includes the signing data of the PIN; wherein the signing data of the PIN is at least used for the session management function SMF to determine whether to accept or refuse to establish a PDU session based on the PIN ID.
  • a sixth aspect of the embodiments of the present disclosure provides a method for establishing a protocol data unit (PDU) session, which is executed by a policy control function (PCF) in a core network device.
  • the method includes:
  • the request message being a fourth request message including a personal Internet of Things PIN identification ID, acquiring policy information of the PIN;
  • a fourth response message is sent, wherein the fourth response message includes policy information of the PIN, wherein the policy information of the PIN is used by the session management function SMF to initiate establishment of a PDU session based on the PIN ID.
  • a seventh aspect of the embodiments of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • a first sending module is configured to send a first request message, wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request a core network device to establish a PDU session;
  • the first receiving module is configured to receive a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established.
  • An eighth aspect of the embodiments of the present disclosure provides a device for establishing a protocol data unit (PDU) session, wherein the device includes:
  • a first determination module is configured to determine whether to accept or reject the PDU session based on the PIN ID in response to a message requesting to establish a PDU session being a first request message including a personal Internet of Things PIN identification ID;
  • the second sending module is configured to send a first response message, wherein the first response message is used to indicate to the user equipment UE whether the PDU session based on the PIN ID is successfully established or failed.
  • a ninth aspect of the embodiments of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • the third sending module is configured to send a second request message in response to the message requesting to establish a PDU session being a first request message including a personal Internet of Things PIN identification ID, wherein the second request message includes: the PIN ID; and the second request message is used by the session management function SMF to determine whether to accept or refuse to establish a PDU session based on the PIN ID;
  • a third receiving module is configured to receive a second response message, wherein the second response message is used to indicate acceptance or rejection of establishing a PDU session based on the PIN ID;
  • the third sending module is configured to send a first response message, wherein the first response message is used to indicate to the user equipment UE whether the PDU session based on the PIN ID is successfully established or failed.
  • a tenth aspect of an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • a fourth receiving module is configured to receive a request message
  • a second determination module is configured to determine, in response to the received request message being a second request message including a personal Internet of Things PIN identification ID, whether to accept or reject the establishment of the PDU session according to the PIN ID and the contract data of the PIN;
  • the fourth sending module is configured to send a second response message, wherein the second response message is used to instruct the access management function AMF or the mobility management entity MME to accept or refuse to establish a PDU session based on the PIN ID.
  • a device for establishing a protocol data unit (PDU) session comprising:
  • a fifth receiving module configured to receive a request message
  • a query module configured to query the contract data of the PIN in response to the request message sent by the second network device being a third request message including the personal Internet of Things PIN identification ID;
  • the fifth sending module is configured to send a third response message, wherein the third response message includes the signing data of the PIN; wherein the signing data of the PIN is at least used by the session management function SMF to determine whether to accept or reject the establishment of a PDU session based on the PIN ID.
  • a twelfth aspect of the embodiments of the present disclosure provides a protocol data unit (PDU) session establishment device, the device comprising:
  • a sixth receiving module configured to receive a request message
  • an acquisition module configured to acquire policy information of the PIN in response to the request message sent by the second network device being a fourth request message including a personal Internet of Things PIN identification ID;
  • the sixth sending module is configured to send a fourth response message, wherein the fourth response message includes policy information of the PIN, wherein the policy information of the PIN is used by the session management function SMF to establish a PDU session based on the PIN ID.
  • a thirteenth aspect of the embodiment of the present disclosure provides a PDU session establishment method, which includes: a user equipment UE, an access management function AMF or a mobility management entity MME and a session management function SMF; the UE sends a first request message, wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request to establish a PDU session;
  • the UE receives a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established;
  • the AMF or MME sends a second request message, wherein the second request message includes: the PIN ID; and the second request message is used by the SMF to determine whether to establish a PDU session based on the PIN ID; receive a second response message, wherein the second response message is used to indicate acceptance or refusal to establish a PDU session based on the PIN ID; send a first response message, wherein the first response message is used to indicate success or failure in establishing a PDU session based on the PIN ID;
  • the SMF receives a request message; in response to the received request message being a second request message including a personal IoT PIN identification ID, determines to accept or reject the establishment of the PDU session based on the PIN ID and the contract data of the PIN; and sends a second response message, wherein the second response message is used to indicate acceptance or rejection of establishing a PDU session based on the PIN ID.
  • a fourteenth aspect of an embodiment of the present disclosure provides a communication system, which is used for the PDU session establishment method provided in the first and second aspects above.
  • a fifteenth aspect of the embodiments of the present disclosure provides a communication system, including the following network elements:
  • a user data manager or a unified data repository (UDR) for executing the method provided in the fifth aspect;
  • a policy control function PCF is used to execute the method provided in the sixth aspect.
  • a sixteenth aspect of an embodiment of the present disclosure provides a communication device, comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein when the processor runs the executable program, the technical solution provided in any of the first to sixth aspects and any of the twelfth aspects is executed.
  • a seventeenth aspect of an embodiment of the present disclosure provides a computer storage medium, which stores an executable program; after the executable program is executed by a processor, it can implement the technical solutions provided in any of the first to sixth aspects and any of the twelfth aspects.
  • the UE can initiate a PDU session based on the PIN ID, thereby ensuring the service quality of the PIN service through the PDU session establishment process.
  • FIG1A is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • FIG1B is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG1C is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG1D is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG. 1E is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG2A is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG2B is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG3A is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG3B is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG4A is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG4B is a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG4C is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG4D is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG5A is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG5B is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG6A is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG6B is a schematic diagram of a flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG7 is a schematic flow chart of a method for establishing a PDU session according to an exemplary embodiment
  • FIG8 is a schematic structural diagram of a PDU session establishment device according to an exemplary embodiment
  • FIG9 is a schematic structural diagram of a PDU session establishment device according to an exemplary embodiment
  • FIG10 is a schematic structural diagram of a PDU session establishment device according to an exemplary embodiment
  • FIG11 is a schematic structural diagram of a device for establishing a PDU session according to an exemplary embodiment
  • FIG12 is a schematic structural diagram of a PDU session establishment device according to an exemplary embodiment
  • FIG13 is a schematic structural diagram of a PDU session establishment device according to an exemplary embodiment
  • FIG14 is a schematic diagram showing the structure of a UE according to an exemplary embodiment
  • Fig. 15 is a schematic diagram showing the structure of a network device according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • the words as used herein may be interpreted as when or when or in response to determination.
  • the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of UEs 11 and a plurality of access devices 12. In some embodiments, the communication system may also include: one or more core network devices, which are not shown in Figure 1.
  • the core network device includes, but is not limited to: a mobile management entity (Mobile Management Entity, MME) or an access management function (Access Management Function, AMF), a session management function (Session Management Function, SMF), a policy control function (Policy Control Function, PCF) and/or a user plane function (User Plane Function, UPF), etc.
  • MME Mobile Management Entity
  • AMF Access Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • UPF User Plane Function
  • UE 11 can be a device that provides voice and/or data connectivity to users.
  • UE 11 can communicate with one or more core networks via a radio access network (RAN).
  • RAN radio access network
  • UE 11 can be an Internet of Things UE, such as a sensor device, a mobile phone (or a cellular phone), and a computer with an Internet of Things UE.
  • it can be a fixed, portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted device.
  • a station STA
  • a subscriber unit a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment (UE).
  • STA station
  • UE user equipment
  • UE 11 can also be a device of an unmanned aerial vehicle.
  • UE 11 may be an onboard device, for example, a driving computer with a wireless communication function, or a wireless communication device external to the driving computer.
  • UE 11 may be a roadside device, for example, a street lamp, a signal lamp, or other roadside device with a wireless communication function.
  • the access device 12 may be a network side device in a wireless communication system.
  • the wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new radio (NR) system or a 5G NR system.
  • 4G fourth generation mobile communication technology
  • 5G also known as a new radio (NR) system or a 5G NR system.
  • NR new radio
  • the wireless communication system may be a next generation system of the 5G system.
  • the access network in the 5G system may be called NG-RAN (New Generation-Radio Access Network).
  • an MTC system may be called NG-RAN (New Generation-Radio Access Network).
  • the access device 12 can be an evolved base station (eNB) adopted in a 4G system.
  • the access device 12 can also be a base station (gNB) adopting a centralized distributed architecture in a 5G system.
  • the access device 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed units, DU).
  • the centralized unit is provided with a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, a radio link layer control protocol (Radio Link Control, RLC) layer, and a media access control (Media Access Control, MAC) layer protocol stack;
  • the distributed unit is provided with a physical (Physical, PHY) layer protocol stack.
  • the embodiment of the present disclosure does not limit the specific implementation method of the access device 12.
  • a wireless connection can be established between the access device 12 and the UE 11 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface can also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
  • PIN connection support may allow PINE communication.
  • PINE communication may include: communication between PINEs via PINE direct connection, communication between PINEs based on PEGC, and/or communication between PINEs or between PINEs and PIN external devices based on PEGC and a mobile communication network (e.g., 4G and/or 5G as shown in FIG. 1 ).
  • One or more applications can run in PINE.
  • Different APPs may have different Quality of Service (QoS) requirements for the services. Therefore, the service data transferred, relayed or transparently transmitted by PEGC is required to meet the corresponding QoS requirements. Therefore, how to ensure the QoS of PIN services is an issue that needs to be further solved in related technologies.
  • QoS Quality of Service
  • an embodiment of the present disclosure provides a PDU session establishment method, which can be executed by a UE, including:
  • S0011 Send a first request message, wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request the core network device to establish a PDU session;
  • S0012 Receive a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established.
  • the UE may be a terminal device that can be connected to a mobile communication network.
  • the UE may be a terminal device that can be connected to a 4G or 5G network.
  • the UE may include, but is not limited to: a notebook, a tablet computer, a wearable device, a smart home device, a smart office device, a vehicle-mounted device and/or a flight device.
  • the UE can be connected to the access device shown in FIG. 1A to use the mobile communication network.
  • the UE may send a first request message, the first request message including a PIN ID.
  • the PIN ID may be used to identify a PIN established based on the UE, or a PIN to which the UE belongs.
  • the first request message may be used by the core network device to receive or reject a PDU session established by the UE based on the PIN ID request.
  • the PIN may include one or more PINEs, which may be smart home devices, smart office devices, smart charging devices, smart vending devices, etc.
  • PINEs may be smart home devices, smart office devices, smart charging devices, smart vending devices, etc.
  • this is just an example of the PINE in the PIN, and the specific implementation is not limited to this example.
  • the first response message here is used for the UE to determine whether it is authorized to establish a PDU session based on the PIN ID. If the UE is authorized to establish a PDU session based on the PIN ID, the network device on the network side will start the PDU session establishment, which means that the PDU session based on the PIN ID is successfully established, otherwise the establishment fails.
  • the first response message can indicate whether the PDU session based on the PIN ID is successfully established through its own message format and/or the content it carries.
  • the first request message requests to establish a PDU session based on a PIN or a PIN ID.
  • the first request message may be a PDU session establishment request message.
  • the PDU session based on a PIN or a PIN ID may be used to transmit service data of a PIN service.
  • the UE After the UE sends the first request message, it will receive a first response message returned by the core network device, which can be a response success message or a response failure message.
  • the response success message can be used to indicate that the first network device accepts the establishment of the PDU session
  • the response failure message can indicate that the first network device rejects the establishment of the PDU session.
  • the first response message may include: a PDU session identifier (ID) assigned by the core network device, and the UE may subsequently conduct a PDU session based on the PDU ID. Therefore, in the disclosed embodiment, by establishing a PDU session, the QoS of the PIN service can be ensured based on the PDU session process, thereby improving the quality of communication services based on the PIN.
  • ID PDU session identifier
  • the UE can initiate a PDU session establishment request that is not related to the PIN service based on itself, or can initiate a PDU session establishment request that is associated with the PIN service. That is, in some embodiments, when the PDU session requested to be established is associated with the PIN service, a first request message containing the PIN ID is sent to the first network device.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by a UE and includes:
  • S1110 Send a first request message to the AMF or MME, where the first request message includes the PIN ID and is used to request to establish a PDU session.
  • S1120 Receive a first response message sent by AMF or MME, where the first response message is used to indicate whether a PDU session based on PIN ID is established successfully.
  • AMF or MME is a device that manages the mobility of the UE.
  • the method may further include: determining whether the PDU session to be established is associated with a PIN service;
  • the sending of the first request message includes: when the PDU session to be established is associated with the PIN service, sending the first request message.
  • the PIN ID is carried in the first request message only when the UE initiates a PDU establishment request associated with the PIN service. If the PDU session initiated by the UE is not related to the PIN service, the PDU session establishment request sent to the first network device does not contain the PIN ID, but includes other IDs of the UE, such as the temporary mobile subscriber identity (TMSI) or the subscription concealed identifier (SUCI). If the first request message already contains the PIN ID, it may carry the UE identification information such as the TMSI or SUCI of the UE, or it may not carry the UE identification information.
  • TMSI temporary mobile subscriber identity
  • SUCI subscription concealed identifier
  • the first network device By carrying the PIN ID in the first request message for requesting to establish a PDU session, the first network device will know, after receiving the first request message, that the PDU session currently requested by the UE is associated with the PIN service or the PIN identified by the PIN ID. Thus, it can determine whether to accept the establishment of the PDU session or configure the QoS parameters of the PDU session based on the contract data of the PIN and/or the special requirements of the PIN service.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by a user equipment UE and includes:
  • S1210 Determine whether the PDU session to be established is associated with the PIN service
  • S1230 Receive the first response message sent by AMF or MME, where the first response message indicates whether the PDU session based on PIN ID is established successfully.
  • determining whether the PDU session to be established is associated with the PIN service includes at least one of the following:
  • the service involved in the PDU session to be established includes the PIN service, it is determined that the PDU session to be established is associated with the PIN service.
  • a common PINE or PEMC in a PIN can communicate with a UE that can be connected to a mobile communication network through a non-3GPP protocol such as a PIN protocol, thereby sending a PIN service request to the UE.
  • a PIN service request from another PINE that cannot be directly connected to a mobile communication network, it can confirm that the current PDU session to be established is related to the PIN service.
  • the UE when the UE receives one or more PIN service requests from the PIN direct communication, it is determined that the PDU session to be established is associated with the PIN service.
  • the UE itself may also initiate a PIN service request.
  • the user interface UI
  • the PDU session to be established may be considered to be associated with the PIN service.
  • the UE when the UE, as a PEGC, PEMC and/or ordinary PINE with the ability to connect to a mobile communication network in the PIN, receives an indication to establish a PDU session associated with the PIN service on the UI interface, or receives an indication to establish a PDU session associated with the PIN service from an upper-layer control device, the PDU session to be established may be considered to be a PDU session associated with the PIN service, and the UE will initiate a request establishment process for a PDU session based on the PIN ID.
  • one or more PIN service-related applications are installed in the UE. Based on the PDU initiated by such application, the PDU session to be established can be considered to be associated with the PIN service.
  • the UE finds that the service identifier corresponding to the PDU session to be established is the identifier of the PIN service.
  • the service of the PDU session to be initiated includes the PIN service, and it is considered that the PDU session to be established is associated with the PIN service.
  • the UE before the UE sends a PDU session establishment request including a PIN ID, it will determine whether the PDU session to be established is associated with the PIN service. If so, the PIN ID will be included, which also facilitates the network side to specifically enhance the communication instructions of the PIN service.
  • the UE is a PIN gateway PEGC.
  • the UE that initiates the first request message containing the PIN ID may also be a PMEC or a common PINE in the PIN that has the ability to access the mobile communication network. If the UE is a PEGC, it can facilitate the PEGC of the PIN to uniformly manage the communication between the PINE and the mobile communication network.
  • an embodiment of the present disclosure provides a PDU session establishment method, which is performed by a core network device, and the method includes:
  • S0021 In response to the message requesting to establish a PDU session being a first request message including a personal IoT PIN identification ID, determining to accept or reject the PDU session based on the PIN ID;
  • S0022 Send a first response message, wherein the first response message is used to indicate to the user equipment UE whether the PDU session based on the PIN ID is established successfully or failed.
  • the core network device here may be any one or more core network devices, which may be executed by directly or indirectly receiving a first request message from a UE.
  • the first request message includes a PIN ID, and a PDU session is established for a PIN identified by the PIN ID, so as to achieve QoS for PIN service transmission through the establishment of the PDU session.
  • the message in response to the request to establish the PDU session is a first request message including a personal Internet of Things PIN identification ID, and determining to accept or reject the PDU session based on the PIN ID includes:
  • the message in response to the request to establish a PDU session is a first request message including a personal Internet of Things PIN identification ID, and the signing data of the PIN identified by the PIN ID allows the establishment of a PDU session, and a PDU session based on the PIN ID is established.
  • the contract data of the PIN may include at least one of the following:
  • the contract data of the PIN includes at least one of the following:
  • Capability information indicating whether the PIN identified by the PIN ID has PDU session capability, or whether the UE has PEGC and/or PEMC capabilities;
  • Time information indicating the time range in which the establishment of a PDU session based on the PIN ID is allowed, or the time range in which the establishment of a PDU session based on the PIN ID is prohibited;
  • Spatial information indicating the spatial range in which the establishment of a PDU session based on the PIN ID is allowed, or the spatial range in which the establishment of a PDU session based on the PIN ID is prohibited;
  • Bandwidth information indicating the bandwidth range allowed for a PDU session established based on a PIN ID.
  • the message in response to the request to establish the PDU session is a first request message including a personal Internet of Things PIN identification ID, and determining to accept or reject the PDU session based on the PIN ID includes:
  • the message in response to the request to establish a PDU session is a first request message including a personal Internet of Things PIN identification ID, and the contract data of the PIN identified by the PIN ID does not allow the establishment of a PDU session, and the PDU session based on the PIN ID is rejected.
  • the capability information indicates that the PIN does not have PDU session capability, or the UE does not have PEGC and/or PEMC capabilities, sending a rejection message to the first network device;
  • the capability information indicates that the PIN has PDU session capability, or the UE has PEGC and/or PEMC capabilities, sending an acceptance message including the PIN ID to the first network device;
  • an acceptance message including the PIN ID is sent to the first network device;
  • an acceptance message including a PIN ID is sent to the first network device.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by an AMF or an MME, and the method includes:
  • S0032 Receive a second response message, wherein the second response message is used to indicate acceptance or rejection of establishing a PDU session based on the PIN ID;
  • S0033 Send a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established or failed.
  • AMF or MME After AMF or MME receives the first request message sent by UE, it can send a second request message.
  • the second request message will be sent directly or indirectly to SMF, and SMF will further determine whether to accept or reject the establishment of PDU session based on PIN ID.
  • sending a second request message includes:
  • the SMF supporting the PIN service session is selected.
  • SMFs that support PIN services and SMFs that do not support PIN services in the network. Since the PDU session is established based on the PIN ID, it is necessary to select an SMF that supports the PIN service to ensure that the established PDU session is suitable for data transmission of the PIN service.
  • the second response message in response to the second response message including the PDU session ID, the second response message further includes at least one of the following:
  • the QFI may be associated with one or more groups of QoS parameters.
  • the number of QFIs in the second response message may be one or more.
  • the QoS parameters associated with different QFIs are at least partially different.
  • a QoS profile may include at least one of the following: QoS rules, QoS flow levels and/or QoS parameters.
  • the QoS profile can also be used by the access device to initiate an update process based on a PDU session.
  • the QoS parameters here may include but are not limited to bandwidth parameters and/or delay parameters, etc.
  • the bandwidth parameters may include but are not limited to: minimum guaranteed bandwidth, or maximum guaranteed bandwidth and/or maximum allowed delay, etc., which can be used for monitoring PDU sessions.
  • an embodiment of the present disclosure provides a method for establishing a protocol data unit PDU session, wherein the method is performed by an AMF or an MME, and the method includes:
  • S2140 Send a first response message to the UE according to the second response message.
  • the AMF or MME may be a core network device, which includes but is not limited to a network device that performs mobility management and/or registration management on the UE, such as an AMF and/or MME.
  • the AMF or MME receives various messages requesting the establishment of a PDU session. For example, upon receiving a first request message carrying a PIN ID, it can be considered that the current UE requests the establishment of a PDU session based on the PIN or PIN ID.
  • a second request message including the PIN ID will be sent to the SMF.
  • the second request message carries the PIN ID, indicating that the AMF or MME requests the SMF to determine whether the PDU session currently requested by the UE can be established.
  • the authorization result of the SMF will be carried in the second response message, or indicated by the second response message.
  • the SMF may be a core network device different from the AMF or MME.
  • the SMF may include but is not limited to a session management function (Session Management Function, SMF).
  • SMF Session Management Function
  • the SMF may be a dedicated network device for PDU session management.
  • the second request message may include but is not limited to: a PDU session establishment session management (Session Management, SM) context request message. If the second request message is a PDU session establishment session management (Session Management, SM) context request message, the second response message may be: a PDU session SM context response message.
  • SM PDU session establishment session management
  • the AMF or MME may return the first response message to the UE.
  • the second response message indicates that the PDU session establishment is accepted, and a response success message is sent to the UE, otherwise a response failure message is sent to the UE.
  • the response success message may include the PDU session ID, etc.
  • the response failure message may include a failure indication and/or a cause indication.
  • the failure indication directly indicates that the PDU session establishment failed.
  • the cause indication indicates the cause of the PDU session establishment failure.
  • an embodiment of the present disclosure provides a method for establishing a protocol data unit (PDU) session, wherein the method is performed by an AMF or an MME, and the method includes:
  • S2230 Send a second request message to the SMF supporting the PIN service, where the second request message includes: PIN ID;
  • S2240 Receive a second response message sent by the SMF
  • S2250 Send a first response message to the UE according to the second response message.
  • the first request message received by the AMF or MME includes a PIN ID, and it can be considered that the PDU session currently requested to be established by the UE is associated with the PIN service, and the SMF supporting the PIN service will be determined based on the pre-configuration.
  • the pre-configuration may be that the communication operator pre-configures the identification information and/or address information of the SMF supporting the PIN and service on the AMF or MME.
  • the SMF supporting the PIN service may also provide session management of non-PIN services.
  • a specific SMF when a PIN request is established, a specific SMF is configured to support its PIN service.
  • the AMF or MME will store the PIN ID and the corresponding information of the specific SMF during the PIN establishment process.
  • the AMF or MME can query the information of the SMF corresponding to the PIN ID based on the PIN ID (for example, identification information and/or IP address), etc., and also realize the selection of the SMF that supports the PIN service, and select the specific SMF bound or registered during the PIN establishment phase, so that the specific SMF can be used to provide personalized business services for the PIN service for the PIN service.
  • sending the first response message to the PEGC according to the second response message includes: when the second response message includes the PDU session ID, sending a PDU session establishment accept message to the UE.
  • the response success message corresponding to the PDU session establishment request message can be a PDU session establishment acceptance message. If the SMF determines to accept the PDU session, it will allocate a PDU session ID and initiate the establishment of the PDU session.
  • the establishment of the PDU session includes: the establishment of an N4 session between core network devices such as SMF and UPF. If the AMF or MME receives the PDU session ID assigned by the SMF, it will be considered that the SMF authorizes the establishment of the PDU session based on the PIN or PIN ID. At this time, the PDU session ID is carried in the first response message, so that the UE is informed through the PDU session ID that the current network side accepts the establishment of the PDU session.
  • the second response message when the second response message includes the PDU session ID, the second response message also includes at least one of the following:
  • QFI Quality of service QoS flow identifier
  • the QFI may be associated with one or more groups of QoS parameters.
  • the QFI carried in the second response message may be one or more. Different QFIs may be associated with different QoS parameters.
  • a QoS profile may include at least one of the following: QoS rules, QoS flow levels and/or QoS parameters.
  • the QoS profile can also be used by the access device to initiate an update process based on a PDU session.
  • the QoS parameters here may include but are not limited to bandwidth parameters and/or delay parameters, etc.
  • the bandwidth parameters may include but are not limited to: minimum guaranteed bandwidth, or maximum guaranteed bandwidth and/or maximum allowed delay, etc., which can be used for monitoring PDU sessions.
  • the method further comprises:
  • a PDU session establishment rejection message is sent to the UE.
  • the message format and/or encapsulation method of the PDU session establishment rejection message of the non-PIN service can be used to send a message indicating the PDU session establishment failure to the UE, so as to publicly know the PDU session establishment failure.
  • the method further includes:
  • the second request message is resent to SMF; until the number of times the second request message has been sent reaches the maximum number of times or a rejection message is received, a PDU session establishment rejection message is sent to the UE.
  • the method further comprises:
  • the UE is the PIN of the PIN, and its SUPI will be carried in the configuration file or configuration information of the PIN and stored in the AMF or MME.
  • the AMF or MME can query the SUPI of the UE based on the PIN ID, rather than querying its SUPI based on the TMSI or SUCI of the UE.
  • the SUPI of the UE will be included in the second request message while including the PIN ID. In this way, it is convenient for the SMF to determine which UE and the network side to establish a PDU session based on the SUPI.
  • an embodiment of the present disclosure provides a method for establishing a protocol data unit PDU session, wherein the method is performed by a session management function SMF in a core network device, and the method includes:
  • S0042 In response to the received request message being a second request message including a PIN ID, determining to accept or reject establishment of the PDU session according to the PIN ID and the contract data of the PIN;
  • S0043 Send a second response message, wherein the second response message is used by the access management function AMF or the mobility management entity MME to indicate acceptance or refusal to establish a PDU session based on the PIN ID.
  • SMF is a device that can perform PDU session management, and the PDU session management includes but is not limited to: PDU session establishment and/or PDU session update, etc.
  • AMF or MME will request SMF to establish a PDU session based on the PDU session establishment request message from UE. At this time, SMF will receive the request message from AMF or MME. At this time, the request message sent by AMF or MME can be divided into two categories according to whether it contains PIN ID, one is the second request message containing PIN ID, and the other is other request messages that do not contain PIN ID.
  • the second request message may include a PDU session establishment session management (Session Management, SM) context request message from the AMF or MME.
  • SM Session Management
  • the second request message carries a PIN ID, it means that the establishment process of this PDU session is initiated by the PIN or PIN service, or is managed by the PIN or PIN service.
  • SMF will obtain the contract data of the PIN instead of the contract data of the UE.
  • the contract data of the PIN is based on the PIN as the contract subject, while the contract data of the UE is based on the UE as the contract subject.
  • the contract data of the PIN it can be known whether the establishment of a PDU session based on the PIN is currently allowed, or whether the establishment of a PDU session associated with the PIN service is allowed (ie, authorized).
  • the response to the received request message being a second request message including a personal IoT PIN identification ID includes:
  • an SMF obtains the contract data of a PIN from other core network devices.
  • the specific implementation is not limited to the above example.
  • the contract data of the PIN obtained by the SMF may also be the contract data of the PIN stored locally.
  • the method further comprises:
  • the PCF When the PDU session is allowed to be established based on the PIN ID, the PCF sends a fourth request message; wherein the fourth request message includes the PIN ID, and the fourth request message is used to request policy information;
  • a fourth response message is received, wherein the fourth response message includes the policy information; the policy information is used for establishing a PDU session.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by SMF and includes:
  • S3110 receiving a request message sent by AMF or MME;
  • S3120 When the request message sent by the AMF or MME is a second request message including a PIN ID, a second response message is sent to the AMF or MME according to the PIN ID and the contract data of the PIN; wherein the second response message is used for the AMF or MME to determine whether to accept the establishment of the PDU session.
  • SMF will send a second response message based on the second request message to AMF or MME.
  • the second response message may be an acceptance message and/or a rejection message. If it is an acceptance message, SMF will initiate the establishment of a PDU session, and AMF or MME will inform UE of its consent to the establishment of the PDU session based on the acceptance message, as well as the ID of the PDU session being established or already initiated (i.e., PDU session ID).
  • the SMF will not initiate the PDU session establishment based on the second request message. In some embodiments, the failure reason will be carried in the rejection message.
  • the failure reason may indicate at least one of the following:
  • the PIN identified by the PIN ID does not have the authorization to request a PDU session
  • the establishment time of the request to establish a PDU session does not include the effective time of the PDU session authorized by the PIN.
  • the establishment time may be the current time when the SMF receives the second request message, or the establishment time indicated by the time information carried in the second request message. If the time information carried by the second request message can come from the first request message. For example, if the PIN pre-requests that the PDU session be established at a specific time, the first request message will carry the time information indicating the specific time, and the time information will be carried in the second request message and accepted by the SMF.
  • the PIN that requests to establish a PDU session is outside the valid spatial range of the PDU session authorized by the PIN. For example, if a mobile phone or wearable device is used as the UE, and the valid spatial range is within 100 meters centered on the user's home, and the mobile phone or wearable device is carried by the user to an office 100 meters away from home, the mobile phone may be considered to be outside the valid spatial range when initiating a PDU session based on the PIN ID, and such a PDU session may be rejected.
  • the SMF will store the contract data of the PIN locally. At this time, the SMF can query the contract data of the PIN locally.
  • the SMF does not store the PIN contract data locally, it can request the PIN contract data from the UDM or UDR.
  • the contract data of the PIN includes at least one of the following:
  • Capability information indicating whether the PIN identified by the PIN ID has PDU session capability, or whether the UE has PEGC and/or PMEC capabilities;
  • Time information indicating the time range in which the establishment of a PDU session based on the PIN ID is allowed, or the time range in which the establishment of a PDU session based on the PIN ID is prohibited;
  • Spatial information indicating the spatial range in which the establishment of a PDU session based on the PIN ID is allowed, or the spatial range in which the establishment of a PDU session based on the PIN ID is prohibited;
  • Bandwidth information indicating the bandwidth range allowed for a PDU session established based on a PIN ID.
  • S3120 may include at least one of the following:
  • a rejection message is sent to the AMF or MME;
  • an accept message including the PIN ID is sent to the AMF or MME;
  • an acceptance message containing the PIN ID is sent to the AMF or MME;
  • an acceptance message including the PIN ID is sent to the AMF or MME;
  • an acceptance message containing the PIN ID is sent to the AMF or MME;
  • a rejection message is sent to the AMF or MME;
  • a rejection message is sent to the AMF or MME;
  • an acceptance message containing the PIN ID is sent to the AMF or MME.
  • the subscription data of the PIN may further indicate whether other PINEs in the PIN are allowed to initiate PDU sessions associated with the PIN service.
  • the subscription data of the PIN may indicate whether the PEMC in the PIN and/or ordinary PINEs with mobile communication capabilities are allowed to initiate PDU sessions associated with the PIN service. Therefore, in some cases, S3120 may further include:
  • the UE that initiates a PDU session based on PIN ID is a normal PINE or PEMC
  • whether the UE is allowed to initiate a session request based on PIN ID is determined according to the PIN contract data. If allowed, an acceptance message including the PIN ID is sent to the AMF or MME; otherwise, a rejection message is sent to the AMF or MME.
  • an embodiment of the present disclosure provides a PDU session establishment method, which is performed by SMF and includes:
  • S3220 when the request message sent by the AMF or MME is the second request message including the PIN ID, send a third request message to the UDM or UDR according to the PIN ID, wherein the third request message includes the PIN ID, and the third request message is used to request the subscription data of the PIN;
  • S3240 Send a second response message to AMF or MME according to the subscription data of the PIN; wherein the second response message is used for AMF or MME to determine whether to accept the establishment of the PDU session.
  • the UDM or UDR here may be a core network device different from AMF or MME and SMF.
  • the UDM or UDR may be User Data Management (UDM) and/or Unified Data Repository (UDR).
  • UDM User Data Management
  • UDR Unified Data Repository
  • the UDM or UDR will return a third response message based on the second request message.
  • the third response message may include the contract data of the PIN, which may also be referred to as PIN contract data.
  • the SMF After receiving the PIN signing data, the SMF can determine whether to agree, accept or allow the establishment of the PDU session.
  • the third request message may include all the contents contained in the second request message. Whether to accept the establishment of the PDU session may be determined by the UDM or UDR. In this case, the third response message may directly indicate whether to agree or allow the initiation of the process of establishing the PDU session. If the establishment of the PDU session is allowed, the SMF will initiate the PDU session establishment process.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by SMF and includes:
  • S3310 receiving a second request message sent by the AMF or the MME; wherein the second request message includes the PIN ID;
  • S3330 Receive a fourth response message sent by the PCF, where the fourth response message includes policy information;
  • S3350 Send a second response message to AMF or MME according to the ID of the PDU session.
  • the PCF may be any device other than AMF or MME, SMF, UDM or UDR.
  • the PCF may be a Policy Control Function (PCF), etc.
  • the SMF After receiving the second request message, if the PDU session is established based on local storage or PIN contract data from UDM or UDR or when permission is received from UDM or UDR, the SMF will obtain the PIN policy information, which can also be referred to as PIN policy information. For example, if PDU sessions associated with the PIN are frequently established and/or updated, the SMF may store the policy information of the PIN locally. If the SMF does not store the policy information locally, it may request the PCF for the policy information; or, once the SMF determines that the PIN-based PDU session is allowed to be established, it will uniformly request the PCF for the policy information of the PIN.
  • PIN policy information can also be referred to as PIN policy information. For example, if PDU sessions associated with the PIN are frequently established and/or updated, the SMF may store the policy information of the PIN locally. If the SMF does not store the policy information locally, it may request the PCF for the policy information; or, once the SMF determines that the
  • the policy information may include: one or more policy control and charging (PCC) and other policy-related information.
  • PCC policy control and charging
  • the PCC rules can be used for SMF PDU session establishment and/or PDU session management after establishment. For example, after receiving the policy information, SMF will generate N4 rules for establishing a PDU session. The N4 rules can be sent to the user plane function (UPF) related to the PDU session management.
  • UPF user plane function
  • S3340 here may include: initiating operations related to PDU session establishment.
  • the process of PDU session establishment can refer to relevant technologies, and the specific implementation will not be repeated here.
  • an embodiment of the present disclosure provides a PDU session establishment method, wherein the method is performed by SMF and includes:
  • S3410 Receive a second request message sent by the AMF or MME; wherein the second request message includes the PIN ID;
  • a rejection message is returned directly to the AMF or MME.
  • the method further comprises:
  • a UPF that supports PIN services can be selected. For example, the UPF is selected based on the subscription data of the PIN, or the UPF is selected based on the local configuration of the SMF or the policy information of the PIN. After the UPF is selected, an N4 session will be established with the UPF to establish the PDU session requested by the UE on a segment-by-segment basis.
  • establishing a session connection with UPF here can be understood as: initiating PDU session establishment based on UPF, and the established PDU session can be used for data transmission of the PIN identified by the PIN ID.
  • the purpose of the present disclosure embodiment is to support UE's request to SMF for establishing a PDU session based on a PIN ID.
  • SMF obtains PIN policy information from PCF, and sends routing policy information or policy parameters obtained based on the policy information to UPF, so that the PIN's traffic data is transmitted on a specific/expected routing path to ensure the QoS of the PIN service.
  • an embodiment of the present disclosure provides a method for establishing a protocol data unit (PDU) session, which is executed by a UDM or a UDR, wherein the method includes:
  • S0053 Send a third response message, wherein the third response message includes the signing data of the PIN; wherein the signing data of the PIN is at least used for the session management function SMF to determine whether to accept or reject the establishment of a PDU session based on the PIN ID.
  • UDM or UDR may be different from any core network equipment of AMF or MME and/or SMF.
  • the request message received from the SMF may or may not carry the PIN ID. If the request message carried by the SMF carries the PIN ID, it means that the currently received request message is a second request message for requesting the PIN's contract data or for determining whether the UE can initiate the authorization of the PDU session based on the PIN ID.
  • the second request message can be any message exchanged between the SMF and the UDM network, for example, Nudm_SDM_Get_Request and other messages.
  • UDM or UDR can assist SMF in deciding whether to accept the PIN ID-based PDU session establishment initiated by UE.
  • the second request message may also include the SUPI of the UE that initiates the PDU session establishment request.
  • the UE's contract data is obtained based on the SUPI contained in the request message sent from the SMF, and/or it is determined whether to accept the PDU session request initiated by the UE based on the UE's contract data.
  • the contract data of the PIN includes at least one of the following:
  • Capability information indicating whether the PIN identified by the PIN ID has PDU session capability, or whether the UE has PEGC and/or PMEC capabilities;
  • Time information indicating a time range in which establishment of a PDU session based on the PIN ID is permitted, or a time range in which establishment of a PDU session based on the PIN ID is prohibited (i.e., not permitted);
  • Spatial information indicating the spatial scope in which establishment of a PDU session based on the PIN ID is allowed, or prohibiting (i.e., not allowing) establishment based on the PIN ID.
  • an embodiment of the present disclosure provides a method for establishing a protocol data unit (PDU) session, which is executed by a UDM or a UDR, wherein the method includes:
  • S4110 Receive a request message sent by SMF
  • S4130 Send a third response message to the SMF, wherein the third response message includes the signing data of the PIN; wherein the signing data of the PIN is at least used for the SMF to determine whether to authorize the establishment of a PDU session based on the PIN ID.
  • an embodiment of the present disclosure provides a PDU session establishment method, which is performed by a PCF, and the method includes:
  • S0062 In response to the request message being a fourth request message including a personal Internet of Things PIN identification ID, acquiring policy information of the PIN;
  • S0063 Send a fourth response message, wherein the fourth response message includes policy information of the PIN, wherein the policy information of the PIN is used by the session management function SMF to initiate the establishment of a PDU session based on the PIN ID.
  • the PCF can be any core network device other than AMF or MME, SMF and/or UDM or UDR. If the request message sent by the SMF does not contain the PIN ID, the UE's subscription data can be obtained based on the SUPI carried in the request message.
  • Obtaining the PIN policy information here may include: generating the PIN policy information based on the PIN ID, or reading the PIN policy information stored locally.
  • the PCF may request the subscription data of the PIN from the UDM or UDR, and generate policy information of the PIN according to the subscription data of the PIN, locally generated policies and/or configuration information, etc.
  • the locally generated policy may be a reference policy used by the PCF to generate policy information including PCC rules.
  • the configuration information may be any information configured by the operator for generating PCC rules and the like.
  • the PIN policy information includes at least one of the following:
  • Selection information is used for the SMF to select a fifth network device to establish the PDU session.
  • This selection information can be used by SMF to establish a fifth network device such as UPF that responds to PDU based on PIN ID.
  • the QFI may be associated with one or more sets of QoS parameters.
  • a QoS profile may include at least one of the following: QoS rules, QoS flow levels and/or QoS parameters.
  • the QoS profile can also be used by the access device to initiate an update process based on a PDU session.
  • the QoS parameters here may include but are not limited to bandwidth parameters and/or delay parameters, etc.
  • the bandwidth parameters may include but are not limited to: minimum guaranteed bandwidth, or maximum guaranteed bandwidth and/or maximum allowed delay, etc., which can be used for monitoring PDU sessions.
  • an embodiment of the present disclosure provides a PDU session establishment method, which is performed by a PCF, and the method includes:
  • S5110 Receive a request message sent by SMF
  • S5130 Send a fourth response message to the SMF, wherein the fourth response message includes policy information of the PIN, wherein the policy information of the PIN is used by the SMF to establish a PDU session based on the PIN ID.
  • the present disclosure embodiment provides a PDU session establishment method, which includes: a user equipment UE, an access management function AMF or a mobility management entity MME and a session management function SMF; the UE sends a first request message, wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request to establish a PDU session;
  • the UE receives a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established;
  • the AMF or MME sends a second request message, wherein the second request message includes: the PIN ID; and the second request message is used by the SMF to determine whether to establish a PDU session based on the PIN ID; receive a second response message, wherein the second response message is used to indicate acceptance or refusal to establish a PDU session based on the PIN ID; send a first response message, wherein the first response message is used to indicate success or failure in establishing a PDU session based on the PIN ID;
  • the SMF receives a request message; in response to the received request message being a second request message including a personal IoT PIN identification ID, determines to accept or reject the establishment of the PDU session based on the PIN ID and the contract data of the PIN; and sends a second response message, wherein the second response message is used to indicate acceptance or rejection of establishing a PDU session based on the PIN ID.
  • the establishment of a PDU session can be used to ensure the QoS of the PIN service.
  • the method further comprises:
  • the user data management UDM or unified data storage UDR in the core network device receives the request message; in response to the request message being a third request message including the personal Internet of Things PIN identification ID, queries the contract data of the PIN; sends a third response message, wherein the third response message includes the contract data of the PIN; wherein the contract data of the PIN is at least used to determine whether to accept or refuse to establish a PDU session based on the PIN ID;
  • the policy control function PCF receives a request message; in response to the request message sent by the second network device being a fourth request message including a personal Internet of Things PIN identification ID, obtains policy information of the PIN; and sends a fourth response message, wherein the fourth response message includes the policy information of the PIN, wherein the policy information of the PIN is used to establish a PDU session based on the PIN ID.
  • the SMF can request the contract data of the PIN from the UDM or UDR.
  • PCF is used to generate PIN policy information, which can be used by SMF, UPF and/or RAN to establish a PDU session based on PIN ID and manage the PDU session.
  • an embodiment of the present disclosure provides a PDU establishment method which may include:
  • the UE sends a PDU session establishment request message to the AMF through the gNB.
  • the PDU session establishment request message includes the PIN ID.
  • AMF sends a PDU session establishment session management context request (Nsmf_PDUSession_CreateSMContext request) containing SUPI and PIN ID to SMF.
  • SMF sends a request (Nudm_SDM_Get request) including SUPI and PIN ID information to UDM to obtain the contract data related to PIN session management.
  • UDM sends a Nudm_SDM_Get response to AMF, including the contract data related to session management.
  • SMF sends Npcf_SMPolicyControl_Create request, including SUPI and PIN ID.
  • PCF sends Npcf_SMPolicyControl_Create response, including PIN policy information.
  • SMF initiates the establishment of N4 session between UPF and SMF.
  • the establishment of N4 session is equivalent to completing at least the IDE part of the network side PDU session establishment.
  • SMF sends a communication message transfer (e.g., Namf_Communication_N1N2MessageTransfer) to AMF, which includes PDU session ID, QFIs, QoS profile, etc.
  • a communication message transfer e.g., Namf_Communication_N1N2MessageTransfer
  • AMF sends a PDU session establishment accept message to the UE.
  • an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • the first sending module 110 is configured to send a first request message, wherein the first request message includes: a personal Internet of Things PIN identification ID, and the first request message is used to request a core network device to establish a PDU session;
  • the first receiving module 120 is configured to receive a first response message, wherein the first response message is used to indicate whether the PDU session based on the PIN ID is successfully established.
  • the PDU session establishing device may be a UE, and the UE may be a PINE such as a PEGC and/or PEMC of a PIN.
  • the first sending module 110 and the first receiving module 120 may be a transceiver antenna or a network interface, or may be a program module, a programmable array or a dedicated integrated circuit capable of performing the above operations. It can be understood that the device also includes:
  • a determination module configured to determine whether the PDU session to be established is associated with the PIN service
  • the first sending module 110 is configured to send a first request message to the first network device when the PDU session to be established is associated with the PIN service.
  • the determination module can be configured to perform at least one of:
  • the service involved in the PDU session to be established includes the PIN service, it is determined that the PDU session to be established is associated with the PIN service.
  • the UE is a personal Internet of Things PIN gateway PEGC.
  • an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • the second receiving module 210 is configured to receive a message requesting to establish a PDU session
  • the first determination module 220 is configured to determine whether to accept or reject the PDU session based on the PIN ID in response to the message requesting to establish the PDU session being a first request message including the personal Internet of Things PIN identification ID;
  • the second sending module 230 is configured to send a first response message, wherein the first response message is used to indicate to the user equipment UE whether the PDU session based on the PIN ID is successfully established or failed.
  • the PDU session establishing device may be a core network device such as MME, AMF, SMF, UDM, UDR and/or PCF.
  • the second receiving module, the first determining module and the second sending module may be transceiver antennas or network interfaces, or may be program modules, programmable arrays or application-specific integrated circuits capable of performing the above operations.
  • the first determination module is configured to establish a PDU session in response to the message requesting to establish a PDU session being a first request message including a personal Internet of Things PIN identification ID, and the signing data of the PIN identified by the PIN ID allows the establishment of a PDU session, and establish a PDU session based on the PIN ID.
  • the first determination module is configured to respond to the message requesting to establish a PDU session as a first request message including a personal Internet of Things PIN identification ID, and the signing data of the PIN identified by the PIN ID does not allow the establishment of a PDU session, and reject the PDU session based on the PIN ID.
  • an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • the third receiving module 310 is configured as a third sending module, and is configured to send a second request message in response to the message requesting to establish a PDU session being a first request message including a personal Internet of Things PIN identification ID, wherein the second request message includes: the PIN ID; and the second request message is used by the session management function SMF to determine whether to accept or refuse to establish a PDU session based on the PIN ID;
  • the third sending module 320 is configured to receive a second response message, wherein the second response message is used to indicate acceptance or rejection of establishing a PDU session based on the PIN ID;
  • the third sending module 320 is also configured to send a first response message, wherein the first response message is used to indicate to the user equipment UE whether the PDU session based on the PIN ID is successfully established or failed.
  • the PDU session establishment device may be a core network device such as AMF or MME.
  • the third receiving module 310 and the third sending module 320 may be transceiver antennas or network interfaces, or may be program modules, programmable arrays or application-specific integrated circuits capable of performing the above operations.
  • the device also includes:
  • the first selection module is configured to select the SMF supporting the PIN service session in response to the message requesting to establish the PDU session being a first request message including a personal Internet of Things PIN identification ID.
  • the second response message in response to the second response message including the PDU session ID, the second response message also includes at least one of the following:
  • an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, wherein the device includes:
  • the fourth receiving module 410 is configured as a fourth receiving module, configured to receive a request message
  • the second determination module 420 is configured to determine, in response to the received request message being a second request message including a personal Internet of Things PIN identification ID, whether to accept or reject the establishment of the PDU session according to the PIN ID and the contract data of the PIN;
  • the fourth sending module 430 is configured to send a second response message, wherein the second response message is used to instruct the access management function AMF or the mobility management entity MME to accept or refuse to establish a PDU session based on the PIN ID.
  • the PDU session establishment device can be SMF
  • the fourth receiving module 410, the second determining module 420 and the fourth sending module 430 may be transceiver antennas or network interfaces, or program modules, programmable arrays or application-specific integrated circuits capable of performing the above operations.
  • the fourth sending module 410 is also configured to send a third request message, wherein the third request message includes the PIN ID, and the third request message is used to request the contract data of the PIN; the fourth receiving module is also configured to receive a third response message, wherein the third response message includes the contract data of the PIN.
  • the fourth sending module is also configured to, when the establishment of a PDU session based on the PIN ID is allowed, the PCF sends a fourth request message; wherein the fourth request message includes the PIN ID, and the fourth request message is used to request policy information; the fourth receiving module is also configured to receive a fourth response message, wherein the fourth response message includes the policy information; the policy information is used to establish the PDU session.
  • the device also includes: a second selection module, configured to select a user plane function UPF in the core network device according to the subscription data of the PIN in response to allowing the establishment of a PDU session based on the PIN ID; wherein the UPF is used to establish the PDU session.
  • a second selection module configured to select a user plane function UPF in the core network device according to the subscription data of the PIN in response to allowing the establishment of a PDU session based on the PIN ID; wherein the UPF is used to establish the PDU session.
  • an embodiment of the present disclosure provides a device for establishing a protocol data unit (PDU) session, the device comprising:
  • the fifth receiving module 510 is configured to receive a request message
  • the query module 520 is configured to query the contract data of the PIN in response to the request message sent by the second network device being a third request message including the personal Internet of Things PIN identification ID;
  • the fifth sending module 530 is also configured to send a third response message, wherein the third response message includes the signing data of the PIN; wherein the signing data of the PIN is at least used by the session management function SMF to determine whether to accept or reject the establishment of a PDU session based on the PIN ID.
  • the PDU session establishing device may be a core network device such as UDM or UDR.
  • the fifth receiving module 510, the query module 520 and the fifth sending module 530 may be transceiver antennas or network interfaces, or may be program modules, programmable arrays or application-specific integrated circuits capable of performing the above operations.
  • the apparatus further comprises:
  • the second selection module is configured to respond to allowing the establishment of a PDU session based on the PIN ID and select a user plane function UPF in the core network device according to the subscription data of the PIN; wherein the UPF is used to establish the PDU session.
  • contract data of the PIN includes at least one of the following:
  • Capability information indicating whether the PIN identified by the PIN ID has PDU session capability, or whether the UE has PEGC and/or PEMC capabilities;
  • Time information indicating a time range during which a PDU session is allowed to be established based on the PIN ID, or a time range during which a PDU session is prohibited to be established based on the PIN ID;
  • Spatial information indicating a spatial range in which a PDU session is allowed to be established based on the PIN ID, or a spatial range in which a PDU session is prohibited to be established based on the PIN ID;
  • Bandwidth information indicating the bandwidth range allowed for the PDU session established based on the PIN ID.
  • an embodiment of the present disclosure provides a protocol data unit (PDU) session establishment device, the device comprising:
  • the sixth receiving module 610 is configured to receive a request message
  • the acquisition module 620 is configured to acquire the policy information of the PIN in response to the request message sent by the second network device being a fourth request message including the personal Internet of Things PIN identification ID;
  • the sixth sending module 630 is configured to send a fourth response message, wherein the fourth response message includes policy information of the PIN, wherein the policy information of the PIN is used by the session management function SMF to establish a PDU session based on the PIN ID.
  • the PDU session establishing device may be a PCF.
  • the sixth receiving module, the acquiring module and the sixth sending module may be transceiver antennas or network interfaces, or may be program modules, programmable arrays or application-specific integrated circuits capable of performing the above operations.
  • the policy information of the PIN includes at least one of the following:
  • the selection information is used for the second network device to select a fifth network device for establishing a PDU session.
  • An embodiment of the present disclosure provides a communication system, which is used to execute the aforementioned PDU session establishment method executed by the UE and by the AMF or MME.
  • the present disclosure provides a communication system, which includes the following network elements:
  • An access management function AMF or a mobility management entity MME used in the PDU session establishment method provided by any technical solution of the third aspect
  • a session management function SMF for executing the PDU session establishment method provided by any technical solution of the fourth aspect
  • a user data manager UDM or a unified data repository UDR for executing the PDU session establishment method provided by any technical solution of the fifth aspect
  • a policy control function PCF used to execute the PDU session establishment method provided by the technical solution of the sixth aspect.
  • the present disclosure provides a communication device, including:
  • a memory for storing processor-executable instructions
  • the processor is configured to execute the PDU session method provided by any of the aforementioned technical solutions.
  • the processor may include various types of storage media, which are non-transitory computer storage media that can continue to retain information stored thereon after the communication device loses power.
  • the communication device includes: UE or network equipment.
  • the network equipment may be network equipment such as AMF, MME, SMF, PCF, UDM, UDR and/or PCF.
  • the processor can be connected to the memory via a bus, etc., and is used to read the executable program stored in the memory, for example, at least one of the methods shown in Figures 1B to 1E, 2A to 2B, 3A to 3B, 4A to 4D, 5A to 5B, and 6A to 6B to 7.
  • the UE 800 may be a mobile phone, a computer, a digital broadcast user equipment, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • UE 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input/output (I/O) interface 812 , a sensor component 814 , and a communication component 816 .
  • the processing component 802 generally controls the overall operation of the UE 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to generate all or part of the steps of the above-described method.
  • the processing component 802 may include one or more modules to facilitate interaction between the processing component 802 and other components.
  • the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
  • the memory 804 is configured to store various types of data to support operations on the UE 800. Examples of such data include instructions for any application or method operating on the UE 800, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 804 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk, or optical disk.
  • the power component 806 provides power to various components of the UE 800.
  • the power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the UE 800.
  • the multimedia component 808 includes a screen that provides an output interface between the UE 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the UE 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), and when the UE 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal may be further stored in the memory 804 or sent via the communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • I/O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.
  • the sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the UE 800.
  • the sensor assembly 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the UE 800, the sensor assembly 814 can also detect the position change of the UE 800 or a component of the UE 800, the presence or absence of user contact with the UE 800, the UE 800 orientation or acceleration/deceleration and the temperature change of the UE 800.
  • the sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor assembly 814 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • the communication component 816 is configured to facilitate wired or wireless communication between the UE 800 and other devices.
  • the UE 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • UE 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors, or other electronic components to perform the above methods.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the UE 800 to generate the above method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
  • the network device 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions that can be executed by the processing component 922, such as an application.
  • the application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to execute any of the aforementioned methods for applying the above-mentioned method to the access device, for example, at least one of the methods shown in FIGS. 1B to 1E , 2A to 2B, 3A to 3B, 4A to 4D, 5A to 5B, 6A to 6B to 7 .
  • the network device 900 may also include a power supply component 926 configured to perform power management of the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input/output (I/O) interface 958.
  • the network device 900 may operate based on an operating system stored in the memory 932, such as Windows Server TM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • each step in a certain implementation mode or example can be implemented as an independent example, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain implementation mode or example can also be implemented as an independent example, and the order of the steps in a certain implementation mode or example can be arbitrarily exchanged.
  • the optional methods or optional examples in a certain implementation mode or example can be arbitrarily combined; in addition, the various implementation modes or examples can be arbitrarily combined. For example, some or all steps of different implementation modes or examples can be arbitrarily combined, and a certain implementation mode or example can be arbitrarily combined with the optional methods or optional examples of other implementation modes or examples.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供一种PDU会话方法及装置、通信设备及存储介质。该由用户设备UE执行的PDU会话建立方法可包括：发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。

Description

PDU会话方法及装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种协议数据单元(Protocol Data Unit，PDU)会话建立方法及装置、电子设备及存储介质。
 背景技术
个人物联网(Personal Internet Network,PIN)由使用PIN直接连接或网络连接进行通信的PIN单元(Personal Internet Network Element,PINE)组成，并在本地进行管理。PIN内的PINE可包括：普通(normal)PINE、具有网关能力的PINE(PINE with Gateway Capability，PEGC)以及具有管理能力的PINE(PINE with Management Capability,PEMC)。PEGC可用于PIN与移动通信网络之间的连接。PEMC可用于PIN的本地管理。
典型的普通PINE可包括但不限于：可穿戴设备网络和智能家居/智能办公设备。PINE可通过PEGC接入第五代移动通信网络(5th Generation，5G)，并可以基于5G等移动通信网络与不在PIN内的设备通信。
发明内容
本公开实施例提供一种PDU会话方法及装置、通信设备及存储介质。
本公开实施例第一方面提供一种PDU会话方法，其中，由用户设备(User Equipment，UE)执行，所述方法包括：
发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
本公开实施例第二方面提供一种协议数据单元PDU会话建立方法，其中，
由核心网设备执行，所述方法包括：
响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
本公开实施例第三方面提供一种协议数据单元PDU会话建立方法，其中，由接入管理功能AMF或者移动管理实体MME执行，所述方法包括：
响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接受或拒绝建立基于PIN ID的PDU会话；
接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败。
本公开实施例第四方面提供一种协议数据单元PDU会话建立方法，由核心网设备中的会话管理功能SMF执行，所述方法包括：
接收请求消息；
响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
发送第二响应消息，其中，所述第二响应消息，用于接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
本公开实施例第五方面提供一种协议数据单元PDU会话建立方法，由核心网设备中的用户数据管理UDM或者统一数据仓储UDR执行，其中，所述方法包括：
接收请求消息；
响应于所述请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于供会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
本公开实施例第六方面提供一种协议数据单元PDU会话建立方法，由核心网设备中的策略控制功能PCF执行，所述方法包括：
接收请求消息；
响应于所述请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF发起基于所述PIN ID的PDU会话的建立。
本公开实施例第七方面提供一种协议数据单元PDU会话建立装置，其中，所述装置包括：
第一发送模块，被配置为发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
第一接收模块，被配置为接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
本公开实施例第八方面提供一种协议数据单元PDU会话建立装置，其中，所述装置包括：
第一确定模块，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
第二发送模块，被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
本公开实施例第九方面提供一种协议数据单元PDU会话建立装置，其中，所述装置包括：
第三发送模块，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接收或拒绝建立基于PIN ID的PDU会话；
第三接收模块，被配置为接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
第三发送模块，被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
本公开实施例第十方面提供一种协议数据单元PDU会话建立装置，其中，所述装置包括：
第四接收模块，被配置为接收请求消息；
第二确定模块，被配置为响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
第四发送模块，被配置为发送第二响应消息，其中，所述第二响应消息，用于向接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
本公开实施例第十一方面提供一种协议数据单元PDU会话建立装置，所述装置包括：
第五接收模块，被配置为接收请求消息；
查询模块，被配置为响应于所述第二网络设备发送的请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
第五发送模块，被配置为发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
本公开实施例第十二方面提供一种协议数据单元PDU会话建立装置，所述装置包括：
第六接收模块，被配置为接收请求消息；
获取模块，被配置为响应于所述第二网络设备发送的请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
第六发送模块，被配置为发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF基于所述PIN ID建立PDU会话。
本公开实施例第十三方面提供一种PDU会话建立方法，其中，包括：用户设备UE、接入管理功能AMF或者移动管理实体MME以及会话管理功能SMF；所述UE发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于请求建立PDU会话；
所述UE接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功；
所述AMF或者MME响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于所述SMF确定是否建立基于PIN ID的PDU会话；接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败；
所述SMF接收请求消息；响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；发送第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话。
本公开实施例第十四方面提供一种通信系统，其中，用于前述第一方面和第二方面提供的PDU会话建立方法。
本公开实施例第十五方面提供一种通信系统，其中，包括如下网元：
用于执行前述第三方面提供的方法接入管理功能AMF或者移动管理实体MME；
用于执行前述第四方面提供的方法的会话管理功能SMF；
用于执行前述第五方面提供的方法的用户数据管理UDM或者统一数据仓储UDR；
用于执行前述第六方面提供的方法的策略控制功能PCF。
本公开实施例第十六方面提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如前述第一方面至第六方面任意以及第十二方面任意一个方面提供的技术方案。
本公开实施例第十七方面提供一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如前述第一方面至第六方面任意以及第十二方面任意一个方面提供的技术方案。
本公开实施例提供的技术方案，UE会可以基于PIN ID发起PDU会话，如此通过PDU会话的建立流程，确保PIN业务的服务质量。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开实施例。
 附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开实施例，并与说明书一起用于解释本公开实施例的原理。
图1A是根据一示例性实施例示出的一种无线通信系统的结构示意图；
图1B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图1C是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图1D是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图1E是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图2A是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图2B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图3A是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图3B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图4A是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图4B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图4C是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图4D是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图5A是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图5B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图6A是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图6B是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图7是根据一示例性实施例示出的一种PDU会话建立方法的流程示意图；
图8是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图9是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图10是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图11是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图12是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图13是根据一示例性实施例示出的一种PDU会话建立装置的结构示意图；
图14是根据一示例性实施例示出的一种UE的结构示意图；
图15是根据一示例性实施例示出的一种网络设备的结构示意图。
 具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开所使用的单数形式的一种、所述和该也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语和/或是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语如果可以被解释成为在……时或当……时或响应于确定。
请参考图1A，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1A所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个UE 11以及若干个接入设备12。在一些实施例中，该通信系统还可包括：一个或多个核心网设备，在图1中未示出核心网设备。该核心网设备包括但不限于：移动管理实体(Mobile Management Entity,MME)或接入管理功能(Access Management Function,AMF)、会话管理功能(Session Management Function,SMF)、策略控制功能(Policy Control Function,PCF)和/或用户面功能(User Plane Function,UPF)等。
其中，UE 11可以是指向用户提供语音和/或数据连通性的设备。UE 11可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，UE 11可以是物联网UE，如传感器设备、移动电话(或称为蜂窝电话)和具有物联网UE的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment，UE)。或者，UE 11也可以是无人飞行器的设备。或者，UE 11也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，UE 11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
接入设备12可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC系统。
其中，接入设备12可以是4G系统中采用的演进型基站(eNB)。或者，接入设备12也可以是5G系统中采用集中分布式架构的基站(gNB)。当接入设备12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对接入设备12的具体实现方式不加以限定。
接入设备12和UE 11之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
PIN连接支持可允许PINE的通信。这种PINE的通信可包括：PINE直连进行的PINE之间的通信、基于PEGC进行的PINE之间的通信，和/或基于PEGC以及移动通信网络(例如如图1所示的4G和/或5G)进行PINE之间或PINE与PIN外部设备之间通信。
PINE内可运行有一个或多个应用程序(Application,APP)，不同的APP对应的业务可能具有不同的服务质量(Quality of Service,QoS)要求，如此，就要求PEGC中转、中继或者透传的业务数据满足对应的QoS要求。因此如何确保PIN业务的QoS是相关技术亟待进一步解决的问题。
如图1B所示，本公开实施例提供一种PDU会话建立方法，可由UE执行，包括：
S0011：发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
S0012：接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
该UE可为能够连接到移动通信网络的终端设备，示例性地，该UE可为能够连接到4G或5G网络的终端设备。该UE可包括但不限于：手记、平板电脑、可穿戴式设备、智能家居设备、智能办公设备、车载设备和/或飞行设备等。总之，该UE能够与图1A所示的接入设备连接，从而使用移动通信网络。
UE可以发送第一请求消息，该第一请求消息包括PIN ID。该PIN ID可用于标识基于UE建立的PIN，或者，UE所属的PIN。第一请求消息被中继或者转发至核心网设备之后，可用于核心网设备接收或拒绝该UE基于PIN ID请求建立的PDU会话。
PIN内可包括一个或多个PINE，这些PINE可为智能家居设备、智能办公设备、智能充电设备、智能售货设备等。当然此处仅仅是对PIN内的PINE的举例说明，具体实现时不局限于该举例。
此处的第一响应消息，也即用于供UE确定是否被授权基于PIN ID建立PDU会话，若UE被授权基于PIN ID建立PDU会话，则网络侧的网络设备会启动PDU会话建立，也即代表基于PIN ID的PDU会话建立成功，否则建立失败。第一响应消息可以通过自身的消息格式和/或携带的内容，指示基于所述PIN ID的PDU会话是否建立成功。
该第一请求消息请求建立基于PIN或说基于PIN ID的PDU会话。第一请求消息可为PDU会话建立请求消息。该基于PIN或者PIN ID的PDU会话，可用于传输PIN业务的业务数据。
若UE发送了第一请求消息之后，会收到核心网设备返回的第一响应消息，该第一响应消息可为响应成功消息或者响应失败消息。响应成功消息可用于指示第一网络设备接受PDU会话的建立，响应失败消息可指示第一网络设备拒绝PDU会话的建立。
若第一响应消息为成功响应消息，则第一响应消息可包括：核心网络设备分配的PDU会话标识(Identifier,ID)，后续UE可以基于该PDU ID进行PDU会话。故本公开实施例中，通过PDU会话的建立，可以基于PDU会话流程确保PIN业务的QoS，从而提升基于PIN的通信服务质量。
由于该UE可连接到移动通信网络，该UE可以基于自身发起与PIN业务无关的PDU会话建立请求，也可以发起基于PIN业务关联的PDU会话建立请求。即在一些实施例中，请求建立的PDU会话与PIN业务关联时，向第一网络设备发送包含PIN ID的第一请求消息。
如图2A所示，本公开实施例提供一种PDU会话建立方法，其中，由UE执行，方法包括：
S1110：向AMF或MME发送第一请求消息，其中，第一请求消息包括PIN ID，且第一请求消息用于请求建立PDU会话；
S1120：接收AMF或MME发送的第一响应消息，其中，第一响应消息，用于指示基于PIN ID的PDU会话是否建立成功。
AMF或者MME等对UE进行移动性管理的设备。
在一些实施例中，该方法还可包括：确定待建立的PDU会话是否与PIN业务关联；
所述发送第一请求消息，包括：当待建立的PDU会话与所述PIN业务关联时，发送所述第一请求消息。
即UE发起与PIN业务关联的PDU建立请求时，才在第一请求消息中携带PIN ID。若UE发起的PDU会话与PIN业务无关，则发送给第一网络设备的PDU会话建立请求不包含PIN ID，包括该UE的其他ID，例如，临时移动用户标识(Temporary Mobile Subscriber Identity，TMSI)或者用户隐藏标识符(subscription concealed identifier，SUCI)等。若第一请求消息已经包含PIN ID，可以携带该UE的TMSI或者SUCI等UE标识信息，也可以不用携带UE标识信息。
UE通过将PIN ID的携带在请求建立PDU会话的第一请求消息中，第一网络设备接收到第一请求消息之后，就会知晓当前UE请求建立的PDU会话与PIN业务关联或者与PIN ID标识的PIN关联，从而可以根据PIN的签约数据和/或PIN业务的特殊需求，确定是否接受PDU会话的建立，或者配置PDU会话的QoS参数等。
示例性地，如图2B所示，本公开实施例提供一种PDU会话建立方法，其中，由用户设备UE执行，方法包括：
S1210：确定待建立的PDU会话是否与PIN业务关联；
S1220：当待建立的PDU会话与PIN业务关联时，向第一网络设备发送第一请求消息；
S1230：接收AMF或MME发送的第一响应消息，其中，第一响应消息，指示基于PIN ID的PDU会话是否建立成功。
在一些实施例中，确定待建立的PDU会话是否与PIN业务关联，包括以下至少之一：
当接收到PIN内至少一个个人物联网单元PINE发送的PIN业务请求时，确定待建立的PDU会话与PIN业务关联；
当检测到与PIN业务关联的PDU会话建立指示时，确定待建立的PDU会话与PIN业务关联；
当待建立的PDU会话涉及的业务包含PIN业务时，确定待建立的PDU会话与PIN业务关联。
例如，PIN内的普通PINE或者PEMC可通过PIN协议等非3GPP协议和能够连接到移动通信网络的UE通信，从而将PIN业务请求发送给该UE。该UE接收到不能直接连接到移动通信网络的其他PINE的PIN业务请求时，可确认当前待建立的PDU会话与PIN业务相关。
又例如，当UE从PIN直连通信接收到一个或多个PIN业务请求时，确定待建立的PDU会话与PIN业务关联。
再例如，该UE自身也可以发起PIN业务请求，例如，在用户界面(User Interface，UI)接收到发起与PIN业务关联的PDU会话建立指示时，可认为待建立的PDU会话与PIN业务关联。示例性地，该UE作为PIN内具有与移动通信网络连接能力的PEGC、PEMC和/或普通PINE，在UI界面接收到与PIN业务关联的PDU会话建立指示，或者从上层控制设备接收到与PIN业务关联的PDU会话建立指示时，可认为有待建立的PDU会话为与PIN业务关联的PDU会话，则UE会发起基于PIN ID的PDU会话的请求建立流程。
例如，该UE内安装有一个或多个PIN业务相关的应用程序，基于这种应用程序发起的PDU，则可认为待建立的PDU会话与PIN业务关联。
在还有一些实施例中，UE发现待建立的PDU会话对应的业务标识是PIN业务的标识，总之，待发起PDU会话的业务包含PIN业务，则认为该待建立的PDU会话与PIN业务关联。
总之，在本公开实施例中，UE发送包含PIN ID的PDU会话建立请求之前，会确定待建立的PDU会话是否和PIN业务关联，在有关联的情况下，才包含PIN ID，也方便网络侧针对性提升PIN业务的通信指令。
在一些实施例中，UE为PIN网关PEGC。在另一些实施例中，该发起包含PIN ID的第一请消息的UE还可以是PMEC或者PIN内具有接入移动通信网络能力的普通PINE。若该UE是PEGC可方便PIN的PEGC统一管理PINE和移动通信网络之间的通信。
如图1C所示，本公开实施例提供一种PDU会话建立方法，由核心网设备执行，所述方法包括：
S0021：响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
S0022：发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
此处的核心网设备可为任意一个或多个核心网设备，这些核心网设备可为执行从UE直接或间接接收到第一请求消息。该第一请求消息包含PIN ID，且为该PIN ID所标识的PIN建立PDU会话，以通过PDU会话的建立，来实现对PIN业务传输的QoS。
在一些实施例中，所述响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话，包括：
响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于所述PIN ID标识的PIN的签约数据允许建立PDU会话，建立基于所述PIN ID的PDU会话。
例如，PIN的签约数据可包括以下至少之一：
PIN的签约数据包括以下至少一项：
能力信息，指示PIN ID标识的PIN是否具有PDU会话能力，或UE是否具备PEGC和/或PEMC的能力；
时间信息，指示允许基于PIN ID建立PDU会话的时间范围，或，禁止基于PIN ID建立PDU会话的时间范围；
空间信息，指示允许基于PIN ID建立PDU会话的空间范围，或禁止基于PIN ID建立PDU会话的空间范围；
带宽信息，指示基于PIN ID建立的PDU会话允许使用的带宽范围。
在一个实施例中，所述响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话，包括：
响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于所述PIN ID标识的PIN的签约数据不允许建立PDU会话，拒绝基于所述PIN ID的PDU会话。
根据PIN的签约数据确定允许或拒绝基于PIN ID建立PDU会话的方式有很多种。示例性地，在根据PIN的签约数据确定接受或拒绝建立PIN ID的PDU会话时，可以采用如下至少之一：
当能力信息指示PIN不具有PDU会话能力，或者UE不具有PEGC和/或PEMC的能力时，向第一网络设备发送拒绝消息；
当能力信息指示PIN具有PDU会话能力，或者UE具有PEGC和/或PEMC的能力时，向第一网络设备发送包含PIN ID的接受消息；
当请求PDU会话的建立时间位于允许建立PDU会话的时间范围内时，向第一网络设备发送包含PIN ID的接受消息；
当请求PDU会话的建立时间位于允许建立PDU会话的时间范围外时，向第一网络设备发送拒绝消息；
当请求PDU会话的建立时间位于禁止(也即不允许)建立PDU会话的时间范围内时，向第一网络设备发送拒绝消息；
当请求PDU会话的建立时间位于禁止(也即不允许)建立PDU会话的时间范围外时，向第一网络设备包含PIN ID的接受消息；
当请求PDU会话的UE位于允许建立PDU会话的空间范围内时，向第一网络设备发送包含PIN ID的接受消息；
当请求PDU会话的UE位于允许建立PDU会话的时间范围外时，向第一网络设备发送拒绝消息；
当请求PDU会话的UE位于禁止(也即不允许)建立PDU会话的时间范围内时，向第一网络设备发送拒绝消息；
当请求PDU会话的UE位于禁止(也即不允许)建立PDU会话的时间范围外时，向第一网络设备包含PIN ID的接受消息。
如图1D所示，本公开实施例提供一种PDU会话建立方法，其中，由AMF或者MME执行，所述方法包括：
S0031：响应于请求建立PDU会话的消息为包括PIN ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接受或拒绝建立基于PIN ID的PDU会话；
S0032：接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
S0033：发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败。
AMF或MME接收到UE发送的第一请求消息之后，可以发送第二请求消息，第二请求消息会被直接或间接发送至SMF，由SMF进一步确定接受或拒绝基于PIN ID的PDU会话建立。
在一些实施例中，所述响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，包括：
响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，选择支持PIN业务会话的所述SMF。
在网络中有可能存在支持PIN业务的SMF和不支持PIN业务的SMF。由于该PDU会话时基于PIN ID建立的，因此需要选择支持PIN业务的SMF，以实现建立的PDU会话适用于PIN业务的数据传输。
在一些实施例中，响应于所述第二响应消息包括PDU会话ID，所述第二响应消息还包括以下至少一项：
服务质量QoS流标识QFI；
QoS配置文件。
该QFI可关联到一组或多组QoS参数。第二响应消息中的QFI的个数可为一个或多个。不同QFI关联的QoS参数至少部分不同。
QoS配置文件(Profile)可包括以下至少之一：QoS规则、QoS流层级和/或QoS参数。
该QoS配置文件还可用于接入设备发起基于PDU会话的更新流程。
此处的QoS参数可包括但不限于带宽参数和/或时延参数等。该带宽参数可包括但不限于：最小保证带宽，或者最大保证带宽和/或最大允许延时等，可用于PDU会话的监控。
如图3A所示，本公开实施例提供一种协议数据单元PDU会话建立方法，其中，由AMF或MME执行，方法包括：
S2110：接收UE请求建立PDU的消息；
S2120：当请求建立PDU的消息是包括PIN ID的第一请求消息时，向SMF发送第二请求消息，其中，第二请求消息包括：PIN ID；
S2130：接收SMF发送的第二响应消息；
S2140：根据第二响应消息，向UE发送第一响应消息。
该AMF或MME可为核心网设备，该核心网设备包括但不限于对UE进行移动性管理和/或注册管理的网络设备，具体可如AMF和/或MME。
在本公开实施例中，AMF或MME会接收各种请求建立PDU会话的消息，例如，接收到携带有PIN ID的第一请求消息，可认为当前UE是基于PIN或者PIN ID请求PDU会话的建立。
若第一请求消息包括PIN ID，则会向SMF发送包含PIN ID的第二请求消息。该第二请求消息携带有PIN ID，即表明AMF或MME请求SMF确定是否可以建立UE当前请求建立的PDU会话。SMF的授权结果会在第二响应消息中携带，或者，通过第二响应消息指示。
该SMF可为不同于AMF或MME的核心网设备，示例性地，该SMF可包括但不限于会话管理功能(Session Management Function,SMF)。该SMF可PDU会话管理的专用网络设备。该第二请求消息可包括但不限于：PDU会话建立会话管理(Session Management，SM)上下文(context)请求消息。若第二请求消息为PDU会话建立会话管理(Session Management，SM)上下文(context)请求消息，则第二响应消息可为：PDU会话SM上下文响应消息。
在收到第二响应消息之后，AMF或MME可以向UE返回第一响应消息。
示例性地，第二响应消息表明接受PDU会话建立，向UE发送响应成功消息，否则向UE发送响应失败消息。该响应成功消息可包括PDU会话ID等。该响应失败消息可包括失败指示和/或原因指示。失败指示直接指示PDU会话建立失败。原因指示，指示PDU会话建立失败的原因。
如图3B所示，本公开实施例提供一种协议数据单元PDU会话建立方法，其中，由AMF或MME执行，方法包括：
S2210：接收UE请求建立PDU会话的消息；
S2220：当UE请求建立PDU的请求消息是包含PIN ID的第一请求消息时，确定支持PIN业务的SMF；
S2230：向支持PIN业务的SMF发送第二请求消息，其中，第二请求消息包括：PIN ID；
S2240：接收SMF发送的第二响应消息；
S2250：根据第二响应消息，向UE发送第一响应消息。
在核心网内部署有一个多个可作为SMF的备选设备，有的设备支持PIN业务，或者有的设备不支持PIN业务。有的设备虽然支持PIN业务的业务能力，但是当前可能并不想要提供PIN业务的服务，此时也可以认为该设备当前不支持PIN业务。
在本公开实施例中，AMF或MME接收到的第一请求消息中包含PIN ID，可认为当前UE请求建立的PDU会话与PIN业务关联，会基于预先配置确定出支持PIN业务的SMF。
例如，该预先配置可为通信运营商预先配置在AMF或MME上支持PIN和业务的SMF的标识信息和/或地址信息等。示例性地，支持PIN业务的SMF也可以提供非PIN业务的会话管理等。
总之，通过SMF的选择，可以确保建立的PDU会话提供PIN业务所需的QoS保证。
在一些实施例中，PIN请求建立时，有配置特定SMF支持其PIN业务，此时AMF或MME会在PIN建立的过程中存储PIN ID并对应存储特定SMF的信息，此时，AMF或MME可以基于PIN ID查询与该PIN ID对应的SMF的信息(例如，标识信息和/或IP地址)等，同样实现了支持PIN业务的SMF的选择，且选择了该PIN建立阶段绑定或者注册的特定SMF，从而使用该特定SMF可以为该PIN提供PIN业务的个性业务服务。
在一些实施例中，根据第二响应消息，向PEGC发送第一响应消息，包括：当第二响应消息包括PDU会话ID时，向UE发送PDU会话建立接受消息。
PDU会话建立请求消息对应的响应成功消息可为PDU会话建立接受消息。若SMF确定接受PDU会话，则会分配PDU会话ID，并发起PDU会话的建立，该PDU会话的建立包括：SMF和UPF等核心网设备之间的N4会话的建立。若AMF或MME接收到SMF分配的PDU会话ID，会认为SMF授权基于PIN或者PIN ID建立PDU会话。此时，将PDU会话ID携带在第一响应消息中，如此通过PDU会话ID告知UE当前网络侧接受PDU会话建立。
示例性地，当第二响应消息包括PDU会话ID时，第二响应消息还包括以下至少一项：
服务质量QoS流标识(Qos Flow Identifier,QFI)；
QoS配置文件。
该QFI可关联到一组或多组QoS参数。在第二响应消息中携带的QFI可为一个或多个。不同QFI可关联到不同的QoS参数。
QoS配置文件(Profile)可包括以下至少之一：QoS规则、QoS流层级和/或QoS参数。
该QoS配置文件还可用于接入设备发起基于PDU会话的更新流程。
此处的QoS参数可包括但不限于带宽参数和/或时延参数等。该带宽参数可包括但不限于：最小保证带宽，或者最大保证带宽和/或最大允许延时等，可用于PDU会话的监控。
当然以上仅仅是对QoS参数的举例，具体实现时不局限于该举例。
在一些实施例中，方法还包括：
当第二响应消息为拒绝消息时，向UE发送PDU会话建立拒绝消息。
若PDU会话建立请求消息对应的响应失败消息即为PDU会话建立拒绝消息，则可以使用非PIN业务的PDU会话建立拒绝消息的消息格式和/或封装方式，给UE发送指示PDU会话建立失败的消息，以公知PDU会话建立失败。在另一些实施例中，方法还包括：
在发送第二请求消息后的预设时长内未收到SMF发送的第二响应消息时，向UE发送PDU会话建立拒绝消息；
或者，
在发送第二请求消息后的预设时长内未收到SMF发送的第二响应消息时，向SMF重新发送第二请求消息；直到第二请求消息的已发送次数达到最大次数或者接收到拒绝消息时，向UE发送PDU会话建立拒绝消息。
在一些实施例中，方法还包括：
根据PIN ID，确定UE的用户签约永久标识SUPI；
向SMF发送包含PIN ID和SUPI的第二请求消息。
若第一请求消息未携带UE的其他标识，该UE作为PIN的PINE，其SUPI会携带在PIN的配置文件或者配置信息中存储在AMF或MME。如此，AMF或MME可以根据PIN ID查询到该UE的SUPI，而非根据UE的TMSI或者SUCI等查询其SUPI。在查询到该UE的SUPI之后，在第二请求消息中包含PIN ID的同时，还会包含该UE的SUPI。如此，方便SMF根据该SUPI确定具体建立哪个UE和网络侧之间的PDU会话。
如图1E所示，本公开实施例提供一种协议数据单元PDU会话建立方法，其中，由核心网设备中的会话管理功能SMF执行，所述方法包括：
S0041：接收请求消息；
S0042：响应于接收的请求消息为包括PIN ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
S0043：发送第二响应消息，其中，所述第二响应消息，用于接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
SMF可进行PDU会话管理的设备，该PDU会话管理包括但不限于：PDU会话建立和/或PDU会话更新等。
AMF或者MME会基于来自UE的PDU会话建立请求消息，向SMF请求PDU会话建立，则此时SMF会接收到来自AMF或MME的请求消息。此时，AMF或MME发送的请求消息可按照是否包含PIN ID可以分为两类，一类是包含PIN ID的第二请求消息，另一类是不包含PIN ID的其他请求消息。
该第二请求消息可包括来自AMF或者MME的PDU会话建立会话管理(Session Management，SM)上下文(context)请求消息。
若第二请求消息携带有PIN ID，则说明本次PDU会话的建立流程是及PIN或者PIN业务发起的，或，与PIN或PIN业务管理的。
此时，SMF会获取该PIN的签约数据，而非获取该UE的签约数据。PIN的签约数据为以PIN为签约主体，而UE的签约数据为以UE为签约主体。
根据PIN的签约数据可知：是否当前是否允许基于PIN的PDU会话建立，或者是否允许(也即授权)建立与PIN业务关联的PDU会话。
在一些实施例中，所述响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立，包括：
发送第三请求消息，其中，所述第三请求消息包括所述PIN ID，且第三请求消息用于请求所述PIN的签约数据；接收第三响应消息，其中，所述第三响应消息包括所述PIN的签约数据。
此处通过一种SMF从其他核心网设备获取PIN的签约数据的方式，具体实现时不局限于上述举例，当然SMF获取的PIN的签约数据也可以是本地存储的PIN的签约数据。
在一些实施例中，所述方法还还包括：
当允许基于所述PIN ID建立PDU会话时，PCF发送第四请求消息；其中，所述第四请求消息包括所述PIN ID，且所述第四请求消息用于请求策略信息；
接收第四响应消息，其中，所述第四响应消息包括所述策略信息；所述策略信息，用于PDU会话的建立。
如图4A所示，本公开实施例提供一种PDU会话建立方法，其中，由SMF执行，方法包括：
S3110：接收AMF或MME发送的请求消息；
S3120：当AMF或MME发送的请求消息是包括PIN ID的第二请求消息时，根据PIN ID和PIN的签约数据，向AMF或MME发送第二响应消息；其中，第二响应消息，用于供AMF或MME确定是否接受PDU会话的建立。
总之，SMF会向AMF或MME发送基于第二请求消息返回的第二响应消息。该第二响应消息可为接受消息和/或拒绝消息。若为接受消息，则SMF会发起PDU会话的建立，并且AMF或MME会基于该接受消息告知UE同意PDU会话的建立，以及正在建立或者已经发起建立的PDU会话的ID(也即PDU会话ID)。
若为拒绝消息，则SMF不会基于第二请求消息发起PDU会话建立。在一些实施例中，会在该拒绝消息中携带失败原因。
该失败原因可指示以下至少之一：
该PIN ID所标识PIN不具有请求PDU会话的授权；
请求建立PDU会话的建立时刻不包含该PIN授权建立的PDU会话的有效时间，该建立时刻可为SMF接收到第二请求消息的当前时刻，或者第二请求消息中携带的时间信息指示的建立时刻。若第二请求消息携带的时间信息可来自第一请求消息。例如，PIN预先请求PDU会话在特定时刻建立，则此时第一请求消息会携带指示该特定时刻的时间信息，此时该时间信息会被携带在第二请求消息中同样被SMF所接受。
请求建立PDU会话的PINE位于该PIN授权建立的PDU会话的有效空间范围外。例如，手机或可穿戴设备作为该UE，若有效空间范围为以该用户的家位置为中心的100米内，而手机或可穿戴设备被用户携带至家100米以外的办公室，此时手机基于PIN ID发起PDU会话建立，可能被认为在有效空间范围外，则这种PDU会话可能会被拒绝。
当然以上仅仅是根据PIN的签约数据发送拒绝消息时，拒绝原因指示的一种或多种可能的PDU会话建立失败的原因。
若一个PIN多次请求建立PDU会话，则SMF会本地存储有该PIN的签约数据，此时SMF本地查询该PIN的签约数据即可。
若SMF本地未存储有PIN的签约数据，则可以向UDM或UDR请求PIN的签约数据。
示例性地，PIN的签约数据包括以下至少一项：
能力信息，指示PIN ID标识的PIN是否具有PDU会话能力，或UE是否具备PEGC和/或PMEC的能力；
时间信息，指示允许基于PIN ID建立PDU会话的时间范围，或，禁止基于PIN ID建立PDU会话的时间范围；
空间信息，指示允许基于PIN ID建立PDU会话的空间范围，或禁止基于PIN ID建立PDU会话的空间范围；
带宽信息，指示基于PIN ID建立的PDU会话允许使用的带宽范围。
S3120可包括以下至少之一：
当能力信息指示PIN不具有PDU会话能力，或者UE不具有PEGC和/或PEMC的能力时，向AMF或MME发送拒绝消息；
当能力信息指示PIN具有PDU会话能力，或者UE具有PEGC和/或PEMC的能力时，向AMF或MME发送包含PIN ID的接受消息；
当请求PDU会话的建立时间位于允许建立PDU会话的时间范围内时，向AMF或MME发送包含PIN ID的接受消息；
当请求PDU会话的建立时间位于允许建立PDU会话的时间范围外时，向AMF或MME发送拒绝消息；
当请求PDU会话的建立时间位于禁止(也即不允许)建立PDU会话的时间范围内时，向AMF或MME发送拒绝消息；
当请求PDU会话的建立时间位于禁止(也即不允许)建立PDU会话的时间范围外时，向AMF或MME包含PIN ID的接受消息；
当请求PDU会话的UE位于允许建立PDU会话的空间范围内时，向AMF或MME发送包含PIN ID的接受消息；
当请求PDU会话的UE位于允许建立PDU会话的时间范围外时，向AMF或MME发送拒绝消息；
当请求PDU会话的UE位于禁止(也即不允许)建立PDU会话的时间范围内时，向AMF或MME发送拒绝消息；
当请求PDU会话的UE位于禁止(也即不允许)建立PDU会话的时间范围外时，向AMF或MME包含PIN ID的接受消息。
在一些实施例中，PIN的签约数据还可指示是否允许PIN内的其他PINE发起与PIN业务关联的PDU会话。示例性地，PIN的签约数据可指示是否允许PIN内的PEMC和/或具有移动通信能力的普通PINE发起PIN业务关联的PDU会话。故在一些情况下，S3120还可包括：
当基于PIN ID发起的PDU会话的UE为普通PINE或者PEMC时，根据PIN的签约数据确定是否允许该UE发起基于PIN ID的会话请求，若允许则向AMF或MME包含PIN ID的接受消息，否则向AMF或MME发送拒绝消息。
如图4B所示，本公开实施例提供一种PDU会话建立方法，其中，由SMF执行，方法包括：
S3210：接收AMF或MME发送的请求消息；
S3220：当AMF或MME发送的请求消息是包括PIN ID的第二请求消息时，根据PIN ID，向UDM或UDR发送第三请求消息，其中，第三请求消息包括PIN ID，且第三请求消息用于请求PIN的签约数据；
S3230：接收UDM或UDR返回的第三响应消息，其中，第三响应消息包括PIN的签约数据；
S3240：根据PIN的签约数据，向AMF或MME发送第二响应消息；其中，第二响应消息，用于供AMF或MME确定是否接受PDU会话的建立。
此处的UDM或UDR可为不同于AMF或MME和SMF的核心网设备。示例性地，该UDM或UDR可为用户数据管理(User Data Management,UDM)和/或统一数据仓储(Unified Data Repository，UDR)。
第二请求消息中携带有PIN ID，则UDM或UDR会基于第二请求消息返回第三响应消息，该第三响应消息可包括该PIN的签约数据，该签约数据也可以称之为PIN签约数据。
在收到该PIN签约数据之后，SMF就可以确定出是否同意或者接受或允许建立该PDU会话。
又示例性地，在一些实施例中，第三请求消息可包括第二请求消息所包含的所有内容，是否接受PDU会话的建立，可以由UDM或UDR来确定，此时，第三响应消息可直接指示是否同意或允许发起该PDU会话建立的流程。如果该PDU会话的建立被允许，则SMF会发起PDU会话建立流程。
如图4C所示，本公开实施例提供一种PDU会话建立方法，其中，由SMF执行，方法包括：
S3310：接收AMF或MME发送的第二请求消息；其中，第二请求消息包括PIN ID；
S3320：当允许基于PIN ID建立PDU会话时，向PCF发送第四请求消息；其中，第四请求消息包括PIN ID，且第四请求消息用于请求策略信息；
S3330：接收PCF发送的第四响应消息，其中，第四响应消息包括策略信息；
S3340：根据策略信息，建立PDU会话；
S3350：根据PDU会话的ID，向AMF或MME发送第二响应消息。
PCF可为不同于AMF或MME、SMF以及UDM或UDR的任意设备。该PCF可为策略控制功能(Policy Control Function,PCF)等。
在接收到该第二请求消息之后，若根据本地存储或者从UDM或UDR的PIN签约数据或收到UDM或UDR允许建立PDU会话时，SMF会获取PIN的策略信息，该PIN的策略信息也可以称之为PIN策略信息。例如，若频繁有与该PIN关联的PDU会话建立和/或更新等，则SMF可能本地存储有该PIN的策略信息。若SMF本地未存储有，可向PCF请求策略信息；或者，SMF一旦确定允许基于PIN的PDU会话建立时，则会统一向PCF请求该PIN的策略信息。
该策略信息可包括：一个或多个策略控制和计费(Policy Control and Charging，PCC)等与策略相关的信息。该PCC规则可用于SMF的PDU会话建立和/或PDU会话建立之后管理。例如，SMF接收到该策略信息之后，会生成建立PDU会话的N4规则等。该N4规则可被下发至与该PDU会话管理的用户面功能(User Plane Function,UPF)。此处的S3340可包括：发起PDU会话建立相关的操作，此处PDU会话建立的流程可以参考相关技术，具体实现就不在此进行赘述。
如图4D所示，本公开实施例提供一种PDU会话建立方法，其中，由SMF执行，方法包括：
S3410：接收AMF或MME发送的第二请求消息；其中，第二请求消息包括PIN ID；
S3420：当不允许基于PIN ID建立PDU会话时，向AMF或MME发送拒绝消息。
例如，SMF本地存储的PIN签约数据和/或从UDM或UDR请求的PIN签约数据或者UDM或UDR指示不允许基于PIN的PDU会话时，直接向AMF或MME返回拒绝消息。
在一些实施例中，方法还包括：
当允许基于PIN ID建立PDU会话时，选择UPF；该UPF用于建立基于PIN ID的PDU会话。
若允许基于PIN建立PDU会话，可选择支持PIN业务的UPF。示例性地，基于PIN的签约数据选择UPF，或者，基于SMF的本地配置或者PIN的策略信息选择UPF。在选择出UPF之后，会与UPF建立N4会话，以逐网段建立UE请求建立的PDU会话。
示例性地，此处的与UPF建立会话连接，可理解为：基于UPF发起PDU会话建立，该建立的PDU会话，可用于PIN ID所标识PIN的数据传输。
本公开实施例是为了支持UE向SMF请求基于PIN ID的PDU会话建立请求，SMF从PCF获得PIN策略信息，并将路由策略信息或者基于策略信息得到的策略参数发送给UPF，使PIN的流量数据在特定/期望的路由路径上传输，以确保PIN业务的QoS。
如图5A所示，本公开实施例提供一种协议数据单元PDU会话建立方法，由UDM或UDR执行，其中，所述方法包括：
S0051：接收请求消息；
S0052：响应于所述请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
S0053：发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于供会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
UDM或UDR可不同于AMF或MME和/或SMF的任意核心网设备。
从SMF接收的请求消息可携带PIN ID，也可以不携带PIN ID。若从SMF携带的请求消息携带PIN ID，则说明当前接收的请求消息为请求PIN的签约数据或者用于确定UE是否可以基于PIN ID发起PDU会话的授权的第二请求消息。该第二请求消息可为SMF和UDM等网络之间交互的任意消息，例如，Nudm_SDM_Get_Request等消息。
如此UDM或UDR可辅助SMF是否接受UE发起的基于PIN ID的PDU会话建立。
值得注意的是：第二请求消息也可包括发起PDU会话请求建立的UE的SUPI。
若从SMF接收的请求消息不包含PIN ID，则根据从SMF发送的请求消息包含的SUPI，获取UE的签约数据，和/或根据UE的签约数据确定是否接受UE发起的PDU会话请求。
在一些实施例中，所述PIN的签约数据包括以下至少一项：
能力信息，指示所述PIN ID标识的PIN是否具有PDU会话能力，或所述UE是否具备PEGC和/或PMEC的能力；
时间信息，指示允许基于所述PIN ID建立PDU会话的时间范围，或，禁止(即不允许)基于所述PIN ID建立PDU会话的时间范围；
空间信息，指示允许基于所述PIN ID建立PDU会话的空间范围，或禁止(即不允许)基于所述PIN ID建立。
当然以上仅仅是对PIN的签约数据的举例，具体实现时不局限于该举例。
如图5B所示，本公开实施例提供一种协议数据单元PDU会话建立方法，由UDM或UDR执行，其中，所述方法包括：
S4110：接收SMF发送的请求消息；
S4120：当所述SMF发送的请求消息为包括个人物联网PIN标识ID的第三请求消息时，查询所述PIN的签约数据；
S4130：向所述SMF发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于供所述SMF是否授权基于所述PIN ID建立PDU会话。
如图6A所示，本公开实施例提供一种PDU会话建立方法，由PCF执行，所述方法包括：
S0061：接收请求消息；
S0062：响应于所述请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
S0063：发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF发起基于所述PIN ID的PDU会话的建立。
该PCF可为不同于AMF或MME、SMF和/或UDM或UDR的任意核心网络设备。若SMF发送的请求消息不包含PIN ID，可以根据请求消息中携带的SUPI获取UE的签约数据。
此处获取PIN的策略信息可包括：根据PIN ID生成PIN的策略信息，或者，读取本地存储的该PIN的策略信息。
在一些实施例中，PCF可从UDM或UDR请求PIN的签约数据，根据PIN的签约数据、本地生成策略和/或配置信息等，生成PIN的策略信息。
本地生成策略可为PCF用于生成包含PCC规则的策略信息的参考策略。
配置信息可为运营商配置的任意用于生成PCC规则等信息。
在一些实施例中，所述PIN的策略信息包括以下至少一项：
服务质量QoS流标识QFI；
QoS配置文件；
选择信息，用于供所述SMF选择建立所述PDU会话的第五网络设备。
该选择信息，可用于SMF建立基于PIN ID的PDU回复的UPF等第五网络设备。
该QFI可关联到一组或多组QoS参数。
QoS配置文件(Profile)可包括以下至少之一：QoS规则、QoS流层级和/或QoS参数。
该QoS配置文件还可用于接入设备发起基于PDU会话的更新流程。
此处的QoS参数可包括但不限于带宽参数和/或时延参数等。该带宽参数可包括但不限于：最小保证带宽，或者最大保证带宽和/或最大允许延时等，可用于PDU会话的监控。
当然以上仅仅是对QoS参数的举例，具体实现时不局限于该举例。
如图6B所示，本公开实施例提供一种PDU会话建立方法，由PCF执行，所述方法包括：
S5110：接收SMF发送的请求消息；
S5120：当所述SMF发送的请求消息是包括PIN ID第四请求消息时，获取所述PIN的策略信息；
S5130：向所述SMF发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于所述SMF基于所述PIN ID建立PDU会话。
本公开实施例提供一种PDU会话建立方法，其中，包括：用户设备UE、接入管理功能AMF或者移动管理实体MME以及会话管理功能SMF；所述UE发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于请求建立PDU会话；
所述UE接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功；
所述AMF或者MME响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于所述SMF确定是否建立基于PIN ID的PDU会话；接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败；
所述SMF接收请求消息；响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；发送第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话。
该实施例涉及的UE、AMF、MME、SMF、PIN、PIN ID以及PDU会话等相关描述，都可以参见前述实施例，具体实现时不局限于前述举例。
通过这种方式，可以使用PDU会话的建立，确保PIN业务的QoS。
在一些实施例中，所述方法还包括：
核心网设备中的用户数据管理UDM或者统一数据仓储UDR接收请求消息；响应于所述请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于确定接受或拒绝建立基于所述PIN ID的PDU会话；
和/或，
策略控制功能PCF接收请求消息；响应于所述第二网络设备发送的请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于所基于所述PIN ID建立PDU会话。
PIN的签约数据没有在SMF上有缓存时，SMF可以到UDM或者UDR上请求该PIN的签约数据。
PCF用于PIN的策略信息的生成，该策略信息可用于SMF、UPF和/或RAN等建立基于PIN ID的PDU会话，并对该PDU会话进行管理。
如图7所示，本公开实施例提供一种PDU建立方法可包括：
1、UE通过gNB向AMF发送PDU会话建立请求消息，该PDU会话建立请求消息包括PIN ID。
2、AMF向SMF发送包含SUPI以及PIN ID的PDU会话建立会话管理上下文)请求(Nsmf_PDUSession_CreateSMContext request)。
3、SMF向UDM发送包括SUPI以及PIN ID等信息的获取请求(Nudm_SDM_Get request)，以获取PIN的会话管理相关的签约数据。
4、UDM向AMF发送Nudm_SDM_Get响应，包括会话管理相关的签约数据。
5、SMF发送Npcf_SMPolicyControl_Create请求，包括SUPI以及PIN ID。
6、PCF发送Npcf_SMPolicyControl_Create响应，包括PIN的策略信息。
7、SMF发起UPF和SMF之间的N4会话建立。该N4会话的建立，相当于至少完成了网络侧PDU会话建立IDE部分内容。
8、SMF向AMF发送通消息传输(例如，Namf_Communication_N1N2MessageTransfer)，该消息传输包括PDU会话ID、QFIs、QoS配置文件(profile)等。
9、AMF向UE发送PDU会话建立接受消息。
如图8所示，本公开实施例提供一种协议数据单元PDU会话建立装置，其中，装置包括：
第一发送模块110，被配置为发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
第一接收模块120，被配置为接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
该PDU会话建立装置可为UE，该UE可为PIN的PEGC和/或PEMC等PINE。
示例性地，该第一发送模块110和第一接收模块120可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。可以理解地，装置还包括：
确定模块，被配置为确定待建立的PDU会话是否与PIN业务关联；
第一发送模块110，被配置为当待建立的PDU会话与PIN业务关联时，向第一网络设备发送第一请求消息。
可以理解地，确定模块，可被配置为执行至少一项：
当接收到PIN内至少一个个人物联网单元PINE发送的PIN业务请求时，确定待建立的PDU会话与PIN业务关联；
当检测到与PIN业务关联的PDU会话建立指示时，确定待建立的PDU会话与PIN业务关联；
当待建立的PDU会话涉及的业务包含PIN业务时，确定待建立的PDU会话与PIN业务关联。
可以理解地，UE为个人物联网PIN网关PEGC。
如图9所示，本公开实施例提供一种协议数据单元PDU会话建立装置，其中，装置包括：
第二接收模块210，被配置为接收请求建立PDU会话的消息；
第一确定模块220，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
第二发送模块230，被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
该PDU会话建立装置可为MME、AMF、SMF、UDM、UDR和/或PCF等核心网设备。
示例性地，该第二接收模块、第一确定模块和第二发送模块可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。
可以理解地，第一确定模块，被配置为响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于所述PIN ID标识的PIN的签约数据允许建立PDU会话，建立基于所述PIN ID的PDU会话。
可以理解地，第一确定模块，被配置为响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于所述PIN ID标识的PIN的签约数据不允许建立PDU会话，拒绝基于所述PIN ID的PDU会话。
如图10所示，本公开实施例提供一种协议数据单元PDU会话建立装置，其中，装置包括：
第三接收模块310，被配置为第三发送模块，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接收或拒绝建立基于PIN ID的PDU会话；
第三发送模块320，被配置为接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
第三发送模块320，还被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
该PDU会话建立装置可为AMF或者MME等核心网设备。
示例性地，该第三接收模块310和第三发送模块320可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。
可以理解地，所述装置还包括：
第一选择模块，被配置为响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，选择支持PIN业务会话的所述SMF。
可以理解地，响应于所述第二响应消息包括PDU会话ID，所述第二响应消息还包括以下至少一项：
服务质量QoS流标识QFI；
QoS配置文件。
如图11所示，本公开实施例提供一种协议数据单元PDU会话建立装置，其中，装置包括：
第四接收模块410，被配置为第四接收模块，被配置为接收请求消息；
第二确定模块420，被配置为响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
第四发送模块430，被配置为发送第二响应消息，其中，所述第二响应消息，用于向接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
该PDU会话建立装置可为SMF
示例性地，该第四接收模块410、第二确定模块420和第四发送模块430可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。
可以理解地，第四发送模块410，还被配置为发送第三请求消息，其中，所述第三请求消息包括所述PIN ID，且第三请求消息用于请求所述PIN的签约数据；第四接收模块，还被配置为接收第三响应消息，其中，所述第三响应消息包括所述PIN的签约数据。
可以理解地，所述第四发送模块，还被配置为当允许基于所述PIN ID建立PDU会话时，PCF发送第四请求消息；其中，所述第四请求消息包括所述PIN ID，且所述第四请求消息用于请求策略信息；第四接收模块，还被配置为接收第四响应消息，其中，所述第四响应消息包括所述策略信息；所述策略信息，用于PDU会话的建立。
在一些实施例中，所述装置还包括：第二选择模块，被配置为响应于允许基于所述PIN ID建立PDU会话，根据所述PIN的签约数据选择核心网设备中的用户面功能UPF；其中，所述UPF，用于所述PDU会话的建立。
如图12所示，本公开实施例提供一种协议数据单元PDU会话建立装置，装置包括：
第五接收模块510，被配置为接收请求消息；
查询模块520，被配置为响应于所述第二网络设备发送的请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
第五发送模块530，还被配置为发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
该PDU会话建立装置可为UDM或UDR等核心网设备。
示例性地，该第五接收模块510、查询模块520和第五发送模块530可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。
在一些实施例中，所述装置还包括：
第二选择模块，被配置为响应于允许基于所述PIN ID建立PDU会话，根据所述PIN的签约数据选择核心网设备中的用户面功能UPF；其中，所述UPF，用于所述PDU会话的建立。
可以理解地，所述PIN的签约数据包括以下至少一项：
能力信息，指示所述PIN ID标识的PIN是否具有PDU会话能力，或所述UE是否具备PEGC和/或PEMC的能力；
时间信息，指示允许基于所述PIN ID建立PDU会话的时间范围，或，禁止基于所述PIN ID建立PDU会话的时间范围；
空间信息，指示允许基于所述PIN ID建立PDU会话的空间范围，或禁止基于所述PIN ID建立PDU会话的空间范围；
带宽信息，指示基于所述PIN ID建立的PDU会话允许使用的带宽范围。
如图13所示，本公开实施例提供一种协议数据单元PDU会话建立装置，所述装置包括：
第六接收模块610，被配置为接收请求消息；
获取模块620，被配置为响应于所述第二网络设备发送的请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
第六发送模块630，被配置为发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF基于所述PIN ID建立PDU会话。
该PDU会话建立装置可为PCF。
示例性地，该第六接收模块、获取模块和第六发送模块可为收发天线或者网络接口，也可以为能够执行上述操作的程序模块、可编程阵列或者专用集成电路等。
在一些实施例中，PIN的策略信息包括以下至少一项：
服务质量QoS流标识QFI；
QoS配置文件；
选择信息，用于供第二网络设备选择建立PDU会话的第五网络设备。
本公开实施例提供一种通信系统，其中，用于执行前述由UE执行以及由AMF或MME执行的PDU会话建立方法。
本公开实施例提供一种通信系统，其中，包括如下网元：
用于前述第三方面任意技术方案提供的PDU会话建立方法的接入管理功能AMF或者移动管理实体MME；
用于执行第四方面任意技术方案提供的PDU会话建立方法的会话管理功能SMF；
用于执行第五方面任意技术方案提供的PDU会话建立方法的用户数据管理UDM或者统一数据仓储UDR；
用于执行第六方面第技术方案提供的PDU会话建立方法的策略控制功能PCF。
本公开实施例提供一种通信设备，包括：
用于存储处理器可执行指令的存储器；
处理器，分别存储器连接；
其中，处理器被配置为执行前述任意技术方案提供的PDU会话方法。
处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
这里，通信设备包括：UE或者网络设备。该网络设备可为AMF、MME、SMF、PCF、UDM、UDR和/或PCF等网络设备。
处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图1B至图1E、2A至图2B、图3A至图3B、图4A至图4D、图5A至图5B、图6A至图6B至图7所示的方法的至少其中之一。
图14是根据一示例性实施例示出的一种UE 800的框图。例如，UE 800可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图14，UE 800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制UE 800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以生成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在UE 800的操作。这些数据的示例包括用于在UE 800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为UE 800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为UE 800生成、管理和分配电力相关联的组件。
多媒体组件808包括在UE 800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当UE 800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当UE 800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为UE 800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如组件为UE 800的显示器和小键盘，传感器组件814还可以检测UE 800或UE 800一个组件的位置改变，用户与UE 800接触的存在或不存在，UE 800方位或加速/减速和UE 800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于UE 800和其他设备之间有线或无线方式的通信。UE 800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，UE 800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由UE 800的处理器820执行以生成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
[根据细则26改正 13.04.2023]
如图15所示，本公开一实施例示出一种网络设备的结构。参照图15，网络设备900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在接入设备的任意方法，例如，如图1B至图1E、2A至图2B、图3A至图3B、图4A至图4D、图5A至图5B、图6A至图6B至图7所示的方法的至少其中之一。
网络设备900还可以包括一个电源组件926被配置为执行网络设备900的电源管理，一个有线或无线网络接口950被配置为将网络设备900连接到网络，和一个输入输出(I/O)接口958。网络设备900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
在不矛盾的情况下，某一实施方式或实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合，例如，在某一实施方式或实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施方式或实施例中各步骤的顺序可以任意交换，另外，某一实施方式或实施例中的可选方式或可选例可以任意组合；此外，各实施方式或实施例之间可以任意组合，例如，不同实施方式或实施例的部分或全部步骤可以任意组合，某一实施方式或实施例可以与其他实施方式或实施例的可选方式或可选例任意组合。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开实施例的其它实施方案。本公开旨在涵盖本公开实施例的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开实施例的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开实施例的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开实施例并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开实施例的范围仅由所附的权利要求来限制。

Claims (30)

  1. 一种协议数据单元PDU会话建立方法，其中，由用户设备UE执行，所述方法包括：
    发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
    接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    确定待建立的PDU会话是否与PIN业务关联；
    所述发送第一请求消息，包括：
    当待建立的PDU会话与所述PIN业务关联时，发送所述第一请求消息。
  3. 根据权利要求2所述的方法，其中，所述确定待建立的PDU会话是否与PIN业务关联，包括以下至少之一：
    当接收到所述PIN内至少一个个人物联网单元PINE发送的PIN业务请求时，确定待建立的PDU会话与所述PIN业务关联；
    当检测到与PIN业务关联的PDU会话建立指示时，确定待建立的PDU会话与所述PIN业务关联；
    当所述待建立的PDU会话涉及的业务包含所述PIN业务时，确定待建立的PDU会话与所述PIN业务关联。
  4. 根据权利要求1至3任一项所述的方法，其中，所述UE为个人物联网PIN网关PEGC和/或PIN管理单元PEMC。
  5. 一种协议数据单元PDU会话建立方法，由核心网设备执行，所述方法包括：
    接收请求建立PDU会话的消息；
    响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
    发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
  6. 根据权利要求5所述的方法，其中，所述响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话，包括：
    响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于所述PIN ID标识的PIN的签约数据允许建立PDU会话，建立基于所述PIN ID的PDU会话。
  7. 根据权利要求5所述的方法，其中，所述响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话，包括：
    响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，且基于 所述PIN ID标识的PIN的签约数据不允许建立PDU会话，拒绝基于所述PIN ID的PDU会话。
  8. 一种协议数据单元PDU会话建立方法，其中，由接入管理功能AMF或者移动管理实体MME执行，所述方法包括：
    响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接受或拒绝建立基于PIN ID的PDU会话；
    接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
    发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败。
  9. 根据权利要求8所述的方法，其中，所述响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，包括：
    响应于所述请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，选择支持PIN业务会话的所述SMF。
  10. 根据权利要求8或9所述的方法，其中，响应于所述第二响应消息包括PDU会话ID，所述第二响应消息还包括以下至少一项：
    服务质量QoS流标识QFI；
    QoS配置文件。
  11. 一种协议数据单元PDU会话建立方法，其中，由核心网设备中的会话管理功能SMF执行，所述方法包括：
    接收请求消息；
    响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
    发送第二响应消息，其中，所述第二响应消息，用于接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
  12. 根据权利要求11所述的方法，其中，所述响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立，包括：
    发送第三请求消息，其中，所述第三请求消息包括所述PIN ID，且第三请求消息用于请求所述PIN的签约数据；
    接收第三响应消息，其中，所述第三响应消息包括所述PIN的签约数据。
  13. 根据权利要求11或12所述的方法，其中，所述方法还包括：
    响应于允许基于所述PIN ID建立PDU会话，发送第四请求消息；其中，所述第四请求消息包括所述PIN ID，且所述第四请求消息用于请求策略信息；
    接收第四响应消息，其中，所述第四响应消息包括所述策略信息；所述策略信息，用于PDU会话的建立。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    响应于允许基于所述PIN ID建立PDU会话，根据所述PIN的签约数据选择核心网设备中的用户面功能UPF；其中，所述UPF，用于所述PDU会话的建立。
  15. 一种协议数据单元PDU会话建立方法，由UDM或UDR核心网设备中的用户数据管理UDM或者统一数据仓储UDR执行，其中，所述方法包括：
    接收请求消息；
    响应于所述请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
    发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于供会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
  16. 根据权利要求15所述的方法，其中，所述PIN的签约数据包括以下至少一项：
    能力信息，指示所述PIN ID标识的PIN是否具有PDU会话能力，或所述UE是否具备PEGC和/或PEMC的能力；
    时间信息，指示允许基于所述PIN ID建立PDU会话的时间范围，或，禁止基于所述PIN ID建立PDU会话的时间范围；
    空间信息，指示允许基于所述PIN ID建立PDU会话的空间范围，或禁止基于所述PIN ID建立PDU会话的空间范围；
    带宽信息，指示基于所述PIN ID建立的PDU会话允许使用的带宽范围。
  17. 一种协议数据单元PDU会话建立方法，由PCF核心网设备中的策略控制功能PCF执行，所述方法包括：
    接收请求消息；
    响应于所述请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
    发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF发起基于所述PIN ID的PDU会话的建立。
  18. 根据权利要求17所述的方法，其中，所述PIN的策略信息包括以下至少一项：
    服务质量QoS流标识QFI；
    QoS配置文件；
    选择信息，用于供所述第二网络设备选择建立所述PDU会话的第五网络设备。
  19. 一种协议数据单元PDU会话建立装置，其中，所述装置包括：
    第一发送模块，被配置为发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于向核心网设备请求建立PDU会话；
    第一接收模块，被配置为接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功。
  20. 一种协议数据单元PDU会话建立装置，其中，所述装置包括：
    第二接收模块，被配置为接收请求建立PDU会话的消息；
    第一确定模块，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息，确定接受或拒绝基于所述PIN ID的PDU会话；
    第二发送模块，被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
  21. 一种协议数据单元PDU会话建立装置，其中，所述装置包括：
    第三发送模块，被配置为响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于会话管理功能SMF确定接收或拒绝建立基于PIN ID的PDU会话；
    第三接收模块，被配置为接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；
    所述第三发送模块，被配置为发送第一响应消息，其中，所述第一响应消息，用于向用户设备UE指示基于所述PIN ID的PDU会话建立成功或建立失败。
  22. 一种协议数据单元PDU会话建立装置，其中，所述装置包括：
    第四接收模块，被配置为接收请求消息；
    第二确定模块，被配置为响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；
    第四发送模块，被配置为发送第二响应消息，其中，所述第二响应消息，用于向接入管理功能AMF或者移动管理实体MME指示接收或拒绝建立基于PIN ID的PDU会话。
  23. 一种协议数据单元PDU会话建立装置，所述装置包括：
    第五接收模块，被配置为接收请求消息；
    查询模块，被配置为响应于所述第二网络设备发送的请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；
    第五发送模块，被配置为发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于会话管理功能SMF确定接受或拒绝建立基于所述PIN ID的PDU会话。
  24. 一种协议数据单元PDU会话建立装置，所述装置包括：
    第六接收模块，被配置为接收请求消息；
    获取模块，被配置为响应于所述第二网络设备发送的请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；
    第六发送模块，被配置为发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于会话管理功能SMF基于所述PIN ID建立PDU会话。
  25. 一种PDU会话建立方法，其中，包括：用户设备UE、接入管理功能AMF或者移动管理实 体MME以及会话管理功能SMF；所述UE发送第一请求消息，其中，所述第一请求消息包括：个人物联网PIN标识ID，且所述第一请求消息用于请求建立PDU会话；
    所述UE接收第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话是否建立成功；
    所述AMF或者MME响应于请求建立PDU会话的消息为包括个人物联网PIN标识ID的第一请求消息时，发送第二请求消息，其中，所述第二请求消息包括：所述PIN ID；且所述第二请求消息，用于所述SMF确定是否建立基于PIN ID的PDU会话；接收第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话；发送第一响应消息，其中，所述第一响应消息，用于指示基于所述PIN ID的PDU会话建立成功或建立失败；
    所述SMF接收请求消息；响应于接收的请求消息为包括个人物联网PIN标识ID的第二请求消息，根据所述PIN ID和所述PIN的签约数据，确定接受或拒绝所述PDU会话的建立；发送第二响应消息，其中，所述第二响应消息，用于指示接收或拒绝建立基于PIN ID的PDU会话。
  26. 根据权利要求25所述的方法，其中，所述方法还包括：
    核心网设备中的用户数据管理UDM或者统一数据仓储UDR接收请求消息；响应于所述请求消息为包括个人物联网PIN标识ID的第三请求消息，查询所述PIN的签约数据；发送第三响应消息，其中，所述第三响应消息，包括所述PIN的签约数据；其中，所述PIN的签约数据，至少用于确定接受或拒绝建立基于所述PIN ID的PDU会话；
    和/或，
    策略控制功能PCF接收请求消息；响应于所述第二网络设备发送的请求消息是包括个人物联网PIN标识ID的第四请求消息，获取所述PIN的策略信息；发送第四响应消息，其中，所述第四响应消息包括所述PIN的策略信息，其中，所述PIN的策略信息，用于所基于所述PIN ID建立PDU会话。
  27. 一种通信系统，其中，用于执行权利要求1至7任一项所述的方法。
  28. 一种通信系统，其中，包括如下网元：
    用于执行权利要求8至10任一项的接入管理功能AMF或者移动管理实体MME；
    用于执行权利要求11至14任一项的会话管理功能SMF；
    用于执行权利要求15至16任一项的用户数据管理UDM或者统一数据仓储UDR；
    用于执行权利要求17至18任一项的策略控制功能PCF。
  29. 一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至4、5至7、8至10、11至14、、15至16，或者17至18任一项提供的方法。
  30. 一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如权利要求1至4、5至7、8至10、11至14、15至16，或者17至18任一项提供的方法。
PCT/CN2023/075083 2023-02-08 2023-02-08 Pdu会话方法及装置、通信设备及存储介质 WO2024164203A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380008177.3A CN116349383A (zh) 2023-02-08 2023-02-08 Pdu会话方法及装置、通信设备及存储介质
PCT/CN2023/075083 WO2024164203A1 (zh) 2023-02-08 2023-02-08 Pdu会话方法及装置、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/075083 WO2024164203A1 (zh) 2023-02-08 2023-02-08 Pdu会话方法及装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024164203A1 true WO2024164203A1 (zh) 2024-08-15

Family

ID=86877454

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/075083 WO2024164203A1 (zh) 2023-02-08 2023-02-08 Pdu会话方法及装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN116349383A (zh)
WO (1) WO2024164203A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113572801A (zh) * 2020-09-30 2021-10-29 中兴通讯股份有限公司 会话建立方法、装置、接入网设备及存储介质
CN113993143A (zh) * 2018-05-22 2022-01-28 华为技术有限公司 会话管理方法、装置和系统
CN114946266A (zh) * 2019-12-10 2022-08-26 高通股份有限公司 用于冗余pdu会话的基于ue的对id
US20220312305A1 (en) * 2021-03-29 2022-09-29 Samsung Electronics Co., Ltd. Method and apparatus for session management in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113993143A (zh) * 2018-05-22 2022-01-28 华为技术有限公司 会话管理方法、装置和系统
CN114946266A (zh) * 2019-12-10 2022-08-26 高通股份有限公司 用于冗余pdu会话的基于ue的对id
CN113572801A (zh) * 2020-09-30 2021-10-29 中兴通讯股份有限公司 会话建立方法、装置、接入网设备及存储介质
US20220312305A1 (en) * 2021-03-29 2022-09-29 Samsung Electronics Co., Ltd. Method and apparatus for session management in wireless communication system

Also Published As

Publication number Publication date
CN116349383A (zh) 2023-06-27

Similar Documents

Publication Publication Date Title
WO2023184195A1 (zh) 支持增强现实业务能力协商方法及装置、网元、ue及存储介质
WO2024164203A1 (zh) Pdu会话方法及装置、通信设备及存储介质
US20230224769A1 (en) Method and apparatus for controlling data transmission rate communication device, and storage medium
WO2024145948A1 (zh) 授权方法、装置、通信设备及存储介质
WO2024164340A1 (zh) Qos监控结果的订阅方法、装置、通信设备及存储介质
WO2024031399A1 (zh) Ue加入pin的方法及装置、通信设备及存储介质
WO2024036495A1 (zh) 信息处理方法及装置、通信设备及存储介质
EP4422150A1 (en) Dns configuration processing method and apparatus, and communication device and storage medium
WO2024130563A1 (zh) QoS管理方法以及装置、通信设备及存储介质
WO2023184183A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2023184194A1 (zh) 基于增强现实业务的会话管理功能选择方法及装置、存储介质
WO2023216117A1 (zh) 一种中继通信方法、装置、设备及存储介质
CN111096046B (zh) 接入方式确定方法、装置及通信设备
WO2023231018A1 (zh) 个人物联网pin基元凭证配置方法、装置、通信设备及存储介质
WO2024000439A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024092801A1 (zh) 认证方法、装置、通信设备及存储介质
WO2024060894A1 (zh) 一种通信方法及装置
WO2023245448A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2023000323A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2023178703A1 (zh) 个人物联网网络建立方法及装置、网元、ue及存储介质
WO2024092467A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2023184172A1 (zh) 创建pin的方法、装置、通信设备及存储介质
WO2024164345A1 (zh) 信息处理方法、系统及装置、通信设备及存储介质
WO2024148498A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2023070509A1 (zh) 信息处理方法及装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23920411

Country of ref document: EP

Kind code of ref document: A1