CN111404814A

CN111404814A - Data transmission method and communication device

Info

Publication number: CN111404814A
Application number: CN202010127267.2A
Authority: CN
Inventors: 胡先专; 姜印清; 李哲
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-02-28
Filing date: 2020-02-28
Publication date: 2020-07-10
Anticipated expiration: 2040-02-28
Also published as: CN111404814B

Abstract

The application provides a data transmission method and a communication device, the method is applied to terminal equipment and comprises the steps of storing URSP information of a first user equipment routing strategy, wherein the first URSP information is the URSP information corresponding to a first public land mobile network P L MN, the first P L MN is a P L MN except a home public land mobile network HP L MN, and obtaining a first URSP rule from the first URSP information, wherein the first URSP rule is used for transmitting data to be transmitted of a started application program.

Description

Data transmission method and communication device

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a data transmission method and a communication device.

Background

In the latest 3rd generation mobile communication standardization organization (3 GPP) protocol, a concept of a UE routing policy (URSP) is defined to determine whether a detected Application (APP) can be associated with an established Protocol Data Unit (PDU) session, can be offloaded to non-3GPP access outside of the PDU session, or can trigger establishment of a new PDU session.

At present, the specific method for the terminal device to implement data transmission according to the URSP information is as follows: the core network obtains the URSP information that the terminal needs to follow from a Policy Control Function (PCF) and provides the obtained information to the terminal device, so that the terminal device will route the data to be sent by the application according to one or more rules in the URSP information.

According to the latest protocol progress, URSP information is generally sent by taking a public land mobile network (P L MN) as a dimension, and PCF can send the URSP information corresponding to the P L MN to a terminal device through a management terminal device policy command (management UE policy command) message.

For example, in some scenarios, even if the network side issues the URSP information of the HP L MN, the URSP information of the HP L MN stored in the terminal device may be lost in some cases, so that the situation that the terminal device has no possibility of using the URSP may be caused, thereby causing adverse effects on the data transmission efficiency of the terminal device and reducing user experience.

Disclosure of Invention

The application provides a data transmission method and a communication device, so that terminal equipment can reasonably store and use URSP information of a non-HP L MN issued by a network side, the efficiency of data routing of the terminal equipment can be improved, and user experience is improved.

In a first aspect, a method for data transmission is provided, where the method is applied to a terminal device, and may be executed by the terminal device, or may also be executed by a chip or a circuit configured in the terminal device, and this application is not limited thereto.

Specifically, the method comprises the steps of storing first user equipment routing strategy (URSP) information, wherein the first URSP information is URSP information corresponding to a first public land mobile network (P L MN), the first P L MN is a P L MN except a home public land mobile network (HP L MN), and obtaining a first URSP rule from the first URSP information, and the first URSP rule is used for transmitting data to be transmitted of an started application program.

According to the data transmission method provided by the embodiment of the application, after acquiring the first URSP information, the terminal device can reasonably store the first URSP information for later use, the first URSP information is the URSP information corresponding to the first P L MN, the first P L MN is a P L MN other than the HP L MN, and when a started application of the terminal device needs to perform data routing, the terminal device can attempt to acquire the URSP rule for the started application to perform data transmission from the first URSP information, so that the efficiency of data routing of the terminal device can be improved, and user experience is improved.

Alternatively, the first URSP information may be uploaded by the user locally.

Optionally, the first URSP information may be acquired by the terminal device from other terminal devices.

Optionally, the first URSP information may be acquired by the terminal device from the network side.

For example, the first URSP information is acquired by the terminal device from the policy control entity PCF. At this time, the first URSP information may be carried in a management terminal device policy command message or other messages.

Further, the PCF may send the first URSP information to the terminal device through the non-access stratum message, and the PCF may pass the first URSP information through the AMF and the access network device to the terminal device, at this time, the AMF and the access network device may not perceive the content of the first URSP information.

For another example, the first URSP information is acquired by the terminal device from a remote cloud server.

Optionally, the terminal device acquires the first URSP rule from the first URSP information, may successfully acquire the first URSP rule, or may not successfully acquire the first URSP rule, which is not limited in this application.

Optionally, when the started application needs to perform data routing, the terminal device may first determine the URSP parameter of the started application, and then search for the first URSP rule from the at least one URSP rule included in the first URSP information according to the URSP parameter.

It should be understood that the started application may correspond to multiple rules in the first URSP information, and at this time, multiple URSP rules may be obtained according to the URSP parameters, that is, at this time, the first URSP rule may include multiple rules, which is not limited in this application.

Optionally, the URSP parameters may include one or more of a traffic description, a seamless download indication, a network slice selection, a session continuity mode selection, a data network name, an access type, and a routing description. The embodiments of the present application do not limit the specific content included in the URSP parameters, which may vary with different network structures and application scenarios.

Optionally, in this embodiment of the present application, the starting in the started application includes: the user clicks a certain application icon to enable the application program corresponding to the application icon to start running, the automatic running of some application programs on the terminal equipment, the running state of the application programs in the foreground or the background and the like. The embodiment of the present application does not limit the concrete expression form of the started application program.

With reference to the first aspect, in some implementations of the first aspect, before storing the first user equipment routing policy, URSP, information, the method further includes receiving a policy message sent by the network side, where the policy message includes URSP information corresponding to at least one P L MN, and the at least one P L MN includes the first P L MN.

With reference to the first aspect, in some implementations of the first aspect, the at least one P L MN includes an HP L MN, and the URSP information corresponding to the HP L MN is second URSP information, the storing the first user equipment routing policy URSP information includes storing the second URSP information, and before acquiring the first URSP rule from the first URSP information, the method further includes acquiring the first URSP rule from the second URSP information without successfully acquiring the first URSP rule.

Specifically, the terminal device may preferentially acquire the first URSP rule from the second URSP information if the terminal device acquires the first URSP information and the second URSP information at the same time, and may subsequently acquire the first URSP rule from the first URSP information when the first URSP rule is not successfully acquired from the second URSP information.

According to the embodiment of the application, the terminal equipment can respectively try to acquire the first URSP rule from the second URSP information and the first URSP information, and the probability of acquiring the first URSP rule is increased, so that the efficiency of data routing of the terminal equipment is improved, and the use experience of a user is improved.

Alternatively, in other embodiments, if the terminal device successfully acquires the first URSP rule from the second URSP information, the first URSP rule may not be acquired from the first URSP information at this time because the URSP rule for the started program to perform data transmission has already been acquired, that is, step 220 may become an optional step at this time.

With reference to the first aspect, in some implementations of the first aspect, before the obtaining the first URSP rule from the first URSP information, the method further includes determining that a second URSP information is not stored, where the second URSP information is URSP information corresponding to the HP L MN.

Therefore, according to the embodiment of the application, the terminal device can firstly determine that the second URSP information is not stored locally, and then obtain the first URSP rule from the first URSP information.

For example, the aforementioned policy information (such as the management terminal device policy command message) includes URSP information corresponding to at least one P L MN, and the at least one P L MN does not include an HP L MN.

Optionally, the terminal device does not store the second URSP information, or may lose the previously stored URSP information due to some other reasons, which is not limited in this application.

With reference to the first aspect, in some implementations of the first aspect, the at least one P L MN includes a third P L MN, the third P L MN is a P L MN other than the HP L MN, and the URSP information corresponding to the third P L MN is third URSP information, and the storing the first user equipment routing policy URSP information includes storing the third URSP information, and if the first URSP rule is not successfully acquired from the first URSP information, the method further includes acquiring the first URSP rule from the third URSP information.

Specifically, in order to increase the probability of acquiring the first URSP rule, the terminal device may store a plurality of pieces of URSP information, which may be corresponding pieces of URSP information of a plurality of non-HP L MNs, for example, storing the first URSP information and the third URSP information at the same time.

According to the embodiment of the application, the terminal equipment can respectively try to acquire the first URSP rule from the first URSP information and the third URSP information, and the probability of acquiring the first URSP rule is increased, so that the efficiency of data routing of the terminal equipment is improved, and the use experience of a user is improved.

Optionally, the first P L MN is EHP L MN and the third P L MN is EP L MN.

Optionally, if the terminal device still fails to acquire the first URSP rule from the third URSP information, at this time, the terminal device may continue to acquire the first URSP rule from the URSP information corresponding to the P L MN, such as the fourth P L MN, the fifth P L MN, and the like, which is not limited in this application.

For example, the fourth P L MN and the fifth P L MN may be non-HP L MN, and may be any one of RP L MN, OP L MN, UP L MN, VP L MN, and the like.

Optionally, if the terminal device still does not successfully acquire the first URSP rule from the third URSP information, at this time, the terminal device may also transmit the data to be transmitted of the started application program by using a default configuration, which is not limited in the present application.

With reference to the first aspect, in some implementations of the first aspect, if the first URSP rule is not successfully acquired from the first URSP information, the method further includes: and transmitting the data to be transmitted of the started application program by using default configuration.

With reference to the first aspect, in some implementations of the first aspect, if the first URSP rule is successfully obtained from the first URSP information, the method further includes: and transmitting the data to be transmitted of the started application program by using the first URSP rule.

With reference to the first aspect, in some implementations of the first aspect, the policy message is a manage terminal device policy command message.

With reference to the first aspect, in some implementations of the first aspect, the receiving a policy message sent by a network side includes: and receiving the policy message sent by a policy control entity PCF or a cloud server.

For example, the PCF may send the policy message to the terminal device through the non-access stratum, and the PCF may pass the policy message through the AMF and the access network device to the terminal device, where the AMF and the access network device may not perceive the content of the policy message.

In combination with the first aspect, in certain implementations of the first aspect, the first P L MN is an equivalent home public land mobile network, EHP L MN.

Because the network side may not directly issue the HP L MN in some scenarios, but directly issues the EHP L MN, according to the method 200 provided by the present application, the URSP information corresponding to the EHP L MN may be stored for later use, which is beneficial to improving the efficiency of data routing of the terminal device, and further improves the use experience.

In a second aspect, a communication apparatus is provided, which includes a storage unit configured to store first user equipment routing policy (URSP) information, where the first URSP information is URSP information corresponding to a first public land mobile network (P L MN), and the first P L MN is a P L MN other than a home public land mobile network (HP L MN), and an obtaining unit configured to obtain a first URSP rule from the first URSP information, where the first URSP rule is used for transmitting data to be transmitted of an application program that has been started.

With reference to the second aspect, in some implementations of the second aspect, the communications apparatus further includes a transceiving unit, configured to receive a policy message sent by a network side before the storing unit stores the first URSP information, where the policy message includes URSP information corresponding to at least one P L MN, and the at least one P L MN includes the first P L MN.

With reference to the second aspect, in some implementations of the second aspect, the at least one P L MN includes the HP L MN, the URSP information corresponding to the HP L MN is second URSP information, the storage unit is further configured to store the second URSP information, and the obtaining unit is specifically configured to obtain the first URSP rule from the second URSP information, and the first URSP rule is not successfully obtained.

With reference to the second aspect, in some implementations of the second aspect, before the obtaining unit obtains the first URSP rule from the first URSP information, the obtaining unit is further configured to determine that a second URSP information is not stored, where the second URSP information is the URSP information corresponding to the HP L MN.

With reference to the second aspect, in some implementations of the second aspect, the at least one P L MN includes a third P L MN, the third P L MN is a P L MN other than the HP L MN, and URSP information corresponding to the third P L MN is third URSP information, the storage unit is further configured to store the third URSP information, and if the obtaining unit does not successfully obtain the first URSP rule from the first URSP information, the obtaining unit is further configured to obtain the first URSP rule from the third URSP information.

With reference to the second aspect, in some implementations of the second aspect, if the obtaining unit fails to obtain the first URSP rule from the first URSP information, the communication device further includes: and the transceiving unit is used for transmitting the data to be transmitted of the started application program by using default configuration.

With reference to the second aspect, in some implementations of the second aspect, if the obtaining unit successfully obtains the first URSP rule from the first URSP information, the communication device further includes: and the transceiving unit is used for transmitting the data to be transmitted of the started application program by using the first URSP rule.

With reference to the second aspect, in some implementations of the second aspect, the policy message is a manage terminal device policy command message.

With reference to the second aspect, in some implementations of the second aspect, the transceiver unit is specifically configured to: and receiving the policy message sent by a policy control entity PCF or a cloud server.

With reference to the second aspect, in certain implementations of the second aspect, the first P L MN is an equivalent home public land mobile network, EHP L MN.

In a third aspect, a communication apparatus is provided, which may be a terminal device or a chip in the terminal device. The apparatus may include a processing unit and a transceiver unit. When the apparatus is a terminal device, the processing unit may be a processor, and the transceiving unit may be a transceiver; the terminal device may further include a storage unit, which may be a memory; the storage unit is configured to store instructions, and the processing unit executes the instructions stored by the storage unit to enable the terminal device to execute the method in the first aspect. When the apparatus is a chip in a terminal device, the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin, a circuit, or the like; the processing unit executes instructions stored by a storage unit (e.g., a register, a cache, etc.) within the chip, or a storage unit (e.g., a read-only memory, a random access memory, etc.) external to the chip within the terminal device, so as to cause the terminal device to perform the method of the first aspect.

In a fourth aspect, a communications apparatus is provided that includes at least one processor configured to couple with a memory, read and execute instructions from the memory to implement any of the methods of the first aspect.

Optionally, the communication device further comprises the memory.

In a fifth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of the first aspect described above.

It should be noted that, all or part of the computer program code may be stored in the first storage medium, where the first storage medium may be packaged with the processor or may be packaged separately from the processor, and this application is not limited in this respect.

In a sixth aspect, a computer-readable medium is provided, having program code stored thereon, which, when run on a computer, causes the computer to perform the method of the first aspect described above.

In a seventh aspect, a chip system is provided, which is used to call and run a computer program from a memory, so that a communication device installed with the chip system executes the method in the first aspect.

In an eighth aspect, a communication system is provided, which comprises the communication apparatus provided in the second, third or fourth aspect.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application.

Fig. 2 is a schematic diagram of a path for transmitting URSP information to a terminal device from a network side.

Fig. 3 is a diagram showing an example of a cell structure for managing a terminal device policy command message.

Fig. 4 is a signaling interaction diagram of PCF sending URSP information to the terminal device.

Fig. 5 is a diagram showing an example of a cell structure for managing a terminal device policy command rejection message.

Fig. 6 is a schematic flowchart of an example of a method for data transmission according to an embodiment of the present application.

Fig. 7 is a schematic flowchart of another example of a method for data transmission according to an embodiment of the present application.

Fig. 8 is a schematic flowchart of another example of a method for data transmission according to an embodiment of the present application.

Fig. 9 is a schematic flowchart of another example of a method for data transmission according to an embodiment of the present application.

Fig. 10 is a schematic flowchart of another example of a method for data transmission according to an embodiment of the present application.

Fig. 11 is a logical relationship diagram corresponding to fig. 10 for obtaining the first URSP rule.

Fig. 12 is a schematic flowchart of another example of a method for data transmission according to an embodiment of the present application.

Fig. 13 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 14 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application can be applied to various communication systems, such as global system for mobile communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), long term evolution (long term evolution, L TE) systems, L TE Frequency Division Duplex (FDD) systems, L TE Time Division Duplex (TDD), universal mobile communication systems (universal mobile communication system, UMTS), Worldwide Interoperability for Microwave Access (WiMAX), WiMAX, fifth generation communication systems (5, NR 5, future radio access (NR 5) communication systems, and so on.

For the understanding of the embodiments of the present application, an application scenario of the embodiments of the present application will be described in detail with reference to fig. 1.

Fig. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application. As shown in fig. 1, the network architecture may be, for example, a non-roaming (non-roaming) architecture. The network architecture may specifically include the following network elements:

1. a UE may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (W LL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capability, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (P L MN), and may also be an end device, a logical entity, a smart device, a terminal device such as a cell phone, a smart terminal, or a gateway, a base station, a controller, and the like, or an Internet appliance, or an Internet meter, and embodiments thereof are not limited to this application.

2. Access Network (AN): the method provides a network access function for authorized users in a specific area, and can use transmission tunnels with different qualities according to the level of the users, the requirements of services and the like. The access network may be an access network employing different access technologies. There are two types of current radio access technologies: third generation partnership Project (3 GPP) access technologies, such as the radio access technologies employed in 3G, 4G or 5G systems, and non-third generation partnership Project (non-3GPP) access technologies. The 3GPP Access technology refers to an Access technology meeting 3GPP standard specifications, and an Access Network adopting the 3GPP Access technology is referred to as a Radio Access Network (RAN), where an Access Network device in a 5G system is referred to as a next generation Base station (gNB). The non-3GPP access technology refers to an access technology that does not conform to the 3GPP standard specification, for example, an air interface technology represented by an Access Point (AP) in wifi.

An access network that implements an access network function based on a wireless communication technology may be referred to as a Radio Access Network (RAN). The radio access network can manage radio resources, provide access service for the terminal, and further complete the forwarding of control signals and user data between the terminal and the core network.

The access network equipment may include, among other things, equipment in the access network that communicates over the air-interface, through one or more sectors, with the wireless terminals. The access network system may be configured to interconvert received air frames with Internet Protocol (IP) packets as routers between the wireless terminal and the rest of the access network, which may include an IP network. The radio access network system may also coordinate management of attributes for the air interface. It should be understood that access network devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home evolved NodeB, or HomeNode B, HNB), BaseBand Unit (BaseBand Unit, BBU), Access Point (AP) in Wireless Fidelity (WIFI) system, Wireless relay Node, Wireless backhaul Node, transmission Point (TRP or transmission Point, TP), etc., and may also be 5G, such as NR, gbb in the system, or transmission Point (TRP or TP), one or a group of antennas (including multiple antennas) of a Base Station in the 5G system, or may also be a transmission panel (NB), a network panel (BBU), or a distributed BBU, DU), and the like.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU, the gNB may further include a Radio Unit (RU), the CU realizes part of the function of the gNB, and the DU realizes part of the function of the gNB, for example, the CU realizes Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP) layer, and the DU realizes the function of radio link control (R L C), Media Access Control (MAC), and physical (physical) layer.

3. Access and mobility management function (AMF) entity: the method is mainly used for mobility management, access management, and the like, and can be used for realizing other functions except session management in Mobility Management Entity (MME) functions, such as functions of lawful interception, or access authorization (or authentication), and the like. In the embodiment of the present application, the method and the device can be used for implementing the functions of the access and mobility management network element.

4. Session Management Function (SMF) entity: the method is mainly used for session management, Internet Protocol (IP) address allocation and management of the UE, selection of a termination point of an interface capable of managing a user plane function, policy control or charging function, downlink data notification, and the like. In the embodiment of the present application, the method and the device can be used for implementing the function of the session management network element.

5. User Plane Function (UPF) entity: i.e. a data plane gateway. The method can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, and the like. The user data can be accessed to a Data Network (DN) through the network element. In the embodiment of the application, the method can be used for realizing the function of the user plane gateway.

6. Data Network (DN): for providing a network for transmitting data. Such as a network of carrier services, an Internet network, a third party's service network, etc.

7. Authentication server function (AUSF) entity: the method is mainly used for user authentication and the like.

8. Network open function (NEF) entity: for securely opening services and capabilities, etc. provided by the 3GPP network functions to the outside.

9. The network storage function (NF) entity is used to store the network function entity and the description information of the service provided by the network function entity, and support service discovery, network element entity discovery, etc.

10. Policy Control Function (PCF) entity: the unified policy framework is used for guiding network behaviors, providing policy rule information for control plane function network elements (such as AMF and SMF network elements) and the like.

11. Unified Data Management (UDM) entity: for handling subscriber identification, access authentication, registration, or mobility management, etc.

12. Application Function (AF) entity: the method is used for carrying out data routing of application influence, accessing network open function network elements, or carrying out strategy control by interacting with a strategy framework and the like.

In the network architecture, an N1 interface is a reference point between a terminal and an AMF entity; the N2 interface is a reference point of AN and AMF entities, and is used for sending non-access stratum (NAS) messages and the like; the N3 interface is a reference point between (R) AN and UPF entities, for transmitting user plane data, etc.; the N4 interface is a reference point between the SMF entity and the UPF entity, and is used to transmit information such as tunnel identification information, data cache indication information, and downlink data notification message of the N3 connection; the N6 interface is a reference point between the UPF entity and the DN for transmitting user plane data, etc.

It should be understood that the network architecture applied to the embodiments of the present application is only an exemplary network architecture described in terms of a conventional point-to-point architecture and a service architecture, and the network architecture to which the embodiments of the present application are applied is not limited thereto, and any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiments of the present application.

It should also be understood that the AMF entity, SMF entity, UPF entity, NSSF entity, NEF entity, AUSF entity, NRF entity, PCF entity, UDM entity shown in fig. 1 may be understood as network elements in the core network for implementing different functions, e.g. may be combined into network slices as needed. The core network elements may be independent devices, or may be integrated in the same device to implement different functions, which is not limited in this application.

Hereinafter, for convenience of description, an entity for implementing the AMF will be referred to as an AMF, and an entity for implementing the PCF will be referred to as a PCF. It should be understood that the above-mentioned names are only used for distinguishing different functions, and do not represent that these network elements are respectively independent physical devices, and the present application is not limited to the specific form of the above-mentioned network elements, for example, they may be integrated in the same physical device, or they may be different physical devices. Furthermore, the above nomenclature is only used to distinguish between different functions, and should not be construed as limiting the application in any way, and this application does not exclude the possibility of other nomenclature being used in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may follow the terminology in 5G, and may also adopt other names, etc. The description is unified here, and will not be repeated below.

It should also be understood that the name of the interface between each network element in fig. 1 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this application. In addition, the name of the transmitted message (or signaling) between the network elements is only an example, and the function of the message itself is not limited in any way.

To facilitate understanding of the embodiments of the present application, a part of technical concepts and communication flows that may be involved in the present application will be first illustrated.

1. Public land mobile network

Public networks, i.e., public land mobile networks (P L MN), are established and operated by governments or operators approved for providing land mobile services to the public.

Different P L MN Identities (IDs) can be used to distinguish different P L MN networks, where P L MN identities consist of two parts, a Mobile Country Code (MCC) and a Mobile Network Code (MNC), where the MCC uniquely identifies a country to which a mobile subscriber belongs, e.g., the MCC in china is 460. MNC uniquely identifies a network in that country, e.g., the MNC in china is 00, and the MNC in china is 01.

China Mobile P L MN is 46000,46002,46007.

China unicom P L MN is 46001,46006.

The China telecom P L MN is 46003,46005.

For a particular terminal device, it is usually necessary to maintain several different types of P L MN.. in general, P L MN can be classified into the following types:

home public land mobile network (home P L MN, HP L MN) P L MN. of Universal Subscriber Identity Module (USIM) of terminal equipment corresponding to International Mobile Subscriber Identity (IMSI) is only one for a certain user, which belongs to P L MN.

An equivalent home public land mobile network (equivalent HP L MN, EHP L MN) is that a home P L MN. which is equal to a P L MN currently selected by a terminal device, for example, an operator corresponding to the HP L MN may have different number sections, for example, three number sections of 46000,46002 and 46007 are provided for China Mobile, wherein 46002 and 46007 are EHP L MN relative to 46000, and the operator writes into a USIM card when burning the card.

Equivalent public land mobile networks (equivalent P L MN, EP L MN) P L MN, which is in equal priority with the P L MN currently selected by the terminal device, P L MN., which is equal to the current network HP L MN, if the terminal device is at home, then EP L MN becomes EHP L MN, if the terminal device is at roaming, then EP L MN becomes EHP L MN.

Registered public land mobile network (registered P L MN, RP L MN) the P L MN which the terminal device registered before the last power-off or network-off will be temporarily stored on the USIM card.

The user controlled public land mobile network (user controlled P L MN, UP L MN) is a parameter stored on the handset card that is relevant for P L MN selection.

Operator controlled P L MN (OP L MN), a parameter stored on the handset card that is relevant for P L MN selection.

Visiting public land mobile network (visited P L MN, VP L MN), P L MN. visited for the terminal user, its P L MN and MCC of IMSI, MNC are not identical, one VP L MN will be selected when the terminal loses coverage.

2. User equipment routing strategy

In the 5G network, a concept of user equipment routing policy (URSP) is introduced, that is, the 5G core network provides, to the terminal device, the URSP information to be followed by the terminal device through the PCF, so that the terminal device may route data to be sent by an Application (APP) according to one or more rules in the URSP information, including routing to an already established Protocol Data Unit (PDU) session, or triggering establishment of a new PDU session, or whether the PDU session can be offloaded to a non-3GPP access outside the PDU session. The URSP information may include the following contents:

"flow filtration (traffic filter): application identification (app ID) ": indicating which applications apply to the rule;

seamless offload (non-seamless offload) indicating whether the corresponding PDU session can be offloaded (offloaded) to a wireless local area network (W L AN);

slice information (slice info): a single or multiple slices (S-NSSAI) for indicating that a corresponding PDU session is supported by an application;

continuity Types (CT): a session and service continuity mode (SSC mode) for indicating a session and service continuity mode (SSC mode) that can be used for applying a corresponding PDU session;

data Network Name (DNN): the PDU conversation corresponding to the application supports the name information of the data network;

access Type (AT): indicating the access type of the PDU session corresponding to the application.

The name of the parameter information in the URSP information is different but the meaning of the parameter information is the same as the network architecture evolves and a new service scenario appears. The name may be modified in the subsequent new service scenario, but the same parameter is indicated as long as the meaning is not changed.

For example, the flow filtration becomes: a traffic description (traffic descriptor);

the seamless unloading becomes: a non-seamless download indication (non-seamless download indication);

the slice information becomes: network slice selection (network slice selection);

the continuity type becomes: session continuity mode selection (SSC mode selection);

the data network name becomes: data network name selection (DNN selection);

the access type becomes: an access type (access type preference) is preferred.

Meanwhile, the new service scene is also added with: a route selection description (route selection descriptor) for describing components of the route selection.

The routing description includes parameters such as seamless download indication, network slice selection, session continuity mode selection, data network name selection and preferred access type.

In addition, the new service scene is added with: the priority (rule precedence) of the URSP rule and the route selection description priority (route selection description precedence) are used to describe the priority of the URSP rule and the priority of the route selection description, respectively.

Wherein the URSP rule includes a priority of the rule, a traffic description, one or more routing descriptions; the routing description also includes the parameters of the priority of the routing description, the indication of seamless downloading, the selection of network slice, the selection of session continuity mode, the selection of data network name and the preferred access type.

The network slice selection, the session continuity mode selection, the data network name selection and the preferred access type are 5G PDU session parameters, and the parameters are used for matching the existing PDU session or building a new PDU session.

And, if the seamless download indication is included in the routing description, the routing description will not include network slice selection, session continuity mode selection, data network name selection and preferred access type.

With the development of communication technology, a plurality of APPs may be installed on a terminal device, and different APPs have different requirements for delay, bandwidth, and the like, so that a user may use different routing rules when starting different APPs, for example, different network slice types may be used.

At this time, the network side may send the URSP information to the terminal device, and the terminal device receives and saves the URSP information. Specifically, fig. 2 is a schematic diagram of a path for sending URSP information to a terminal device from a network side.

As shown in fig. 2, the PCF may first send the URSP information to the AMF, and then the AMF sends the URSP information to the access network device (e.g., the gNB), and the access network device sends the URSP information to the terminal device. The PCF may send the URSP information to the terminal device through a non-access stratum (NAS) message, that is, the PCF transmits the URSP information to the terminal device through the AMF and the access network device, and at this time, the AMF and the access network device do not perceive the content of the URSP information.

The URSP information includes at least one URSP rule, each URSP rule corresponds to at least one APP, that is, when any one of the at least one APP is started, the URSP rule can be searched according to the URSP parameter of the application, and the data to be sent by the APP is routed according to the URSP rule. In addition, the APP may correspond to a plurality of rules in the URSP information, and when the APP is started, the plurality of rules may be searched according to the URSP parameters, and data to be sent by the APP may be routed according to the plurality of URSP rules.

At this point, the end device may use the URSP rule to determine how to route outgoing traffic. The end device may route traffic to an established PDU session, may offload traffic to a non-3GPP access outside of the PDU session, or may trigger establishment of a new PDU session.

By way of example, the URSP parameters may include one or more of a traffic description, a seamless download indication, a network slice selection, a session continuity mode selection, a data network name, an access type, and a routing description, among others.

3. Managing terminal device policy command messages

In a 5G network, in order to meet different service requirements of a terminal device, different policy control services are generally provided for the terminal device through a PCF. The management terminal device policy command (management UE policy command) message may be used to carry the relevant policy information to the terminal device, that is, the PCF may send the relevant policy information to the terminal device through the management terminal device policy command message. For example, the policy command message for managing the terminal device may be used to carry the URSP information to the terminal device.

Fig. 3 is a schematic diagram illustrating an example of a cell structure of a policy command message for managing terminal devices, as shown in fig. 3, one policy command message for managing terminal devices may carry URSP information corresponding to a plurality of P L MNs, that is, the URSP information is usually sent in the dimension of P L MN.

In fig. 3, the management terminal device policy command message carries n pieces of (n is an integer greater than or equal to 1) URSP information, which are respectively in one-to-one correspondence with n P L MNs, for example, URSP #1 is the URSP information of P L MN #1, URSP #2 is the URSP information of P L MN #2, and URSP # n is the URSP information of P L MN # n.

Fig. 4 is a schematic diagram of signaling interaction for PCF to send URSP information to terminal device, as shown in fig. 3 and 4, PCF may send n URSP information corresponding to the above-mentioned n P L MNs to terminal device at the same time through a policy command message (hereinafter referred to as command message) of managing terminal device.

Specifically, the terminal device receives the command message, where the command message carries n pieces of URSP information corresponding to n P L MNs, and at this time, the terminal device determines, according to the identifier of its HP L MN, which one of the n P L MNs is its own HP L MN, and stores the URSP information corresponding to the HP L MN, and for the URSP information corresponding to P L MNs other than the HP L MN, the terminal device discards unconditionally, that is, the terminal device does not store the URSP information corresponding to P L MNs other than the HP L MN.

For example, the terminal device determines that P L MN #2 of the n P L MNs in fig. 3 is its HP L MN according to the identity of its HP L MN, and the terminal device only needs to store the URSP #2 and unconditionally discards the URSP information corresponding to other P L MNs.

According to the existing protocol progress, when the terminal device determines that the command message carries URSP information of other P L MN besides HP L MN, the terminal device replies a management terminal device policy command reject (management UE policy command request) message to the PCF.

The management terminal device policy order rejection message (hereinafter, referred to as a rejection message) may be used to indicate the result of the terminal device processing the URSP information carried by the P L MNs, and in particular, may be used to indicate that the URSP information of that P L MN is saved (i.e., which P L MN is indirectly indicated to the PCF as the HP L MN as well), and that the URSP information of which P L MN or MNs is discarded (i.e., which P L MN is indirectly indicated to the PCF as the non-HP L MN as well).

Fig. 5 is a schematic diagram of an example of a cell structure for managing a terminal policy command reject message, since P L MN #2 is the HP L MN of the terminal, the terminal stores the URSP #2, and unconditionally discards the URSP information corresponding to other P L MNs, as shown in fig. 5, the processing result of the URSP information corresponding to the n P L MNs can be fed back to the PCF through the reject message, that is, the PCF is indicated by the reject message to store the URSP #2, and the other URSP information is discarded.

It should be understood that the terminal device may already store the URSP information of the HP L MN before storing the URSP information corresponding to the HP L MN in the command message, and at this time, the old URSP information may be updated by the new URSP information, for example, addition, deletion, or replacement is performed.

It should be understood that the foregoing descriptions of the concepts related to P L MN, URSP, and management terminal device policy command message are only for facilitating understanding of the technical solutions of the present application, and do not constitute any limitation to the technical solutions of the present application.

As can be seen from the foregoing description, the unconditional discarding of the URSP information of the non-HP L MN issued by the terminal device on the network side may cause the terminal device to be unable to reasonably utilize the URSP information in a special network and a special scenario, in some scenarios, the network side may not issue the URSP information of the HP L MN of the terminal device, for example:

1. a network with subscription information, in particular a network with a plurality of small operators sharing a core network;

2. in a multi-operator core network (MOCN) network, one RAN may be connected to multiple operator core network nodes, i.e., a common base station, and not a common core network.

3. In a roaming scenario.

In addition, even if the network side issues the URSP information of the HP L MN, under some circumstances, the URSP information of the HP L MN stored in the terminal device may be lost, so that the terminal device cannot reasonably utilize the URSP information, and the situation that the terminal device does not have the possibility of using the URSP may be caused, thereby causing adverse effects on the data transmission efficiency (i.e., routing efficiency) of the terminal device, and reducing user experience.

Based on the above problems, the present application provides a data transmission method and a communication device, so that a terminal device can reasonably store and reasonably use URSP information of a non-HP L MN issued by a network side, thereby improving the efficiency of data routing of the terminal device and improving user experience.

The method for data transmission provided by the embodiment of the present application is described below with reference to the accompanying drawings, and the method may be applied to a terminal device, for example, the terminal device may be a UE in the communication system shown in fig. 1.

Fig. 6 is a schematic flow chart of a method 200 for data transmission provided by an embodiment of the present application. Hereinafter, a method 200 provided by the embodiment of the present application is described with reference to fig. 6, where the method 200 includes:

in step 210, the terminal device stores first user equipment routing policy, URSP, information, the first URSP information being URSP information corresponding to a first public land mobile network, P L MN, the first P L MN being a P L MN other than the home public land mobile network, HP L MN.

In step 220, the terminal device obtains a first URSP rule from the first URSP information, where the first URSP rule is used to transmit data to be transmitted of the started application program.

Specifically, the method 200 provided in this embodiment of the present application may be applied to a terminal device in any communication system (for example, a 5G network), and the terminal device may store the first URSP information after acquiring the first URSP information, so as to be used later.

In step 210, the terminal device stores the first URSP information, which may also be understood as that the terminal device stores (or stores) the first URSP information in a local memory of the terminal device for use later when the terminal device needs to perform data transmission (for example, to open an application).

The first URSP information is URSP information corresponding to a first P L MN, or the first URSP information is URSP information for the terminal device in a first P L MN network, the first P L MN is a P L MN other than an HP L MN, i.e. a first P L MN is a non-HP L MN.

The terminal device can store the first URSP information only after the terminal device first needs to acquire the first URSP information, and how the terminal device acquires the first URSP information is not limited in the embodiment of the application.

Alternatively, the first URSP information may be uploaded by the user locally.

Specifically, when a started application needs to perform data transmission (i.e., perform data routing), data may be routed using the applicable URSP rule of the started application, i.e., the first URSP rule of the present application. At this time, the first URSP rule may be acquired from the first URSP information according to the URSP parameter of the started application.

As can be seen from the foregoing description, the URSP information may include at least one URSP rule, and the terminal device may obtain a first URSP rule from the first URSP information, where the first UPSP rule is used for data routing of the started application program.

It should be understood that, here, the terminal device obtains the first URSP rule from the first URSP information, it may be understood that the terminal device searches, retrieves, finds, or matches the first URSP rule from the first URSP information.

In this embodiment of the application, the terminal device acquires the first URSP rule from the first URSP information, and may successfully acquire the first URSP rule or may not successfully acquire the first URSP rule, which is not limited in this application.

How to obtain the first URSP rule from the first URSP information will be illustrated below.

When the started application needs to perform data routing, the terminal device may first determine the URSP parameter of the started application, and then search for a first URSP rule from at least one URSP rule included in the first URSP information according to the URSP parameter.

According to the data transmission method 200 provided by the embodiment of the application, after acquiring the first URSP information, the terminal device may reasonably store the first URSP information for later use, where the first URSP information is URSP information corresponding to the first P L MN, and the first P L MN is a P L MN other than the HP L MN, and when a started application of the terminal device needs to perform data routing, it may attempt to acquire a URSP rule for the started application to perform data transmission from the first URSP information, so that efficiency of data routing of the terminal device can be improved, and user experience is improved.

Optionally, if the terminal device successfully acquires the first URSP rule from the first URSP information, the terminal device may transmit the data to be transmitted of the started application program by using the first URSP rule. At this point, the end device may use the first URSP rule to determine how to route outgoing traffic.

For example, the terminal device may route data to be transmitted for the initiated application to the established PDU session.

For another example, the terminal device may also route the data to be transmitted of the started application to a new PDU session.

For another example, the terminal device may also route the data to be transmitted of the started application to a non-3GPP access (such as W L AN) outside the PDU session.

Optionally, the terminal device may unsuccessfully obtain the first URSP rule from the first URSP information, and at this time, the terminal device may transmit the data to be transmitted of the started application program by using a default configuration.

Optionally, the first P L MN may be an equivalent home public land mobile network EHP L MN., and since the network side may not directly issue the HP L MN in some scenarios, but directly issues the EHP L MN, according to the method 200 provided by the present application, the URSP information corresponding to the EHP L MN may be stored for later use, which is beneficial to improving the efficiency of the data routing of the terminal device, and further improves the use experience.

Optionally, the first P L MN may also be any one of an equivalent public land mobile network EP L MN, a registered public land mobile network RP L MN, a user controlled public land mobile network UP L MN, an operator controlled public land mobile network OP L MN, a visited public land mobile network VP L MN, and the like.

Optionally, after the SIM card of the terminal device is removed, the stored first URSP information may be cleared, so as to reduce memory usage.

Optionally, before step 210, that is, before the terminal device stores the first URSP information, the method 200 further includes:

and receiving a policy message sent by a network side, wherein the policy message comprises URSP information corresponding to at least one P L MN, and the at least one P L MN comprises the first P L MN.

That is, the terminal device may receive a policy message including URSP information corresponding to the at least one P L MN from the network side, and may confirm which of the at least one P L MN is the first P L MN and then store the URSP information of the first P L MN, i.e., store the first URSP information.

As an example, the system or protocol may provide that the first P L MN is an EHP L MN, and then the terminal device may determine which of the at least one P L MN is its own EHP L MN after receiving the policy message, and then store the URSP information (i.e., the first URSP information) of the EHP L MN.

It should be understood that the "protocol" in the embodiment of the present application may refer to a standard protocol in the communication field, and may include, for example, L TE protocol, NR protocol, and related protocols applied in future communication systems, which is not limited in the present application.

Optionally, the terminal device may or may not store the URSP information of the P L MN other than the first P L MN in the at least one P L MN, which is not limited in this application.

Optionally, the terminal device receives the policy message sent by the network side, where the policy message may be a policy message sent by the PCF or a cloud server, and this is not limited in this application.

Optionally, the policy message may be a policy command message for managing the terminal device or other messages, which is not limited in this application.

Optionally, the at least one P L MN may include an HP L MN of the terminal device, and the URSP information corresponding to the HP L MN is the second URSP information fig. 7 is a schematic flow chart of another example of the method 200 for data transmission provided in this embodiment of the present application, as shown in fig. 7, at this time, step 210 may include:

in step 211, the terminal device stores the first URSP information and the second URSP information.

And prior to step 220, method 200 further comprises:

in step 219, the terminal device acquires the first URSP rule from the second URSP information, and fails to acquire the first URSP rule.

Fig. 8 is a schematic flow chart of still another example of a method 200 for data transmission according to an embodiment of the present application. As shown in fig. 8, optionally, before step 220, the method 200 further comprises:

in step 218, the terminal device determines that the second URSP information is not stored, and the second URSP information is the URSP information corresponding to the HP L MN.

Specifically, as can be seen from the foregoing description, the terminal device may preferentially attempt to acquire the first URSP rule from the second URSP information (i.e., the URSP information of the HP L MN), but in some cases, the terminal device may not locally store the second URSP information.

According to the technical scheme provided by the embodiment of the application, under the condition that the network side does not send out the URSP information of the HP L MN, the URSP information of the non-HP L MN can be used, so that the situation that no URSP is available for the terminal equipment can not occur, the efficiency of data routing of the terminal equipment can be improved, and the use experience of a user can be improved.

Optionally, the aforementioned at least one P L MN may include a third P L MN, the third P L MN being a P L MN other than the HP L MN, and the URSP information corresponding to the third P L MN being third URSP information, it is easily understood that the third P L MN and the first P L MN are two different P L MNs.

Fig. 9 is a schematic flow chart of still another example of a method 200 for data transmission according to an embodiment of the present application. As shown in fig. 9, at this time, step 210 may include:

in step 212, the terminal device stores the first URSP information and the third URSP information.

In step 220, if the first URSP rule is not successfully acquired from the first URSP information, the method 200 further includes:

in step 230, the terminal device obtains the first URSP rule from the third URSP information.

Optionally, the first P L MN is EHP L MN and the third P L MN is EP L MN.

Optionally, the aforementioned at least one P L MN may include the first P L MN, the HP L MN and the third P L MN. at the same time, fig. 10 is a schematic flow chart of still another example of the method 200 for data transmission provided in this embodiment of the present application, and fig. 11 is a logic relationship diagram for acquiring the first URSP rule corresponding to fig. 10.

As shown in fig. 10, at this time, step 210 may include step 213, and the method 200 specifically includes:

in step 213, the terminal device stores the first URSP information, the second URSP information and the third URSP information.

In step 220, the terminal device acquires the first URSP rule from the first URSP information, and fails to acquire the first URSP rule.

Specifically, in order to increase the probability of acquiring the first URSP rule, the terminal device may store a plurality of pieces of URSP information, for example, simultaneously store the first URSP information, the second URSP information, and the third URSP information. When the terminal device fails to acquire the first URSP rule from the second URSP information, the terminal device may continue to attempt to acquire the first URSP rule from the first URSP information and the third URSP information until successful acquisition is achieved.

Here, the priority of the first P L MN may be higher than that of the third P L MN, that is, the terminal device may preferentially acquire the URSP information from the first URSP information and acquire the URSP information from the third URSP information after not acquiring the URSP information.

According to the embodiment of the application, the terminal equipment can respectively try to acquire the first URSP rule from the second URSP information, the first URSP information and the third URSP information, and the probability of acquiring the first URSP rule is increased, so that the efficiency of data routing of the terminal equipment is improved, and the use experience of a user is improved.

As shown in fig. 11, the terminal device first obtains the first URSP rule from the second URSP information, and if the first URSP rule is successfully obtained, the first URSP rule is directly used for data transmission (i.e. routing the traffic of the started application), otherwise, the first URSP rule is continuously obtained from the first URSP information, if the first URSP rule is not successfully obtained yet, the first URSP rule is then obtained from the third URSP information, and if the first URSP rule is not successfully obtained yet, the terminal device may use a default configuration to transmit the data to be transmitted of the started application at this time.

The foregoing embodiment describes the method 200 for data transmission provided herein with reference to fig. 6-11, and in order to more fully illustrate the method 200, the method 300 for data transmission provided herein will be described with reference to fig. 12, wherein the method 300 can be regarded as a specific application of the method 200, i.e., the embodiment shown in fig. 12 can be regarded as a more specific example of the method 200.

Fig. 12 is a schematic flow chart of a method 300 for data transmission provided by an embodiment of the present application. A method 300 provided by an embodiment of the present application is described below with reference to fig. 12, where the method 300 includes:

step 310, the PCF sends a terminal device policy management command message to the terminal device, where the message includes URSP information corresponding to at least one P L MN, the at least one P L MN includes a first P L MN, the first P L MN is a P L MN other than the HP L MN, and the URSP information corresponding to the first P L MN is the first URSP information.

In the embodiment of the present application, the at least one P L MN does not include the HP L MN of the terminal device.

In step 320, the terminal device stores the first URSP information for later use.

Step 330, the terminal device sends a policy command rejection message for managing the terminal device to the PCF, where the rejection message is used to indicate the result of processing the URSP information corresponding to the at least one P L MN by the terminal device.

For example, it may be used to indicate that the terminal device saved the first URSP information.

As another example, it may also be used to instruct the terminal device to discard the URSP information of other P L MNs.

Step 340, starting some application program APP installed on the terminal device, and there is data to be routed.

For example, the application may be any one of chat software, shopping software, a browser, payment software, video software, and the like.

In step 350, the terminal device may obtain the first URSP rule from the first URSP information, for example, may retrieve the first URSP rule from a plurality of rules in the first URSP information according to the URSP parameters of the application.

Alternatively, before the terminal device acquires the first URSP rule from the first URSP information, the terminal device may first confirm that it does not store the URSP information of the HP L MN.

In the embodiment of the application, the terminal device successfully acquires the first URSP rule from the first URSP information.

And step 360, the terminal equipment uses the first URSP rule to perform data routing.

In this embodiment of the present application, the first URSP rule is used to instruct the terminal device to use an existing PDU or establish a new PDU for data upload to the access network device.

Optionally, the access network device is a base station in a 5G communication system, i.e., a gNB.

The method for data transmission according to the embodiment of the present application is described in detail above with reference to fig. 1 to 12, and the apparatus according to the embodiment of the present application is described in detail below with reference to fig. 13 and 14. It should be understood that the apparatus shown in fig. 13, 14 can implement the steps of one or more of the method flows shown in fig. 6-12. To avoid repetition, detailed description is omitted.

Fig. 13 is a schematic block diagram of a communication device 400 provided in an embodiment of the present application. As shown in fig. 13, the communication apparatus 400 includes: a storage unit 410 and an acquisition unit 420.

A storage unit 410 for storing first user equipment routing policy, URSP, information, the first URSP information being URSP information corresponding to a first public land mobile network, P L MN, the first P L MN being a P L MN other than a home public land mobile network, HP L MN;

an obtaining unit 420, configured to obtain a first URSP rule from the first URSP information, where the first URSP rule is used to transmit data to be transmitted of a started application.

Optionally, the communication apparatus 400 further comprises:

a transceiving unit 430, configured to receive a policy message sent by a network side before the storing unit 410 stores the first URSP information, where the policy message includes URSP information corresponding to at least one P L MN, and the at least one P L MN includes the first P L MN.

Optionally, the at least one P L MN includes the HP L MN, the URSP information corresponding to the HP L MN is second URSP information, the storage unit 410 is further configured to store the second URSP information, and the obtaining unit 420 is specifically configured to obtain the first URSP rule from the second URSP information, where the first URSP rule is not successfully obtained.

Optionally, before the obtaining unit 420 obtains the first URSP rule from the first URSP information, the obtaining unit 420 is further configured to determine that second URSP information is not stored, where the second URSP information is URSP information corresponding to the HP L MN.

Optionally, the at least one P L MN includes a third P L MN, the third P L MN is a P L MN other than the HP L MN, and the URSP information corresponding to the third P L MN is third URSP information, the storage unit 410 is further configured to store the third URSP information, and if the obtaining unit 420 does not successfully obtain the first URSP rule from the first URSP information, the obtaining unit 420 is further configured to obtain the first URSP rule from the third URSP information.

Optionally, if the obtaining unit 420 does not successfully obtain the first URSP rule from the first URSP information, the transceiver unit 430 is configured to transmit the data to be transmitted of the started application program by using a default configuration.

Optionally, if the obtaining unit successfully obtains the first URSP rule from the first URSP information, the transceiving unit 430 is configured to transmit the to-be-transmitted data of the started application program by using the first URSP rule.

Optionally, the policy message is a policy command message for managing the terminal device.

Optionally, the transceiver unit 430 is specifically configured to: and receiving the policy message sent by a policy control entity PCF or a cloud server.

Optionally, the first P L MN is an equivalent home public land mobile network, EHP L MN.

Specifically, the communication apparatus 400 may correspond to the terminal device in the communication methods 200 and 300 according to the embodiments of the present application, or a chip configured in the terminal device. The communication apparatus 400 may include means for performing the methods performed by the terminal devices of fig. 6-12. Moreover, each unit and the other operations and/or functions in the communication apparatus 400 are respectively for implementing the corresponding flows of the methods 200 and 300, and the specific processes of each unit for executing the corresponding steps are already described in detail in the methods 200 and 300, and are not repeated herein for brevity.

The communication device 400 may be a smart terminal or a wearable device, and the transceiver 430 may be a transceiver or a transceiver circuit. Optionally, the transceiver may also be an input/output circuit or interface.

The communication device 400 may also be a chip. The transceiving unit 430 may be an input/output circuit or an interface of a chip.

In a possible implementation manner, the communication apparatus 400 may be the terminal device 50, wherein the functions of the storage unit 410 and the obtaining unit 420 may be implemented by the processor 502 of the terminal device 50, and the functions of the transceiving unit 430 may be implemented by the transceiver 501 (i.e., the control circuit and the antenna together) of the terminal device. The structure of the terminal device according to the embodiment of the present application is described below with reference to fig. 14.

Fig. 14 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device can be applied to the system shown in fig. 1, and performs the functions of the terminal device in the above method embodiment. For convenience of explanation, fig. 14 shows only main components of the terminal device. As shown in fig. 14, the terminal device 50 includes a processor, a memory, a control circuit, an antenna, and an input-output means. The processor is mainly configured to process the communication protocol and the communication data, control the entire terminal device, execute a software program, and process data of the software program, for example, to support the terminal device to perform the actions described in the above method embodiments. The memory is used primarily for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The control circuit and the antenna together, which may also be called a transceiver, are mainly used for transceiving radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user.

When the terminal device is started, the processor can read the software program of the memory, interpret and execute the instruction of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor outputs a baseband signal to the radio frequency circuit after performing baseband processing on the data to be sent, and the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.

Those skilled in the art will appreciate that fig. 14 shows only one memory and one processor for ease of illustration. In an actual terminal device, there may be multiple processors and multiple memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be a memory element on the same chip as the processor, that is, an on-chip memory element, or a separate memory element, which is not limited in this embodiment.

As an optional implementation manner, the terminal device may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process a communication protocol and communication data, and the central processing unit is mainly used to control the whole terminal device, execute a software program, and process data of the software program. The processor of fig. 14 may integrate the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal device may include a plurality of baseband processors to accommodate different network formats, the terminal device may include a plurality of central processors to enhance its processing capability, and various components of the terminal device may be connected by various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.

In the embodiment of the present application, the antenna and the control circuit having the transceiving function may be regarded as the transceiving unit 501 of the terminal device 50, for example, for supporting the terminal device to perform the receiving function and the transmitting function. The processor 502 with processing functionality is considered as the processing unit 502 of the terminal device 50. As shown in fig. 14, the terminal device 50 includes a transceiving unit 501 and a processing unit 502. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Alternatively, a device for implementing a receiving function in the transceiving unit 501 may be regarded as a receiving unit, and a device for implementing a sending function in the transceiving unit 501 may be regarded as a sending unit, that is, the transceiving unit 501 includes a receiving unit and a sending unit, the receiving unit may also be referred to as a receiver, an input port, a receiving circuit, and the like, and the sending unit may be referred to as a transmitter, a sending circuit, and the like.

The processor 502 may be configured to execute the instructions stored in the memory to control the transceiver unit 501 to receive and/or transmit signals, so as to implement the functions of the terminal device in the above-described method embodiments. The processor 502 also includes an interface to implement signal input/output functions. As an implementation manner, the function of the transceiving unit 501 may be considered to be implemented by a transceiving circuit or a dedicated chip for transceiving.

It should be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), and the processor may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory the volatile memory may be Random Access Memory (RAM) which functions as an external cache memory, by way of example and not limitation, many forms of Random Access Memory (RAM) may be used, such as static RAM (static RAM), SRAM, Dynamic RAM (DRAM), synchronous DRAM (synchronous, SDRAM), double data rate Synchronous DRAM (SDRAM), SDRAM (SDRAM), and DDR direct access DRAM (DDR L).

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of any of the embodiments shown in figures 6-12.

There is also provided a computer readable medium having program code stored thereon, which when run on a computer causes the computer to perform the method of any one of the embodiments shown in fig. 6-12.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

For ease of understanding, the terms referred to in the introduction to the present application are described below.

In the embodiments of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. If the information indicated by a certain piece of information (such as the "indicating information" in the foregoing description) is referred to as information to be indicated, in a specific implementation process, there are many ways to indicate the information to be indicated, for example, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein an association relationship exists between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other part of the information to be indicated is known or predetermined. For example, the indication of the specific information may be implemented by means of a predetermined arrangement order of the respective information (e.g., protocol specification), thereby reducing the indication overhead to some extent.

In the embodiments of the present application, the terms and acronyms, terminal device routing policy (URSP), public land mobile network (P L MN), policy control function entity (PCF), Protocol Data Unit (PDU), etc. are given as illustrative examples for convenience of description and should not be construed as limiting the application in any way.

In the embodiments of the present application, the first, second, third and various numbers are only used for convenience of description and are not used to limit the scope of the embodiments of the present application. For example, different indication information is distinguished.

The "communication protocol" referred to in the embodiments of the present application may refer to a standard protocol in the field of communication, and may include, for example, L TE protocol, NR protocol, and related protocols applied in future communication systems, which is not limited in the present application.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In the present application, "at least one" means one or more, "a plurality" means two or more. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

In the embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data transmission method is applied to terminal equipment and is characterized by comprising the following steps:

storing first user equipment routing policy, URSP, information, the first URSP information being URSP information corresponding to a first public land mobile network, P L MN, the first P L MN being a P L MN other than a home public land mobile network, HP L MN;

and acquiring a first URSP rule from the first URSP information, wherein the first URSP rule is used for transmitting data to be transmitted of the started application program.

2. The method according to claim 1, wherein prior to said storing first user equipment routing policy, URSP, information, the method further comprises:

receiving a policy message sent by a network side, wherein the policy message includes URSP information corresponding to at least one P L MN, and the at least one P L MN includes the first P L MN.

3. The method of claim 2, wherein the at least one P L MN comprises the HP L MN, and wherein the corresponding URSP information of the HP L MN is a second URSP information;

the storing the first user equipment routing policy URSP information includes:

storing the second URSP information;

before the obtaining the first URSP rule from the first URSP information, the method further includes:

and acquiring the first URSP rule from the second URSP information without successfully acquiring the first URSP rule.

4. The method of claim 2, wherein prior to said obtaining a first URSP rule from said first URSP information, said method further comprises:

determining that second URSP information is not stored, the second URSP information being URSP information corresponding to the HP L MN.

5. The method of any of claims 2-4, wherein the at least one P L MN comprises a third P L MN, the third P L MN is a P L MN other than the HP L MN, and the corresponding URSP information of the third P L MN is third URSP information;

the storing the first user equipment routing policy URSP information includes:

storing the third URSP information;

if the first URSP rule is not successfully acquired from the first URSP information, the method further includes:

and acquiring the first URSP rule from the third URSP information.

6. The method according to any of claims 1-4, wherein if the first URSP rule is not successfully obtained from the first URSP information, the method further comprises:

and transmitting the data to be transmitted of the started application program by using default configuration.

7. The method according to any of claims 1-4, wherein if the first URSP rule is successfully obtained from the first URSP information, the method further comprises:

and transmitting the data to be transmitted of the started application program by using the first URSP rule.

8. The method according to any of claims 2-5, wherein the policy message is a manage end device policy command message.

9. The method according to any of claims 2-5, wherein the receiving the policy message sent by the network side comprises:

and receiving the policy message sent by a policy control entity PCF or a cloud server.

10. The method of any of claims 1-9, wherein the first P L MN is an equivalent home public land mobile network, EHP L MN.

11. A communications apparatus, comprising:

a storage unit, configured to store first user equipment routing policy, URSP, information, the first URSP information being URSP information corresponding to a first public land mobile network, P L MN, the first P L MN being a P L MN other than a home public land mobile network, HP L MN;

an obtaining unit, configured to obtain a first URSP rule from the first URSP information, where the first URSP rule is used to transmit data to be transmitted of a started application program.

12. The communications device of claim 11, further comprising:

a transceiving unit, configured to receive a policy message sent by a network side before the storage unit stores the first URSP information, where the policy message includes at least one URSP information corresponding to a P L MN, and the at least one P L MN includes the first P L MN.

13. The communications apparatus of claim 12, wherein the at least one P L MN includes the HP L MN, and wherein the URSP information corresponding to the HP L MN is a second URSP information;

the storage unit is further configured to:

storing the second URSP information;

the obtaining unit is specifically configured to:

14. The apparatus according to claim 12, wherein before the obtaining unit obtains the first URSP rule from the first URSP information, the obtaining unit is further configured to:

15. The communications apparatus as claimed in any of claims 12-14, wherein the at least one P L MN comprises a third P L MN, the third P L MN is a P L MN other than the HP L MN, and the URSP information corresponding to the third P L MN is third URSP information;

the storage unit is further configured to:

storing the third URSP information;

if the obtaining unit does not successfully obtain the first URSP rule from the first URSP information, the obtaining unit is further configured to:

and acquiring the first URSP rule from the third URSP information.

16. The apparatus according to any of claims 11-14, wherein if said obtaining unit unsuccessfully obtains the first URSP rule from the first URSP information, the apparatus further comprises:

and the transceiving unit is used for transmitting the data to be transmitted of the started application program by using default configuration.

17. The apparatus according to any one of claims 11 to 14, wherein if the acquiring unit successfully acquires the first URSP rule from the first URSP information, the apparatus further comprises:

and the transceiving unit is used for transmitting the data to be transmitted of the started application program by using the first URSP rule.

18. A communication apparatus according to any of claims 12-15, wherein the policy message is a manage end device policy command message.

19. The communication device according to any of claims 12-15, wherein the transceiver unit is specifically configured to:

20. The communications device according to any of claims 11-19, wherein the first P L MN is an equivalent home public land mobile network, EHP L MN.

21. A computer-readable storage medium, having stored thereon a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 10.

22. A chip system, comprising: a processor for calling and running a computer program from a memory so that a communication device in which the system-on-chip is installed performs the method of any one of claims 1 to 10.

23. A communications apparatus comprising at least one processor configured to couple to a memory, read and execute instructions in the memory, and to implement the method of any one of claims 1 to 10.