Data stream transmission method, routing policy update method, and user equipment
By updating the routing policy in the user equipment to match the replaced slice, the problem of abnormal data stream transmission after slice replacement is solved, and the normal transmission and stability of the data stream are achieved.
Patent Information
- Application Number
- PCT/CN2024/091123
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-06
- Publication Date
- 2024-11-21
AI Technical Summary
In 5G networks, the existing technology is difficult to effectively solve the problem of abnormal data stream transmission after slice replacement.
Receive messages carrying PDU session identification and slice information through the user device, update the routing policy to match the replaced slice, ensuring that the data flow is transmitted using the matching first slice in the target application, and avoiding the use of the second slice before the replacement.
The normal transmission of the data stream after slice replacement is achieved, avoiding data stream transmission exceptions, and ensuring the accuracy and stability of the data stream.
Smart Images

Figure CN2024091123_21112024_PF_FP_ABST
Abstract
Description
Data stream transmission method, routing strategy updating method and user equipment
[0001] Cross-references
[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on May 12, 2023, with application number 202310543108.4 and invention name “Data stream transmission method, routing strategy update method and user equipment”. The entire contents of the application are incorporated by reference into this application. Technical Field
[0003] The present application belongs to the field of communication technology, and specifically relates to a data stream transmission method, a routing strategy update method, and a user equipment. Background Art
[0004] In 5G networks, the logical functions of network resources are divided into several combinations, such as the combination of core network elements and wireless links. The network elements in a combination are limited to the same Public Land Mobile Network (PLMN) and include at least two parts: the access network and the core network. Each combination is called a slice. In order to identify these slices, an identifier (ID) is set for each slice, called Single Network Slice Selection Assistance Information (S-NSSAI). Each S-NSSAI contains a slice / service type (SST) and a slice differentiator (SD). Multiple S-NSSAIs are combined to form Network Slice Selection Assistance Information (NSSAI).
[0005] If a slice becomes unavailable or congested due to network changes, the network may replace the current slice with a replacement slice. Therefore, ensuring the normal transmission of data streams after a slice replacement is a technical issue that needs to be addressed.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide a data stream transmission method, a routing policy update method, and a user device, which can ensure the correct transmission of the data stream after the slice is replaced.
[0008] In a first aspect, a method for transmitting a data stream is provided, which is performed by a user equipment, the method comprising: a UE receiving a first message, wherein the information carried in the first message includes one of the following: a protocol data unit (PDU) session identifier and a first slice, a first slice, and a second slice; when the target route selection descriptor (RSD) matching the target application in the user equipment route selection policy (URSP) includes the second slice, the user equipment selects a PDU session matching the first slice to transmit the data stream of the target application.
[0009] According to a second aspect, a method for updating a routing policy is provided, which is executed by a user device, and the method includes: the user device receives a target user device routing policy sent by a third network element, wherein the target user device routing policy includes a replaced first slice; the user device uses the target user device routing policy to update a locally stored user device routing policy.
[0010] According to a third aspect, a method for updating a routing policy is provided, which is executed by a network-side device. The method includes: after learning that a first slice is used to replace a second slice, a first network element updates a user device routing policy based on the replaced second slice and the replaced first slice, wherein the updated target user device routing policy includes the first slice; and the first network element sends the updated target user device routing policy to a third network element.
[0011] In a fourth aspect, a data stream transmission device is provided, which includes: a receiving module for receiving a first message, wherein the information carried in the first message includes one of the following: a PDU session identifier and a first slice, a first slice and a second slice; a transmission module for selecting a PDU session matching the first slice to transmit the data stream of the target application when the target RSD matching the target application in the URSP includes the second slice.
[0012] In the fifth aspect, a routing policy update device is provided, which includes: a receiving module for receiving a target user equipment routing policy sent by a third network element, wherein the target user equipment routing policy includes a replaced first slice; an updating module for using the target user equipment routing policy to update a locally stored user equipment routing policy.
[0013] In the sixth aspect, a routing policy update device is provided, which includes: an update module for updating the user equipment routing policy based on the replaced second slice and the replaced first slice after learning that the first slice is used to replace the second slice, wherein the updated target user equipment routing policy includes the first slice; a sending module for sending the updated target user equipment routing policy to a third network element.
[0014] In the seventh aspect, a user device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
[0015] In the eighth aspect, a user device is provided, comprising a processor and a communication interface, wherein the communication interface is used to communicate with an external device, and the processor is used to implement the steps of the method described in the first aspect above, or to implement the steps of the method described in the second aspect above.
[0016] In the ninth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect are implemented.
[0017] In the tenth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to communicate with an external device, and the processor is used to implement the steps of the method described in the third aspect.
[0018] In the eleventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.
[0019] In the twelfth aspect, a wireless communication system is provided, including: a user device and a network side device, wherein the user device can be used to execute the steps of the method described in the first aspect or the steps of the method described in the second aspect, and the network side device can be used to execute the steps of the method described in the third aspect.
[0020] In the thirteenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.
[0021] In the fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.
[0022] In an embodiment of the present application, a user device receives a first message, and the information carried in the first message includes a protocol data unit PDU session identifier and a first slice, or in the case of a first slice and a second slice, when the user device subsequently matches a routing policy for a target application, if the target RSD that matches the target application in the locally stored URSP includes the second slice, the user device selects the PDU session that matches the first slice to transmit the data stream of the target application. Through the technical solution provided in the embodiment of the present application, it is possible to use the PDU session that matches the first slice after the slice replacement to transmit the data stream of the target application after the slice replacement occurs, avoiding the use of the PDU session that matches the second slice before the replacement to transmit the data stream of the target application, thereby preserving the normal transmission of the transmission data stream. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] FIG1 shows a block diagram of a wireless communication system to which embodiments of the present application may be applied;
[0024] FIG2 is a schematic diagram showing a flow chart of a data stream transmission method provided in an embodiment of the present application;
[0025] FIG3 is a schematic diagram showing a flow chart of a method for updating a routing policy provided in an embodiment of the present application;
[0026] FIG4 is a schematic diagram showing a flow chart of another method for updating a routing policy provided in an embodiment of the present application;
[0027] FIG5 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0028] FIG6 shows a schematic flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0029] FIG7 shows a schematic flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0030] FIG8 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0031] FIG9 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0032] FIG10 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0033] FIG11 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0034] FIG12 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application;
[0035] FIG13 is a schematic diagram showing a data stream transmission device provided in an embodiment of the present application;
[0036] FIG14 is a schematic diagram showing a routing policy updating device according to an embodiment of the present application;
[0037] FIG15 is a schematic diagram showing another apparatus for updating routing policies according to an embodiment of the present application;
[0038] FIG16 shows a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0039] FIG17 is a schematic diagram showing a hardware structure of a user equipment provided in an embodiment of the present application;
[0040] FIG18 shows a schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0041] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.
[0042] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0043] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.
[0044] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.
[0045] FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal (also referred to as user equipment (UE)) 11 and a network-side device 12. The user equipment 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), a teller machine (ATM), or a self-service kiosk, etc., or other user-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be referred to as a vehicle-mounted user device, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the user device 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0046] The core network device may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application server discovery function (EASDF), unified data management (UDM), unified data storage (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BNSF), network access function (UE ... Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.
[0047] First, the slices, user equipment policy (UE policy), session management policy (SM policy), and slice replacement involved in this application are introduced.
[0048] Slices in user equipment (UE) and networks include the following types:
[0049] (1) Requested Network Slice Selection Assistance Information (NSSAI): This is carried by the UE in the Registration Request message. When the UE registers on a Public Land Mobile Network (PLMN), it informs the network which slices of the current PLMN the UE wishes to request services on.
[0050] (2) Allowed NSSAI: This is configured on the network side and can be sent to the UE via a registration accept message or a configuration update command message. After the UE successfully registers in the current PLMN, the slices of the current PLMN that are allowed to be used by the UE's services are indicated by the Allowed NSSAI, for example, allowing the terminal to establish a Protocol Data Unit (PDU) session in these slices.
[0051] (3) Configured NSSAI: This is configured by the network side. It can be sent to the UE via a registration accept message or a configuration update command message. Unlike the Allowed NSSAI, the slices in the Configured NSSAI cannot be guaranteed to be used directly by the UE. The UE still needs to carry it in the Requested NSSAI to ask the network whether it can become the Allowed NSSAI.
[0052] (4) Default configured NSSAI: This is configured for the UE by the Unified Data Management (UDM) of the Home Public Land Mobile Network (HPLMN). It is generally configured within the UE but can also be modified via a configuration update command message. Its purpose is to allow the UE to use the default configured NSSAI to request registration when the serving network does not provide a configured NSSAI to the UE.
[0053] (5) Subscribed NSSAI: This is the slice that exists in the UDM after the UE joins the network. It is the slice that the UE has subscribed to. If the slice is not in this Subscribed NSSAI, the network cannot provide the service of the slice to the UE.
[0054] (6) Default NSSAI: One or more S-NSSAIs among multiple Subscribed S-NSSAIs are marked as default, also known as Default Subscribed S-NSSAI.
[0055] (7) Pending NSSAI: Some slices require network slice-specific authentication and authorization (NSSAA) on the network side. When the UE requests this type of slice, the network will authenticate and authorize it. Before the result is determined, the slice is called pending NSSAI.
[0056] UE policy can be divided into UE Route Selection Policy (URSP), Access Network Discovery & Selection policy (ANDSP), Vehicle to everything policy (V2X policy) and Proximity based Service policy (ProSeP). URSP can contain the following three items: (a) Rule precedence, which indicates the priority of URSP; (b) Traffic descriptor, which describes the application traffic; (c) List of Route selection descriptors (RSD), which describes the routing to PDU. UE uses URSP to determine whether an application can be associated with an established PDU session or trigger the establishment of a new PDU session. URSP presents a set of association rules that can select a suitable PDU session for a data packet. Regarding ANDSP, the UE uses ANDSP to select non-3GPP (3rd Generation Partnership Project) accesses and the Non-3GPP Inter Working Function (N3IWF), a set of policies for non-3GPP accesses. Regarding V2X policy, this policy provides the UE with configuration parameters for V2X communication over the PC5 reference point, the Uu reference point, or both. Regarding ProSeP, this policy provides the UE with configuration parameters for ProSe direct discovery, ProSe direct communication, ProSe UE-to-network relay, and remote UE.
[0057] A URSP-type UE policy contains one or more URSPs, each of which contains the following three items:
[0058] 1. Rule precedence (indicates the priority of the URSP);
[0059] 2. Traffic descriptor (traffic description, description information for APP traffic);
[0060] 3. List of RSD (description of which PDU to route to).
[0061] The list of RSD information may include one or more match PDU descriptions. For example, when an app's traffic meets the description in the traffic descriptor:
[0062] 1. Rule Precedence = 1
[0063] 2.Traffic Descriptor:Application descriptor=App1
[0064] 3.RSD:
[0065] A.Route Selection Descriptor Precedence=1
[0066] B.Network Slice Selection:S-NSSAI-a
[0067] C.SSC Mode Selection:SSC Mode 3
[0068] D.DNN Selection:internet
[0069] E.Access Type preference:3GPP access
[0070] Then the above RSD including A, B, C, D and E is the RSS matched by the APP, and the APP traffic is routed to the PDU session described (i.e. associated) by the RSD, and the corresponding traffic can be transmitted through the PDU session (using S-NSSAI-a, SSC mode 3, and DNN is the PDU session of 3GPP access to the internet). Among them, S-NSSAI-a is the slice identifier associated with the PDU session. Furthermore, if the current PDU session exists, the PDU session is used directly. If it is not established, an attempt is made to establish it. If the establishment fails, the content of the next RSD will be matched. The slices here belong to allowed NSSAI.
[0071] Regarding the SM policy, during the PDU session establishment process, the SMF selects the PCF serving the PDU session, then requests the PCF to establish an SM policy for the PDU session. It then initiates the Npcf_SMPolicyControl_Create Service request to the PCF to establish an SM Policy Association and download the corresponding session rules, PCC rules, and so on. Subsequently, the SMF performs operations such as packet detection, QoS flow binding, and mapping based on the information obtained from the PCF. In the Npcf_SMPolicyControl_Create Service, the SMF must provide the following parameters: Subscription Permanent Identifier (SUPI), Permanent Equipment Identifier (PEI) (in the case of an emergency PDU session without SUPI), PDU Session ID, Data Network Name (DNN), S-NSSAI, and Radio Access Technology (RAT) type, which includes slice information.
[0072] If a slice is no longer available or congested due to network changes, the network will perform a slice replacement, as follows:
[0073] (1) If the Network Slice Selection Function (NSSF) detects that the S-NSSAI becomes unavailable or congested (e.g., based on Operations Administration and Maintenance (OAM) or Network Data Analytics Function (NWDAF) analysis output), it sends a network slice availability notification of the S-NSSAI to the AMF. The notification may include an alternative S-NSSAI, which the AMF may use to replace the S-NSSAI. When the S-NSSAI becomes available again, the NSSF notifies the AMF.
[0074] (2) If the PCF detects that the S-NSSAI becomes unavailable or congested for the UE (e.g., based on OAM or NWDAF analysis output), it sends an access and mobility related policy notification to the AMF. The notification may include an alternative S-NSSAI, which the AMF may use to replace the S-NSSAI. When the S-NSSAI becomes available to the UE again, the PCF notifies the AMF.
[0075] (3) When the S-NSSAI becomes unavailable or congested (and when the S-NSSAI becomes available again), OAM sends a notification to the AMF and provides the AMF with an alternative S-NSSAI.
[0076] During the PDU session establishment, modification, and release process, both the terminal and network sides will store the PDU session-related context. A PDU session identifier represents a unique PDU session, and the slice information associated with the PDU session is bound to one PDU session. Therefore, on both the terminal and network sides, when only the PDU session identifier is received, both sides can find the associated slice; conversely, when only the slice identifier is received, both sides can find the associated PDU session.
[0077] After the slice is replaced, if the UE policy of the UE or the SM policy of the SMF is not updated, data stream transmission abnormalities may occur. To address this problem, an embodiment of the present application provides a data stream transmission method, a routing policy update method, and a user device.
[0078] The data stream transmission method, routing policy update method and user equipment provided by the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.
[0079] FIG2 is a flow chart showing a method for transmitting a data stream according to an embodiment of the present application, which can be executed by a UE. Referring to FIG2 , the method may include the following steps:
[0080] Step 202: The UE receives a first message, wherein the information carried in the first message includes one of the following: a PDU session identifier and an identifier of the replaced first slice, an identifier of the first slice, and an identifier of the second slice;
[0081] The first message may be sent by the second network element or the third network element.
[0082] For example, the SMF (i.e., the second network element) sends a PDU session modification message or a PDU session release message to the user equipment. The information carried in the message may include the PDU session identifier and the identifier of the first slice, indicating that the second slice currently associated with the PDU session identifier is replaced with the first slice. Through this message, the UE can know that a slice replacement has occurred on the network side, that is, the first slice is used to replace the second slice.
[0083] For another example, the AMF sends updated replacement slice information to the user equipment through the registration process or the user equipment configuration update (UE configuration update, UCU) process. The message includes the identifier of the first slice and the identifier of the second slice. Through this message, the UE can know that a slice replacement has occurred on the network side, that is, the first slice is used to replace the second slice.
[0084] It should be noted that in an embodiment of the present application, the identifier of the first slice or the identifier of the second slice carried in the message may be the single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) corresponding to the first slice or the second slice. For the convenience of description, it is referred to as the identifier of the first slice or the identifier of the second slice in the embodiment of the present application, and the same is true below.
[0085] Step 204: When the target RSD matching the target application in the URSP includes the identifier of the second slice, the user equipment selects the PDU session associated with the first slice to transmit the data stream of the target application, wherein the PDU session corresponding to the PDU session identifier is associated with the second slice.
[0086] Among them, the UE policy in the embodiment of the present application is not limited to URSP, and can also be ANDSP, V2X Policy, ProSeP, etc.
[0087] In an embodiment of the present application, after the UE learns that the second slice is replaced with the first slice, when subsequently matching the routing policy for the target application, if the target RSD matching the target application in the locally stored URSP includes the identifier of the second slice, the UE selects the PDU session associated with the first slice to transmit the data stream of the target application. For example, in the case where a PDU session associated with the first slice has been established, the UE selects the PDU session to transmit the data stream of the target application. If the PDU session associated with the first slice has not been established, the UE requests to establish a PDU session associated with the first slice and uses the established PDU session to transmit the data stream of the target application. This can avoid the situation where the data stream transmission is abnormal due to the use of the PDU session associated with the replaced second slice to transmit the data stream of the target application.
[0088] In one implementation, the above step 204 may include: when a first condition is met, the user equipment selects a PDU session matching the first slice to transmit the data flow of the target application;
[0089] The first condition includes at least one of the following:
[0090] (1) The target traffic descriptor corresponding to the target RSD is a non-default traffic descriptor in the URSP;
[0091] (2) The user equipment does not have any non-3GPP access connection established;
[0092] (3) the user equipment does not establish a connection from the 5G proximity-based service layer 3 user equipment to the network relay user equipment;
[0093] (4) The user equipment does not establish a PDU session;
[0094] (5) The target RSD does not include a seamless non-3GPP offload indication;
[0095] (6) The target RSD does not include a 5G layer 3 user equipment to network relay offload indication.
[0096] In an embodiment of the present application, after the user equipment receives a message carrying a protocol data unit PDU session identifier and a first slice, or an identifier of the first slice and an identifier of the second slice, the user equipment selects a PDU session that matches the first slice to be replaced when the traffic description in the non-default URSP rule matches the application information, the user equipment has no established non-3GPP access, the user equipment has not established a connection from the third layer user equipment of the 5G proximity-based service to the network relay user equipment, the user equipment has not established a PDU session, or any combination of the above, the RSD does not include a seamless non-3GPP offload indication (non-seamless non-3GPP offload indication) or a 5G third layer user equipment to network relay offload indication (5G ProSe layer-3UE-to-network relay offload indication), and the RSD matching the target application in the URSP includes the replaced second slice. One of the conditions, to transmit the data flow of the target application.
[0097] In one implementation, the above-mentioned step 202 may include: the UE receives a first message sent by the second network element, wherein the information carried in the first message includes: the PDU session identifier and the identifier of the first slice. For example, the second network element may include an SMF, and the SMF may send a PDU session modification instruction message or a PDU session release instruction message to the UE after receiving the update and replacement slice information sent by the AMF. The PDU session modification instruction message or the PDU session release instruction message carries the PDU session identifier and the identifier of the first slice, indicating that the slice matching the PDU session corresponding to the PDU session identifier is replaced with the first slice.
[0098] In another implementation, the above-mentioned step 202 may include: the UE receiving a first message sent by a third network element, wherein the information carried in the first message includes: an identifier of the first slice and an identifier of the second slice. For example, the third network element may include an AMF, and after receiving the information about the replacement slice, the AMF may update the replacement slice information to the UE through a registration process or a UE configuration update process (UE configuration update process, UCU process), including the identifier of the old slice (i.e., the second slice) and the identifier of the new slice (i.e., the first slice).
[0099] FIG3 shows a flow chart of a method for updating a routing policy provided by an embodiment of the present application, which can be executed by a user equipment. Referring to FIG3 , the method can include the following steps.
[0100] Step 302: The user equipment receives a target user equipment routing policy sent by a third network element, wherein the target user equipment routing policy does not include an identifier of the replaced second slice;
[0101] The third network element may include an AMF. For example, the AMF may encapsulate the updated UE policy in a DL NAS TRANSPORT message and send it to the user equipment.
[0102] Step 304: The user equipment uses the target user equipment routing policy to update the locally stored user equipment routing policy.
[0103] In one implementation, the target user equipment routing policy does not include the identifier of the replaced second slice, thereby avoiding the UE from subsequently selecting a PDU session that matches the second slice.
[0104] For example, after the PCF triggers the replacement of the slice, the PCF first sends the replacement slice to the AMF, triggering the generation of a new UE policy. The PCF sends the updated UE policy to the AMF through the Npcf_UEPolicyControl_UpdateNotify message. The UE policy includes the replaced first slice but does not include the identifier of the replaced second slice. Then the AMF encapsulates the updated UE policy in the DL NAS TRANSPORT message and sends it to the user equipment. The user equipment actively updates the locally stored user equipment routing policy according to the target user equipment routing policy sent by the AMF, thereby realizing the update of the UE policy.
[0105] Alternatively, in the case where the slice replacement is not triggered by the PCF, after receiving the information about the replacement slice, the AMF updates the replacement slice information to the UE through the registration process or the UE configuration update process (UCU process), including the identifier of the old slice (i.e., the second slice) and the identifier of the new slice (i.e., the first slice). The UE replies with a registration acceptance message or a registration update completion message, indicating that the slice replacement has been completed. After receiving the UE's response in step 2, the AMF triggers the update of the UE policy to the PCF. The updated UE policy may include the user equipment routing policy association identifier (UE policy association ID) and the identifier of the new slice (i.e., the first slice), but does not include the identifier of the old slice, i.e., the second slice. For example, the user equipment routing policy association identifier and the new slice identifier can be sent to PCF by using the Npcf_UEPlocyControl_update message. PCF generates the updated UE policy and sends it to AMF through Npcf_UEPolicyControl_UpdateNotify. AMF encapsulates the updated UE policy in a DL NAS TRANSPORT message and sends it to the user equipment. The user equipment actively updates the locally stored user equipment routing policy based on the target user equipment routing policy sent by AMF, thereby realizing the update of the UE policy.
[0106] In one implementation, the update of the user equipment routing policy may also be initiated by the terminal. Therefore, in one implementation, before step 302, the method may further include the following steps:
[0107] Step 1: The user equipment receives a first message, wherein the information carried in the first message includes one of the following: a PDU session identifier and an identifier of the replaced first slice, an identifier of the first slice, and an identifier of the second slice; this step is the same as step 202 in Figure 2. For details, please refer to the above description of step 202, which will not be repeated here.
[0108] Step 2. When it is determined that the identifier of the slice in the RSD of at least one URSP rule in the locally stored URSP is the identifier of the first slice, the user device sends a third message to the third network element, wherein the third message carries user device status indication information, and the user device status indication information is used to instruct the network side to update the URSP rule indicated by the target UE policy selection identifier (UE Policy Section Identifier, UPSI).
[0109] In the above implementation, after receiving the first message, the UE checks the locally stored URSP. If the slice identifier in the RSD of at least one URSP rule in the URSP is the identifier of the first slice, the UE sends a third message to the third network element, thereby triggering a policy update process on the network side. In one implementation, the third message may be a UL NAS TRANSPORT message.
[0110] In the above implementation, the third message may further carry at least one of the following:
[0111] (1) an identifier of the first slice;
[0112] (2) The identifier of the second slice.
[0113] The identifier of the first slice carried in the third message may be all the replacement slice information in the first message, or may include identifiers of affected old slices in the URSP and information about related new slices.
[0114] In one implementation, the user equipment status indication information includes at least one of the following:
[0115] (1) a UPSI list, wherein the UPSI identification list includes at least one target UPSI, and the target UPSI is used to indicate one or more URSP rules;
[0116] (2) UE policy class Mark;
[0117] (3) User equipment operating system identifier (UE OS ID);
[0118] (4) at least one URSP rule, which can be used to indicate the URSP rule that needs to be updated;
[0119] (5) indication information, used to indicate that the URSP rules in the user equipment status indication information need to be updated;
[0120] (6) Identifier of the first slice; it can be the identifiers of all first slices in the first message, or it can be the identifier of the first slice corresponding to the affected second slice in the URSP.
[0121] (7) Identification of the second slice.
[0122] The difference between item (1) and item (5) is that in item (1), one UPSI may represent one or more URSP rules, while item (5) indicates that the URSP rules indicated by the user equipment status indication information need to be updated, for example, the URSP rules indicated in item (1).
[0123] Through the above method provided in the embodiment of the present application, the UE can obtain a user equipment routing policy that does not include the replaced second slice after replacing the slice on the network side, so that when the UE performs routing policy matching subsequently, the data stream will not be matched to the PDU session corresponding to the second slice, thereby ensuring the accuracy of session transmission.
[0124] FIG4 shows a flow chart of another method for updating routing policies provided by an embodiment of the present application, which may be executed by a first network element. Referring to FIG4 , the method may include the following steps.
[0125] Step 402: After learning that the second slice is replaced with the first slice, the first network element updates the user equipment routing policy based on the replaced second slice and the replaced first slice, wherein the updated target user equipment routing policy does not include the identifier of the second slice.
[0126] The first network element may include a PCF.
[0127] Step 404: The first network element sends the updated routing policy of the target user equipment to a third network element.
[0128] Among them, the third network element may include AMF.
[0129] In one implementation, the target user equipment routing policy does not include the replaced second slice to avoid the UE subsequently matching the data flow to the PDU session corresponding to the second slice.
[0130] In an embodiment of the present application, after a PCF-triggered slice replacement or a non-PCF-triggered slice replacement, and after it is learned that the first slice has replaced the second slice, the PCF updates the user equipment routing policy. In one case, the updated policy only updates the slice, and the updated target user equipment routing policy may include the first slice, but not the replaced second slice; in another case, the entire policy may be replaced, and the updated target user equipment routing policy does not include the replaced second slice; the update of the UE policy is implemented, so that the user equipment receives the updated UE policy to replace the original UE policy.
[0131] In one implementation, the learning to replace the second slice with the first slice in step 402 may include: the first network element determining to replace the second slice with the first slice, and notifying the third network element. That is, in this implementation, the first network element triggers the slice replacement and notifies the third network element of information about the replaced slice.
[0132] In one implementation, the learning that the first slice is used to replace the second slice in step 402 may include: the first network element receiving a second message sent by the third network element, where the second message carries at least one of the following:
[0133] (1) an identifier of the first slice;
[0134] (2) an identifier of the second slice;
[0135] (3) User equipment routing policy association identifier (UE policy association ID), wherein the UE policy association ID is used to instruct the first network element to determine the updated routing policy.
[0136] In the above implementation, when slice replacement is triggered by a non-first network element, the first network element can determine that slice replacement has occurred through the second message sent by the third network element, thereby updating the UE routing policy.
[0137] Among them, the above-mentioned second message can be a user equipment policy control update notification message, such as an Npcf_UEPolicyControl_update message. The first network element generates an updated UE policy based on the identifier of the first slice, the identifier of the second slice and at least one of the user equipment routing policy association identifiers carried by the second message, and then sends the updated UE policy to the third network element. The third network element then sends the updated UE policy to the user equipment, thereby realizing the update of the UE policy.
[0138] In an embodiment of the present application, after the first network element updates the user equipment routing policy, the first network element sends the updated target user equipment routing policy to the third network element through a user equipment policy control update notification message, such as an Npcf_UEPolicyControl_UpdateNotify message. At this time, the target user equipment routing policy has been updated. Optionally, the target user equipment routing policy includes the identifier of the first slice, but does not include the identifier of the second slice; or only requires not including the identifier of the second slice.
[0139] To illustrate in detail the routing policy update method provided in the embodiment of the present application, the following takes the first network element as PCF, the second network element as SMF, and the third network element as AMF as an example, and describes it in combination with several specific embodiments.
[0140] Figure 5 shows a flow chart of a method for updating routing policies according to an embodiment of the present application. In this embodiment, when the PCF triggers a slice replacement, the PCF does not update the URSP. When the UE matches the session locally, it matches the new slice. This is performed by the user equipment, the first network element, the second network element, and the third network element. The first network element may include the PCF, the second network element may include the SMF, and the third network element may include the AMF. The method of this embodiment includes the following steps:
[0141] Step 501: The first network element sends the replaced slice information and the replaced slice information (eg, slice identifier) to the third network element.
[0142] Among them, after PCF triggers the slice replacement, PCF needs to inform AMF of the replaced slice information and the replacement slice information.
[0143] Step 502a: The third network element updates the replacement slice information to the user equipment.
[0144] For example, the replacement slice information, including the old slice and the new slice, is updated to the UE through the registration process or the UE configuration update process (UCU process). The UE replies with a registration acceptance message or a registration update completion message, indicating that the slice replacement has been completed.
[0145] Step 502b: The third network element sends updated replacement slice information to the second network element.
[0146] If AMF finds that the old slice in the replacement slice is associated with a PDU session, AMF updates the replacement slice information to SMF.
[0147] It should be noted that there is no temporal order between the above steps 502a and 502b.
[0148] Step 503: The second network element sends a first message to the user equipment.
[0149] For example, the SMF sends a PDU session modification instruction message or a PDU session release instruction message to the terminal, which carries the PDU session ID and replacement slice information. The UE can find the corresponding replaced slice information according to the PDU session ID, and the UE replaces the slice information of the PDU session.
[0150] Step 504: The user equipment replies to the second network element with a PDU session modification completion instruction message or a PDU session release completion instruction message.
[0151] Step 505: The UE performs the following operations when performing URSP matching:
[0152] If the UE finds a traffic description in a non-default URSP rule that matches the application information; and there is no established connection with a non-3GPP access, no established connection with a 5G ProSe layer-3 UE-to-network relay UE, no one or more established PDU sessions or any combination of these; and the RSD does not contain a non-seamless non-3GPP offload indication nor a 5G ProSe layer-3 UE-to-network relay offload indication; and there is at least one S-NSSAI in the RSD that is the old slice of the replaced slice (i.e. the replaced slice), then the UE NAS matches the PDU session that uses the new slice of the replaced slice (i.e. the slice after replacement).
[0153] It should be emphasized that this step may also occur after step 502a, that is, after the new slice and old slice information are received.
[0154] It should be noted that in this embodiment, the slice information of RSD in URSP will not be replaced or updated. When NAS matches the PDU session, it will directly match the PDU session of the new slice rather than the replaced slice.
[0155] FIG6 shows a flow diagram of a method for updating a routing policy according to an embodiment of the present application. In this embodiment, when the PCF triggers a slice replacement, the PCF updates the URSP, and the UE accepts and uses the updated URSP. As shown in FIG6 , the method according to this embodiment includes the following steps:
[0156] Step 601a is the same as step 501.
[0157] Step 601b is the same as step 502b.
[0158] Step 602: The first network element updates the user equipment routing policy, triggering the generation of a new UE policy.
[0159] The PCF updates the user equipment routing policy of each associated UE. When updating the user equipment routing policy, each URSP rule containing the old slice is updated to a URSP rule containing the new slice.
[0160] Step 603: The first network element sends the updated user equipment routing policy to the third network element via a user equipment policy control update notification message.
[0161] The replaced second slice is not included in the routing policy of the target user equipment.
[0162] Step 604: The third network element sends the updated user equipment routing policy to the user equipment.
[0163] Optionally, the AMF may encapsulate the updated user equipment routing policy in a DL NAS TRANSPORT message and send it to the user equipment.
[0164] Step 605: After receiving the updated user equipment routing policy, the user equipment replaces the current user equipment routing policy with the received updated user equipment routing policy. Thus, the user equipment implements the update of the user equipment routing policy.
[0165] The embodiment shown in FIG6 differs from the embodiment shown in FIG5 in that, in this embodiment, after step 601b, the UE does not perform the operation of the embodiment shown in FIG5. Instead, after the PCF actively updates the URSP, the UE replaces the updated URSP.
[0166] Figure 7 shows a flow diagram of a method for updating routing policies according to an embodiment of the present application. In this embodiment, the PCF triggers slice replacement, and the PCF triggers the SMF to update the slice and obtain the SM policy through the AMF. As shown in Figure 7, the method of this embodiment includes the following steps:
[0167] Step 701 is the same as step 501.
[0168] Step 702: The third network element sends slice replacement information to the second network element.
[0169] For example, AMF sends an Nsmf_PDUSession_UpdateSMContext service message to SMF, which carries the replacement slice information.
[0170] Step 703: After receiving the slice replacement information sent by the third network element, the second network element updates the locally stored slice of the PDU session and replaces it with the new slice.
[0171] Step 704: The second network element triggers to obtain the updated SM policy from the first network element;
[0172] For example, the SMF may trigger the PCF to obtain an updated SM policy using the Npcf_SMPolicyControl_Create message, in which the new slice is used.
[0173] Step 705: The first network element generates an updated SM policy and sends it to the second network element, including the updated PCC rules.
[0174] Figure 8 shows a flow chart of a method for updating routing policies according to an embodiment of the present application. In this embodiment, when a non-PCF triggers a slice replacement, the AMF does not trigger the PCF to update the URSP. When the UE matches the session locally, it matches the new slice. As shown in Figure 8, the method of this embodiment includes the following steps:
[0175] Step 801: OAM or NSSF sends the replaced slice information and the replaced slice information to the third network element.
[0176] Step 802a: Same as step 502b.
[0177] Step 802b: Same as step 502a.
[0178] Step 803 is the same as step 503.
[0179] Step 804 is the same as step 504.
[0180] Step 805 is the same as step 505.
[0181] Figure 9 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application. In this embodiment, when a non-PCF triggers a slice replacement, the AMF triggers the PCF to update the URSP, and the UE accepts and uses the updated URSP. As shown in Figure 9, the method of this embodiment includes the following steps:
[0182] Step 901: OAM or NSSF sends the replaced slice information and the replaced slice information to the third network element.
[0183] Step 902: After receiving the replaced slice information and the replacement slice information, the third network element updates the user equipment replacement slice information through the registration process or the UCU process; the user equipment replies with a registration acceptance message or a registration update completion message, indicating that the slice replacement has been completed.
[0184] Step 903: The third network element triggers an update of the user equipment routing policy including the user equipment routing policy association identifier and the replacement slice to the first network element through a user equipment policy control update message.
[0185] Among them, the user equipment policy control update message may include an Npcf_UEPolicyControl_update message. In this embodiment, the AMF triggers the update of the UE policy to the PCF through the Npcf_UEPlocyControl_update message, and the UE policy includes the UE policy association identifier and the replacement slice.
[0186] Step 904: After generating the updated user equipment policy, the first network element sends the generated updated user equipment routing policy to the third network element via a user equipment policy control update notification message.
[0187] The user equipment policy control update notification message may include an Npcf_UEPolicyControl_UpdateNotify message.
[0188] Step 905: The third network element sends the updated user equipment routing policy to the user equipment;
[0189] Optionally, the AMF may encapsulate the updated user equipment routing policy in a DL NAS TRANSPORT message and send it to the user equipment.
[0190] Step 906: After receiving the updated user equipment routing policy, the user equipment replaces the current user equipment routing policy with the received updated user equipment routing policy. Thus, the user equipment implements the update of the user equipment routing policy.
[0191] Figure 10 shows a flow chart of a method for updating routing policies according to an embodiment of the present application. In this embodiment, when a non-PCF triggers a slice replacement, the AMF triggers the SMF to update the slice to obtain the SM policy. As shown in Figure 10, the method of this embodiment includes the following steps:
[0192] Step 1001: OAM or NSSF sends the replaced slice information and the replaced slice information to the third network element.
[0193] Steps 1002-1005 are the same as steps 702-705.
[0194] FIG11 shows a flow chart of a method for updating a routing policy according to an embodiment of the present application. In this embodiment, when the PCF triggers a slice replacement, the UE triggers the PCF to update the URSP. As shown in FIG11 , the method according to this embodiment includes the following steps:
[0195] Steps 1101 to 1104 are the same as steps 501 to 504.
[0196] Step 1105 : The user equipment checks all URSPs. If it is found that a slice in the RSD of at least one URSP rule is an old slice (ie, a replaced slice), step 1106 is triggered.
[0197] In step 1106, the user equipment initiates a UL NAS TRANSPORT message to the third network element, wherein the payload container carries a UE state indication message. The UE state indication message indicates that the network side (PCF) needs to update the URSP rules indicated by the UPSI.
[0198] The UL NAS TRANSPORT message may optionally carry at least one item: a new slice and an old slice (which may include all the replacement slice information in step 1102a or information including the affected old slices and related new slices in the URSP).
[0199] The UE status indication message includes at least one item: UPSI list, UE policy class Mark, UE OS ID, URSP rules (one or more), indication information (an explicit indication indicating that the PCF needs to update the URSP rules referred to by the UPSI or the rules in the URSP rules), new slice, old slice (here it can be all the replacement slice information in step 1102a, or it can refer to the information including the affected old slices and related new slices in the URSP).
[0200] Step 1107: The third network triggers an update of the user equipment routing policy including the user equipment routing policy association identifier and the replacement slice to the first network element.
[0201] For example, the AMF can trigger the PCF to update the UE policy through the Namf_Commuication_N1MessageNotify message.
[0202] Step 1108: The first network element sends the updated UE routing policy to the third network element, where the updated UE routing policy includes slice replacement information.
[0203] For example, the PCF may send the updated UE routing policy to the third network element through an Npcf_UEPolicyControl_UpdateNotify message.
[0204] After receiving the message in step 1107 , the PCF updates the URSP rules indicated in the UE state indication message and replaces the old slice with the new slice.
[0205] Step 1109: The third network element sends the updated UE routing policy to the user equipment.
[0206] Through the above method provided in the embodiment of the present application, when the UE learns that a slice replacement has occurred on the network side, it can trigger the network side to update the UE routing policy, so that the updated UE routing policy includes the replaced slice, thereby ensuring that the UE can subsequently transmit data streams normally.
[0207] FIG12 shows a flow chart of a method for updating routing policy according to an embodiment of the present application. In this embodiment, when a non-PCF triggers a slice replacement, the UE triggers the PCF to update the URSP. As shown in FIG12 , the method of this embodiment includes the following steps:
[0208] Steps 1201-1204 are the same as steps 1001-1004.
[0209] Steps 1205-1209 are the same as steps 1105-1109.
[0210] This embodiment differs from the embodiment shown in FIG11 in that the handover replacement is not triggered by the PCF, and the rest of the process is the same as the embodiment shown in FIG11. In addition, another difference from the embodiment shown in FIG11 is that the new slice and the old slice are mandatory in this embodiment.
[0211] The data stream transmission method provided in the embodiment of the present application can be executed by a data stream transmission device. In the embodiment of the present application, the data stream transmission device provided in the embodiment of the present application is described by taking the data stream transmission method executed by the data stream transmission device as an example.
[0212] FIG13 shows a schematic diagram of a data stream transmission device provided in an embodiment of the present application. As shown in FIG13 , the device 1300 includes: a receiving module 131 and a transmission module 132 .
[0213] Among them, the receiving module 131 is used to receive a first message, wherein the information carried in the first message includes one of the following: a protocol data unit PDU session identifier and an identifier of the replaced first slice, an identifier of the replaced first slice and an identifier of the replaced second slice; the transmission module 132 is used to select the PDU session associated with the first slice to transmit the data stream of the target application when the target routing descriptor RSD matching the target application in the user equipment routing policy URSP includes the identifier of the second slice, wherein the PDU session corresponding to the PDU session identifier is associated with the second slice.
[0214] In one implementation, the transmission module 132 selects the PDU session associated with the first slice to transmit the data stream of the target application, including: if a first condition is met, selecting the PDU session associated with the first slice to transmit the data stream of the target application;
[0215] The first condition includes at least one of the following:
[0216] (1) The target traffic descriptor corresponding to the target RSD is a non-default traffic descriptor in the URSP;
[0217] (2) The user equipment does not have any non-3GPP access connection established;
[0218] (3) the user equipment does not establish a connection from the 5G proximity-based service layer 3 user equipment to the network relay user equipment;
[0219] (4) The user equipment does not establish a PDU session;
[0220] (5) The target RSD does not include a seamless non-3GPP offload indication;
[0221] (6) The target RSD does not include a 5G layer 3 user equipment to network relay offload indication.
[0222] In one implementation, the above-mentioned receiving module 131UE receives a first message, including: the UE receives a first message sent by a second network element, wherein the information carried in the first message includes: the PDU session identifier and the identifier of the first slice; or, the UE receives a first message sent by a third network element, wherein the information carried in the first message includes: the identifier of the first slice and the identifier of the second slice.
[0223] The data stream transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a user device, or it can be a device other than a user device. For example, the user device can include but is not limited to the types of user devices 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0224] The data stream transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be described here.
[0225] The routing policy updating method provided in the embodiment of the present application can be executed by a routing policy updating device. In the embodiment of the present application, the routing policy updating method performed by the routing policy updating device is taken as an example to illustrate the routing policy updating device provided in the embodiment of the present application.
[0226] FIG14 shows a schematic diagram of a routing policy updating device provided in an embodiment of the present application. As shown in FIG14 , the device 140 includes: a receiving module 141 and an updating module 142 .
[0227] Among them, the receiving module 141 is used to receive the target user equipment routing policy sent by the third network element, wherein the target user equipment routing policy does not include the identifier of the replaced second slice; the updating module 142 is used to use the target user equipment routing policy to update the locally stored user equipment routing policy.
[0228] In one implementation, before receiving the target user equipment routing policy sent by the third network element, the receiving module 141 may further be used to: receive a first message, wherein the information carried in the first message includes one of the following: a PDU session identifier and an identifier of the replaced first slice, an identifier of the first slice, and an identifier of the second slice;
[0229] When it is determined that the slice in the RSD of at least one URSP rule in the locally stored URSP is the first slice, a third message is sent to the third network element, wherein the third message carries user equipment status indication information, and the user equipment status indication information is used to instruct the network side to update the URSP rule indicated by the target UE policy selection identifier UPSI.
[0230] In one implementation, the third message further carries at least one of the following:
[0231] (1) an identifier of the first slice;
[0232] (2) The identifier of the second slice.
[0233] In one implementation, the user equipment status indication information includes at least one of the following:
[0234] (1) a UPSI list, wherein the UPSI identification list includes at least one target UPSI, and one target UPSI is used to indicate one or more URSP rules;
[0235] (2) User device policy level identification;
[0236] (3) User device operating system identifier;
[0237] (4) at least one URSP rule;
[0238] (5) indication information, used to indicate that the URSP rules in the user equipment status indication information need to be updated;
[0239] (6) Target UE UPSI, used to indicate the URSP rules that need to be updated;
[0240] (7) Identification of the first slice;
[0241] (8) Identification of the second slice.
[0242] FIG15 shows a schematic diagram of another routing policy updating device provided in an embodiment of the present application. As shown in FIG15 , the device 1500 includes: an updating module 151 and a sending module 152 .
[0243] Among them, the updating module 151 is used to update the user equipment routing policy based on the replaced second slice and the replaced first slice after learning that the first slice is used to replace the second slice, wherein the updated target user equipment routing policy does not include the identifier of the second slice; the sending module 152 is used to send the updated target user equipment routing policy to the third network element.
[0244] In one implementation, the updating module 151 learns that the first slice is used to replace the second slice, including: determining to use the first slice to replace the second slice, and notifying the third network element.
[0245] In one implementation, the updating module 151 learning to replace the second slice with the first slice includes: receiving a second message sent by the third network element, wherein the second message carries at least one of the following:
[0246] (1) an identifier of the first slice;
[0247] (2) an identifier of the second slice;
[0248] (3) User equipment routing policy association identifier.
[0249] In one implementation, the above-mentioned sending module 152 sends the updated target user device routing policy to the third network element, including: sending the updated target user device routing policy to the third network element through the user device policy control update notification message, and the target user device routing policy does not include the identifier of the second slice.
[0250] The routing policy updating device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a user device, or it can be a device other than a user device. For example, the user device can include but is not limited to the types of user devices 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0251] The routing policy update device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 3 to 12 and achieve the same technical effects. To avoid repetition, they will not be described here.
[0252] As shown in Figure 16, an embodiment of the present application further provides a communication device 1600, including a processor 1601 and a memory 1602, wherein the memory 1602 stores a program or instruction that can be run on the processor 1601. For example, when the communication device 1600 is a user device, the program or instruction is executed by the processor 1601 to implement the various steps of the embodiment of the above-mentioned data stream transmission method, or to implement the various steps of the embodiment of the above-mentioned routing policy update method, and can achieve the same technical effect. When the communication device 1600 is a network-side device, the program or instruction is executed by the processor 1601 to implement the various steps of the embodiment of the above-mentioned routing policy update method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0253] The present application also provides a user device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiments shown in Figures 2 to 3. This user device embodiment corresponds to the above-mentioned user device side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this user device embodiment and can achieve the same technical effect. Specifically, Figure 17 is a schematic diagram of the hardware structure of a user device implementing an embodiment of the present application.
[0254] The user equipment 1700 includes but is not limited to: a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709 and at least some of the components of the processor 1710.
[0255] Those skilled in the art will appreciate that user equipment 1700 may further include a power supply (such as a battery) to power various components. The power supply may be logically connected to processor 1710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The user equipment structure shown in FIG17 does not limit the user equipment. The user equipment may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.
[0256] It should be understood that in an embodiment of the present application, the input unit 1704 may include a graphics processing unit (GPU) 17041 and a microphone 17042, and the graphics processor 17041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1706 may include a display panel 17061, and the display panel 17061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1707 includes a touch panel 17071 and at least one of other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include two parts: a touch detection device and a touch controller. Other input devices 17072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0257] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1701 may transmit the data to the processor 1710 for processing. Furthermore, the RF unit 1701 may send uplink data to the network-side device. Typically, the RF unit 1701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.
[0258] Memory 1709 can be used to store software programs or instructions and various data. Memory 1709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, memory 1709 may include volatile memory or non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0259] Processor 1710 may include one or more processing units. Optionally, processor 1710 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1710.
[0260] The radio frequency unit 1701 is used to receive a first message, wherein the information carried in the first message includes one of the following: a protocol data unit PDU session identifier and an identifier of the replaced first slice, an identifier of the replaced first slice, and an identifier of the replaced second slice.
[0261] Processor 1710 is configured to select a PDU session associated with the first slice to transmit the data stream of the target application when the target routing descriptor RSD matching the target application in the user equipment routing policy URSP includes the identifier of the second slice, wherein the PDU session corresponding to the PDU session identifier is associated with the second slice.
[0262] Alternatively, the radio frequency unit 1701 is used to receive a target user equipment routing policy sent by a third network element, wherein the target user equipment routing policy does not include an identifier of the replaced second slice; the processor 1710 is used to use the target user equipment routing policy to update a locally stored user equipment routing policy.
[0263] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the data stream transmission method embodiment and the routing policy update method embodiment, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.
[0264] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 4 to 12. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.
[0265] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 18, network-side device 1800 includes an antenna 181, a radio frequency device 182, a baseband device 183, a processor 184, and a memory 185. Antenna 181 is connected to radio frequency device 182. In the uplink direction, radio frequency device 182 receives information via antenna 181 and sends the received information to baseband device 183 for processing. In the downlink direction, baseband device 183 processes the information to be transmitted and sends it to radio frequency device 182. Radio frequency device 182 processes the received information and then sends it through antenna 181.
[0266] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 183 , which includes a baseband processor.
[0267] The baseband device 183 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 18, one of the chips is, for example, a baseband processor, which is connected to the memory 185 through a bus interface to call the program in the memory 185 and execute the network device operations shown in the above method embodiment.
[0268] The network side device may further include a network interface 186, which is, for example, a Common Public Radio Interface (CPRI).
[0269] Specifically, the network side device 1800 of the embodiment of the present application also includes: instructions or programs stored in the memory 185 and can be run on the processor 184. The processor 184 calls the instructions or programs in the memory 185 to execute the methods executed by each module shown in Figure 11 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0270] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data stream transmission method embodiment or the various processes of the above-mentioned routing policy update method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0271] The processor is the processor in the user equipment described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.
[0272] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data stream transmission method embodiment, or to implement the various processes of the above-mentioned routing policy update method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0273] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0274] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data stream transmission method embodiment, or to implement the various processes of the above-mentioned routing policy update method embodiment, and can achieve the same technical effects. To avoid repetition, they are not described here.
[0275] An embodiment of the present application also provides a wireless communication system, including: a user device and a network side device, wherein the user device can be used to execute the steps of the data stream transmission method as described above or execute the steps of the routing policy update method as described above, and the network side device can be used to execute the steps of the routing policy update method as described above.
[0276] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0277] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for causing a user device or a network-side device to execute the methods described in each embodiment of the present application.
[0278] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.
Claims
1. A data stream transmission method, comprising: The user equipment UE receives a first message, wherein the information carried in the first message includes one of the following: a protocol data unit PDU session identifier and an identifier of the replaced first slice, an identifier of the replaced first slice, and an identifier of the replaced second slice; When the target routing descriptor RSD matching the target application in the user equipment routing policy URSP includes the identifier of the second slice, the user equipment selects the PDU session associated with the first slice to transmit the data stream of the target application, wherein the PDU session corresponding to the PDU session identifier is associated with the second slice.
2. The method according to claim 1, wherein: The user equipment selects a PDU session associated with the first slice to transmit a data stream of the target application, including: When the first condition is met, the user equipment selects the PDU session associated with the first slice to transmit the data flow of the target application; The first condition includes at least one of the following: The target traffic descriptor corresponding to the target RSD is a non-default traffic descriptor in the URSP; The user equipment has no non-3GPP access with established connection; The user equipment does not establish a connection from the 5G proximity-based service layer 3 user equipment to the network relay user equipment; The user equipment has not established a PDU session; The target RSD does not include a seamless non-3GPP offload indication; The target RSD does not include a 5G layer 3 user equipment to network relay offload indication.
3. The method according to claim 1 or 2, wherein: The UE receives a first message, including: The UE receives a first message sent by a second network element, wherein the information carried in the first message includes: the PDU session identifier and an identifier of the first slice; or, The UE receives a first message sent by a third network element, wherein the information carried in the first message includes: an identifier of the first slice and an identifier of the second slice.
4. A method for updating a routing strategy, comprising: The user equipment receives a target user equipment routing policy sent by a third network element, wherein the target user equipment routing policy does not include an identifier of the replaced second slice; The user equipment updates the locally stored user equipment routing policy using the target user equipment routing policy.
5. The method according to claim 4, wherein: Before the user equipment receives the target user equipment routing policy sent by the third network element, the method further includes: The user equipment receives a first message, wherein the information carried in the first message includes one of the following: a PDU session identifier and an identifier of the replaced first slice, an identifier of the first slice, and an identifier of the second slice; When it is determined that the identifier of a slice in the RSD of at least one URSP rule in the locally stored URSP is the identifier of the first slice, the user equipment sends a third message to the third network element, wherein the third message carries a user equipment status indication message, and the user equipment status indication message is used to instruct the network side to update the URSP rule indicated by the target UE policy segment identifier UPSI.
6. The method according to claim 5, wherein: The third message also carries at least one of the following: an identifier of the first slice; An identifier of the second slice.
7. The method according to claim 5 or 6, wherein: The user equipment status indication information includes at least one of the following: A UPSI list, wherein the UPSI identification list includes at least one target UPSI, and one target UPSI is used to indicate one or more URSP rules; User device policy level identification; User device operating system identifier; At least one URSP rule; Indication information, used to indicate that the URSP rule in the user equipment status indication information needs to be updated; The identification of the first slice; The identifier of the second slice.
8. A method for updating a routing strategy, comprising: After learning that the second slice is replaced with the first slice, the first network element updates the user equipment routing policy based on the replaced second slice and the replaced first slice, wherein the updated target user equipment routing policy does not include an identifier of the replaced second slice; The first network element sends the updated routing policy of the target user equipment to the third network element.
9. The method according to claim 8, wherein: The step of learning to use the first slice to replace the second slice includes: The first network element determines to use the first slice to replace the second slice, and notifies the third network element.
10. The method according to claim 8, wherein: The step of learning to use the first slice to replace the second slice includes: The first network element receives a second message sent by the third network element, wherein the second message carries at least one of the following: an identifier of the first slice; an identifier of the second slice; User equipment routing policy association identifier.
11. The method according to any one of claims 8 to 10, wherein: The first network element sending the updated routing policy of the target user equipment to the third network element includes: The first network element sends the updated target user equipment routing policy to the third network element through a user equipment policy control update notification message, and the target user equipment routing policy does not include the identifier of the second slice.
12. A data stream transmission device, comprising: A receiving module, configured to receive a first message, wherein the information carried in the first message includes one of the following: a protocol data unit PDU session identifier and an identifier of the replaced first slice, an identifier of the replaced first slice, and an identifier of the replaced second slice; A transmission module is used to select a PDU session associated with the first slice to transmit the data stream of the target application when the target routing descriptor RSD matching the target application in the user equipment routing policy URSP includes the identifier of the second slice, wherein the PDU session corresponding to the PDU session identifier is associated with the second slice.
13. A routing strategy updating device, comprising: A receiving module, configured to receive a target user equipment routing policy sent by a third network element, wherein the target user equipment routing policy does not include an identifier of the replaced second slice; The updating module is used to update the locally stored user equipment routing policy using the target user equipment routing policy.
14. A routing strategy updating device, comprising: an updating module, configured to update a user equipment routing policy based on the replaced second slice and the replaced first slice after learning that the second slice is replaced with the first slice, wherein the updated target user equipment routing policy does not include an identifier of the second slice; The sending module is used to send the updated routing policy of the target user equipment to the third network element.
15. A user equipment, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 7 are implemented.
16. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the routing policy update method as described in any one of claims 8 to 11 are implemented.
17. A readable storage medium storing a program or an instruction, wherein the program or the instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11.
18. A chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method according to any one of claims 1 to 11.
19. A computer program product, wherein the computer program product is stored in a storage medium, and the computer program product is executed by at least one processor to implement the steps of the method according to any one of claims 1 to 11 of the first aspect.
Citation Information
Patent Citations
Session updating method, terminal and network side equipment
CN114080056A
Network congestion processing method and device, terminal, and storage medium
WO2022222753A1
Configuring protocol data unit sessions
WO2023057081A1
