Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: on the basis of a first policy, a terminal determines a first network associated with a first service, the first policy comprising a first association relationship between services and networks; and the terminal transmits the first service by means of the first network. In embodiments of the present application, a first policy is introduced, wherein the first policy comprises a first association relationship between services and networks, such that a terminal can determine, on the basis of the first association relationship, a first network associated with a first service, and transmit the first service by means of the first network, thereby improving the transmission efficiency of the services in a multi-access scenario.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method and communication device. Background Art

[0002] In some scenarios, a terminal can access multiple networks simultaneously and use user plane connections in multiple networks to transmit services. This is also known as a multi-access scenario. For example, a terminal can simultaneously access 3rd Generation Partnership Project (3GPP) access network 1 and 3GPP access network 2, and transmit services with user plane network element 1 in the core network through 3GPP access network 1, and transmit services with user plane network element 2 in the core network through 3GPP access network 2. However, current technologies do not specify how a terminal should use multiple networks for service transmission, resulting in low efficiency when a terminal accesses multiple networks for service transmission.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a method for wireless communication is provided, including: a terminal determining a first network associated with a first service based on a first strategy, the first strategy including a first association relationship between the service and the network; and the terminal transmitting the first service through the first network.

[0006] In a second aspect, a method for wireless communication is provided, including: a core network device sends a first policy to a terminal, where the first policy includes a first association relationship between a service and a network.

[0007] In a third aspect, a method for wireless communication is provided, including: a terminal determines a UE route selection policy (URSP) corresponding to a first service, the URSP being used to indicate one or more of the following: a third association relationship between a network and a radio access technology (RAT) type; a fourth association relationship between the network and a system type, the system type being used to indicate a type of a core network in the network and / or a type of a non-access network in the network.

[0008] In a fourth aspect, a method for wireless communication is provided, including: a core network device sends a UE routing selection policy URSP to a terminal, wherein the URSP is used to indicate one or more of the following: a third association relationship between the network and the radio access technology RAT type; a fourth association relationship between the network and the system type, wherein the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

[0009] In a fifth aspect, a method for wireless communication is provided, comprising: a first device sending first information to a second device, wherein the first information carries capability information associated with a network access method.

[0010] In a sixth aspect, a method for wireless communication is provided, comprising: a second device receiving first information sent by a first device, wherein the first information carries capability information associated with a network access method.

[0011] In a seventh aspect, a terminal is provided, comprising: a processing unit for determining a first network associated with a first service based on a first strategy, wherein the first strategy includes a first association relationship between the service and the network; and transmitting the first service through the first network.

[0012] In an eighth aspect, a core network device is provided, including: a sending unit, configured to send a first policy to a terminal, wherein the first policy includes a first association relationship between a service and a network.

[0013] In the ninth aspect, a terminal is provided, including: a processing unit for determining a UE routing selection strategy URSP corresponding to a first service, wherein the URSP is used to indicate one or more of the following: a third association relationship between a network and a radio access technology RAT type; a fourth association relationship between the network and a system type, wherein the system type is used to indicate the type of a core network in the network and / or the type of a non-access network in the network.

[0014] In the tenth aspect, a core network device is provided, including: a sending unit for sending a UE routing selection policy URSP to a terminal, wherein the URSP is used to indicate one or more of the following: a third association relationship between the network and the radio access technology RAT type; a fourth association relationship between the network and the system type, wherein the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

[0015] In an eleventh aspect, a communication device is provided, which is a first device and includes: a sending unit, configured to send first information to a second device, wherein the first information carries capability information associated with a network access method.

[0016] In a twelfth aspect, a communication device is provided, which is a second device and includes: a receiving unit for receiving first information sent by a first device, where the first information carries capability information associated with a network access method.

[0017] In the thirteenth aspect, a communication device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the methods of the above aspects.

[0018] In a fourteenth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal and / or network device. In another possible design, the system may also include other devices that interact with the terminal or network device in the solution provided in the embodiment of the present application.

[0019] In the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal or a network device) to execute part or all of the steps in the methods of the above aspects.

[0020] In a sixteenth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal or a network device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0021] In the seventeenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0022] A first strategy is introduced in an embodiment of the present application, wherein the first strategy includes a first association relationship between a service and a network. In this way, the terminal can determine the first network associated with the first service based on the first association relationship, and transmit the first service through the first network to improve the transmission efficiency of the service in a multi-access scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a schematic diagram of a wireless communication system to which an embodiment of the present application is applicable.

[0024] FIG2 is a flowchart of a UE policy configuration process applicable to an embodiment of the present application.

[0025] FIG3 is a schematic diagram of service transmission based on a multi-access method applicable to an embodiment of the present application.

[0026] FIG4A is a schematic diagram of another multi-access-based service transmission method applicable to an embodiment of the present application.

[0027] FIG4B is a schematic diagram of another multi-access-based service transmission method applicable to an embodiment of the present application.

[0028] FIG4C is a schematic diagram of another multi-access-based service transmission method applicable to an embodiment of the present application.

[0029] FIG5 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0030] FIG6 is a schematic flowchart of a method for using the first strategy in an embodiment of the present application.

[0031] FIG7 is a schematic flowchart of a method for using the first strategy in another embodiment of the present application.

[0032] FIG8 is a schematic flowchart of a method for using preemptive priority in an embodiment of the present application.

[0033] FIG9 is a schematic flowchart of a wireless communication method according to another embodiment of the present application.

[0034] FIG10 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0035] FIG11 is a schematic flowchart of a wireless communication method according to another embodiment of the present application.

[0036] FIG12 is a schematic diagram of a terminal according to an embodiment of the present application.

[0037] Figure 13 is a schematic diagram of the core network device of an embodiment of the present application.

[0038] FIG14 is a schematic diagram of a terminal according to another embodiment of the present application.

[0039] FIG15 is a schematic diagram of a core network device according to another embodiment of the present application.

[0040] FIG16 is a schematic diagram of a communication device according to an embodiment of the present application.

[0041] FIG17 is a schematic diagram of a communication device according to another embodiment of the present application.

[0042] FIG18 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0043] The technical solutions in this application will be described below in conjunction with the accompanying drawings. To facilitate understanding of this application, the following first introduces the architecture applicable to the embodiments of this application, the communication processes involved, and terminology.

[0044] FIG1 is a schematic diagram of a wireless communication system to which an embodiment of the present application is applicable. As shown in Figure 1, the fifth generation (5G) system or new radio (NR) network architecture released by the 3rd Generation Partnership Project (3GPP) standard group includes: terminal equipment (also known as "user equipment (UE)" 101, access network equipment supporting 3GPP technology 102 (including radio access network (RAN) or access network (AN)), user plane function (UPF) network element 105, access and mobility management function (AMF) network element 103, session management function (SMF) network element 104, policy control function (PCF) network element 106, application function (AF) network element 109, data network (DN) 108, network slice selection function (NSSF) 111, authentication server function (AUSF) 110, unified data management function (UDF) network element 111, and the like. Management, UDM)107.

[0045] It should be noted that the network architecture shown in Figure 1 does not constitute a limitation on the 5G network architecture. In specific implementations, the 5G network architecture may include more or fewer network elements than shown, or may combine certain network elements. In addition, in Figure 1, the AN or RAN is represented in the form of (R)AN.

[0046] The terminal device 101 can be user equipment (UE), a terminal, a handheld terminal, a laptop computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device (handheld), a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a handheld device with wireless communication function, a computing device, a processing device connected to a wireless modem, a drone, a vehicle-mounted device, a wearable device, a terminal in the Internet of Things, a virtual reality device, a terminal device in a future communication system (e.g., 6G) network, a terminal in a future evolved public land mobile network (PLMN), etc.

[0047] The access network device 102 is an access device that connects terminal devices to the network architecture wirelessly. It is mainly responsible for radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. Examples include base stations NodeB, evolved base stations eNodeB, base stations in 5G mobile communication systems or new radio (NR) communication systems, and base stations in future mobile communication systems.

[0048] UPF network element 105, AMF network element 103, SMF network element 104, and PCF network element 106 are network elements of the 3GPP core network (referred to as core network elements). UPF network element 105 can be called a user plane function network element, which is mainly responsible for the transmission of user data. The other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable transmission of user data.

[0049] The UPF network element 105 (or simply "UPF") can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. The transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: a user plane connection between the UPF network element and the access network device, and a channel established between the access network device and the terminal. The user plane connection is a quality of service (QoS) flow that can be established between the UPF network element and the access network device to transmit data.

[0050] The AMF network element 103 (or "AMF" for short) can be used to manage terminal access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session when providing services for the terminal session to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0051] The SMF network element 104 (or "SMF" for short) can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS.

[0052] The PCF network element 106 (or simply "PCF") is used to provide policies, such as QoS policy, slice selection policy, UE policy, etc., to the AMF network element 103 and the SMF network element 104. In some implementations, the PCF can manage the issuance and update of policies.

[0053] The AF network element 109 (or simply "AF") is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.

[0054] DN 108 can provide data services to users on networks such as IP Multimedia Service (IMS) and the Internet. DN 108 can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement the functions of AF network elements.

[0055] NSSF 111 is used for network slice selection and supports the following functions: selecting a set of network slice instances to serve the UE; determining the allowed network slice selection assistance information (NSSAI) and, when necessary, determining the mapping to the contracted single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on the configuration.

[0056] AUSF 110 is used to receive the request from AMF 103 to authenticate the terminal, request the key from UDM 107, and then forward the issued key to AMF 103 for authentication processing.

[0057] UDM 107 includes functions such as generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.

[0058] It should be understood that each network element in Figure 1 can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0059] As introduced above, in the above-mentioned communication system, the network elements related to the UE policy may include PCF, AMF, etc. The following describes the UE policy configuration process applicable to the embodiment of the present application in combination with Figure 2.

[0060] UE policy configuration process

[0061] Figure 2 is a flow chart of a UE policy configuration process applicable to an embodiment of the present application. The method shown in Figure 2 includes steps S210 to S260.

[0062] In step S210 , the PCF determines whether to update the UE policy.

[0063] It should be noted that if the PCF does not intend to update the UE policy, step S210 may not be included in the process shown in Figure 2. If the PCF does determine that the UE policy is to be updated, step S210 will be included in the process shown in Figure 2. In addition, if the PCF determines that the UE policy is to be updated, the process shown in Figure 2 is also referred to as the "UE configuration update (UCU)" process.

[0064] In step S220, the PCF sends a communication service request to the AMF.

[0065] In some implementations, the uplink service request may carry a container, which includes relevant information of the UE policy, such as the content of the UE policy or a UE policy identifier.

[0066] The communication service request can be transmitted via N1 and N2 messages. Therefore, the communication service request can also be expressed as "Namf_Communication_N1N2 Message Transfer".

[0067] In step S230 , the network triggers a service request (network triggered service request) so that the network can communicate with the UE.

[0068] In step S240, the AMF sends the UE policy to the UE.

[0069] In some implementations, the UE policy may be encapsulated in a container, which may be a container sent by the PCF to the AMF. Accordingly, after receiving the container, the AMF may transparently transmit the container directly to the UE. Transparent transmission may be understood as the AMF not being aware of or modifying the container.

[0070] In other implementations, the above-mentioned UE policy or container can be sent by the AMF to the UE through a NAS message (or a downlink NAS message).

[0071] In step S250, the UE sends the UE policy transmission result to the AMF.

[0072] In some implementations, the UE policy transmission result is used to indicate whether the UE successfully receives the UE policy.

[0073] In step S260, the AMF sends an N1 message notification (expressed as "Namf_N1MessageNotify") to the PCF to inform the PCF of the above UE policy transmission result.

[0074] In some implementations, the above-mentioned N1 message notification can be called "Manage UE policy complete message".

[0075] It should be noted that the above steps S220 and S260 may include two messages, namely a request and a response to the request. The method shown in FIG2 only shows the requests of the two steps, and does not show the two responses to the above two requests.

[0076] In addition, as described above, the PCF can send a container to the UE to transmit the UE policy. Conversely, the UE can also send a container to the PCF through the container. At this time, the container can be sent by the UE to the AMF through a non-access stratum (NAS) message (or uplink NAS message), and then transparently transmitted by the AMF to the PCF.

[0077] In the process shown in Figure 2, to convey UE policy, a "UE policy container" cause value is introduced into downlink NAS and uplink NAS messages. For example, the UE policy container cause value can be added to the payload container. Accordingly, after obtaining the UE policy container cause value, the AMF can perform a transparent transmission function to transparently transmit the container to the UE or PCF.

[0078] UE Strategy

[0079] UE policy may include UE route selection policy (URSP) and access network discovery and selection policy (ANDSP), etc. URSP is taken as an example below.

[0080] The URSP can indicate the binding relationship between application data and protocol data unit (PDU) sessions. In addition, the URSP can also indicate what type of PDU session the UE needs to establish to transmit application data. Generally, the URSP can include one or more URSP rules. The following describes the URSP rules in conjunction with Table 1.

[0081] As shown in Table 1, a URSP rule may include one or more of the following information: rule precedence, traffic descriptor (TD), application descriptors, IP descriptors, domain descriptors, non-IP descriptors, data network name (DNN), connection capabilities, and route selection descriptor (RSD) list.

[0082] It should be noted that each URSP rule in a URSP has a different rule priority. In other words, different URSP rules in a URSP correspond to different rule priorities.

[0083] Typically, when the characteristics of application data match the service descriptors in the URSP rules, the PDU session established based on the RSD in the URSP rules can be used to transmit the application data. This is the binding of application data to the PDU session described above. The following describes the RSD list in the URSP rules in conjunction with Table 2. Typically, the RSD list can include one or more RSDs.

[0084] Table 1: Structure of URSP rules

[0085] As shown in Table 2, the RSD may include one or more of the following information: RSD priority (route selection descriptor precedence), route selection components, session and service continuity mode selection (SSC mode selection), network slice selection, DNN selection, PDU session type selection, Non-Seamless offload indication, access type preference, route selection validation criteria, time window, and location criteria.

[0086] It should be noted that each piece of information in an RSD may be a single value or may contain multiple values. For example, the values ​​of S-NSSAI and DNN can be one or more. Therefore, each RSD can correspond to one or more parameter combinations, each parameter combination is a characteristic of a PDU session, and the service data corresponding to the service descriptor can be transmitted in the PDU session corresponding to a parameter value combination of the RSD. When an application data flow described by a service descriptor appears, the UE can select a parameter combination according to the corresponding RSD and initiate a PDU session establishment request.

[0087] Table 2: Structure of RSD

[0088] How to use URSP

[0089] The purpose of URSP is to allow the terminal to associate different services with corresponding PDU sessions for transmission based on URSP rules. The association process can be divided into steps 1 and 2.

[0090] In step 1, it is determined which URSP corresponding to the public land mobile network (PLMN) is to be used.

[0091] Generally, the URSP corresponding to a PLMN can be selected based on the following priority: the URSP corresponding to the registered PLMN takes precedence over the URSP corresponding to the equivalent PLMN of the registered PLMN. In addition, the URSP corresponding to the equivalent PLMN of the registered PLMN takes precedence over the URSP corresponding to the HPLMN (or non-VPLMN).

[0092] In step 2, an evaluation process is performed using URSP.

[0093] Generally, the process of finding a suitable PDU session for a service based on URSP can be called an evaluation process. In some implementations, when a new service appears and needs to transmit data, the terminal needs to determine which user plane connection (e.g., PDU session) to bind the data of the service to for transmission. To this end, the terminal uses URSP to check whether the characteristics of the service match the traffic descriptor (TD) of a certain rule in the URSP. The order of checking is determined by the priority (precedence) of the TD in the URSP, that is, the terminal checks the matching situation in order based on the priority. When a URSP corresponding to a TD is matched, the RSD list in the URSP can be used to bind the PDU session.

[0094] In some implementations, when the URSP corresponding to the TD matches the service, the terminal searches for a suitable PDU session according to the priority order in the RSD. The RSD with a high priority can be used first. If a parameter in the RSD has one or more values, the terminal can select a value of the parameter and combine it with other parameters to search for whether the PDU session exists.

[0095] In some implementations, if a PDU session exists, the service can be bound to the PDU session. Conversely, if the PDU session does not exist, the terminal triggers the establishment of the PDU session and carries the attribute parameters of the PDU session requested to be established in the PDU session establishment request message.

[0096] In some implementations, if the PDU session is successfully established, the terminal binds the service to the PDU session. Conversely, if the PDU session fails to be established, the terminal searches again for the existence of the PDU session based on other values ​​of a parameter in the RSD combined with other parameters.

[0097] In some implementations, if a suitable PDU session cannot be found for binding in the URSP, the terminal can search the TD in the second-priority URSP according to the priority order to see whether it can match the service data flow characteristics. When the TD in the second-priority URSP matches the service, the above evaluation process is repeated.

[0098] In some scenarios, after the above evaluation process, the terminal determines the PDU session that matches the service, and then the terminal may re-execute the evaluation process. In some implementations, in one or more of the following situations, the terminal may re-execute the evaluation process to determine whether the binding relationship between the service and the PDU session needs to be changed.

[0099] In some implementations, the above situations may include the PCF updating the URSP; the terminal moving from the EPC to the 5GS; the allowed NSSAI or configured NSSAI changing; the availability of the LADN DNN changing; the terminal registering over 3GPP access or non-3GPP access (UE registers over 3GPP or non-3GPP access); the terminal establishing a connection with the WLAN access.

[0100] Service transmission based on multi-access mode

[0101] Figure 3 is a schematic diagram of service transmission based on a multi-access method applicable to an embodiment of the present application. As shown in Figure 3, the current 3GPP system supports a multi-access PDU (MA-PDU) session mode based on a combination of 3GPP access and non-3GPP access. This means that a terminal can access the core network simultaneously through 3GPP access and non-3GPP access, and transmit data packets through either 3GPP access or non-3GPP access.

[0102] For example, the terminal can access the 3GPP access network, where the 3GPP access network and UPF1 can communicate through interface N3. Accordingly, UPF1 can communicate with the server through UPF PSA, where UPF1 and UPF PSA can communicate through interface N9, and UPF PSA and the server can communicate through interface N6.

[0103] The terminal can access a non-3GPP access network. Accordingly, the non-3GPP access network can communicate with UPF2 through a non-3GPP interworking function (N3IWF), wherein N3IWF and UPF2 can communicate through interface N3. UPF2 can communicate with the server through UPF PSA, wherein UPF2 and UPF PSA can communicate through interface N9, and UPF PSA and the server can communicate through interface N6.

[0104] In some implementations, 3GPP access may include one or more of the following: NR terrestrial network radio access technology, Evolved UMTS Terrestrial Radio Access (E-UTRA), and NR satellite access technology. NR satellite access technology may include one or more of the following: NR Geosynchronous Orbit (GEO) radio access technology, NR Medium Earth Orbit (MEO) radio access technology, and NR Low Earth Orbit (LEO) satellite access technology. In other implementations, non-3GPP access may include access based on wireless fidelity (WiFi).

[0105] In some scenarios, a terminal can access multiple networks simultaneously and use user plane connections in multiple networks to transmit services. This is also known as a multi-access scenario. For example, as shown in Figure 4A, a terminal can simultaneously access 3GPP access network 1 and 3GPP access network 2, and transmit services with user plane network element 1 in the core network through 3GPP access network 1, and with user plane network element 2 in the core network through 3GPP access network 2. However, current technologies do not specify how a terminal should use multiple networks for service transmission, resulting in low efficiency when a terminal accesses multiple networks for service transmission.

[0106] The applicant has discovered that different networks have different transmission performance characteristics. Therefore, to improve service transmission efficiency, different services can be transmitted over different networks. For example, if the service transmission latency on network 1 is lower than that on network 2, and the transmission latency required by service 1 is lower than that required by service 2, network 1 can be used to transmit service 1, and network 2 can be used to transmit service 2. However, determining the appropriate network for transmitting a service remains a pressing issue.

[0107] Therefore, in response to the above problems, the applicant proposed a wireless communication method, in which a first strategy is introduced, wherein the first strategy includes a first association relationship between the service and the network, so that the terminal can determine the first network associated with the first service based on the first association relationship, and transmit the first service through the first network to improve the transmission efficiency of the service in the multi-access scenario.

[0108] In some scenarios, the system architecture applicable to the embodiment of the present application can be applied to other architectures in addition to that shown in Figure 4A, which will be introduced below in conjunction with Figures 4B and 4C.

[0109] As shown in Figure 4B, the terminal can access 3GPP access network 1 and 3GPP access network 2 at the same time, and transmit services with UPF1 through 3GPP access network 1, and transmit services with UPF2 through 3GPP access network 2, where UPF1 and UPF2 transmit services with AF through the user plane anchor node (for example, anchor UPF).

[0110] When uplink service data is transmitted based on the architecture shown in Figure 4B, the uplink service data transmitted through UPF1 and UPF2 can be aggregated at the user plane anchor node and then sent to the AF. On the contrary, when downlink service data is transmitted based on the architecture shown in Figure 4B, the downlink service data can be diverted at the user plane anchor node and transmitted to the terminal through UPF1 and UPF2 respectively. In this scenario, the user plane connections corresponding to the multiple 3GPP access networks to which the terminal is respectively connected can correspond to the same IP address. Accordingly, for the AF, there is no need to distinguish between the multiple 3GPP access networks to which the terminal is connected. The AF can use only one IP address to transmit service data with the terminal, which helps to reduce the complexity of AF transmitting service data.

[0111] As shown in Figure 4C, the terminal can access 3GPP access network 1 and 3GPP access network 2 at the same time, and transmit services with UPF1 through 3GPP access network 1, and transmit services with UPF2 through 3GPP access network 2, where UPF1 and UPF2 transmit services with AF, that is, UPF1 and UPF2 do not need to transmit services with AF through the user plane anchor node.

[0112] Based on the architecture shown in Figure 4C, the user plane connections corresponding to 3GPP access network 1 and 3GPP access network 2 correspond to different UPFs. In this case, the two user plane connections correspond to different IP addresses. Accordingly, the AF needs to distinguish the IP addresses corresponding to different user plane connections when sending or receiving service data. The network topology shown in Figure 4C does not require associating multiple 3GPP accesses with the same user plane anchor node, which helps to simplify system complexity.

[0113] It should be noted that the above text, in conjunction with Figures 4A to 4C, introduces the scenario in which the terminal communicates based on multiple user plane connections in an embodiment of the present application. In some implementations, multiple user plane connections may correspond to one PDU session, or in other words, multiple user plane connections may correspond to the same PDU session. In other implementations, multiple user plane connections may correspond to different PDU sessions, for example, all user plane connections in the multiple user plane connections correspond to different PDU sessions. For another example, some user plane connections in the multiple user plane connections may correspond to different PDU sessions, while the remaining user plane connections may correspond to the same PDU session.

[0114] The following describes a wireless communication method according to an embodiment of the present application in conjunction with FIG5 . The method shown in FIG5 includes steps S510 to S520 .

[0115] In step S510, the terminal determines a first network associated with a first service based on a first policy, where the first policy includes a first association relationship between the service and the network.

[0116] In the embodiments of the present application, the network is not limited. In some implementations, the network may be a wireless network. For example, the network may be a PLMN. In another example, the network may be a non-public network (NPN). In another example, the network may be a stand-alone NPN (SNPN). Of course, the aforementioned networks may also be other networks introduced in future communication systems.

[0117] In step S520, the terminal transmits a first service through the first network.

[0118] In some implementations, the first association relationship may indicate that the first service is associated with one network (ie, the first network). In other implementations, the first association relationship may indicate that the first service is associated with multiple networks, including the first network.

[0119] In some implementations, the priorities corresponding to the multiple networks are different, where the priorities corresponding to the multiple networks are used to indicate a priority order for transmitting the first service through the corresponding networks. Assume that a first association relationship indicates that the first service is associated with network 1 and network 2, where the priority corresponding to network 2 is higher than the priority corresponding to network 1. In this case, the first service is preferentially transmitted through network 2.

[0120] In an embodiment of the present application, the first association relationship can be presented in the form of a list. At this time, the priorities corresponding to multiple networks can be arranged from high to low according to the presentation order in the list. Of course, the priorities corresponding to multiple networks can be arranged from low to high according to the presentation order in the list, which will be introduced in conjunction with Table 4 below.

[0121] Of course, in the embodiments of the present application, there may be no priority distinction between the multiple networks associated with the first service. In this case, one of the multiple networks may be selected to transmit the first service. For example, one of the multiple networks may be randomly selected to transmit the first service. In another example, the network to transmit the first service may be selected based on the busyness of the multiple networks, although this embodiment of the present application does not limit this.

[0122] In some implementations, the aforementioned network includes a PLMN. If the first association indicates that the first service is associated with multiple networks, and a first network among the multiple networks is a registered PLMN or an equivalent PLMN, the first network is used to transmit the first service. In other words, if the first association indicates that the PLMNs associated with the first service include a registered PLMN or an equivalent PLMN, the first service is preferentially transmitted through the registered PLMN or the equivalent PLMN, thereby simplifying the process of network selection by the terminal.

[0123] For example, if the multiple networks associated with a first service include a first network and a second network, and the first network is a registered PLMN or an equivalent PLMN, and the priority of the second network is higher than the priority of the first network, the first service is preferentially transmitted through the first PLMN.

[0124] In some implementations, the first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service. In other words, the first network can be associated with multiple services. Of course, in the embodiment of the present application, the first network can be associated with one service.

[0125] In the embodiments of the present application, the manner in which the network is indicated in the first policy is not limited. In some implementations, the network may be indicated by a network identifier. For example, if the network is a PLMN, the network identifier may be a PLMN ID. For example, if the network is an NPN, the network identifier may be an NPN ID. For example, if the network is an SNPN, the network identifier may be an SNPN ID.

[0126] In addition, in the embodiment of the present application, the service type in the first policy is not limited. In some implementations, the service type may include one or more of the following: IMS service, voice service, SMS service, video service, Internet service, FTP file transfer service, WeChat service, and Weibo service.

[0127] In some implementations, the traffic in the first policy may be represented by a traffic descriptor (TD).

[0128] Table 3

[0129] As shown in Table 3, the service descriptor may include one or more of the following parameters: IP descriptors; domain descriptors; non-IP descriptors; DNN information; connection capabilities; PIN ID; and connectivity group ID.

[0130] In some implementations, the IP descriptor is used to indicate a destination IP triplet. For example, the destination IP triplet may include: an IP address or an IPv6 network prefix; a port number; and a protocol ID of the protocol above IP.

[0131] In some implementations, the domain descriptor is used to describe a fully qualified domain name (FQDN) or a regular expression as a domain name matching criterion.

[0132] In some implementations, the non-IP descriptor is used to describe the purpose information of the non-IP service.

[0133] In some implementations, the above DNN information matches the DNN information of the business.

[0134] In some implementations, the connection capability matches information provided by a terminal service when requesting a network connection with certain functions.

[0135] In some implementations, the PIN ID matches the PIN ID of a specific PIN configured in the PEGC.

[0136] In some implementations, the connection group ID matches the connection group ID of a specific connection group in the 5G-RG.

[0137] In some scenarios, the terminal may be provided with multiple universal subscriber identity modules (USIMs). For example, the terminal may be connected to multiple different networks through multiple USIMs, or the terminal may initiate multiple registration requests, or the terminal may have multiple SUPIs. In this case, the terminal may use a first USIM among the multiple USIMs to transmit the first service through the first network. Of course, the solution in the embodiment of the present application is also applicable to a terminal provided with only one USIM.

[0138] In some implementations, the first USIM may be determined based on an association between the USIM and the network. For example, the first USIM may be a first USIM associated with the identifier of the first network, determined based on the identifier of the first network and the association between the USIM and the identifier of the network. That is, step S520 includes: the terminal selecting, from multiple USIMs, a first USIM associated with the first network based on the first network and the association between the multiple USIMs and the network; and the terminal transmitting the first service via the first network using the first USIM.

[0139] In the embodiment of the present application, the first network is associated with the first USIM, or in other words, the first network and the first USIM have an associated relationship. This can be understood as the first network being the registered network of the first USIM, or in other words, a registration request is sent to the first network via the first USIM. Of course, in the embodiment of the present application, the first network is associated with the first USIM, and the SUPI of the first USIM includes the identifier of the first network. For example, if the first network is the first PLMN, the first PLMN is associated with the first USIM, and the SUPI of the first USIM includes the PLMN ID of the first PLMN.

[0140] In some implementations, the first strategy includes a second association relationship between the service and the preemption priority, wherein the preemption priority indicates the priority of the service to occupy the associated network for transmission, or in other words, the preemption priority indicates the priority of the service to preempt the associated network for transmission, or in other words, the preemption priority indicates the order in which the service preempts the associated network for transmission.

[0141] For example, network 1 is associated with service 1 and service 2, and the preemption priority associated with service 1 is lower than the preemption priority associated with service 2. Assuming that the terminal cannot transmit service 1 and service 2 simultaneously through network 1, if data for service 2 needs to be transmitted while the terminal is transmitting service 1 through network 1, the terminal will preferentially transmit the data for service 2 through network 1. The reason why the terminal cannot transmit service 1 and service 2 simultaneously through network 1 can be found in the description below in conjunction with the first condition.

[0142] For another example, network 1 is associated with service 1, network 2 is associated with service 2, and the preemption priority associated with service 1 is lower than the preemption priority associated with service 2. Assuming that the terminal cannot transmit services 1 and 2 simultaneously, if data for service 2 needs to be transmitted while the terminal is transmitting service 1 through network 1, the terminal will preferentially transmit the data for service 2 through network 2. The reason why the terminal cannot transmit services 1 and 2 simultaneously through network 1 can be found in the description below in conjunction with the first condition.

[0143] In the embodiment of the present application, by introducing the second association relationship into the first strategy to indicate the preemption priority of the service association, it helps to improve the rationality of the terminal in determining the order of transmitting different services.

[0144] In some implementations, the second association relationship indicates that the preemption priority of the second service is higher than the preemption priority of the first service. When the first condition is met, the transmission of the second service can preempt the resources of the first service, or in other words, when the first condition is met, the second service is preferentially transmitted through the second network, where the resources may include relevant resources of the terminal transmission service, for example, the resources may include the user plane connection of the terminal.

[0145] In some implementations, the first condition includes one or more of the following: the terminal does not support simultaneous transmission of the first service on the first network and the second service on the second network; the terminal does not support simultaneous transmission of the first service and the second service through multiple RATs; during the process of simultaneous transmission by the terminal through multiple networks, the number of multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; during the process of simultaneous transmission by the terminal through multiple RATs, the number of multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

[0146] In the embodiments of the present application, the method for preferentially transmitting the second service over the second network is not limited. For example, preferentially transmitting the second service over the second network may include stopping transmission of the first service over the first network and transmitting the second service over the second network. For another example, preferentially transmitting the second service over the second network may include suspending transmission of the first service over the first network and transmitting the second service over the second network; later, after transmission of the second service is completed, resuming transmission of the first service.

[0147] In the embodiments of the present application, the manner in which the preemption priority is set is not limited. In some implementations, the preemption priority can be set to multiple levels. For example, the preemption priority can include a high level, a medium level, and a low level. For another example, the preemption priority can include a high level and a low level.

[0148] In some implementations, the first policy includes a third association between the network and the RAT type. Different networks may support different RAT types. Therefore, introducing the third association into the first policy helps the terminal obtain the RAT types associated with different networks.

[0149] In the embodiments of the present application, there is no limitation on the RAT type. In some implementations, the RAT type may include one or more of the following: NR terrestrial network radio access technology, Evolved UMTS Terrestrial Radio Access (E-UTRA), NR satellite access technology, NR Geosynchronous Orbit (GEO) radio access technology, NR Medium Earth Orbit (MEO) radio access technology, and NR Low Earth Orbit (LEO) satellite access technology.

[0150] In some implementations, the third association relationship may indicate that the first network is associated with one RAT type. In other implementations, the third association relationship may indicate that the first network is associated with multiple RAT types.

[0151] In some implementations, the priorities associated with the multiple RAT types are different, where the priorities associated with the multiple RAT types are used to indicate the priority of accessing the network using the associated RAT type. Assume that a third association indicates that network 1 is associated with RAT type 1 and RAT type 2, where the priority associated with RAT type 2 is higher than the priority associated with RAT type 1. In this case, the first service preferentially accesses network 1 based on RAT type 2.

[0152] In an embodiment of the present application, the third association relationship can be presented in the form of a list. At this time, the priorities corresponding to multiple RAT types can be arranged from high to low according to the presentation order in the list. Of course, the priorities corresponding to multiple RAT types can be arranged from low to high according to the presentation order in the list, which will be introduced in conjunction with Table 4 below.

[0153] Of course, in the embodiments of the present application, there may be no priority distinction between the multiple RAT types associated with the first network. In this case, one of the multiple RAT types may be selected to access the first network. For example, one of the multiple RAT types may be randomly selected to access the first network. In another example, a currently available RAT type may be selected from multiple RAT types to access the first network, but this embodiment of the present application is not limited to this.

[0154] In some scenarios, a terminal may be configured with multiple USIMs. For example, the terminal may be connected to multiple different networks through multiple USIMs, or the terminal may have initiated multiple registration requests, or the terminal may have multiple SUPIs. In this case, the terminal may select a first USIM associated with the RAT type of the first network from the multiple USIMs based on the RAT type associated with the first network and the association between the USIM and the RAT type.

[0155] In some implementations, the terminal includes multiple USIMs, and the above step S520 includes: the terminal selects a first USIM associated with the RAT type of the first network from the multiple USIMs based on the RAT type associated with the first network and the association relationship between the USIM and the RAT type; and the terminal uses the first USIM to access the first network to transmit the first service.

[0156] In the embodiment of the present application, the RAT type of the above-mentioned first network is associated with the first USIM, or in other words, there is an association relationship between the RAT type and the first USIM, which can be understood as the first USIM using the RAT type associated with the first network to register and / or establish a user plane connection.

[0157] In some implementations, the first strategy includes a fourth association relationship between the network and the system type. Different networks may support different system types. Therefore, introducing the fourth association relationship into the first strategy helps the terminal obtain system types associated with different networks.

[0158] In some implementations, the system type is also referred to as the "network type," where the network type may include a 5G system (5GS) and an evolved packet system (EPS). For example, if the system type is used to indicate the type of non-access stratum (NAS) message in the network, the non-access stratum (NAS) message type may include a 5GS-based NAS message type and an EPS-based NAS message type. Of course, in the embodiments of the present application, the system type may also include the core network type in the network.

[0159] In some implementations, the terminal includes multiple USIMs, and the above step S520 includes: the terminal selects a first USIM associated with the system type of the first network from the multiple USIMs based on the system type associated with the first network and the association relationship between the USIM and the system type; and the terminal uses the first USIM to access the first network to transmit the first service.

[0160] In the embodiment of the present application, the RAT type of the first network is associated with the first USIM, which can be understood as the first USIM using the RAT type associated with the first network to register and / or establish a user plane connection.

[0161] The above describes the first to fourth association relationships in the embodiments of the present application. In the embodiments of the present application, the association relationships in the above embodiments can be used alone or in combination with each other. If the first association relationship and the third association relationship are used in combination with each other, the first association relationship and the third association relationship can be combined, that is, the first association relationship includes the association relationship between the service and the network, and the second association relationship includes the association relationship between the network and the RAT type. Accordingly, the combination of the first association relationship and the third association relationship can be expressed as an association relationship between the service, the network, and the RAT type. In this case, the third association relationship can be replaced by the association relationship between the service and the RAT type.

[0162] If the first association relationship and the fourth association relationship are used in combination with each other, the first association relationship and the fourth association relationship can be combined. That is, the first association relationship includes the association relationship between the business and the network, and the fourth association relationship includes the association relationship between the network and the system type. Accordingly, the combination of the first association relationship and the fourth association relationship can be expressed as the association relationship between the business, the network, and the system type. In this case, the fourth association relationship can be replaced by the association relationship between the business and the system type.

[0163] It should be noted that the association relationships from the first association relationship to the fourth association relationship can be arbitrarily combined, and the combination method is similar to that introduced above. For the sake of brevity, they will not be described in detail below.

[0164] For ease of understanding, the following takes the first strategy including the first to fourth association relationships as an example, and introduces the first strategy in the embodiment of the present application in combination with Table 4.

[0165] Table 4

[0166] As shown in Table 4, in the first association relationship included in the first policy, service 1 is associated with PLMN1 and PLMN2, and the priority of PLMN1 is higher than the priority of PLMN2. Service 2 is associated with PLMN2. Service 3 is associated with NPN1 and PLMN1, and the priority of NPN1 is higher than the priority of PLMN1.

[0167] In the second association relationship included in the first policy, the preemption priority associated with service 1 is level 1, the preemption priority associated with service 2 is level 3, and the preemption priority associated with service 3 is level 5. Generally, a smaller preemption priority level indicates a higher preemption priority. In other words, the preemption priority associated with service 1 is higher than the preemption priority associated with service 2, and the preemption priority associated with service 2 is higher than the preemption priority associated with service 3.

[0168] In the third association relationship included in the first strategy, the RAT type of the network associated with service 1 includes NR terrestrial network RAT, E-UTRA, and satellite-based RAT; the RAT type of the network associated with service 2 includes E-UTRA and satellite-based RAT; the RAT type of the network associated with service 3 includes NR.

[0169] In the fourth association relationship included in the first policy, the RAT types of the network associated with service 1 include 5GS and EPS. The network system types associated with services 2 and 3 are not limited.

[0170] As described above, a service can correspond to multiple networks. In this case, the association relationship between the service and the multiple networks can be an independent row in the list representing the first strategy. For example, as shown in Table 4, the association relationship between service 1 and PLMN1 and the association relationship between service 1 and PLMN2 can be a row in the list. Of course, in an embodiment of the present application, the association relationship between the service and the multiple networks can occupy multiple rows in the list representing the first strategy. For example, the association relationship between service 1 and PLMN1 can be a row in the list, and the association relationship between service 1 and PLMN2 can be another row in the list, that is, the association relationship between service 1 and the network (PLMN1 and PLMN2) can occupy two independent rows.

[0171] In addition, the above description uses the presentation of the first association in the list as an example. In the embodiment of the present application, the presentation of one or more of the second association, the third association, and the fourth association in the list can be similar to the presentation of the first association described above. For the sake of brevity, it will not be repeated below.

[0172] As described above, the third association relationship and / or the fourth association relationship can be carried in the first policy, which helps to reduce the changes to the traditional UE policy to be compatible with the traditional communication process. In other scenarios, the third association relationship and / or the fourth association relationship can be carried in the UE policy to match the purpose of introducing the UE policy in the traditional communication process. At this time, the UE policy carrying the third association relationship and / or the fourth association relationship can also be called an "enhanced UE policy". Taking the UE policy as URSP as an example, the URSP carrying the third association relationship and / or the fourth association relationship can be called an "enhanced URSP".

[0173] It should be understood that the third association relationship and / or fourth association relationship carried in the UE policy are the same as the third association relationship and fourth association relationship carried in the first policy, and can be referred to above. The following mainly describes how the third association relationship and / or fourth association relationship are carried in the UE policy.

[0174] In some implementations, the third and / or fourth association relationships are carried in the URSP's routing descriptor (RSD). For example, the third and / or fourth association relationships are carried in the RSD's access type priority information, as described below in conjunction with Table 5. For another example, the third and / or fourth association relationships are dedicated information in the RSD, as described below in conjunction with Table 6. It should be noted that for an introduction to other parameters in the RSD, see Table 2 above. The following description, in conjunction with Tables 5 and 6, primarily discusses how the third and / or fourth association relationships are carried.

[0175] As shown in Table 5, assuming that RAT type 1 includes satellite-based RAT, system type 1 includes 5GS, and the RSD shown in Table 5 belongs to the URSP matching service 1, the access type priority of the RSD indicates that the RAT type of the network associated with service 1 is satellite-based RAT, and the system type of the network associated with service 1 is 5GS.

[0176] As shown in Table 6, assuming that RAT type 1 includes a satellite-based RAT, system type 1 includes 5GS, and the RSD shown in Table 6 belongs to a URSP matching service 1, then dedicated information "RAT type" can be newly introduced in the RSD to indicate that the RAT type of the network associated with service 1 is a satellite-based RAT. In addition, dedicated information "system type" can be newly introduced in the RSD to indicate that the system type of the network associated with service 1 is 5GS.

[0177] It should be noted that the above-mentioned dedicated information may be one piece of information, that is, a new piece of dedicated information may be introduced into the RSD to indicate both the “RAT type” and the “system type”.

[0178] Table 5

[0179] Table 6

[0180] The above introduces the first strategy and the enhanced UE strategy in the embodiment of the present application. The following introduces the usage process of the first strategy and the enhanced UE strategy in the embodiment of the present application.

[0181] In some implementations, assuming that the third association relationship is carried by the first strategy, the above method also includes: the terminal determines the RAT type associated with the first network based on the third association relationship; the above step S520 includes: the terminal accesses the first network based on the RAT type associated with the first network to transmit the first service.

[0182] In some implementations, assuming that the fourth association relationship is carried in the first policy, before step S520, the method further includes: the terminal determining the system type associated with the first network based on the fourth association relationship.

[0183] In some implementations, the first association relationship indicates that the first service is associated with the first network and the second network, and the above-mentioned step S520 includes: if the second condition is met, the terminal transmits the first service through the first network, wherein the second condition includes one of the following: the first service does not match the URSP rules corresponding to the second network; the first service cannot be transmitted through the PDU session corresponding to any RSD in the matching URSP rules corresponding to the second network, wherein the matching URSP rule can be understood as the URSP rule that matches the first service.

[0184] For ease of understanding, the following describes a method for using the first strategy in an embodiment of the present application in conjunction with Figure 6. Assuming that the third association relationship and the fourth association relationship are carried in a URSP, as shown in Figure 6, the method includes steps S610 to S640.

[0185] In step S610 , service 1 occurs.

[0186] In some implementations, the emergence of service 1 may be understood as activation of service 1, or data of service 1 is about to be sent, or data of service 1 has not yet been determined through which user plane connection to transmit.

[0187] In step S620, the terminal determines the PLMN associated with service 1 based on the first policy.

[0188] In some implementations, as shown in FIG4 , service 1 is associated with PLMN1 and PLMN2, and PLMN1 has a higher priority than PLMN2. The terminal then preferentially selects PLMN1 as the PLMN associated with service 1.

[0189] In step S630, if the selected PLMN has a corresponding URSP, a URSP evaluation process is performed, and the RAT associated with the PLMN and the system type associated with the PLMN are determined based on the URSP.

[0190] During the URSP evaluation process, if there is a URSP rule that can match service 1 among all URSP rules or non-completely matched (match-all) URSP rules corresponding to the selected PLMN, a suitable RAT is selected according to the RAT type contained in the RSD in the URSP rule, and based on the RAT, the PDU session (or user plane connection) corresponding to the RSD in the matching URSP rule is used to transmit the data of service 1, that is, service 1 is successfully bound to the PDU session, and step S640 is executed.

[0191] It should be noted that the above-mentioned PDU session may be an established PDU session or a PDU session to be established.

[0192] During the URSP evaluation process, if any of the following situations occurs, the binding of service 1 to the PDU session fails. Accordingly, the terminal selects the second-priority PLMN2 according to the first strategy and re-executes steps S620 to S630, that is, performing URSP evaluation based on the URSP corresponding to PLMN2.

[0193] Case 1: The selected PLMN does not have a corresponding URSP;

[0194] Case 2: During the URSP evaluation process, all corresponding URSP rules or non-completely matched URSP rules cannot match Business 1;

[0195] Case 3: During the URSP evaluation process, the PDU session of the RSD corresponding to the matching URSP rule cannot be used for data transmission, or in other words, the PDU session cannot be established based on the RSD corresponding to the matching URSP rule.

[0196] In some implementations, assuming that the third association relationship and / or the fourth association relationship are carried by the UE policy, the above method includes: the terminal determines the radio access technology RAT type associated with the first network based on the UE policy, and the UE policy includes the association relationship between the network and the RAT (for example, the third association relationship introduced above); and / or the terminal determines the system type associated with the first network based on the UE policy, and the UE policy includes the association relationship between the network and the system type, and the system type indicates the type of the core network and / or the type of the non-access network in the associated network (for example, the fourth association relationship introduced above).

[0197] In some implementations, if the URSP corresponding to the first network matches the first service, the first service is transmitted via a first PDU session, and the first PDU session corresponds to the RSD in the URSP corresponding to the first network. In other words, the first strategy can be used in conjunction with a traditional URSP, helping to improve the compatibility of the first strategy with traditional communication processes. Of course, in the embodiments of the present application, the first strategy can be used alone.

[0198] In some implementations, the first association relationship indicates that the first service is associated with the first network and the second network, and the above-mentioned step S520 includes: if the second condition is met, the terminal transmits the first service through the first network, wherein the second condition includes one of the following: the first service does not match the URSP rules corresponding to the second network; the first service cannot be transmitted through the PDU session corresponding to the RSD in the matching URSP rule corresponding to the second network.

[0199] For ease of understanding, the following describes a method for using the first strategy in an embodiment of the present application in conjunction with Figure 7. Assuming that the third association relationship and the fourth association relationship are carried in a URSP, as shown in Figure 7, the method includes steps S710 to S740.

[0200] In step S710 , service 1 occurs.

[0201] In some implementations, the emergence of service 1 may be understood as activation of service 1, or data of service 1 is about to be sent, or data of service 1 has not yet been determined through which user plane connection to transmit.

[0202] In step S720, the terminal determines the PLMN associated with service 1, the RAT associated with the PLMN, and the system type associated with the PLMN based on the first policy.

[0203] In some implementations, as shown in FIG4 , service 1 is associated with PLMN1 and PLMN2, and PLMN1 has a higher priority than PLMN2. The terminal then preferentially selects PLMN1 as the PLMN associated with service 1.

[0204] In step S730, if the selected PLMN has a corresponding URSP, the URSP evaluation process is performed.

[0205] During the URSP evaluation process, if there is a URSP rule that can match service 1 among all URSP rules or non-completely matched (match-all) URSP rules corresponding to the selected PLMN, the PDU session (or user plane connection) corresponding to the RSD in the matching URSP rule is used to transmit the data of service 1, that is, service 1 is successfully bound to the PDU session, and step S740 is executed.

[0206] It should be noted that the above-mentioned PDU session may be an established PDU session or a PDU session to be established.

[0207] During the URSP evaluation process, if any of the following situations occurs, the binding of service 1 to the PDU session fails. Accordingly, the terminal selects the second-priority PLMN2 according to the first strategy and re-executes steps S720 to S730, that is, performing URSP evaluation based on the URSP corresponding to PLMN2.

[0208] Case 1: The selected PLMN does not have a corresponding URSP;

[0209] Case 2: During the URSP evaluation process, all corresponding URSP rules or non-completely matched URSP rules cannot match Business 1;

[0210] Case 3: During the URSP evaluation process, the PDU session of the RSD corresponding to the matching URSP rule cannot be used for data transmission, or in other words, the PDU session cannot be established based on the RSD corresponding to the matching URSP rule.

[0211] The following describes a method for using preemption priority in an embodiment of the present application in conjunction with Figure 8. The method shown in Figure 8 includes steps S810 to S840. Assume that the terminal does not support simultaneous data transmission on multiple PLMNs or multiple RATs.

[0212] In step S810, service 2 appears, and the terminal binds service 2 to the user plane connection corresponding to PLMN2 and E-UTRA according to the first policy and URSP, wherein the first policy is shown in Table 4.

[0213] In step S820, service 1 appears, and the terminal binds service 1 to the user plane connection corresponding to PLMN1 and NR terrestrial radio access technology according to the first policy and URSP requirements.

[0214] In step S830, since the preemption priority of service 1 is higher than that of service 2, the terminal stops or releases the user plane connection associated with service 2 (or, the user plane connections of all PLMN2 and E-UTRA associated with service 2), and starts to establish a user plane connection based on PLMN1 and NR associated with service 1 to transmit the data of service 1.

[0215] It should be noted that, since the user plane connection of PLMN2 and E-UTRA has been stopped or released, the terminal can determine a suitable user plane connection for service 2 according to the URSP associated with PLMN1.

[0216] The above describes how to use the first strategy and the UE strategy in the embodiment of the present application. The following describes the transmission method of the first strategy and the UE strategy in the embodiment of the present application.

[0217] The first strategy transmission method

[0218] In some implementations, the above method further includes: the first core network device sending configuration information to the terminal, where the configuration information is used to configure the first policy for the terminal.

[0219] In some implementations, the first core network device is an AMF. In other implementations, the first core network device is a PCF. Accordingly, the above configuration information can be sent by the PCF to the terminal via the AMF. For example, the first policy can be configured for the terminal by the PCF through a UCU process (for example, as shown in FIG2 ).

[0220] In some implementations, the method further includes: a second core network device sending a registration response message to the terminal, wherein the registration response message carries the first policy. The second core network device may be an AMF.

[0221] Enhanced UE policy transmission method

[0222] In some implementations, taking the enhanced UE policy including URSP as an example, the above method further includes: the first core network device sends configuration information to the terminal, where the configuration information is used to configure the URSP for the terminal.

[0223] In some implementations, the first core network device is an AMF. In other implementations, the first core network device is a PCF. Accordingly, the configuration information may be sent by the PCF to the terminal via the AMF. For example, the first policy may be configured for the terminal by the PCF through a UCU process (e.g., as shown in FIG2 ).

[0224] In some implementations, the method further includes: the second core network device sending a registration response message to the terminal, wherein the registration response message carries the URSP. The second core network device may be an AMF.

[0225] With the development of communication systems, various types of communication devices have been introduced, and the capabilities of different communication devices vary significantly. In this case, if the first policy and / or UE policy are uniformly configured for the communication devices, the associated services may not be transmitted. For example, a terminal determines, based on the first policy and / or UE policy, that the access method associated with a first service is access method 1. However, the network device does not support the network accessed by the terminal using access method 1. In this case, the first service cannot be transmitted over the network using access method 1.

[0226] Therefore, to address the above issues, an embodiment of the present application provides a wireless communication method, in which first information can be transmitted between communication devices (also referred to as a "first device" and a "second device"). The first information carries capability information associated with the network access method, which helps to improve the success rate of the first service transmission. The wireless communication method of an embodiment of the present application is described below in conjunction with Figure 9.

[0227] In the embodiments of the present application, the first device and / or the second device are not limited. In some implementations, the first device may be a terminal, and the second device may be a network device. In other implementations, the first device may be a network device, and the second device may be a terminal. Of course, in the embodiments of the present application, both the first device and the second device may be terminals. It should be understood that the network device mentioned above may be a core network device, such as an AMF or PCF.

[0228] In step S910, the first device sends a first message to the second device. The first message carries capability information associated with the network access method. For example, the capability information carried in the first message may be the capability information of the terminal. For another example, the capability information carried in the first message may be the capability information of the network device.

[0229] In the embodiments of the present application, the network access method is not limited. In some implementations, the network access method may include a 3GPP access method and / or a non-3GPP access method. In other implementations, the network access method may include multiple wireless access technologies in the 3GPP access method. For example, the network access method may include one or more of the following: NR terrestrial network wireless access technology, evolved UMTS terrestrial wireless access E-UTRA, NR satellite access technology, NR geosynchronous orbit GEO wireless access technology, NR medium earth orbit MEO wireless access technology, and NR low earth orbit LEO.

[0230] In some implementations, the capability information is used to indicate one or more of the following: whether network access based on multiple network access methods is supported; and whether access method switching based on multiple network access methods is supported.

[0231] Taking the capability information used to indicate whether network access based on multiple network access methods is supported as an example, the capability information can be understood as being used to indicate whether guidance (steer) in multiple network access methods is supported, or in other words, the capability information is used to indicate whether it supports selecting a user plane connection of a network (including one or more of the access network, RAT type, and system type) to transmit services.

[0232] Taking the capability information used to indicate whether access mode switching based on multiple network access modes is supported as an example, the capability information is also called switching capability.

[0233] In some implementations, because different access methods may be associated with different networks, access method switching based on multiple network access methods may also be accompanied by network switching. Therefore, the above-mentioned switching capability can be understood as indicating whether a service can be switched from one network to another. Of course, in the embodiments of the present application, different access methods may be associated with the same network. In this case, access method switching based on multiple network access methods may not be accompanied by network switching.

[0234] In some implementations, multiple user plane connections can be established based on multiple access methods. Accordingly, the above-mentioned capability information is used to indicate one or more of the following: whether to support transmission of different data in the same service through multiple user plane connections; whether to support non-simultaneous transmission through multiple user plane connections; whether to support simultaneous transmission through multiple user plane connections; whether to support transmission through multiple user plane connections using one USIM; whether to support transmission through multiple user plane connections using multiple USIMs; whether to support transmission through multiple user plane connections using one SUPI; whether to support transmission through multiple user plane connections using multiple SUPIs; and the type of core network that supports the use of multiple user plane connections.

[0235] For example, capability information indicating whether different data in the same service can be transmitted through multiple user plane connections is supported. This capability information is also called "split capability." For example, this capability information indicates the ability to split among multiple 3GPP accesses.

[0236] For example, the capability information is used to indicate whether non-simultaneous transmission over multiple user plane connections is supported. In other words, the capability information is used to indicate whether services can be transmitted over multiple user plane connections at different times. For example, the capability information is used to indicate whether services can be transmitted over only one user plane connection at a time.

[0237] For example, the capability information is used to indicate whether simultaneous transmission via multiple user plane connections is supported. In other words, the capability information is used to indicate whether services can be transmitted via multiple user plane connections at the same time. For example, the capability information is used to indicate whether services can be transmitted via multiple user plane connections at one time.

[0238] The capability information is used to indicate whether transmission through multiple user plane connections using one USIM is supported, or in other words, the capability information is used to indicate whether multiple user plane transmissions are supported through one USIM.

[0239] The capability information is used to indicate whether the use of multiple USIMs for transmission through multiple user plane connections is supported, or in other words, the capability information is used to indicate whether multiple user plane transmission is supported through multiple USIMs, where different USIMs in the multiple USIMs may correspond to different user plane connections.

[0240] The capability information is used to indicate whether transmission through multiple user plane connections using one SUPI is supported, or in other words, the capability information is used to indicate whether multiple user plane transmissions are supported through one SUPI.

[0241] The capability information is used to indicate whether the use of multiple SUPIs for transmission over multiple user plane connections is supported, or in other words, the capability information is used to indicate whether multiple user plane transmissions are supported over multiple SUPIs, where different SUPIs in the multiple SUPIs may correspond to different user plane connections.

[0242] For example, the capability information is used to indicate the type of core network that supports the use of multiple user plane connections. In other words, the capability information is used to indicate the type of core network that supports the use of multiple user plane connections. The core network type may include 5GS and / or EPS. Of course, in the embodiment of the present application, the core network type may be replaced by the type of NAS message, wherein the NAS message type may include a NAS message transmitted based on 5GS and / or a NAS message transmitted based on EPS.

[0243] In some implementations, the above method also includes: the first device receives second information sent by the second device, and the second information includes one or more of the following: available capability information in the capability information carried by the first information; capability information supported by the second device in the capability information carried by the first information; capability information allowed to be used by the second device in the capability information carried by the first information; and UE policy used by the first device.

[0244] Taking the example that the second information includes the available capability information in the capability information carried by the first information, that is, the second device can indicate the available capability information in the capability information carried by the first information through the second information, and / or the second device can indicate the unavailable capability information in the capability information carried by the first information through the second information.

[0245] Taking the example of the second information including the capability information supported by the second device in the capability information carried by the first information, that is, the second device can indicate the capability information supported by the second device in the capability information carried by the first information through the second information, and / or the second device can indicate the capability information not supported by the second device in the capability information carried by the first information through the second information.

[0246] Taking the example of the second information including the capability information that the second device is allowed to use in the capability information carried by the first information, that is, the second device can indicate the capability information that the second device is allowed to use in the capability information carried by the first information through the second information, and / or the second device can indicate the capability information that the second device is not allowed to use in the capability information carried by the first information through the second information.

[0247] Taking the example that the second information includes the UE policy used by the first device, the UE policy used by the first device corresponds to the capability information of the first device, or in other words, the UE policy used by the first device corresponds to the capability information carried by the first information, or in other words, the UE policy used by the first device is determined based on the capability information carried by the first information.

[0248] In the embodiment of the present application, the above UE policy may be, for example, URSP. Of course, in the embodiment of the present application, the UE policy may also be other policies introduced in future communication systems.

[0249] The above describes the capability information in the embodiment of the present application, and the following describes the transmission scheme of the capability information in the embodiment of the present application.

[0250] In some implementations, the second information is carried in one or more of the following: a registration response message; configuration information, where the configuration information is used to configure a UE policy for the terminal.

[0251] In some implementations, the first information is carried in a registration request, and the registration request is used to request registration of the terminal.

[0252] In some implementations, the registration request carries a UE policy container, and the UE policy container includes the first information; or the registration request carries the UE policy container and the first information.

[0253] In some implementations, the registration request is typically sent by the terminal device to the PCF via the AMF.

[0254] In some implementations, the second information may be determined by the PCF based on the first information. For example, since the AMF generally does not process information in a UE policy container, if the first information is carried in a UE policy container, the AMF directly forwards the UE policy container to the PCF, and the PCF determines the second information based on the first information.

[0255] In other implementations, the second information may be determined by the AMF based on the first information. For example, if the first information is the terminal's capability information, carried in the registration request and located outside the UE policy container, the AMF may obtain the terminal's capability information and, after the PCF sends the network device's capability information, determine the second information based on the terminal's capability information and the network device's capability information. For the network device's capability information, refer to the above description of the first information.

[0256] In the embodiment of the present application, the above-mentioned capability information transmission scheme can be used in combination with the transmission mode of the first strategy and the UE strategy to improve the success rate of the transmission service.

[0257] Figure 10 is a schematic flow chart of a wireless communication method according to an embodiment of the present application. The method shown in Figure 10 includes steps S1010 to S1040.

[0258] In step S1010, the terminal sends a registration request to the AMF, where the UE policy container of the registration request includes the capability information of the terminal (as an example of the first information).

[0259] In step S1020, the AMF sends a UE policy container to the PCF, where the UE policy container includes the capability information of the terminal.

[0260] In step S1030, the PCF determines second information according to the capability information of the terminal.

[0261] In step S1040, the PCF sends the first policy, the enhanced UE policy, and the second information to the terminal through the AMF.

[0262] In some implementations, the PCF may send the first policy, the enhanced UE policy, and the second information to the terminal by triggering a UCU process (eg, the method described above in conjunction with FIG. 2 ).

[0263] It should be noted that PCF can also refer to the contract information (for example, contract information from UDM / UDR) to determine the second information, which may contain content that is the same or similar to the first information to help the core network control plane network element determine the reply content of the second information.

[0264] Figure 11 is a schematic flow chart of a wireless communication method according to another embodiment of the present application. The method shown in Figure 11 includes steps S1110 to S1140.

[0265] In step S1110, the terminal sends a registration request to the AMF, where the registration request includes the capability information of the terminal (as an example of the first information). In some implementations, the first policy may be located outside the UE policy container.

[0266] In step S1120, the AMF sends the terminal capability information to the PCF.

[0267] In step S1130, the PCF sends the capability information of the network device and the first policy to the AMF.

[0268] In step S1140, the AMF generates second information based on the capability information of the terminal and the capability information of the network device.

[0269] It should be noted that the AMF can also refer to the contract information (for example, contract information from UDM / UDR) to determine the second information, which may contain content that is the same or similar to the first information to help the core network control plane network element determine the reply content of the second information.

[0270] In step S1150, the AMF sends the first policy and the second information to the terminal.

[0271] In some implementations, the PCF may send the first policy and the second information to the terminal by triggering a UCU process (eg, the method described above in conjunction with FIG. 2 ).

[0272] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 11. The device embodiment of the present application is described in detail below in conjunction with Figures 12 to 18. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0273] FIG12 is a schematic diagram of a terminal according to an embodiment of the present application. The terminal 1200 shown in FIG12 includes: a processing unit 1210 .

[0274] The processing unit 1210 is configured to determine a first network associated with a first service based on a first policy, wherein the first policy includes a first association relationship between the service and the network; and

[0275] The processing unit 1210 is configured to transmit the first service through the first network.

[0276] In some implementations, the first association relationship indicates that the first service is associated with multiple networks, where the multiple networks include the first network, and the multiple networks have different corresponding priorities.

[0277] In some implementations, the network includes a PLMN. If the first association relationship indicates that the first service is associated with multiple networks, and the first network among the multiple networks is a registered PLMN or an equivalent PLMN, the first network is used to transmit the first service.

[0278] In some implementations, the multiple networks include the first network and a second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

[0279] In some implementations, the first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service.

[0280] In some implementations, the terminal includes multiple USIMs, and the processing unit 1210 is configured to use a first USIM among the multiple USIMs to transmit the first service through the first network.

[0281] In some implementations, the first USIM is determined based on an association relationship between the USIM and a network.

[0282] In some implementations, the first policy includes a second association between the service and a preemption priority, where the preemption priority indicates a priority for the service to occupy an associated network for transmission.

[0283] In some implementations, the second association relationship indicates that the preemption priority of the second service is higher than the preemption priority of the first service, and when the first condition is met, the transmission of the second service preempts the resources for transmitting the first service, wherein the first condition includes one or more of the following: the terminal does not support simultaneous transmission of the first service on the first network and the second service on the second network; the terminal does not support simultaneous transmission of the first service and the second service through multiple wireless access technologies RAT; during the process of simultaneous transmission by the terminal through multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; during the process of simultaneous transmission by the terminal through multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

[0284] In some implementations, the processing unit 1210 is configured to determine, based on a UE policy, a radio access technology RAT type associated with the first network, wherein the UE policy includes an association relationship between the network and the RAT type; and / or determine, based on the UE policy, a system type associated with the first network, wherein the UE policy includes an association relationship between the network and the system type, wherein the system type indicates a type of a core network and / or a type of a non-access stratum NAS message in the associated network.

[0285] In some implementations, the first policy includes a third association between the network and a RAT type.

[0286] In some implementations, the third association relationship indicates that the first network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

[0287] In some implementations, the processing unit 1210 is configured to determine a RAT type associated with the first network based on the third association relationship; and access the first network based on the RAT type associated with the first network to transmit the first service.

[0288] In some implementations, the terminal includes multiple USIMs, and the processing unit 1210 is configured to select a first USIM from the multiple USIMs based on the RAT type associated with the first network, and the first USIM uses the RAT type associated with the first network to register and / or establish a user plane connection; and use the first USIM to access the first network to transmit the first service.

[0289] In some implementations, the RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geosynchronous orbit GEO radio access technology, NR medium earth orbit MEO radio access technology, and NR low earth orbit LEO.

[0290] In some implementations, the first policy includes a fourth association relationship between the network and a system type, where the system type indicates a type of a core network in the network and / or a type of a non-access stratum (NAS) message in the network.

[0291] In some implementations, the processing unit 1210 is configured to determine a system type associated with the first network based on the fourth association relationship.

[0292] In some implementations, the terminal further includes: a first receiving unit, configured to receive configuration information sent by a first core network device, where the configuration information is used to configure the first policy for the terminal.

[0293] In some implementations, the first core network device is AMF; or the first core network device is PCF, then the configuration information is sent by the PCF to the terminal through the AMF.

[0294] In some implementations, the terminal further includes: a second receiving unit, configured to receive a registration response message sent by a second core network device, wherein the registration response message carries the first policy.

[0295] In some implementations, if the URSP corresponding to the first network matches the first service, the first service is transmitted through a first PDU session, and the first PDU session corresponds to the RSD in the URSP corresponding to the first network.

[0296] In some implementations, the first association relationship indicates that the first service is associated with the first network and the second network, and the processing unit 1210 is used to transmit the first service through the first network if a second condition is met, wherein the second condition includes one of the following: the first service does not match the URSP rules corresponding to the second network; the first service cannot be transmitted through the PDU session corresponding to any RSD in the matching URSP rules corresponding to the second network.

[0297] FIG13 is a schematic diagram of a core network device according to an embodiment of the present application. The core network device 1300 shown in FIG13 includes: a sending unit 1310 .

[0298] The sending unit 1310 is configured to send a first policy to a terminal, where the first policy includes a first association relationship between a service and a network.

[0299] In some implementations, the first association relationship indicates that the first service is associated with multiple networks, where the multiple networks include the first network, and the multiple networks have different corresponding priorities.

[0300] In some implementations, the network includes a PLMN. If the first association relationship indicates that the first service is associated with multiple networks, and the first network among the multiple networks is a registered PLMN or an equivalent PLMN, the first network is used to transmit the first service.

[0301] In some implementations, the multiple networks include the first network and a second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

[0302] In some implementations, the first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service.

[0303] In some implementations, the first policy includes a second association between the service and a preemption priority, where the preemption priority indicates a priority for the service to occupy an associated network for transmission.

[0304] In some implementations, the second association relationship indicates that the preemption priority of the second service is higher than the preemption priority of the first service, and when the first condition is met, the transmission of the second service preempts the resources for transmitting the first service, wherein the first condition includes one or more of the following: the terminal does not support simultaneous transmission of the first service on the first network and the second service on the second network; the terminal does not support simultaneous transmission of the first service and the second service through multiple wireless access technologies RAT; during the process of simultaneous transmission by the terminal through multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; during the process of simultaneous transmission by the terminal through multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

[0305] In some implementations, the first policy includes a third association between the network and a RAT type.

[0306] In some implementations, the third association relationship indicates that the first network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

[0307] In some implementations, the RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geosynchronous orbit GEO radio access technology, NR medium earth orbit MEO radio access technology, and NR low earth orbit LEO.

[0308] In some implementations, the first policy includes a fourth association relationship between the network and a system type, where the system type indicates a type of a core network in the network and / or a type of a non-access stratum (NAS) message in the network.

[0309] In some implementations, the first policy is carried in configuration information, and the configuration information is used to configure the first policy for the terminal.

[0310] In some implementations, the core network device is AMF; or the core network device is PCF, then the configuration information is sent by the PCF to the terminal through the AMF.

[0311] In some implementations, the first policy is carried in a registration response message.

[0312] In some implementations, if the URSP corresponding to the first network matches the first service, the first service is transmitted through a first PDU session, and the first PDU session corresponds to the RSD in the URSP corresponding to the first network.

[0313] FIG14 is a schematic diagram of a terminal according to another embodiment of the present application. The terminal 1400 shown in FIG14 includes a processing unit 1410 .

[0314] Processing unit 1410 is used to determine a UE routing selection strategy URSP corresponding to the first service, where the URSP is used to indicate one or more of the following: a third association relationship between a network and a radio access technology RAT type; a fourth association relationship between the network and a system type, where the system type is used to indicate a type of a core network in the network and / or a type of a non-access network in the network.

[0315] In some implementations, the third association relationship and / or the fourth association relationship is carried in a routing descriptor RSD in the URSP.

[0316] In some implementations, the third association relationship and / or the fourth association relationship are carried in access type priority information in the RSD.

[0317] In some implementations, the third association relationship and / or the fourth association relationship is dedicated information in the RSD.

[0318] In some implementations, the third association relationship indicates that the network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

[0319] In some implementations, the RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geosynchronous orbit GEO radio access technology, NR medium earth orbit MEO radio access technology, and NR low earth orbit LEO.

[0320] In some implementations, the URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal.

[0321] In some implementations, the core network device is AMF; or the core network device is PCF, then the configuration information is sent by the PCF to the terminal through the AMF.

[0322] In some implementations, the URSP is carried in a registration response message.

[0323] FIG15 is a schematic diagram of a core network device according to another embodiment of the present application. The core network device 1500 shown in FIG15 includes a sending unit 1510 .

[0324] A sending unit 1510 is configured to send a UE routing policy URSP to the terminal, where the URSP is used to indicate one or more of the following: a third association relationship between a network and a radio access technology RAT type; a fourth association relationship between the network and a system type, where the system type is used to indicate a type of a core network in the network and / or a type of a non-access network in the network.

[0325] In some implementations, the third association relationship and / or the fourth association relationship is carried in a routing descriptor RSD in the URSP.

[0326] In some implementations, the third association relationship and / or the fourth association relationship are carried in access type priority information in the RSD.

[0327] In some implementations, the third association relationship and / or the fourth association relationship is dedicated information in the RSD.

[0328] In some implementations, the third association relationship indicates that the network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

[0329] In some implementations, the RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geosynchronous orbit GEO radio access technology, NR medium earth orbit MEO radio access technology, and NR low earth orbit LEO.

[0330] In some implementations, the URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal.

[0331] In some implementations, the core network device is AMF; or the core network device is PCF, then the configuration information is sent by the PCF to the terminal through the AMF.

[0332] In some implementations, the URSP is carried in a registration response message.

[0333] FIG16 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1600 shown in FIG16 is a first device, and the communication device 1600 includes a sending unit 1610 .

[0334] The sending unit 1610 is configured to send first information to the second device, where the first information carries capability information associated with the network access mode.

[0335] In some implementations, the capability information is used to indicate one or more of the following: whether network access based on multiple network access modes is supported; and whether access mode switching based on multiple network access modes is supported.

[0336] In some implementations, multiple user plane connections are established based on the multiple access modes, and the capability information is used to indicate one or more of the following: whether to support transmission of different data in the same service through the multiple user plane connections; whether to support non-simultaneous transmission through the multiple user plane connections; whether to support simultaneous transmission through the multiple user plane connections; whether to support transmission through the multiple user plane connections using one USIM; whether to support transmission through the multiple user plane connections using multiple USIMs; whether to support transmission through the multiple user plane connections using one SUPI; whether to support transmission through the multiple user plane connections using multiple SUPIs; and the type of core network that supports the use of the multiple user plane connections.

[0337] In some implementations, the device further includes: a receiving unit for receiving second information sent by the second device, the second information including one or more of the following: available capability information in the capability information carried by the first information; capability information supported by the second device in the capability information carried by the first information; capability information allowed to be used by the second device in the capability information carried by the first information; and UE policy used by the first device.

[0338] In some implementations, the first device is a terminal, and the second device is a core network device.

[0339] In some implementations, the second information is carried in one or more of the following: a registration response message; configuration information, where the configuration information is used to configure a UE policy for the terminal.

[0340] In some implementations, the first information is carried in a registration request, and the registration request is used to request registration of the terminal.

[0341] In some implementations, the registration request carries a UE policy container, and the UE policy container includes the first information; or the registration request carries a UE policy container and the first information.

[0342] In some implementations, the first device is a terminal device and the second device is an AMF or a PCF.

[0343] FIG17 is a schematic diagram of a communication device according to another embodiment of the present application. The communication device 1700 shown in FIG17 is a second device, and the communication device 1700 includes a receiving unit 1710 .

[0344] The receiving unit 1710 is configured to receive first information sent by a first device, where the first information carries capability information associated with a network access method.

[0345] In some implementations, the capability information is used to indicate one or more of the following: whether network access based on multiple network access modes is supported; and whether access mode switching based on multiple network access modes is supported.

[0346] In some implementations, multiple user plane connections are established based on the multiple access modes, and the capability information is used to indicate one or more of the following: whether to support transmission of different data in the same service through the multiple user plane connections; whether to support non-simultaneous transmission through the multiple user plane connections; whether to support simultaneous transmission through the multiple user plane connections; whether to support transmission through the multiple user plane connections using one USIM; whether to support transmission through the multiple user plane connections using multiple USIMs; whether to support transmission through the multiple user plane connections using one SUPI; whether to support transmission through the multiple user plane connections using multiple SUPIs; and the type of core network that supports the use of the multiple user plane connections.

[0347] In some implementations, the device further includes: a sending unit for sending second information to the first device, where the second information includes one or more of the following: available capability information in the capability information carried by the first information; capability information supported by the second device in the capability information carried by the first information; capability information allowed to be used by the second device in the capability information carried by the first information; and UE policy used by the first device.

[0348] In some implementations, the first device is a terminal, and the second device is a core network device.

[0349] In some implementations, the second information is carried in one or more of the following: a registration response message; configuration information, where the configuration information is used to configure a UE policy for the terminal.

[0350] In some implementations, the first information is carried in a registration request, and the registration request is used to request registration of the terminal.

[0351] In some implementations, the registration request carries a UE policy container, and the UE policy container includes the first information; or the registration request carries a UE policy container and the first information.

[0352] In some implementations, the first device is a terminal device and the second device is an AMF or a PCF.

[0353] Figure 18 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 18 indicate that the unit or module is optional. Device 1800 may be used to implement the method described in the above method embodiment. Device 1800 may be a chip, a terminal, or a network device.

[0354] The device 1800 may include one or more processors 1810. The processor 1810 may support the device 1800 to implement the method described in the method embodiment above. The processor 1810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0355] The apparatus 1800 may further include one or more memories 1820. The memories 1820 store programs that can be executed by the processor 1810, causing the processor 1810 to perform the methods described in the above method embodiments. The memories 1820 may be independent of the processor 1810 or integrated into the processor 1810.

[0356] The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips via the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips via the transceiver 1830.

[0357] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0358] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0359] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0360] It should be understood that the terms "service" and "application" are used interchangeably in this application. Furthermore, the term "terminal" used in this application may include one or more USIM cards. Of course, in this application, a terminal may include one or more UE functions to access different networks.

[0361] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0362] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0363] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0364] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0365] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0366] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0367] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0368] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

[0370] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

[0372] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0373] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for wireless communication, characterized in that, including: The terminal determines a first network associated with a first service based on a first policy, where the first policy includes a first association relationship between the service and the network; The terminal transmits the first service through the first network.

2. The method according to claim 1, wherein The first association relationship indicates that the first service is associated with multiple networks, the multiple networks include the first network, and the priorities corresponding to the multiple networks are different.

3. The method according to claim 1 or 2, characterized in that, The network includes a Public Land Mobile Network (PLMN). If the first association relationship indicates that the first service is associated with multiple networks and the first network among the multiple networks is a registered PLMN or an equivalent PLMN, then the first network is used to transmit the first service.

4. The method according to claim 3, characterized in that, The multiple networks include the first network and a second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

5. The method according to any one of claims 1 to 4, characterized in that, The first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service.

6. The method according to any one of claims 1-5, characterized in that, The terminal includes multiple Universal Subscriber Identity Modules (USIMs). The terminal transmitting the first service through the first network includes: The terminal uses a first USIM among the multiple USIMs to transmit the first service through the first network.

7. The method according to claim 6, characterized in that The first USIM is determined based on the association relationship between the USIM and the network.

8. The method according to any one of claims 1 to 7, characterized in that, The first policy includes a second association relationship between the service and a preemption priority, and the preemption priority indicates the priority for the service to occupy the associated network for transmission.

9. The method according to claim 8, wherein The second association relationship indicates that the preemption priority of a second service is higher than the preemption priority of the first service. Under the condition of meeting a first condition, the transmission of the second service preempts the resources for transmitting the first service, where the first condition includes one or more of the following: The terminal does not support simultaneously transmitting the first service on the first network and transmitting the second service on the second network; The terminal does not support simultaneously transmitting the first service and the second service through multiple Radio Access Technologies (RATs); During the process of the terminal simultaneously transmitting through multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; During the process of the terminal simultaneously transmitting through multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

10. The method according to any one of claims 1-9, characterized in that, The method includes: The terminal determines a Radio Access Technology (RAT) type associated with the first network based on a UE policy, where the UE policy includes an association relationship between the network and the RAT type; and / or The terminal determines a system type associated with the first network based on the UE policy, where the UE policy includes an association relationship between the network and the system type, and the system type indicates the type of the core network and / or the type of Non-Access Stratum (NAS) messages in the associated network.

11. The method according to any one of claims 1-9, characterized in that, The first policy includes a third association relationship between the network and the RAT type.

12. The method according to claim 11, wherein The third association relationship indicates that the first network is associated with multiple RAT types, and the priorities corresponding to the multiple RAT types are different.

13. The method according to claim 11 or 12, characterized in that, The method further includes: The terminal determines the RAT type associated with the first network based on the third association relationship; The terminal transmits the first service through the first network, including: The terminal accesses the first network based on the RAT type associated with the first network to transmit the first service.

14. The method according to any one of claims 9-13, characterized in that, The terminal includes multiple USIMs. The terminal transmits the first service through the first network, including: The terminal selects a first USIM from the multiple USIMs based on the RAT type associated with the first network, and the first USIM uses the RAT type associated with the first network for registration and / or establishing a user plane connection; The terminal uses the first USIM to access the first network to transmit the first service.

15. The method according to any one of claims 10-14, characterized in that, The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved universal mobile telecommunications system UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geostationary orbit GEO radio access technology, NR medium Earth orbit satellite MEO radio access technology, NR low Earth orbit satellite LEO.

16. The method according to any one of claims 1-15, characterized in that, The first policy includes a fourth association relationship between the network and the system type, and the system type indicates the type of the core network in the network and / or the type of the non-access stratum NAS message in the network.

17. The method according to claim 16, characterized in that, Before the terminal transmits the first service through the first network, the method further includes: The terminal determines the system type associated with the first network based on the fourth association relationship.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: The terminal receives configuration information sent by a first core network device, and the configuration information is used to configure the first policy for the terminal.

19. The method according to claim 18, characterized in that, The first core network device is an access and mobility management function AMF; or If the first core network device is a policy control function PCF, the configuration information is sent by the PCF to the terminal through the AMF.

20. The method according to any one of claims 1-17, characterized in that, The method further includes: The terminal receives a registration response message sent by a second core network device, and the first policy is carried in the registration response message.

21. The method according to any one of claims 1 to 20, characterized in that, If the UE routing selection policy URSP corresponding to the first network matches the first service, the first service is transmitted through a first protocol data unit PDU session, and the first PDU session corresponds to a routing selection descriptor RSD in the URSP corresponding to the first network.

22. The method according to any one of claims 1-21, characterized in that, The first association relationship indicates that the first service is associated with the first network and the second network. The terminal transmits the first service through the first network, including: If a second condition is satisfied, the terminal transmits the first service through the first network, where the second condition includes one of the following: The first service does not match any of the URSP rules corresponding to the second network; The first service cannot be transmitted through any PDU session corresponding to an RSD in the matching URSP rules corresponding to the second network.

23. A method for wireless communication, characterized in that, Including: The core network device sends a first policy to the terminal, and the first policy includes a first association relationship between the service and the network.

24. The method according to claim 23, wherein The first association relationship indicates that the first service is associated with multiple networks, the multiple networks including the first network, and the multiple networks having different priorities.

25. The method according to claim 23 or 24, characterized in that The network includes a PLMN. If the first association relationship indicates that the first service is associated with multiple networks, and the first network among the multiple networks is a registered PLMN or an equivalent PLMN, then the first network is used to transmit the first service.

26. The method according to claim 25, wherein The multiple networks include the first network and a second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

27. The method according to any one of claims 23-26, characterized in that, The first association relationship indicates that multiple services are associated with the first network, the multiple services including the first service.

28. The method according to any one of claims 23-26, characterized in that, The first policy includes a second association relationship between the service and a preemption priority, the preemption priority indicating the priority for the service to occupy the associated network for transmission.

29. The method according to claim 28, wherein The second association relationship indicates that the preemption priority of the second service is higher than the preemption priority of the first service. Under the condition of meeting the first condition, the transmission of the second service preempts the resources for transmitting the first service, where the first condition includes one or more of the following: The terminal does not support simultaneously transmitting the first service on the first network and transmitting the second service on the second network; The terminal does not support simultaneously transmitting the first service and the second service through multiple radio access technologies (RATs); During the process of the terminal performing simultaneous transmission through multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; During the process of the terminal performing simultaneous transmission through multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

30. The method according to any one of claims 23-29, characterized in that, The first policy includes a third association relationship between the network and the RAT type.

31. The method according to claim 30, characterized in that, The third association relationship indicates that the first network is associated with multiple RAT types, and the multiple RAT types have different priorities.

32. The method according to claim 30 or 31, characterized in that The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geostationary orbit (GEO) radio access technology, NR medium Earth orbit (MEO) satellite radio access technology, NR low Earth orbit (LEO) satellite.

33. The method according to any one of claims 23-32, characterized in that, The first policy includes a fourth association relationship between the network and the system type, the system type indicating the type of the core network in the network and / or the type of the non-access stratum (NAS) message in the network.

34. The method according to any one of claims 23-33, characterized in that, The first policy is carried in configuration information, and the configuration information is used to configure the first policy for the terminal.

35. The method according to claim 34, characterized in that, The core network device is an AMF; or The core network device is a PCF, then the configuration information is sent by the PCF to the terminal through the AMF.

36. The method according to any one of claims 23-33, characterized in that, The first policy is carried in a registration response message.

37. The method according to any one of claims 23-36, characterized in that, If the URSP corresponding to the first network matches the first service, then the first service is transmitted through a first PDU session, and the first PDU session corresponds to the RSD in the URSP corresponding to the first network.

38. A method for wireless communication, characterized in that, Includes: The terminal determines a UE Routing Selection Policy (URSP) for a first service, and the URSP is used to indicate one or more of the following: A third association relationship between the network and radio access technology (RAT) types; A fourth association relationship between the network and system types, where the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

39. The method according to claim 38, wherein The third association relationship and / or the fourth association relationship is carried in a Routing Selection Descriptor (RSD) in the URSP.

40. The method according to claim 39, wherein The third association relationship and / or the fourth association relationship is carried in access type priority information in the RSD.

41. The method according to claim 39, wherein The third association relationship and / or the fourth association relationship is dedicated information in the RSD.

42. The method according to any one of claims 38 - 41, characterized in that, The third association relationship indicates that the network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

43. The method according to any one of claims 38 to 42, characterized in that, The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access (E-UTRA), NR satellite access technology, NR geostationary orbit (GEO) radio access technology, NR medium Earth orbit (MEO) satellite radio access technology, NR low Earth orbit (LEO) satellite.

44. The method according to any one of claims 38 - 43, characterized in that, The URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal.

45. The method according to claim 44, wherein, The core network device is the AMF; or If the core network device is the PCF, the configuration information is sent by the PCF to the terminal through the AMF.

46. The method according to any one of claims 38 to 43, characterized in that, The URSP is carried in a registration response message.

47. A method for wireless communication, characterized in that, Including: The core network device sends a UE Routing Selection Policy (URSP) to the terminal, and the URSP is used to indicate one or more of the following: A third association relationship between the network and radio access technology (RAT) types; A fourth association relationship between the network and system types, where the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

48. The method according to claim 47, wherein The third association relationship and / or the fourth association relationship is carried in a Routing Selection Descriptor (RSD) in the URSP.

49. The method according to claim 48, wherein The third association relationship and / or the fourth association relationship is carried in access type priority information in the RSD.

50. The method according to claim 48, wherein The third association relationship and / or the fourth association relationship is dedicated information in the RSD.

51. The method according to any one of claims 47 to 50, characterized in that, The third association relationship indicates that the network is associated with multiple RAT types, and the multiple RAT types have different corresponding priorities.

52. The method according to any one of claims 47-51, characterized in that, The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access (E-UTRA), NR satellite access technology, NR geostationary orbit (GEO) radio access technology, NR medium Earth orbit (MEO) satellite radio access technology, NR low Earth orbit (LEO) satellite.

53. The method according to any one of claims 47 - 52, characterized in that, The URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal.

54. The method according to claim 53, wherein The core network device is the AMF; or If the core network device is the PCF, the configuration information is sent by the PCF to the terminal through the AMF.

55. The method according to any one of claims 47 - 54, characterized in that, The URSP is carried in a registration response message.

56. A method for wireless communication, characterized in that, Including: The first device sends first information to the second device, and the first information carries capability information associated with a network access mode.

57. The method according to claim 56, wherein The capability information is used to indicate one or more of the following: Whether it supports network access based on multiple network access modes; Whether it supports access mode switching based on multiple network access modes.

58. The method according to claim 56 or 57, characterized in that, Based on the multiple access modes, multiple user plane connections are established, and the capability information is used to indicate one or more of the following: Whether it supports transmitting different data in the same service through the multiple user plane connections; Whether it supports non-simultaneous transmission through the multiple user plane connections; Whether it supports simultaneous transmission through the multiple user plane connections; Whether it supports transmitting through the multiple user plane connections using one USIM; Whether it supports transmitting through the multiple user plane connections using multiple USIMs; Whether it supports transmitting through the multiple user plane connections using one SUPI; Whether it supports transmitting through the multiple user plane connections using multiple SUPIs; The type of core network that supports using the multiple user plane connections.

59. The method according to any one of claims 56-58, characterized in that, The method further includes: The first device receives second information sent by the second device, and the second information includes one or more of the following: The available capability information in the capability information carried by the first information; The capability information supported by the second device in the capability information carried by the first information; The capability information allowed to be used by the second device in the capability information carried by the first information; The UE policy used by the first device.

60. The method according to any one of claims 56 - 59, characterized in that, The first device is a terminal, and the second device is a core network device.

61. The method according to claim 60, characterized in that, The second information is carried on one or more of the following: A registration response message; Configuration information, which is used to configure a UE policy for the terminal. The method according to any one of claims 56 to 61, characterized in that, The first information is carried on a registration request, and the registration request is used to request the registration of the terminal.

63. The method according to claim 62, wherein, The registration request carries a UE policy container, and the UE policy container contains the first information; or, The registration request carries a UE policy container and the first information.

64. The method according to claim 62 or 63, characterized in that, The first device is a terminal device, and the second device is an AMF or a PCF.

65. A method for wireless communication, characterized in that, It includes: The second device receives the first information sent by the first device, and the first information carries capability information associated with a network access mode.

66. The method according to claim 65, wherein The capability information is used to indicate one or more of the following: Whether it supports network access based on multiple network access modes; Whether it supports access mode switching based on multiple network access modes.

67. The method according to claim 65 or 66, characterized in that, Based on the multiple access modes, multiple user plane connections are established, and the capability information is used to indicate one or more of the following: Whether it supports transmitting different data in the same service through the multiple user plane connections; Whether it supports non-simultaneous transmission through the multiple user plane connections; Whether it supports simultaneous transmission through the multiple user plane connections; Whether it supports transmitting through the multiple user plane connections using one USIM; Whether it supports transmitting through the multiple user plane connections using multiple USIMs; Whether it supports transmitting through the multiple user plane connections using one SUPI; Whether it supports transmitting using multiple SUPI through the multiple user plane connections; The type of core network that supports using the multiple user plane connections.

68. The method according to any one of claims 65 - 67, characterized in that, The method further includes: The second device sends second information to the first device, and the second information includes one or more of the following: The available capability information in the capability information carried by the first information; The capability information supported by the second device in the capability information carried by the first information; The capability information allowed to be used by the second device in the capability information carried by the first information; The UE policy used by the first device.

69. The method according to any one of claims 65-68, characterized in that, The first device is a terminal, and the second device is a core network device.

70. The method according to claim 69, wherein The second information is carried on one or more of the following: A registration response message; Configuration information, which is used to configure the UE policy for the terminal.

71. The method according to any one of claims 65 to 70, characterized in that, The first information is carried on a registration request, and the registration request is used to request registration of the terminal.

72. The method according to claim 71, characterized in that, The registration request carries a UE policy container, and the UE policy container contains the first information; or, The registration request carries a UE policy container and the first information.

73. The method according to claim 71 or 72, characterized in that, The first device is a terminal device, and the second device is an AMF or a PCF.

74. A terminal, characterized in that, Includes: A processing unit, configured to determine a first network associated with a first service based on a first policy, where the first policy includes a first association relationship between the service and the network; A sending unit, configured to transmit the first service through the first network.

75. The terminal according to claim 74, characterized in that, The first association relationship indicates that the first service is associated with multiple networks, the multiple networks include the first network, and the corresponding priorities of the multiple networks are different.

76. The terminal according to claim 74 or 75, characterized in that, The network includes a public land mobile network (PLMN). If the first association relationship indicates that the first service is associated with multiple networks, and the first network among the multiple networks is a registered PLMN or an equivalent PLMN, then the first network is used to transmit the first service.

77. The terminal according to claim 76, wherein The multiple networks include the first network and a second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

78. The terminal according to any one of claims 74-77, characterized in that, The first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service.

79. The terminal according to any one of claims 74-78, characterized in that, The terminal includes multiple universal subscriber identity modules (USIMs), and the sending unit is configured to use a first USIM among the multiple USIMs to transmit the first service through the first network.

80. The terminal according to claim 79, wherein The first USIM is determined based on the association relationship between the USIM and the network.

81. The terminal according to any one of claims 74-80, characterized in that, The first policy includes a second association relationship between the service and a preemption priority, and the preemption priority indicates the priority for the service to occupy the associated network for transmission.

82. The terminal according to claim 81, characterized in that, The second association relationship indicates that the preemption priority of a second service is higher than the preemption priority of the first service. Under the condition of meeting a first condition, the transmission of the second service preempts the resources for transmitting the first service, where the first condition includes one or more of the following: The terminal does not support simultaneously transmitting the first service on the first network and transmitting the second service on the second network; The terminal does not support transmitting the first service and the second service simultaneously via multiple radio access technologies (RATs). During the process of the terminal transmitting simultaneously via multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission. During the process of the terminal transmitting simultaneously via multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

83. The terminal according to any one of claims 74-82, characterized in that, The processing unit is configured to: Determine the radio access technology (RAT) type associated with the first network based on the UE policy, where the UE policy includes the association relationship between the network and the RAT type; and / or Determine the system type associated with the first network based on the UE policy, where the UE policy includes the association relationship between the network and the system type, and the system type indicates the type of the core network and / or the type of non-access stratum (NAS) messages in the associated network.

84. The terminal according to any one of claims 74-82, characterized in that, The first policy includes a third association relationship between the network and the RAT type.

85. The terminal according to claim 84, wherein The third association relationship indicates that the first network is associated with multiple RAT types, and the priorities of the multiple RAT types are different.

86. The terminal according to claim 84 or 85, characterized in that, The processing unit is configured to determine the RAT type associated with the first network based on the third association relationship. The sending unit is configured to access the first network based on the RAT type associated with the first network to transmit the first service.

87. The terminal according to any one of claims 82-86, characterized in that, The terminal includes multiple USIMs, and the sending unit is configured to: Select a first USIM from the multiple USIMs based on the RAT type associated with the first network, where the first USIM is registered and / or establishes a user plane connection using the RAT type associated with the first network; Use the first USIM to access the first network to transmit the first service.

88. The terminal according to any one of claims 83-87, characterized in that, The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA), NR satellite access technology, NR geostationary orbit (GEO) radio access technology, NR medium Earth orbit (MEO) satellite radio access technology, NR low Earth orbit (LEO) satellite.

89. The terminal according to any one of claims 74-88, characterized in that, The first policy includes a fourth association relationship between the network and the system type, where the system type indicates the type of the core network in the network and / or the type of non-access stratum (NAS) messages in the network.

90. The terminal according to claim 89, wherein Before the terminal transmits the first service via the first network, the sending unit is configured to determine the system type associated with the first network based on the fourth association relationship.

91. The terminal according to any one of claims 74-90, characterized in that, The terminal further includes: A first receiving unit, configured to receive configuration information sent by a first core network device, where the configuration information is used to configure the first policy for the terminal.

92. The terminal according to claim 91, wherein The first core network device is the access and mobility management function (AMF); or If the first core network device is the policy control function (PCF), the configuration information is sent by the PCF to the terminal via the AMF.

93. The terminal according to any one of claims 74-90, characterized in that, The terminal further includes: A second receiving unit, configured to receive a registration response message sent by a second core network device, where the first policy is carried in the registration response message.

94. The terminal according to any one of claims 74-93, characterized in that, If the UE routing selection policy (URSP) corresponding to the first network matches the first service, the first service is transmitted through a first protocol data unit (PDU) session, and the first PDU session corresponds to a routing selection descriptor (RSD) in the URSP corresponding to the first network.

95. The terminal according to any one of claims 74-94, characterized in that, The first association relationship indicates that the first service is associated with the first network and the second network. The sending unit is configured to: If a second condition is satisfied, the terminal transmits the first service through the first network, where the second condition includes one of the following: The first service does not match any of the URSP rules corresponding to the second network; The first service cannot be transmitted through any PDU session corresponding to an RSD in the matching URSP rules corresponding to the second network.

96. A core network device, characterized in that, including: A sending unit, configured to send a first policy to a terminal, where the first policy includes a first association relationship between a service and a network.

97. The core network device according to claim 96, characterized in that, The first association relationship indicates that the first service is associated with multiple networks, and the multiple networks include the first network, and the priorities corresponding to the multiple networks are different.

98. The core network device according to claim 96 or 97, characterized in that The network includes a PLMN. If the first association relationship indicates that the first service is associated with multiple networks, and the first network in the multiple networks is a registered PLMN or an equivalent PLMN, the first network is used to transmit the first service.

99. The core network device according to claim 98, characterized in that, The multiple networks include the first network and the second network, and the priority corresponding to the second network is higher than the priority corresponding to the first network.

100. The core network device according to any one of claims 96-99, characterized in that, The first association relationship indicates that multiple services are associated with the first network, and the multiple services include the first service.

101. The core network device according to any one of claims 96-99, characterized in that, The first policy includes a second association relationship between the service and a preemption priority, and the preemption priority indicates the priority for the service to occupy the associated network for transmission.

102. The core network device according to claim 101, characterized in that, The second association relationship indicates that the preemption priority of the second service is higher than the preemption priority of the first service. When a first condition is satisfied, the transmission of the second service preempts the resources for transmitting the first service, where the first condition includes one or more of the following: The terminal does not support transmitting the first service on the first network and transmitting the second service on the second network simultaneously; The terminal does not support transmitting the first service and the second service through multiple radio access technologies (RATs) simultaneously; During the process of the terminal transmitting simultaneously through multiple networks, the number of the multiple networks has reached the upper limit of the number of networks supported by the terminal for simultaneous transmission; During the process of the terminal transmitting simultaneously through multiple RATs, the number of the multiple RATs has reached the upper limit of the number of RATs supported by the terminal for simultaneous transmission.

103. The core network device according to any one of claims 96-102, characterized in that, The first policy includes a third association relationship between the network and the RAT type.

104. The core network device according to claim 103, characterized in that, The third association relationship indicates that the first network is associated with multiple RAT types, and the priorities corresponding to the multiple RAT types are different.

105. The core network device according to claim 103 or 104, characterized in that, The RAT types include one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geostationary orbit GEO radio access technology, NR medium Earth orbit satellite MEO radio access technology, NR low Earth orbit satellite LEO.

106. The core network device according to any one of claims 96-105, characterized in that, The first policy includes a fourth association relationship between the network and the system type, and the system type indicates the type of the core network in the network and / or the type of the non-access stratum NAS message in the network.

107. The core network device according to any one of claims 96-106, characterized in that, The first policy is carried in configuration information, and the configuration information is used to configure the first policy for the terminal.

108. The core network device according to claim 107, characterized in that, The core network device is the AMF; or If the core network device is the PCF, the configuration information is sent by the PCF to the terminal through the AMF.

109. The core network device according to any one of claims 96-106, characterized in that, The first policy is carried in a registration response message.

110. The core network device according to any one of claims 96-109, characterized in that, If the URSP corresponding to the first network matches the first service, the first service is transmitted through a first PDU session, and the first PDU session corresponds to the RSD in the URSP corresponding to the first network.

111. A terminal, characterized in that, Includes: A processing unit, configured to determine a UE routing selection policy URSP corresponding to a first service, where the URSP is used to indicate one or more of the following: A third association relationship between the network and the radio access technology RAT type; The fourth association relationship between the network and the system type, where the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

112. The terminal according to claim 111, characterized in that, The third association relationship and / or the fourth association relationship is carried in a routing selection descriptor RSD in the URSP.

113. The terminal according to claim 112, characterized in that, The third association relationship and / or the fourth association relationship is carried in the access type priority information in the RSD.

114. The terminal according to claim 112, wherein The third association relationship and / or the fourth association relationship is dedicated information in the RSD.

115. The terminal according to any one of claims 111-114, characterized in that, The third association relationship indicates that the network is associated with multiple RAT types, and the priorities corresponding to the multiple RAT types are different.

116. The terminal according to any one of claims 111-115, characterized in that, The RAT types include one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access E-UTRA, NR satellite access technology, NR geostationary orbit GEO radio access technology, NR medium Earth orbit satellite MEO radio access technology, NR low Earth orbit satellite LEO.

117. The terminal according to any one of claims 111-116, characterized in that, The URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal.

118. The terminal according to claim 117, wherein The core network device is the AMF; or If the core network device is the PCF, the configuration information is sent by the PCF to the terminal through the AMF.

119. The terminal according to any one of claims 111-116, characterized in that, The URSP is carried in a registration response message.

120. A core network device, characterized in that, Includes: A sending unit, configured to send a UE routing selection policy URSP to a terminal, where the URSP is used to indicate one or more of the following: A third association relationship between the network and the radio access technology RAT type; The fourth association relationship between the network and the system type, where the system type is used to indicate the type of the core network in the network and / or the type of the non-access network in the network.

121. The core network device according to claim 120, characterized in that, The third association relationship and / or the fourth association relationship are carried in the routing selection descriptor (RSD) in the URSP.

122. The core network device according to claim 121, characterized in that, The third association relationship and / or the fourth association relationship are carried in the access type priority information in the RSD.

123. The core network device according to claim 121, characterized in that, The third association relationship and / or the fourth association relationship are dedicated information in the RSD.

124. The core network device according to any one of claims 120-123, characterized in that, The third association relationship indicates that the network is associated with multiple RAT types, and the priorities corresponding to the multiple RAT types are different. The core network device according to any one of claims 120-124, characterized in that, The RAT type includes one or more of the following: NR terrestrial network radio access technology, evolved UMTS terrestrial radio access (E-UTRA), NR satellite access technology, NR geostationary orbit (GEO) radio access technology, NR medium Earth orbit (MEO) satellite radio access technology, NR low Earth orbit (LEO) satellite.

126. The core network device according to any one of claims 120-125, characterized in that, The URSP is carried in configuration information, and the configuration information is used to configure the URSP for the terminal. The core network device according to claim 126, characterized in that, The core network device is the AMF; or If the core network device is the PCF, the configuration information is sent by the PCF to the terminal through the AMF.

128. The core network device according to any one of claims 120-125, characterized in that, The URSP is carried in a registration response message.

129. A communication device, characterized in that, The communication device is a first device, including: A sending unit, configured to send first information to a second device, where the first information carries capability information associated with a network access mode.

130. The communication device according to claim 129, characterized in that, The capability information is used to indicate one or more of the following: Whether it supports network access based on multiple network access modes; Whether it supports access mode switching based on multiple network access modes.

131. The communication device according to claim 129 or 130, characterized in that, Based on the multiple access modes, multiple user plane connections are established, and the capability information is used to indicate one or more of the following: Whether it supports transmitting different data in the same service through the multiple user plane connections; Whether it supports non-simultaneous transmission through the multiple user plane connections; Whether it supports simultaneous transmission through the multiple user plane connections; Whether it supports transmission through the multiple user plane connections using one USIM; Whether it supports transmission through the multiple user plane connections using multiple USIMs; Whether it supports transmission through the multiple user plane connections using one SUPI; Whether it supports transmission through the multiple user plane connections using multiple SUPIs; The type of core network that supports using the multiple user plane connections.

132. The communication device according to any one of claims 129-131, characterized in that, The communication device further includes: A receiving unit, configured to receive second information sent by the second device, where the second information includes one or more of the following: The available capability information in the capability information carried by the first information; The capability information supported by the second device in the capability information carried by the first information; The capability information allowed to be used by the second device in the capability information carried by the first information; The UE policy used by the first device.

133. The communication device according to any one of claims 129-132, characterized in that, The first device is a terminal, and the second device is a core network device.

134. The communication device according to claim 133, characterized in that, The second information is carried in one or more of the following: A registration response message; Configuration information, where the configuration information is used to configure the UE policy for the terminal.

135. The communication device according to any one of claims 129-134, characterized in that, The first information is carried in a registration request, and the registration request is used to request registration of the terminal.

136. The communication device according to claim 135, characterized in that, The registration request carries a UE policy container, and the UE policy container contains the first information; or, The registration request carries a UE policy container and the first information. The communication device according to claim 135 or 136, characterized in that, The first device is a terminal device, and the second device is an AMF or a PCF.

138. A communication device, characterized in that, The communication device is the second device, including: The second device receives first information sent by the first device, and the first information carries capability information associated with a network access mode.

139. The communication device according to claim 138, characterized in that, The capability information is used to indicate one or more of the following: Whether it supports network access based on multiple network access modes; Whether it supports access mode switching based on multiple network access modes.

140. The communication device according to claim 138 or 139, characterized in that, Based on the multiple access modes, multiple user plane connections are established, and the capability information is used to indicate one or more of the following: Whether it supports transmitting different data in the same service through the multiple user plane connections; Whether it supports non-simultaneous transmission through the multiple user plane connections; Whether it supports simultaneous transmission through the multiple user plane connections; Whether it supports transmitting through the multiple user plane connections using one USIM; Whether it supports transmitting through the multiple user plane connections using multiple USIMs; Whether it supports transmitting through the multiple user plane connections using one SUPI; Whether it supports transmitting through the multiple user plane connections using multiple SUPIs; The type of core network that supports using the multiple user plane connections.

141. The communication device according to any one of claims 138 - 140, characterized in that, The communication device further includes: The second device sends second information to the first device, and the second information includes one or more of the following: The available capability information in the capability information carried by the first information; The capability information supported by the second device in the capability information carried by the first information; The capability information allowed to be used by the second device in the capability information carried by the first information; The UE policy used by the first device.

142. The communication device according to any one of claims 138 - 141, characterized in that, The first device is a terminal, and the second device is a core network device.

143. The communication device according to claim 142, wherein, The second information is carried in one or more of the following: A registration response message; Configuration information, which is used to configure a UE policy for the terminal.

144. The communication device according to any one of claims 138-143, characterized in that, The first information is carried in a registration request, and the registration request is used to request the registration of the terminal.

145. The communication device according to claim 144, wherein The registration request carries a UE policy container, and the UE policy container contains the first information; or, The registration request carries a UE policy container and the first information.

146. The communication device according to claim 144 or 145, characterized in that, The first device is a terminal device, and the second device is an AMF or a PCF.

147. A communication device, characterized in that, It includes a transceiver, a memory, and a processor. The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the communication device executes one of the following: the method according to any one of claims 1-22, the method according to any one of claims 23-37, the method according to any one of claims 38-46, the method according to any one of claims 47-55, the method according to any one of claims 56-64, the method according to any one of claims 65-73.

148. A device, characterized in that, Comprising a processor for invoking a program from a memory to cause the device to perform one of the following: the method according to any one of claims 1 - 22, the method according to any one of claims 23 - 37, the method according to any one of claims 38 - 46, the method according to any one of claims 47 - 55, the method according to any one of claims 56 - 64, the method according to any one of claims 65 - 73.

149. A chip, characterized in that, Comprising a processor for invoking a program from a memory such that the device installed with the chip performs one of the following: the method according to any one of claims 1 - 22, the method according to any one of claims 23 - 37, the method according to any one of claims 38 - 46, the method according to any one of claims 47 - 55, the method according to any one of claims 56 - 64, the method according to any one of claims 65 - 73.

150. A computer-readable storage medium, characterized in that, A program is stored thereon, and the program causes a computer to perform one of the following: the method according to any one of claims 1 - 22, the method according to any one of claims 23 - 37, the method according to any one of claims 38 - 46, the method according to any one of claims 47 - 55, the method according to any one of claims 56 - 64, the method according to any one of claims 65 - 73.

151. A computer program product, characterized in that, Comprising a program, and the program causes a computer to perform one of the following: the method according to any one of claims 1 - 22, the method according to any one of claims 23 - 37, the method according to any one of claims 38 - 46, the method according to any one of claims 47 - 55, the method according to any one of claims 56 - 64, the method according to any one of claims 65 - 73.

152. A computer program, characterized in that, The computer program causes a computer to perform one of the following: the method according to any one of claims 1 - 22, the method according to any one of claims 23 - 37, the method according to any one of claims 38 - 46, the method according to any one of claims 47 - 55, the method according to any one of claims 56 - 64, the method according to any one of claims 65 - 73.

Images