WO2020199105A1

WO2020199105A1 - Data binding method, information update method and device, and terminal

Info

Publication number: WO2020199105A1
Application number: PCT/CN2019/080890
Authority: WO
Inventors: 许阳
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-04-01
Filing date: 2019-04-01
Publication date: 2020-10-08
Also published as: CN112020878B; CN112020878A

Abstract

Embodiments of the present application provide a data binding method and an information update method and device. The method comprises: a terminal performing a first operation in an idle state, wherein the first operation is an update operation for implementing a binding relationship between an application and a session.

Description

Data binding method, information update method and device, terminal

Technical field

The embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a data binding method, an information update method and device, and a terminal.

Background technique

In the user equipment policy (User Equipment policy, UE policy) issued by the network to the terminal, the UE Route Selection Policy (URSP) is used by the terminal to associate the application with the corresponding Protocol Data Unit (Protocol Data Unit, PDU). ) On the conversation. However, the current URSP update effective time is not specified, which will cause erroneous terminal behavior.

Summary of the invention

The embodiments of the application provide a data binding method, information update method and device, and terminal.

The data binding method provided by the embodiment of the application includes:

The terminal performs a first operation when in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.

The data binding method provided by the embodiment of the application includes:

When the network slice parameter in the terminal is updated, the terminal performs a first operation on the UE policy or all UE policies that include the updated network slice parameter, and the first operation is to implement the binding relationship between the application and the session Update operation.

The data binding method provided by the embodiment of the present application includes

The terminal transmits at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of the replicated data are bound to one session.

The information update method provided by the embodiment of the application includes:

The terminal receives the first parameter and/or the second parameter sent by the network device, where the first parameter is used to indicate the time information for performing the first operation and/or the time information for performing the second operation, and the second parameter is used to indicate Time information for performing the third operation;

Wherein, the second operation is an operation to determine the binding relationship between the application and the session, the first operation is an operation to update the binding relationship between the application and the session, and the third operation is to manage access and mobility. The parameter is updated.

The data binding device provided in the embodiment of the present application is applied to a terminal, and the device includes:

The update unit is configured to perform a first operation when the terminal is in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.

The update unit is used to perform a first operation on the UE policy or all UE policies including the updated network slice parameter in the case of updating the network slice parameters in the terminal, and the first operation is to implement binding between the application and the session Update operation of the relationship.

The transmission unit is configured to transmit at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of the replicated data are bound to one session.

The information update device provided by the embodiment of the present application is applied to a terminal, and the device includes:

The receiving unit is configured to receive a first parameter and/or a second parameter sent by a network device, where the first parameter is used to indicate time information for performing the first operation and/or time information for performing the second operation, the second The parameter is used to indicate the time information for performing the third operation;

The terminal provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned data binding method or information update method.

The chip provided in the embodiment of the present application is used to implement the above-mentioned data binding method or information update method.

Specifically, the chip includes a processor, which is used to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned data binding method or information update method.

The computer-readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned data binding method or information update method.

The computer program product provided by the embodiment of the present application includes computer program instructions that cause a computer to execute the above-mentioned data binding method or information update method.

The computer program provided in the embodiment of the present application, when it runs on a computer, causes the computer to execute the aforementioned data binding method or information update method.

Through the above technical solution, the terminal itself can clarify the time when the URSP update takes effect, or coordinate the time when the URSP update takes effect and the time when the access and mobility management parameters are updated through the instructions of the network side, thereby avoiding erroneous terminal behavior .

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation of the application. In the attached picture:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

Figure 2 is a network architecture diagram provided by an embodiment of the present application;

FIG. 3 is a configuration flowchart of a UE policy provided by an embodiment of the present application;

Fig. 4 is a configuration flowchart of access and mobility management related parameters provided by an embodiment of the present application;

FIG. 5 is a first flowchart of a data binding method provided by an embodiment of the present application;

FIG. 6 is a second schematic diagram of the data binding method provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of an information update method provided by an embodiment of the application;

FIG. 8 is a schematic diagram 1 of the structural composition of a data binding device provided by an embodiment of the application;

FIG. 9 is a second schematic diagram of the structural composition of the data binding device provided by an embodiment of the application;

FIG. 10 is a schematic diagram of the structural composition of an information update apparatus provided by an embodiment of the application;

FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a chip of an embodiment of the present application;

FIG. 13 is a schematic block diagram of a communication system provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or a terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110. The "terminal" used here includes, but is not limited to, connection via wired lines, such as public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device. Terminal can refer to access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.

Optionally, the terminals 120 may perform device-to-device (D2D) communication.

Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; The device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies involved in the embodiments of the present application will be described below.

The UE policy is introduced in 5G, and the UE policy can include WLAN Selection Policy (WLANSP), UE Route Selection Policy (URSP), and Internet of Vehicles policies. Among them, WLANSP contains multiple rules. The rules in WLANSP are called WLANSP rules, and WLANSP rules are used when the UE selects which WLAN access point. URSP contains multiple rules. The rules in URSP are called URSP Rules. Each URSP Rule is composed of a service description (Traffic Descriptor) and a set of routing description (Route Selection Descriptor, RSD). URS is used for terminals to apply specific application data. The flow is bound to a specific session (such as a PDU session). Based on different business types, UE strategies can also be divided into vehicle networking strategies, Beijing data strategies, and Internet of Things strategies. The mechanisms are the same as URSP.

At present, relevant content has been formulated for URSP, as shown in Table 1 and Table 2 below:

Table 1: URP Rule

Table 2: RSD

The method of using URSP is as follows: UE associates the application (or application data stream) to the corresponding PDU session for transmission based on URSP. The mechanism is as follows:

When data appears in the application layer, the UE uses the URSP rule in the URSP to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rule. The order of viewing is based on the priority in the Traffic Descriptor in the URSP rule ( Precedence) to determine, that is, the UE checks the matching situation in sequence based on the order of priority. When a URSP rule is matched, it uses the RSD list under the URSP rule to bind the PDU session.

When a URSP rule is matched, the UE searches for a suitable PDU session according to the Precedence order in the RSD. The RSD with higher priority is preferentially used here. If a parameter in the RSD has one or more values, the UE selects One of them is combined with other parameters to find whether the PDU session exists:

1) If it exists, bind the application data to the session for transmission;

2) If it does not exist, the UE triggers the establishment of the PDU session, and the UE reports the attribute parameters of the PDU session in the establishment request message; further,

2.1) If the session is successfully established, the UE will bind the application data to the session for transmission;

2.2) If the session establishment is unsuccessful, the UE searches for the existence of the PDU session again based on other parameter combinations in the RSD or using the parameter combination in the RSD of the second priority (cycle step 1));

If a suitable PDU session cannot be found for binding according to the matched URSP rule, the UE searches for the Traffic Descriptor in the second-priority URSP rule according to the Precedence order to see if it can match the application data stream characteristics. When it matches, repeat The process described earlier.

The above process of finding a suitable PDU session for the application is called "evaluation" in this application. After finding a suitable PDU session binding, the UE will re-execute the evaluation in the following situations to determine the original application data and PDU Whether the binding relationship of the session needs to be updated:

-PCF update URSP;

-UE moves from EPC to 5GC;

-Allowed NSSAI or Configured NSSAI is updated;

-Effective local data network-The data network name (LADN DNN availability) is updated;

-UE is registered to 3GPP access network or non-3GPP access network;

-The UE establishes a connection to the WLAN access network.

The UE Configuration Update (UCU) process includes the UCU process of AMF (as shown in Figure 3) and the UCU process of PCF (as shown in Figure 4). The connection architecture between each network element in these processes is shown in the figure 2 shown.

The configuration of the UE policy is implemented through the UE Configuration Update (UCU) process, as shown in Figure 3, the process includes the following steps:

Step 0-1: When the policy control function network element (PCF) on the network side decides to update the UE policy, it will put the UE policy in the container and send it to the core access and mobility management network element (Core Access and Mobility). Management Function, AMF).

Step 2-3: AMF uses the downlink NAS message to transparently transmit the container to the UE. If the UE is in an idle state, it needs to initiate step 2 to make the UE in a connected state.

Step 4-5: The UE receives the UE policy backward, and transmits the transmission result (such as indicating whether the UE policy transmission is successful) to the AMF through the container, and the AMF then transparently transmits the container to the PCF.

In the PDU session establishment process, the UE will send a PDU session establishment request message to the network side (such as AMF). In the PDU session establishment request message, the UE will report the S-NSSAI and the data network name (Data Network Name, DNN) to the network side. ), access type (Access Type), PDU session identifier and other information, the network establishes the required PDU session for the UE according to these information. Every time a PDU session is established, the network side will inform the UE of the mapped EPS QoS information (EPS QoS information includes EPS bearer identification and mapped QoS parameters). When the UE needs to perform a 5G->4G handover, the network side maps it according to the EPS QoS information previously issued to the UE. Among them, some of the existing PDU sessions/data streams may be merged into the default bearer, and some of the PDU sessions/data streams will be mapped into the dedicated load.

In the 5G network, the terminal needs to go through the registration process to the 5G network before it can perform related 5G services. In the Registration Request message, the UE sends the Requested NSSAI to the RAN and AMF, and the AMF sends the Requested NSSAI to the NSSF to obtain the allowed S-NSSAI (Allowed NSSAI). The AMF sends the Requested NSSAI to the RAN and the AMF in the Registration Accept message. Send the Allowed NSSAI back to the UE.

The UE will subsequently carry S-NSSAI (one of the Allowed NSSAI) in the PDU session request message, and the AMF will query the network slice selection function (Network Slice Selection Function, NSSF) for the corresponding network slice temporary identifier according to the S-NSSAI carried by the UE. (Network Slice Instance-ID, NSI-ID), then AMF sends the returned NSI-ID to the Policy Control Function (NRF) and returns the corresponding SMF network element information. AMF finds the corresponding SMF network element through this information , Generate the corresponding PDU session.

The network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI) in the network slice parameters is divided into the following three types:

1) Requested NSSAI (Requested NSSAI)

Requested NSSAI is sent in the UE registration request message. This information is used for which S-NSSAI the UE applies for. At the same time, the RAN can also send the UE's NAS message to a specific AMF (AMF supporting Requested NSSAI) based on this information.

2) Signed NSSAI (Subscribed NSSAI)

Subscribed NSSAI is the NSSAI information subscribed by the network for the user. When the NSSAI information subscribed by the user changes, the UDM will notify the AMF to trigger the AMF to update the NSSAI configuration for the UE.

3) Allowed NSSAI (Allowed NSSAI)

AMF judges which NSSAI is allowed to use according to the NSSAI requested by the UE in the registration request message, and sends the Allowed NSSAI to the UE in the Registration accept message. The UE's subsequent PDU session establishment request message carries an S-NSSAI in the Allowed NSSAI for establishing a corresponding PDU session.

The configuration of parameters related to access and mobility management is implemented through the UE Configuration Update (UCU) process, as shown in Figure 4, the process includes at least the following steps:

Step 0: AMF decides to update UE configuration.

Further, the AMF can indicate whether the UE needs to perform a registration procedure.

Step 1: The AMF sends a UE configuration update command to the UE.

Step 2: The UE sends a configuration update complete message to the AMF.

The AMF can provide access and mobility management related parameters to the UE through step 1), and can indicate whether the UE needs to perform a registration procedure to update the network slice information.

Among them, access and mobility management related parameters include at least one of the following: Configuration Update Indication, 5G-GUTI, TAI List (TAI List), Allowed NSSAI, Allowed NSSAI Mapping (Mapping Of Allowed NSSAI), Serving PLMN's Configured NSSAI, Configured NSSAI mapping (Mapping Of Configured NSSAI), rejected S-NSSAI (rejected S-NSSAIs), NITZ, mobility restrictions (Mobility Restrictions), LADN information, MICO, operator-defined access types Definitions (Operator-defined access category definitions), SMS subscription instructions (SMS Subscribed Indication). These accesses related to mobility management can all be sent to the UE through the above procedure.

The relationship between URSP and network slicing information: Allowed NSSAI in network slicing parameters is the NSSAI that the network allows the UE to use. When the UE determines the binding relationship between the application and the PDU session, which S-NSSAI of the RSD parameters in the URSP rule is selected It is selected based on Allowed NSSAI, which means that the S-NSSAI parameter selected by the UE in RSD must be one of Allowed NSSAI.

In this case, it can be seen that when the UE's network slice parameters need to be updated, its URSP is likely to be updated. Therefore, the effective time of the update of URSP and network slice information is very important. If one update takes effect but the other does not take effect, It will cause problems. On the other hand, after network slicing parameters are configured for the UE, Allowed NSSAI sometimes takes effect immediately, and sometimes takes effect after the UE enters the idle state. However, the current URSP update takes effect (that is, the binding of the application and the PDU session according to the new evaluation result) The update operation of the fixed relationship) time is not specified. To this end, the following technical solutions of the embodiments of the present application are proposed.

Fig. 5 is a schematic flow chart 1 of the data binding method provided by an embodiment of the application. As shown in Fig. 5, the data binding method includes the following steps:

Step 501: The terminal performs a first operation when in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.

In the embodiment of the present application, the terminal may be any device capable of communicating with the network, such as a mobile phone, a tablet computer, a notebook, a vehicle-mounted terminal, and a wearable device.

It should be noted that the first operation involved in the embodiment of the present application is to implement an update operation of the binding relationship between the application and the session. Compared with the first operation, the second operation involved in the following embodiments of this application is the operation of determining the binding relationship between the application and the session. For the specific behavior of the second operation, refer to the relevant description of the aforementioned evaluation. Specifically, when the application When data appears in the layer, the UE uses the URSP rule in the URSP to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rule, and the viewing order is based on the priority in the Traffic Descriptor in the URP rule (Precedence) To decide, that is, the UE checks the matching situation in order based on the priority order. When a URSP rule is matched, it uses the RSD list under the URSP rule to bind the PDU session.

1) If it exists, bind the application data to the session for transmission;

The above process of finding a suitable PDU session for the application is called evaluation (that is, the second operation) in this application.

In the embodiment of the present application, the terminal decides when to perform the first operation by itself. Specifically, the timing for the terminal to perform the first operation includes the following situations:

Case 1: The terminal performs the first operation after entering the idle state and before entering the next connected state or data transmission.

Case 2: The terminal performs the first operation after initiating the registration process.

Case 3: The terminal implements the update operation of the binding relationship between the application and the first part of the session when in the connected state, and the terminal implements the update operation of the binding relationship between the application and the second part of the session after entering the idle state.

It should be noted that after the binding relationship between the application and the session is determined through the evaluation (that is, the second operation), the above-mentioned case 1 and case 2 all belong to the update operation of the entire binding relationship between the application and the session when the terminal is in the idle state. . The third situation above is that the terminal implements the update operation of the first part of the binding relationship between the application and the session when in the connected state, and implements the second part of the binding relationship between the application and the session after entering the idle state (except for the first part of all binding relationships) Binding relationship other than the binding relationship) update operation. Here, for the third case above, after a part of the binding relationship is changed when the terminal is in the connected state, the remaining unimplemented binding relationship is implemented after the terminal enters the idle state.

In an embodiment, the first partial binding relationship includes a binding relationship corresponding to a specific service. Here, the specific service may be a service with a faster terminal moving speed (it is necessary to complete the update operation of the binding relationship before the terminal moves out of a certain area), such as a car networking service. The specific service may also be a service with low requirements for service interruption (the delay caused by the update of the binding relationship has no or small impact on the service), such as the Internet of Things service.

In the embodiment of the present application, the terminal determines the binding relationship between the new application and the session based on the UE policy when the terminal is in the connected state, and executes the first binding relationship based on the binding relationship between the new application and the session when the terminal is in the idle state. One operation.

Further, when the network slice parameter in the terminal is updated, the terminal performs a first operation on the UE policy or all UE policies that include the updated network slice parameter, and the first operation is to implement application and session binding Update operation of the relationship.

Here, the network slice parameter update means that the original network slice parameters are replaced by new network slice parameters, that is, the terminal starts to use the new network slice parameters. For example, the new Allowed NSSAI and/or Configured NSSAI replace the original Allowed NSSAI and/or Configured NSSAI.

Here, the network slicing parameter includes at least one of the following: Allowed NSSAI, Configured NSSAI. Preferably, the network slicing parameter is Allowed NSSAI.

In the above solution, the binding relationship between the application and the session is obtained according to the UE policy (refer to the relevant description of the aforementioned evaluation).

The above-mentioned solutions of the embodiments of the present application will be described with examples in combination with specific application scenarios.

Application scenario 1: The terminal is in an idle state when performing the second operation (ie evaluation)

Update method 1: The terminal directly implements the update operation of the binding relationship between the application and the session.

Update method 2: Before the terminal enters the next connection state or data transmission, an update operation of the binding relationship between the application and the session is performed.

Update method 3: The terminal implements an update operation of the binding relationship between the application and the session after the registration process is initiated.

The above three update methods all belong to the update operation of the binding relationship between the application and the session when the terminal is in an idle state.

Application scenario 2: The terminal is in the connected state when performing the second operation (ie evaluation)

Update method 1: The terminal implements an update operation of the binding relationship between the application and the session after entering the idle state.

Update method 2: The terminal implements an update operation of the binding relationship between the application and the session before entering the connected state or sending data next time.

Update method 3: The terminal implements an update operation of the binding relationship between the application and the session after initiating a registration process (such as location update).

Update method 4: The terminal implements the update operation of the binding relationship between the application and the first part of the session before entering the idle state (in the connected state), and implements the update operation of the binding relationship between the application and the second part of the session after the idle state.

The embodiment of the present application also provides a data binding method. As shown in FIG. 6, the data binding method includes the following steps:

Step 601: The terminal transmits at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of replicated data are bound to one session.

Here, replicated data refers to multiple channels of data from the application layer, and the content of the application layer data is the same. The transmission of replicated data can ensure the reliability of data transmission.

In the above solution, the binding of one or more channels of data in the replicated data to a session is determined according to the URSP strategy. For example: one or more channels of data in the replicated data match a business of a URSP rule Description (Traffic Descriptor), and select the route corresponding to the Traffic Descriptor to describe the session corresponding to a set of parameters in the RSD for binding.

FIG. 7 is a schematic flowchart of an information update method provided by an embodiment of the application. As shown in FIG. 7, the information update method includes the following steps:

Step 701: The terminal receives a first parameter and/or a second parameter sent by a network device, where the first parameter is used to indicate time information for performing a first operation and/or time information for performing a second operation, and the second parameter Time information for indicating the execution of the third operation; wherein, the second operation is an operation for determining the binding relationship between the application and the session, and the first operation is an update operation for implementing the binding relationship between the application and the session. The third operation is an operation of updating access and mobility management parameters.

The first operation involved in the embodiment of the present application is to implement an update operation of the binding relationship between the application and the session. Compared with the first operation, the second operation involved in the embodiment of the present application is an operation of determining the binding relationship between the application and the session. For the specific behavior of the second operation, refer to the relevant description of the aforementioned evaluation, which will not be repeated here.

In the embodiment of the present application, the configuration granularity of the first parameter (that is, the control granularity) includes the value of a first parameter corresponding to a strategy type, or the value of a first parameter corresponding to a strategy identifier, or the value sent to the terminal. All strategies correspond to a value of the first parameter.

For example, the value of the first parameter corresponding to the USRP strategy is t1, the value of the first parameter corresponding to the V2X strategy is t2, and the value of the first parameter corresponding to the IoT strategy is t3.

It should be noted that different types of strategy types may correspond to the same value of the first parameter, or may correspond to different values of the first parameter.

For example, the first policy identifier (Policy Section Identifier, PSI) corresponds to the value of the first parameter t1, the second PSI corresponds to the value of the first parameter t2, and the third PSI corresponds to the value of the first parameter t3.

It should be noted that different PSIs may correspond to the same value of the first parameter, or may correspond to different values of the first parameter.

For example, the value of the first parameter corresponding to the first strategy is t1, the value of the first parameter corresponding to the second strategy is t2, and the value of the first parameter corresponding to the third strategy is t3.

It should be noted that different strategies may correspond to the same value of the first parameter, or may correspond to different values of the first parameter.

In the embodiment of the present application, the time information indicated by the first parameter refers to a time period or point in time. Further, the time information includes one or a combination of the following: when the terminal is in an idle state, when the terminal is in a connected state, after the terminal is in an idle state and initiates a registration process, the terminal enters the next time Before connecting or transferring data.

In the embodiment of the present application, the network device is a PCF, the first parameter is encapsulated in a container by the PCF and sent to the AMF, and the container is transparently transmitted to the terminal through the AMF. Further, the container is sent to the terminal using a NAS message through the AMF. The NAS message here is a downlink NAS message.

In the embodiment of the present application, the sending of the first parameter may be sent along with the UE policy. Specifically, the terminal receives the UE policy sent by the network device, and the UE policy carries first indication information, and the first indication The information is used to indicate the first parameter. Referring to FIG. 3, in step 1 and step 3, the first parameter may be directly carried in the UE policy.

In the embodiment of the present application, the third parameter is used to indicate the time to update the access and mobility management parameters. Specifically, the update time here means that the configured access and mobility management parameters are increased to and/ Or replace the time for the existing access and mobility management parameters of the terminal.

In the embodiment of the present application, the access and mobility management parameters include at least network slicing parameters. Here, the network slice parameters include at least one of the following: Allowed NSSAI, Requested NSSAI, Subscribed NSSAI, and Configured NSSAI.

In the embodiment of the present application, the time information indicated by the second parameter refers to a time period or point in time.

In the embodiment of the present application, the configuration granularity (ie, control granularity) of the second parameter includes one or more access and mobility management parameters corresponding to a second parameter value, or all the access and mobility management parameters sent to the terminal. The management parameter corresponds to the value of a second parameter.

Here, the access and mobility management related parameters in the NAS message sent by the network side to the terminal include at least one of the following: Configuration Update Indication, 5G-GUTI, TAI List, Allowed NSSAI, Allowed NSSAI mapping (Mapping Of Allowed NSSAI), Serving PLMN Configured NSSAI, Configured NSSAI mapping (Mapping Of Configured NSSAI), rejected S-NSSAI (rejected S-NSSAIs), NITZ, mobility restrictions (Mobility Restrictions), LADN information , MICO, operator-defined access category definitions, and SMS subscription indication (SMS Subscribed Indication).

The one or more access and mobility management parameters sent to the terminal correspond to a second parameter value, or all the access and mobility management parameters sent to the terminal correspond to a second parameter value.

In this embodiment of the application, the network device is AMF, and the second parameter is sent to the terminal by the AMF using a NAS message. The NAS message here is a downlink NAS message.

Further, the sending of the second parameter may be sent along with the access and mobility management parameters. Specifically, the terminal receives the access and mobility management parameters sent by the network device, and the access and mobility management parameters Carrying second indication information, where the second indication information is used to indicate the second parameter. Referring to FIG. 4, in step 1, the second parameter may be directly carried in the access and mobility management parameters.

In the embodiment of the present application, the first parameter and/or the second parameter are determined through interaction between AMF and PCF.

The technical solution of the embodiment of the present application can coordinate the UE strategy and the update of access and mobility management parameters. On the other hand, reuse of the existing process to the greatest extent can reduce the impact on the existing process.

It should be noted that the UE policy in the embodiment of the present application is not limited to URSP, and may also be other types of policies, such as V2X policies, IoT policies, and so on.

FIG. 8 is a schematic diagram 1 of the structural composition of a data binding device provided by an embodiment of the application. The data binding device is applied to a terminal, and the data binding device includes an update unit 801.

In an application example, the update unit 801 is configured to perform a first operation when the terminal is in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.

In an embodiment, the update unit 801 is configured to perform the first operation after the terminal enters the idle state and before entering the next connected state or data transmission.

In one embodiment, the update unit 801 is configured to perform the first operation after the terminal initiates a registration process.

In one embodiment, the update unit 801 is configured to perform an update operation of the binding relationship between the application and the first part of the session when the terminal is in the connected state, and implement the second part of the application and the session after the terminal enters the idle state. Update operation of binding relationship.

In an embodiment, the first partial binding relationship includes a binding relationship corresponding to a specific service.

In an embodiment, the update unit 801 is configured to determine the binding relationship between a new application and session based on the UE policy when the terminal is in the connected state, and the terminal is based on the new application and session when in the idle state. The binding relationship of executes the first operation.

In another application example, the updating unit 801 is used for updating network slice parameters in the terminal, performing a first operation on UE policies or all UE policies that include the updated network slice parameters. One operation is to implement an update operation of the binding relationship between the application and the session.

In an embodiment, the network slicing parameter is Allowed NSSAI.

In an embodiment, the binding relationship between the application and the session is obtained according to the UE policy.

Those skilled in the art should understand that the relevant description of the foregoing data binding apparatus in the embodiment of the present application can be understood with reference to the relevant description of the data binding method in the embodiment of the present application.

FIG. 9 is a second schematic diagram of the structural composition of a data binding device provided by an embodiment of the application. The data binding device is applied to a terminal, and the data binding device includes:

The transmission unit 901 is configured to transmit at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of the replicated data are bound to one session.

In one embodiment, binding one or more channels of data in the replication data to a session is determined according to the URSP policy; the one or more channels of data are matched to a TrafficDescriptor of a URSP rule, and the The routing description corresponding to the TrafficDescriptor describes the binding of the session corresponding to a set of parameters in the RSD.

FIG. 10 is a schematic diagram of the structural composition of an information update device provided by an embodiment of the application. The information update device is applied to a terminal, and the information update device includes:

The receiving unit 1001 is configured to receive a first parameter and/or a second parameter sent by a network device, where the first parameter is used to indicate time information for performing a first operation and/or time information for performing a second operation. The second parameter is used to indicate the time information for performing the third operation;

In an embodiment, the second operation is an operation to determine the binding relationship between the application and the session, the first operation is an operation to update the binding relationship between the application and the session, and the third operation is to access Update operations with mobility management parameters.

In an embodiment, the configuration granularity of the first parameter includes a strategy type corresponding to a first parameter value, or a strategy identifier corresponding to a first parameter value, or all strategies sent to the terminal correspond to a first parameter value. The value of the parameter.

In one embodiment, the time information refers to a time period or point in time.

In an embodiment, the time information includes one or a combination of the following: when the terminal is in an idle state, when the terminal is in a connected state, after the terminal is in an idle state and initiates a registration process, the Before the terminal enters the connected state or transmits data next time.

In an embodiment, the network device is a PCF, the first parameter is encapsulated in a container by the PCF and sent to the AMF, and the container is transparently transmitted to the terminal through the AMF.

In an embodiment, the container is sent to the terminal using a NAS message through the AMF.

In an implementation manner, the receiving unit 1001 is configured to receive a UE policy sent by the network device, where the UE policy carries first indication information, and the first indication information is used to indicate the first parameter.

In an embodiment, the configuration granularity of the second parameter includes one or more access and mobility management parameters corresponding to a second parameter value, or all access and mobility management parameters sent to the terminal correspond to a first parameter. The value of the second parameter.

In an embodiment, the network device is an AMF, and the second parameter is sent to the terminal by the AMF using a NAS message.

In an embodiment, the receiving unit 1001 is configured to receive an access and mobility management parameter sent by the network device, where the access and mobility management parameter carries second indication information, and the second indication information Used to indicate the second parameter.

In an embodiment, the access and mobility management parameters include at least network slicing parameters.

In an embodiment, the first parameter and/or the second parameter are determined through negotiation between AMF and PCF.

Those skilled in the art should understand that the relevant description of the foregoing information update apparatus in the embodiment of the present application can be understood with reference to the relevant description of the information update method in the embodiment of the present application.

FIG. 11 is a schematic structural diagram of a communication device 1100 according to an embodiment of the present application. The communication device may be a terminal or a network device. The communication device 1100 shown in FIG. 11 includes a processor 1110. The processor 1110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11, the communication device 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

The memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.

Optionally, as shown in FIG. 11, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Wherein, the transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 1100 may specifically be a network device in an embodiment of the application, and the communication device 1100 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For the sake of brevity, details are not repeated here. .

Optionally, the communication device 1100 may specifically be a mobile terminal/terminal according to an embodiment of the application, and the communication device 1100 may implement the corresponding procedures implemented by the mobile terminal/terminal in each method of the embodiments of the application. For the sake of brevity, This will not be repeated here.

FIG. 12 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1200 shown in FIG. 12 includes a processor 1210, and the processor 1210 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 12, the chip 1200 may further include a memory 1220. The processor 1210 can call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

The memory 1220 may be a separate device independent of the processor 1210, or it may be integrated in the processor 1210.

Optionally, the chip 1200 may further include an input interface 1230. The processor 1210 can control the input interface 1230 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 1200 may further include an output interface 1240. The processor 1210 can control the output interface 1240 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application. For brevity, details are not described herein again.

Optionally, the chip can be applied to the mobile terminal/terminal in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application. For the sake of brevity, it will not be omitted here. Repeat.

It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.

FIG. 13 is a schematic block diagram of a communication system 1300 according to an embodiment of the present application. As shown in FIG. 13, the communication system 1300 includes a terminal 1310 and a network device 1320.

Wherein, the terminal 1310 may be used to implement the corresponding functions implemented by the terminal in the foregoing method, and the network device 1320 may be used to implement the corresponding functions implemented by the network device in the foregoing method. For brevity, details are not described herein again.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application, for It’s concise and will not be repeated here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

Optionally, the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding procedures implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application, for the sake of brevity , I won’t repeat it here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application. When the computer program runs on the computer, the computer can execute the corresponding methods implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A data binding method, the method includes:

The terminal performs a first operation when in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.
The method according to claim 1, wherein the terminal performs the first operation after entering the idle state and before entering the next connected state or data transmission.
The method according to claim 1, wherein the terminal performs the first operation after initiating a registration procedure.
The method according to claim 1, wherein the terminal implements an update operation of the binding relationship between the application and the first part of the session when in the connected state, and implements the binding relationship between the application and the second part of the session after the terminal enters the idle state Update operation.
The method according to claim 4, wherein the first partial binding relationship includes a binding relationship corresponding to a specific service.
The method according to any one of claims 1 to 5, wherein the terminal determines the binding relationship between the new application and the session based on the UE policy when the terminal is in the connected state, and the terminal is based on the new The binding relationship between the application and the session executes the first operation.
A data binding method, the method includes:

When the network slice parameter in the terminal is updated, the terminal performs a first operation on the UE policy or all UE policies that include the updated network slice parameter, and the first operation is to implement the binding relationship between the application and the session Update operation.
The method according to claim 7, wherein the network slicing parameter is Allowed NSSAI.
The method according to claim 7 or 8, wherein the binding relationship between the application and the session is obtained according to the UE policy.
A data binding method, the method includes

The terminal transmits at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of the replicated data are bound to one session.
The method according to claim 10, wherein the binding of one or more channels of data in the replicated data to a session is determined according to the URSP policy; the one or more channels of data match the service description Traffic of a URSP rule On the Descriptor, the session corresponding to a set of parameters in the RSD is selected for binding to the routing description corresponding to the Traffic Descriptor.
An information update method, the method includes:

The terminal receives the first parameter and/or the second parameter sent by the network device, where the first parameter is used to indicate the time information for performing the first operation and/or the time information for performing the second operation, and the second parameter is used to indicate Time information for performing the third operation;

Wherein, the second operation is an operation to determine the binding relationship between the application and the session, the first operation is an operation to update the binding relationship between the application and the session, and the third operation is to manage access and mobility. The parameter is updated.
The method according to claim 12, wherein the configuration granularity of the first parameter includes a value of a first parameter corresponding to a policy type, or a value of a first parameter corresponding to a policy identifier, or all information sent to the terminal. The strategy corresponds to the value of a first parameter.
The method according to claim 12 or 13, wherein the time information refers to a time period or point in time.
The method according to claim 14, wherein the time information includes a combination of one or more of the following: when the terminal is in an idle state, when the terminal is in a connected state, and the terminal is in an idle state and initiates registration After the process, the terminal enters the connected state or before transmitting data next time.
The method according to any one of claims 12 to 15, wherein the network device is a policy control function network element PCF, and the first parameter is encapsulated in a container by the PCF and sent to the core access and mobility management network Meta AMF, the container is transparently transmitted to the terminal through the AMF.
The method according to claim 16, wherein the container is sent to the terminal by using a NAS message through the AMF.
The method according to any one of claims 12 to 17, wherein the terminal receiving the first parameter sent by the network device comprises:

The terminal receives the UE policy sent by the network device, where the UE policy carries first indication information, and the first indication information is used to indicate the first parameter.
The method according to any one of claims 12 to 18, wherein the configuration granularity of the second parameter includes one or more access and mobility management parameters corresponding to a second parameter value, or a value sent to the terminal All access and mobility management parameters correspond to a second parameter value.
The method according to any one of claims 12 to 19, wherein the network device is an AMF, and the second parameter is sent to the terminal by the AMF using a NAS message.
The method according to any one of claims 12 to 20, wherein the terminal receiving the second parameter sent by the network device comprises:

The terminal receives an access and mobility management parameter sent by the network device, where the access and mobility management parameter carries second indication information, and the second indication information is used to indicate the second parameter.
The method according to any one of claims 12 to 21, wherein the access and mobility management parameters include at least network slicing parameters.
The method according to any one of claims 12 to 22, wherein the first parameter and/or the second parameter are determined by interaction between AMF and PCF.
A data binding device applied to a terminal, the device comprising:

The update unit is configured to perform a first operation when the terminal is in an idle state, and the first operation is to implement an update operation of the binding relationship between the application and the session.
The device according to claim 24, wherein the update unit is configured to perform the first operation after the terminal enters the idle state and before entering the next connected state or data transmission.
The apparatus according to claim 24, wherein the update unit is configured to perform the first operation after the terminal initiates a registration procedure.
The apparatus according to claim 24, wherein the update unit is configured to perform an update operation of the binding relationship between the application and the first part of the session when the terminal is in the connected state, and implement the application and the session after the terminal enters the idle state. The second part of the update operation of the binding relationship.
The apparatus according to claim 27, wherein the first partial binding relationship includes a binding relationship corresponding to a specific service.
The apparatus according to any one of claims 24 to 28, wherein the update unit is configured to determine a binding relationship between a new application and a session based on a UE policy when the terminal is in a connected state, and the terminal is idle The first operation is performed based on the binding relationship between the new application and the session in the state.
A data binding device applied to a terminal, the device comprising:

The update unit is used to perform a first operation on the UE policy or all UE policies including the updated network slice parameter in the case of updating the network slice parameters in the terminal, and the first operation is to implement binding between the application and the session Update operation of the relationship.
The apparatus according to claim 30, wherein the network slicing parameter is Allowed NSSAI.
The apparatus according to claim 30 or 31, wherein the binding relationship between the application and the session is obtained according to the UE policy.
A data binding device applied to a terminal, the device comprising:

The transmission unit is configured to transmit at least one channel of replicated data through at least one session, where the replicated data includes multiple channels of data from the application layer, and one or more channels of the replicated data are bound to one session.
The device according to claim 33, wherein the binding of one or more channels of data to a session in the replicated data is determined according to a URSP policy; the one or more channels of data are matched to a service description Traffic Descriptor of a URSP rule And select the session corresponding to a set of parameters in the RSD of the routing description corresponding to the Traffic Descriptor for binding.
An information update device applied to a terminal, the device comprising:

The receiving unit is configured to receive a first parameter and/or a second parameter sent by a network device, where the first parameter is used to indicate time information for performing the first operation and/or time information for performing the second operation, the second The parameter is used to indicate the time information for performing the third operation;

Wherein, the second operation is an operation to determine the binding relationship between the application and the session, the first operation is an operation to update the binding relationship between the application and the session, and the third operation is to manage access and mobility. The parameter is updated.
The device according to claim 35, wherein the configuration granularity of the first parameter comprises a value of a first parameter corresponding to a policy type, or a value of a first parameter corresponding to a policy identifier, or all information sent to the terminal. The strategy corresponds to the value of a first parameter.
The device according to claim 35 or 36, wherein the time information refers to a time period or point in time.
The device according to claim 37, wherein the time information includes one or more of the following: when the terminal is in an idle state, when the terminal is in a connected state, and the terminal is in an idle state and initiates registration After the process, the terminal enters the connected state or before transmitting data next time.
The apparatus according to any one of claims 35 to 38, wherein the network device is a policy control function network element PCF, and the first parameter is encapsulated in a container by the PCF and sent to the core access and mobility management network Meta AMF, the container is transparently transmitted to the terminal through the AMF.
The apparatus according to claim 39, wherein the container is sent to the terminal through the AMF using a NAS message.
The apparatus according to any one of claims 35 to 40, wherein the receiving unit is configured to receive a UE policy sent by the network device, the UE policy carrying first indication information, and the first indication information Used to indicate the first parameter.
The apparatus according to any one of claims 35 to 41, wherein the configuration granularity of the second parameter includes one or more access and mobility management parameters corresponding to a second parameter value, or a value sent to the terminal All access and mobility management parameters correspond to a second parameter value.
The apparatus according to any one of claims 35 to 42, wherein the network device is an AMF, and the second parameter is sent to the terminal by the AMF using a NAS message.
The apparatus according to any one of claims 35 to 43, wherein the receiving unit is configured to receive an access and mobility management parameter sent by the network device, and the access and mobility management parameter carries a Two indication information, where the second indication information is used to indicate the second parameter.
The apparatus according to any one of claims 35 to 44, wherein the access and mobility management parameters include at least network slicing parameters.
The apparatus according to any one of claims 35 to 45, wherein the first parameter and/or the second parameter are determined through negotiation between AMF and PCF.
A terminal comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the computer program according to any one of claims 1 to 6 Method, or the method of any one of 7 to 9, or the method of any one of 10 to 11, or the method of any one of claims 12 to 23.
A chip, comprising: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 1 to 6, or any one of 7 to 9 The method of one, or the method of any one of 10 to 11, or the method of any one of claims 12 to 23.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 9, or The method of any one of 10 to 11, or the method of any one of claims 12 to 23.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 9, or 10 to 11 The method of any one of or the method of any one of claims 12 to 23.
A computer program that causes a computer to execute the method according to any one of claims 1 to 6, or the method according to any one of 7 to 9, or any one of claims 10 to 11 , Or the method of any one of claims 12 to 23.