WO2022033521A1 - 会话更新方法、终端和网络侧设备 - Google Patents

会话更新方法、终端和网络侧设备 Download PDF

Info

Publication number
WO2022033521A1
WO2022033521A1 PCT/CN2021/112074 CN2021112074W WO2022033521A1 WO 2022033521 A1 WO2022033521 A1 WO 2022033521A1 CN 2021112074 W CN2021112074 W CN 2021112074W WO 2022033521 A1 WO2022033521 A1 WO 2022033521A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
terminal
slice identifier
pdu session
message
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/112074
Other languages
English (en)
French (fr)
Inventor
陈旭
黄震宁
张翀
宋月
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
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 China Mobile Communications Group Co Ltd, Research Institute of China Mobile Communication Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to EP21855572.0A priority Critical patent/EP4192077B1/en
Priority to JP2023510478A priority patent/JP7641359B2/ja
Priority to US18/041,405 priority patent/US20230300912A1/en
Publication of WO2022033521A1 publication Critical patent/WO2022033521A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a session update method, a terminal, and a network side device.
  • URSP UE Route Selection Policy
  • the network side After the vertical industry user activates the slicing service, the network side generates a UE Route Selection Policy (URSP), and sends it to the UE after the user terminal (User Equipment, UE) registers with the network.
  • UE User Equipment
  • the UE saves the URSP
  • the specified slice is selected according to the URSP, and the 5G network slicing technology ensures the service quality.
  • the network side provides the end-to-end slicing service function, and the URSP delivery process and matching rules have been defined, when the UE side implements the URSP matching application, it is difficult to follow the route/slice selection strategy delivered by the network side as: The application-related business flow matches the corresponding slice.
  • Embodiments of the present disclosure provide a session update method, a terminal, and a network-side device, so as to solve the problem that it is difficult for the UE to select a slice according to the URSP when a session is established.
  • an embodiment of the present disclosure provides a session update method for a terminal, where the session update method includes:
  • Protocol Data Unit Protocol Data Unit
  • receive an indication message sent by a network side device where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform an update on the PDU according to the slice identifier
  • the session is modified, re-established, or a PDU session establishment process is initiated.
  • an embodiment of the present disclosure provides a session update method for a network-side device, where the session update method includes:
  • the terminal After the terminal establishes a PDU session, it sends an indication message to the terminal; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify, rebuild, or initiate a PDU session according to the slice identifier. Build a process.
  • an embodiment of the present disclosure provides a session update method for a Policy Control Function (PCF), where the session update method includes:
  • the slice identifier is sent.
  • an embodiment of the present disclosure provides a terminal, where the terminal includes: a processor and a transceiver;
  • the transceiver is configured to receive an indication message sent by a network side device after establishing a PDU session, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform the PDU session based on the slice identifier. Modify, rebuild, or initiate a PDU session establishment process.
  • an embodiment of the present disclosure provides a network-side device, where the network-side device includes: a processor and a transceiver;
  • the transceiver is configured to send an indication message to the terminal after the terminal establishes a PDU session; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify the PDU session according to the slice identifier , reestablish, or initiate a PDU session establishment procedure.
  • embodiments of the present disclosure provide a PCF, where the PCF includes: a processor and a transceiver;
  • the processor for querying the routing policy
  • the processor is further configured to determine a slice identifier according to the routing policy
  • the transceiver is configured to send the slice identifier.
  • an embodiment of the present disclosure provides a terminal, where the terminal includes:
  • a receiving module configured to receive an indication message sent by a network side device after establishing a PDU session, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify the PDU session according to the slice identifier, Rebuild, or initiate a PDU session establishment process.
  • an embodiment of the present disclosure provides a network-side device, where the network-side device includes:
  • a sending module configured to send an indication message to the terminal after the terminal establishes a PDU session; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify and rebuild the PDU session according to the slice identifier , or initiate a PDU session establishment process.
  • an embodiment of the present disclosure provides a PCF, where the PCF includes:
  • the query module is used to query the routing strategy
  • a determining module further configured to determine a slice identifier according to the routing strategy
  • a sending module configured to send the slice identifier.
  • an embodiment of the present disclosure provides a terminal, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program is implemented when executed by the processor The steps in the session update method according to the first aspect.
  • an embodiment of the present disclosure provides a network-side device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor When executed, the steps in the session update method described in the second aspect are implemented.
  • embodiments of the present disclosure provide a PCF, including a processor, a memory, and a computer program stored on the memory and executable on the processor, when the computer program is executed by the processor Steps in the session update method as described in the third aspect are implemented.
  • an embodiment of the present disclosure provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the session update according to the first aspect is implemented
  • the terminal after establishing a PDU session, receives an indication message sent by a network-side device, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform an update on the PDU session according to the slice identifier. Modify, modify, or initiate a PDU session establishment process. In this way, the terminal only needs to modify, rebuild or establish the PDU session according to the slice identifier indicated by the network side device, and then the PDU session can be switched to the specified slice, which avoids the difficulty for the UE to select the slice according to the URSP when the session is established. question.
  • FIG. 1 is a structural diagram of a network system to which an embodiment of the present disclosure can be applied;
  • FIG. 2 is a flowchart of a first session update method provided by an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a second session update method provided by an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of a third session update method provided by an embodiment of the present disclosure.
  • Embodiment 1 of a session update method provided by an embodiment of the present disclosure
  • Embodiment 6 is a flowchart of Embodiment 2 of a session update method provided by an embodiment of the present disclosure
  • FIG. 8 is a structural diagram of a terminal provided by an embodiment of the present disclosure.
  • FIG. 9 is a structural diagram of a network side device provided by an embodiment of the present disclosure.
  • FIG. 10 is a structural diagram of a PCF provided by an embodiment of the present disclosure.
  • FIG. 11 is a structural diagram of another entity provided by an embodiment of the present disclosure.
  • the session update method provided by this embodiment of the present disclosure can be applied to the slicing network system shown in FIG. 1 , where the system includes a terminal 11 and a slicing network (as shown in FIG. 1 : a first slicing network 12 , a second slicing network network 13 and a third slice network 14).
  • Different slice networks can correspond to different radio access networks 121 (Radio Access Network, RAN), transport network 122 (Transport Network, TN) and core network 123 (Core Network, CN), so as to provide users with different slice networks respectively.
  • Provide different service functions that is, provide dedicated, differentiated and quality-assured private network services for vertical industry users, such as: online cloud games serving the 5th Generation (5th Generation, 5G) communication system network (public network) services, and application scenarios such as serving 5G private network customers.
  • 5G 5th Generation
  • public network public network
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (vehicle user equipment, VUE), pedestrian terminal (pedestrian user equipment, PUE) and other terminal-side devices, wearable devices include: bracelets, earphones, glasses, etc., the embodiment of the present disclosure does not limit the specific type of the terminal 11.
  • the mapping between slices and application services is implemented through a pre-defined URSP policy, and the URSP is delivered to the UE after the UE registers with the network.
  • the UE uses the application service, it finds the specified slice information according to the URSP policy, and tells the network which slice to select when the session is established.
  • the 5G network After vertical industry users order and activate slices, the 5G network will generate a URSP and deliver it to the UE after the UE registers with the network. The UE saves the URSP.
  • the specified slice is selected according to the URSP, and the 5G network slicing technology ensures the service quality.
  • the business descriptor (Application Identity, APP ID) in URSP is currently difficult to define in the 3rd Generation Partnership Project (3GPP) standardized protocol.
  • the APP ID is related to the application management environment and may require the first Three-party application providers, terminal manufacturers, and operators negotiate, that is, the standard progress limits the development of terminal slicing functions.
  • Difficulty 2 The terminal uses other service matching conditions defined by URSP, such as IP triples, which also have practical application limitations.
  • IP triples which also have practical application limitations.
  • the IP address of the application server may change due to the disaster recovery plan or resource adjustment, and it is difficult to establish a session according to the slice and DNN selection policies delivered by the network side.
  • Difficulty 3 If the terminal is customized, and the routing/slice selection strategy is built into the terminal to realize the binding of service flow and slice, it will limit the application scenario, resulting in the inflexibility of the slice function, or the problem that it cannot adapt to the application scenario, such as : In game slicing services, since there are many types of terminal choices for users, it is impossible to customize each terminal selection; for another example, vertical industry customers require multiple slices and industry terminals support multiple slices. In the multi-slice scenario, there are still Slices and applications cannot be mapped.
  • the network side informs the terminal of the slice that the network provides for the application, so as to solve the above-mentioned problem.
  • FIG. 2 is a flowchart of a session update method provided by an embodiment of the present disclosure, which is used for a terminal. As shown in FIG. 2, the session update method may include the following steps:
  • Step 201 After establishing a PDU session, receive an indication message sent by a network side device, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify and rebuild the PDU session according to the slice identifier, Or initiate a PDU session establishment process.
  • the "PDU session” is a session established on a slice (or also called a slice network), and the session is used to obtain services from the service platform.
  • the above-mentioned slice identifier may be single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), that is, indicating that the terminal needs to update the PDU session to the target slice corresponding to the S-NSSAI.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the indication message may also include other information, for example: one or more items of session type/DNN/Internet Protocol (Internet Protocol, IP) address, etc.
  • the indication information may also instruct the terminal to update the session Session type/DNN/IP address, etc.
  • the indication message also includes the data network name DNN.
  • the terminal updates the PDU session to the PDU session associated with the S-NSSAI and the DNN according to the indication message.
  • the above-mentioned “update” may include session modification, session re-establishment, or initiation of a PDU session establishment process, and the like.
  • the reestablishment of the session may be implemented by multiplexing the session release command message in the related art.
  • a cause value may be carried in the session release command message to instruct the terminal to release the session, and rebuild the PDU session according to the slice identifier, and make the reconstructed PDU session correlate with the slice identifier.
  • the so-called correlation/association between the PDU session and the slice identifier can be understood as the PDU session being carried by the slice or slice network indicated by the slice identifier.
  • the indication message may not include other information (for example: session type/DNN/IP), then the terminal only updates the S-NSSAI when reestablishing the PDU session, but does not update the session type/DNN/IP address and other session information.
  • other information for example: session type/DNN/IP
  • the above-mentioned instruction message may also include the application access address, the processing method (reservation or release) of the original PDU session, etc., to instruct the terminal to modify the PDU session, rebuild the PDU session, or initiate the PDU session establishment process.
  • the network side device instructs the terminal to modify, rebuild or create a PDU session, so that the network side can control the UE to provide services to users through appropriate slices, and solves the problem that it is difficult for the terminal to follow the routing/slice selection strategy issued by the network side.
  • the established PDU session may be a session established on any slice network corresponding or not corresponding to the specified application/application server.
  • the user plane and application detection mechanism can identify the service flow that needs to be selected to the specified slice, and detect whether the PDU session established by the terminal matches the service flow that needs to be selected to the specified slice. And the entity performing the service flow detection notifies the network entity of the detection result.
  • the network side can instruct the network to provide a slice (for example, S-NSSAI) for the application, thereby triggering the terminal to modify the PDU session according to the slice identifier and rebuild the PDU session, or initiate a PDU session establishment procedure, so that the terminal switches to the slice corresponding to the specified application.
  • a slice for example, S-NSSAI
  • the above-mentioned network-side device may be a session management function entity (Session Management Function, SMF) or a network platform that performs session management on the PDU session.
  • SMF Session Management Function
  • the indication message includes at least one of the following messages:
  • the session modification command message sent by the SMF is used to instruct the terminal to modify the slice identifier related to the PDU session as the slice identifier included in the session modification command message;
  • session release command message sent by the SMF, where the session release command message is used to instruct the terminal to release a session, and rebuild the session according to the slice identifier;
  • An application trigger message sent by the network platform where the application trigger message is used to instruct the terminal to access an application server through a PDU session related to the slice identifier.
  • the instruction message is: a session modification command message sent by an SMF that performs session management on the PDU session, and the session modification command message is used to instruct the terminal to modify the PDU session-related
  • the slice identifier is the slice identifier included in the session modification command message to update the PDU session.
  • modifying the PDU session may be understood as modifying a session attribute in the PDU session.
  • the terminal modifies the session attribute of the PDU session based on the session modification command message sent by the SMF, so as to modify the slice identifier related to the PDU session to the slice identifier contained in the session modification command message, thereby realizing the The PDU session is associated with the target slice.
  • the instruction message is: a session release command message sent by the SMF that performs session management on the PDU session, the session release command message is used to instruct the terminal to release the session, and according to the Slice identification reconstructs the session.
  • the terminal releases the PDU session and rebuilds the session associated with the slice identifier based on the session release command message sent by the SMF.
  • the session release command message may carry a cause value, where the cause value is used to instruct the terminal to re-establish the PDU session, and the re-established PDU session is related to the slice identifier.
  • the terminal can also re-establish the PDU session, specifically, establishing the PDU session on the slice corresponding to the slice identifier sent by the network side, so as to associate the PDU session with the target slice.
  • the terminal after the terminal reestablishes the PDU session, it can send the service flow of the current PDU session to the user plane channel of the reestablished PDU session.
  • the indication message is an application trigger message sent by the network platform, where the application trigger message is used to instruct the terminal to access the application server through the PDU session related to the slice identifier.
  • a session creation command message sent by the SMF that performs session management on the PDU session may also be used, and the session release command message is used to instruct the terminal to create the session according to the slice identifier.
  • the SMF sends the indication message
  • the network platform sends the indication message
  • the terminal receives the indication message
  • the terminal can directly use the PDU session related to the slice identifier to access the application server.
  • the terminal does not establish a PDU session related to the slice identifier, it establishes a PDU session related to the slice identifier for accessing the application server, thereby realizing associating the PDU session with the target slice.
  • the indication message when the indication message is an application trigger message, it further includes:
  • the session related to the slice identifier In the case that the session related to the slice identifier is not established, initiate a PDU session establishment process, and establish a PDU session related to the slice identifier for accessing the application server;
  • the application server is accessed using the PDU session associated with the slice identification, if the session associated with the slice identification has been established.
  • a PDU session corresponding to the slice identifier when the PDU session corresponding to the slice identifier is not established, if it is necessary to access the application server based on the slice identifier, a PDU session corresponding to the slice identifier needs to be established, so as to initiate a PDU session establishment process to establish For accessing the application server, the PDU session associated with the slice identifier.
  • the terminal can directly use the PDU session related to the slice identifier to access the application server without re-establishing the PDU session.
  • the network side instructs the terminal to access the application through the target slice corresponding to the slice identifier by carrying the slice identifier in the instruction message sent to the terminal.
  • the terminal needs to match the URSP according to the service descriptor, and find the identifier of the slice that the network provides services for the application.
  • the UE carries the session information (or session parameters) and the identifier of the slice to establish the PDU session. In this way, after the PDU session is established successfully, the PDU session established by the UE uses the resources of this slice, and the slice provides quality assurance.
  • the UE directly establishes the PDU session, and then associates the PDU session with the correct slice according to the network side instruction.
  • the determination of the correct slice is decided by the network side, which avoids the problem in the related art that it is difficult for the terminal to match the corresponding slice for the application-related service flow according to the routing/slice selection policy issued by the network side.
  • the terminal specifically modifies, rebuilds, or initiates the PDU session, which can be determined by judging the support capability of the SMF corresponding to the PDU session before the handover to the target slice, which can include the following three situations:
  • the network side device is an SMF, and when the SMF supports the target slice corresponding to the slice identifier, the indication message is the session modification command message or the session release command message.
  • the PDU session is modified or rebuilt, so that the terminal updates the session to the slice corresponding to the slice identifier supported by the SMF.
  • the network-side device is an SMF, and the PDU session may be re-established if the SMF does not support the target slice corresponding to the slice identifier.
  • the original PDU session can be released and a PDU session corresponding to the slice identifier can be established, so that the terminal can update the session to a newly established PDU session.
  • the network side device is a network platform capable of sending a notification message to the terminal, and the network platform can send an application trigger message to the terminal, where the application trigger message is used to instruct the terminal to access the application server through the PDU session related to the slice identifier. Then, when the PDU session related to the slice identifier is not established, the terminal will create a new PDU session related to the slice identifier, and locate the application server through the newly created PDU session.
  • a new PDU session corresponding to the slice identifier is created on the basis of retaining the original PDU session.
  • the terminal after establishing a PDU session, receives an indication message sent by a network-side device, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform an update on the PDU session according to the slice identifier. Modify, modify, or initiate a PDU session establishment process. In this way, the terminal only needs to modify, rebuild or establish the PDU session according to the slice identifier indicated by the network side device, and then the PDU session can be switched to the specified slice, which avoids the difficulty for the UE to select the slice according to the URSP when the session is established. question.
  • FIG. 3 is a flowchart of a second session update method provided by an embodiment of the present disclosure.
  • the session update method is applied to a network side device.
  • the session update method may include the following steps:
  • Step 301 After the terminal establishes a PDU session, an indication message is sent to the terminal; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify and rebuild the PDU session according to the slice identifier, or Initiate the PDU session establishment process.
  • the above indication message has the same meaning as the indication message in the method embodiment shown in FIG. 2 , and details are not repeated here.
  • the indication message further includes the data network name DNN.
  • the network side device is a network platform or an SMF that performs session management on the PDU session.
  • the indication message includes at least one of the following messages:
  • the session modification command message is used to instruct the terminal to modify the slice identifier related to the PDU session as the slice identifier included in the session modification command message;
  • session release command message sent by the SMF, where the session release command message is used to instruct the terminal to release a session, and rebuild the session according to the slice identifier;
  • An application trigger message sent by the network platform where the application trigger message is used to instruct the terminal to access an application server through a PDU session related to the slice identifier.
  • the above session modification command message is used to instruct the terminal to modify the slice network of the PDU session, so that the terminal can access the application platform on the modified slice network.
  • the above session release command message is used to instruct the terminal to release the current PDU session and rebuild a session related to the slice identifier.
  • the session release command message sent by the SMF to the terminal may carry a cause value, where the cause value is used to instruct the terminal to re-establish the PDU session, and the re-established PDU session is related to the slice identifier .
  • the terminal can access the application platform through the rebuilt PDU session.
  • the above application trigger message is used to instruct the terminal to access the application server through the PDU session related to the slice identifier.
  • the SMF sends a session release command message to the terminal, in this embodiment, when the terminal receives the application trigger message, it determines whether its current PDU session is related to the slice identifier, and if so, The application platform can be accessed through the PDU session; if it is irrelevant, a PDU session related to the slice identifier can be newly created, and the application platform can be accessed through the newly created PDU session, and the original PDU session can be retained.
  • the network side device is the SMF, and when the SMF does not support the slice identifier, the indication message is the session release command message;
  • the network-side device is the SMF, and when the SMF supports the slice identifier, the indication message is the session modification command message or the session release command message.
  • the terminal may be instructed to re-establish a session on another SMF that newly supports the slice identifier, so as to access the application server through the session. At this point, the session on the original SMF can be released to save network resources.
  • the session can be updated to the slice identifier through a session modification command message, or a session can be re-established on the same SMF through a session release command message, to access the application server through this session.
  • the network-side device is the SMF, and before sending the indication message to the terminal, the method further includes:
  • a first session control message sent by the PCF is received, where the first session control message carries the slice identifier determined according to the routing policy. (In other words, that is: receiving the first session control message sent by the PCF after determining that the PDU session needs to be associated with the slice selection auxiliary information, the first session control message carries the slice that the PDU session needs to be associated with logo.)
  • the PCF can acquire: application-related information and/or user-related information (such as application information, session information, and UE information), etc., so as to determine the slice that the PDU session needs to be associated with by querying the routing policy according to the information. logo.
  • application-related information and/or user-related information such as application information, session information, and UE information
  • the first session control message may also carry application-related information and/or user-related information, so that the SMF determines whether to modify, rebuild, or create a PDU session based on the information and the slice identifier.
  • the network-side device is the SMF, and before sending the indication message to the terminal, the method further includes:
  • the first service request may carry a query parameter
  • the query parameter may include at least one of application-related information and user-related information, and may also include session information established by the terminal and the like.
  • the first service request sent by the NEF or AF is received, and the first service request carries application-related information (for example, an application-related address, which may also be referred to as “application information”) or user-related information (which may also be referred to as “application information”).
  • application information for example, an application-related address, which may also be referred to as "application information”
  • UE information user-related information
  • the SMF requests the PCF to request the acquisition of the slice identifier that needs to be associated with the PDU session, thereby sending a first request message to the PCF.
  • the terminal After detecting that the terminal has accessed the application according to the first service request, send a first request message to the PCF, where the first request message is used to instruct the PCF to query the routing policy, and the first request message may carry the above Application information and UE information.
  • the above-mentioned application-related information may include: the address of the application and/or the identifier of the application; the user-related information may include: the address of the user and/or the identifier of the user.
  • the session parameter may include at least one of the following parameters: the application information corresponding to the PDU session, the server information corresponding to the PDU session and terminal identification information corresponding to the PDU session.
  • the PCF After receiving the request message, the PCF performs a routing policy query to determine the slice identifier that needs to be associated with the PDU session, and carries the slice identifier obtained by the query in a response message to send to the SMF.
  • the response message may also include a data network name.
  • the SMF can be made to instruct the terminal to associate the PDU session associated with the slice identifier with the data network name according to the response message.
  • the response message is a second session control message.
  • the SMF may determine to modify, rebuild or create a PDU session according to the first session control message or the second session control message.
  • the SMF can actively trigger the modification, reconstruction or new creation of the PDU session based on the first service request sent by the NEF or the AF, and actively search for the slice identifier from the PCF.
  • the network-side device is a network platform, and before sending the instruction message to the terminal, it further includes:
  • a service message (the service message may also be referred to as a "service notification message") sent by the AF or NEF, where the service message carries a slice identifier that needs to be associated with a PDU session accessing the application server.
  • the receiving a service message sent by the AF or the NEF, where the service message carries a slice identifier that needs to be associated with a PDU session accessing the application server may be: after the UE establishes the PDU session, when the UE accesses the application server through the PDU session , the NEF or the AF triggers the PCF to perform a routing policy query based on the action, so as to determine the slice identifier that needs to be associated with the PDU session accessing the application server, and send it to the UE.
  • the NEF or the AF may be: after the UE establishes the PDU session, when the UE accesses the application server through the PDU session , the NEF or the AF triggers the PCF to perform a routing policy query based on the action, so as to determine the slice identifier that needs to be associated with the PDU session accessing the application server, and send it to the UE.
  • the service message also includes the DNN.
  • the AF initiates the PDU session creation process, and in the process of the AF initiating the PDU session creation process, the network platform (for example, SMSC) sends an instruction to create a PDU session based on session information to the UE, and the UE checks by itself Whether a PDU session based on the session information already exists, if so, no need to create a new PDU session, if not, create a new PDU session based on the session information.
  • the network platform for example, SMSC
  • FIG. 4 is a flowchart of a third session update method provided by an embodiment of the present disclosure.
  • the session update method is applied to PCF.
  • the session update method may include the following steps:
  • Step 401 query the routing policy.
  • Step 402 Determine the slice identifier according to the routing policy.
  • Step 403 Send the slice identifier.
  • the slice identifier is used by the terminal to modify and rebuild the established PDU session, or initiate a PDU session establishment procedure.
  • the PCF can determine the slice identifier corresponding to the service platform corresponding to the PDU session based on query parameters (application-related information and/or user-related information) and routing policy corresponding to the PDU session established by the terminal.
  • the session update method further includes:
  • the data network name DNN is also sent.
  • the PCF may send the DNN to the network-side device, so that the network-side device instructs the terminal to update the DNN associated with the PDU session.
  • the method before the querying of the routing selection policy, the method further includes:
  • the sending of the slice identifier is specifically:
  • the slice identifier determined according to the routing policy is sent to the NEF or the AF.
  • the SMF can actively request the PC to send a service request based on at least one of the application-related information and the user-related information by sending a first request message to the PCF when receiving the first service request sent by the AF or the NEF.
  • the routing policy is queried, and the slice identifier obtained by using the routing policy obtained by the query is sent to at least one of the SMF, the AF or the NEF.
  • the SMF may instruct the terminal to perform session modification or session reconstruction based on its slice support capability.
  • the AF or NEF can notify the terminal of the slice identifier through a network platform capable of sending a notification message to the terminal, so as to instruct the terminal to access the application through the session related to the slice identifier. And when the terminal does not establish a session related to the slice identifier, the terminal is made to initiate a session establishment process, so as to establish a session related to the slice identifier, and then access the application through the session.
  • the PCF can receive the request message sent by the AF or the NEF, to actively query the routing policy according to the application-related information and/or user-related information carried in the request message, and use the routing policy to query
  • the resulting slice identification is sent to at least one of SMF, AF or NEF.
  • the slice identifier is used to obtain the SMF for session management of the PDU session, or actively send it to the SMF, and the SMF instructs the terminal to modify the session, rebuild the session, or initiate a session such as a session establishment process. update operation.
  • the slice identifier is sent to the terminal via a network platform capable of sending notification messages to the terminal, so as to inform the terminal to access the application server through the slice identifier, so that the terminal can determine whether to create a new PDU session based on the slice identifier.
  • the slice identifier may be determined by the PCF according to the routing policy in the local or UDR.
  • the application-related information and/or user-related information is sent by the AF or the NEF, and the slice identifier is sent to the SMF that performs session management on the PDU session.
  • This embodiment may correspond to an embodiment in which the network device is an SMF, and the PCF actively performs a routing policy query, for example, steps 3 and 4 in the embodiment shown in FIG. 5 .
  • the application-related information and/or user-related information is sent by the SMF that performs session management on the PDU session, and the slice identifier is sent to the SMF.
  • This embodiment may correspond to an embodiment in which the network device is an SMF, and the SMF actively triggers the PCF to query the routing policy, for example, steps 4 and 5 in the embodiment shown in FIG. 6 , which are not repeated here.
  • the application-related information and/or user-related information is sent by the AF or NEF, and the slice identification is sent to the AF or NEF.
  • This embodiment can correspond to an embodiment in which the network device is a network platform, and the PCF is actively triggered by the AF or NEF to query the routing policy. For example, step 3, step 4 and step 5 in the embodiment shown in FIG. This will not be repeated here.
  • the PCF determines the slice identifier that needs to be associated with the PDU session established by the terminal based on the application-related information and/or the user-related information (query parameter), so that the network side device instructs the terminal to update the session according to the slice identifier. Similarly , which can avoid the problem that it is difficult for the terminal to select a specified slice to establish a session when establishing a PDU session.
  • the session update method is described below with an example in conjunction with the data interaction process between the terminal and the network side device:
  • the network side device is an SMF that performs session management on the PDU session, and the SMF can receive the indication message sent by the PCF, then the process of updating the session may be as shown in Figure 5, and the updating session may include the following processes:
  • Step 1 The UE initiates session establishment, and chooses to establish session A on slice A.
  • the slice A may be any slice network, and the terminal may select the slice A by randomly selecting or fixedly selecting the same slice network for different sessions.
  • Step 2 The UE accesses the application platform from the user plane of session A, that is, the application function (Application Function, AF) entity.
  • the application function Application Function, AF
  • Step 3 The NEF or the AF sends the first service request to the PCF.
  • the AF detects that the UE uses the application service, it sends the first service request to the PCF through the Network Exposure Function (NEF), so that the NEF can inform the PCF that the UE accesses the application platform and informs the UE information (for example: UE's IP address) and application information (for example: application address, application ID).
  • NEF Network Exposure Function
  • the AF may also directly notify the PCF, which is not specifically limited here.
  • Step 4 The PCF sends the first session control message to the original SMF.
  • the PCF can find the corresponding session and the SMF that manages the session according to the binding relationship between the UE information and the application information and the UE session respectively, and determine that the user needs to switch to slice B according to the routing policy, and then in the first step
  • the PCF responsible for session policy control can query the UDR to obtain the routing policy.
  • UDR Unified Data Repository
  • Step 5 The SMF judges its own support capability for slice B according to the above-mentioned first session control message.
  • step 6 when the judgment result of this step is support, step 6 is performed, and when the judgment result of this step is unsupported, step 7 is performed.
  • the terminal will modify the session information of the PDU session according to the session modification command message sent by the SMF, so as to update the slice associated with the PDU session.
  • the SMF may send a session release command message to the UE.
  • the terminal may release the original PDU session A.
  • the session modification command message may be used to carry the above session information in the instruction message.
  • the UE accesses the application platform from the user plane corresponding to the modified session and the reconstructed session.
  • the PCF initiates the modification or re-establishment of the PDU session, and after determining the modification/re-establishment of the PDU session, the SMF that manages the original PDU instructs the UE to modify or re-establish the PDU session.
  • a session creation command message sent by the SMF that performs session management on the PDU session may also be used, and the session release command message is used to instruct the terminal to create the session according to the slice identifier.
  • the network-side device is an SMF that performs session management on the PDU session, and the SMF can actively search for the target slice from the PCF when the terminal uses the application service, and the process of updating the session can be shown in Figure 6,
  • the update session can include the following procedures:
  • Step 1 The UE initiates session establishment, and chooses to establish session A on slice A.
  • slice A may be any slice network.
  • Step 2 The UE accesses the application platform AF from the user plane of session A.
  • Step 3 The NEF or AF sends a first service request to the SMF that manages the session.
  • the above-mentioned first service request has the same meaning as the first service request in the embodiment shown in FIG. 5 , and details are not repeated here.
  • Step 4 The SMF sends a request message to the PCF.
  • the request information may carry UE information (for example: UE's IP address) and application information (for example: application address, application ID), or may also carry query parameters such as session information (application-related information and/or user information) related information) to request the PCF to query the user's routing policy based on the above query parameters.
  • UE information for example: UE's IP address
  • application information for example: application address, application ID
  • query parameters such as session information (application-related information and/or user information) related information) to request the PCF to query the user's routing policy based on the above query parameters.
  • Step 5 The PCF sends a response message to the SMF.
  • the above response message is specifically a response message of a request message, and the response message carries the slice identifier that is determined according to the session query parameter and that the PDU session needs to be associated with.
  • the PCF responsible for session policy control can obtain the routing policy by querying the UDR.
  • Step 6 The SMF judges its ability to support slice B.
  • step 7 when the judgment result of this step is support, step 7 is executed, and when the judgment result of this step is not support, step 8 is executed.
  • This step is the same as step 7 in the embodiment shown in FIG. 5 , and details are not repeated here.
  • the SMF initiates the modification or reconstruction of the PDU session, and in the process of initiating the modification/reconstruction of the PDU session, the routing policy is searched from the PCF to determine the slice B, thereby instructing the terminal to modify the session of the PDU session accordingly, Or do session rebuild.
  • a session creation command message sent by the SMF that performs session management on the PDU session may also be used, and the session release command message is used to instruct the terminal to create the session according to the slice identifier.
  • the network side device is a network platform
  • the network platform can instruct the terminal to create a PDU session.
  • the process of updating the session can be as shown in FIG. 7
  • the updating session can include the following processes:
  • Step 1 The UE initiates session establishment, and chooses to establish session A on slice A.
  • Step 2 The UE accesses the application platform AF from the user plane of session A.
  • Step 3 NEF or AF sends query parameters to PCF.
  • Step 4 The PCF queries the routing policy according to the query parameters.
  • the PCF responsible for session policy control can obtain the routing policy by querying the UDR.
  • Step 5 The PCF returns the corresponding slice identifier to the AF or NEF.
  • the PCF can also return UE information and application information to the AF or NEF.
  • Step 6 The AF or NEF sends a service notification message to the network platform.
  • the service notification message may also carry UE information and application information and push it to a network platform that can send a notification to the UE.
  • Step 7 The network platform sends an application trigger message to the UE.
  • the application trigger message is used to instruct the terminal to access the application server through the PDU session related to the slice identifier.
  • Step 8 The UE checks whether the session information has already established a PDU session.
  • step 8 when the judgment result of this step is that the session information has established a PDU session, step 8 is executed, and when the judgment result of this step is that the session information has not established a PDU session, step 9 is executed.
  • Step 9 Access the application server through the PDU session.
  • Step 10 Initiate a new PDU session establishment process according to the instruction of the network entity, and access the application server through the newly created PDU session through the process.
  • the AF initiates the PDU session creation process, and in the process of initiating the PDU session creation process, the AF sends the session-based information to the UE through a network platform (for example, a Short Message Service Center (Short Message Service Center, SMSC)).
  • SMSC Short Message Service Center
  • the instruction to create a PDU session, and the UE will check whether there is a PDU session based on the session information. If there is, there is no need to create a new PDU session.
  • FIG. 8 is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • the terminal 800 includes:
  • the first transceiver module 801 is configured to receive an indication message sent by a network-side device after establishing a PDU session, where the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform an update on the PDU session according to the slice identifier. Modify, rebuild, or initiate a PDU session establishment process.
  • the indication message also includes the data network name DNN.
  • the indication message includes at least one of the following messages:
  • a session modification command message sent by the SMF that performs session management on the PDU session where the session modification command message is used to instruct the terminal to modify the slice identifier related to the PDU session as the slice identifier included in the session modification command message;
  • the session release command message sent by the SMF for session management is carried out to the PDU session, and the session release command message is used to instruct the terminal to release the session, and rebuild the session according to the slice identifier;
  • An application trigger message sent by the network platform where the application trigger message is used to instruct the terminal to access the application server through the PDU session related to the slice identifier.
  • the terminal 800 further includes:
  • an establishment module configured to initiate a PDU session establishment process without establishing a session related to the slice identifier, and establish a PDU session related to the slice identifier for accessing the application server;
  • An access module configured to access the application server by using the PDU session related to the slice identifier when the session related to the slice identifier has been established.
  • the terminal in the embodiment of the present disclosure can receive an instruction message sent by the network side device, so as to determine the slice information corresponding to the session according to the slice identifier specified by the network side device, so as to modify the session, rebuild the session or initiate the session establishment process based on the slice identifier specified by the network side device.
  • the terminal When establishing a PDU session, the terminal needs to select a slice corresponding to the session, and there is a problem that the process of selecting a slice is difficult to implement.
  • FIG. 9 is a schematic structural diagram of a network-side device provided by an embodiment of the present disclosure.
  • the network-side device 900 includes:
  • the first sending module 901 is configured to send an indication message to the terminal after the terminal establishes a PDU session; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to perform the PDU session on the PDU session according to the slice identifier. Modify, rebuild, or initiate a PDU session establishment process.
  • the indication message also includes the data network name DNN.
  • the network side device is a network platform or an SMF that performs session management on the PDU session.
  • the indication message includes at least one of the following messages:
  • the session modification command message is used to instruct the terminal to modify the slice identifier related to the PDU session as the slice identifier included in the session modification command message;
  • session release command message sent by the SMF, where the session release command message is used to instruct the terminal to release a session, and rebuild the session according to the slice identifier;
  • An application trigger message sent by the network platform where the application trigger message is used to instruct the terminal to access an application server through a PDU session related to the slice identifier.
  • the network side device is the SMF, and in the case that the SMF does not support the slice identifier, the indication message is the session release command message;
  • the network-side device is the SMF, and when the SMF supports the slice identifier, the indication message is the session modification command message or the session release command message.
  • the network-side device is the SMF
  • the network-side device 900 further includes a second receiving module configured to receive a first session control message sent by the PCF, where the first session control message carries the routing policy according to the routing Determined slice ID.
  • the network side device is the SMF, and the network side device 900 further includes:
  • a third receiving module configured to receive a first service request sent by the NEF or AF, where the first service request carries application-related information and/or user-related information;
  • a second sending module configured to send a first request message to the PCF after detecting that the terminal accesses the application according to the first service request, where the first request message is used to instruct the PCF to query a routing policy;
  • the fourth receiving module is configured to receive a response message sent by the PCF, where the response message carries the slice identifier determined according to the routing policy.
  • response message also includes the data network name DNN.
  • the application-related information includes: the address of the application and/or the identifier of the application;
  • the user-related information includes: the address of the user and/or the identifier of the user.
  • the response message is a second session control message.
  • the network side device is a network platform, and the network side device 900 further includes:
  • the fifth receiving module is configured to receive a service message sent by the AF or NEF, where the service message carries a slice identifier that needs to be associated with a PDU session accessing the application server.
  • the service message further includes the DNN.
  • the network-side device in the embodiment of the present disclosure can send an instruction message to the terminal to instruct the PDU session to be modified, reestablished, or initiate a session establishment process, so that the terminal can update the corresponding session according to the instruction message, thereby avoiding the need for the terminal to establish a session.
  • a slice corresponding to the session needs to be selected, and there is a problem that the process of selecting a slice is difficult to implement.
  • FIG. 10 is a schematic structural diagram of a PCF entity provided by an embodiment of the present disclosure.
  • the PCF entity 1000 includes:
  • a query module 1001 is used to query a routing strategy
  • the determining module 1002 is further configured to determine a slice identifier according to the routing strategy
  • the third sending module 1003 is configured to send the slice identifier.
  • the slice identifier is used by the terminal to modify and rebuild the established PDU session, or initiate a PDU session establishment procedure.
  • the method further includes:
  • a fourth receiving module configured to receive a request message sent by the SMF, AF or NEF, where the request message carries application-related information and/or user-related information for querying the routing policy;
  • the third sending module 1003 is specifically used for:
  • the slice identifier determined according to the routing policy is sent to the NEF or the AF.
  • PCF entity also includes:
  • the fourth sending module is configured to send the data network name DNN after the slice identifier is determined according to the routing strategy.
  • the PCF entity 1000 in the embodiment of the present disclosure can determine the slice identifier that needs to be associated with the PDU session based on the query parameter corresponding to the PDU session established by the terminal, thereby avoiding the need for the terminal to select the slice corresponding to the session when establishing the PDU session.
  • an embodiment of the present disclosure further provides an entity including a bus 1101 , a transceiver 1102 , an antenna 1103 , a bus interface 1104 , a processor 1105 and a memory 1106 .
  • the entity is a network side device, and the entity includes a processor 1105 and a transceiver 1102;
  • the transceiver 1102 is configured to send an indication message to the terminal after the terminal establishes a PDU session; the indication message includes a slice identifier, and the indication message is used to instruct the terminal to modify the PDU session according to the slice identifier, Rebuild and release the PDU session, or initiate a PDU session establishment procedure.
  • the indication message further includes the data network name DNN.
  • the network side device is a network platform or an SMF that performs session management on the PDU session.
  • the indication message includes at least one of the following messages:
  • the session modification command message is used to instruct the terminal to modify the slice identifier related to the PDU session as the slice identifier included in the session modification command message;
  • session release command message sent by the SMF, where the session release command message is used to instruct the terminal to release a session, and rebuild the session according to the slice identifier;
  • An application trigger message sent by the network platform where the application trigger message is used to instruct the terminal to access an application server through a PDU session related to the slice identifier.
  • the network side device is the SMF, and in the case that the SMF does not support the slice identifier, the indication message is the session release command message;
  • the network-side device is the SMF, and when the SMF supports the slice identifier, the indication message is the session modification command message or the session release command message.
  • the network-side device is the SMF
  • the transceiver 1102 is further configured to:
  • a first session control message sent by the PCF is received, where the first session control message carries a slice identifier corresponding to the PDU session determined according to the routing policy.
  • the network-side device is the SMF
  • the transceiver 1102 is further configured to:
  • response message also includes the DNN.
  • the application-related information includes: the address of the application and/or the identifier of the application;
  • the user-related information includes: the address of the user and/or the identifier of the user.
  • the response message is a second session control message.
  • the network side device is a network platform, and before the transceiver 1102 executes sending the instruction message to the terminal, it is further used for:
  • the service message further includes the DNN.
  • the entity can implement each process implemented by the network-side device in the method embodiment shown in FIG. 6 , which is not repeated here to avoid repetition.
  • the entity in this embodiment can instruct the terminal to update the session after the terminal establishes the PDU session, so that the terminal can modify the session, rebuild the session or initiate the session update process according to the instruction of the entity, thereby avoiding the need for the terminal to establish the PDU session. Selecting a slice corresponding to the session has the problem that the process of selecting a slice is difficult to implement.
  • the entity is a PCF entity, and the entity includes a processor 1105 and a transceiver 1102;
  • the processor 1005 is configured to query the routing policy
  • the processor 1005 is further configured to determine a slice identifier according to the routing strategy
  • the transceiver 1002 is configured to send the slice identifier.
  • the slice identifier is used by the terminal to modify and rebuild the established PDU session, or initiate a PDU session establishment procedure.
  • the transceiver 1002 is further configured to receive a request message sent by the SMF, AF or NEF, where the request message carries application-related information and/or user-related information for querying the routing policy;
  • the sending of the slice identifier performed by the transceiver 1002 is specifically:
  • the slice identifier determined according to the routing policy is sent to the NEF or the AF.
  • transceiver 1102 is also used for:
  • the DNN is also sent.
  • the entity can implement each process implemented by the PCF in the method embodiment shown in FIG. 7 , which is not repeated here to avoid repetition.
  • the entity in this embodiment can, after the terminal establishes a PDU session, receive a session query request to determine a slice identifier that needs to be associated with the PDU session established by the terminal, and can subsequently inform the terminal through the network side to perform session modification, reconstruction, or initiate a session update process, In this way, the PDU session is updated to be related to the slice identifier, thereby avoiding the problem that the terminal needs to select the slice corresponding to the session when establishing the PDU session, and the process of selecting the slice is difficult to implement.
  • bus 1101 will include one or more processors represented by processor 1105 and memory represented by memory 1106 The various circuits are linked together.
  • the bus 1101 may also link together various other circuits, such as peripherals, voltage regulators and power management circuits, etc., which are well known in the art and therefore will not be described further herein.
  • Bus interface 1104 provides an interface between bus 1101 and transceiver 1102 .
  • Transceiver 1102 may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium.
  • the data processed by the processor 1105 is transmitted on the wireless medium through the antenna 1103 , and further, the antenna 1103 also receives the data and transmits the data to the processor 1105 .
  • the processor 1105 is responsible for managing the bus 1101 and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions.
  • memory 1106 may be used to store data used by processor 1105 in performing operations.
  • the processor 1105 may be a central processing unit (central processing unit, CPU), an ASIC, an FPGA, or a complex programmable logic device (Complex Programmable Logic Device, CPLD).
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • CPLD complex programmable logic device
  • an embodiment of the present disclosure further provides a terminal, including a processor 1105 , a memory 1106 , a computer program stored in the memory 1106 and executable on the processor 1105 , when the computer program is executed by the processor 105
  • a terminal including a processor 1105 , a memory 1106 , a computer program stored in the memory 1106 and executable on the processor 1105 , when the computer program is executed by the processor 105
  • a terminal including a processor 1105 , a memory 1106 , a computer program stored in the memory 1106 and executable on the processor 1105 , when the computer program is executed by the processor 105
  • Embodiments of the present disclosure further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the session update method shown in FIG. 2 , FIG. 6 or FIG. 7 is implemented. In order to avoid repetition, the details are not repeated here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solutions of the present disclosure can be embodied in the form of software products in essence or the parts that make contributions to related technologies.
  • the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) ), including several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the various embodiments of the present disclosure.
  • modules, units, and sub-units can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSP Device, DSPD) ), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, in other electronic units or combinations thereof.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processor
  • DSP Device Digital Signal Processing Device
  • DSPD Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the technologies described in the embodiments of the present disclosure may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • Software codes may be stored in memory and executed by a processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

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

Abstract

本公开提供一种会话更新方法、终端和网络侧设备，该应用于终端的会话更新方法，包括：建立协议数据单元PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。

Description

会话更新方法、终端和网络侧设备
相关申请的交叉引用
本申请主张在2020年8月13日在中国提交的中国专利申请号No.202010815092.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种会话更新方法、终端和网络侧设备。
背景技术
在5G通信中提供端到端切片服务，为垂直行业用户提供专属、差异化和质量保证的专网服务。其中，垂直行业用户开通切片服务后，由网络侧生成UE路由选择策略(UE Route Selection Policy，URSP)，在用户终端(User Equipment，UE)注册网络后下发给UE。UE保存URSP后，在使用垂直行业用户提供的应用服务时，根据URSP选择指定切片，由5G网络切片技术保证服务质量。
在相关技术中，虽然网络侧提供端到端切片服务功能，且已定义URSP的下发流程及匹配规则，但是UE侧实现URSP匹配应用时，难以按照网络侧下发的路由/切片选择策略为应用相关的业务流匹配对应的切片。
发明内容
本公开实施例提供一种会话更新方法、终端和网络侧设备，以解决UE难以在会话建立时根据URSP选择切片的问题。
为解决上述技术问题，本公开是这样实现的：
第一方面，本公开实施例提供了一种会话更新方法，用于终端，所述会话更新方法包括：
建立协议数据单元(Protocol Data Unit，PDU)会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述 终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第二方面，本公开实施例提供一种会话更新方法，用于网络侧设备，所述会话更新方法包括：
在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第三方面，本公开实施例提供一种会话更新方法，用于策略控制功能实体(Policy Control Function，PCF)，所述会话更新方法包括：
查询路由选择策略；
根据所述路由选择策略确定切片标识；
发送所述切片标识。
第四方面，本公开实施例提供一种终端，所述终端包括：处理器和收发机；
所述收发机，用于建立PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第五方面，本公开实施例提供一种网络侧设备，所述网络侧设备包括：处理器和收发机；
所述收发机，用于在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第六方面，本公开实施例提供一种PCF，所述PCF包括：处理器和收发机；
所述处理器，用于查询路由选择策略；
所述处理器，还用于根据所述路由选择策略确定切片标识；
所述收发机，用于发送所述切片标识。
第七方面，本公开实施例提供一种终端，所述终端包括：
接收模块，用于建立PDU会话后，接收网络侧设备发送的指示消息，所 述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第八方面，本公开实施例提供一种网络侧设备，所述网络侧设备包括：
发送模块，用于在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
第九方面，本公开实施例提供一种PCF，所述PCF包括：
查询模块，用于查询路由选择策略；
确定模块，还用于根据所述路由选择策略确定切片标识；
发送模块，用于发送所述切片标识。
第十方面，本公开实施例提供一种终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第一方面所述的会话更新方法中的步骤。
第十一方面，本公开实施例提供一种网络侧设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第二方面所述的会话更新方法中的步骤。
第十二方面，本公开实施例提供一种PCF，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第三方面所述的会话更新方法中的步骤。
第十三方面，本公开实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如第一方面所述的会话更新方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如第二方面所述的会话更新方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如第三方面所述的会话更新方法中的步骤。
本公开实施例中，终端在建立PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、修改，或发起PDU会话建立流程。这样，终端仅需根据网络侧设备的指示的切片标识，对PDU会话进行修改、重建或者建立，便能够实现将PDU会话切换至指定切片上，避免了UE难以 在会话建立时根据URSP选择切片的问题。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例可应用的一种网络系统的结构图；
图2是本公开实施例提供的第一种会话更新方法的流程图；
图3是本公开实施例提供的第二种会话更新方法的流程图；
图4是本公开实施例提供的第三种会话更新方法的流程图；
图5是本公开实施例提供的会话更新方法的实施例一的流程图；
图6是本公开实施例提供的会话更新方法的实施例二的流程图；
图7是本公开实施例提供的会话更新方法的实施例三的流程图；
图8是本公开实施例提供的一种终端的结构图；
图9是本公开实施例提供的一种网络侧设备的结构图；
图10是本公开实施例提供的一种PCF的结构图；
图11是本公开实施例提供的另一种实体的结构图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开实施例提供的会话更新方法可以应用于如图1所示切片网络系统，其中，该系统包括终端11和切片网络(如图1中所示的：第一切片网络12、第二切片网络13和第三切片网络14)。不同的切片网络可以对应不同的无线接入网121(Radio Access Network，RAN)、传输网122(Transport Network，TN)和核心网123(Core Network，CN)，以分别通过不同的切片网络向用户 提供不同的服务功能，即为垂直行业用户提供专属、差异化和具有质量保证的专网服务，例如：服务于第5代(5th Generation，5G)通信系统大网(公众网)的网络云游戏服务，以及服务于5G专网客户等应用场景。
其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(vehicle user equipment，VUE)、行人终端(pedestrian user equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等，本公开实施例并不限定终端11的具体类型。
值得指出的是，本申请实施例所描述的技术不限于5G通信系统，其也可应用于新空口(New Radio，NR)系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
目前通过预先定义的URSP策略实现切片和应用服务的映射，URSP在UE注册网络后下发给UE。UE在使用应用服务时，根据URSP策略找到指定切片信息，在会话建立时告诉网络需要选择的切片。
垂直行业用户订购开通切片后，5G网络会生成URSP，并在UE注册网络后下发给UE。而UE保存URSP，在使用垂直行业用户提供的应用服务时，根据URSP选择指定切片，由5G网络切片技术保证服务质量。
然而，在相关技术中，通过UE侧实现URSP匹配应用存在难度，UE难以按照网络侧下发的路由/切片选择策略匹配应用相关的业务流，并选择指定切片和DNN建立会话。具体包括以下三大难点：
难点一、URSP中的业务描述符(Application Identity，APP ID)目前在第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)标准化协议中难以定义，该APP ID与应用管理环境相关，可能需要第三方应用提供商、终端厂商、运营商协商，即标准进度限制了终端切片功能的开发。
难点二、终端采用URSP定义的其他业务匹配条件如IP三元组也存在实际应用限制。例如：应用服务器的IP地址可能因为容灾备份方案或者资源调 整发生变化，难以按照网络侧下发的切片和DNN选择策略建立会话。
难点三、如果对终端进行定制，把路由/切片选择策略内置在终端里，实现业务流和切片绑定，则对应用场景存在限制，造成切片功能不灵活，或者不能适应应用场景的问题，例如：游戏类切片服务中，由于用户的终端选择类型很多，不可能对每一个终端选择进行定制；又如，垂直行业客户要求多切片和行业终端支持多切片，则在多切片场景下，还是存在切片和应用无法映射的情况。
而本申请实施例中，在终端访问应用时，由网络侧告知终端网络为该应用提供服务的切片，以解决上述的难题。
参见图2，图2是本公开实施例提供的一种会话更新方法的流程图，用于终端，如图2所示，所述会话更新方法可以包括以下步骤：
步骤201、建立PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
其中，“PDU会话”为在切片(或者还可以称之为：切片网络)上建立的会话，该会话用于从服务平台获取服务。上述切片标识可以是单网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)，即指示终端需要将PDU会话更新至S-NSSAI对应的目标切片上。当然，该指示消息还可以包括其他信息，例如：会话类型/DNN/网际互连协议(Internet Protocol，IP)地址等中的一项或者多项，此时，指示信息还可以指示终端更新会话的会话类型/DNN/IP地址等。
例如，在PDU会话的数据网络名称(Data Network Name，DNN)需要修改时，所述指示消息还包含数据网络名称DNN。此时，终端根据该指示消息将PDU会话更新为与S-NSSAI和DNN关联的PDU会话。
在本公开具体实施例中，上述的“更新”可以包括会话修改、会话重建或发起PDU会话建立流程等。
需要说明的是，在具体实施中，对于会话的重建可以通过复用相关技术中的会话释放命令消息来实现。例如，通过在会话释放命令消息中可以携带原因值，以指示终端释放会话，并根据所述切片标识重建所述PDU会话，且 使得重建的所述PDU会话与切片标识相关。
本公开具体实施例中，所谓所述PDU会话与切片标识相关/关联可以理解为该PDU会话由切片标识指示的切片或切片网络承载。
在重建PDU会话的过程中，该指示消息可以不包括其他信息(例如：会话类型/DNN/IP)，则终端在重建PDU会话时仅更新S-NSSAI，而不更新会话类型/DNN/IP地址等其他会话信息。
另外，上述指示消息还可以包括应用访问地址、对原有PDU会话的处理方式(保留或释放)等，以指示终端对PDU会话进行修改，还是重建PDU会话，还是发起PDU会话建立流程。
本公开实施例通过网络侧设备指示终端进行PDU会话修改、重建或者新建，使得网络侧能够控制UE通过合适的切片来为用户提供服务，解决了终端难以按照网络侧下发的路由/切片选择策略为应用相关的业务流匹配合适的切片的问题。
需要说明的是，在执行步骤201之前，终端建立PDU会话时，所建立的PDU会话可以是在与指定应用/应用服务器对应或者不对应的任一切片网络上建立的会话。
而且，在终端建立PDU会话且使用应用时，可以通过用户面和应用检测机制识别出需要选择到指定切片的业务流，并检测终端建立的PDU会话与需要选择到指定切片的业务流是否匹配，且进行业务流检测的实体将检测结果通知网络实体。当网络实体在获知终端建立的PDU会话与需要选择到指定切片的业务流匹配时，不作处理，即终端保持PDU会话在当前的切片上访问应用；当网络实体在获知终端建立的PDU会话与需要选择到指定切片的业务流不匹配时，可以由网络侧指示网络为该应用提供服务的切片(例如S-NSSAI)，从而触发终端根据所述切片标识对所述PDU会话进行修改、重建所述PDU会话，或发起PDU会话建立流程，以使终端切换至与指定应用对应的切片上。
在具体实施中，上述网络侧设备可以是对所述PDU会话进行会话管理的会话管理功能实体(Session Management Function，SMF)或者网络平台。所述指示消息包括如下消息中的至少一个：
所述SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所 述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
所述SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
所述网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
在第一种实施方式中，所述指示消息为：对所述PDU会话进行会话管理的SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识，以更新PDU会话。
在具体实施中，对所述PDU会话进行修改可以理解为修改PDU会话中的会话属性。
本实施方式中，终端基于SMF发送的会话修改命令消息，对PDU会话的会话属性进行修改，以将所述PDU会话相关的切片标识修改为所述会话修改命令消息包含的切片标识，从而实现将PDU会话关联到目标切片上。
在第二种实施方式中，所述指示消息为：对所述PDU会话进行会话管理的SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话。
本实施方式中，终端基于SMF发送的会话释放命令消息，释放所述PDU会话并重建与所述切片标识关联的会话。
进一步的，所述会话释放命令消息可以携带原因值，所述原因值用于指示所述终端重建所述PDU会话，且重建的所述PDU会话与所述切片标识相关。
这样，终端在释放所述PDU会话之后，还可以重新建立PDU会话，具体可以是在网络侧发送的切片标识对应切片上建立PDU会话，从而实现将PDU会话关联到目标切片上。
在实际应用中，终端进行PDU会话重建后，可以发送当前PDU会话的业务流到重建的PDU会话的用户面通道。
在第三种实施方式中，所述指示消息为：网络平台发送的应用触发消息， 所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
本公开具体实施例中还可以通过对所述PDU会话进行会话管理的SMF发送的会话新建命令消息，所述会话释放命令消息用于指示所述终端根据所述切片标识新建所述会话。
本实施方式与以上两种实施方式的不同之处在于：以上两种实施方式中由SMF发送指示消息，而本实施方式中由网络平台发送指示消息，且终端在接收到所述指示消息时，能够在该终端已建立与该切片标识相关的PDU会话时，直接使用与所述切片标识相关的PDU会话访问应用服务器。而在终端未建立与该切片标识相关的PDU会话时，则建立用于访问所述应用服务器的，与所述切片标识相关的PDU会话，从而实现将PDU会话关联到目标切片上。
换句话说，在所述指示消息为应用触发消息的情况下，还包括：
在没有建立与所述切片标识有关的会话的情况下，发起PDU会话建立流程，建立用于访问所述应用服务器的，与所述切片标识相关的PDU会话；
或者
在已经建立与所述切片标识有关的会话的情况下，使用与所述切片标识相关的PDU会话访问所述应用服务器。
在具体实施中，在所述切片标识对应的PDU会话未建立时，若需要基于该切片标识访问应用服务器，则需要建立与所述切片标识对应的PDU会话，从而发起PDU会话建立流程，以建立于访问所述应用服务器的，与所述切片标识相关的PDU会话。
另外，在已经建立与所述切片标识有关的会话的情况下，终端无需重新建立PDU会话，即可以直接使用与所述切片标识相关的PDU会话访问所述应用服务器。
本公开具体实施方式中，网络侧通过向终端发送的指示消息中携带切片标识，指示终端通过切片标识对应的目标切片访问应用。
本申请实施例与相关技术不同的是：在相关技术中，终端需要在PDU会话建立前，根据业务描述符匹配URSP，找到网络为应用提供服务的切片的标识，以在PDU会话建立的过程中，UE携带会话信息(或者称之为会话参 数)、切片的标识进行PDU会话建立，这样，PDU会话建立成功后，UE所建立的PDU会话使用这个切片的资源，并由这个切片提供质量保证。
而本申请的技术方案中，则是UE直接建立PDU会话，而后根据网络侧指示来讲PDU会话关联到正确的切片。正确切片的确定由网络侧决策，避免了相关技术中终端难以按照网络侧下发的路由/切片选择策略为应用相关的业务流匹配对应切片的问题。
在实际应用中，终端具体是对所述PDU会话进行修改、重建，或发起PDU会话，可以通过判断切换前的PDU会话对应的SMF对目标切片的支持能力确定，具体可以包括以下三种情况：
情况一
网络侧设备为SMF，所述SMF支持所述切片标识对应的目标切片的情况下，所述指示消息为所述会话修改命令消息或会话释放命令消息。
本实施方式中，通过对所述PDU会话进行修改或者重建，以使终端将会话更新至所述SMF支持的所述切片标识对应的切片上。
情况二
网络侧设备为SMF，所述SMF不支持所述切片标识对应的目标切片的情况下，可以对所述PDU会话进行重建。
其中，通过对所述PDU会话进行重建，能够释放原有的PDU会话并建立与所述切片标识对应的PDU会话，以使终端将会话更新为新建立的PDU会话。
情况三
网络侧设备为能够向终端发送通知消息的网络平台，该网络平台能够向终端发送应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。则终端在未建立与所述切片标识相关的PDU会话的情况下，将新建与所述切片标识相关的PDU会话，并通过新建的PDU会话方位应用服务器。
另外，在对所述PDU会话进行新建时，在保留原有的PDU会话的基础上，新建一个与所述切片标识对应的PDU会话。
本公开实施例中，终端在建立PDU会话后，接收网络侧设备发送的指示 消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、修改，或发起PDU会话建立流程。这样，终端仅需根据网络侧设备的指示的切片标识，对PDU会话进行修改、重建或者建立，便能够实现将PDU会话切换至指定切片上，避免了UE难以在会话建立时根据URSP选择切片的问题。
请参阅图3，是本公开实施例提供的第二种会话更新方法的流程图，该会话更新方法应用于网络侧设备，如图3所示，该会话更新方法可以包括以下步骤：
步骤301、在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
其中，上述指示消息与如图2所示方法实施例中的指示消息具有相同含义，在此不再赘述。
进一步的，在PDU会话的数据网络名称DNN需要修改时，所述指示消息还包含数据网络名称DNN。
进一步的，所述网络侧设备为网络平台或对所述PDU会话进行会话管理的SMF。
进一步的，所述指示消息包括如下消息中的至少一个：
所述SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
所述SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
所述网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
情况一
上述会话修改命令消息，用于指示终端修改PDU会话的切片网络，以使终端在修改后的切片网络上访问应用平台。
情况二
上述会话释放命令消息，用于指示终端释放当前的PDU会话，并重建一个与切片标识相关的会话。
在具体实施中，SMF可以向终端发送的会话释放命令消息中可以携带原因值，所述原因值用于指示所述终端重建所述PDU会话，且重建的所述PDU会话与所述切片标识相关。
这样，终端能够通过重建的PDU会话访问应用平台。
情况三
上述应用触发消息，用于指示终端通过与所述切片标识相关的PDU会话访问应用服务器。
与情况二中的：SMF向终端发送会话释放命令消息不同的是，本实施方式中，终端在接收到该应用触发消息时，判断其当前的PDU会话是否与所述切片标识相关，若相关，则可以通过该PDU会话访问应用平台；若不相关，则可以新建与该切片标识相关的PDU会话，并通过该新建的PDU会话访问应用平台，且原PDU会话可以保留。
在一种可选的实施方式中，所述网络侧设备为所述SMF，所述SMF不支持所述切片标识的情况下，所述指示消息为所述会话释放命令消息；
或者
所述网络侧设备为所述SMF，所述SMF支持所述切片标识的情况下，所述指示消息为所述会话修改命令消息或会话释放命令消息。
其中，在述SMF不支持所述切片标识的情况下，通过会话释放命令消息，可以指示终端在新支持所述切片标识的另一SMF上重新建立一个会话，以通过该会话访问应用服务器。此时，原SMF上的会话可以释放，以节约网络资源。
另外，在述SMF支持所述切片标识的情况下，可以通过会话修改命令消息，将会话更新至所述切片标识上，或者，还可以通过会话释放命令消息，在同一SMF上重新建立一个会话，以通过该会话访问应用服务器。
在第一种实施方式中，所述网络侧设备为所述SMF，发送指示消息到终端之前，还包括：
接收PCF发送的第一会话控制消息，所述第一会话控制消息携带根据所 述路由选择策略确定的切片标识。(换句话说，也就是：接收PCF在确定所述PDU会话需要与切片选择辅助信息关联后发送的第一会话控制消息，所述第一会话控制消息携带所述PDU会话需要关联的所述切片标识。)
在具体实施中，PCF能够获取：应用相关信息和/或用户相关信息(例如应用信息、会话信息以及UE信息)等，以根据这些信息，通过查询路由选择策略确定所述PDU会话需要关联的切片标识。
另外，所述第一会话控制消息还可以携带应用相关信息和/或用户相关信息，以使所述SMF基于这些信息和切片标识确定对PDU会话进行修改，还是进行重建，还是进行新建。
在第二种实施方式中，所述网络侧设备为所述SMF，发送指示消息到终端之前，还包括：
接收NEF或AF发送的第一服务请求，所述第一服务请求携带应用相关信息和/或用户相关信息；
根据所述第一服务请求检测到终端访问了所述应用后，向PCF发送第一请求消息，所述第一请求消息用于指示所述PCF查询路由选择策略；
接收PCF发送的响应消息，所述响应消息携带根据所述路由选择策略确定的所述切片标识。
在具体实施中，第一服务请求中可以携带查询参数，该查询参数可以包括应用相关信息和用户相关信息中的至少一项，其还可以包括终端建立的会话信息等。
所述接收NEF或AF发送的第一服务请求，所述第一服务请求携带应用相关信息(例如：应用相关的地址，其也可以称之为“应用信息”)或用户相关信息(其也可以称之为“UE信息”)，所述SMF在接收到该第一服务请求时，请求PCF请求获取所述PDU会话需要关联的所述切片标识，由此向PCF发送第一请求消息。
所述根据所述第一服务请求检测到终端访问了所述应用后，向PCF发送第一请求消息，所述第一请求消息用于指示PCF查询路由选择策略，该第一请求消息可以携带上述应用信息和UE信息。具体的，上述应用相关信息可以包括：所述应用的地址和/或所述应用的标识；所述用户相关信息可以包括： 所述用户的地址和/或所述用户的标识。
换句话说，也就是SMF发送的用于请求PCF查询路由选择策略的第一请求消息中携带的查询参数，该会话参数以包括如下参数中的至少一个：所述PDU会话对应的应用信息、所述PDU会话对应的服务器信息和所述PDU会话对应的终端标识信息。
PCF在接收到该请求消息后，进行路由选择策略查询，以确定所述PDU会话需要关联的所述切片标识，并将查询得到的所述切片标识携带于响应消息中，以发送至SMF。
在具体实施中，所述响应消息还可以包含数据网络名称。
换句话说，也就是当所述PDU会话需要关联数据网络名称DNN时，可以使SMF根据该响应消息指示终端将与所述切片标识关联的PDU会话与数据网络名称关联。
进一步的，所述响应消息为第二会话控制消息。
在具体实施会中，SMF可以根据第一会话控制消息或者第二会话控制消息确定对PDU会话进行修改、重建或者新建。
本实施方式中，SMF能够基于NEF或AF发送的第一服务请求主动触发对PDU会话进行修改、重建或者新建，并主动从PCF中查找切片标识。
在第三种实施方式中，所述网络侧设备为网络平台，发送指示消息到终端之前，还包括：
接收AF或NEF发送的服务消息(服务消息也可以称之为“服务通知消息”)，所述服务消息携带访问应用服务器的PDU会话需要关联的切片标识。
在具体实施中，所述接收AF或NEF发送的服务消息，所述服务消息携带访问应用服务器的PDU会话需要关联的切片标识，可以是：UE建立PDU会话后，通过该PDU会话访问应用服务器时，NEF或AF基于该动作触发PCF进行路由选择策略查询，以确定访问应用服务器的PDU会话需要关联的切片标识，并发送给UE。其具体可以参照如图7所示实施例的过程。
进一步的，所述服务消息还包含DNN。
本实施方式中，由AF发起PDU会话新建流程，且在AF发起PDU会话新建流程的过程中，通过网络平台(例如：SMSC)向UE发送基于会话信 息新建PDU会话的指示，并由UE自行检查是否已经存在基于该会话信息的PDU会话，若果有，则不需要新建PDU会话，如果没有，则基于该会话信息新建PDU会话。
请参阅图4，是本公开实施例提供的第三种会话更新方法的流程图，该会话更新方法应用于PCF，如图4所示，该会话更新方法可以包括以下步骤：
步骤401、查询路由选择策略。
步骤402、根据所述路由选择策略确定切片标识。
步骤403、发送所述切片标识。
在具体实施中，所述切片标识用于终端对建立的PDU会话进行修改、重建，或发起PDU会话建立流程。
具体的，PCF能够基于所述终端建立的PDU会话对应的查询参数(应用相关信息和/或用户相关信息)和路由选择策略确定与该PDU会话对应的服务平台对应的切片标识。
作为一种可选的实施方式，所述会话更新方法，还包括：
在根据所述路由选择策略确定切片标识后，还发送数据网络名称DNN。
在具体实施中，PCF可以向网络侧设备发送该DNN，以使网络侧设备指示终端更新PDU会话关联的DNN。
作为一种可选的实施方式，所述查询路由选择策略之前，还包括：
接收SMF、AF或NEF发送的请求消息，所述请求消息携带用于查询所述路由选择策略的应用相关信息和/或用户相关信息；
所述发送所述切片标识具体为：
向SMF发送根据所述路由选择策略确定的切片标识；
或
向NEF或AF发送根据所述路由选择策略确定的切片标识。
在一种实施方式中，SMF能够在接收AF或NEF发送的第一服务请求时，通过向PCF发送第一请求消息，以主动请求PC发基于该应用相关信息和用户相关信息中的至少一个进行路由选择策略查询，并将利用查询得到的路由选择策略得到的切片标识发送至SMF、AF或NEF中的至少一个。
具体的，当切片标识发送至SMF时，该SMF可以基于其切片支持能力 指示终端进行会话修改或者会话重建。
当切片标识发送至AF或NEF时，AF或NEF能够通过能够向终端发送通知消息的网络平台将该切片标识告知终端，以指示终端通过该切片标识相关的会话访问应用。且在终端未建立与该切片标识相关的会话时，使终端发起会话建立流程，以建立与切片标识相关的会话后，通过该会话访问应用。
在另一种实施方式中，PCF能够接收AF或NEF发送的请求消息，以根据该请求消息中携带的应用相关信息和/或用户相关信息主动进行路由选择策略查询，并将利用路由选择策略查询得到的切片标识发送至SMF、AF或NEF中的至少一个。
换而言之，该切片标识用于供对所述PDU会话进行会话管理的SMF获取，或者主动将其发送至该SMF，并由该SMF指示终端进行会话修改、重建或者发起会话建立流程等会话更新操作。或者，该切片标识经能够向终端发送通知消息的网络平台发送至终端，以告知终端通过该切片标识访问应用服务器，从而使终端基于该切片标识判断是否需要新建PDU会话。
在实施中，该切片标识可以是PCF根据本地或UDR中的路由选择策略确定的。
例如：
所述应用相关信息和/或用户相关信息由AF或NEF发送，所述切片标识发送到对所述PDU会话进行会话管理的SMF。
本实施方式，可以对应网络设备为SMF，且由PCF主动进行路由选择策略查询的实施例，例如：如图5所示实施例中的步骤3和步骤4。
或者
所述应用相关信息和/或用户相关信息由对所述PDU会话进行会话管理的SMF发送，所述切片标识发送到所述SMF。
本实施方式，可以对应网络设备为SMF，且由该SMF主动触发PCF进行路由选择策略查询的实施例，例如：如图6所示实施方式中的步骤4和步骤5，在此不再赘述。
或者
所述应用相关信息和/或用户相关信息由AF或NEF发送，所述切片标识 发送到所述AF或NEF。
本实施方式，可以对应网络设备为网络平台，且由AF或NEF主动触发PCF进行路由选择策略查询的实施例，例如：如图7所示实施方式中的步骤3、步骤4和步骤5，在此不再赘述。
本公开实施例中，通过PCF基于应用相关信息和/或用户相关信息(查询参数)确定终端建立的PDU会话需要关联的切片标识，以便于网络侧设备指示终端根据该切片标识进行会话更新，同样，可以避免终端在建立PDU会话时，难以选择指定切片建立会话的问题。
为便于理解本公开实施例提供的会话更新方法，下面结合终端与网络侧设备之间的数据交互过程，对所述会话更新方法作举例说明：
实施方式一
所述网络侧设备是对所述PDU会话进行会话管理的SMF，且该SMF能够接收PCF发送的指示消息，则更新会话的流程可以如图5所示，该更新会话可以包括以下过程：
步骤1.UE发起会话建立，选择在切片A上建立会话A。
其中，切片A可以是任一切片网络，终端可以通过随机选取或者对不同的会话固定选取同一切片网络的方式选取所述切片A。另外，会话A即PDU会话A(含S-NSSAI＝A)。
步骤2.UE从会话A的用户面访问应用平台，即：应用功能(Application Function，AF)实体。
步骤3.NEF或AF发送第一服务请求至PCF。
本步骤中，AF检测到UE使用应用服务后，通过网络开放功能实体(Network Exposure Function，NEF)向PCF发送第一服务请求，这样，NEF能够告知PCF，UE访问应用平台，并告知UE信息(例如：UE的IP地址)和应用信息(例如：应用地址、应用ID)。
在具体实施中，AF也可以直接通知PCF，在此不作具体限定。
步骤4.PCF向原SMF发送第一会话控制消息。
本步骤中，PCF能够根据UE信息和应用信息分别与UE会话的绑定关系，找到对应的会话和对该会话进行管理的SMF，并根据路由选择策略判断用户 需要切换到切片B，然后在第一会话控制消息中携带切片标识(即S-NSSAI＝B)、应用信息、UE信息，以下发给对UE的会话进行管理的SMF。
本步骤中，在上述路由选择策略位于统一数据存储功能实体(Unified Data Repository，UDR)中的情况下，负责会话策略控制的PCF可以从UDR中查询得到该路由选择策略。
步骤5.SMF根据上述第一会话控制消息判断自己对切片B的支持能力。
其中，在本步骤的判断结果为支持时，执行步骤6，在本步骤的判断结果为不支持时，执行步骤7。
步骤6.SMF更新会话上下文，并向UE发送会话修改命令消息，以发起会话修改，更新会话相关联的S-NSSAI＝B。
本步骤中，终端将根据SMF发送的会话修改命令消息，修改PDU会话的会话信息，以更新PDU会话关联的切片。
步骤7.SMF向UE发送会话释放命令消息，以指示UE发起会话重建，并携带S-NSSAI＝B。
在本步骤中，SMF可以向UE发送会话释放命令消息，该会话释放命令消息携带S-NSSAI＝B，表示需要将会话的S-NSSAI更新为B，且该指示消息还可以不携带其他会话信息，则默认其他会话信息不变(例如：会话类型/DNN/IP地址等不变)。
需要说明的是，终端在接收到SMF的会话释放命令消息后，可以释放原PDU会话A。
另外，在释放原PDU之后，UE还执行在S-NSSAI＝B上重建PDU会话的请求，该PDU会话由支持S-NSSAIB的SMF进行会话管理。
在具体实施会中，可以在指示消息采用会话修改命令消息携带上述会话信息。
步骤8.UE根据SMF的指示进行会话修改或重建，将访问指定应用的PDU会话切换到切片B上(即S-NSSAI＝B)。
本步骤中，在完成会话修改或重建后，UE从修改后的会话、重建的会话对应的用户面访问应用平台。
本实施方式中，由PCF发起PDU会话修改或重建，并在确定进行PDU 会话修改/重建后，通过对原PDU进行管理的SMF指示UE进行PDU会话修改或重建。
本公开具体实施例中还可以通过对所述PDU会话进行会话管理的SMF发送的会话新建命令消息，所述会话释放命令消息用于指示所述终端根据所述切片标识新建所述会话。
实施方式二
所述网络侧设备是对所述PDU会话进行会话管理的SMF，且该SMF在获取到终端使用应用服务时，能够主动从PCF中查找目标切片，则更新会话的流程可以如图6所示，该更新会话可以包括以下过程：
步骤1.UE发起会话建立，选择在切片A上建立会话A。
其中，与如图5所示实施例相同的，切片A可以是任一切片网络。
步骤2.UE从会话A的用户面访问应用平台AF。
步骤3.NEF或AF发送第一服务请求至对该会话进行管理的SMF。
其中，上述第一服务请求与图5所示实施例中的第一服务请求具有相同含义，在此不再赘述。
步骤4.SMF向PCF发送请求消息。
本步骤中，该请求信息中可以携带UE信息(例如：UE的IP地址)和应用信息(例如：应用地址、应用ID)，或者还可携带会话信息等查询参数(应用相关信息和/或用户相关信息)，以请求PCF基于上述查询参数查询用户的路由选择策略。
步骤5.PCF向SMF发送响应消息。
其中，上述响应消息具体为请求消息的的响应消息，该响应消息携带根据会话查询参数确定的，所述PDU会话需要关联的所述切片标识。
另外，在上述路由选择策略位于UDR中的情况下，负责会话策略控制的PCF可以从UDR中查询得到该路由选择策略。
本步骤中，PCF根据路由选择策略判断用户需要切换到切片B，并将会话信息(含S-NSSAI＝B)下发给对UE的会话进行管理的SMF(即对会话A进行管理的SMF)。
步骤6.SMF判断自己对切片B的支持能力。
另外，在本步骤的判断结果为支持时，执行步骤7，在本步骤的判断结果为不支持时，执行步骤8。
步骤7.SMF更新会话上下文，并向UE发送会话修改命令消息，以发起会话修改，进而更新会话相关联的S-NSSAI＝B。
步骤8.SMF向UE发送会话释放命令消息，以指示UE发起会话重建，并携带S-NSSAI＝B
本步骤与如图5所示实施方式中的步骤7相同，在此不再赘述。
步骤9.UE根据SMF的指示进行会话修改或重建，将访问指定应用的PDU会话切换到切片B上(即S-NSSAI＝B)。
本实施方式中，由SMF发起PDU会话修改或重建，并在发起PDU会话修改/重建的过程中从PCF中查找路由选择策略，以确定切片B，从而据此指示终端对PDU会话进行会话修改，还是进行会话重建。
本公开具体实施例中还可以通过对所述PDU会话进行会话管理的SMF发送的会话新建命令消息，所述会话释放命令消息用于指示所述终端根据所述切片标识新建所述会话。
实施方式三
在所述网络侧设备是网络平台的情况下，该网络平台可以指示终端进行PDU会话新建，具体的，更新会话的流程可以如图7所示，该更新会话可以包括以下过程：
步骤1.UE发起会话建立，选择在切片A上建立会话A。
步骤2.UE从会话A的用户面访问应用平台AF。
步骤3.NEF或AF发送查询参数至PCF。
步骤4.PCF根据查询参数查询路由选择策略。
在具体实施中，在上述路由选择策略位于UDR中的情况下，负责会话策略控制的PCF可以从UDR中查询得到该路由选择策略。
步骤5.PCF向AF或NEF返回对应的切片标识。
其中，PCF返回给AF或NEF对应的切片B(即S-NSSAI＝B)，除此之外，PCF还可以给AF或NEF返回UE信息和应用信息。
步骤6.AF或NEF向网络平台发送服务通知消息。
其中，网络平台具体为可以给UE发送通知的网络平台，服务通知消息携带访问应用服务器的PDU会话需要关联的切片标识(S-NSSAI＝B)。
本步骤中，服务通知消息中还可以携带UE信息和应用信息推送给可以给UE发送通知的网络平台。
步骤7.网络平台向UE发送应用触发消息。
其中，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
步骤8.UE检查该会话信息是否已经建有PDU会话。
另外，在本步骤的判断结果为该会话信息已经建有PDU会话时，执行步骤8，在本步骤的判断结果为该会话信息未建有PDU会话时，执行步骤9。
步骤9.通过该PDU会话访问应用服务器。
步骤10.根据网络实体的指示发起PDU会话新建立流程，并通过该流程新建的PDU会话访问应用服务器。
本实施方式中，由AF发起PDU会话新建流程，且在AF发起PDU会话新建流程的过程中，通过网络平台(例如：短消息服务中心(Short Message Service Center，SMSC))向UE发送基于会话信息新建PDU会话的指示，并由UE自行检查是否已经存在基于该会话信息的PDU会话，若果有，则不需要新建PDU会话，如果没有，则基于该会话信息新建PDU会话。
请参阅图8，是本公开实施例提供的一种终端的结构示意图，如图8所示，该终端800包括：
第一收发模块801，用于建立PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
进一步的，所述指示消息还包含数据网络名称DNN。
进一步的，所述指示消息包括如下消息中的至少一个：
对所述PDU会话进行会话管理的SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
对所述PDU会话进行会话管理的SMF发送的会话释放命令消息，所述 会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
进一步的，所述指示消息为应用触发消息的情况下，终端800还包括：
建立模块，用于在没有建立与所述切片标识有关的会话的情况下，发起PDU会话建立流程，建立用于访问所述应用服务器的，与所述切片标识相关的PDU会话；
或者
访问模块，用于在已经建立与所述切片标识有关的会话的情况下，使用与所述切片标识相关的PDU会话访问所述应用服务器。
本公开实施例的终端，能够接收网络侧设备发送的指示消息，以根据网络侧设备指定的切片标识确定会话对应的切片信息，从而基于此进行会话修改、重建或者发起会话建立流程，从而避免了终端在建立PDU会话时需要选择该会话对应的切片，存在的选择切片的过程难以实现的问题。
请参阅图9，是本公开实施例提供的一种网络侧设备的结构示意图，如图9所示，该网络侧设备900包括：
第一发送模块901，用于在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
进一步的，所述指示消息还包含数据网络名称DNN。
进一步的，所述网络侧设备为网络平台或对所述PDU会话进行会话管理的SMF。
进一步的，所述指示消息包括如下消息中的至少一个：
所述SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
所述SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
所述网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
进一步的，所述网络侧设备为所述SMF，所述SMF不支持所述切片标识的情况下，所述指示消息为所述会话释放命令消息；
或者
所述网络侧设备为所述SMF，所述SMF支持所述切片标识的情况下，所述指示消息为所述会话修改命令消息或会话释放命令消息。
进一步的，所述网络侧设备为所述SMF，网络侧设备900还包括第二接收模块，用于接收PCF发送的第一会话控制消息，所述第一会话控制消息携带根据所述路由选择策略确定的切片标识。
进一步的，所述网络侧设备为所述SMF，网络侧设备900还包括：
第三接收模块，用于接收NEF或AF发送的第一服务请求，所述第一服务请求携带应用相关信息和/或用户相关信息；
第二发送模块，用于根据所述第一服务请求检测到终端访问了所述应用后，向PCF发送第一请求消息，所述第一请求消息用于指示所述PCF查询路由选择策略；
第四接收模块，用于接收PCF发送的响应消息，所述响应消息携带根据所述路由选择策略确定的所述切片标识。
进一步的，所述响应消息还包含数据网络名称DNN。
进一步的，所述应用相关信息包括：所述应用的地址和/或所述应用的标识；
所述用户相关信息包括：所述用户的地址和/或所述用户的标识。
进一步的，所述响应消息为第二会话控制消息。
进一步的，所述网络侧设备为网络平台，网络侧设备900还包括：
第五接收模块，用于接收AF或NEF发送的服务消息，所述服务消息携带访问应用服务器的PDU会话需要关联的切片标识。
进一步的，所述服务消息还包括DNN。
本公开实施例的网络侧设备，能够向终端发送指示消息，以指示对PDU会话进行修改、重建或者发起会话建立流程，以使终端根据该指示消息进行 相应的会话更新，从而避免了终端在建立PDU会话时需要选择该会话对应的切片，存在的选择切片的过程难以实现的问题。
请参阅图10，是本公开实施例提供的一种PCF实体的结构示意图，如图10所示，该PCF实体1000包括：
查询模块1001，用于查询路由选择策略；
确定模块1002，还用于根据所述路由选择策略确定切片标识；
第三发送模块1003，用于发送所述切片标识。
进一步的，所述切片标识用于终端对建立的PDU会话进行修改、重建，或发起PDU会话建立流程。
进一步的，所述查询路由选择策略之前，还包括：
第四接收模块，用于接收SMF、AF或NEF发送的请求消息，所述请求消息携带用于查询所述路由选择策略的应用相关信息和/或用户相关信息；
所述第三发送模块1003具体用于：
向SMF发送根据所述路由选择策略确定的切片标识；
或
向NEF或AF发送根据所述路由选择策略确定的切片标识。
进一步的，PCF实体还包括：
第四发送模块，用于在根据所述路由选择策略确定切片标识后，还发送数据网络名称DNN。
本公开实施例的PCF实体1000，能够基于终端建立的PDU会话对应的查询参数确定所述PDU会话需要关联的切片标识，从而避免了终端在建立PDU会话时需要选择该会话对应的切片，存在的选择切片的过程难以实现的问题。
参见图11，本公开实施例还提供了一种实体，包括总线1101、收发机1102、天线1103、总线接口1104、处理器1105和存储器1106。
在本申请一个实施例中，所述实体为网络侧设备，所述实体包括处理器1105和收发机1102；
收发机1102，用于在终端建立PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标 识对所述PDU会话进行修改、重建释放所述PDU会话，或发起PDU会话建立流程。
进一步的，在PDU会话的DNN数据网络名称需要修改时，所述指示消息还包含数据网络名称DNN。
进一步的，所述网络侧设备为网络平台或对所述PDU会话进行会话管理的SMF。
进一步的，所述指示消息包括如下消息中的至少一个：
所述SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
所述SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
所述网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
进一步的，所述网络侧设备为所述SMF，所述SMF不支持所述切片标识的情况下，所述指示消息为所述会话释放命令消息；
或者
所述网络侧设备为所述SMF，所述SMF支持所述切片标识的情况下，所述指示消息为所述会话修改命令消息或会话释放命令消息。
进一步的，所述网络侧设备为所述SMF，收发机1102在执行发送指示消息到终端之前，还用于：
接收PCF发送的第一会话控制消息，所述第一会话控制消息携带根据所述路由选择策略确定的与所述PDU会话对应的切片标识。
进一步的，所述网络侧设备为所述SMF，收发机1102在执行发送指示消息到终端之前，还用于：
接收NEF或AF发送的第一服务请求，所述第一服务请求携带应用相关信息和/或用户相关信息；
根据所述第一服务请求检测到终端访问了所述应用后，向PCF发送第一请求消息，所述第一请求消息用于指示所述PCF查询路由选择策略；
接收PCF发送的响应消息，所述响应消息携带根据所述路由选择策略确定的切片标识。
进一步的，所述响应消息还包含DNN。
进一步的，所述应用相关信息包括：所述应用的地址和/或所述应用的标识；所述用户相关信息包括：所述用户的地址和/或所述用户的标识。
进一步的，所述响应消息为第二会话控制消息。
进一步的，所述网络侧设备为网络平台，收发机1102在执行发送指示消息到终端之前，还用于：
接收AF或NEF发送的服务消息，所述服务消息携带访问应用服务器的PDU会话需要关联的切片标识。
进一步的，所述服务消息还包括DNN。
本实施方式中，实体能够实现图6所示方法实施例中网络侧设备实现的各个过程，为避免重复，这里不再赘述。
本实施例的实体，能够在终端建立PDU会话之后，指示终端进行会话更新，以使终端更具该实体的指示进行会话修改、重建或者发起会话更新流程，从而避免了终端在建立PDU会话时需要选择该会话对应的切片，存在的选择切片的过程难以实现的问题。
在本申请一个实施例中，所述实体为PCF实体，所述实体包括处理器1105和收发机1102；
所述处理器1005，用于查询路由选择策略；
所述处理器1005，还用于根据所述路由选择策略确定切片标识；
所述收发机1002，用于发送所述切片标识。
进一步的，所述切片标识用于终端对建立的PDU会话进行修改、重建，或发起PDU会话建立流程。
进一步的，在所述查询路由选择策略之前：
所述收发机1002，还用于接收SMF、AF或NEF发送的请求消息，所述请求消息携带用于查询所述路由选择策略的应用相关信息和/或用户相关信息；
所述收发机1002执行的所述发送所述切片标识，具体为：
向SMF发送根据所述路由选择策略确定的切片标识；
或
向NEF或AF发送根据所述路由选择策略确定的切片标识。
进一步的，所述收发机1102，还用于：
在根据所述路由选择策略确定切片标识后，还发送DNN。
本实施方式中，实体能够实现图7所示方法实施例中PCF实现的各个过程，为避免重复，这里不再赘述。
本实施例的实体，能够在终端建立PDU会话之后，接收到的会话查询请求确定终端建立的PDU会话需要关联的切片标识，后续可以通过网络侧告知终端进行会话修改、重建或者发起会话更新流程，以实现将PDU会话更新至与所述切片标识相关，从而避免了终端在建立PDU会话时需要选择该会话对应的切片，存在的选择切片的过程难以实现的问题。
在图11中，总线架构(用总线1101来代表)，总线1101可以包括任意数量的互联的总线和桥，总线1101将包括由处理器1105代表的一个或多个处理器和存储器1106代表的存储器的各种电路链接在一起。总线1101还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1104在总线1101和收发机1102之间提供接口。收发机1102可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1105处理的数据通过天线1103在无线介质上进行传输，进一步，天线1103还接收数据并将数据传送给处理器1105。
处理器1105负责管理总线1101和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器1106可以被用于存储处理器1105在执行操作时所使用的数据。
可选的，处理器1105可以是中央处理器(central processing unit，CPU)、ASIC、FPGA或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)。
可选的，本公开实施例还提供一种终端，包括处理器1105，存储器1106， 存储在存储器1106上并可在所述处理器1105上运行的计算机程序，该计算机程序被处理器105执行时实现上述图2所示会话更新方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述图2、图6或图7所示的会话更新方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接， 可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本公开各个实施例所述的方法。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求 所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。

Claims (30)

  1. 一种会话更新方法，用于终端，包括：
    建立协议数据单元PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
  2. 根据权利要求1所述的会话更新方法，其中，所述指示消息还包含数据网络名称DNN。
  3. 根据权利要求1所述的会话更新方法，其中，所述指示消息包括如下消息中的至少一个：
    对所述PDU会话进行会话管理的会话管理功能实体SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包括的切片标识；
    对所述PDU会话进行会话管理的SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
    网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
  4. 根据权利要求3所述的会话更新方法，其中，所述指示消息为应用触发消息的情况下，所述方法还包括：
    在没有建立与所述切片标识有关的会话的情况下，发起PDU会话建立流程，建立用于访问所述应用服务器的，与所述切片标识相关的PDU会话；
    或者
    在已经建立与所述切片标识有关的会话的情况下，使用与所述切片标识相关的PDU会话访问所述应用服务器。
  5. 一种会话更新方法，用于网络侧设备，包括：
    在终端建立协议数据单元PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建释放所述PDU会话，或发起PDU会话建立流程。
  6. 根据权利要求5所述的会话更新方法，其中，所述指示消息还包含数据网络名称DNN。
  7. 根据权利要求5所述的会话更新方法，其中，所述网络侧设备为网络平台或对所述PDU会话进行会话管理的会话管理功能实体SMF。
  8. 根据权利要求7所述的会话更新方法，其中，所述指示消息包括如下消息中的至少一个：
    所述SMF发送的会话修改命令消息，所述会话修改命令消息用于指示所述终端修改所述PDU会话相关的切片标识为所述会话修改命令消息包含的切片标识；
    所述SMF发送的会话释放命令消息，所述会话释放命令消息用于指示所述终端释放会话，并根据所述切片标识重建所述会话；
    所述网络平台发送的应用触发消息，所述应用触发消息用于指示所述终端通过与所述切片标识相关的PDU会话访问应用服务器。
  9. 根据权利要求7所述的会话更新方法，其中：
    所述网络侧设备为所述SMF，所述SMF不支持所述切片标识的情况下，所述指示消息为所述会话释放命令消息；
    或者
    所述网络侧设备为所述SMF，所述SMF支持所述切片标识的情况下，所述指示消息为所述会话修改命令消息或会话释放命令消息。
  10. 根据权利要求7所述的会话更新方法，其中，所述网络侧设备为所述SMF，发送指示消息到终端之前，所述方法还包括：
    接收策略控制功能实体PCF发送的第一会话控制消息，所述第一会话控制消息携带根据路由选择策略确定的切片标识。
  11. 根据权利要求7所述的会话更新方法，其中，所述网络侧设备为SMF，发送指示消息到终端之前，所述方法还包括：
    接收网络开放功能实体NEF或应用功能实体AF发送的第一服务请求，所述第一服务请求携带应用相关信息和/或用户相关信息；
    根据所述第一服务请求检测到终端访问了所述应用后，向PCF发送第一请求消息，所述第一请求消息用于指示所述PCF查询路由选择策略；
    接收PCF发送的响应消息，所述响应消息携带根据所述路由选择策略确定的切片标识。
  12. 根据权利要求11所述的会话更新方法，其中，所述响应消息还包含数据网络名称DNN。
  13. 根据权利要求11所述的会话更新方法，其中：
    所述应用相关信息包括：所述应用的地址和/或所述应用的标识；
    所述用户相关信息包括：所述用户的地址和/或所述用户的标识。
  14. 根据权利要求11所述的会话更新方法，其中，所述响应消息为第二会话控制消息。
  15. 根据权利要求7所述的会话更新方法，其中，所述网络侧设备为网络平台，发送指示消息到终端之前，所述方法还包括：
    接收AF或NEF发送的服务消息，所述服务消息携带访问应用服务器的PDU会话需要关联的切片标识。
  16. 根据权利要求15所述的会话更新方法，其中，所述服务消息还包括DNN。
  17. 一种会话更新方法，用于策略控制功能实体PCF，包括：
    查询路由选择策略；
    根据所述路由选择策略确定切片标识；
    发送所述切片标识。
  18. 根据权利要求17所述的会话更新方法，其中，所述切片标识用于终端对建立的PDU会话进行修改、重建，或发起PDU会话建立流程。
  19. 根据权利要求17所述的会话更新方法，其中，所述查询路由选择策略之前，所述方法还包括：
    接收SMF、AF或NEF发送的请求消息，所述请求消息携带用于查询所述路由选择策略的应用相关信息和/或用户相关信息；
    所述发送所述切片标识具体为：
    向SMF发送根据所述路由选择策略确定的切片标识；
    或
    向NEF或AF发送根据所述路由选择策略确定的切片标识。
  20. 根据权利要求17所述的会话更新方法，其中，在根据所述路由选择策略确定切片标识后，还发送数据网络名称DNN。
  21. 一种终端，包括：处理器和收发机；
    所述收发机，用于建立协议数据单元PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
  22. 一种网络侧设备，包括：处理器和收发机；
    所述收发机，用于在终端建立协议数据单元PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
  23. 一种策略控制功能实体PCF，包括：处理器和收发机；
    所述处理器，用于查询路由选择策略；
    所述处理器，还用于根据所述路由选择策略确定切片标识；
    所述收发机，用于发送所述切片标识。
  24. 一种终端，包括：
    接收模块，用于建立协议数据单元PDU会话后，接收网络侧设备发送的指示消息，所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
  25. 一种网络侧设备，包括：
    发送模块，用于在终端建立协议数据单元PDU会话后，发送指示消息到终端；所述指示消息包含切片标识，所述指示消息用于指示所述终端根据所述切片标识对所述PDU会话进行修改、重建，或发起PDU会话建立流程。
  26. 一种策略控制功能实体PCF，包括：
    查询模块，用于查询路由选择策略；
    确定模块，还用于根据所述路由选择策略确定切片标识；
    发送模块，用于发送所述切片标识。
  27. 一种终端，包括处理器、存储器及存储在所述存储器上并可在所述 处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至4中任一项所述的会话更新方法中的步骤。
  28. 一种网络侧设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求5至16中任一项所述的会话更新方法中的步骤。
  29. 一种PCF，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求17至20中任一项所述的会话更新方法中的步骤。
  30. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至4中任一项所述的会话更新方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如权利要求5至16中任一项所述的会话更新方法中的步骤，或者，所述计算机程序被所述处理器执行时实现如权利要求17至20中任一项所述的会话更新方法中的步骤。
PCT/CN2021/112074 2020-08-13 2021-08-11 会话更新方法、终端和网络侧设备 Ceased WO2022033521A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21855572.0A EP4192077B1 (en) 2020-08-13 2021-08-11 Session update method, terminal, and network-side device
JP2023510478A JP7641359B2 (ja) 2020-08-13 2021-08-11 セッション更新方法、端末及びネットワーク側機器
US18/041,405 US20230300912A1 (en) 2020-08-13 2021-08-11 Session update method, terminal, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010815092.4A CN114080056B (zh) 2020-08-13 2020-08-13 一种会话更新方法、终端和网络侧设备
CN202010815092.4 2020-08-13

Publications (1)

Publication Number Publication Date
WO2022033521A1 true WO2022033521A1 (zh) 2022-02-17

Family

ID=80246980

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/112074 Ceased WO2022033521A1 (zh) 2020-08-13 2021-08-11 会话更新方法、终端和网络侧设备

Country Status (5)

Country Link
US (1) US20230300912A1 (zh)
EP (1) EP4192077B1 (zh)
JP (1) JP7641359B2 (zh)
CN (1) CN114080056B (zh)
WO (1) WO2022033521A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023170636A1 (en) * 2022-03-11 2023-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Network control of slice use
CN116828546A (zh) * 2022-03-22 2023-09-29 维沃移动通信有限公司 非3gpp设备的会话通道建立方法、装置及设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023179595A1 (zh) * 2022-03-22 2023-09-28 维沃移动通信有限公司 非3gpp设备的会话通道建立方法、装置及设备
CN118102235A (zh) * 2022-11-28 2024-05-28 上海大唐移动通信设备有限公司 数据传输方法及装置
CN118785523A (zh) * 2023-04-07 2024-10-15 中国移动通信有限公司研究院 信息交互方法、装置、设备及存储介质
CN118945759A (zh) * 2023-05-12 2024-11-12 维沃移动通信有限公司 数据流的传输方法、路由策略的更新方法及用户设备

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580360A (zh) * 2016-07-04 2018-01-12 中国移动通信有限公司研究院 一种网络切片选择的方法、设备及网络架构
US20180324577A1 (en) * 2017-05-08 2018-11-08 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
CN109788491A (zh) * 2017-11-10 2019-05-21 中国电信股份有限公司 用于管理切片迁移的方法、装置和系统
CN109964468A (zh) * 2016-11-14 2019-07-02 华为技术有限公司 会话处理方法、装置和系统
CN110392448A (zh) * 2018-04-18 2019-10-29 华为技术有限公司 一种会话重建方法、装置和系统
CN110474840A (zh) * 2018-05-09 2019-11-19 华为技术有限公司 数据传输方法、装置和可读存储介质
CN112152926A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种管理应用的网络切片的方法及装置
CN112543486A (zh) * 2019-09-23 2021-03-23 华为技术有限公司 网络切片选择的方法、设备及系统
CN113015162A (zh) * 2021-02-24 2021-06-22 中国联合网络通信集团有限公司 协议数据单元会话策略建立方法、装置、认证单元及网元
CN113098726A (zh) * 2021-06-10 2021-07-09 深圳艾灵网络有限公司 网络切片方法、设备及存储介质

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019208089A (ja) * 2016-10-07 2019-12-05 シャープ株式会社 端末装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）、ＣＰＦ（Ｃｏｎｔｒｏｌ Ｐｌａｎｅ Ｆｕｎｃｔｉｏｎ）、及び通信制御方法
KR102620149B1 (ko) * 2017-05-08 2024-01-03 모토로라 모빌리티 엘엘씨 데이터 접속을 재구성하기 위한 방법들 및 장치들
JP2020520172A (ja) * 2017-05-09 2020-07-02 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ネットワークスライス選択ポリシー更新方法および装置
CN109548099B (zh) * 2017-08-15 2021-02-05 华为技术有限公司 通信方法、装置和系统
KR102477765B1 (ko) * 2017-10-20 2022-12-14 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 데이터 전송 방법, 단말 기기 및 네트워크 기기
CN110120879B (zh) * 2018-02-06 2020-12-01 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
US10506506B2 (en) * 2018-04-30 2019-12-10 Ofinno, Llc 5G policy control for restricted local operator services
CN113207095B (zh) * 2018-10-09 2022-08-02 Oppo广东移动通信有限公司 执行群组通信的装置和方法
CN111436081B (zh) * 2019-03-06 2023-06-30 维沃移动通信有限公司 数据传送的保障方法及通信设备

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580360A (zh) * 2016-07-04 2018-01-12 中国移动通信有限公司研究院 一种网络切片选择的方法、设备及网络架构
CN109964468A (zh) * 2016-11-14 2019-07-02 华为技术有限公司 会话处理方法、装置和系统
US20180324577A1 (en) * 2017-05-08 2018-11-08 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
CN109788491A (zh) * 2017-11-10 2019-05-21 中国电信股份有限公司 用于管理切片迁移的方法、装置和系统
CN110392448A (zh) * 2018-04-18 2019-10-29 华为技术有限公司 一种会话重建方法、装置和系统
CN110474840A (zh) * 2018-05-09 2019-11-19 华为技术有限公司 数据传输方法、装置和可读存储介质
CN112152926A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种管理应用的网络切片的方法及装置
CN112543486A (zh) * 2019-09-23 2021-03-23 华为技术有限公司 网络切片选择的方法、设备及系统
CN113015162A (zh) * 2021-02-24 2021-06-22 中国联合网络通信集团有限公司 协议数据单元会话策略建立方法、装置、认证单元及网元
CN113098726A (zh) * 2021-06-10 2021-07-09 深圳艾灵网络有限公司 网络切片方法、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4192077A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023170636A1 (en) * 2022-03-11 2023-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Network control of slice use
CN116828546A (zh) * 2022-03-22 2023-09-29 维沃移动通信有限公司 非3gpp设备的会话通道建立方法、装置及设备

Also Published As

Publication number Publication date
JP2023537154A (ja) 2023-08-30
US20230300912A1 (en) 2023-09-21
JP7641359B2 (ja) 2025-03-06
EP4192077A4 (en) 2024-09-04
CN114080056B (zh) 2024-08-09
EP4192077A1 (en) 2023-06-07
CN114080056A (zh) 2022-02-22
EP4192077B1 (en) 2026-02-18

Similar Documents

Publication Publication Date Title
WO2022033521A1 (zh) 会话更新方法、终端和网络侧设备
EP4191959B1 (en) Method and system for ensuring service level agreement of an application
US12034611B2 (en) NF service consumer restart detection using direct signaling between NFs
AU2018366776B2 (en) Session establishing method and device
TWI654859B (zh) 用於點對點應用之網路輔助裝置對裝置搜尋
JP7125041B2 (ja) 通信方法及び通信装置
CN111869177A (zh) 一种ue策略的更新方法及装置、计算机存储介质
US12549934B2 (en) Method for determining policy control network element, apparatus, and system
CN111698755A (zh) 基于ursp规则的应用数据路由方法及用户设备
US11323502B2 (en) Transport method selection for delivery of server notifications
JP2011034567A (ja) 端末装置の設定
US11638138B2 (en) Device-to-device content providing method
TWI854211B (zh) 一種用於傳輸上下文的方法和通信裝置
US12445821B2 (en) Application relocation method and apparatus
WO2015110080A1 (zh) 一种数据处理的方法、装置及系统
CN116419268A (zh) Ursp规则的监控和上报方法、装置、终端及网元
EP3770784B1 (en) Api topology hiding method, device and system
JP2026012707A (ja) セッション復元のための方法及び装置
EP4462850A1 (en) Method, device and system for requesting application function
HK40087332A (zh) 会话更新方法、终端和网络侧设备
CN112055307A (zh) 位置信息的上报、upf的重选方法、装置、设备及介质
WO2015172338A1 (zh) 一种接入点的选择方法及相关装置
EP4304250B1 (en) Communication network arrangement and method for providing a communication service
US20240406056A1 (en) System And Method To Reduce Network Function Interruptions In A Service-Based Architecture
WO2023241614A1 (zh) Ims服务获取方法、终端、网络侧设备及介质

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: 21855572

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023510478

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021855572

Country of ref document: EP

Effective date: 20230302

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2021855572

Country of ref document: EP